Monitoring installations

Is it possible to add an option to monitor a new installation that monitors everything that's installed, including reg entries?
It appears that programmes install hidden entries that aren't seen by uninstallers.
Thanks.

Duplicate of https://github.com/Klocman/Bulk-Crap-Uninstaller/issues/258, I'm currently not planning to add this feature because of limited time.


Create PROFILE.md

Why:
Closes [issue link]
What's being changed:

Check off the following:

[ ] For workflow changes, I have verified the Actions workflows function as expected.
[ ] For content changes, I have reviewed the style guide.

Unsubscribe
Pada tanggal Sen, 7 Nov 2022 21.19, TimRutjens @.***>
menulis:

Closed #159 https://github.com/skills/introduction-to-github/pull/159.
—
Reply to this email directly, view it on GitHub
https://github.com/skills/introduction-to-github/pull/159#event-7752552409,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZRBEW4VKSCUDT6TSX4DXXDWHD6UTANCNFSM6AAAAAARZFZ6FM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>


v5 SSR Returning Empty Style Tags

Environment
System:

OS: macOS High Sierra 10.13.4
CPU: (4) x64 Intel(R) Core(TM) i7-6567U CPU @ 3.30GHz
Memory: 254.39 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash

Binaries:

Node: 8.12.0 - ~/.nvm/versions/node/v8.12.0/bin/node
Yarn: 1.6.0 - /usr/local/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v8.12.0/bin/npm
Watchman: 4.7.0 - /usr/local/bin/watchman

npmPackages:

babel-plugin-styled-components: ^1.10.1 => 1.10.1
styled-components: ^5.0.0-beta.3 => 5.0.0-beta.3

Reproduction
Steps to reproduce
Within the context of an Express middleware:
const sheet = new ServerStyleSheet()
const reactTree = (

)

const html = ReactDOMServer.renderToString(reactTree)
const css = sheet.getStyleTags()
const { js } = flushChunks(clientStats, { chunkNames: flushChunkNames() })

res.status(200)
res.render('base', { html, css, js })

Base is just a Handlebars template, but it's not relevant. Can just print out contents of css here.
Within the context of my .babelrc:
"development": {
      "plugins": [
        "react-hot-loader/babel",
        [
          "styled-components",
          {
            "minify": false,
            "ssr": true,
            "displayName": true,
          }
        ]
      ]
    },

Expected Behavior
Style tag (css above) in rendered HTML contains classes.
On server (and client hydration):

Actual Behavior
On Server:

On Client Hydration:

Notes
sheet.getStyleElement() is the same result, a style tag that has dangerouslySetInnerHTML: { _html: '' }

@rtymchyk what version are you upgrading from? you don't need to use StyleSheetManager for SSR.
Should just be:
const sheet = new ServerStyleSheet();
const html = ReactDOMServer.renderToString(
      sheet.collectStyles(
        <Router location={req.url} />
      )
);
const css = sheet.getStyleTags()

@probablyup I am upgrading from 4.2.0. I'll need to rule out the possibility that there may have been an issue in 4.3.0.
As for your second point, the documentation speaks to these 2 APIs as being equivalent for SSR, so I prefer to use the declarative one:

The collectStyles method wraps your element in a provider. Optionally you can use the StyleSheetManager provider directly, instead of this method. Just make sure not to use it on the client-side.

Ok I think I found the issue... there's a backward compat fix that needs to be added because during the refactor the internal variable got renamed for some reason. Will fix.

@probablyup Glad to hear :) I can confirm that the latest v4 is working fine.

Released in https://github.com/styled-components/styled-components/releases/tag/v5.0.0-beta.4

Fix is good. Seeing a server vs. client mismatch on class names, but this looks like a separate issue.

@rtymchyk the mismatches are in dev or prod mode? If it's dev yeah we have a PR in progress to change a few internal behaviors

I'm getting empty style tags in 5.0.0-beta.8, so I had to switch back to 4.3.2.

This is happening on CRA as well. The style tags have content on local development but are empty on deployment.

might this post help?

I'm having the same problem.
This is my code:
`var React = require("react");
const ReactDOMServer = require('react-dom/server');
const { ServerStyleSheet } = require('styled-components');
const { Button }  = require("swirl"); // external component library using styled components
const html = (locals) => {
const sheet = new ServerStyleSheet();
let html = '';
let styleTags = '';
try {
html = ReactDOMServer.renderToString(
sheet.collectStyles(This is a button)
);
styleTags = sheet.getStyleTags();
} catch (error) {
console.error(error)
} finally {
sheet.seal()
}
return html
}
export default html;`
I use StaticSiteGeneratorPlugin from webpack to render this staticly.
The HTML looks just fine:
<button class="sc-bdnxRM bBXhOB" type="button">This is a button</button>
But the variable css is always empty.
I'm not sure what I'm doing wrong. Could someone help me please?


Mldb 1340 access log

added basic request log to MLDB
the logging is disable by default and can be enable with a command line option (enable-access-log)
the logging seems to have a significant impact on the performance - I will investigate that to see if there are low handing fruits

@guyd Je pense que ça veut dire que tu as ton +1!

Oui mais il y a une question qui reste: est-ce que l'on voudrait simplement utiliser la fonctionnalité existante dans nginx?

@jraby what do you think? Should MLDB have its own internal HTTP access-log logging or should we rely exclusively on nginx? Can nginx provide such a log? Can nginx be configured easily to log only certain things without restarting etc?

If you sometime you need access logging outside of docker, you need to keep something builtin to mldb_runner.
For docker use, nginx do the access logs, they can be written to a file or to the syslog socket. The logs can be turned on or off based on the URL,  but changing the configuration requires a reload of nginx.
Reloading nginx shouldn't affect the current http connections,  but only new connections would get logged.

ok, +1 to merge


Upgrade to v0.10.1 in standalone.yaml

I believe this was accidentally left out of 9acb50c916c88975ba8e547f62346ed148fdd287, but it may have been intentional.

Signed. FYI, I'm<EMAIL_ADDRESS>

cc @brendandburns @erictune


eloquent's withCount() not working with multiple db relationships.

I'm using two separate database,DB A holds vendor information and DB B holds products information .I've specified the connection in both models.When I call Vendor::with('products'),everything is working but when I chain withCount('products') it gives me an error,saying table does not exists.Eloquent is looking for products table in DB.A as the vendor's database.
Table 'DB_A.products' doesn't exist (SQL: select vendors.*, (select count(*) from productswheremerchants.id=products.vendor_id) as products_countfromvendors where (shop_slug = 'Some-Slug') limit 1)

Please see #23042.

thanks


feat: testing-library

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/valentingavran/anglify/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Codecov Report

Merging #200 (42dff77) into develop (025a95c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #200   +/-   ##
========================================
  Coverage    53.49%   53.49%
========================================
  Files           94       94
  Lines         1901     1901
  Branches       233      233
========================================
  Hits          1017     1017
  Misses         855      855
  Partials        29       29

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 025a95c...42dff77. Read the comment docs.


Multpile Typos error

Hey @swapnilsparsh,
I found typos in some scripts.
For ex- Typing Platform/script.js - line 7,51...  "timming" should be "timing" + others.
I would like to fix them, Kindly assign this issue to me under GSSOC'24 label and the correct level.
Best Regards,
Nikhil Verma

@NIKHIL0VERMA All the best 👍🏻


Projects: Coordinate Cost Summary with Items in Handle-It Work Item

The Handle-It Work Items with Items listed with costs should show up in the Cost Summary. Totaling Volunteer hours there would be nice along with number of volunteers.

I fixed it so that Cost Summary for projects will show all work items in the "Project Work Items" category. Should be working now in the newest commit.


Fix polygon bounds

Custom version of #3196 without trigonometric functions

OK, your tests helped me, thank you.
Basically,
sinTheta = (y2 - y) / w;
cosTheta = (x2 - x) / w;

atan2 is dividing stuff on "w" then calculating the angle by its sin and cos. But whats the point if we already have them? :)

Also, in that commit I found one interesting thing: now we actually have convention about order of operators, i cant just write
a * b + c * d

Confirmed; https://codepen.io/staff0rd/pen/qaeZjv?editors=0010

Thanks @ivanpopelyshev


feat: Create service account and roles

References #23, #24

ServiceAccount is already created in #19
Create a role and a role-binding for peribolos-as-service ServiceAccount.
I am going to add the serviceAccountName after PR 19 is merged.

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

Needs approval from an approver in each of these files:

OWNERS

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

/hold

/hold
Please don't recreate the PR, rather fix your history and force push. :slightly_smiling_face:
I think a simple git rebase main should do the trick now and you should be left with 3 commits in this PR, then just push --force to this branch

Thanks for the tip! It should be fine now.

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

Needs approval from an approver in each of these files:

OWNERS [tumido]

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

/unhold


Biome Scanner could work better

The Biome Scanner only returns a list of possible biomes and this is very long and not very useful.
However, reading your configuration documentation it seems that certain pressures and temperatures create specific biomes and so the list for a specific planet could be more accurate.
Thanks again for such a fun mod.

It's supposed to return a planet specific list, but it had broken in the 1.10.2 update apparently.
Fixed


Socialfish isn’t recording login credentials

I can’t seem to find a fix for this please help!

I have the same problem.

ohhh just fix the problem its working fine for me.

let me know if you need anyhelp.

Yes please how did you fix the issue???
On Tue, Jun 20, 2023 at 2:14 PM AHMAD EDREES @.***>
wrote:

let me know if you need anyhelp.
—
Reply to this email directly, view it on GitHub
https://github.com/UndeadSec/SocialFish/issues/347#issuecomment-1599367092,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7ALKAP74V2UREUNXXU4XI3XMHZBHANCNFSM6AAAAAAWVOFZNI
.
You are receiving this because you authored the thread.Message ID:
@.***>

could you explain me more ? when you run the project does it run perfectly. i mean when you run the [SocialFish.py] its working you dont get any error ?

This is the error I get now when trying to open SocialFish
Traceback (most recent call last):
File "/home/odin/SocialFish/SocialFish.py", line 6, in
from core.scansf import nScan
File "/home/odin/SocialFish/core/scansf.py", line 1, in
import nmap
ModuleNotFoundError: No module named 'nmap'
I have Nmap installed too but error persists.

