[FirebasePlugin messaging:didRefreshRegistrationToken:]: unrecognized selector sent to instance

App crashes due to this error with the latest plugin release 0.1.25

Confirmed this on IOS 11
[Firebase/Messaging][I-FCM002023] The object <FirebasePlugin: 0x1d409a770> does not respond to -messaging:didReceiveRegistrationToken:, nor -messaging:didRefreshRegistrationToken:. Please implement -messaging:didReceiveRegistrationToken: to be provided with an FCM token.

Bit more logging, tokens do get created and returned.
magicalCordovaIOS[2581:1042130] InstanceID token: f0hBo_SjJfQ:APA91bHUU7dZigBjzVtMeB-GvhLbX4avBWTru_gLOhzp6J5SYD9niTHAO47b-ZDWSGfF3829GMzpyJsT2KI58AWA6_9diVuGqj5tFfh6MfwI05KTSm6UprzW3yjIT47nEFzIPx0o3V3R
magicalCordovaIOS[2581:1042130] Unable to connect to FCM. Error Domain=com.google.fcm Code=2001 "FIRMessaging is already connected" UserInfo={NSLocalizedFailureReason=FIRMessaging is already connected}
magicalCordovaIOS[2581:1042130] Connected to FCM.
magicalCordovaIOS[2581:1042130] InstanceID token: f0hBo_SjJfQ:APA91bHUU7dZigBjzVtMeB-GvhLbX4avBWTru_gLOhzp6J5SYD9niTHAO47b-ZDWSGfF3829GMzpyJsT2KI58AWA6_9diVuGqj5tFfh6MfwI05KTSm6UprzW3yjIT47nEFzIPx0o3V3R
magicalCordovaIOS[2581:1042130] Asking for Firebase Permission
magicalCordovaIOS[2581:1042130] After asking for Firebase Permission
magicalCordovaIOS[2581:1042810] [Firebase/Messaging][I-FCM002023] The object <FirebasePlugin: 0x1d409a770> does not respond to -messaging:didReceiveRegistrationToken:, nor -messaging:didRefreshRegistrationToken:. Please implement -messaging:didReceiveRegistrationToken: to be provided with an FCM token.
magicalCordovaIOS[2581:1042130] f0hBo_SjJfQ:APA91bHUU7dZigBjzVtMeB-GvhLbX4avBWTru_gLOhzp6J5SYD9niTHAO47b-ZDWSGfF3829GMzpyJsT2KI58AWA6_9diVuGqj5tFfh6MfwI05KTSm6UprzW3yjIT47nEFzIPx0o3V3R
magicalCordovaIOS[2581:1042130] Successfully Sent token to magical server...
magicalCordovaIOS[2581:1042130] InstanceID token: etMUkNvSNgw:APA91bH43e9KMkUDrxSDs05kKWTlM1crSbRtDQqvazjWQNmI_b63UcvxWfKTcdvy4tuIio7osNZJsBGycrTmLSxXzobW5BhAcearjo-AlJ4D_BqoNrInXCMASAx0oV3-33KiOIRreG5l
magicalCordovaIOS[2581:1042130] Unable to connect to FCM. Error Domain=com.google.fcm Code=2001 "FIRMessaging is already connected" UserInfo={NSLocalizedFailureReason=FIRMessaging is already connected}
magicalCordovaIOS[2581:1042130] etMUkNvSNgw:APA91bH43e9KMkUDrxSDs05kKWTlM1crSbRtDQqvazjWQNmI_b63UcvxWfKTcdvy4tuIio7osNZJsBGycrTmLSxXzobW5BhAcearjo-AlJ4D_BqoNrInXCMASAx0oV3-33KiOIRreG5l

I think there may be a relationship with this error message:
FIRMessaging received data-message, but FIRMessagingDelegate's-messaging:didReceiveMessage: not implemented.
The IOS 1.25 code does not accept Data Only notifications. Standard default Notifications are received successfully. Both with the app in the background and the foreground.

Here are the 3 message types:
Data Only:
[Firebase/Messaging][I-FCM002019] FIRMessaging received data-message, but FIRMessagingDelegate's-messaging:didReceiveMessage: not implemented
Notification Only:
aps =     {
    alert =         {
        body = "message body goes here";
        title = "Magical OI Example";
    };
};
"gcm.message_id" = "0:1519949841485656%98df36c898df36c8";
tap = 0;

}
Notification and Data:
aps =     {
    alert =         {
        body = "message body goes here";
        title = "Magical OI Example";
    };
};
"gcm.message_id" = "0:1519950025514507%98df36c898df36c8";
icon = "https://www.jbhifi.com.au/FileLibrary/ProductResources/Images/187591-L-LO.jpg";
"original_item_id" = "%%MAGLIKEVIEWBC.LIKEGUIDS%%";
tap = 0;
text = "%%MAGLIKEVIEWBC.LIKENAMES%%";
title = "%%ORYXSESSION.FIRSTNAME%% %%ORYXSESSION.LASTNAME%% added a new item";
"to_name" = "%%MAGFRIENDLIKEBC.FRIENDFIRSTNAME%%";
username = "%%ORYXSESSION.USERNAME%%";

}

If I did commented out this code in my Javascript, the Data message showed in the console
/*
window.FirebasePlugin.grantPermission(function () {
window.FirebasePlugin.hasPermission(function (data) {
console.log(data.isEnabled);
});
});
*/

Downgraded to 0.1.24 and that error went away - however IOS push notifications still not working in background nor foreground...

I’ll post my code and you can try it. It took a few days to figure it out. And a combination of other people’s code.

Thnks, nice one, I've been struggling with this for a while now. IOS push just doesn't work with Firebase, but on the other hand I can send notifications with APN directly using https://github.com/noodlewerk/NWPusher

Get the latest cordova-plugin-firebase from GitHub
cordova plugin add https://github.com/arnesson/cordova-plugin-firebase --save
In your  -Info.plist file, FirebaseAppDelegateProxyEnabled = NO
I assume you have set up the correct Firebase APNKEYs or ID's
Check you  Capabilities:

I did not execute the grantPermission / hasPermission code - this stopped the Data notifications from working.
AppDelegate.m goes in /Classes and
AppDelegate+FirebasePlugin.m goes in /Plugins/cordova-plugin-firebase
AppDelegate.h.zip
AppDelegate+FirebasePlugin.m.zip

I have figured out that should only ask for permission first time app is installed and then thereafter just check via hasPermission:
            console.log('Checking for Notification Permission');

                        if (isIOS()) {
                console.log('Checking for Notification Permission');
                window.FirebasePlugin.hasPermission(function (data) {
                    if (!data.isEnabled) {
                        console.log("App does NOT have IOS Notification Permission");
                        magical.utility.popup('App cannot send you notifications via your device. Please go to settings \
                                and enable app notifications');
                    } else {
                        console.log("App does have IOS Notification Permission " + data.isEnabled);
                    }
                });
            }

Can anyone confirm whether https://github.com/arnesson/cordova-plugin-firebase/pull/576 fixes this issue?

I got working with this:
cordova platform remove ios
cordova plugin add https://github.com/arnesson/cordova-plugin-firebase --save
cordova platform add ios

This issue is blocking me from deploying an app.
I have limited Obj-C experience but it looks like at we at least need to stub the selector...
reason: '-[FirebasePlugin messaging:didRefreshRegistrationToken:]: unrecognized selector sent to instance 0x60000106c480'
Can someone point me to what delegate this method needs to be implemented in?
Does anyone know in what cases the problem may occur?

@jonasmunk Check what fixed it for me here  #584

@fjckls I do not believe that is a fix, if the delegate selector is not implemented the app will crash at seemingly random instances (very seldom).
Can you explain why this should fix the issue?

@jonasmunk to be honest haven't paid that much attention - that's just what I did - installed from git master instead of npm and there were no more errors, which where coming up constantly with the npm version...

@fjckls Ok, thanks - that sounds like a different issue then.

@jonasmunk Did you find the solution?
I got it rejected as well from iOS app store.

per @fjckls this has been fixed on master, so it should be resolved in version 1.0


I'd like to join this project's community

Your public repo
https://github.com/geordanshannon/gov4git-identity-public.git
Your public branch
main

Approved.

 Follow up
On Wednesday, 06-Mar-24 01:58:49 UTC by Gov4Git dev
@geordanshannon was added to the community.


Crash when selecting and CTRL+D

Godot version:3.2.dev.offical
OS/device including version:windows10 64bit
Issue description:
Sorry for using Google Translate.
In 2D workspace, left mouse button selects a Node2D (press and hold), then press CTRL+D, Godot will crash.

Duplicate of #27523


Error connecting to target: TLS Cannot be established

I'm running this against the request smuggling labs on hackthebox, but they don't have https properly setup. Is there a way to bypass this error message?

Hi, thanks for trying out SmuggleFuzz, i appreciate it. For more info see here: https://github.com/Moopinger/smugglefuzz/tree/experimental-h2c


Remove CircleCI

Switch fully to GitHub Actions

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.62%. Comparing base (b0010bf) to head (10cec55).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master       #5      +/-   ##
==========================================
- Coverage   95.70%   95.62%   -0.08%
==========================================
  Files          54       54
  Lines        2583     2583
==========================================
- Hits         2472     2470       -2
- Misses        111      113       +2

Flag
Coverage Δ

unittests
95.62% <ø> (?)

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

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


Calling get_palette before setup seems to raise an error

