AVI Video Support

Feature enhancement request:  Support for AVI format video files.
Thanks!
Rob

I'll add to the backlog  for the next release.

Thanks!

I looked into this unfortunately the html5 video control that we are using to load videos does not support avi. I recommend using ffmpeg to convert the video until a better solution can be found.


[BUG] JSON deserialization failure when retrieving host inventory

Describe the bug
When executing wash ctl get inventory <HOST_ID>  the command exits with
...Error: JSON deserialization failure: missing field 'instances' at line 1 column 188
To Reproduce
Steps to reproduce the behavior:

Follow Get started tutorial
After you add HTTP server capability provider run wash ctl get inventory <HOST_ID> as the tutorial suggests.
You'll get an error ...Error: JSON deserialization failure: missing field 'instances' at line 1 column 188

Expected behavior
The command should report the host's inventory.
**Environment (please complete the following information) **

OS:  MacOS
Shell: zsh
wash Version: 0.7.2

I was using the wrong wasmcloud_host docker image. The image from the provided docker-compose has a tag latest but since I already had the latest image in my docker cache, wash executed the command against the wrong host version. This sounds almost like a local issue, however, to prevent similar issues in the future I've explicitly set wasmcloud/wasmcloud_host image to the desired version in the docker-compose file.
Maybe I've missed it, but is there a wash command to get what version has a particular host?

@tadejstanic ATM there isn't a command to get the host version, though we could attach that as a label on the host 🤔 Your best bet is likely to access the dashboard and click the wasmcloud icon in the top right for now if you need the version


Provide conversion APIs between TimeAmount and Swift.Duration

Motivation:
SE-0329: Clock, Instant, and Duration now has a draft implementation in Swift 5.7. It would be ergonomic to provide APIs to convert Swift.Duration to and from NIO.TimeAmount.
Modifications:
Add TimeAmount.init(_: Duration) and Duration.init(_: TimeAmount) extensions. Because Duration has higher precision and range, the conversion to TimeAmount is truncated and clamped to the maximum expressible nanosecond value, Int64.max.
Result:
Resolves #2175.

This would resolve https://github.com/apple/swift-nio/issues/2175

I've left a brief note in the implementation: additionally, I agree with @fabianfett's suggestion that this lives in a _NIOBeta57 target and product for a while, as there is a risk of things breaking.

Why a 5.7 specific module rather than a something more general purpose?

I've left a brief note in the implementation: additionally, I agree with @fabianfett's suggestion that this lives in a _NIOBeta57 target and product for a while, as there is a risk of things breaking.

Why a 5.7 specific module rather than a something more general purpose?

For now I created a _NIOBeta57 module, but we can rename it to whatever.

Because the module would only be temporary, we'd remove it when the 5.7 beta lands. Because it's underscored we reserve the right to break it by removing it (which we will). The reason it's not in, say, NIOCore is that the API surface isn't final: the Swift team absolutely may break it down the road, and we don't want users who are using our stable APIs to be broken by that.

Because the module would only be temporary, we'd remove it when the 5.7 beta lands. Because it's underscored we reserve the right to break it by removing it (which we will). The reason it's not in, say, NIOCore is that the API surface isn't final: the Swift team absolutely may break it down the road, and we don't want users who are using our stable APIs to be broken by that.

Ah I was more wondering why we'd have a temporary API breaking module rather than a _NIOBeta or similar that we can keep around the next time we want to add things ahead of a release.

Oh, I see. We could do that I suppose. No strong preference really.


jsref_unescape can not decode chinese word

The unescape() function was deprecated in JavaScript version 1.5. Use decodeURI() or decodeURIComponent() instead.
The unescape() function decodes an encoded string.
https://www.w3schools.com/jsref/jsref_unescape.asp
Can you update the lib?  change the  unescape function. thanks~~
// in cookieStore.js
function read(key) {
	if (!key || !_has(key)) { return null }
	var regexpStr = "(?:^|.*;\\s*)" +
		escape(key).replace(/[\-\.\+\*]/g, "\\$&") +
		"\\s*\\=\\s*((?:[^;](?!;))*[^;]?).*"
	return unescape(doc.cookie.replace(new RegExp(regexpStr), "$1"))
}

Any chance explaining how you got around this, the values in local storage are all in Chinese Characters

I am having the same issue, I initially thought the project got hacked

Created an issue for this only https://github.com/marcuswestin/store.js/issues/283 ... maybe a duplicate


memcached: fix Delete and Get for missing items

according to the godoc of github.com/bradfitz/gomemcache at https://pkg.go.dev/github.com/bradfitz/gomemcache/memcache both Get and Delete may return a memcache.ErrCacheMiss when the key is not found. This should be reflected with a NotFound error for a Get or no error for a Delete.
Used https://github.com/daangn/minimemcached to test this.

Thank you @woutslakhorst


Windows version stalls at initialization