Look https://github.com/UndeadSec/SocialFish/commit/0006dca62fd0c3483402dc495b3c112c2deed19f


ng9 IVY Ng2-odometer library issue when compile with AoT

See the ticket on the angular github as well:
https://github.com/angular/angular/issues/35203
Affected Package
The issue is caused by package @angular/....
Is this a regression?
Sort of, it's because of IVY + AoT + https://github.com/jmandreslopez/ng2-odometer
it works with NG8 + AoT
Description
A clear and concise description of the problem...
Sooooo, upgrade to NG9 took some time but eventually I got there.
Development works when I use the settings:
"optimization":false,
"sourceMap":true,
"extractCss":true,
"namedChunks":false,
"aot":false,
"extractLicenses":false,
"vendorChunk":false,
"buildOptimizer":false,
When I set
"aot":true
It doesn't
error message is:
ERROR in node_modules/ng2-odometer/dist/index.d.ts:3:23 - error NG6005: Ng2OdometerModule.forRoot returns a ModuleWithPro
viders type without a generic type argument. Please add a generic type argument to the ModuleWithProviders type. If this
occurrence is in library code you don't control, please contact the library authors.
3 static forRoot(): ModuleWithProviders;
I already have an old issue open on the library in respect to IVY:
jmandreslopez/ng2-odometer#8
but nobody's home it seems ;).
I seem to remember the angular team was trying to be compatible with as much libraries as possible for IVY, not sure if that is still relevant/the case.
On first look, IVY is crazy fast in comparison to viewEngine for our application. Well done!
Best regards,
Lander

I forked this repo and fixed this issue. (https://github.com/arin-pang/ng9-odometer)

I forked this repo and fixed this issue. (https://github.com/arin-pang/ng9-odometer)

You are a saver man, thanks for this


Update regex check for existing clients and make it idempotent again

See https://github.com/angristan/openvpn-install/issues/652#issuecomment-650372450
Fix #652

When do you plan on merging? I am hoping this will solve the linked issue.

This creates a loop where it just keeps asking for a client name.

Just checked this. Doesn't create a loop for me when applied on current master (2ab48f). I'm not familiar with EasyRSA, so I can't tell if this is the right solution to the "recreate revoked client" issue, but it seems to work.


Githubdam h79 updates test iOS VoiceOver

Hi Marc, Please review the branch if you find any incorrect please advise.

Merged - OK to delete this branch.


iframe briefly freezes

For https://github.com/phetsims/QA/issues/216.  Found on Win 7 Internet Explorer.  Not found on other browsers on Win 7 or on Win 10 IE.
When dragging any atom in the atomic interactions iframe, it is possible to drag it off screen.  If the atom is "let go of" outside the sim, then there are several seconds where the sim can't be interacted with, before intractability returns.  @jbphet thought this sounded like a scenery issue.
https://drive.google.com/file/d/1U_9-pEDQXglWy7SgK_6Aeq_STGLU3hHu/view?usp=sharing

I didn't realize that this was only in IE when @KatieWoe showed it to me.  I don't think it's worth @jonathanolson's time to investigate in that case.  Closing.


Epic: wait for the endpoint to be available in proxy

Motivation
During the compute wake-up, the control plane returns a compute address that is not always immediately available for connection. We attempted to rectify this by conducting more connectivity checks on the control plane side. However, both NodePort and ClusterIP are just rules in local iptables, which are maintained by the node-local kube-proxy. So even when the control plane can reach the compute through sni_proxy, there's no guarantee that a user connection through the proxy will be able to reach the compute. This is due to the fact that sni_proxy and proxy could be on different k8s nodes, and an iptables rule could be available on one and not on the other node. Moreover, with ClusterIP, we use a DNS name to connect to compute immediately after pod creation, and sometimes the domain name resolution fails for a few seconds.
Implementation Ideas
As a mitigation, we might accept the fact that k8s networking is eventually consistent and retry connection attempts in the proxy. We already retry the connection once in case we have stale destination host information in the cache. It still makes sense to retry right after a failed connection attempt, but after that, we might retry connection attempts every 100ms. We need to be cautious about which connection errors we retry and which we don't. For example, we should not retry wrong passwords, etc. I believe we should have an explicit list of errors that we retry, such as: couldn't connect, time out, DNS resolution error.
With this change, we'll shift some of the waiting logic to the proxy side. Therefore, we should measure and log the end-to-end connection wait time. The user-proxy geographical distance will influence this, so it makes sense to track how long it takes for the client to send a reply during authentication to get a sense of ping time, and subtract ping_time * N from the total latency (we can do this as a follow-up so as not to block the initial roll-out).
Tasks

[x] Implement and merge the waiting logic
[ ] #6923
[ ] Conduct a load / wake-up test on staging
[ ] Implement and merge ping and latency measurement logic
[ ] #6924

Dashboard with errors: https://neonprod.grafana.net/d/fefbf47f-a8a6-4201-8472-98765f1654de/proxy-error-classification

Discussed this and it is done. Create some followup tasks.


Fix the break in Benchmark test and make it more robust.

The benchmark test broke after recent change to mixer. This was not caught because the test was not getting executed as part of perftest.sh and was also not checking for success. Added both of these to ensure that the test does not break silently.

This change is

Jenkins job mixer/presubmit passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Jenkins job mixer/presubmit passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/manager-regression passed

Friendly ping.


Media not marked as available despite existing on server and displayed "Play on Jellyfin" button.

Description
Hello Jellyseerr Team.
I have just setup Jellyseerr via docker and all went smooth. However I spotted one issue. After manually requesting full library scan, some media that I own are displayed as "Available" with "Play on Jellyfin" button and without the button to request them.
Some media however are not displayed as available, despite existing on server. Jellyseerr displays "Play on Jellyfin" button and it works correctly however there is also button to request the title.
Search result:

Play/request button:

I can mark the movie/series as available but I would need to check for all my media how it is displayed on Jellyseerr.
Version
1.2.1
Steps to Reproduce

Connect Jellyseerr with Jellyfin
Do full manual library scan.
Check if some movies/series are not reported as available but can be played & requested at the same time.

Screenshots
No response
Logs
2022-11-27T15:05:00.707Z [debug][Jellyfin Sync]: Updating existing title: Elfen Lied
2022-11-27T15:00:00.782Z [debug][Jellyfin Sync]: Updating existing title: Elfen Lied
2022-11-27T14:55:00.354Z [debug][Jellyfin Sync]: Updating existing title: Elfen Lied

Platform
desktop
Device
Windows PC
Operating System
Windows 10
Browser
Chrome
Additional Context
No response
Code of Conduct

[X] I agree to follow Overseerr's Code of Conduct

Could you see if you turn on sonarr/radarr scan in services and running that scan it works or not?

@Fallenbagel I will do that, I just have to install Sonarr first.

I just had that issue aswell with just my 4k Sonarr instance. I noticed my service connection didn't have "enable Scan" set for sonarr4k which fixed it after running a sonarr scan. So show availability in the jellyseerr GUI seems to be linked to sonarr/radarr scans?

I just had that issue aswell with just my 4k Sonarr instance. I noticed my service connection didn't have "enable Scan" set for sonarr4k which fixed it after running a sonarr scan. So show availability in the jellyseerr GUI seems to be linked to sonarr/radarr scans?

No its linked to jellyfin. It will also show availability with *arr. The reason why it wasn't showing availability with jellyfin is because of missing ids in your metadata that was produced by the jellyfin

Hello all,
I am having the same issue now (with the last version). I am running sonarr/radarr/jellyfin/jellyseerr.
I request the series, download it, but it does not appears correctly as downloaded on the jellyseer.
I begin to happens around week ago with the series, but I didn't happen me in the last few months.
For example: Mandalorian, The man in the high castle, attack on titan, but for example "Foundation" was downloaded weeks ago, is correctly set as "Partially Available":

Checking in the logs of the jellyseerr I found that it knows that the series are there:

Let me know anything where to look into, or provide more logs.
Thanks in advance.

Updated on my case: I checked that the sonarr and radarr was disable the scan.
I enabled it, and now are in the "Recently added" tab the series, but it does not know that are available on jellyfin and there is no the typical link to "plan on jellyfin". I am checking the logs on jellyfin and jellyseerr to undesrtand why it does not getting that data. In the case of Mandalorian it works few months ago with the old seasons, but now it's not working with the new one.

Updated on my case: I checked that the sonarr and radarr was disable the scan.
I enabled it, and now are in the "Recently added" tab the series, but it does not know that are available on jellyfin and there is no the typical link to "plan on jellyfin". I am checking the logs on jellyfin and jellyseerr to undesrtand why it does not getting that data. In the case of Mandalorian it works few months ago with the old seasons, but now it's not working with the new one.

Sounds like a tmdb id missing issue. Try moving the affected stuff out of directory, and delete any nfos or anything and move back and replace metadata

I was checking on the jellyfin and the metadata is there. Also, I don't have any nfo on the same folders.
Every Show is in a independent folder, with an strict order {Serie name - YEAR}/{name - SXXEXX - Title}. And I don't see any nfo on the folders of the shows.
I am not sure how to do of the cleaning of the metadata on jellyfin, any advice? On my way, I went to jellyfin > series > refresh metada > refresh all metada. It finished correctly, refreshing all the metadata on jellyfin database, but I force library sync in jellyseer and it seems not working.
Thanks in advance.

From my testings it works when you move the stuff out of the library folder, let jellyfin delete the media then move back in

Let me know if I did it correctly, it doesn't work this steps:

I move the folder of "The mandalorian" to /tmp/The Mandalorian".
I go to jellyfin and enable scan library. The show disappear from the library.
I go the jellyseer and sync libraries, scan libraries and (not necessary I think) I run all the jobs for syncing.
I move to the show from /tmp to the shows data folder again.
In jellyfin I sync the library, wait for it: the show again appears correctly.
In jellyseerr I sync the libraries, (I did the same that step 3).

I miss something? I did not see any special in the logs, errors or something like that. Also, I got the push notification that there are new episodes from the show that I moved out and move in.
I am not sure if could be a bug (because this happens only in the new requests, but not in the last month requests) or a missing configuration from mi side :)
Thanks a lot for your patience.

Also, I will add some information of the stack:

Jellyfin in docker of linuxserver.io (running as user). Stable. 1.8.9.
Jellyseerr in docker. Stable release. 1.4.1.
Sonarr in docker from linuxserver.io, version <IP_ADDRESS>6
Radarr in docker from linuxserver.io, version <IP_ADDRESS>57

In the same stack I also have qbittorent, prowlarr and swag. And I use watchtower to update the images.

Did you clear series from jellyseerr itself? What's the issue exactly? (Also might not be a bug since I'm not able to recreate it and a lot of others too)