Description
It seems like the recent change to set default_options instead of options causes this to error.  It raises here https://github.com/catppuccin/nvim/blob/main/lua/catppuccin/palettes/init.lua#L7 since O is nil.
I was able to fix this by changing that line to default_options, but I'm not sure if that's the correct approach. That property does get set after setup.
For reference, I pull in the palettes to pass to some custom highlights in setup:
local colors = require("catppuccin.palettes").get_palette(palette or "mocha")
require("catppuccin").setup({
  flavour = palette or "mocha",
  custom_highlights = {
    cjsxElement = { link = "@constructor" },
    cjsxAttribProperty = { link =<EMAIL_ADDRESS>},
    MatchParenCur = { fg = colors.yellow, style = { "bold" } },
    MatchParen = { bg = colors.base, fg = colors.yellow, style = { "bold" } },
    LspInlayHint = { link = "Comment" },
  },
  ...

Neovim version
NVIM v0.10.0-dev-546+g3bf887f6e0
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3

Terminal and multiplexer
wezterm 20230622-212623-9a24f61c with tmux 3.3a
Catppuccin version / branch / rev
main
Steps to reproduce
The snippet is listed above.
Expected behavior
I'd expect it to not throw an error.
Actual behavior
It does.
Repro
No response

Can you try again?

Yeah I've encountered the same issue. I've refactored my custom_highlights into a function, but am unsure how to set the value for an integration, e.g. integrations.navic.custom_bg = colours.base.

Sorry for the inconveniece, maybe fixed in https://github.com/catppuccin/nvim/commit/841d8abf3be39de833d95a592a1fbbb1b9851296
For a better way, you can use the function
require("catppuccin").setup({
  flavour = palette or "mocha",
  custom_highlights = function(colors)
    return {
      cjsxElement = { link = "@constructor" },
      cjsxAttribProperty = { link =<EMAIL_ADDRESS>},
      MatchParenCur = { fg = colors.yellow, style = { "bold" } },
      MatchParen = { bg = colors.base, fg = colors.yellow, style = { "bold" } },
      LspInlayHint = { link = "Comment" },
    }
  end
}

About the navic integration, yeah I'm troubled by it too. Maybe we should accept integration function...

Can you try again?

This works great for me! Can hold off on closing if the above question is still relevant. Thank you 😄

Will add this to backwards compatibility check asap, thank you so much!!

Sorry for hijacking this thread, but yeah I've just resorted to hard coding the value for now. I've seen some other themes dynamically convert strings but not sure if this is the best way either.


HTTPS feeds does not displaed with self-signed certificate.

Vienna (Version 3.0.0 Beta 20 :0fb193d:)
does not display feeds with self-signed certificate.
I have some inter-corporate feeds with https:// and private self-signed certificate,
Vieena does not display them.
See screenshot:

If run Vieena from console, displayed this errors:
mks-mac:MacOS mike$ ./Vienna
2014-02-09 13:03:53.829 Vienna[6407:b70b] CFNetwork SSLHandshake failed (-9807)
2014-02-09 13:03:53.905 Vienna[6407:b70b] CFNetwork SSLHandshake failed (-9807)

Ohh, yes.. after one year I install vienna on new device.. and again forgot why all my feeds (intra company) not displayed.
Only by this ticket I remembered :)
And nothing changed since that time.

« Window -> Activity Window »

Connecting to https://mycompany/feed.php?************************
Error retrieving RSS feed: A connection failure occurred: SSL problem (Possible causes may include a bad/expired/self-signed certificate, clock set to wrong date)

Please add option or popup or any other user interaction, for add exclude for these certificates.

Same here I would like the option per feed to allows self-signed certs for my internal company feeds rather than doing the work around to install the certificate manually (which is not the end of the world), like one does in a web browser.


mnist_manipulation.py is not working at all for me

I'm running python 2.7 on OS X.  Most of the code has been working (or I could make it work with a couple little tweaks here and there, but this section seems totally broken.
Existing is:
fig = plt.figure()
for n in range(10):
    sfig = fig.add_subplot(5, 2, n)
    ax.matshow(z1, cmap = matplotlib.cm.binary)
    plt.xticks(np.array([]))
    plt.yticks(np.array([]))
plt.show()

I think this is a bit closer...  But it just makes plots that are single long lines.
for n in range(10):
    sfig = fig.add_subplot(5, 2, n+1)
    sfig.matshow(avg_pixels.ix[n:n,:], cmap = matplotlib.cm.binary)
    plt.xticks(np.array([]))
    plt.yticks(np.array([]))
plt.show()

Thanks for the report! The fixes are here. The missing line took one row of a pandas data frame and turned it into a 28x28 matrix, ready to be plotted.
https://github.com/DarrenCook/h2o/commit/c70c4e180157de9a1edd36e993e2a3df25975a6d
(Looks like it was some bad copy-and-pasting from the Jupyter notebook I was working in, at the time.)

Great, thanks!


Minor edits to improve readability

Looks great! Thanks. 🙂  The only part I disagreed with was the use of however, so just reverted that.


ENH: update package version

Hi! This is the friendly automated conda-forge-webservice.
I've started a version update as instructed in #236.
I'm currently searching for new versions and will update this PR shortly if I find one! Thank you for waiting!
Fixes #236

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.


update nodemon => fix security issues from dependencies

Hi,
thank you for the package :-)
Just updated the nodemon version as npm audit shows me some vulnerabilities from this package which do no longer occur with the newer version.
Would be nice if you could update the package. Thank you.
Regards
Felix

well - just thought the test would pass ;-) but the node version was really old. so I updated the test and used another more popular (and working) version of the md file linter.
now everything should be up to date again.

Hi guys, could you give me write access to the repo, so I can merge the stuff on my own? I see that you have no time to work on the project. I don't have much time either, but I can offer to update a project like this twice a year.
Of course I can create my own version of the package, which is up to date. But I prefer not to mess up npm.
Regards Felix

@ChrisWren any chance to merge/publish this fixes and give access to @FelixFurtmayr ?

Published fork with this fixes here<EMAIL_ADDRESS>
https://www.npmjs.com/package/@baladins/grunt-nodemon
https://github.com/Baladins/grunt-nodemon/commits/master

@FelixFurtmayr i invited you on the npm and github witg write access.

Hi hthetiot, thanks for the innitiative :-)
I suggest we change  the package name then to "grunt-nodemon-latest" and publish it on npm - what do you think?

well, i wanted "grunt-contrib-nodemon" but was taken, i prefer using @baladins/grunt-nodemon since i use this github org to maintain dead packages. and only the prefix change not the package name.

I'm fine with @baladins/grunt-nodemon.


#42 prepared release 0.3.1

resolves #42

Codecov Report

Merging #44 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #44   +/-   ##
=======================================
  Coverage   96.66%   96.66%
=======================================
  Files          12       12
  Lines         120      120
  Branches        6        6
=======================================
  Hits          116      116
  Misses          4        4

Continue to review full report at Codecov.

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


[PepperBridgeAbstract, DealabsBridge, HotUKDealsBridge, MydealsBridge] Streamlining Group Management

Since groups can change URLs, be created, or removed at the discretion of website administrators, maintaining a valid and functional list of groups is impractical.
Users can now enter the part of the URL that defines the group in a text field, rather than searching through a lengthy, likely outdated list.
The way the RSS feed title is retrieved had to be adjusted accordingly.
Titles are now cached for 15 days to avoid unnecessary website access and to prevent potential bot blocking.
Existing feeds will continue to work, as their parameters remain unchanged; only the method for inputting them has been modified.

ok cool.
I want to deprecate loadCacheValue.
$this->cache should be used instead in my personal opinion. all bridges have access to this cache


pshtt may not be handling client cert authentication properly

See https://github.com/18F/pulse/issues/758 for the details, but it looks like pshtt may choke when client certs are required and mark it as non-compliant. If this is true, I think we should look into ways to prevent this.
cc @PaulSD

The reference example is sdv.example.com. Here's GSA's latest pshtt scan for it, showing that port 80 redirects to 443, but the connection is refused on port 443 because we don't attempt to initiate a connection with a client certificate.
So, thinking about this a bit more...

The requests library does allow a client certificate to be passed with the cert parameter, so in theory we can generate a (fake, invalid) certificate and use it for such requests to measure the connection.
The error message we get when attempting to requests.get("https://sdv.max.gov") with the usual options provides no information to suggest that a client certificate is required to connect. It's just a flat Connection refused at the libcurl level.
Similarly, visiting https://sdv.max.gov in Chrome causes an ERR_CONNECTION_REFUSED error. I am not prompted to provide a client certificate (as I have seen in some websites which ask for one).
Retrying every failed HTTPS connection just to see if it requires a client certificate would be a probably unacceptable performance/bandwidth hit to our scans, as well as extra (unusual-looking) network traffic to federal web services.

Stepping back and looking at it from a policy intent perspective: M-15-13 and BOD 18-01 ask that agencies deprecate insecure traffic and take all available measures to instruct clients to initiate secure connections (and to support those connections once clients make them).
Pshtt evaluates support for secure connections for traditional (server certificate) TLS by making sure port 443 is open and ensuring that the certificate is unexpired and for the intended hostname. The former check is relevant for client authentication, but the latter are not -- so even if we could detect endpoints that expect client certificates, pshtt would not be able to use the same logic path to evaluate the strength of the connection. But when the client provides the certificate, the client is the one that is ensuring authenticity, and so we shouldn't be evaluating the server's obligations there anyway.
That's all to say that pshtt can't really have anything interesting to say about client certificate connections. If they're available at all, then the server's meeting its policy obligations to support them by definition whether or not we scan it, because opening the port is all we could evaluate.
So, we could look into something novel like retrying HTTPS connections another time with a client cert in the specific case of an HTTP redirect that appears to redirect directly to a Connection refused error (as opposed to other certificate/connection error types). However, this is more complexity than we'd ideally need to add to address this case.
@PaulSD: How viable is it to drop the port 80->443 redirect for this hostname? Is it ever expected that that would be used? Dropping port 80 would at least patch the problem, because the domain would be seen as entirely inaccessible over HTTP.
This may also be be compatible with policy intent as a general solution: 80->443 is only allowed for compatibility reasons, so that old links, and the common user behavior of manual link entry, can still be supported even before an HSTS policy takes effect. But these may not be very relevant for the highly specialized (and rare) cases of client-certificate-enabled services, and so it may be acceptable to ask service owners to remove that compatibility redirect.

Another thought: even if we essentially ignore client cert connections from a pshtt / M-15-13 perspective, from a BOD 18-01 perspective we should still be asking that the connection drop support for RC4/3DES/SSLv2/SSLv3.
That would be a domain-scan/sslyze problem, not a pshtt problem, though sslyze may have a better chance of being able to detect the server's need for a client cert than the libcurl-based requests library does.
I'd defer to @h-m-f-t and @jsf9k as to whether they think it's worth looking into the possibility of instrumenting sslyze for this possibility, but I'd also note that if pshtt stays working as it is, then it would be a moot point, because pshtt will still detect the domain as not operative on port 443, which is information the sslyze scanner in domain-scan uses to skip over hostnames without scanning.

Yet another thought: I'm not an expert at TLS connections using client certificates, and thinking about it more, I may be wrong about the server not having obligations to present a valid unexpired certificate during the connection, if the connection is trying to establish mutual authentication. But I also don't know whether we could realistically present a certificate that would get us far enough to evaluate the presented server certificate, if we presented an invalid certificate to the server.

Sorry, port 443 on sdv.max.gov was actually down over the weekend, hence the connection refused error ... That's not the error you should normally get.
The way TLS works with client certificates is:

Client sends "Client Hello" packet to server indicating supported TLS versions, supported Cipher Suites, SNI extension, and some other irrelevant stuff
Server responds with several messages:

"Server Hello" that specifies the selected TLS version, selected Cipher Suite, and some other irrelevant stuff
A message containing the server's certificate
A certificate request (which includes a list of CAs whose certificates the server might accept)
Some other irrelevant messages