Windows version (on Windows 10 Creator's Update, x64) stalls at a grey screen with an animated square. Window title is 'initial'.

this might be the same issue as #58 with case-sensitive file-paths
I'll test on Windows tonight and check

Possibly fixed in beta4: https://github.com/codeforscience/sciencefair/releases/tag/v1.0.0-beta4 (downloads will appear when they have finished building)

Still not loading beyond the 'initial' grey screen on Windows 10

@gmaciocci, I had similar issue and was able to resolve it by closing the app, removing the ~/.sciencefair folder, and opening the app again.

OK I'll debug on a Windows machine this evening

@joehand no luck on Windows 10.

OK I have identified a set of bugs that are Windows-specific:

[ ] The nanoraf router that is used by choo can't resolve routes in electron+windows. Solution is to use hash routes instead of slash routes (e.g. #home instead of /home)
[ ] The discovery-swarm module uses utp-native for UTP, but it's silently failing on windows10, and because we have TCP turned off we end up with no way to connect at all (rerpoted issue https://github.com/mafintosh/discovery-swarm/issues/27). Short term solution: turn on TCP and UTP. Long term solution: make UTP work on windows.
[ ] The append-tree module used by hyperdrive uses / as the path separator, which breaks on Win (reported issue https://github.com/mafintosh/append-tree/issues/7). Solution: fix append-tree so it uses path.sep which is OS-aware.

I need to fix the above before I can see if there are any more issues, as I can't progress to the point of having metadata synced right now.

@mafintosh preferred that the solution to the append-tree issue should be in hyperdrive, keeping append-tree abstract. So here's the PR for the fix: https://github.com/mafintosh/hyperdrive/pull/159

Found another windows quirk - CSS urls for local files don't work as normal, so node's usually cross platform path-joining breaks things.

v1.0.0-beta5 contains all the above fixes - I suspect there will be more Windows-specific issues but it was becoming impractical to find them without a new release.
Anyone with a Windows machine please feel free to try out this release and report issues in this thread.

beta 5 appears to have broken the Mac release (Sierra 10.12.3):

starting with a nuked .sciencefait folder allows the app to initialise to 99%.
App gets stuck synching initial data at 99%
closing the app and restarting results in the app getting stuck at the grey screen with the animated squares.

Beta5 for windows now installs, opens, passes the square loading logo and then gets stuck at 0% of 'syncing initial data...'.
If you close it down and reopen it, it then gets stuck at the square loading logo, unless you delete the .sciencefair directory in home.

@cboursnell if you nuke the ~/.sciencefair dir and run the app, is there any error in the console?
You can find the console in developer tools with: Ctrl Shift I or F12

This is the error that I get on Win7:
Uncaught ReferenceError: makesafe is not defined
at module.exports.img (C:\Program Files\ScienceFair\resources\app\client\lib\imgpath.js:8)
at CachedSearch._render (C:\Program Files\ScienceFair\resources\app\client\views\search.js:57)
at CachedSearch.CacheElement.render (C:\Program Files\ScienceFair\resources\app\node_modules\cache-component\index.js:37)
at module.exports (C:\Program Files\ScienceFair\resources\app\client\views\search.js:78)
at module.exports (C:\Program Files\ScienceFair\resources\app\client\views\main.js:25)
at module.exports (C:\Program Files\ScienceFair\resources\app\client\views\home.js:5)
at C:\Program Files\ScienceFair\resources\app\node_modules\choo\index.js:43
at emit (C:\Program Files\ScienceFair\resources\app\node_modules\nanorouter\index.js:47)
at Function.<anonymous> (C:\Program Files\ScienceFair\resources\app\node_modules\choo\index.js:58)
at redraw (C:\Program Files\ScienceFair\resources\app\node_modules\nanoraf\index.js:28)

thanks @pkraker, that was fixed in https://github.com/codeforscience/sciencefair/commit/5037dabcc2187512dd0f8dd28783b566a4bd9d62
release coming up after I finish some more bugfixes/enhancements

I think all the issues raised here have been solved by https://github.com/codeforscience/sciencefair/releases/tag/v1.0.0-beta9
As far as I can tell, this issue is now the major/only Windows bug - if anyone can spare some energy to help debug it I would greatly appreciate it.
I'm closing this issue as the specific problems listed here has been solved. Thanks all for your help :)


SUBMARINE-433. Expose Spark Security API with Authz w/ w/o DataMasking and Row Filtering

What is this PR for?
Expose Spark Security API with Authz w/ w/o DataMasking and Row Filtering
Then one is only enabled with security features with authorization and conf restricting
the other is fully applied data masking and row filtering too.
What type of PR is it?
Improvement
Todos

[ ] - Task

What is the Jira issue?

Open an issue on Jira https://issues.apache.org/jira/browse/SUBMARINE-433
Put link here, and add [SUBMARINE-Jira number] in PR title, eg. [SUBMARINE-23]

How should this be tested?

First time? Setup Travis CI as described on https://submarine.apache.org/contribution/contributions.html#continuous-integration
Strongly recommended: add automated unit tests for any new or changed behavior
Outline any manual steps to test the PR here.

pass current travis
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

cc @liuxunorg


Add mirror padding with exponential decay

Closes #12.

The ITK version in CircleCI configuration needs to be changed.


docs(providers): kong ai gateway integration guide redux

Description
Documentation on how to harness LangChain for calling multiple providers/models, using the OpenAI formatter, via Kong AI Gateway.
It describes how to support LangChain, running via Kong gateway, using the ChatOpenAI library.

[x] Lint and test: Run make format, make lint and make test from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/

⚠ ⚠  There are linting errors, but not in my doc.

@efriis Sorry with the last one, I got carried away a bit. Was just copying other providers.
This is reduced, and describes exclusively implementing LangChain feature when run through Kong AI gateway.

same comment - would recommend putting this in your docs though!

Hi @efriis , sorry for bugging you so much; please would you explain what we are doing differently to other providers, or other AI gateways e.g. PortKey?
All of our users that I have spoken to, are asking about using LangChain via Kong, so I think this doc makes sense as a supported integration.


Update edit toolbar to use checkIfFeatureEnabled

This is the last place where chrome.storage.sync.get is still being used directly to check if a feature is enabled.

This is implementing the last of this issue: https://github.com/wikitree/wikitree-browser-extension/issues/103

Actually I have found a problem with this change so closing this PR


How i can add function Drag to Grid?

Is there a way to drag items in the grid?

Duplicate of #21580


{ServiceConnector} Some user experience improvements

Description

Testing Guide

This PR adds the following features/improvements for service connector

Auto register target subscription if not yet registered
Mark object-id as optional when using service principal as auth type
Validate appconfig to avoid secret auth type when local auth is disabled

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

ServiceConnector


Mock response cannot contain numbers and content type is always text/plain

Configuration for the response cannot contain number values. Also the response content-type is always text/plain.

I already have fixed this issue, but I cannot create a branch.

I already have fixed this issue, but I cannot create a branch.


Add support for --extra-index-url param

I have a use-case where I have a python package hosted in a private pypi, but it has dependencies on projects that exist in the main pypi. I see support was added for the --index-url flag, but this doesn't let pip find dependencies from the main pypi.
When using pip, the following works:
pip install --extra-index-url https://pypi.mydomain.com mypackage

Ideally, the following would also work:
pipx install --extra-index-url https://pypi.mydomain.com mypackage

Thanks for the awesome tool!

This should currently be possible with
pipx install --pip-args "--extra-index-url https://pypi.mydomain.com mypackage" package

You're right @cs01, thank you!
Should have rtm, again thanks for the great tool!

np glad it solves your problem!


[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed

There is a chance that an SSL error occurs.
How to fix: get your certs right :)
It should look something like this:
IOError: [Errno socket error] [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)

So for me (I tried on a new computer), running the same command again just magically worked.


Adds test case of OllamaChatRequestBuilder

I felt there was a lack of test cases for OllamaChatRequestBuilder, so I added tests for a few methods.
If there are any mistakes, please comment🙇♂
PR. https://github.com/amithkoujalgi/ollama4j/pull/37

Thanks for the PR @anjeongkyun!


Merge<EMAIL_ADDRESS>into aws-cwa-dev

Description: Merge<EMAIL_ADDRESS>into aws-cwa-dev
Link to tracking Issue: N/A
Testing:
OTel Contrb Tests: https://github.com/amazon-contributing/opentelemetry-collector-contrib/actions/runs/10052666345
CWA Integ Tests: https://github.com/aws/amazon-cloudwatch-agent/actions/runs/10063006520

For https://github.com/amazon-contributing/opentelemetry-collector-contrib/pull/223/commits/3979143ed145525e987bbac33379efbd2a518725, prepending the socket with passthrough was required as explained in https://github.com/grpc/grpc-go/issues/1786 since NewClient uses a DNS resolver by default instead of passthrough.
Also, removed WIthBlock since its deprecated and is an anti-pattern as per https://github.com/grpc/grpc-go/blob/master/Documentation/anti-patterns.md.
cc: @straussb @aditya-purang


Accessibility?

Does this affect accessibility somehow?
Considering Section 508, EU accessibility directive and WCAG 2.1.

Let's consider something like this, you are reading the page aloud with a screen reader, resize the browser and then what happens?

From my point of view the question is unrelated to this library. This library gives you a nice wrapper to react on screen changes, but what you are doing with it is up to you.

@thevangelist Yeah I think it is out of scope for this library - how you handle page accessibility is ultimately up to you. I don't know how screen readers react to content changing on the page but if it is a concern that people using screen readers are resizing the page you should avoid conditionally rendering different content. If they resize the page and you are using react-responsive to change classnames or positioning of things it shouldn't mess up a screen reader since the DOM of the content isn't being updated.


[Bug] Problem with accents

^^^ root.locales[0].description :

On continue en face pour descendre sur El Draguillo. Un peu plus bas dans la descente, deux possibilitée:
? ^

On continue en face pour descendre sur El Draguillo. Un peu plus bas dans la descente, deux possibilitéśe:
? ^^
Save https://www.camptocamp.org/routes/1079822 : Accents manquants, Diverses fautes, y/[n] ?

I could not see any problem in the article giving the corrections.
Maybe it is related to the fact that the é was entered as _ '+e _ ?

It may be the colon (:) which interferes in some way (there has already been a colon question in the past).

With the Automatic corrections in the guidebook article, the correction
deux possibilitée >> deux possibilités

is active, in the Diverses fautes section.

Also check the Accents manquants section and the Diverses fautes section for "possibilités".

Really really weird. On the original document, it's not a "e accent aigu", but a "e" followed by the generic diacritic accent : https://fr.wikipedia.org/wiki/Table_des_caractères_Unicode/U0300 => character code U+0301.
If I print the expected word possibilités' , it should be : possibilit\u00e9e, and  \u00e9stands foré`.
But in the original document, it's deux possibilite\u0301e, and e\u0301 stands for e modified by \u0301.
And bad luck, the engine that process corrections does not understand at all the char \u0301, and think it's a word boundary. In consequence, here is the substitutions used, in this order :
possibilite  >> possibilité
deux possibilité  >> possibilités

I'll add a core substitution in the processor for replacement of this weird char...


Fixes/checkoutproblem

(fixed issue #154 )
Hello, there was an checkout problem at window if you try to checkout your project from scratch via git clone.
Cause: the file Array/LongStrWithoutRepeat.js has 3 trailing spaces!
$ git clone git@github.com:Huluvu424242/JavaScript.git
Cloning into 'JavaScript'...
Enter passphrase for key '/c/Users/huluv/.ssh/id_rsa':
remote: Enumerating objects: 747, done.
remote: Counting objects: 100% (208/208), done.
remote: Compressing objects: 100% (97/97), done.
remote: Total 747 (delta 145), reused 118 (delta 110), pack-reused 539
Receiving objects: 100% (747/747), 181.20 KiB | 871.00 KiB/s, done.
Resolving deltas: 100% (284/284), done.
error: invalid path 'Array/LongStrWithoutRepeat.js '
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

This PR fixed this problem. I have removed the trailing spaces via 2 commits.

Have you tried to clone your project at window os at now? there is no content checked out because an file in the Array folder has trailing spaces (error: invalid path).
In this PR i have removed the trailing spaces from the file name (is not simple) because git!
So there is no changes - that right but the file name has changed.
It is only an info - you can fix it or not. This was an try to help you.


Hi What is

It's a great repo, and I want to know if the model's performance have reached the original paper

Hi, thank you for your interest in this code.
Currently, the model cannot reach the performance reported in the original paper. Discussion
about model performance could be found in #12. And I still make attempt to reproduce the
original performance.

Thanks for you kindly reply I am training on a modified version based on  code , I will try to find the reason   of the performance gap


Add an --watch flag for testing

Watches all file changes and run's tests on any change.

Closing out this issue as Conche is deprecated for the Swift Package Manager (SPM). Instead you can use SPM (https://github.com/Conche/Conche/commit/78708a9556b00d602de4c3e518a7f201b55a519b).


perf(napi): pass comments to JS as JSON

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2725  👈
#2724
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite

I'm surprised. This doesn't make any difference.


Update color checks

Update the checks added in https://github.com/googlefonts/fontbakery/issues/3886 to match guidance in https://github.com/googlefonts/googlefonts.github.io/pull/82 once merged. Note in particular SVG is required only for static COLRv1.

"If the font is variable it must not have an SVG table"
Why? I vaguely recall someone explained this at a recent video call. Could you please describe the reasoning for this requirement?


EasyAnimation crash in my project.

Xcode 7.1, Swift 2.0
I installed EasyAnimation via cocoapods.
When I launched my app, it stopped at:
private static func replaceAnimationMethods() {
    //replace actionForKey
    method_exchangeImplementations(
        class_getInstanceMethod(self, "actionForKey:"),
        class_getInstanceMethod(self, "EA_actionForKey:"))
}

thread #2: tid = 0x278da, 0x00000001008e6c90 libswiftCore.dylib`swift_unknownRelease + 24, stop reason = EXC_BAD_ACCESS (code=1, address=0x20)

the only known crashing issue right now is when you have an opengl view in your app. other than that I can't tell what the problem can be without more details

I used SpriteKit in my project.

Than this must be the issue - using OpenGL view currently is a crashing problem. Let me know if you do find a workaround

Good news latest PR solves this :+1:


Possible optimization in AsyncClientManager with message comparison

Description:
Currently we have a few filters, Rate Limit, Ext_proc, Ext_authz that rely on the async client manager. When these filters are created on a request, the filter will send the GrpcService proto to the AsyncClientManager to get a cached client from an internal map. Previously, this was hashing the entire proto on every single request when trying to find the client. This was fixed in a previous PR 29199.
So for us, one of our projects was showing Ext_authz using about ~4.2% of our cpu. After the PR, this dropped the usage down to about 2% which is significant improvement. But we still see a bulk of the filter creation time in the CPU is being taken up by comparing the message itself within the find.
I wanted to throw this out to the open source community to see if we can come up with a good idea of how we can possibly save some of this time since I'm sure many folks can be invested in the optimization of these filters.
Context:
The previously mentioned PR that had the first fix stored the config within a wrapper object found here. GrpcServiceConfigWithHashKey This object will pre compute the hash on creation so that we don't need to hash the config on each request. But while it skips the hash, it still uses the original config for the comparison.
Possible Solution:
A possible idea I had for this would be to maybe have some sort of singleton class that has some sort of config -> unique identifier map which the GrpcServiceConfigWithHashKey object will call on creation to get a smaller unique ID associated to that config. And we use that unique identifier internally instead of the actual config itself. Maybe using the ObjectSharedPool  for this? What do people think? A concern I have for this idea would be how to prune unique IDs that are not being used to avoid creating an ever growing list of IDs.

It sounds like you're looking for perfect hashing with no collisions. Maybe using cryptographic hash is a simpler solution here?
CC @tyxia


max rank in sparse.linalg.eigsh

It's currently not possible to compute the full eigendecomposition with eigsh.
>>> A = rand(5, 4)
>>> AA = np.dot(A.T, A)
>>> from scipy.sparse.linalg import eigsh
>>> eigsh(AA, AA.shape[0])
[...]
ValueError: k must be between 1 and the order of the square input matrix.

https://github.com/scipy/scipy/blob/master/scipy/sparse/linalg/eigen/arpack/arpack.py#L1506
I think k >= n should be replaced by k > n.

Or instead of raising an exception, one could do k = min(k, n).

ARPACK requires k < n.

In principle, it would be possible to switch to LAPACK dense solver for
the cases ARPACK doesn't handle. For abstract linear operators, this
would require first computing n matrix products to get a dense
representation, so there's some hassle in implementing it. The result
however may still be faster than ARPACK.

Calculating full (or nearly full) eigendecompositions negates much of the point of using a linear operators. If you use ARPACK for k=n-1, for example, it will do calculations on nxn matrices anyway --- and because it is optimized for the sparse case, it will not perform well when compared to LAPACK.

Fixed by https://github.com/scipy/scipy/pull/7004
Which references a near duplicate issue: https://github.com/scipy/scipy/issues/6430


Firebird - Unique Keys is not shown if it is not PK

In TableView on tab 'Unique Keys' only  Primary Key is shown, though DDL clearly show existance of anothet two Unique Keys aside PK.

There are no two other unique keys but there are two other unique indexes.
Check Indexes tab.

Ah, my bad. I believed I've created keys. Thanks.


added hybrid commands

I have added hybrid commands from discord.py and error handling.
Fix #11

@lonewolf9277 Good work! But can you make a few changes?
Format and clean up the file:

Remove extra spaces and empty lines that are not necessary.
Remove unnecessary comments
Remove the print statements as they are not necessary after development.

Overall, can you make the code cleaner?

@lonewolf9277 There are merge conflicts, please rectify :)


Instructions are broken

PS C:\Users\lukesch> Uninstall-AllModules -TargetModule Az -Version 2.1.0 -Force
Creating list of dependencies...
WARNING: Could not find uninstall candidate for Az.Accounts:2.1.0 - module may require manual uninstall. Available
versions are: 1.5.2
WARNING: Could not find uninstall candidate for Az.Aks:2.1.0 - module may require manual uninstall. Available versions
are: 1.0.1
WARNING: Could not find uninstall candidate for Az.AnalysisServices:2.1.0 - module may require manual uninstall.
Available versions are: 1.1.0
WARNING: Could not find uninstall candidate for Az.ApiManagement:2.1.0 - module may require manual uninstall. Available
versions are: 1.1.0
WARNING: Could not find uninstall candidate for Az.ApplicationInsights:2.1.0 - module may require manual uninstall.
Available versions are: 1.0.0
WARNING: Could not find uninstall candidate for Az.Automation:2.1.0 - module may require manual uninstall. Available
versions are: 1.2.2
WARNING: Could not find uninstall candidate for Az.Batch:2.1.0 - module may require manual uninstall. Available
versions are: 1.1.0
WARNING: Could not find uninstall candidate for Az.Billing:2.1.0 - module may require manual uninstall. Available
versions are: 1.0.0
WARNING: Could not find uninstall candidate for Az.Cdn:2.1.0 - module may require manual uninstall. Available versions
are: 1.2.0
WARNING: Could not find uninstall candidate for Az.CognitiveServices:2.1.0 - module may require manual uninstall.
Available versions are: 1.1.1
WARNING: Could not find uninstall candidate for Az.ContainerInstance:2.1.0 - module may require manual uninstall.
Available versions are: 1.0.1
WARNING: Could not find uninstall candidate for Az.ContainerRegistry:2.1.0 - module may require manual uninstall.
Available versions are: 1.0.1
WARNING: Could not find uninstall candidate for Az.DataFactory:2.1.0 - module may require manual uninstall. Available
versions are: 1.1.1
WARNING: Could not find uninstall candidate for Az.DataLakeAnalytics:2.1.0 - module may require manual uninstall.
Available versions are: 1.0.0
WARNING: Could not find uninstall candidate for Az.DataLakeStore:2.1.0 - module may require manual uninstall. Available
versions are: 1.2.1
WARNING: Could not find uninstall candidate for Az.DeploymentManager:2.1.0 - module may require manual uninstall.
Available versions are: 1.0.0
WARNING: Could not find uninstall candidate for Az.DevTestLabs:2.1.0 - module may require manual uninstall. Available
versions are: 1.0.0
WARNING: Could not find uninstall candidate for Az.Dns:2.1.0 - module may require manual uninstall. Available versions
are: 1.1.0
WARNING: Could not find uninstall candidate for Az.EventGrid:2.1.0 - module may require manual uninstall. Available
versions are: 1.1.1
WARNING: Could not find uninstall candidate for Az.EventHub:2.1.0 - module may require manual uninstall. Available
versions are: 1.1.0
WARNING: Could not find uninstall candidate for Az.FrontDoor:2.1.0 - module may require manual uninstall. Available
versions are: 1.0.0
WARNING: Could not find uninstall candidate for Az.HDInsight:2.1.0 - module may require manual uninstall. Available
versions are: 2.0.0
WARNING: Could not find uninstall candidate for Az.IotHub:2.1.0 - module may require manual uninstall. Available
versions are: 1.1.0
WARNING: Could not find uninstall candidate for Az.KeyVault:2.1.0 - module may require manual uninstall. Available
versions are: 1.2.0
WARNING: Could not find uninstall candidate for Az.LogicApp:2.1.0 - module may require manual uninstall. Available
versions are: 1.2.1
This works:
workflow Uninstall-AzureModules
{
$Modules = (Get-Module -ListAvailable Azure*).Name |Get-Unique
Foreach -parallel ($Module in $Modules)
{
Write-Output ("Uninstalling: $Module")
Uninstall-Module $Module -Force
}
}
Uninstall-AzureModules
Uninstall-AzureModules   #second invocation to truly remove everything

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

ID: 37445ffd-7887-959f-b203-1090ccb3fe51
Version Independent ID: b3ce94fa-6e76-4ffe-e70e-07f7a321fcd4
Content: Uninstall Azure PowerShell
Content Source: docs-conceptual/azps-2.3.2/uninstall-az-ps.md
GitHub Login: @sptramer
Microsoft Alias: sttramer

The line above should read
$Modules = (Get-Module -ListAvailable Az.*).Name |Get-Unique

You're correct that the current script may not work as expected. This is because uninstalling modules which use a MinimumVersion requirement rather than RequiredVersion can cause dependency problems when being removed, if only uninstalling a single version. Right now the removal script can only provide guidance on how to handle minimum version removal.

Any thought on updating the docs to use some form of the script I provided?
On Tue, Jul 2, 2019, 14:20 Stephen Tramer<EMAIL_ADDRESS>wrote:

You're correct that the current script may not work as expected. This is
because uninstalling modules which use a MinimumVersion requirement
rather than RequiredVersion can cause dependency problems when being
removed, if only uninstalling a single version. Right now the removal
script can only provide guidance on how to handle minimum version removal.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs-powershell/issues/1133?email_source=notifications&email_token=ACHQHCLBHHNTK5KZSBMK76DP5PBCDA5CNFSM4H3NIOUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZCSSCI#issuecomment-507848969,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACHQHCJ7KDXXGZV2D6AYMMDP5PBCDANCNFSM4H3NIOUA
.

Same issue encountered.
PS H:\onebranch\Storage\XSync\Dev\src\Kailani> $versions | foreach { Uninstall-AllModules -TargetModule AzureRM -Version ($_.Version) -Force }
Creating list of dependencies...
WARNING: Could not find uninstall candidate for AzureRM.Profile:6.13.1 - module may require manual uninstall. Available versions are: 5.8.2, 5.8.3
WARNING: Could not find uninstall candidate for Azure.Storage:6.13.1 - module may require manual uninstall. Available versions are: 4.6.1
WARNING: Could not find uninstall candidate for AzureRM.AnalysisServices:6.13.1 - module may require manual uninstall. Available versions are: 0.6.14
WARNING: Could not find uninstall candidate for Azure.AnalysisServices:6.13.1 - module may require manual uninstall. Available versions are: 0.5.4
WARNING: Could not find uninstall candidate for AzureRM.ApiManagement:6.13.1 - module may require manual uninstall. Available versions are: 6.1.7
WARNING: Could not find uninstall candidate for AzureRM.ApplicationInsights:6.13.1 - module may require manual uninstall. Available versions are: 0.1.8
WARNING: Could not find uninstall candidate for AzureRM.Automation:6.13.1 - module may require manual uninstall. Available versions are: 6.1.1
WARNING: Could not find uninstall candidate for AzureRM.Backup:6.13.1 - module may require manual uninstall. Available versions are: 4.0.11
WARNING: Could not find uninstall candidate for AzureRM.Batch:6.13.1 - module may require manual uninstall. Available versions are: 4.1.5
WARNING: Could not find uninstall candidate for AzureRM.Billing:6.13.1 - module may require manual uninstall. Available versions are: 0.14.6
WARNING: Could not find uninstall candidate for AzureRM.Cdn:6.13.1 - module may require manual uninstall. Available versions are: 5.0.6
WARNING: Could not find uninstall candidate for AzureRM.CognitiveServices:6.13.1 - module may require manual uninstall. Available versions are: 0.9.12
WARNING: Could not find uninstall candidate for AzureRM.Compute:6.13.1 - module may require manual uninstall. Available versions are: 5.9.1
WARNING: Could not find uninstall candidate for AzureRM.Consumption:6.13.1 - module may require manual uninstall. Available versions are: 0.3.7
WARNING: Could not find uninstall candidate for AzureRM.ContainerInstance:6.13.1 - module may require manual uninstall. Available versions are: 0.2.12
WARNING: Could not find uninstall candidate for AzureRM.ContainerRegistry:6.13.1 - module may require manual uninstall. Available versions are: 1.0.10
WARNING: Could not find uninstall candidate for AzureRM.DataFactories:6.13.1 - module may require manual uninstall. Available versions are: 5.0.3
WARNING: Could not find uninstall candidate for AzureRM.DataFactoryV2:6.13.1 - module may require manual uninstall. Available versions are: 0.5.11
WARNING: Could not find uninstall candidate for AzureRM.DataLakeAnalytics:6.13.1 - module may require manual uninstall. Available versions are: 5.1.4
WARNING: Could not find uninstall candidate for AzureRM.DataLakeStore:6.13.1 - module may require manual uninstall. Available versions are: 6.2.1
WARNING: Could not find uninstall candidate for AzureRM.DevTestLabs:6.13.1 - module may require manual uninstall. Available versions are: 4.0.9
WARNING: Could not find uninstall candidate for AzureRM.Dns:6.13.1 - module may require manual uninstall. Available versions are: 5.1.0
WARNING: Could not find uninstall candidate for AzureRM.EventGrid:6.13.1 - module may require manual uninstall. Available versions are: 0.3.7
WARNING: Could not find uninstall candidate for AzureRM.EventHub:6.13.1 - module may require manual uninstall. Available versions are: 0.7.0
WARNING: Could not find uninstall candidate for AzureRM.HDInsight:6.13.1 - module may require manual uninstall. Available versions are: 4.1.8
WARNING: Could not find uninstall candidate for AzureRM.Insights:6.13.1 - module may require manual uninstall. Available versions are: 5.1.5
WARNING: Could not find uninstall candidate for AzureRM.IotHub:6.13.1 - module may require manual uninstall. Available versions are: 3.1.8
WARNING: Could not find uninstall candidate for AzureRM.KeyVault:6.13.1 - module may require manual uninstall. Available versions are: 5.2.1
WARNING: Could not find uninstall candidate for AzureRM.LogicApp:6.13.1 - module may require manual uninstall. Available versions are: 4.1.4
WARNING: Could not find uninstall candidate for AzureRM.MachineLearning:6.13.1 - module may require manual uninstall. Available versions are: 0.18.5
WARNING: Could not find uninstall candidate for AzureRM.MachineLearningCompute:6.13.1 - module may require manual uninstall. Available versions are: 0.4.8
WARNING: Could not find uninstall candidate for AzureRM.MarketplaceOrdering:6.13.1 - module may require manual uninstall. Available versions are: 0.2.7
WARNING: Could not find uninstall candidate for AzureRM.Media:6.13.1 - module may require manual uninstall. Available versions are: 0.10.4
WARNING: Could not find uninstall candidate for AzureRM.Network:6.13.1 - module may require manual uninstall. Available versions are: 6.11.1
WARNING: Could not find uninstall candidate for AzureRM.NotificationHubs:6.13.1 - module may require manual uninstall. Available versions are: 5.0.3
WARNING: Could not find uninstall candidate for AzureRM.OperationalInsights:6.13.1 - module may require manual uninstall. Available versions are: 5.0.6
WARNING: Could not find uninstall candidate for AzureRM.PolicyInsights:6.13.1 - module may require manual uninstall. Available versions are: 1.1.0
WARNING: Could not find uninstall candidate for AzureRM.PowerBIEmbedded:6.13.1 - module may require manual uninstall. Available versions are: 4.1.10
WARNING: Could not find uninstall candidate for AzureRM.RecoveryServices:6.13.1 - module may require manual uninstall. Available versions are: 4.1.9
WARNING: Could not find uninstall candidate for AzureRM.RecoveryServices.Backup:6.13.1 - module may require manual uninstall. Available versions are: 4.5.2
WARNING: Could not find uninstall candidate for AzureRM.RecoveryServices.SiteRecovery:6.13.1 - module may require manual uninstall. Available versions are: 0.2.12
WARNING: Could not find uninstall candidate for AzureRM.RedisCache:6.13.1 - module may require manual uninstall. Available versions are: 5.1.0
WARNING: Could not find uninstall candidate for AzureRM.Relay:6.13.1 - module may require manual uninstall. Available versions are: 0.3.12
WARNING: Could not find uninstall candidate for AzureRM.Resources:6.13.1 - module may require manual uninstall. Available versions are: 6.7.3
WARNING: Could not find uninstall candidate for AzureRM.Scheduler:6.13.1 - module may require manual uninstall. Available versions are: 0.16.10
WARNING: Could not find uninstall candidate for AzureRM.ServiceBus:6.13.1 - module may require manual uninstall. Available versions are: 0.6.13

Didn't expect Microsoft to write a script that will be easily broken... lol

Was facing the same issue. The below script worked for me
$versions | foreach { Uninstall-AllModules -TargetModule AzureRM -Version ($_.Version) -Force }
Get-Module -ListAvailable | Where-Object { $_.Name -like 'AzureRM*' } | Uninstall-Module```

This is utterly useless... but just unleashing your rage on C:\Program Files\WindowsPowerShell\Modules will work.

Absolutely --- Microsoft is terrible -- You should not be allowed to be 1trillion software company when you don't understand how to properly remove your own software --- further -- you shouldn't be a 1trillion dollar software company if you do not know how to upgrade your own software. You can afford to hire people that understand how things work.
PS C:\WINDOWS\system32> $versions = Get-InstalledModule AzureRM.* | Select-Object -Property Name,Version PS C:\WINDOWS\system32> $versions | foreach { Uninstall-AllModules -TargetModule $_.Name -Version ($_.Version) -Force }

Ok let me follow up with what works
Merry Christmas!
Remove-Module AzureRM.Profile -Force
$versions = Get-InstalledModule Azure* | Select-Object -Property Name,Version
$versions | foreach { Uninstall-AllModules -TargetModule $_.Name -Version ($_.Version) -Force }

is the doc updated?

Hi all -
I've been tracking this issue for a while now, thinking about how to best handle it. The real problem with the script is that we want to keep things flexible for users to allow uninstalling whatever version they want, while preserving dependency relations. That's why the script hasn't just changed to be a highly-efficient nuke of the entire Az.* module set (although that works fine, and is what I'd personally recommend for right now, and what @cutty201 has helpfully provided.) PowerShell doesn't have good tools in place for resolving dependency hell, which is what makes uninstall hard to do with a generic script.
I'm targeting the uninstall instructions to be updated sometime this month to be much simpler and more comprehensive, although they may be stored in an external script. We're also re-introducing MSI installs on the documentation page, which is a more efficient way to manage your installations if you need to frequently remove older versions. You can actually get the MSIs right now, from the GitHub Releases page.

And the documentation still persists with old non working script.. 🤦♂

My penny...
$versions = Get-InstalledModule Az.* | Select-Object -Property Name,Version
$countmods = Get-InstalledModule Az.* | Measure-Object

Write-Host "Modules found: " $versions

while($countmods.Count -gt 0)
{
    $versions | foreach {
        Uninstall-Module -Name $_.Name -MinimumVersion $_.Version  -Force
        Write-Host "Removed: " $_.Name $_.Version
    }
}

Otherwise, you have to iterate manually to make it work.
Cheers!

My penny...
Warning: no error handling...
$versions = Get-InstalledModule Az.* | Select-Object -Property Name,Version
$countmods = Get-InstalledModule Az.* | Measure-Object

Write-Host "Modules found: " $versions

while($countmods.Count -gt 0)
{
    $versions | foreach {
        Uninstall-Module -Name $_.Name -MinimumVersion $_.Version  -Force
        Write-Host "Removed: " $_.Name $_.Version
    }

    $versions = Get-InstalledModule Az.* | Select-Object -Property Name,Version
    $countmods = Get-InstalledModule Az.* | Measure-Object
}

Cheers!


in tailwindcss example, purge in tailwind.config.js should be filled

since it is example of how using tailwindcss, I think it is better to include
purge: ['./imports/ui/**/*.{js,jsx,ts,tsx}', './public/*.html']
instead of
purge: []
imho, just to be as real-world as possible.

thank you, the PR is merged now with this update.


Fixes #456

Fixes #456

@Voltfest
@kruegeralex
Please check: https://deploy-preview-487--umh-docs.netlify.app/docs/publications/blue-ocean-iiot-platform-strategy/


v0.12.3?

nvm lists v0.12.3 available for install, but it fails:
$ nvm install v0.12.3
######################################################################## 100.0%
Checksums empty
tar: Unrecognized archive format
tar: Error exit delayed from previous errors.
Binary download failed, trying source.

It also doesn't exist (yet) unless I'm missing something? It's causing issues on my end where apps haven't defined a version and rely on the latest stable.

v0.12.3 isn't actually released yet - it's a release candidate, that's breaking nvm. I'll look into it.

Should be fixed now https://twitter.com/misterdjules/status/583788249820205059


Wrong prices for stock

Windows 10, Python 3.10.10, just run pip3 install yfinance --upgrade --no-cache-dir to make sure I'm on latest.
This is the code I'm running:
print(yf.__version__)
 ticker = 'IMPP'
 yf_ticker = yf.Ticker(ticker)
yf_historic_prices = yf_ticker.history(start="2020-12-01", end="2023-4-28")
print(yf_historic_prices)
exit()

And this is the output I'm getting:
0.2.18
                                Open        High        Low       Close   Volume  Dividends  Stock Splits
Date
2021-12-06 00:00:00-05:00   5.999999  124.500000   5.999999  112.500000    15995        0.0           0.0
2021-12-07 00:00:00-05:00  91.500000  107.699997  63.301498   71.099998    20834        0.0           0.0
2021-12-08 00:00:00-05:00  67.500000   68.699997  46.950001   48.299999    19591        0.0           0.0
2021-12-09 00:00:00-05:00  48.149998   48.430500  39.014999   40.649998    11041        0.0           0.0
2021-12-10 00:00:00-05:00  41.250000   44.700001  37.500000   40.200001     7193        0.0           0.0
...                              ...         ...        ...         ...      ...        ...           ...
2023-04-21 00:00:00-04:00   2.930999    2.998499   2.872499    2.990999   169956        0.0           0.0
2023-04-24 00:00:00-04:00   3.083999    3.083999   2.882999    2.992499   152540        0.0           0.0
2023-04-25 00:00:00-04:00   2.917499    2.999999   2.879999    2.984999   259383        0.0           0.0
2023-04-26 00:00:00-04:00   2.549999    2.786999   2.324999    2.515499  1153415        0.0           0.0
2023-04-27 00:00:00-04:00   2.437499    2.665499   2.437499    2.521499   361455        0.0           0.0

[350 rows x 7 columns]

The prices are completely different from the ones that comes from Yahoo.
https://finance.yahoo.com/quote/IMPP/
It doesn't seem to me that Yahoo is returning bad data, as I've tried a bunch of other stocks right after/before this and they all seem to return the correct data. Also I've tried running this like 30 times now, always the same result.
Though from the previous executions of my program it seems like I was able to download the prices correctly yesterday. So maybe this is actually Yahoo trying to fool me, as sick as this approach would be.

I am sorry. Just noticed that IMPP is actually splitting 1:15 tomorrow.
This is just a bug in my program. :)
Thanks for this awesome library, BTW!


Support PHP7+ Errors

Implement a new error handler, PhpError which handles PHP 7's new Throwable interface.
This fixes #1762.
Note that I couldn't just use the current Error handler as I'd have had to have changed the method signatures which would have broken BC. I've chosen to catch Throwable in this new handler so that when we go to 4.0, we can simply remove the current Error handler and this one can then be used to catch both Exceptions and PHP 7+ Errors.

Explicit ping for @codeguy & @silentworks :) Thoughts appreciated from everyone else!

I like it. But we as we build new features into Slim you can really start to see some of the short-comings.

Hard-coded content-types
No Handler Interfaces

These 2 issues force a user to extend the current class and override the methods instead of simply implementing an interface. I don't think its a big deal breaker, but these sorts of issues should be cataloged somewhere for 4.0


Rancher UI not loading with pods Readiness probe failed

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Researched troubleshooting page over the past few days but no conclusion
Result:
Nothing useful
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): latest, 2.4.5
Installation option (single install/HA): HA

Cluster information
- Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Local VMs
- Machine type (cloud/VM/metal) and specifications (CPU/memory): VM (4<EMAIL_ADDRESS>RAM)
- Kubernetes version (use `kubectl version`):
Client Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+1e3cff4", GitCommit:"1e3cff4", GitTreeState:"clean", BuildDate:"2019-07-18T00:11:14Z", GoVersion:"go1.11.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-15T16:51:04Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
- rke version:
INFO[0000] Running RKE version: v1.1.4
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-15T16:51:04Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client: Docker Engine - Community
 Version:           19.03.12
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        48a66213fe
 Built:             Mon Jun 22 15:46:54 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.12
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       48a66213fe
  Built:            Mon Jun 22 15:45:28 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Additional information:
Upon finding https://github.com/rancher/rancher/issues/26385, I ran through these troubleshooting steps:

All tests return good except:
for pod in $(kubectl -n ingress-nginx get pods -l app=ingress-nginx -o custom-columns=NAME:.metadata.name --no-headers); do echo $pod; kubectl -n ingress-nginx exec $pod -- curl -s --unix-socket /tmp/nginx-status-server.sock http://localhost/configuration/backends; echo;  done

nginx-ingress-controller-5sdls
command terminated with exit code 7

nginx-ingress-controller-6ct4d
command terminated with exit code 7

nginx-ingress-controller-b7pmd
command terminated with exit code 7

AND
for rancherpod in $(kubectl -n cattle-system get ep rancher -o go-template='{{range .subsets}}{{range .addresses}}{{ .ip}}{{"\n"}}{{end}}{{end}}'); do for pod in $(kubectl -n ingress-nginx get pods -l app=ingress-nginx -o custom-columns=NAME:.metadata.name --no-headers); do echo "$pod to Rancher pod $rancherpod"; kubectl -n ingress-nginx exec $pod -- curl -sLk https://$rancherpod/ping; echo;  done; done
nginx-ingress-controller-5sdls to Rancher pod <IP_ADDRESS>
pong
nginx-ingress-controller-6ct4d to Rancher pod <IP_ADDRESS>
pong
nginx-ingress-controller-b7pmd to Rancher pod <IP_ADDRESS>
pong
nginx-ingress-controller-5sdls to Rancher pod <IP_ADDRESS>
pong
nginx-ingress-controller-6ct4d to Rancher pod <IP_ADDRESS>
pong
nginx-ingress-controller-b7pmd to Rancher pod <IP_ADDRESS>
pong
nginx-ingress-controller-5sdls to Rancher pod <IP_ADDRESS>
pong
nginx-ingress-controller-6ct4d to Rancher pod <IP_ADDRESS>
pong
nginx-ingress-controller-b7pmd to Rancher pod <IP_ADDRESS>

I have an external L4 Nginx LB:
user nginx;
worker_processes 4;
worker_rlimit_nofile 40000;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;

# Load dynamic modules. See /usr/share/doc/nginx/README.dynamic.
include /usr/share/nginx/modules/*.conf;

events {
    worker_connections 8192;
}

stream {
    upstream rancher_servers_http {
        least_conn;
        server <IP_ADDRESS>:80 max_fails=3 fail_timeout=5s;
        server <IP_ADDRESS>:80 max_fails=3 fail_timeout=5s;
        server <IP_ADDRESS>:80 max_fails=3 fail_timeout=5s;

    }
    server {
        listen 80;
        proxy_pass rancher_servers_http;
    }

    upstream rancher_servers_https {
        least_conn;
        server <IP_ADDRESS>:80 max_fails=3 fail_timeout=5s;
        server <IP_ADDRESS>:80 max_fails=3 fail_timeout=5s;
        server <IP_ADDRESS>:80 max_fails=3 fail_timeout=5s;
    }
    server {
        listen 443;
        proxy_pass rancher_servers_https;
    }
}

kubectl get nodes -o wide
NAME   STATUS   ROLES                      AGE   VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION                CONTAINER-RUNTIME
kcg0   Ready    controlplane,etcd,worker   48m   v1.18.6   <IP_ADDRESS>   <none>        CentOS Linux 7 (Core)   3.10.0-1127.18.2.el7.x86_64   docker://19.3.12
kcg1   Ready    controlplane,etcd,worker   48m   v1.18.6   <IP_ADDRESS>   <none>        CentOS Linux 7 (Core)   3.10.0-1127.18.2.el7.x86_64   docker://19.3.12
kcg2   Ready    controlplane,etcd,worker   48m   v1.18.6   <IP_ADDRESS>   <none>        CentOS Linux 7 (Core)   3.10.0-1127.18.2.el7.x86_64   docker://19.3.12

There is a DNS name pointed to rancher.hostname.com pointed at this LB.  If I move that LB to a worker node directly, the UI loads just fine.  It seems like the ingress controller is ignoring something about my config.
W0803 15:18:48.639148       6 controller.go:393] Service "ingress-nginx/default-http-backend" does not have any active Endpoint
W0803 15:24:52.355272       6 backend_ssl.go:46] Error obtaining X.509 certificate: no object matching key "cattle-system/tls-rancher-ingress" in local store
I0803 15:24:52.355765       6 event.go:278] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"cattle-system", Name:"rancher", UID:"ad77ed4a-9be1-43a4-a1f2-fe4185ed038c", APIVersion:"networking.k8s.io/v1beta1", ResourceVersion:"2236", FieldPath:""}): type: 'Normal' reason: 'CREATE' Ingress cattle-system/rancher
W0803 15:24:55.678645       6 controller.go:909] Service "cattle-system/rancher" does not have any active Endpoint.
W0803 15:24:55.678759       6 controller.go:1119] Error getting SSL certificate "cattle-system/tls-rancher-ingress": local SSL certificate cattle-system/tls-rancher-ingress was not found. Using default certificate
I0803 15:24:55.678864       6 controller.go:139] Configuration changes detected, backend reload required.
I0803 15:24:55.780665       6 controller.go:155] Backend successfully reloaded.
W0803 15:24:59.011949       6 controller.go:909] Service "cattle-system/rancher" does not have any active Endpoint.
W0803 15:24:59.012030       6 controller.go:1119] Error getting SSL certificate "cattle-system/tls-rancher-ingress": local SSL certificate cattle-system/tls-rancher-ingress was not found. Using default certificate
I0803 15:25:17.580226       6 store.go:421] secret cattle-system/tls-rancher-ingress was added and it is used in ingress annotations. Parsing...
I0803 15:25:17.581584       6 backend_ssl.go:66] Adding Secret "cattle-system/tls-rancher-ingress" to the local store
W0803 15:25:17.581749       6 controller.go:909] Service "cattle-system/rancher" does not have any active Endpoint.
I0803 15:25:44.886038       6 status.go:275] updating Ingress cattle-system/rancher status from [] to [{<IP_ADDRESS> } {<IP_ADDRESS> } {<IP_ADDRESS> }]
I0803 15:25:44.899251       6 event.go:278] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"cattle-system", Name:"rancher", UID:"ad77ed4a-9be1-43a4-a1f2-fe4185ed038c", APIVersion:"networking.k8s.io/v1beta1", ResourceVersion:"4381", FieldPath:""}): type: 'Normal' reason: 'UPDATE' Ingress cattle-system/rancher
I0803 15:25:44.908655       6 event.go:278] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"cattle-system", Name:"rancher", UID:"ad77ed4a-9be1-43a4-a1f2-fe4185ed038c", APIVersion:"networking.k8s.io/v1beta1", ResourceVersion:"4385", FieldPath:""}): type: 'Normal' reason: 'UPDATE' Ingress cattle-system/rancher

Anything else I can try?

Steps to resolve:
Point DNS directly at a node in the cluster.
Login to the URL, set password, verify server link.
Allow time for cluster to go "Active" (a few seconds to a minute...if not, then edit the cluster and then SAVE)
Logout
Point DNS back to L4 Nginx LB
Login to the URL
I pointed my DNS back at the L4 Nginx LB and now traffic is passing.  This seems to be directly related to the issue: https://github.com/rancher/rancher/issues/16213
I'm going to close the ticket for now...but I can be available to try out different configs/troubleshooting steps if need be.


edit logic for multiple envs on same cognito pool

Description:
Issue Reference URL
https://github.com/awslabs/aws-eks-data-maker/issues/

Do not change content below. Mark applicable check boxes only.
Thank you for submitting a contribution to AWS Orbit Workbench.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a ISSUE associated with this PR?
[ ] Does your PR title start with ISSUE-XXXX where XXXX is the issue number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[ ] Has your PR been rebased against the latest commit within the target branch (typically 'main')?
[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under Apache License 2.0?

I cannot replicate the mypy validation error on my local to correct this.  I ran mypy and validate.sh from cli and from image/jupyter-user with python 3.7.10 and a fresh virtual env with dependencies.


Exclude unhealthy instances while programming the DNS.

Fix is provided in https://github.com/rancher/cattle/pull/1053

Tested with server version - V0.46-0-rc2
Tested the following scenario:
Setup - 3 hosts
Have service with scale 2 which has exposed port so they get deployed in different hosts.
Pick the host that does not have any instance of the service running and make it "Inactive" , so it cannot be picked for any new instance deployment.
DNS resolution for service name returns ip address of 2 instances of the service.
Bring down one of the host where service instances are running. This results in instance being marked "unhealthy" but still in "running" state since new instance for the service cannot be deployed due to not having hosts to satisfy the port requirement.
DNS resolution for service name returns only 1 ip address which is of the healthy instance. It does not include the ip address of the unhealthy instance.
Make the host that was inactive, active now.
This will result in new instances being created for the unhealthy service and DNS resolution for service name returns ip address of 2 instances both of which are healthy.


segmentation fault when allocating

(posting this here instead of only IRC)
I was trying some wasm code with allocations and got a segmentation fault while running it.
To reproduce:

use wasmtime from #21 (commits  4a28542 or 6854dec should be fine)
compile this rust file to wasm32-unknown-unknown:

#![feature(link_args)]
#![link_args = "--import-memory --initial-memory=1114112 --max-memory=65536000"]

#[no_mangle]
pub extern "C" fn hello(ctx: *const *mut u8) {
  let v = "hello".to_string();
}

(note: I tried using std::alloc directly, but could not reproduce)
I get the following output with lldb:
$ lldb ./target/debug/wasmtime
(lldb) target create "./target/debug/wasmtime"
Traceback (most recent call last):
  File "<input>", line 1, in <module>
  File<EMAIL_ADDRESS>line 52, in <module>
    import weakref
  File<EMAIL_ADDRESS>line 14, in <module>
    from _weakref import (
ImportError: cannot import name _remove_dead_weakref
Current executable set to './target/debug/wasmtime' (x86_64).
(lldb) r ./testalloc.wasm --function=hello
Process 55272 launched: './target/debug/wasmtime' (x86_64)
Process 55272 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x2029ffff0)
    frame #0: 0x000000010179ecb9
->  0x10179ecb9: movl   %eax, (%rdx,%rcx)
    0x10179ecbd: movl   $0x5, %eax
    0x10179ecc3: movl   0x14(%rsp), %ecx
    0x10179eccb: movl   %ecx, %ecx
Target 0: (wasmtime) stopped.
(lldb) register read
General Purpose Registers:
       rax = 0x0000000000110008
       rbx = 0x0000000102821000
       rcx = 0x00000000fffffff0
       rdx = 0x0000000102a00000
       rdi = 0x0000000102a00000
       rsi = 0x0000000102a00000
       rbp = 0x00007ffeefbfd660
       rsp = 0x00007ffeefbfd640
        r8 = 0x000000000000006f
        r9 = 0x0000000000000005
       r10 = 0x000000010160d008
       r11 = 0x00007ffdee465e60
       r12 = 0x0000000000000000
       r13 = 0x0000000000000000
       r14 = 0x00007ffeefbfed00
       r15 = 0x00007ffeefbfecc0
       rip = 0x000000010179ecb9
    rflags = 0x0000000000010206
        cs = 0x000000000000002b
        fs = 0x0000000000000000
        gs = 0x0000000000000000

This happens right after grow_memory is called. It adds a page and returns 17 (17 pages specified by the --initial-memory link arg).
From the debugger output, I see in the movl   %eax, (%rdx,%rcx) instructions that rdx = 0x0000000102a00000, which is the base address for the LinearMemory, to which rcx = 0x00000000fffffff0 is added.
What I suspect here is that it's not trying to write rax = 0x0000000000110008 (which is 1114120 ie the initial memory size + 8) at the address 0x2029ffff0, but at the LinearMemory's base address minus 16 bytes, using an addition with overflow. Wasm32 assumes 32bit addresses and offsets, but here we're compiling to x86_64, so it won't ovrflow.

Thanks for debugging this to this point! I'll take a closer look next week.

BTW, I was able to reproduce with a much smaller example:
#![feature(link_args)]
#![allow(unused_attributes)] // link_args actually is used
#![link_args = "--import-memory --initial-memory=1114112 --max-memory=65536000"]

fn address(v: *mut u8) {
  unsafe {
    let v2 = (v as usize - 16) as *mut u8;
    *v2 = 0x32;
  };
}
#[no_mangle]
pub extern "C" fn load() {
  unsafe {
    let v: *mut u8 = 2_147_483_647 as *mut u8;

    address(v);
  }
}

(module
  (type $t0 (func))
  (type $t1 (func (param i32)))
  (import "env" "memory" (memory $env.memory 17 1000))
  (func $testload::address::hfcb094981e27477e (type $t1) (param $p0 i32)
    (local $l0 i32) (local $l1 i32) (local $l2 i32)
    (set_local $l0
      (i32.const 50))
    (set_local $l1
      (i32.const 16))
    (set_local $l2
      (i32.sub
        (get_local $p0)
        (get_local $l1)))
    (i32.store8
      (get_local $l2)
      (get_local $l0))
    (return))
  (func $load (export "load") (type $t0)
    (local $l0 i32)
    (set_local $l0
      (i32.const<PHONE_NUMBER>))
    (call $testload::address::hfcb094981e27477e
      (get_local $l0))
    (return))
  (table $__indirect_function_table (export "__indirect_function_table") 1 1 anyfunc)
  (global $__heap_base (export "__heap_base") i32 (i32.const 1048576))
  (global $__data_end (export "__data_end") i32 (i32.const 1048576)))

LLDB output:
(lldb) r
Process 49228 launched: './target/debug/wasmtime' (x86_64)
make_heap offset=0, offset32=0
Process 49228 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x182afffef)
    frame #0: 0x0000000101796599
->  0x101796599: movb   %al, (%rdx,%rcx)
    0x10179659d: popq   %rbp
    0x10179659f: retq
    0x1017965a0: addl   %eax, (%rax)
Target 0: (wasmtime) stopped.
(lldb) dis -s 0x101796590
    0x101796590: movl   %edi, %ecx
    0x101796592: movq   0x8(%rsi), %rdx
    0x101796596: movq   (%rdx), %rdx
->  0x101796599: movb   %al, (%rdx,%rcx)
    0x10179659d: popq   %rbp
    0x10179659f: retq
    0x1017965a0: addl   %eax, (%rax)
    0x1017965a2: addb   %al, (%rax)
    0x1017965a4: addb   %al, (%rax)
    0x1017965a6: addb   %al, (%rax)
    0x1017965a8: addl   %eax, (%rax)
    0x1017965aa: movl   $0x7ffeef, %edi           ; imm = 0x7FFEEF
(lldb) register read
General Purpose Registers:
       rax = 0x0000000000000032
       rbx = 0x00007ffeefbfeca8
       rcx = 0x000000007fffffef
       rdx = 0x0000000102b00000
       rdi = 0x000000007fffffef
       rsi = 0x000000010164b000
       rbp = 0x00007ffeefbfd640
       rsp = 0x00007ffeefbfd640
        r8 = 0x0000000000000064
        r9 = 0x0000000000000004
       r10 = 0x0000000000000004
       r11 = 0x00007ffdee465e50
       r12 = 0x0000000000000000
       r13 = 0x0000000000000000
       r14 = 0x00007ffeefbfece0
       r15 = 0x00007ffeefbfeca0
       rip = 0x0000000101796599
    rflags = 0x0000000000010203
        cs = 0x000000000000002b
        fs = 0x0000000000000000
        gs = 0x0000000000000000

here is the wat without memory imports:
(module
  (type $t0 (func))
  (type $t1 (func (param i32)))
  (func $testload::address::hfcb094981e27477e (type $t1) (param $p0 i32)
    (local $l0 i32) (local $l1 i32) (local $l2 i32)
    (set_local $l0
      (i32.const 50))
    (set_local $l1
      (i32.const 16))
    (set_local $l2
      (i32.sub
        (get_local $p0)
        (get_local $l1)))
    (i32.store8
      (get_local $l2)
      (get_local $l0))
    (return))
  (func $load (export "load") (type $t0)
    (local $l0 i32)
    (set_local $l0
      (i32.const<PHONE_NUMBER>))
    (call $testload::address::hfcb094981e27477e
      (get_local $l0))
    (return))
  (table $__indirect_function_table (export "__indirect_function_table") 1 1 anyfunc)
  (memory $memory (export "memory") 16)
  (global $__heap_base (export "__heap_base") i32 (i32.const 1048576))
  (global $__data_end (export "__data_end") i32 (i32.const 1048576)))

this last file was an example to demonstrate the issue of going from 32 bit wasm to x86_64 pointers. I have not tested yet if the first example would now work, since memory imports changed recently

There have now been a bunch more changes, and lots of bugs fixed -- Wasmtime now passes the entire spec testsuite! So it'd be interesting to retry your testcase here now.

Closing; if there are any further issues, please report them!


Angular 17 app can't run with bugsnag/plugin-angular and esbuild

Describe the bug
Angular app fails on start with error Class constructor ErrorHandler cannot be invoked without 'new'
Steps to reproduce

Have in app.module setup like in documentation:

export function errorHandlerFactory() {
  return new BugsnagErrorHandler()
}

In the module providers:
{ provide: ErrorHandler, useFactory: errorHandlerFactory },

Set "builder": "@angular-devkit/build-angular:browser-esbuild", in angular.json
Start the app
An error logged in the console Class constructor ErrorHandler cannot be invoked without 'new'

Btw, it works great with the "builder": "@angular-devkit/build-angular:browser",
Environment

Bugsnag version: 7.22.2
bugsnag/plugin-angular: 7.22.2,
Browser framework version (if any):

Angular: 17.0.7

Browser version (e.g. chrome, safari):
Device (e.g. iphonex):

Example Repo

[ ] Create a minimal repository that can reproduce the issue
[ ] Link to it here:

Example code snippet
# (Insert code sample to reproduce the problem)

Error messages:
Class constructor ErrorHandler cannot be invoked without 'new'

Hi @mclack,
I run yarn start which is ng serve --hmr --port 3000 --open=true.
I don't change anything else when I switch to "builder": "@angular-devkit/build-angular:browser"
Yes, the error stops when comment out { provide: ErrorHandler, useFactory: errorHandlerFactory },
Maybe something to mention is in my angular.json is "aot": true,
"serve": {
          "builder": "@angular-devkit/build-angular:dev-server",
...
}

Can't share the project.
I've found a workaround:
{ provide: ErrorHandler, useClass: AppErrorHandler}

...

export class AppErrorHandler implements ErrorHandler {
   handleError(error: any) {
    Bugsnag.notify(error)
    console.error(error)
  }
}

Please let me know if you need something else from me.

tsconfig is:
{
  "compilerOptions": {
    "target": "ES2022",
    "module": "es2020",
    "moduleResolution": "node",
    "sourceMap": true,
    "emitDecoratorMetadata": true,
    "allowSyntheticDefaultImports": true,
    "experimentalDecorators": true,
    "lib": [
      "es2015",
      "es2016",
      "dom",
      "esnext"
    ],
    "noImplicitAny": true,
    "downlevelIteration": true,
    "suppressImplicitAnyIndexErrors": true,
    "ignoreDeprecations": "5.0",
    "noUnusedParameters": true,
    "strictNullChecks": true,
    "skipLibCheck": true,
    "resolveJsonModule": true,
    "typeRoots": [
      "./node_modules/@types"
    ],
    "useDefineForClassFields": false
  },
  "files": [
    "app/main.ts",
    "polyfills.ts"
  ],
  "include": [
    "**/*.d.ts"
  ]
}

Hi @mclack, have added the link to the project https://stackblitz.com/edit/angular-ivy-7x7fkm?file=src%2Fapp%2Fapp.module.ts

Hi, are there any updates?

Hi, I have the same issue after upgrading to the angular 17 error is thrown:
TypeError: Class constructor ErrorHandler cannot be invoked without 'new'     at new BugsnagErrorHandler2 (index.js:28:28)     at new CustomErrorHandler (CustomErrorHandler.ts:7:5)     at Object.customErrorHandlerFactory [as useFactory] (app.module.ts:30:10)     at Object.factory (core.mjs:6288:38)     at core.mjs:6189:43     at runInInjectorProfilerContext (core.mjs:867:9)     at R3Injector.hydrate (core.mjs:6188:17)     at R3Injector.get (core.mjs:6058:33)     at injectInjectorOnly (core.mjs:911:40)     at ɵɵinject (core.mjs:917:42)

Hi @mclack do you need anything else from my side for this issue?

Hi @mivanyna and @pumpernikiell
Please accept our apologies for the delay in response here.
We are investigating this now, and will post any updates or questions on this thread as soon as we have them.
Thank you for your patience.

No rush? We can live w/o good error logging :)

Hi @mivanyna and @pumpernikiell
Thanks for your continued patience while we've investigated this issue.
We were unable to reproduce the error on our end, both using a separate Angular 17 app, and the app provided by @mivanyna.
@mivanyna, is the code you've shared up to date, and are the dependencies exactly the same as you're currently using in your app? When we've tried to run the repro code, we got dependency conflicts between Angular 17 and several other dependencies. Could you please tell us more about how you've upgraded your app, and which version you used prior to Angular 17?
@pumpernikiell could you also let us know which version of Angular you have upgraded from? Would you also be willing to share an app which reproduces this error, similar to the one here?

Hi @mclack , I'm opening the provided link and it's still reproducing:

There is an error logged in the console.

Hi @mivanyna
Thank you for the clarification.
After looking into this a bit more, we've realised that this error does indeed appear when opening the app on StackBlitz. However, we initially downloaded the app and attempted to build/run this locally, and when doing this, we noticed different errors which were regarding dependency conflicts instead.
Due to the above, we believe that this issue could be due to the dependency conflicts we have observed, and it's possible that the debugging mechanisms on StackBlitz are potentially hiding these conflicts.

Can you confirm whether you have only seen this error when running the app within StackBlitz?
Am I right in thinking you upgraded your app to Angular 17 from a different version? If so, did you only begin to see this error after upgrading?
Can you run this locally and let us know whether you see different errors? If so, would you be able to resolve any dependency conflicts, and then attempt to run this on StackBlitz again?

Hi @mclack,
This error appears only after the start of the app.
Yes, I have upgraded from angular 16 to angular 17.
Please read the steps in the issue and following my answers:
step 2: Set "builder": "@angular-devkit/build-angular:browser-esbuild", in angular.json
Just create a simple project and follow the steps, please.
Everything is specified in the issue here and in comments below.

Hi @mclack,
This is what you need to do for the downloaded project:

Update angular and bugsnag to the latest version in package.json
Use yarn to install
styles.scss - remove imports of the styles - it should be empty
tscongif.json - change "target": "ES2022",
start the app using yarn start
open the http://localhost:4200/
check in the browser's console the error:

Please let me know if there are any questions

Hi @mivanyna
Thank you for your patience here.
We have been able to reproduce the error you were seeing, and have made the necessary changes on the StackBlitz project you provided in order to fix all the errors appearing in the console.
The issue seems like it was down to using the old NgModule rather than standalone components. As suggested by the error message, this meant that the new keyword is required before invoking ErrorHandler. In your app.module.ts, you should edit the NgModule so that providers looks like:
providers:[{ provide: new ErrorHandler, useFactory: errorHandlerFactory }]
You are likely to run into some more errors after this. If so, this should be fixed by adding @bugsnag/js inside allowedCommonJsDependencies within your angular.json. This will look something like:
"architect": {
...
          "options": {
            "allowedCommonJsDependencies": [
              "@bugsnag/js"
            ],
...

Please try the recommendations above and let us know whether that solves the problem.

it works, thanks

Hi!
I've applied your solution @mclack - it fixes problem with the error handler, but right now any errors are not sent to the bugsnag

Hi @pumpernikiell
Are you experiencing any other errors in your app? Can you also check whether any network requests are being made to BugSnag? If so, what are the status of these requests? E.g. 200 (Accepted), 408 (Request Timeout). Additionally, can you please check whether the requests are being made to https://notify.bugsnag.com/.
If you're not doing this already, could you also please try sending a handled event to BugSnag and let us know the outcome of this.
If you're not seeing any requests being made, could you please share some code snippets of how you have configured BugSnag in your app? As this is a public thread, please feel free to open a ticket with us directly by contacting<EMAIL_ADDRESS>

I'm experiencing the same issue.
FWIW: The issue appears to be caused by the following two factors:

The build for my angular application literally imports ErrorHandler from @angular/core. At runtime the @angular/core/fesm2022/core.mjs is resolved for this import, which provides ErrorHandler as a class.

The resolved module for @bugsnag/plugin-angular is in my case @bugsnag/plugin-angular/dist/esm5/index.js, which has the following code in it:

import { ErrorHandler, Injectable } from '@angular/core';
import Bugsnag, { Client } from '@bugsnag/js';
// zones are optional, so we need to detect if they are being used
// see https://angular.io/guide/zone#noopzone
var isNgZoneEnabled = typeof Zone !== 'undefined' && !!Zone.current;
var BugsnagErrorHandler = /** @class */ (function (_super) {
    __extends(BugsnagErrorHandler, _super);
    function BugsnagErrorHandler(client) {
        var _this = _super.call(this) || this;
        if (client) {
            _this.bugsnagClient = client;
        }
        else {
            _this.bugsnagClient = Bugsnag._client;
        }
        return _this;
    }
    BugsnagErrorHandler.prototype.handleError = function (error) {
        var handledState = {
            severity: 'error',
            severityReason: { type: 'unhandledException' },
            unhandled: true
        };
        var event = this.bugsnagClient.Event.create(error, true, handledState, 'angular error handler', 1);
        if (error.ngDebugContext) {
            event.addMetadata('angular', {
                component: error.ngDebugContext.component,
                context: error.ngDebugContext.context
            });
        }
        this.bugsnagClient._notify(event);
        ErrorHandler.prototype.handleError.call(this, error);
    };
    BugsnagErrorHandler = __decorate([
        Injectable(),
        __metadata("design:paramtypes", [Client])
    ], BugsnagErrorHandler);
    return BugsnagErrorHandler;
}(ErrorHandler));
export { BugsnagErrorHandler };

The error is thrown at the line var _this = _super.call(this) || this; in the constructor function. That calls _super without new which is illegal because _super is the resolved ErrorHandler class.

Hi @JJWesterkampAtEndeavour
Thanks for highlighting that.
We are looking into the fesm distribution, and have added a task to our backlog to include this. As such, I'm going to reopen this issue, and while we don't currently have an ETA, we will make sure to share any updates when we have them.

@mclack is there any update on this? I have this problem on several projects and this is preventing me from an essential upgrade.

Hi @JesperHonders
There is currently no update for an ETA we can share on this, but we do have some tasks lined up regarding JavaScript modules, and adding an fesm distribution for Angular is included in this upcoming work.
We will make sure to post any further updates on this thread as they become available. Thanks for your patience in the meantime.


jobs should include information on backend settings used.

What is the expected enhancement?
Currently the configurable settings like, for example, rep_delay or use_esp_readout are not included in either the job, or the included results.  As such, the job does not include full information about how the job was executed on the backend.

5


Add Windows support to Makefile

The make recipes here assume use of .tar.gz archives containing the required dylib from https://github.com/spacemeshos/ed25519_bip32; however, for Windows the dll is released as a zip file. It would be helpful to improve Windows support in the Makefile to handle the library correctly.

This is no longer an issue


Fixed rshift

infl.rshift doesn't exitst in my running.

Thanks for the report. I fixed the problem the correct way, so the fix works in all setups : using bit or bit32 libraries, or Lua 5.3 native bitwise operators.


INT B-18826 Admin UI list requested office users

Agility ticket
Summary
When a MilMove Admin logs in, we want to show the list of requested office users so they can have quick visibility of who has requested accounts. In future work, these users will request accounts via a form in the Office application.
This PR does the following:

updates backend to allow for search functionality in UI
adds UI page for listing requesting office users

How to test

Access MM as an admin
Log in
You should see the newly defaulted UI page of "Requested Office Users"
This should be blank for now since there are none in the db
Change the status value for some users in the office_users table to REQUESTED
Refresh the UI
You should see those users now pop up on this page

Screenshots
When no users in REQUESTED status are in the db

After changing status to REQUESTED for some users

Warnings

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against c73ab7166ef7ec63246574fa6743309fbbc19bc4


Component Support

An initial Component support, which intentionally punts on what to do with attributes. With the way iDOM is currently handling notifications ("create" and "delete"), it'd be very hard to pull attributes into a hash to push into the notification function. Instead, retrieve them with getAttribute / this[prop] on the component's root element.
Closes #9.
TODO

[ ] We still need a way to translate from some arbitrary Component class into the proper tagName.
[ ] What are we going to do with children elements?

In response to the TODO questions, could there be a way to declare a static renderComponent(Component, props, children) method whose return value maps into the iDOM tree?  I realize this could be tough at the babel plugin level, but letting the plugin user define the translation seems necessary for this to remain framework-agnostic.

Closing this initial PR in favor of #43.


how to load more data on scroll?

Thanks for this easy-to-follow code/article series on Flutter's BLOC pattern. After going through the code, I  realized that there's no way we can load more data on scrolling to the bottom of the list. How do you think we can achieve it? Obviously, there's going to be Listview/gridview controller to listen to the scrolling events, but how to pass the page number to the Bloc class so that it can call the API (with new page number) again using the repository/provider classes?
Many thanks in advance!

Interested ...

@amrit-citrusleaf and @computerzman  I am working on Part 3 of this series where you will find this feature and lot more.

Is it implemented?

I will update it this weekend.

@amrit-citrusleaf  @computerzman @Xoshbin Implemented the feature. It's part of the master branch.


In ABCI we need to validate message timestamps w.r.t block time

Codecov Report

Merging #184 (99025c4) into main (7c9eef6) will increase coverage by 7.70%.
The diff coverage is 38.46%.

@@            Coverage Diff             @@
##             main     #184      +/-   ##
==========================================
+ Coverage   61.26%   68.96%   +7.70%
==========================================
  Files          31       31
  Lines        6911     6145     -766
==========================================
+ Hits         4234     4238       +4
+ Misses       2677     1907     -770

Impacted Files
Coverage Δ

src/many-ledger/src/main.rs
0.58% <0.00%> (-0.03%)
:arrow_down:

src/many-ledger/src/module.rs
70.60% <55.55%> (+3.06%)
:arrow_up:

src/ledger/src/multisig.rs
0.00% <0.00%> (ø)

src/many-abci/src/module.rs
0.00% <0.00%> (ø)

src/many-abci/src/many_app.rs
0.00% <0.00%> (ø)

src/ledger/src/main.rs
0.41% <0.00%> (+0.08%)
:arrow_up:

src/many-abci/src/main.rs
0.69% <0.00%> (+0.09%)
:arrow_up:

src/kvstore/src/main.rs
0.81% <0.00%> (+0.18%)
:arrow_up:

src/http_proxy/src/main.rs
1.21% <0.00%> (+0.22%)
:arrow_up:

... and 14 more


Translation on Filipino

I want to ccontribute in translation

Cool, could you use this issue instead #552
Sent with GitHawk


[docs] Demo SearchIcons crashes

[ ] I have searched for similar issues in this repository and believe that this is not a duplicate.

Steps to Reproduce

Visit https://mui.com/components/material-icons/
??
demo SearchIcons crashes

Your Environment

Tech
Version

MUI
v5.5.0

netlify deploy
https://622bf492b027b5000960dea3--material-ui-docs.netlify.app

Browser
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36

Can you please elaborate the issue with screenshots?

This issue was solved in this week's latest version - 5.5.1. Just do a hard refresh and you'll get the latest with this fixed. Thanks for reporting :)


The system can handle the user exceeding login attempts

Prerequisites: #6 #17

done when:
the user exceeds the number of login attempts and the account is blocked until the pharmacist can verify the user and their account.

max 3 attempts -> frozen until employee unfreezes

1 hour


JAMES-3693 Fixup RedisHealthCheck wrong check when Redis Cluster

The healthcheck: org.apache.james.backends.redis.RedisHealthCheck always log can not connect to Redis.
even when Redis cluster work up normal
Reason

Before invoking method redisClusterClient.connectAsync we need to initial partition first by invoking method `redisClusterClient.getPartitions
The method redisClusterClient.connectAsync(StringCodec.UTF8) always success when the cluster fail (eg: 1 /3 node down) => We need one more step for checking.

How to fix it

call .getPartitions first, then .connectAsync -> .clusterInfo()

It seems that RedisHealthCheck has to create new redis connection when check method is run. IMO we should create connection only once

It seems that RedisHealthCheck has to create new redis connection when check method is run. IMO we should create connection only once

I based it on the old way, WDYT? @quantranhong1999

It seems that RedisHealthCheck has to create new redis connection when check method is run. IMO we should create connection only once

If we reuse a single connection, then does Lettuce have a mechanism to recover the connection after a Redis outage? If yes, we can just use a single connection IMO.

It seems that RedisHealthCheck has to create new redis connection when check method is run. IMO we should create connection only once

yes, but we create new ones and close immediately after that

It seems that RedisHealthCheck has to create new redis connection when check method is run. IMO we should create connection only once

yes, but we create new ones and close immediately after that

redisClusterClient is used to create connections. It seems to me that this one is quite heavy and should not be recreated over and over again.

updated, Use single connection for health check


Reading downloaded files from react

Describe the bug
When we download a file from node and it is stored in the default storage __dirname /storage/sd/dist. There seems to be no way for the react app to read that file.
To Reproduce
Steps to reproduce the behavior:

Create endpoint in the node application which downloads a video file (for example: /storage/sd/dist/default.mp4)
Call the endpoint to download file, and after the video is downloaded use <video src="default.mp4"> tag to show the downloaded video.

Expected behavior
The video should play after being downloaded from node.
Screenshots
N/A
BrightSign Device (please complete the following information):

OS Version: <IP_ADDRESS>
Device model: XT1145

Additional context
N/A

Hello, https://blog.j2i.net/2019/05/03/node-on-brightsign/ This blog here might help you start somewhere. You might need to use Nodejs fs module to read the file, as you'll see from the blog post you can call nodejs from index.html. I haven't tried a use case like yours but it should work.

Thanks! was able to figure it out.
Downloaded the file on node with node-file-downloader to /storage/sd/dist and used express to host the static directory /storage/sd/dist. And in react I could just go to the http://<Player_ip>:8020/downloaded_file.mp4 to show the file.


Add "i915_monitoring" resource to GPU plugin

Added "i915_monitoring" resource mounts all GPU devices to requesting container.
This is needed to get GPU metrics from the host.  Requesting pod doesn't know how many GPUs the node it's assigned to has, so there needs to means to request them all.  Only alternative for this would be requesting Privileged mode, which is clearly worse as that would grant access also to all other devices and capabilities.
Checking for expected number of monitoring resources (0/1) is added to tests.

As can be seen from previous CI results, simply adding testing for new GPU plugin resource pushed TestScan() over project "golangci-lint" complexity limit.
Avoiding that requires either:

Doing what Mikko for file creation, but that helps only marginally and is IMHO somewhat messy: https://github.com/mythi/intel-device-plugins-for-kubernetes/commit/479cfdcc1d8caa4fe55f789c516ca88c380d4402
Lifting the notifier checks to its own function, e.g. validateNotifierScan(), but that requires specifying testCase as its own type
Lifting the whole test case running to its own function.  That also requires specifying testCase as its own type

I chose last option because moving the file system creation there also (as suggested earlier by Dmitry Rozhkov) allows simplifying the mock file system management, and means that testCase type is defined only few lines above its usage: https://github.com/eero-t/intel-device-plugins-for-kubernetes/blob/gpu-plugin-i915_monitoring-resource/cmd/gpu_plugin/gpu_plugin_test.go#L45
(Also, if testCase run at some later point point grows also too complex, it's then simply to split validateNotifierScan() off it.)
I've split the commits for easier review, so that "gofmt" is done as separate (last) commit.

I chose last option because moving

@eero-t FWIW, this version gives gocognit score of 22 while my version gives 16 (out of 31).

@eero-t FWIW, this version gives gocognit score of 22 while my version gives 16 (out of 31).

@mythi Oh, my assumption was really off.  I didn't realize gocognit penalizes those loops that badly (Fedora doesn't have package for that or even gocyclo) => I'll update the options comment
While your suggestion simplifies FS cleanup I still like a bit more using defer for that in separate function, and not needing to "explode" testcase contents to createTestFiles() args.  But I don't have strong preference.
What the others say?

While your suggestion simplifies FS cleanup I still like a bit more using defer for that in separate function,
and not needing to "explode" testcase contents to createTestFiles() args.

my version was hacked rather quickly, maybe defer works with t.Run() too so its worth giving a try. one other alternative could be to create root in createTestFiles() and have it return sysfs and devfs paths...

my version was hacked rather quickly, maybe defer works with t.Run() too so its worth giving a try.

Yes, defer works for lambda functions too.

I replaced separate test function with a variant of Mikko's earlier suggestion of having separate function just for setting up the sysfs/devfs mock files.  Changes from that suggestion were:

returning sysfs & devfs paths from the function (as I thought creating the path strings separately on two different levels of code was a bit nasty)
Using defer for root removal

@eero-t LGTM too but can you squash the commits please

LGTM too but can you squash the commits please

@mythi I'll push rebase with squashed commits.   Isn't there any project setting where you could specify that preference, or is this something you only request on per-PR basis?

nit: createTestFiles can be done in a separate PR.

@bart0sh If that is missing, PR would fail golangci-lint complexity check (as mentioned in my second comment).

I'll push rebase with squashed commits. Isn't there any project setting where you could specify that preference

@eero-t thanks. I guess my rule of thumb is that the individual commits in a PR would be justified as PRs of their own too but I don't think we're too strict on this. This PR had monitoring+testing for it + gofmt as their own commits but those would be logical to have in a single commit (or PR). createTestFiles could have been a PR of its own and merged before this....

createTestFiles could have been a PR of its own and merged before this....

Why it would need separate PR instead of just being a separate commit in this PR (like it was earlier)?

@eero-t

Why it would need separate PR instead of just being a separate commit in this PR (like it was earlier)?

Because introducing createTestFiles is an independent change.

Because introducing createTestFiles is an independent change.

@bart0sh All commits are supposed to be "independent" to some degree, but I assume you're talking here about the change being independent enough that the commit order can be changed without conflicts.
This doesn't seem to be a documented project policy, and it's applied inconsistently. For example all 4 commits in the previous PR merged from me were independent to that degree: https://github.com/eero-t/intel-device-plugins-for-kubernetes/commits/gpu-plugin-testing-improvements
Are you suggesting that also all of them should have been separate PRs? If not, could you explain more in detail where the line should be drawn, agree with the others, and document the "Good pull request guidelines"?
(Or if there's already a good policy documented elsewhere, point to it.)
That way you can just link the doc if PR seems non-conforming, and my & others' future PRs get less bikeshedding.


[FX-4590] Refactor from typescript to plain javascript

FX-4590
Description
Refactor Tailwind preset from typescript, so it can be also used in Picasso itself for development.
How to test

Temploy
It was tested in the Picasso here
and in the Staff Portal here

Screenshots
Development checks

[x] Add changeset according to guidelines (if needed)
[x] Read CONTRIBUTING.md and Component API principles
Make sure that additions and changes on the design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
Annotate all props in component with documentation
Create examples for component
Ensure that deployed demo has expected results and good examples
Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[x] Self reviewed
Covered with tests (visual tests included)

Breaking change

codemod is created and showcased in the changeset
[x] test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-anvil ping reviewers

@toptal-bot run package:alpha-release

@toptal-anvil ping reviewers

@toptal-bot run package:alpha-release

@toptal-anvil ping reviewers


extend CompareToZero doc

Thank You Error Prone for not just helping a project "conform to contract", but actually avoid real bugs we've found when enforcing this bug pattern... it seems worth to me spell this out more clearly in this doc.
see https://github.com/apache/fineract/pull/951 for https://issues.apache.org/jira/browse/FINERACT-1014
@xurror @thesmallstar @ptuomola FYI

@percyashu FYI & great job for having found the related bug in our code using Error Prone - Thank You for your participation in Google Summer of Code!

Thank you for the kind note!  I'm sure the author of this check, @graememorgan, would be excited to hear this. 😄
Our source of truth is the Google-internal repo, so we'll review this internally and then push it back out.

We discussed this internally and decided to stick with the current docs.  But thank you for the positive feedback!


[mempool] Mempool testing

Testing using cluster test

/canary

:broken_heart: Test Failed - ci-test-success

/canary

:sunny: Canary successful

this is blocked by the lack of a test for the default fn failover. looks good otherwise

@davidiw This is kinda a clustering of 2-3 different PRs, because I'm just holding one PR open so I can run cluster test against whatever I want.  Hence the draft :)


Done chunk norris joke generator ap

I have created chunk norris joke generator app using reactjs
#week 5 challenge

@satendrassharma could you solve the conflicts please?
once that is done I'll merge this pr

Thanks for submitting your work, hope we can see more @satendrassharma


Can't always close browser with ctrl-c

When the built in browser has focus, I'm unable to close it with ctrl-c.
I have to click the header first, which took me a while to figure out when first using it :)

Are you on OSX? Does this happen with all sites you visit in HyperTerm?
Has anyone else experienced this/Can anyone else reproduce this?

Yes, if you open a page:
$ google.com
then you can close it with ctrl-c
but if you click somewhere on the page, it will take the focus,
which makes ctrl-c not got to the terminal

We can fix this with a global accelerator registration of ctrl+c and thusly make the webview great again?

sounds good, I could work on this if you'd like. not sure how difficult it would be :)

I can confirm that this is happening. Would love to see a fix -- this feature is the coolest thing about HyperTerm.
OS X 10.11.6 and HyperTerm <IP_ADDRESS> installed by homebrew

It is indeed a useful feature. Any news? :)

Not sure if this is related, but it seems that new tabs don't work as expected when the browser is open... opening a new tab always gives me the same browser view. It's not just a rendering issue, I can interact with the browser normally from any of the new tabs.

BTW I just found this built-in browser accidentally, I was trying to clone a repo and somehow it opened the github URL instead

That shouldn't be the case since it should have said "command not found". Did you paste the url by mistake?