I am sorry, but I don't know how to clear the series from jellyseer?
The issue that I am having is that the button "play on jellyfin" does not appears on this series. The three are downloaded on this month with the new release, all the previous ones has the button that link directly with jellyfin. The mandalorian has the button, but I deleted the old seasons and when it begins to download the season three has the same issue, next screenshot to check (I have the two episodes but it doesn't show the button that link directly with jellyfin:

It works! I found the clear button on the left button, and resync all the libraries and the series now has the direct link to jellyfinl
It's ok, but, I don't understand why it happens only with the new series. At least it working fine 👍
Thanks a million!

It's ok, but, I don't understand why it happens only with the new series. At least it working fine 👍

Like I said earlier, what happened was the tmdbID was missing in your jellyfin metadata. That's why jellyseerr was unable to find it as jellyseerr uses tmdb as a database and matches with the id given by jellyfin with jellyseerrs own database.
The reason why it still showed as partially available was because it matched with sonarr sync. But due to the missing tmdb id, it didn't match with jellyfin sync. Once you refreshed the metadata it fixed and grabbed the tmdb ID so jellyseerr was able to match

Thanks a lot for the explanation. Also, if it happens in the future and is any way to get a detailed logs to know what is happening I will be happy to share with you.
Thanks a lot!

Thanks a lot for the explanation. Also, if it happens in the future and is any way to get a detailed logs to know what is happening I will be happy to share with you.

As long as you have the logs in debug level, just run a jellyfin full scan(on jellyseerr) and the logs should show a tmdb id error which would be helpful to narrow down the issue c:

Sorry to ask this, but how I setup the logs in debug mode? I checked in the tab of logs and there is no errors. I don't find anything in the documentation/readme of the github repository.
Also, I tried to download a film, and it works perfectly (it sync and show the button), so I think someone was incorrect with this three series/films that were missing, but it seems don't happen anymore.
Really appreciate all your effort on great piece of software :)

Sorry to ask this, but how I setup the logs in debug mode? I checked in the tab of logs and there is no errors. I don't find anything in the documentation/readme of the github repository.

It's the DEBUG_LEVEL in dockercompose environment c:

Sorry to ask this, but how I setup the logs in debug mode? I checked in the tab of logs and there is no errors. I don't find anything in the documentation/readme of the github repository.

It's the LOG_LEVEL in dockercompose environment c:

Ok, next time it happens I will set the log_level to debug and read the logs.
Thanks a million!

I am going to close this as I assume its working since there has been no further clarification.


Eliminate libc++ and libunwind dependencies

Currently, compiling Roc programs relies on libc++ and libunwind for cxa_throw and friends. This means anyone who wants to build a Roc program needs to have libc++ and libunwind installed on their system.
That's undesirable for several reasons, including how it blocks the goal to have people be able to download the roc static executable and be able to run it without needing anything else installed!
Since both libc++ and libunwind are MIT-licensed, we can bundle only the parts we need into roc_std and remove the step where we link in libc++ and libunwind. While we're at it, we can also rename them to things like roc_throw, to prevent namespace conflicts in hosts in case we ever decide to make Roc-specific changes to how they work.
This issue will be resolved when we can remove this step from BUILDING_FROM_SOURCE and have everything still work!

Done in https://github.com/roc-lang/roc/pull/1605


Unable to Create cloudflare_access_service_token

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v0.14.4
+ provider registry.terraform.io/cloudflare/cloudflare v2.21.0
+ provider registry.terraform.io/hashicorp/aws v3.42.0
+ provider registry.terraform.io/hashicorp/random v3.1.0
+ provider registry.terraform.io/integrations/github v4.3.1

Affected resource(s)
resource "cloudflare_access_service_token" "my_app" {
  zone_id = var.zone_id
  name       = "CI/CD app"
}

Terraform configuration files
resource "cloudflare_access_service_token" "my_app" {
  zone_id = var.zone_id
  name       = "CI/CD app"
}

Debug output
error creating access service token: HTTP status 405: POST method with API Tokens is not supported by this API (10000)
on ../../../../stacks/aws/argo-tunnel/service_token.tf line 1, in resource "cloudflare_access_service_token" "":
1: resource "cloudflare_access_service_token" ""
Panic output
No response
Expected output
service token to be created
Actual output
error creating access service token: HTTP status 405: POST method with API Tokens is not supported by this API (10000)
on ../../../../stacks/aws/argo-tunnel/service_token.tf line 1, in resource "cloudflare_access_service_token" "":
1: resource "cloudflare_access_service_token" ""
Steps to reproduce
1 - create a new resource
2- terraform plan run successfullly
3- terraform plan - have error
Additional factoids
No response
References
No response

The error message here is pretty self explanatory

POST method with API Tokens is not supported by this API

You'll need to use your API key instead.

i was using api_token to authenticate the provider but I found that my API Token was not supporting creating access tokens and access groups, once adding the required permissions.
it worked


Use non-global RNGs

Fixes https://github.com/TuringLang/Turing.jl/issues/1260.

Ready to merge once the tests pass.

Should we add predict(rng::AbstractRNG, ...) as we spoke about @devmotion in this PR or should I make another one after this has gotten merged?:)

The PR is based on Turing master before predict and MLE and MAP were added, so if we want to fix predict we would have to merge master first (or rebase). I don't mind if it's addressed in this PR or in a separate one, but I guess we should also make sure that VI uses user-provided RNGs.

It'll be cleaner if done separately.


dragAndDrop method

From<EMAIL_ADDRESS>on February 13, 2013 07:33:15
It will be nice to have dragAndDrop methods
Original issue: http://code.google.com/p/robotium/issues/detail?id=390

From<EMAIL_ADDRESS>on February 13, 2013 07:33:56
"would be nice" of course

From<EMAIL_ADDRESS>on February 26, 2013 22:34:20
Will open up if we decide to implement this.
Status: WontFix


Opening external simulator device CarPlay never triggers an event by the registerOnConnect

Describe the bug
From my iPhone 15, iOS 17 simulator, opening external simulator device CarPlay never triggers an event by the registerOnConnect
To Reproduce
Steps to reproduce the behavior:

Template code found on your side implemented in React Native (ejected Expo) project
Code execution started (yarn start)
Using an iPhone 15, iOS 17 simulator, selecting external display = CarPlay from the I/O menu
CarPlay.registerOnConnect is executed program start but events is never fired on opening/closing the separate CarPlay simulator

Expected behavior
From your example code, I would expect the carPlayConnected to be set to true. That never happens since onConnect never fires.
function onConnect() {
setCarPlayConnected(true);
}
Screenshots/Videos

CarPlay (please complete the following information):

Device: iPhone 15 Simulator
OS version: iOS 17
RNCarPlay version [e.g. 2.4.0]

Android Auto (please complete the following information):

Device: [e.g. Pixel 8 / emulator]
Android Version: [e.g. iOS8.1]
RNCarPlay version 2.3.0 (have tried with diff versions (including the latest 2.4.0-beta.2 which fail all together).

Additional context
I'm running VScode on macOS Sonoma 14

Apart from that, really appreciating your effort in getting this project going!!

You can check this -> https://github.com/birkir/react-native-carplay/issues/150


Add support for Terminal-based deployment

tik currently assumes execution in a graphical environment, hence the liberal use of zenity for dialog boxes, lists, progressbars, and password entry
Most of these are called by the 'd' function (and all should be called by 'd' and/or it's equivalents once #41 is implemented)
Original tik design assumed zenity would be used interchangably with dialog for terminal use, however dialog doesn't support all target architectures we wish to work on.
Therefore I propose expanding the 'd' function to instead use nice simple plain text outputs that will work on any terminal on any architecture.
There will obviously need to be some magic for more complex differences such as references to "Press [a GUI button] to continue" vs "Press any key to continue"
Some below mockups for example

zenity --info --ok-label="Install Now" --no-wrap --width=300 --height=300 --icon=distributor-logo-Aeon-symbolic --title="" --text="<big>Welcome to Aeon</big>\n\nPlease press Install Now to continue"

clear
echo "Welcome to Aeon"
read -n 1 -s -r -p "Press any key to continue"

zenity --question --no-wrap --title="Begin Installation?" --text="Once the installation begins the changes to the selected disk are irreversible.\n\nProceeding will fully erase the disk.\n\nContinue with installation?"

clear
tput bold
echo "Begin Installation?"
tput sgr0
echo -e "Once the installation begins the changes to the selected disk are irreversible.\n\n$(tput bold)Proceeding will fully erase the disk.$(tput sgr0)\n\nContinue with installation?"
read -p "(y/n)?" choice
case "$choice" in
  y|Y ) echo "yes";;
  n|N ) echo "no";;
  * ) echo "invalid";;
esac

Just for tracking and to keep things together, PR for cli support is here: https://github.com/sysrich/tik/pull/44


ENH: Disable file compression for images loaded with ImageStacks module

This makes sure file loading/saving is fast, regardless of SlicerMorph customizations (which disables compression in all new volumes by default).
Also added two minor fixes:

do not wrap lines in file list (this makes it easier to see the filenames even if path is long)
instantiate output volume node using the scene (to create the volume with default settings specified in the scene)

Inspired by this discussion: https://discourse.slicer.org/t/bad-performance-when-segmenting-11gb-micro-ct/38362/2

thank you!


CAB-3590 - round date range search correctly

Coverage increased (+0.005%) to 82.871% when pulling 37fe67d5317c212cb1b079fe88bab5afc265c4a0 on feature/CAB-3590 into 3abe08a639c06a7403e8f267ead56b1c9692c866 on develop.


Rank range is 1-65536, not 0-65535, so a short overflow happens for full containers.
There is a fix w/ regression tests.