If the client has a certificate, it responds with the certificate and some additional irrelevant handshake messages.  Otherwise, the client will reject the handshake.
If the server doesn't like the certificate sent by the client, then the server will reject the handshake.

So, for the purposes here, client certificate authentication does not technically prevent checking the server SSL/TLS version, the configured cipher suites, or the server's certificate.  Whether or not libcurl or sslyze can return those without completing the handshake is a different question, but it is technically possible to get them.  The only thing client cert auth prevents is checking the HSTS header returned in the HTTPS response after the connection is established.  However, in this particular case, the base domain is HSTS preloaded, so does it actually matter that you can't check the HSTS header returned after the connection is established?
In this particular case, I could drop the port 80->443 redirect because users never actually type this URL in manually ... However, there are other cases in my environment where client certs are required and the port 80->443 redirect is needed, for example on a domain that unconditionally requires PIV authentication.  So that wouldn't be a generic solution.
Another monkey wrench here: This particular URL is actually only used by a specific client-side desktop application that uses its own embedded trust store, so we created an internal CA for it that is only trusted by that client app.  So, even after we get past the client cert auth issue, we're still going to run into cert validation issues.  However, I think the discussion https://github.com/18F/pulse/issues/760 may cover this issue.

Sorry, port 443 on sdv.max.gov was actually down over the weekend, hence the connection refused error ... That's not the error you should normally get.
...So, for the purposes here, client certificate authentication does not technically prevent checking the server SSL/TLS version, the configured cipher suites, or the server's certificate. Whether or not libcurl or sslyze can return those without completing the handshake is a different question, but it is technically possible to get them.

Ah, okay, this helps -- now it looks like it's a ERR_CONNECTION_CLOSED in Chrome, and a (35) Server aborted the SSL handshake in cURL.
Running requests.get("https://sdv.max.gov", verify=False) gives:
SSLError: HTTPSConnectionPool(host='sdv.max.gov', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError("bad handshake: SysCallError(-1, 'Unexpected EOF')",),))

Some quick efforts to generate a fake PEM to use as a client certificate and pass in as the cert parameter for that aren't working well:
Error: [('PEM routines', 'PEM_read_bio', 'no start line'), ('SSL routines', 'SSL_CTX_use_PrivateKey_file', 'PEM lib')]

Though I think even if I could figure it out, most of what I said still applies. If killing the port 80 redirect isn't a generic option, this may be tough. Hmm...

The only thing client cert auth prevents is checking the HSTS header returned in the HTTPS response after the connection is established. However, in this particular case, the base domain is HSTS preloaded, so does it actually matter that you can't check the HSTS header returned after the connection is established?

For Pulse's case, and in DHS' scans, this won't be an issue, because preloading a domain automatically grants HSTS compliance for each individual hostname in the domain. (pshtt calculates these separately, though it does return a field about whether the hostname's base domain is preloaded.)

Another monkey wrench here: This particular URL is actually only used by a specific client-side desktop application that uses its own embedded trust store, so we created an internal CA for it that is only trusted by that client app. So, even after we get past the client cert auth issue, we're still going to run into cert validation issues. However, I think the discussion 18F/pulse#760 may cover that issue.

Yeah, you should be fine here as well - it's not required to use a trusted CA, just that it's unexpired and valid for that hostname.

Some quick efforts to generate a fake PEM to use as a client certificate and pass in as the cert parameter for that aren't working well:

A fake cert isn't actually going to help ... Assuming the server is properly validating the client cert, it will simply reject your fake cert and terminate the handshake in the same way as it does when you don't provide a cert.  A quick test using curl on the command line returns SSL_connect: SSL_ERROR_SYSCALL in connection both for a missing client cert and for a fake client cert that is rejected by the server.
--
Re-reading your earlier comments, this stands out at me as as an indicator of some sort of misunderstanding:

But when the client provides the certificate, the client is the one that is ensuring authenticity, and so we shouldn't be evaluating the server's obligations there anyway.

When client auth is not enabled, the server provides the client a cert, and the client ensures the authenticity of the server cert.
When client auth is enabled, the server provides the client a cert, and the client ensures the authenticity of the server's cert, and also the client provides the server a cert, and the server ensures the authenticity of the client's cert.
So, if pshtt needs to ensure that the server's certificate is unexpired and for the intended hostname, then it needs to do this regardless of whether or not client auth is enabled.
Note that in the TLS exchange described above, the server sends its certificate to the client near the beginning of the handshake.  The client should always be validating the server's certificate before reaching the point in handshake processing where client cert auth is relevant.  If the server's certificate is invalid, libcurl should fail with an error about that before it fails with any error related to client cert auth.
So, if we can enough info out of curl to determine that the failure is definitely because of client cert auth (SSL_ERROR_SYSCALL alone seems too generic to be a reliable indicator of that), then it should be safe to assume that curl made it past the server cert validation part...

Hmm... To make things more complicated, it looks like different servers behave slightly differently and cause different curl errors.  Some servers terminate the connection without terminating the handshake resulting in SSL_ERROR_SYSCALL, other servers send an SSL alert before terminating the connection resulting in error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure...

And when I try hitting it via sslyze (via domain-scan), I get this when pinging sdv.max.gov:443:
_nassl.OpenSSLError: error:140E6118:SSL routines:SSL_CIPHER_PROCESS_RULESTR:invalid command
error:140E6118:SSL routines:SSL_CIPHER_PROCESS_RULESTR:invalid command
error:140E6118:SSL routines:SSL_CIPHER_PROCESS_RULESTR:invalid command

The full command and stack trace is:
$ ./scan sdv.max.gov --scan=sslyze --debug
[375f5b42-c19b-470c-93e1-07a84cdf4e7f] Scan UUID.
[sdv.max.gov][sslyze] Running scan...
	Executing local scan...
	Running scans in serial.
		SSLv2 scan.
		SSLv3 scan.
		TLSv1.0 scan.
	Unknown exception: Traceback (most recent call last):

  File "./scan", line 338, in perform_scan
    data = scan_method(scanner, domain, handles, scan_environment, options, meta)

  File "./scan", line 384, in perform_local_scan
    response = scanner.scan(domain, environment, options)

  File "/home/eric/18f/scan/scanners/sslyze.py", line 106, in scan
    response = run_sslyze(data, environment, options)

  File "/home/eric/18f/scan/scanners/sslyze.py", line 204, in run_sslyze
    sslv2, sslv3, tlsv1, tlsv1_1, tlsv1_2, certs = scan_serial(scanner, server_info, data, options)

  File "/home/eric/18f/scan/scanners/sslyze.py", line 420, in scan_serial
    tlsv1 = scanner.run_scan_command(server_info, Tlsv10ScanCommand())

  File "/home/eric/.pyenv/versions/3.6.1/lib/python3.6/site-packages/sslyze/synchronous_scanner.py", line 52, in run_scan_command
    return plugin.process_task(server_info, scan_command)

  File "/home/eric/.pyenv/versions/3.6.1/lib/python3.6/site-packages/sslyze/plugins/openssl_cipher_suites_plugin.py", line 170, in process_task
    preferred_cipher = self._get_preferred_cipher_suite(server_connectivity_info, ssl_version, accepted_cipher_list)

  File "/home/eric/.pyenv/versions/3.6.1/lib/python3.6/site-packages/sslyze/plugins/openssl_cipher_suites_plugin.py", line 220, in _get_preferred_cipher_suite
    first_cipher = self._get_selected_cipher_suite(server_connectivity_info, ssl_version, first_cipher_string)

  File "/home/eric/.pyenv/versions/3.6.1/lib/python3.6/site-packages/sslyze/plugins/openssl_cipher_suites_plugin.py", line 238, in _get_selected_cipher_suite
    ssl_connection.set_cipher_list(openssl_cipher_string)

  File "/home/eric/.pyenv/versions/3.6.1/lib/python3.6/site-packages/nassl/ssl_client.py", line 313, in set_cipher_list
    self._ssl.set_cipher_list(cipher_list)

_nassl.OpenSSLError: error:140E6118:SSL routines:SSL_CIPHER_PROCESS_RULESTR:invalid command
error:140E6118:SSL routines:SSL_CIPHER_PROCESS_RULESTR:invalid command
error:140E6118:SSL routines:SSL_CIPHER_PROCESS_RULESTR:invalid command

Using cached Public Suffix List...
Results written to CSV.

This looks like a toughie...

@PaulSD can you share another hostname which demonstrates different behavior via cURL from sdv.max.gov

Ok, for testing:
sdv.max.gov now has a bad server cert, which makes curl barf before hitting the cert auth part.  If you tell curl to ignore the server cert error and continue, then the server rejects the missing (or invalid) cert by closing the TCP connection without a TLS alert.
sdx.max.gov has a good server cert.  The server rejects the missing (or invalid) cert by sending a TLS alert before closing the TCP connection.

It looks to me like something is hosed in your sslyze.  self._ssl.set_cipher_list(cipher_list) should be called before the SSL handshake starts.
Here's what I get:
$ python3 -m sslyze sdv.max.gov
   sdv.max.gov:443                       => <IP_ADDRESS>   WARNING: Server REQUIRED client authentication, specific plugins will fail.