Coverage remained the same at 91.91% when pulling 9bf5a0884f6588a3fcd05d61ee5225cc9ffbecfa on khitrin:rank-iterator-bugfix into<PHONE_NUMBER>662af3e86c4c596f121cd15637f605 on RoaringBitmap:master.

Great.


Update documentation

The repository should have a more generic README and CONTRIBUTING Guide as it hosts various bots of our community.
The current README and CONTRIBUTING Guide are focused on the telegram-bot so it should be moved into telegram-bot folder.

Updated CONTRIBUTING.md with https://github.com/osdc/bots/commit/ce91f7702aecab793d5048aed235009edbf36d6c.
README should have something similar to #10 for all the bots instead of setup instructions.


Backend work for Notebook Parameterization and Tests

This PR introduces the backend cell model work that is required for Parameterization. There are two important tags for parameterization as a whole: parameters and injected-parameters. This enables the use of Papermill to work properly with ADS Notebooks.
The current backend work is demonstrated in the gif below. It focuses on using the cell toolbar action to change the metadata based on the action of "Make parameter cell" and "Remove parameter cell". I have added tests for both the parameter cell as well as the injected-parameter cell.
The injected-parameter cell will be added to a notebook below the parameters cell when a user uses Papermill (for example) to parameterize a notebook.
Please leave any feedback or questions!
Work to do: UI components for the visual tag of the parameter cell.

Gif: Click cell -> Use toolbar action 'Make parameter cell' -> Save notebook -> View metadata of notebook cell with new tag "parameters" -> Use toolbar action 'Remove parameter cell' -> Save notebook -> View metadata of notebook cell and see that the "parameters" tag is no longer there.

Pull Request Test Coverage Report for Build 306977796

41 of 53 (77.36%)  changed or added relevant lines in 3 files are covered.
84 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.03%) to 39.557%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/services/notebook/browser/models/cell.ts
35
36
97.22%

src/sql/workbench/contrib/notebook/browser/cellToolbarActions.ts
4
15
26.67%

Files with Coverage Reduction
New Missed Lines
%

src/sql/base/browser/ui/selectBox/selectBox.ts
2
46.78%

extensions/notebook/src/jupyter/serverInstance.ts
4
74.52%

src/sql/base/browser/ui/panel/panel.ts
11
41.74%

src/sql/workbench/contrib/notebook/browser/notebookActions.ts
67
32.65%

Totals

Change from base Build 305478738:
0.03%

Covered Lines:
20256

Relevant Lines:
46915

💛  - Coveralls


Better logging for insufficient resources

Add better logging for when a job cannot be scheduled due to insufficient resources.
Resolution for https://github.com/mesos/chronos/issues/394
@elingg
@michaeljin

:+1:


Removed py ref from github workflow

Checklist before submitting

[ ] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes # (issue).
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

Closing this. It is covered in https://github.com/open-ce/xgboost-feedstock/pull/50.


Allow for forking the query and retaining the schedule

Create a new query, set a refresh schedule
Fork it: the new query doesn't has the refresh schedule set.

Actually this is by design. I wanted to avoid situation that queries get scheduled by mistake, just because the original one was scheduled.

mrmr. I'm mostly forking queries to make them execute at another
datasource; so I really want to copy the schedule ;)
does the query results cache works by hashing the query text or it does it
by query-id? if it's in the first case, it wouldn't be a problem if you
duplicated the schedule without noticing it because the query won't be run
again (because of the query cache)
On Mon, May 11, 2015 at 2:48 PM, Arik Fraimovich<EMAIL_ADDRESS>wrote:

Actually this is by design. I wanted to avoid situation that queries get
scheduled by mistake, just because the original one was scheduled.
—
Reply to this email directly or view it on GitHub
https://github.com/EverythingMe/redash/issues/424#issuecomment-100995008
.

Well, the use case around fork is usually different: you want to fork it to play around with the query or change something. In such cases, caching won't help as the user will end up running a different query (but you're correct that it's done using query text).
I won't change the default behavior of fork, but it's possible to add another fork button that retains the scheduling...

Super Fork?
Maybe "Clone" ?
On Tue, May 12, 2015 at 2:56 AM, Arik Fraimovich<EMAIL_ADDRESS>wrote:

Well, the use case around fork is usually different: you want to fork it
to play around with the query or change something. In such cases, caching
won't help as the user will end up running a different query (but you're
correct that it's done using query text).
I won't change the default behavior of fork, but it's possible to add
another fork button that retains the scheduling...
—
Reply to this email directly or view it on GitHub
https://github.com/EverythingMe/redash/issues/424#issuecomment-101141412
.

It's not a common enough use case to make the UI more complex than it is now.


Make images and slides for notebook 02

done, see slides here: https://github.com/mrdbourke/pytorch-deep-learning/blob/main/slides/02_pytorch_classification.pdf


Set the logging scope for notification handling one level higher so it’s also set for cancel notifications

@swift-ci Please test


Rest API initializing double Chains and notifications going to .neopython

Current behavior
API rest is starting the chains and notifications twice, even when --datadir /root/.XXX/ is called.
In addition, notifications are not being reported by the API, the JSON is returning always empty.
[I 180525 02:48:58 utils:42] Notification/Block [] 183
[] is the empty notification and 183 was the requested block
[I 180525 02:45:04 _observer:131] "<IP_ADDRESS>" - - [25/May/2018:02:45:03 +0000] "GET /v1/notifications/block/184 HTTP/1.1" 200 119 "-" "Mozilla/5.0 (X11; Linux x86_64;
Even debugging from inside RestApi.py, it was seeing that the notification were empty before being sent.
Thus, the error may be in the function notifications = self.notif.get_by_block(block)

What is the problem?

Include a screenshot if it makes sense.

Expected behavior

What should be happening?
Include a screenshot if it makes sense.

How to reproduce

Please explain the steps to reproduce the problem. If you are having an issue with your machine or build tools, the issue belongs on another repository as that is outside of the scope of this project.

Your environment
Let us know in what environment you're running into the issue:

OS: (Windows version/Linux distro/OSX version)
neo-python version: (hint: use np-prompt --version)
Python version: (hint: python -V)

Version 0.69 or 0.7 Development
IDEA FOR FIXING:
settings.py
DATA_DIR_PATH = PATH_USER_DATA
Perhaps, PATH_USER_DATA should not be used anymore after the initialization.
def set_data_dir(self, path):
if path == '.':
self.DATA_DIR_PATH = os.getcwd()
else:
self.DATA_DIR_PATH = path
I do not know, something like that... :dagger:

What's the exact command you use to start the rest api (with all arguments)?

Hi, @metachris,
My fault, I did not follow all the steps for the issue, I apologize.

In fact, there are **two problems**.

1) The first one is the screenshot, initiallized with the command:

/neo-python-rpc-rest/neo/bin/api_server.py --datadir /root/.neo-python-rpc-rest/ --privnet --port-rest 8080

The other one took our team 4 hour of debugging yesterday!

We tried to simply initialize two prompts (because we need the wallet ON-THE-FLY for being called). However, the same --datadir command does not move the logs (prompt.log and .prompt.py.history).

We tried to hardcode in the neo Settings and nothings worked. It seems that the standard (.neopython) was inserted in some binary.

What do your recommend?
Furthermore, if you have any other any idea for letting the wallets ready for being called, please, let us know.
Best regards,

Hey @vncoelho
I'm not sure I can follow. The api-server does not use prompt.log or prompt.py.history. These files are only used/created with prompt.py
Btw, You should start the api server with np-api-server instead of directly referencing the Python file.
I tried reproducing the datadir problem and indeed there was an error that I most likely fixed with #436. Can you please double-check?

I just reproduced, @metachris. It was easy to check.
The problem is that even with --datadir the /.neopython is still being created and the prompt.py and history being redirected to there.
I think that the configuration was inserted some binary. Because we already tried to hard code several things.

np-prompt does not create prompt.log or prompt.py.history, only np-prompt creates those files. They have been in that directory from before.
Have you actually used the branch with my latest code from the PR? I believe you are not using the code from my PR.
For me it works:
# np-prompt -p --datadir /root/.test
[I 180529 13:53:36 Settings:245] Data directory /root/.test does not yet exist. Creating...
Privatenet useragent '/NEO:2.7.4/', nonce:<PHONE_NUMBER>
[I 180529 13:53:36 Settings:295] Created 'Chains' directory at /root/.test/Chains
[I 180529 13:53:36 LevelDBBlockchain:114] Created Blockchain DB at /root/.test/Chains/privnet
[I 180529 13:53:36 NotificationDB:73] Created Notification DB At /root/.test/Chains/privnet_notif
NEO cli. Type 'help' to get started

neo>

As you can see, no mention of the .neopython directory.

No, they were not. I deleted the folder two times, Metachris.

Sorry, I confused this issue.
There are two points.

The logs of np-prompt have this problem. I just deleted them now and np-promp still sends them to .neopython. Something in the Binary could be happenning, as I said

the 2) is the api-server, it is also calling .neopython and then changing the chain folder.
But, perhaps, can be the same problem.

It's not in the binary, but set here: https://github.com/CityOfZion/neo-python/blob/development/neo/bin/prompt.py#L53
Proposing a pull request in a few minutes to put the prompt log and history into the custom datadir

Could be this.
There is also something else, Metachris.
3) the RPC and Rest are still with problems when run together.

4) the Rest is not publishing the notifications, we tried the 0.6.9 version and now the 0.7.
 The notifications are empty even in the auxiliary vector, I mean,  even when we check the vector that came from Block.Notification, not only in the API outside.

See #437 for a proposal to store prompt log and history files in a custom datadir.
Not sure what you mean with (3) and (4) exactly, please open a new ticket for those issues with an exact description and steps to reproduce.

Thanks for copying this issue into https://github.com/CityOfZion/neo-python/pull/437
I think you can deal with it from now on.


Automated Package Upgrade

:tada: This PR is included in version 7.7.379 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove unnecessary output which may cause errors in pai-management/k8sPaiLibrary/maintainlib/common.py

In ubuntu environment which uses Chinese language, python paictl.py cluster k8s-bootup -p /path/to/cluster-configuration/dir will cause the encoding error as the picture shown below.
So I remove the unnecessary output code.
Or maybe it could be resolved by using utf-8 encoding, but i think it's not a universal solution.

Coverage decreased (-28.9%) to 51.36% when pulling 6f0984d633c3dbbc5bb89be6fabac12b5be48a7d on Beyyes:fixBranch into a97798ab429fb11d040e019ac2872eb8778d4818 on Microsoft:master.

Using correct encoding for each text being processed is the solution indeed. Please propose a PR of a complete solution (for example, to radically solve the encoding issue) or create an issue so that we can officially make a schedule :)

Yes, agree with @hwuu
@Beyyes, I think  executing command in a silent way is unfriendly for issue debugging. And we'd better find a solution based on encoding.

@hwuu
I have changed the  print(response_msg.strip('\n')) to print(response_msg.encode('utf-8').strip('\n')), is this ok?

@beyyes: Sure. Thanks for making this change!


deploy-ert.configure-ert attemps to configure resource properties that cannot be changed - install on GCP

When running the GCP pipeline (version 0.16.0) the deploy-ert stage fails when setting the instances on the ERT resources. It appears it is trying to configure properties for resources that cannot be changed.
The error message is as follows:
$ fly -t ci w -j gcp-pipeline/deploy-ert
initializing
running pcf-pipelines/tasks/configure-ert/task.sh
/tmp/build/78490f5a
configuring product...
setting properties
finished setting properties
setting up network
finished setting up network
applying resource configuration for the following jobs:
	autoscaling
could not execute "configure-product": failed to configure resources: request failed: unexpected response:
HTTP/1.1 422 Unprocessable Entity
Transfer-Encoding: chunked
Cache-Control: no-cache, no-store
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Thu, 07 Sep 2017 15:12:07 GMT
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Pragma: no-cache
Server: nginx/1.4.6 (Ubuntu)
Strict-Transport-Security: max-age=31536000
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Request-Id: f59f5232-ade7-4bbc-9f25-2dc30e28a28e
X-Runtime: 1.575581
X-Xss-Protection: 1; mode=block

4f
{"errors":{"instances":["number may not be changed on non-configurable jobs"]}}
0

failed

@mhausmann-pivotal this is a known issue with Ops Manager. They plan on cutting a release early next week to fix this issue (which affects versions 1.11.9+). If you use 1.11.8 (pin this version to opsman_major_minor_version), then you should be fine. Thanks.


Error while restoring a container.

Description
Kindly help me. I am trying to checkpoint a docker, which is done on one server. Thereafter I am taking the checkpoint image to another server (with same docker version running) and trying to restore to the docker container. The restore is failing with the error "Error response from daemon: oci runtime error: criu failed: type NOTIFY errno 0" . The containers on both the servers were started with the same configuration. Restore log details at http://pastebin.com/x6Z0qwa1

Steps to reproduce the issue:
1.docker checkpoint ck cr
2.scp /var/lib/docker/containers/921de66b87.../checkpoints/ck server2
3.docker start --checkpoint ck cr_second
Describe the results you received:
Error response from daemon: oci runtime error: criu failed: type NOTIFY errno 0
log file: /var/lib/docker/containers/39bc78109ac6be1e47b95eb76fa7d7516b75f730cf619868d25ed30099daf943/checkpoints/ck/criu.work/restore-2017-01-17T21:06:33Z/restore.log
Describe the results you expected:
docker container should have started. I had earlier tried the same thing with docker 1.13.0-dev experimental and it use to work. However trying with Docker version 1.14.0-dev is giving me the above mentioned issue.
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Docker version 1.14.0-dev
Output of docker info:
Containers: 6
Running: 1
Paused: 0
Stopped: 5
Images: 277
Server Version: 1.14.0-dev
Storage Driver: overlay
Backing Filesystem: extfs
Supports d_type: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 03e5862ec0d8d3b3f750e19fca3ee367e13c090e
runc version: 51371867a01c467f08af739783b8beafc154c4d7
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.5.0-040500rc1-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.66 GiB
Name: xx.xx.xx.xx
ID: xx:xx:xx:xx
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Experimental: true
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
criu --version
Version: 2.6

ping @boucher @xemul ptal
@harshitdaga can you also add which version of criuu you have installed?

@thaJeztah added

Does anyone know what /proc/asound is?

The /proc/asound is the sound subsystem file. And it's missing on the destination node.

seems like /proc/sound is indeed the sound subsystem file. I have no idea why it started giving an issue now. I tried doing the same case on a different set of servers and it worked.
Thanks for the help :)

It's, I would say, an issue to be fixed in the long run. AFAIU the /proc/asound file is hidden by runc at container start with a bind-mount, so when restoring the corresponding container on a node that doesn't have this file, the restore shouldn't fail (unless the file is opened), but instead this bind-mount should just be ignored.

@xemul I came across this issue as well when restoring to a CentOS VM (worked fine in RHEL 7).  Did a CRIU ticket for this ever get created?

@rockymtnman this is not CRIU issue, that's what CRIU caller should do before calling criu restore -- tune the objects to restore before doing the restore itself. So no, ticket for CRIU has not been created for this. If there's some API missing on the CRIU side to make this work, then surely I'll create one, but in this particular case the --ext-mount-map option for asound should not be given.

@xemul I am facing same issue on one destination host. Would you like to tell if there is any fix for this problem? Thanks


Bump AGP/Gradle/Kotlin warn versions

Bumps the versions up a bit, so we can keep people moving forward.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@gmackall do you want a review on this? :)

@gmackall do you want a review on this? :)

Sure, thanks for reminding me! I wanted to let the tests finish running before requesting, but I must have closed the tab

This LGTM but I do want to ask if there's a reason behind these specific versions at this time, e.g. we are trying to get to particular versions by X time?

No specific driving reason this time, just to keep our window from growing too large (versions are getting released faster than we drop support) and keep users up to date


Fix inconsistent validation

Fixes #1508

So looks like that code was there intentionally, but without specs. I think it's worth mentioning the behavior change in UPGRADING, please?

If you really want to be nice, squash your commits after you've fixed the version in UPGRADING. I'll merge.

Oh, sorry. Force push doesn't result in a notification. Glad I could contribute. Thanks!

Thanks for your excellent work @dgasper!


[SPARK-18657][SPARK-18668] Make StreamingQuery.id persists across restart and not auto-generate StreamingQuery.name

What changes were proposed in this pull request?
Here are the major changes in this PR.

Added the ability to recover StreamingQuery.id from checkpoint location, by writing the id to checkpointLoc/metadata.
Added StreamingQuery.runId which is unique for every query started and does not persist across restarts. This is to identify each restart of a query separately (same as earlier behavior of id).
Removed auto-generation of StreamingQuery.name. The purpose of name was to have the ability to define an identifier across restarts, but since id is precisely that, there is no need for a auto-generated name. This means name becomes purely cosmetic, and is null by default.
Added runId to StreamingQueryListener events and StreamingQueryProgress.

Implementation details

Renamed existing StreamExecutionMetadata to OffsetSeqMetadata, and moved it to the file OffsetSeq.scala, because that is what this metadata is tied to. Also did some refactoring to make the code cleaner (got rid of a lot of .json and .getOrElse("{}")).
Added the id as the new StreamMetadata.
When a StreamingQuery is created it gets or writes the StreamMetadata from checkpointLoc/metadata.
All internal logging in StreamExecution uses (name, id, runId) instead of just name

TODO

[x] Test handling of name=null in json generation of StreamingQueryProgress
[ ] Test handling of name=null in json generation of StreamingQueryListener events
[ ] Test python API of runId

How was this patch tested?
Update unit tests and new unit tests

Test build #69538 has started for PR 16113 at commit aca547f.

Test build #69538 has finished for PR 16113 at commit aca547f.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
              \"(class org.apache.spark.sql.streaming.StreamingQueryListener$\") =>
case class UsingJoin(tpe: JoinType, usingColumns: Seq[String]) extends JoinType

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69538/
Test FAILed.

Test build #69540 has started for PR 16113 at commit bec2fb3.

Test build #69540 has finished for PR 16113 at commit bec2fb3.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class StreamMetadata(id: String)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69540/
Test FAILed.

Test build #69588 has started for PR 16113 at commit 0554e5e.

Test build #69588 has finished for PR 16113 at commit 0554e5e.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69588/
Test FAILed.

Test build #69589 has started for PR 16113 at commit 6e1bbdd.

Test build #69589 has finished for PR 16113 at commit 6e1bbdd.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69589/
Test FAILed.

Test build #69590 has started for PR 16113 at commit c9224ef.

Test build #69593 has started for PR 16113 at commit afd5c0f.

Test build #69594 has started for PR 16113 at commit 7ee4cf1.

Test build #69590 has finished for PR 16113 at commit c9224ef.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69590/
Test FAILed.

Test build #69593 has finished for PR 16113 at commit afd5c0f.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69593/
Test FAILed.

Test build #69594 has finished for PR 16113 at commit 7ee4cf1.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69594/
Test FAILed.

Merged build finished. Test FAILed.

Test build #69693 has started for PR 16113 at commit 19461e1.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69693/
Test FAILed.

Test build #69695 has started for PR 16113 at commit 4041a22.

Test build #69695 has finished for PR 16113 at commit 4041a22.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69695/
Test PASSed.

Merging to master and 2.1


[Azure-Machine learning] ValidationException while running automated ML

Hi ,
I am trying to execute the automl experiment on custom data set, but i am getting the following error . can you please help on this.
import logging

automl_settings = {
    "iteration_timeout_minutes": 10,
    "experiment_timeout_hours": 0.3,
    "enable_early_stopping": True,
    "primary_metric": 'r2_score',
    "featurization": 'auto',
    "verbosity": logging.INFO,
    "n_cross_validations": 5
}
from azureml.train.automl import AutoMLConfig
automl_config=AutoMLConfig(task='regression',debug_log='automated_ml_errors.log',
                             training_data=x_train,
                             label_column_name="sold_price",
                             **automl_settings)
from azureml.core import Experiment
experiment=Experiment(ws, 'sample-price')
experiment.submit(automl_config,show_output=True)

and error is:

ValidationException                       Traceback (most recent call last)
<ipython-input-85-0519fb6f2be1> in <module>
      1 from azureml.core import Experiment
      2 experiment=Experiment(ws, 'sample-price')
----> 3 experiment.submit(automl_config,show_output=True)