Hmm, you're right that the sslyze command line interface seems to handle this better than the Python code. I get crashes in Python (and filed an issue about one here: https://github.com/nabla-c0d3/sslyze/issues/294).
It looks like this is going to be tough given pshtt's current code structure, since the SSLyze-based checks only happen after we've already ruled out various TLS handshake errors (we only proceed to the SSLyze section if the connection failed with verify=True but passed with verify=False).
So we could change the logic to run all TLS handshake errors (where it's something more interesting than "port 443 isn't open") through SSLyze as well and try to determine error conditions there. That would require adjusting a decent amount of logic, but might have other benefits in detecting other novel situations (and in just detecting all cases where port 443 is open but not responding in expected ways, which agencies may be interested whether or not certain kinds of configurations are compliant with policies, etc).
Since it'd be a non-trivial change, with the possibility of regressions, I'd love to hear any thoughts from @h-m-f-t or @jsf9k before I take a whack at it.

@konklone I think you're right.  As long as port 443 is open we should run the host through {{sslyze}}.

@konklone @PaulSD
I'm running into this issue as well with workspace.usda.gov.

We are seeing this same issue with https://vhs.services.nesdis.noaa.gov which is Citrix NetScaler Access Gateway with Client Certificate Authentication set to mandatory.

We are seeing this same issue with trident.fisheries.noaa.gov and trident-test.fisheries.noaa.gov. Both have Client Certificate set to mandatory and when scanned return saying that TLS/SSL is not enabled let alone being able to detect an HSTS header.

We have a pseudo workaround for our netscaler, allowing it to be scanned and show complaint without lowering our security posture too much. Be happy to share configurations @jonathanosullivan @rickminer .

Client cert issues should be resolved by #179.


Failures on [macros] Add first language tests for introspection.

Most of these failures are to do with wiring up macro configuration rather than being about the details of the test, I'll tackle those first.
There are new test failures on [macros] Add first language tests for introspection..
The tests
language/macros/introspect/class_test Crash (expected Pass)
language/macros/introspect/class_test DartkCrash (expected Pass)
language/macros/introspect/failure_test Crash (expected Pass)

are failing on configurations
cfe-strong-linux
cfe-weak-linux
dart2js-hostasserts-linux-d8
dart2js-linux-chrome
dart2js-minified-linux-d8
dart2js-production-linux-d8
dart2wasm-linux-chrome
dart2wasm-linux-d8
dart2wasm-linux-firefox
dart2wasm-linux-jscm-chrome
ddc-linux-chrome
ddc-linux-chrome-unsound
vm-mac-debug-arm64
vm-mac-release-arm64

More:
The tests
language/macros/augment/class_declarations_macro_test CompileTimeError (expected Pass)
language/macros/augment/class_declarations_macro_test Crash (expected Pass)
language/macros/augment/class_declarations_macro_test DartkCrash (expected Pass)
language/macros/augment/class_definition_macro_test CompileTimeError (expected Pass)
language/macros/augment/class_definition_macro_test Crash (expected Pass)
language/macros/augment/class_definition_macro_test DartkCrash (expected Pass)
language/macros/augment/class_types_macro_test CompileTimeError (expected Pass)
language/macros/augment/class_types_macro_test Crash (expected Pass)
language/macros/augment/class_types_macro_test DartkCrash (expected Pass)

are failing on configurations
analyzer-asserts-linux
analyzer-linux
cfe-strong-linux
cfe-weak-linux
dart2js-hostasserts-linux-d8
dart2js-hostasserts-linux-d8-unsound
dart2js-linux-chrome
dart2js-minified-linux-d8
dart2js-production-linux-d8
dart2wasm-linux-chrome
dart2wasm-linux-d8
dart2wasm-linux-firefox
dart2wasm-linux-jscm-chrome
ddc-linux-chrome
ddc-linux-chrome-unsound
vm-mac-debug-arm64
vm-mac-release-arm64

Thanks @nshahan, it looks like simple timeouts, sent a PR increasing the timeout
https://dart-review.googlesource.com/c/sdk/+/355700

@davidmorgan
pkg/dev_compiler/test/macros/macros_test is still flaking with timeouts as recently as today.
https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket/8753652133615332705/+/u/test_results/ignored_flaky_test_failure_logs
Interestingly it looks like it timed out at 30 seconds instead of 1 minute so something still isn't working as expected?

Thanks!
Indeed it looks like the annotation does nothing :( or at least not what I expected: I checked by adding sleep in the test.
If I move it to the "group" it seems to work
https://dart-review.googlesource.com/c/sdk/+/357300
as verified with a "sleep".

@davidmorgan
The test seems to be more reliable but it is still timing out on the linux configuration.
https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket/8752497656701347281/+/u/test_results/ignored_flaky_test_failure_logs

Sorry about that--thanks for nudging again.
I tried harder to repro this time, I managed to get a failure with 200 simultaneous runs on my Linux workstation.
for s in (seq 401 650); fish -c "if out/ReleaseX64/dart-sdk/bin/dart --enable_asserts --sound-null-safety -Dtest_runner.configuration=web-dev-unittest-asserts-linux --ignore-unrecognized-flags --packages=.dart_tool/pac
kage_config.json pkg/dev_compiler/test/macros/macros_test.dart 2>&1 >~/var/deflake/$s; echo "ok"; else; echo $s; end" & end

if I increase the number of simultaneous runs to 250 I get plenty of failures.
If I then double the timeout I get no failures, so I think there is no actual breakage here, just slowness under load.
Sent you https://dart-review.googlesource.com/c/sdk/+/360000

If updating the kernel version vm-aot macro tests crash, e.g. python3 tools/test.py -n vm-aot-linux-release-x64 language/macros/augment/class_types_macro_test.
This seems to be caused by
a) The test is run via pkg/vm/tool/gen_kernel which runs a checked in dart.
b) It then finds the wrong platform when compiling macros. Doing something like this seems to fix that (untested for other scenarios):
diff --git a/pkg/front_end/lib/src/macros/macro_target_io.dart b/pkg/front_end/lib/src/macros/macro_target_io.dart
index c231c82e8ec..4647a8a4b1c 100644
--- a/pkg/front_end/lib/src/macros/macro_target_io.dart
+++ b/pkg/front_end/lib/src/macros/macro_target_io.dart
@@ -30,12 +33,12 @@ Uri _findSdkSummary({Uri? targetSdkSummary}) {
     return targetSdkSummary!;
   }

-  // If the currently-running tool is in a Dart SDK folder, use the platform
-  // dill from there. Failing that, try searching from the target dill.
+  // Search the target dill, if any, first. Then if the currently-running tool
+  // is in a Dart SDK folder, use the platform dill from there.
   List<Directory> searchDirectories = [
-    new File(Platform.resolvedExecutable).parent,
     if (targetSdkSummary != null && targetSdkSummary.isScheme("file"))
       new File.fromUri(targetSdkSummary).parent,
+    new File(Platform.resolvedExecutable).parent,
   ];

   for (Directory searchDirectory in searchDirectories) {

c) When trying to execute the macro that is now compiled with the updated-kernel-version it does so on the running dart version and fails, crashing the compiler without trace:
Unhandled exception:
IsolateSpawnException: Unable to spawn isolate: Can't load Kernel binary: Invalid kernel binary format version.

In this case it seems to be at _SingleIsolatedMacroExecutor.start (package:_macros/src/executor/isolated_executor.dart).
I am going to mark the crashes as accepted in https://dart-review.googlesource.com/c/sdk/+/399662.


Fix Error Causing Voting to Fail

Voting using .vote() checks if the post is archived, and if it is, it raises the VotingInvalidOnArchivedPost error.
However, prior to this fix, it checked if the net_rshares of the post was 0, which would also fire if the post did not have any votes on it yet. This fix allows posts that aren't archived but have 0 votes to be voted on.

+1.


How to remove some column of select