/anaconda/envs/azureml_py36/lib/python3.6/site-packages/azureml/core/experiment.py in submit(self, config, tags, **kwargs)
    218         submit_func = get_experiment_submit(config)
    219         with self._log_context("submit config {}".format(config.__class__.__name__)):
--> 220             run = submit_func(config, self.workspace, self.name, **kwargs)
    221         if tags is not None:
    222             run.set_tags(tags)

/anaconda/envs/azureml_py36/lib/python3.6/site-packages/azureml/train/automl/automlconfig.py in _automl_static_submit(automl_config_object, workspace, experiment_name, **kwargs)
     98             compute_target,
     99             parent_run_id,
--> 100             show_output)
    101
    102         automl_run.add_properties(global_tracking_info_registry.gather_all(settings.path))

/anaconda/envs/azureml_py36/lib/python3.6/site-packages/azureml/train/automl/automlconfig.py in _start_execution(experiment, settings_obj, fit_params, run_config, compute_target, parent_run_id, show_output)
    197             package_utilities._get_package_incompatibilities(
    198                 packages=package_utilities.AUTOML_PACKAGES,
--> 199                 ignored_dependencies=package_utilities._PACKAGES_TO_IGNORE_VERSIONS
    200             )
    201         automl_run = _default_execution(experiment, settings_obj, fit_params, True, show_output, parent_run_id)

/anaconda/envs/azureml_py36/lib/python3.6/site-packages/azureml/automl/core/package_utilities.py in _get_package_incompatibilities(packages, ignored_dependencies, is_databricks_run)
    428                         missing_packages_message='\n'.join(messages),
    429                         reference_code=ReferenceCodes._PACKAGE_INCOMPATIBILITIES_FOUND,
--> 430                         validated_requirements_file_path=VALIDATED_REQ_FILE_PATH
    431                     )
    432                 )

ValidationException: ValidationException:
	Message: Install the required versions of packages using the requirements file. Requirements file location: /anaconda/envs/azureml_py36/lib/python3.6/site-packages/azureml/automl/core/validated_linux_requirements.txt. Alternatively, use remote target to avoid dependency management.
Package name/Required version/Installed version
azureml-core/pyopenssl<20.0.0/pyOpenSSL 20.0.0
	InnerException: None
	ErrorResponse
{
    "error": {
        "code": "UserError",
        "message": "Install the required versions of packages using the requirements file. Requirements file location: /anaconda/envs/azureml_py36/lib/python3.6/site-packages/azureml/automl/core/validated_linux_requirements.txt. Alternatively, use remote target to avoid dependency management. \nPackage name/Required version/Installed version\nazureml-core/pyopenssl<20.0.0/pyOpenSSL 20.0.0",
        "target": "azureml-core",
        "inner_error": {
            "code": "NotSupported",
            "inner_error": {
                "code": "IncompatibleOrMissingDependency"
            }
        },
        "reference_code": "435ab938-fd87-49bc-932e-6eec0d6aee4f"
    }
}

@NSVR57 please include the link to the document that you are following so that we can better assist.

Based on the error it seems to be missing some packages and dependencies. Please create an issue on the piece of documentation where you would like to leave feedback and we will gladly help troubleshoot.

I ran into the same error too when trying the sample notebook "regression-automl-nyc-taxi" of the tutorial included in Azure ML Studio.
The error message suggests there are version conflicts inside azureml core.
Can you please re-open the issue to investigate?

I ran into the same error too when trying the sample notebook "regression-automl-nyc-taxi" of the tutorial included in Azure ML Studio.
The error message suggests there are version conflicts inside azureml core.
Can you please re-open the issue to investigate?


🐛 Firebase Web isn't initializing.