Hi!
I have one modelObject which select some columns of a table, the user could query which columns wants to show, but I want omit some columns by permissions.
Using omit I could remove the columns  but this method was deprecated and removed from 3.0
I have not idea how could remove any column from select or list the columns selected,
My system carry de modelObject from many "filters" before fetch (await // then) data from db
works like this:
 ......
 const modelObject=MyModel.query();
 queryColumns(modelObject); //(mo)=>mo.select(...req.query.fields)
 omitColumns(modelObject); //(mo)=>mo.omit(...req.query.fields) here the user could remove some colums if he won't that info
 addColumnsWithFilters(modelObject); //(mo)=>mo.select(...) here I force to show the columns if any filter require that info
 applyFilters(modelObject); // here could be added withgraphjoined, and other stuffs to filter rows
 applyOrder(modelObejct); // ordering
 ......
 omitColumnsByPermissions(modelObject);//here, how could I list or make a review of the columns to replace omit method?
 const data = await modelObject;
 // I know here I could data.forEach and then delete that fields but I won't do that, I want omit that columns o.O
 send(data);

Thanks a LOOOOOOOOT
you are GIGANT!!!

The only way to alter selects in 3.0.0 is by using clearSelect() which erases all previous selects.
If you wanted to add something like omit() again, you could add your own QueryBuilder and implement something like this (simplified)
class QueryBuilder extends objection.QueryBuilder {
  selects = []

  select(...columns) {
    this.selects.push(…columns)
    return super.select(…columns)
  }

  omit(…columns) {
    this.selects = this.selects.filter(column => !columns.includes(column))
    return this.clearSelect().select(…this.selects)
  }
}

class Model extends objection.Model {
  static QueryBuilder = QueryBuilder
}

This should do the trick.

Actually, this wouldn't work for the most common case of select('*'). An alternative version would use runAfter() to remove the desired properties from the results, something like this:
```js
class QueryBuilder extends objection.QueryBuilder {
  omit = []

  omit(...properties) {
    this.omit.push(…properties)
  }

  execute() {
    if (this.omit.length > 0) {
      this.runAfter(result => {
        for (const res of Array.isArray(result) ? result : [result]) {
          for (const key of this.omit) {
            delete res[key]
          }
        }
        return result
      })
    }
    return super.execute()
  }
}

class Model extends objection.Model {
  static QueryBuilder = QueryBuilder
}


iTwin header

Add iTwin images to header and favicon

Fix stray comma in rush.json

TODO: Replace pngs with svgs when they are available


Better fix for Dash.js 2.4 event naming change

Putting "magic strings" for event name is prone to failure when such a name change happens again. A better way to fix this problem, since the constant variable name is the same, only the value changed, is to get its value on run-time. The value of this constant is accessible in window.dashjs.MediaPlayer.events, by extracting this the correct event name for the page-included Dash.js version could be obtained.

We won't need 2 fixed Dash.js 2.4 lines though. (The previous fix already appended it to CHANGELOG) 👍


Login/SignUp Backend error

During Registration Error is happening:

Tasks I would like to work on

Implemented user authentication using Node.js and JWT (JSON Web Token).
Provided secure login and signup functionality.
Token-based authentication for managing user sessions.

@soham0005 I would like to work on this issue

Hello @eshaalal , the issue raised by issue is already implemented and will get merged today. Please do consider raising another issue or contributing to other issues. Happy Coding!!


Substitute jQuery.param function

This removes the only jQuery dependency from the addon.
The reason why the function is bundled is the current relatively poor NPM module story in Ember addons. Hopefully this could be solved soon by importing from jquery-param directly.

Why can't we just use this package now? 🤔

Honestly, I tried to get that NPM package working for like 15 minutes and gave up. That's pretty much the amount of time I'm willing to spend on using a 3rd party library. I'm happy to work on anything else related to the addon code, but it just felt wrong to spend this much time on a task that should be a trivial 2-liner :(

I fully understand you But I can accept it in that form :/ Its giving us another file and logic to support, watch changes and have tests for that. I will try to import the package to get rid of it.
But thanks a lot for the idea :)

Sure, no problem. Sorry that I can't take this further :(


Adding timezone conversion function in utils

This PR is focused on localizing data to a specific area's timezone, rather than UTC time, for applications that require hourly granularity and specific local time ranges (i.e. heating degree days of a specific area).
To test: Message me for a copy of a Jupyter Notebook that runs creates sampled data and runs the utils function on the given dataset to convert it to the local timezone.

Will need to include timezonefinder in Docker image for future usage.

Will need to include timezonefinder in Docker image for future usage.

timezonefinder            6.0.2              pyhd8ed1ab_0    conda-forge
Looks like it is already on board the HUB image...

Could we just make it simple on us and use a UTC offset parameter instead of the location info? Seems like the end user would know which timezone they would be working in?

Tested in the tester notebook provided, and on the hub. A few things:
Tester notebook: It appears that there still might be some 'too early' slicing of data with the timezone conversion, in that the last few hours in the converted data are not present (see screenshot)
Hub with WRF area-averaged gridded data, not station data: This at present doesn't work because the CFTimeIndex requires cftime.datetime objects, and the WRF gridded date has numpy.datetime64. I think there should be some sort of if/else statement in the function that identifies based on the input selections whether it's station data --> use CFtime.datetime index; or gridded data --> process with numpy.datetime64 index

2 of the timezone sensitive functions (+ renewables once it's online) will use the gridded WRF data (TMY, heat index), and 1 uses station (degree days), so definitely needs to be flexible for both options!

Did you use any specific selections to get the adj_data? Or just the ones used in the notebook?
Thanks for testing the WRF data and the station data, I can definitely add this conditional in the function.

Could we just make it simple on us and use a UTC offset parameter instead of the location info? Seems like the end user would know which timezone they would be working in?

This would be an easy solution, but needs to be aware of daylight savings, in terms of whether it's UTC-8 or UTC-7 (for CA). Especially since some states in our domain don't abide by DS.

I did some fiddling in a separate branch trying to deal with datetime64 from gridded data but ran into issues at the end of the code.
I am working on integrating timezonefinder into the testing conda environment so the tests won't fail. I'm starting from scratch though as I lost the file I used to generate the lock file when a hard drive failed...

Noticing this now on both the station data load and the convert_to_local_time load (likely because it's grabbing additional data):
srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/coding/times.py:360: FutureWarning: Index.ravel returning ndarray is deprecated; in a future version this will return a view on self.
  sample = dates.ravel()[0]
/home/jovyan/src/climakitae/climakitae/core/data_load.py:957: RuntimeWarning: Converting a CFTimeIndex with dates from a non-standard calendar, 'noleap', to a pandas.DatetimeIndex, which uses dates from the standard calendar.  This may lead to subtle errors in operations that depend on the length of time between dates.
  da_adj["time"] = da_adj.indexes["time"].to_datetimeindex()

 timezone conversion functionality for calcs that must be timezone aware in climakitae and notebooks


Problem with model

I have problem with model of network when I use your instruction:
ValueError: Error when checking target: expected flatten_1 to have shape (None, 1749) but got array with shape (162, 1)
I would be grateful you for help

what version of tensorflow and keras do you have installed? There might be some issues with api changes in the newer versions. I am looking at updating this but did not yet find the time to do it.

I've installed keras 2.0.8 and tensorflow 1.3.0.  Which version do you have?

I have just tested against the latest keras (and added a tf version) but i did not encounter this error. Do you have that error in training? In that case it is just a normal classifier make sure your y vector has the right shape (compare with my concrete example if necessary).

Thanks to you data I've found error in my training.Thank you so much


Dynamic Tabs Issue

I'm having an issue when adding tabs dynamically. The new tabs seem to be added vertically and upon resizing the width of the window they jump into place horizontally and everything works as expected.
Any chance you could take a look for me and point me in the right direction. Created a plunker here http://plnkr.co/edit/IkkXut?p=preview
Thanks

Funny, just minutes ago, based on another request, I checked in an update that handles dynamically-added tabs. I forked your plunk with the latest code:
http://plnkr.co/edit/2WnUV5l2cMqiGUr4Olyt?p=preview
To make it work, you need to add a watch-tab attribute to the scrolling-tabs-wrapper directive element.
The update was mostly for using AngularUI tabset but it also works if you're wrapping regular Bootstrap tabs, provided that each new tab you add dynamically is not going to default to be the active tab. I'm still working on making it work for that scenario. But it looks like it's working for yours since you're not defaulting the new tabs to active.
Let me know if you have any problems.
Mike

Just dropped it into my project and the changes work brilliantly.
Thanks for such a quick response :+1:

Latest commit (v0.0.12) provides a more complete solution for this. Dynamically added tabs are now supported by both the scrolling-tabs and scrolling-tabs-wrapper directives. And they both handle the newly-added tab being the active tab.


Add Stable Diffusion examples on GPU and CPU

Add Stable Diffusion examples on GPU and CPU

add one generated picture?

add one generated picture?

Add figure generated by sdxl-base-1.0


Perfetto reader + Omnitrace Perfetto Trace Support

Closes #471
Provides GraphFrame.from_omnitrace for Omnitrace perfetto traces
Provides PerfettoReader

Named as such (instead of OmnitraceReader) because it is a generalized implementation for handling perfetto traces. There is basically nothing that is specific to Omnitrace in it's implementation

Added util/readers.py

Provides a graphframe_indexing_helper function that simplifies / streamlines the last stages before creating a Graphframe instance

Efficient reusable implementation for indexing with a multi-index

Added several omnitrace perfetto traces
Added several tests for the above traces (more to come)

Aside from my plans to add a few more tests and documentation/comments, this is basically ready to go. I had 3 feature requests this week for Omnitrace where this sort of capability was a core component so I would greatly appreciate prioritizing this.

Regarding the test data, I am assuming those are five different traces. Is it possible to have smaller or fewer traces? We try to keep the bloat in the repo to a minimum as much as possible.

Regarding the test data, I am assuming those are five different traces. Is it possible to have smaller or fewer traces? We try to keep the bloat in the repo to a minimum as much as possible.

Yes and no. The MPI ones are similar and it comes from the two modes for perfetto: in-process and system. For in-process mode, we output one file per rank. In system mode, we start a daemon and all the ranks report to it and the daemon eventually writes a file with all the ranks in one file.
I'll see what I can do. Is there a combined size you want me to target?


GET doesn't work with request body

I am using springdoc-openapi version 1.5.9 and have a GET method in my controller with a request body. The endpoint works completly fine with postman but with Swagger UI, it gives 'TypeError : Failed to execute fetch on Window.Request with GET/HEAD method cannot have body'.
Expected behavior:
GET with request body should be allowed
The PR to support this expectation : https://github.com/OAI/OpenAPI-Specification/pull/2117

Apparently its a Swagger UI issue.


Short array syntax

@MathiasReker Sorry but I must close this pull request. It doesn't bring any value in fixing a bug or implementing a feature.


Use the TextEditor in Identify

Use the TextEditor For comments and IDs like we do on obs detail.

I can take a look at this if you didn't already have a plan of action @kueda. Do you think it makes more sense to get this in "Identify" first or approach #2721, #2722, and #2724 first?

They all kind of complicate each other equally, so if you want to take a crack at this, go for it. Much obliged.


FileValidator checkExtensionByMimeType wrong message

Just had to step thru to find why was getting message that extension wasn't allowed when it was. Turned out the file was Mime type image/gif for a .bmp extensioned file.
Message should have said something like "Extension .bmp does not match mime type image.gif".
Issue is that validateExtension performs the check for valid extensions and for mime type to extension match, however it only has the one message when returning false which is that extension isn't allowed - hence confusing to a user and is wrong message.
Have turned off checkExtensionByMimeType for now.

I think there is not an error message for the case you mention. The message $wrongMimeType is used when the property $mimeTypes is set with a list of allowed mime types, not to match the file extension and mime type.
How about a new error message $notMatchMimeTypeAndExtension ? as usual the names I propose are bloby.

Yip, the new message sounds fine. Wasn't proposing any solution, was just hiliting the problem.

@andrewblake1 no prob, you can still make an opinion about how to name the new error message, i will make the PR.

Naming of the new message as you have suggested sounds good.

May be better auto turn off checkExtensionByMimeType if empty($mimeTypes) ? Then you get $wrongMimeType message.
Why it checks twice now?

Extension .bmp does not match mime type image.gif

This kind of error is useless because:

The average user will not understand what's going on
Extension is a lie (probably). That's why we do not trust extensions by default and force mime-type checking.

Issue is that validateExtension performs the check for valid extensions and for mime type to extension match, however it only has the one message when returning false which is that extension isn't allowed - hence confusing to a user and is wrong message.

As a result of point 2, mime-type checking is safer. But it's not convenient enough, because usually we know the extensions we want to allow, but don't know representative mime-types.
Assuming there is a simple way to get mime-type for the extension, we give a simple way to declare allowed mime-types through extensions.
In case you want to rely on extensions only, set property checkExtensionByMimeType to false.
Current behavior is just correct, no changes required, as for me.

Current behaviour caused confusion for my tester due to a wrongly named file which does happen in the real world. This resulted in having to step thru to find out what was wrong. When this system goes live, we will receive support calls. This is not the first time I have come across files with incorrect extensions and won't be the last. It is of course a rare situation, and my debate would be that although the message suggested as a solution might not be understood by an average user, it is clearer  and more accurate than the alternative which is just plain inaccurate.
I.e. the extension was allowed - that is image.bmp. The user was left with no idea how to resolve the issue by the error message, fortunately we were only testing. I still don't even know how we ended up with the misnamed file - but have seen it happen before.
If this is closed then I will continue to use my extended FileValidator class that is dealing with this but I think one day someone will come across this and raise it again.

The user was left with no idea how to resolve the issue by the error message

I agree, that more specific error message is better.

I had the same issue, and here is my solution:

first check default extention,
second check mime type and write another error message.

public function rules()
{
    return [
        [['file'], 'file', 'extensions' => 'png, jpg, jpeg', 'checkExtensionByMimeType' => false],
        [['file'], 'file', 'extensions' => 'png, jpg, jpeg', 'wrongExtension' => Yii::t('app', "It seems that your file corrupted, try re-save this file with another name and upload again.")],
    ];
}

Maybe it's help someone.
Sorry if this off-top
p.s. but if we create in validator new error message when extension of file try validate by MIME type, which we can rewrite (when use validator), it would be great.
Then my solution can be shown like this:

public function rules()
{
    return [
        [['file'], 'file', 'extensions' => 'png, jpg, jpeg', 'wrongExtensionsByMimeType' => Yii::t('app', "It seems that your file corrupted, try re-save this file with another name and upload again.")],
    ];
}

and default message of wrongExtensionsByMimeType in validator can be something like: Yii::t('yii', 'File extension and its MIME type is different.');


Sync but black screen

Hi
I aquired this board from videogameperfection.com
I have followed the info on https://youtu.be/oo_gWjK-gGw
I also have the OSSC, it shows sync on YPbr, 316-p, 31.21kHz 98.77Hz
But the screen remains black.
My C64 Board is 250407 Rev B and my VIC chip is MOS 6569r1
I notice is that the VIC is not seated very firmly in the roundholed adapter from this kit.
What can be done with this?
I have shorted the JPLUM1 bridge as described in the Wiki (allthough I had applied power once before I did this...is that very bad?)
So I am a little stuck and don't know what to test next.
Any ideas is very welcome!
thanks
brg,
Magnus AKA Magazaki

Update: it's a bad connection issue on the VIC and adapter board. I just got it working by pushing it down gently while powered!
Any tips on how to get the flat VIC pins to make a good connection in the round holed adapter socket would be much appreciated 😀

Brute force was the answer to my socket contact issue. I guess I am just not familiar with machined sockets

This was actually one of my favourite issue threads. Raising the problem, working through the solution and closing the issue in 2 hours all by yourself  ;-)


Support UTF-8 in TextEdit and LineEdit navigation

This allows jumps over whole non ASCII words with Ctrl+Left/Right in
a LineEdit or TextEdit.
Fixes #25681

But this is !is_symbol. is_symbol has c != '_'.

Thanks!

Cherry-picked for 3.1.2.


Added git functionality to get line numbers and POST request to send git data

Added git functionality to get line numbers of each file.
Added function to send git data to an endpoint after auth has passed and there is a valid idToken for the firebase auth user.

[x] Does the PR description accurately reflect the changes made?
[x] Do the commit messages accurately reflect the changes made?
[x] Is the changelist for this pull request under ~200 lines? (Excepting automatically generated code and package installations)
[x] Does the code follow the coding style guidelines that we have set up?
[ ] Does the coder include unit tests for his functions?
[ ] Does the QA who reviews the code include his unit tests for all the functions?
[x] Is there a documentation in place if the functions is related to how users build, test, interact with, or release code?

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

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


Bind error when trying to create the db while starting a new WordPress site

Describe the bug
I wanted to give ddev a try. When I tried to spin up a new WordPress site like described in the WordPress quickstart the creation of the database returns an error Cannot create container for service db: invalid mount config for type "bind": bind source path does not exist
To Reproduce
Steps to reproduce the behavior:

I've downloaded https://wordpress.org/wordpress-4.9.9.zip
Created a folder wptest in ~/sites
Unpacked the archive within wptest
Ran ddev init with the suggested defaults
Ran ddev start

Expected behavior
I would have expected that ddev would have been able to start in the basic setup
Screenshots
When i've started the first time the output looked like that:
https://gist.github.com/rpkoller/a4b080b4d60e011e8e99e01af793cb35
Afterwards I've removed the project:
https://gist.github.com/rpkoller/cd193380ed1d9197b0caa320a662affb
and restarted:
https://gist.github.com/rpkoller/04fa808994422711968ee2ecdcd19283
Version and configuration information (please complete the following information):

Host computer OS and Version:  macOS High Sierra (10.13.6)
Docker version information (use docker version) and insert it here:

 Version:           18.09.0
 API version:       1.39
 Go version:        go1.10.4
 Git commit:        4d60db4
 Built:             Wed Nov  7 00:47:43 2018
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.0
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.4
  Git commit:       4d60db4
  Built:            Wed Nov  7 00:55:00 2018
  OS/Arch:          linux/amd64
  Experimental:     true

ddev version information (use ddev version)

cli           	v1.5.0
commit        	v1.5.0
db            	drud/ddev-dbserver:v1.5.0-10.2
dba           	drud/phpmyadmin:v1.5.0
ddev-ssh-agent	drud/ddev-ssh-agent:v1.5.0
docker        	18.09.0
docker-compose	1.23.2
domain        	ddev.local
router        	drud/ddev-router:v1.5.0
web           	drud/ddev-webserver:v1.5.0

config.yaml contents for the misbehaving project

name: wptest
type: wordpress
docroot: ""
php_version: "7.1"
webserver_type: nginx-fpm
router_http_port: "80"
router_https_port: "443"
xdebug_enabled: false
additional_hostnames: []
additional_fqdns: []
mariadb_version: "10.2"
webcache_enabled: false
provider: default

Do you have any custom configuration (nginx, php, mysql) in the .ddev folder? If so, have you tried without them? I've used no custom configuration

Additional context
In the Docker settings the path /Users/myuser/Sites is set in the file sharing tab. Technically the binding should be possible within that directory. :/

I think if you'll just share /Users (which is shared by default) or reset your docker to factory settings you'll have it working.
It appears that you have it as "Sites" in the docker share and as "sites" in your filesystem. You and I know that they're the same on a case-insensitive macOS filesystem, but Docker doesn't know that. Could you just share /Users and see how it goes?

@rfay Yep you are right. Turns out resetting the factory settings, the file sharing settings in particular did the trick. But that way Docker is monitoring the whole Users folder, a scenario I tried to prevent before. :/ Because that caused a high cpu load and the fans spinning steadily when using docker e.g. with ddev, when i tried evaluate with a Drupal instance  a few months ago. Think I have to dig a bit deeper, into the naming thing you mentioned, and also observe how Docker is acting nowadays with the new version as well as the latest ddev version. Back then it was hardly usable on my computer. :/ But will revisit and play around a bit. Anyway ddev start works now as expected and I know now for the future. Thanks! Will play around with ddev running WordPress and Drupal now a bit again. Thanks again for the fast help and have relaxed holidays!


Include tests in PyPI tarball

Hi! Thanks for you PR.
Why should we include the tests in the PyPI tarball?

They are useful for downstream distributions to test if the package works correctly with their build recipe. Also, they provide a way to test if the dependencies as they are packaged by the distribution are compatible.

Thank you for explaining. I followed up on that and learned that this is common best practice. As there is another PR, I will close this one and the other PR to include the test in the source dist.


Add support for several /sys/class/sas_* classes

This adds support for several SAS classes from /sys/class:

sas_host
sas_device
sas_end_device
sas_expander
sas_phy
sas_port

These are for issue #452, which is needed for https://github.com/prometheus/node_exporter/issues/2386.  Once that is complete, it'll be possible to track SAS communication errors on each individual SAS link in a system, and then map those links to specific block devices.
Use case: I recently discovered that I had a bad SAS cable in my system and was seeing weird, intermittent disk timeouts and errors which caused ZFS problems.  Being able to track SAS issues for each node should make detecting and debugging this sort of problem much easier.

Some minor comments but LGTM in general. Thanks!

I started writing my node_exporter code, and found a couple bugs, which I just fixed.  There are also a couple convenience functions that should really be in here.  I may or may not have time for them today.

Okay, that ended up being bigger than expected.  OTOH, the node_exporter code shrank quite a bit, especially the bits where it has to chain through multiple classes to find some random bit of data.  Let me know if there's a different pattern that you'd like to see or if there are any other changes that you'd suggest.  Thanks.

@SuperQ any chance this could get a review?


Migrations overhaul

Main changes:

Moved init containers needing to run once at startup to movable helper template
Added value: initContainers.mainHandler="web" # valid values are "web" "job" or "workflow" which decides which handler should have the DB initialization init containers
Added value initContainers.createDatabase=true which will create the DB on the first run and also run migrations at each startup (to ensure that upgrading the image is still enough to perform an upgrade). If set to false, the DB will be expected to have been initialized and only migrations will be run
Only the main container will wait on the DB directly, the rest of the containers wait for the DB initialization signal in the shared filesystem.
~All handler pods don't have a waiting init container anymore, they simply wait in the main container. This is slightly faster than waiting in init containers, but we can still move them to init containers if we don't mind the extra few seconds and want main container probes to be cleaner~
All handlers have an init container waiting for the signal on the shared filesystem, and only the main container does the init mounts and init DB. This seems cleaner than having a wait in the main container and a few seconds are really not that important to save right now. I made this init container use the galaxy image to keep it pulled as early as possible
There still seems to be a race condition caused by multiple handlers coming up at once (the DB would get locked and become unresponsive when job and workflow handler would come up exactly at the same time), but as of 21.01 the create_db.sh was solved in https://github.com/galaxyproject/galaxy/pull/11753 so we can now bypass migrations. It's not an ideal solution, but to avoid the race condition as a stop gap, I just scattered the startups by 10 seconds. After the DB init signal is given, web handler will start right away, job handler will wait 10 seconds, and workflow handler will wait 20 seconds. This is enough to seemingly reliably avoid the race condition while keeping overhead minimal. This should only be temporary though.

What this accomplishes:

No more handler restarts
DB created much faster when migrations are not needed
DB init containers can be moved to any handler

Updated version highlights:

DB creation/migrations, and init mounts (copying config/galaxy-lib tools etc...) are now run in a k8s job independent of any handler
Handlers have init containers waiting for both the db to be initialized and the init mounts to be done
Adds *handlers.startupDelay values, used to slightly scatter handlers
Main accomplishments:

Eliminates the crashbackloop on handlers
Creates DB from scratch on first startup (faster), and only runs migrations on upgrades

Considerations:

Why job vs init container?
Having the migrations happen independently from handlers seems both conceptually better and is a more extensible implementation. Main benefit that I thought of for using jobs vs init containers:

Any handler can now scale without duplicating migration scripts
This allows to easily "pre-create" Galaxy instances that can be simply spun up. Essentially running with replicaCount=0 on all handlers is an out-of-the box way of preparing the database and shared filesystem for an upcoming Galaxy that can then just be scaled up

Why not use helm hooks?
TLDR: pre- hooks don't work because the init db script needs postgres to be deployed, post- hooks don't work when using --wait because they don't come up until the command returns, but the command can't return until handlers are up which wait for the hook jobs, hence a recursive wait (and we need --wait for Leo in AnVIL).
Solution: Init job and lock filenames per Helm release, but deployed as normal jobs


PSP migration.

Partial rework. Better language. Requires completion and a note about AppVia.

Thanks @flavio. I will merge.


catch and display disk usage issue in wis2box-api

While debugging and supporting users I have noted that a lack of disk space results in the error:
elasticsearch.exceptions.TransportError: TransportError(429, 'cluster_block_exception', 'index [stations] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];')
which is raised inside the wis2box-api container.
This issue often goes unnoticed as the status of the wis2box-containers does not change and the error is not displayed in the Grafana Dashboard.
We should display this issue in the main Grafana dashboard and document it in the FAQ

2024-07-24:

@maaikelimper to check w/ @alimand on status/updates

wis2box silently failing due the disk usage issue resulted in 5 days of data loss in the CMO-server, so I'm raising the priority of this issue.
I think instead of just displaying the disk usage issue we should consider disabling the wis2box as a whole when we detect that Elasticsearch stops functioning.

2024-08-14:

PR in #721 (needs to resolve conflicts)
needs deploy/test/validate

Thanks for checking and now there is no conflicts with main branch

I've tested and reviewed the fix for and merged this in https://github.com/wmo-im/wis2box/pull/729
This fix adds a new panel to Grafana to display alerts and includes a new alert triggered by the elasticsearch-exporter.


feat(jwt) support for config.key_claim_name in header

Addresses the issue discussed in #2858.
Context
The JWT plug-in previously only supported setting the config.key_claim_name parameter to a claim in the body and not the header. Many identity providers who use JWKS (such as Amazon Cognito) support signing their tokens with more than one public key. This results in the need to support the "kid" (key ID) claim which identifies the public key required to validate the signature of the token. Due to the JWKS defining multiple public keys, the standard "iss" (issuer) claim is not unique. The "kid" claim is typically set in the header of the token and therefore requires also checking the token header for claims. The change that was made is fully backwards compatible due to keeping the functionality that checks the token body claims first and if the config.key_claim_name is not found there it then checks the header. An additional test case was also written to confirm that setting config.key_claim_name to a claim that is in the header succeeds.
Solution
The current release of the JWT plugin only checks the token body (claims) for the config.key_claim_name parameter. While this works for most scenarios, in the aforementioned scenario of the "kid" claim in the header, this does not suffice. Adding an additional check against the header of the token if the config.key_claim_name parameter isn't found in the body resolves this issue.
After making this change, an IdP that uses more than one public key can be configured for a single consumer as follows -
# Configure the plugin and ensure config.key_claim_name is set to the appropriate header claim -
curl -X POST http://localhost:8001/apis/myapi/plugins --data "name=jwt" --data "config.claims_to_verify=exp" --data "config.key_claim_name=kid"

# Configure the FIRST public key for the consumer. Each of the parameters in curly braces should be replaced to fit your scenario -
curl -i -X POST http://localhost:8001/consumers/{MY_CONSUMER}/jwt -F "algorithm=RS256" -F<EMAIL_ADDRESS>-F "key={MY_FIRST_PUBLIC_KEY_KID}"

# Configure the SECOND public key for the consumer. Each of the parameters in curly braces should be replaced to fit your scenario -
curl -i -X POST http://localhost:8001/consumers/{MY_CONSUMER}/jwt -F "algorithm=RS256" -F<EMAIL_ADDRESS>-F "key={MY_SECOND_PUBLIC_KEY_KID}"

See also
JWKS standard: https://tools.ietf.org/html/rfc7517#section-5
Related issue: https://github.com/Kong/kong/issues/2858

I like option 2. It should be fully backwards compatible assuming people don’t have existing claims using that exact format. I’ll get this changed up today.

Rebased and merged with the necessary modifications, thank you for the patch!


'Show More' popup on AWS details - expanded table item has no page title

Describe the bug
'Show More' popup on AWS details - expanded table item has no page title
To Reproduce
Steps to reproduce the behavior:

Go to AWS details
Click on arrow to expand an account
Click on 'Show More' button
See popup has no title or any information on what its showing you

Expected behavior
Popup should have a title
Screenshots

Desktop (please complete the following information):

OS: Fedora
Browser Chrome
Version 66

Additional context
Testing against CI insightsbeta

I'm not able to reproduce with insights beta.

Looking at when this was opened, I suspect you were testing while I was updating items on this page? If this is still an issue, feel free to reopen. However, the modal definitely has a title.


Add setting for custom ffz mod/VIP badges

Pull request checklist:

[X] CHANGELOG.md was updated, if applicable

Description
Adds a toggle setting that allows disabling using the custom FFZ moderator and VIP badges.
Currently implemented as one setting for both, to avoid more settings, and is enabled by default.
Currently not sure about:

The location of the setting in the menu and in the settings file.
Other badge settings update old messages when changed, for example disabling the Chatterino badge setting will remove that badge from already existing messages in chat. However, due to how the current implementation works, this setting doesn't update on old messages, and will only change whether or not the custom badges are used for new messages. Not sure if this is a problem, and if it's worth the effort to make this work when, to my knowledge, there isn't a simple solution that doesn't change the original implementation.

Closes #2693

In the long run a dropdown with a string value won't make sense so it's more worth keeping the settings as 'single values', even though it will add a bit more clutter now it can be cleaned up the future if another value were to be added. tl;dr: 2 checkboxes > 1 dropdown menu imo. Setting scope is fine, setting position we've chatted about but it can be added after a separator in the "Visible badges" category


SHACL - support shape constraints that validate targets and not paths

Example:
ex:MyShape
	a sh:NodeShape ;
	sh:targetNode "hello" ;
	sh:datatype xsd:string .

don't forget to support as part of nested sh:pr


Command to create, list, show, update, and delete mapping rules

Lower level command for mapping rules management

When creating mapping rules, create method (maybe triggered by optional parameter)


Implement more fine grained tagging in prometheus metrics

Describe the feature you would like and why you want it
Add additional tags to prometheus check value metrics:
https://github.com/Comcast/kuberhealthy/blob/6dab3697e6626f1e76f3e3a2f3e4941524046f80/pkg/metrics/exporter.go#L40
e.g. check=$checkname,namespace=$namespace for additional grainularity.
Additional context
We're feeding these into DataDog such as:  https://photos.app.goo.gl/4o989E9uvSWkoVmd6
It would be excellent if we had per check/namespace tuples that we could filter on and use in alerts if a check value drops below 1.

@ihoegen did the Prometheus integration. He is off in Mexico on a honeymoon right now though...  I assigned him to this one.

The replace is there because for a little bit the name of the metric was the name of the check, and spaces made things tricky. Now it's just leftover code I could remove. I'll update it to parse that when I get back on Monday

Right, but we don't want to remove the fidelity were getting there since
the podstatuscheck can execute for N namespaces same as the podhealthcheck
Right?  Just create a tuple of tags {check=type,namespace=namespace}
On Thu, Jul 19, 2018 at 1:10 PM, Ian Hoegen<EMAIL_ADDRESS>wrote:

The replace is there because for a little bit the name of the metric was
the name of the check, and spaces made things tricky. Now it's just
leftover code I could remove. I'll update it to parse that when I get back
on Monday
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Comcast/kuberhealthy/issues/43#issuecomment-406349313,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AiRB9jPxGVHLJK8E2eUMGxncAv9i8Koqks5uIL2fgaJpZM4VWfxc
.

Yeah that makes sense. I'll remove the parsing of the spaces, and use the namespace field from the check object to populate that tuple

#56 addresses this


KDE not Booting and login not fullscreen

First of all: I really love this project. It is hilarious!
However, i do have issues with selecting KDE:
When i boot up my machine, it shows plasma as DE. If i log in, everything works. However, if i click on the button to switch the DE to i3 and then fully turn off the machine, i3 is still selected. If i then click on the toggle again to get back to KDE, i only get the option Plasma (X11). Curiously, if i pick this option and log in, i only get a black screen.
Only way to resolve this was to remove osrs as web-greeter theme, choose dracula, reboot and then choose osrs again.
Additionally, the login window is not fullscreen for me but rather a small-ish window in the middle with the rest being black.
I am on a fresh install of EndeavorOS and closely followd the steps in the readme.
The dracula theme works flawless for me.

I 2nd this issue. Fresh arch install the login window is there but loging in just gives a black screen, login is also not fullscreen. Above workaround works for me as well

Thanks for the thorough bug report. I’ve been able to recreate your reported behaviour. This is a problem with the codebase. Currently, a LightDMSession.name instead of a LightDMSession.key is being used when launching the desktop session. This only impacts some DEs/WMs, such as Plasma. An attempted quick fix led to some side effects. I hope I will have a stable fix pushed in the next couple of days.
With respect to not being fullscreen, this is by design to mimic the actual Old School RuneScape login which has fixed asset sizes and a black border. However, on HDPI screens this currently may lead to an exaggerated smallness which is undesirable. I’ll create a separate feature request for this. Currently I can’t put a timeframe on when I’ll be able to work on this feature, but please feel free to have a try yourself and make a PR too.

Thank you for your quick response and the amount of effort you are putting in this project!
What is the best way to update this on my machine? Full uninstall and then reinstall?
That might be something to add to the readme as well.

No worries! Thanks for checking it out, I've had a lot of fun making this! I have merged a fix for the plasma issue into the main branch. It's been tested on a machine running Arch with bspwm and sowm, as well as a machine running KDE Neon with Plasma (X11) and Plasma (Wayland). Hopefully this means it will work for you too now.
If you still have the git repository cloned locally you can just do the following to upgrade
cd <path to local osrs-web-greeter-theme git repository>
npm install
sudo npm run build

Otherwise, just follow the 'Installation' steps in the README again. Editing /etc/lightdm/web-greeter.yml is only required, if you are currently not using the osrs theme.


Cannot get storage-blob library to work in Angular 7 application using IE 11

Azure Storage Blob client library for JavaScript

12.1.2

Windows 10

[ ] browser

name/version:  IE 11

[ ] typescript

version: 3.1.1

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

I do not think this is a bug, but I would appreciate some assistance. I am using this package in an Angular 7 application and it works with all browsers except for IE 11; the only IE version that I need to support. I get this error:
Script1002: Syntax error
vendor.js (145800,1)
At that line in vendor.js is this:
class AzureKeyCredential {
I have run into a similar problem in the past and I had to use polyfills to fix it, but this time I have added all the polyfills and I still get the problem. Below is a copy of my polyfills.ts file. I also tried adding all the core-js\es7 polyfills and it did not help. Any assistance would be appreciated.
/**

This file includes polyfills needed by Angular and is loaded before the app.
You can add your own extra polyfills to this file.

This file is divided into 2 sections:

Browser polyfills. These are applied before loading ZoneJS and are sorted by browsers.

Application imports. Files imported after ZoneJS that should be loaded before your main

 file.

The current setup is for so-called "evergreen" browsers; the last versions of browsers that
automatically update themselves. This includes Safari >= 10, Chrome >= 55 (including Opera),
Edge >= 13 on the desktop, and iOS 10 and Chrome on mobile.

Learn more in https://angular.io/guide/browser-support
*/

/***************************************************************************************************

BROWSER POLYFILLS
*/

/** IE9, IE10 and IE11 requires all of the following polyfills. **/
import 'core-js/es6/symbol';
import 'core-js/es6/object';
import 'core-js/es6/function';
import 'core-js/es6/parse-int';
import 'core-js/es6/parse-float';
import 'core-js/es6/number';
import 'core-js/es6/math';
import 'core-js/es6/string';
import 'core-js/es6/date';
import 'core-js/es6/array';
import 'core-js/es6/regexp';
import 'core-js/es6/map';
import 'core-js/es6/weak-map';
import 'core-js/es6/set';
/**

If the application will be indexed by Google Search, the following is required.
Googlebot uses a renderer based on Chrome 41.
https://developers.google.com/search/docs/guides/rendering
**/
import 'core-js/es6/array';
import 'core-js/es7/array';

/** IE10 and IE11 requires the following for NgClass support on SVG elements */
import 'classlist.js';  // Run npm install --save classlist.js.
/** IE10 and IE11 requires the following for the Reflect API. */
import 'core-js/es6/reflect';
/**

Web Animations @angular/platform-browser/animations
Only required if AnimationBuilder is used within the application and using IE/Edge or Safari.
Standard animation support in Angular DOES NOT require any polyfills (as of Angular 6.0).
**/
// import 'web-animations-js';  // Run npm install --save web-animations-js.

/**

By default, zone.js will patch all possible macroTask and DomEvents
user can disable parts of macroTask/DomEvents patch by setting following flags
*/

// (window as any).__Zone_disable_requestAnimationFrame = true; // disable patch requestAnimationFrame
// (window as any).__Zone_disable_on_property = true; // disable patch onProperty such as onclick
// (window as any).__zone_symbol__BLACK_LISTED_EVENTS = ['scroll', 'mousemove']; // disable patch specified eventNames
/*

in IE/Edge developer tools, the addEventListener will also be wrapped by zone.js
with the following flag, it will bypass zone.js patch for IE/Edge
*/
// (window as any).__Zone_enable_cross_context_check = true;

/***************************************************************************************************

Zone JS is required by default for Angular itself.
*/
import 'zone.js/dist/zone';  // Included with Angular CLI.

/***************************************************************************************************

APPLICATION IMPORTS
*/

Unfortunately class is not supported in IE11.  Two dependencies of the storage library use them: @azure/core-auth and @opentelemetry/api and we don't have control over the latter.
We have some guide to work around this when bundling: https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/storage/storage-blob/README.md#special-bundling-notes-for-ie11. Could you please have a look?  Does Angular run a particular bundler behind the scenes?

Another question: is there a browserslist file where you can enable the support for IE?

I have previously taken the steps to make my app work in IE 11. I also use the MSAL library which requires steps to make it run in IE 11. I believe the bundler in Angular is webpack.
Here is my browserslist:
"broswerslist" : [
"last 2 versions",
"not ie <= 10",
"not is_mob <= 10",
"IE 11"
],
And here are my compiler options to produce ES5:
{
"compileOnSave": false,
"compilerOptions": {
"baseUrl": "./",
"outDir": "./dist/out-tsc",
"sourceMap": true,
"declaration": false,
"module": "es2015",
"moduleResolution": "node",
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"target": "es5",
"typeRoots": [
"node_modules/@types"
],
"lib": [
"es2018",
"esnext.asynciterable",
"dom"
]
}
}

I am confused. Angular uses class extensively.

I am confused. Angular uses class extensively.

I suspect that when bundling, Angular does not touch vendor libraries by default.  I created a test project that shows how to make storage blob library to work in IE 11 using Webpack + Babel.
https://github.com/jeremymeng/storage-webpack-bundle#use-babel-to-transpile-our-output
Not sure yet how easy it would be to customize Angular to integrate this.

I did some search on the Internet, and @angular-builders/custom-webpack looks a popular one to use. A random link: https://netbasal.com/customize-webpack-configuration-in-your-angular-application-d09683f6bd22

I was looking at the code in the debugger and I noticed that it appears that I am getting modules from the wrong distribution. I should be getting the version from dist not dist-esm. I had a similar problem early on using the storage-blob library, see #7296. You helped me with that one.
//<EMAIL_ADDRESS>/!**********************************************************************!
<EMAIL_ADDRESS>!
********************************************************************/
/! exports provided: AzureKeyCredential /
// (function(module, webpack_exports, webpack_require) {
"use strict";
webpack_require.r(webpack_exports);
/* harmony export (binding) / webpack_require.d(webpack_exports, "AzureKeyCredential", function() { return AzureKeyCredential; });
// Copyright (c) Microsoft Corporation.
// Licensed under the MIT License.
/*

A static-key-based credential that supports updating
the underlying key value.
/
class AzureKeyCredential {
/*

Create an instance of an AzureKeyCredential for use
with a service client.

@param key the initial value of the key to use in authentication
/
constructor(key) {
if (!key) {
throw new Error("key must be a non-empty string");
}
this._key = key;
}
/*
The value of the key to be used in authentication
/
get key() {
return this._key;
}
/*
Change the value of the key.

Updates will take effect upon the next request after
updating the key value.

@param newKey the new key value to be used
*/
update(newKey) {
this._key = newKey;
}
}
//# sourceMappingURL=azureKeyCredential.js.map

/***/ }),

The problem in #7296 was not dist-esm v.s. dist, but because we didn't have a browser replacement for ./dist-esm/src/utils/utils.node.js.
In this case, AzureKeyCredential from<EMAIL_ADDRESS>also has the class keyword because it is not ES5 compatible. Simiar for<EMAIL_ADDRESS>

This information helps a lot. I am wondering if this is similar to the problem that MSAL had at one point. I believe they provided a library compatible with ES5. I don't remember all of the details. I did find this https://github.com/AzureAD/microsoft-authentication-library-for-js/pull/868/files. I will look into the transpiling options. Is it possible for you to provide an ES5/IE11 compatible version of this library like MSAL did?

I remembered some of the details of the problem with MSAL. It would not work with IE 11 so I had to download the source code and added that code to my project to compile it into ES5. A few months later they updated MSAL and I was able to consume their library without any problems with IE 11.  I removed the code and installed the new library using npm.

We have fixed @azure/core-auth, but we don't own @opentelemetry/api though. The issue is tracked at https://github.com/open-telemetry/opentelemetry-js/issues/902

To clarify the fix to @azure/core-auth has not been released yet but will be soon.

@jeremymeng, Now that the fix to @azure/core-auth has been released, what are the next steps here?

We are still blocked by https://github.com/open-telemetry/opentelemetry-js/issues/902. I think it is still useful to have this as a tracking issue.  Not sure how it would impact out issue status reporting though.

Removing the Service Attention label as the pending work here is related to our dependency on Open Telemetry.
Assigning to @xirzec
Either we wait for OT to fix this and then we update our dependency
Or we look for alternative solutions like downlevel compiling the types package

The OpenTelemetry issue was fixed in this PR: https://github.com/open-telemetry/opentelemetry-js/pull/1368
As soon as they publish a release that contains that fix, we can adopt the new version.

That is great news @xirzec!
Another piece of good news is that there doesnt seem to be any breaking changes to deal with from our side when moving to 0.6.1 to the latest 0.10.1. See https://github.com/Azure/azure-sdk-for-js/pull/10393
Assuming the same proves for the next version, it should be a trivial change for us

Re-opening as we still need to release the storage packages with updated dependencies

@ramya-rao-a do we have date for this package release? Really important for our project

I believe the plan is to have a new release of storage libraries later this month.

I think we will need to postpone the release to early September.

@ljian3377 is there a release planned this month still?

new versions of Storage libraries have just been released which should fix this.  Closing.


Support Go Mod?

Cannot use in my GOMOD project

What needs to be done here is simply push the v0 tag of the latest stable commit.

...let me know if you need any help with this.


Upgrade CP4BA to 21.0.2 IF003

Is your feature request related to a problem? Please describe.
The latest release of CP4BA is out, so this repository should be tested with that version for clean install and for upgrades.
Describe the solution you'd like

Upgrade the artifacts in this repository to support both a clean installation of CP4BA 21.0.2 IF003 and upgrade from CP4BA 21.0.2 IF002 to 21.0.2 IF003
Inspect the release notes for potential fixes to workarounds in the repository, then remove unnecessary and/or harmful workarounds.

Describe alternatives you've considered
None, the requirement is pretty narrow.
Additional context
Add any other context or screenshots about the feature request here.

Need to include this change to node configuration: https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/21.0.x?topic=deployment-installing-capabilities-in-operator-hub


The file encoding conversion from UTF16-LE BOM to UTF-8 - to resolve …

…issue  #6

V1.16, 03/12/2015 - Added checks for clients connections statistics per CAS servers

Declining PR as it's merging to master.


remove sending deviceid and uid

Likely the cause of the no tlf name specified errors. if we didn't have the uid or device id (not clear how that happens but lets not figure that out right now) we'd bail out and not send messages. there's no real point in sending this and mike verified we don't actually need to.
@keybase/react-hackers

https://keybase.atlassian.net/browse/DESKTOP-3654


Faster avatar service and cool full body views

@McLive Thanks buddy, but at the moment I don't want work in the master branch at all until we finished our refactor (PR#17). You can find a ongoing discussion about it here, where we also plan to get rid of the client side skin rendering using JavaScript: https://github.com/BanManagement/BanManager-WebUI/issues/16
I'll put this for hold for now, okay?

Oh, didn't know that. :D

Not a problem :)

@McLive I just added a new feature for a configurable skin service: https://github.com/BanManagement/BanManager-WebUI/blob/master/settingsRename.php#L60-L61
Thanks for your PR and sorry for not merging, though.

That's fine :+1:


Authentication Issue

App works well on browser which i used to install, but if i open installed app on other browser/pc it shows me login/install screen.

Similar to another issue... can you please outline the steps you've taken so I can try and reproduce.

1.Install app using this url https://loyaltypoints-new.herokuapp.com/ on shopify store using chrome
2.Open firefox and in your shopify store navigate to app, then any page from menu of app.
Below is the example of route
Route::resource('programDetails', 'ProgramDetailController')->middleware(['auth.shop']);

When you say any page, where do I go?

Program details

@Saadnine15 I think you set a wrong URL for App URL, so you can not login to app.

HI @ohmybrew
Please see this video: https://www.loom.com/share/4786c063f40a40959d7bce0b9ce05922
If possible then please resolve ASPS.
Thank you.

Merging to #244

Hi @ohmybrew
The same issue I faced in version 10.1 https://prnt.sc/pd78hv
Is there any solution? or I have to do some configuration?
Thank You


Design browser database schema

Design a database schema to index the required project and file metadata to support the browser.
Requirements:

Enables querying of projects by assay, organ and species fields
Enables querying of files by assay, organ and species fields
Stores sufficient metadata about projects and files to render Project List and Project Detail pages
Stores sufficient metadata about files to enable download of files

Schema design doc

@calvinnhieu  I quickly reviewed the design doc. I tried to address your open questions. My hope is we can assume 1:1 relationships for file:{organ, species, assay} for now. If not, I'd like to know why and see if we can problem solve.
When you've cleaned up the todos, I suggest that when you sit with @liaprins-czi and confirm that it contains all the information needed for her prototype. If she signs off, consider it reviewed for content.
I leave it to you to determine who should review it on the tech side beyond Marcus.

Great - moving ahead with 1:1 relationships between file:{organ, species, assay} until it's no longer true. Reviewing with @jahilton , @liaprins-czi , @mckinsel and @parthshahva to finalize today.