Bug report
I've automatically configured firebase project running flutterfire.bat configure and using google_sign_in package I was able to login in my app running on Android but I'm not even able to initialize firebase web as it throws an error right on await Firebase.initializeApp. I've seen that there's another closed thread about this problem #5334 which they say this issue was already fixed but apparently it hasn't. I've tested in both master and stable channels with same result. (I logged with a google just to be sure that the firebase was running correctly, again, it worked on Android but it didn't on Web).
Error thrown at await Firebase.initializeApp:
Error: Expected a value of type 'Object', but got one of type 'Null'
    at Object.throw_ [as throw] (http://localhost:30292/dart_sdk.js:5067:11)
    at Object.castError (http://localhost:30292/dart_sdk.js:5026:15)
    at Object.cast [as as] (http://localhost:30292/dart_sdk.js:5351:17)
    at Function.as (http://localhost:30292/dart_sdk.js:6576:31)
    at firebase_core_web.FirebaseCoreWeb.new.get [_ignoredServiceScripts] (http://localhost:30292/packages/firebase_core_web/firebase_core_web.dart.lib.js:142:65)
    at firebase_core_web.FirebaseCoreWeb.new._initializeCoreRequireJs (http://localhost:30292/packages/firebase_core_web/firebase_core_web.dart.lib.js:187:27)
    at _initializeCoreRequireJs.next (<anonymous>)
    at runBody (http://localhost:30292/dart_sdk.js:40590:34)
    at Object._async [as async] (http://localhost:30292/dart_sdk.js:40621:7)
    at firebase_core_web.FirebaseCoreWeb.new.[_initializeCoreRequireJs] (http://localhost:30292/packages/firebase_core_web/firebase_core_web.dart.lib.js:182:20)
    at firebase_core_web.FirebaseCoreWeb.new.initializeApp (http://localhost:30292/packages/firebase_core_web/firebase_core_web.dart.lib.js:214:47)
    at initializeApp.next (<anonymous>)
    at runBody (http://localhost:30292/dart_sdk.js:40590:34)
    at Object._async [as async] (http://localhost:30292/dart_sdk.js:40621:7)
    at firebase_core_web.FirebaseCoreWeb.new.initializeApp (http://localhost:30292/packages/firebase_core_web/firebase_core_web.dart.lib.js:210:20)
    at initializeApp (http://localhost:30292/packages/firebase_core/firebase_core.dart.lib.js:100:59)
    at initializeApp.next (<anonymous>)
    at runBody (http://localhost:30292/dart_sdk.js:40590:34)
    at Object._async [as async] (http://localhost:30292/dart_sdk.js:40621:7)
    at Function.initializeApp (http://localhost:30292/packages/firebase_core/firebase_core.dart.lib.js:99:20)
    at main (http://localhost:30292/packages/mice_online_app/main.dart.lib.js:576:36)
    at main.next (<anonymous>)
    at http://localhost:30292/dart_sdk.js:40571:33
    at _RootZone.runUnary (http://localhost:30292/dart_sdk.js:40441:59)
    at _FutureListener.thenAwait.handleValue (http://localhost:30292/dart_sdk.js:35363:29)
    at handleValueCallback (http://localhost:30292/dart_sdk.js:35931:49)
    at Function._propagateToListeners (http://localhost:30292/dart_sdk.js:35969:17)
    at _Future.immediate.[_completeWithValue] (http://localhost:30292/dart_sdk.js:35817:23)
    at async._AsyncCallbackEntry.new.callback (http://localhost:30292/dart_sdk.js:35838:35)
    at Object._microtaskLoop (http://localhost:30292/dart_sdk.js:40708:13)
    at _startMicrotaskLoop (http://localhost:30292/dart_sdk.js:40714:13)
    at http://localhost:30292/dart_sdk.js:36191:9

Error thrown at await Firebase.initializeApp after running flutter with "--no-sound-null-safety":
Error: Invalid argument(s): object cannot be a num, string, bool, or null
    at Object.throw_ [as throw] (http://localhost:29886/dart_sdk.js:5391:11)
    at Function.fromBrowserObject (http://localhost:29886/dart_sdk.js:66382:19)
    at firebase_core_web.FirebaseCoreWeb.new.get [_ignoredServiceScripts] (http://localhost:29886/packages/firebase_core_web/firebase_core_web.dart.lib.js:152:35)
    at firebase_core_web.FirebaseCoreWeb.new._initializeCoreRequireJs (http://localhost:29886/packages/firebase_core_web/firebase_core_web.dart.lib.js:199:27)
    at _initializeCoreRequireJs.next (<anonymous>)
    at runBody (http://localhost:29886/dart_sdk.js:43013:34)
    at Object._async [as async] (http://localhost:29886/dart_sdk.js:43044:7)
    at firebase_core_web.FirebaseCoreWeb.new.[_initializeCoreRequireJs] (http://localhost:29886/packages/firebase_core_web/firebase_core_web.dart.lib.js:194:20)
    at firebase_core_web.FirebaseCoreWeb.new.initializeApp (http://localhost:29886/packages/firebase_core_web/firebase_core_web.dart.lib.js:227:47)
    at initializeApp.next (<anonymous>)
    at runBody (http://localhost:29886/dart_sdk.js:43013:34)
    at Object._async [as async] (http://localhost:29886/dart_sdk.js:43044:7)
    at firebase_core_web.FirebaseCoreWeb.new.initializeApp (http://localhost:29886/packages/firebase_core_web/firebase_core_web.dart.lib.js:223:20)
    at initializeApp (http://localhost:29886/packages/firebase_core/firebase_core.dart.lib.js:111:59)
    at initializeApp.next (<anonymous>)
    at runBody (http://localhost:29886/dart_sdk.js:43013:34)
    at Object._async [as async] (http://localhost:29886/dart_sdk.js:43044:7)
    at Function.initializeApp (http://localhost:29886/packages/firebase_core/firebase_core.dart.lib.js:110:20)
    at main (http://localhost:29886/packages/mice_online_app/main.dart.lib.js:609:36)
    at main.next (<anonymous>)
    at http://localhost:29886/dart_sdk.js:42993:33
    at _RootZone.runUnary (http://localhost:29886/dart_sdk.js:42849:58)
    at _FutureListener.thenAwait.handleValue (http://localhost:29886/dart_sdk.js:37417:29)
    at handleValueCallback (http://localhost:29886/dart_sdk.js:38020:49)
    at Function._propagateToListeners (http://localhost:29886/dart_sdk.js:38058:17)
    at _Future.immediate.[_completeWithValue] (http://localhost:29886/dart_sdk.js:37900:23)
    at async._AsyncCallbackEntry.new.callback (http://localhost:29886/dart_sdk.js:37923:35)
    at Object._microtaskLoop (http://localhost:29886/dart_sdk.js:43153:13)
    at _startMicrotaskLoop (http://localhost:29886/dart_sdk.js:43159:13)
    at http://localhost:29886/dart_sdk.js:38289:9

Steps to reproduce
Steps to reproduce the behavior:

Create a flutter app
Configure Firebase
Run app on Web
See error.

Expected behavior
Firebase to initialize for web.
Sample project
https://gist.github.com/rsegecin/f9cceb81d6bfd6e715badb0a032ae4ec

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.10.0, on Microsoft Windows [Version 10.0.19044.1466], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[√] Chrome - develop for the web
[!] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.3)
    X Visual Studio is missing necessary components. Please re-run the Visual Studio installer for the "Desktop development with C++" workload, and include these components:
        MSVC v142 - VS 2019 C++ x64/x86 build tools
         - If there are multiple build tool versions available, install the latest
        C++ CMake tools for Windows
        Windows 10 SDK
[√] Android Studio (version 2020.3)
[√] VS Code (version 1.64.0)
[√] Connected device (4 available)
[√] HTTP Host Availability

! Doctor found issues in 1 category.

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.16.0
Flutter SDK 2.10.0
funtestic 1.0.0+1

dependencies:
- cupertino_icons 1.0.4
- firebase_auth 3.3.6 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_auth_web 3.3.7 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core 1.12.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- flutter 0.0.0 [characters collection material_color_utilities meta typed_data vector_math sky_engine]
- google_sign_in 5.2.3 [flutter google_sign_in_platform_interface google_sign_in_web]

dev dependencies:
- flutter_lints 1.0.4 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph typed_data]

transitive dependencies:
- async 2.8.2 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- characters 1.2.0
- charcode 1.3.1
- clock 1.1.0
- collection 1.15.0
- fake_async 1.2.0 [clock collection]
- firebase_auth_platform_interface 6.1.11 [firebase_core flutter meta plugin_platform_interface]
- firebase_core_platform_interface 4.2.4 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.5.4 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta typed_data vector_math]
- google_sign_in_platform_interface 2.1.1 [flutter quiver]
- google_sign_in_web 0.10.0+4 [flutter flutter_web_plugins google_sign_in_platform_interface js pedantic]
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- intl 0.17.0 [clock path]
- js 0.6.3
- lints 1.0.1
- matcher 0.12.11 [stack_trace]
- material_color_utilities 0.1.3
- meta 1.7.0
- path 1.8.0
- pedantic 1.11.1
- plugin_platform_interface 2.1.2 [meta]
- quiver 3.0.1+1 [matcher]
- sky_engine 0.0.99
- source_span 1.8.1 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- string_scanner 1.1.0 [charcode source_span]
- term_glyph 1.2.0
- test_api 0.4.8 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.3.0 [collection]
- vector_math 2.1.1

I hope it hasn't taken time of anyone. Apparently it was some corrupted cache, after I did flutter pub cache repair its not stuck on Firebase.initializeApp anymore, I'm still getting stuck at google sign in though saying that appClientId is null but that is another problem.

@rsegecin
I used your code sample and ran it on latest stable on web which compiled and built properly without any issues:
dhs@Dhss-MacBook-Pro ios_bug % flutter run -d chrome
Downloading Web SDK...                                             38.8s
Downloading CanvasKit...                                            7.5s
Launching lib/main.dart on Chrome in debug mode...
Waiting for connection from debug service on Chrome...             21.6s
This app is linked to the debug service: ws://<IP_ADDRESS>:52693/sxUjA4jgdeY=/ws
Debug service listening on ws://<IP_ADDRESS>:52693/sxUjA4jgdeY=/ws

💪 Running with sound null safety 💪

🔥  To hot restart changes while running, press "r" or "R".
For a more detailed help message, press "h". To quit, press "q".

An Observatory debugger and profiler on Chrome is available at: http://<IP_ADDRESS>:52693/sxUjA4jgdeY=
The Flutter DevTools debugger and profiler on Chrome is available at: http://<IP_ADDRESS>:9100?uri=http://<IP_ADDRESS>:52693/sxUjA4jgdeY=

The app I ran was already configured through CLI tool and use firebaseOptions inside main().

were you able to login?

I have the same issue but isn't allowed to share the code.

Did you configured with one of your Firebase's Project? Were you able to login? In the debug options check if you're catching all exceptions.

Yes, the firebase project is configured already. Tapping on login didn't perform any action and browser console, I don't see any logs.

Did you configured with one of your Firebase's Project? Were you able to login? In the debug options check if you're catching all exceptions.

Yes, the firebase project is configured already. Tapping on login didn't perform any action and browser console, I don't see any logs.

It should print out "you've logged" in the debug console after tapping login and selecting with what google account you want to use for login. But the simply fact that you've checked "All exceptions" and still not getting any errors when seeing the page already bugs me. The code that I posted to test, configured with firebase is all there is. Why it works when I'm running it as android app but not on browser? I've tried to change to dev flutter channel with the same result. I haven't seeing in the documentation any additional steps that I should take for deployment on Web, is it there any?. @isanecat glad to hear that I'm not alone with this problem.

To continue trying to solve this problem I tried the Manual Configuration and I was able to get much further, up until google sign in itself where I was able to select a google account and signin but on the flutter side the code gets stuck at
await FirebaseAuth.instance.signInWithCredential(credential)
After the user tries to login using google's authentication form from the iframe it tries to save a cookie in the user's browser but it breaks saying:

Which it is a issue already opened here https://github.com/firebase/firebase-js-sdk/issues/2284, and I suspect that's the reason why flutter also breaks.
Anyway, the documentation here should say that Flutter Web should still use Manual Configuration and only after they fix the issue https://github.com/firebase/firebase-js-sdk/issues/2284 flutter google sign for web will be usable.

Thank you @darshankawar


(PUP-11048) Correct changes from system to execute

Commit 2f14ddd26 changed the debian and systemd service providers from calling
Kernel.system to Puppet::Provider.execute, but the methods don't take
arguments in the same way, resulting in:
wrong number of arguments (given 5, expected 1..2)

This code path only seems to occur when ensuring a non-existent service isn't
enabled such as:
# puppet resource service doesnotexist ensure=false enable=false

Prior to 2f14ddd26 we did not use a shell when calling Kernel.system:
# strace -fi -e trace=execve ruby -e "system('ls','*')"
..
[pid  1631] [00007fe41e5d1e37] execve("/bin/ls", ["ls", "*"], 0x55c1d97b3c50 /* 20 vars */) = 0

So we preserve that behavior when calling Puppet::Provider#execute:
# strace -fi -e trace=execve /opt/puppetlabs/puppet/bin/ruby -e \
  "require 'puppet'; Puppet::Util::Execution.execute(['ls', '*'])"
..
[pid  1613] [00007f1231b57e37] execve("/bin/ls", ["ls", "*"], 0x5615349c44d0 /* 18 vars */) = 0

We also have to pass failonfail => false to prevent puppet from raising on
non-zero exit status.

jenkins please test this on redhat7-64a,ubuntu1804-64a,debian10-64a

@gimmyxd or @GabrielNagy could you review and merge before the main CI run?


Add a couple of enhancements to the local testing guide.

This does the following:

Update debian box version used
Add the missing ansible installation during the provisioning of VMs
Fix the wrong synced folder paths in the docs
Add more fixes/notes on what could go wrong
Make the readme richer by setting up execution contexts/info

Hmm, I think that's worth a shot! If we can make the local setup easier
in any way we should.


WW-4834 Improve RegEx used to validate URLs

see #157 and #156

Is it ready to merge? Does it contain the latest changes from #157?

@lukaszlenart
i copied the regex after the changes from #157 .
So it should be the same. Feel free to check.


Idea:  Jest Support

ESRun should support Jest out-of-the-box.
Jest seems to be the primary test framework for Node these days.     It would be great to have ESRun just work with it, without any additional setup or configs.
I tried to get it to work with ESRun, but was unsuccessful.    Perhaps it could be implemented to work as a --loader?     I was able to get my own TypeScript/ESM/Mapped Paths setup working with ts-jest, but it took a good amount of trial and error effort.

That's rather a Jest issue than a Esrun issue. Jest is losing popularity and it uses some old tools like babel, I'm not surprised it's not compatible with Typescript.
Some ways to go:

you can try using esbuild-jest.
you can search for other testing frameworks that support Typescript better than Jest, like Vitest (it's front-end-oriented, but I think it works for unit tests too).
create a plugin similar to esbuild-jest that uses Esrun.
leave Node and start using Bun 😝 Seriously, it might be the best advice. I switched to Bun with my newest projects. It's a better Node that can natively execute Typescript files, and has its own Jest-like test suite (just run bun test).


Does not work when using nginx reverse proxy

📑 I have found these related issues/pull requests
#4797 The difference is I am using nginx config is from https://github.com/louislam/uptime-kuma/wiki/Reverse-Proxy#nginx
🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
No response
👟 Reproduction steps

Start uptime-kuma docker image with the following:

docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime louislam/uptime-kuma:1

Setup nginx reverse proxy with SSL (Certbot).

nginx config generated by Certbot:
server {

    server_name uptime.example.com status.example.com;

    location / {
        proxy_set_header   X-Real-IP $remote_addr;
        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header   Host $host;
        proxy_pass         http://localhost:3001/;

        # WebSocket support
        proxy_http_version 1.1;
        proxy_set_header   Upgrade $http_upgrade;
        proxy_set_header   Connection "upgrade";
    }

    listen [::]:443 ssl; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/uptime.example.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/uptime.example.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = status.example.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    if ($host = uptime.example.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    listen 80;
    listen [::]:80;

    server_name uptime.example.com status.example.com;
    return 404; # managed by Certbot

}

Open uptime.example.com on a browser.

👀 Expected behavior
It should open the setup page and enable me to register and login to the dashboard.
😓 Actual Behavior
It just loads blank screen with error Lost connection to the socket server. Reconnecting....

Sometimes the error does not appear.
🐻 Uptime-Kuma Version
1.23.13
💻 Operating System and Arch
Linux 6.1.0-18-cloud-amd64  Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux
🌐 Browser
Chromium 125.0.6422.141
🖥 Deployment Environment

Runtime: Docker version 25.0.3
Database: sqlite
Filesystem used to store the database on:
number of monitors: 0

📝 Relevant log output
uptime-kuma  | ==> Performing startup jobs and maintenance tasks
uptime-kuma  | ==> Starting application with user 0 group 0
uptime-kuma  | Welcome to Uptime Kuma
uptime-kuma  | Your Node.js version: 18.20.2
uptime-kuma  | 2024-06-06T11:44:10Z [SERVER] INFO: Welcome to Uptime Kuma
uptime-kuma  | 2024-06-06T11:44:10Z [SERVER] INFO: Node Env: production
uptime-kuma  | 2024-06-06T11:44:10Z [SERVER] INFO: Inside Container: true
uptime-kuma  | 2024-06-06T11:44:10Z [SERVER] INFO: Importing Node libraries
uptime-kuma  | 2024-06-06T11:44:10Z [SERVER] INFO: Importing 3rd-party libraries
uptime-kuma  | 2024-06-06T11:44:11Z [SERVER] INFO: Creating express and socket.io instance
uptime-kuma  | 2024-06-06T11:44:11Z [SERVER] INFO: Server Type: HTTP
uptime-kuma  | 2024-06-06T11:44:11Z [SERVER] INFO: Importing this project modules
uptime-kuma  | 2024-06-06T11:44:11Z [NOTIFICATION] INFO: Prepare Notification Providers
uptime-kuma  | 2024-06-06T11:44:11Z [SERVER] INFO: Version: 1.23.13
uptime-kuma  | 2024-06-06T11:44:11Z [DB] INFO: Data Dir: ./data/
uptime-kuma  | 2024-06-06T11:44:11Z [SERVER] INFO: Connecting to the Database
uptime-kuma  | 2024-06-06T11:44:12Z [DB] INFO: SQLite config:
uptime-kuma  | [ { journal_mode: 'wal' } ]
uptime-kuma  | [ { cache_size: -12000 } ]
uptime-kuma  | 2024-06-06T11:44:12Z [DB] INFO: SQLite Version: 3.41.1
uptime-kuma  | 2024-06-06T11:44:12Z [SERVER] INFO: Connected
uptime-kuma  | 2024-06-06T11:44:12Z [DB] INFO: Your database version: 10
uptime-kuma  | 2024-06-06T11:44:12Z [DB] INFO: Latest database version: 10
uptime-kuma  | 2024-06-06T11:44:12Z [DB] INFO: Database patch not needed
uptime-kuma  | 2024-06-06T11:44:12Z [DB] INFO: Database Patch 2.0 Process
uptime-kuma  | 2024-06-06T11:44:12Z [SERVER] INFO: Load JWT secret from database.
uptime-kuma  | 2024-06-06T11:44:12Z [SERVER] INFO: No user, need setup
uptime-kuma  | 2024-06-06T11:44:12Z [SERVER] INFO: Adding route
uptime-kuma  | 2024-06-06T11:44:12Z [SERVER] INFO: Adding socket handler
uptime-kuma  | 2024-06-06T11:44:12Z [SERVER] INFO: Init the server
uptime-kuma  | 2024-06-06T11:44:12Z [SERVER] INFO: Listening on 3001
uptime-kuma  | 2024-06-06T11:44:12Z [SERVICES] INFO: Starting nscd
uptime-kuma  | 2024-06-06T11:48:53Z [SOCKET] INFO: New polling connection, IP = <IP_ADDRESS>
uptime-kuma  | 2024-06-06T11:48:53Z [SERVER] INFO: Redirect to setup page
uptime-kuma  | 2024-06-06T11:49:54Z [SOCKET] INFO: New polling connection, IP = <IP_ADDRESS>
uptime-kuma  | 2024-06-06T11:49:54Z [SERVER] INFO: Redirect to setup page
uptime-kuma  | 2024-06-06T11:50:57Z [SOCKET] INFO: New polling connection, IP = <IP_ADDRESS>
uptime-kuma  | 2024-06-06T11:50:57Z [SERVER] INFO: Redirect to setup page

From the configuration and the log, i cannot see something obvious.

(getting the stupid stuff out off the way first) have you maybe not applied a change in nginx?
Could you send the SIGUSR1 signalnginx -s reload

are you using a custom filter set as the user in https://github.com/louislam/uptime-kuma/issues/4256, or are you running vanilla nginx?
As a hunch: could you try launching the docker container with the -e UPTIME_KUMA_WS_ORIGIN_CHECK=bypass option (see https://github.com/louislam/uptime-kuma/releases/tag/1.23.9)?

(getting the stupid stuff out off the way first) have you maybe not applied a change in nginx?

Yeah, I have

are you using a custom filter set as the user in /socket.io is POSTed with content-type: text/plain and trips ModSecurity OWASP rules #4256, or are you running vanilla nginx?

I am running vanilla nginx.

As a hunch: could you try launching the docker container with the -e UPTIME_KUMA_WS_ORIGIN_CHECK=bypass option (see https://github.com/louislam/uptime-kuma/releases/tag/1.23.9)?

I tried but still no change.
Should the ip on uptime-kuma logs be my ip?

Are you running behind a firewall, vpn.. that might impede the websocket connection?
About the IP in the logs:
https://github.com/louislam/uptime-kuma/blob/4794f9eb0bc47ebfe3eed3edaa7f880430052543/server/uptime-kuma-server.js#L138
=> we print the ip that we recive unless trustProxy is set.

Are you running behind a firewall, vpn.. that might impede the websocket connection?

Not sure, I am using a gcp compute engine with the default allow-https/allow-http firewall settings.

... trustProxy is set.

Do i need to set this? If so, where do i set it?

gcp compute engine with [...] firewall settings

Could you try disabling the fiewall and see if this fixes the problem?
I don't know what that firewall filters as I don't use GCP.

Do i need to set this

You don't need to set this. (plus you can't if socketio is not working ^^)

Could you try disabling the fiewall and see if this fixes the problem?

I'm not sure if it is possible, I will check.

... I don't know what that firewall filters as ...

I think it basically block access to all ports on the server by default and you have to allow the ports you want accessible (allow-http and allow-https in this case allows traffic on ports 80 and 433).


A bug in VGG_FC_ILSVRC_16_layers-symbol.json

I downloaded the vgg16fc model from baidu yun mentioned in the fcn-xs example. But I found a bug in the corresponding symbol.json:
{
"op": "Convolution",
"param": {
"kernel": "(3, 3)",
"no_bias": "False",
"num_filter": "512",
"num_group": "1",
"pad": "(1, 1)",
"stride": "(1, 1)",
"workspace": "512"
},
"name": "conv5_2",
"inputs": [[48, 0], [49, 0], [50, 0]],
"backward_source_id": -1
},
{
"op": "Activation",
"param": {"act_type": "relu"},
"name": "conv1_2",
"inputs": [[51, 0]],
"backward_source_id": -1
},
The name of relu after conv5_2 should be relu5_2 instead of conv1_1. I'm not sure the influence for finetuning by using this symbol.json.

If there are some parameters have same name, it will cause error when reload parameters.

@solin319 But no error occured when I load the vgg16fc parameters.

@apache/mxnet-committers: This issue has been inactive for the past 90 days. It has no label and needs triage.
For general "how-to" questions, our user forum (and Chinese version) is a good place to get help.

@thbupt you are right, I will fix and update the fixed files s3.

@ThomasDelteil @thbupt Is this issue resolved now?

@vandanavk still not, will try to prioritize


feat: Add matching Docs header

@huguestennier let's try to merge it to master and check how it will look at labelstud.io.


Feat/msdk 373 expose middleware queries

:tada: This PR is included in version 2.0.0-alpha.52 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add grpc server - derec-crypto-core-grpc, add dotnet grpc client

This pull requests create grpc server folder and dotnet folder.
In grpc server folder is derec-crypto-core-grpc docker application to serve the cryptography primitives through grpc protocol.
This enables people coding in languages other then rust and java use the DeRec cryptography primitives in their applications.
Current docker image is scholtz2/derec-crypto-core-grpc but feel free to merge this pull request, create derec official docker image repo and serve it there.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


fix(q): :bug: could not install plugin on cordova 9+

the error message is an attempt to communicate that we do not really want to support using "requireCordovaModule" to load non-Cordova module "q" any longer.

https://github.com/apache/cordova/issues/52#issuecomment-475696680
https://stackoverflow.com/questions/55304065/cordova-error-using-requirecordovamodule-to-load-non-cordova-module-q-is-no

Contributing checklist

[x] Code must follow existing styling conventions
[x] Added a descriptive commit message

Solves issue(s)

Superseded by https://github.com/opentok/cordova-plugin-opentok/pull/199

Superseded by https://github.com/opentok/cordova-plugin-opentok/pull/199


Handlebars partial block causes weird indentation

Description
Opening a partial block causes the beautifier to indent once (which is correct), but closing the block never unindents, which causes the remainder of the code to have extra indentation.
Input Before Beautification
This is what the code looked like before:

    Stuff

{{#>partialBlock}}

        Inner portion

{{/partialBlock}}

    More stuff

Expected Output
The beautified code should have looked the same.
Actual Output
The beautified code actually looked like this:

    Stuff

{{#>partialBlock}}

        Inner portion

    {{/partialBlock}}

        More stuff

Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code does not look right!

Debug
Here is a link to the debug.md Gist: https://gist.github.com/SonOfHans/42ae1754eb33807114f15690cc434461
Checklist
I have:

[X] Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[X] Reloaded (or restarted) Atom to ensure it is not a caching issue
[X] Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[X] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[X] Generated debugging information by executing Atom Beautify: Help Debug Editor command in Atom and added link for debug.md Gist to this issue

You are using the default HTML beautifier, JS Beautify.  Switch to Pretty Diff and the issue is resolved.

Thanks for the input. Though it's true that Pretty Diff doesn't have this particular issue, it actually has its own bug that outright breaks some of my pages and therefore makes it not a viable option for use with Handlebars.


Wonderful and very helpful project

Thank you for this project and your web page. This is very useful to me, and surprisingly hard to find as an Android app.
(And I hope it's appropriate to post this kind of comment here. I don't see any place for comments.)

Kind feedback is always welcome, thank you :)
Good to hear that the script is as helpful as the number of requests suggested. If you are concerend with API stuff, you may also be interested in my newest tool: https://www.soscisurvey.de/tools/post-monkey.php