Cannot update plugins since latest ui-x update

Current Situation
Since latest update to ui-x, if I click on the (up arrow) to update plugins nothing happens. Already tried to change browser but issue persist. No error on logs either
Logs
No response
Config
No response
Homebridge UI Version
4.57.1
Homebridge Version
1.8.4
Node.js Version
20.17
Operating System
Official Homebridge Raspberry Pi Image
Environment Info
Using hb-service
Raspberry Pi Model
Raspberry Pi 4 B

I just checked on Raspberry Pi 4B, Homebridge 1.8.4, Homebridge UI 4.57.1 and works without problems.

I'm having the same issue. Homebridge 1.8.4 and UI 4.57.1. I'm on a RPi Model 3 B+.

@Palinghaas can you give an example of a plugin that you are trying to update and isn't working?

Sure, I'm unable to update the Denon TV plugin.

I just installed an older version of this plugin, tried to update, and it worked fine :/
What happens when you click the 'up' icon? does a modal appear with the plugin release notes?
I'm really asking how far you get. A screen recording would be useful.
and if possible could you do it with the browser dev tools open on the console screen, to see if any errors appear there?

Attached you'll find a screen recording. Immediately after clicking the update arrow 1 error is displayed in the console. I've copied the text below. Let me know if you need more.
main.f1717ed88be56f6b.js:1 ERROR Error: Uncaught (in promise): TypeError: Invalid comparator: ^20.15.1, TypeError: Invalid comparator: ^20.15.1,     at n.parse (main.f1717ed88be56f6b.js:1:1692216)     at new n (main.f1717ed88be56f6b.js:1:1692034)     at main.f1717ed88be56f6b.js:1:1695296     at Array.map (<anonymous>)     at n.parseRange (main.f1717ed88be56f6b.js:1:1695288)     at main.f1717ed88be56f6b.js:1:1693929     at Array.map (<anonymous>)     at new n (main.f1717ed88be56f6b.js:1:1693916)     at Le.exports (main.f1717ed88be56f6b.js:1:1712618)     at main.f1717ed88be56f6b.js:1:266985     at n.parse (main.f1717ed88be56f6b.js:1:1692216)     at new n (main.f1717ed88be56f6b.js:1:1692034)     at main.f1717ed88be56f6b.js:1:1695296     at Array.map (<anonymous>)     at n.parseRange (main.f1717ed88be56f6b.js:1:1695288)     at main.f1717ed88be56f6b.js:1:1693929     at Array.map (<anonymous>)     at new n (main.f1717ed88be56f6b.js:1:1693916)     at Le.exports (main.f1717ed88be56f6b.js:1:1712618)     at main.f1717ed88be56f6b.js:1:266985     at K (polyfills.985044b7a7399140.js:1:16771)     at polyfills.985044b7a7399140.js:1:15859     at polyfills.985044b7a7399140.js:1:15965     at e (main.f1717ed88be56f6b.js:1:2683423)     at E (main.f1717ed88be56f6b.js:1:2683626)     at y.invoke (polyfills.985044b7a7399140.js:1:7352)     at Object.onInvoke (main.f1717ed88be56f6b.js:1:2302356)     at y.invoke (polyfills.985044b7a7399140.js:1:7292)     at x.run (polyfills.985044b7a7399140.js:1:2715)     at polyfills.985044b7a7399140.js:1:17566
https://github.com/user-attachments/assets/5990259c-e267-4eaa-9b47-dd8e1b7ae00e

@Palinghaas can you do me a favour and click the three dots on this plugin to update to 5.1.2.
Then restart homebridge (or the child bridge if you have this set up)
Then go back to the plugins page, and see if it will let you then update to 5.1.7?

After selecting the version I want to install and I click the purple install button the 'pop up' window just disappears and nothing happens further.

In the 5.1.1 was bug in package.config, just uninstall plugin without removing config and install latest version again.

yes i noticed that comma 😆 but this has made me wonder why when trying to update a plugin, the UI checks your node version vs the engines.node of the version of the plugin you have installed rather than for the newer version of the plugin

In the 5.1.1 was bug in package.json, just uninstall this plugin without removing config and install latest version again.

This fixed my issue. Thanks! :)

@redeemer666 im assuming you were experiencing this issue for the same plugin? please see fix above.
i am making some changes to the UI to avoid this situation happening in the future!


Rediscuss file presentations incl. formalization of access modalities

I would like to rediscuss the way files are represented in openMINDS currently. The following aspects seem to be non-ideal:

distinction of the location/access url and "file" since the same file could potentially have multiple locations
properties in file representations which are usually not easily automatically acquired (such as "specialUsageRole", "contentDescription" etc.) should be extracted from the "file" entity to simplify automatic ingestion
for access protected resources (this is also relevant e.g. for protected web services), we should find a way to formalize the authentication protocols required for such a file so automated pipelines have a chance to execute the proper steps for gathering a valid token and to properly authenticate.

Also in this aspect, we might want to think about how to deal with archives (ZIP / TARs) and/or the "FileArchive" schema

I'll merge the issue.

I think #318 is also relevant. We probably need a brainstorming meeting to work through all of this.

PS (from @apdavison) this includes also better representations of archived or secondary repositories.


Stabilise integration tests when running on Android

On each run of the Android matrix they're failing on at least one of the API levels.
At the time of writing on the latest push to main here. Also see this comment.
I'm also puzzled, at the time of writing, why the status badge (featured at the top of our readme) states that the flutter_integration workflow is passing - which it's clearly not. 🤔

@QuintinWillison #93 improves the way integration tests are invoked and executed (either sides of driver) and the failures are very rare. It may still fail in these 2 scenarios:

the driver connection between emulator is being lost half way (fiable by attempting re-connection)
the emulator would not start (rare - not sure if we can fix it easily, might need us to re-work on the action directly)

Regarding the mismatched status badge, I think we should embed this URL: https://github.com/ably/ably-flutter/actions/workflows/flutter_integration.yaml/badge.svg (best to copy markdown from the flutter_integation under actions tab afresh)

Thanks.
In terms of the status badge, this is my fault...
I broke it with this commit, by removing the explicit name, meaning the workflow path from the perspective of the status badge renderer is different. We're just showing status at the moment for the commits prior to that change!
I still don't want an explicit name in the workflow file(s), so the fix going forward will be to update the status badge code in the readme.


utils::logging: implement tracing_chrome & tracing_flame support

This was useful while investigating basebackup slowness
For posterity, a branch on top of this PR that contains additional debug spans used in that investigation: problame/2023-12--slow-basebackup-investigation--cleaned-up2 (we might never commit it, the debug spans inhibit readability in the code).

I'm not sure whether the use of Box<dyn ...>, without enabling the two layers introduced in this PR, has substantial performance impact at runtime.
Will test that with my WIP getpage@lsn benchmark #5771
If it doesn't, I'm inclined to merge this.
@koivunej is that ok for you or can you not bear the boxes even if they don't have a measurable perf impact?

Following the previous comment we discussed this and Christian was going to bench the effects.

# setup
./target/release/neon_local init
./target/release/neon_local start
./target/release/neon_local tenant create --set-default

# workload
./target/release/pagebench get-page-latest-lsn --runtime 10s

(pagebench from https://github.com/neondatabase/neon/pull/6174 )
Results on an idle i3en.3xlarge (test_output on EBS volume though, not the local NVME)
The tenant has an initdb'd timeline with no other contents.
The entire working set fits in RAM => no IO.
Without this PR
2023-12-20T16:49:36.665603Z  INFO RPS: 17360
2023-12-20T16:49:37.666599Z  INFO RPS: 17617
2023-12-20T16:49:38.667604Z  INFO RPS: 17318
2023-12-20T16:49:39.668606Z  INFO RPS: 17267
2023-12-20T16:49:40.669594Z  INFO RPS: 17517
2023-12-20T16:49:41.670623Z  INFO RPS: 17263
2023-12-20T16:49:42.671599Z  INFO RPS: 17382
2023-12-20T16:49:43.672599Z  INFO RPS: 17369
2023-12-20T16:49:44.673621Z  INFO RPS: 17317
{
  "total": {
    "request_count": 173891,
    "latency_mean": "56us",
    "latency_percentiles": {
      "p95": "67us",
      "p99": "67us",
      "p99.9": "67us",
      "p99.99": "67us"
    }
  }
}

With this PR:
2023-12-20T16:50:45.669375Z  INFO RPS: 15021
2023-12-20T16:50:46.670368Z  INFO RPS: 15092
2023-12-20T16:50:47.671358Z  INFO RPS: 14725
2023-12-20T16:50:48.672378Z  INFO RPS: 15096
2023-12-20T16:50:49.673377Z  INFO RPS: 14882
2023-12-20T16:50:50.674375Z  INFO RPS: 15020
2023-12-20T16:50:51.675371Z  INFO RPS: 15304
2023-12-20T16:50:52.676364Z  INFO RPS: 15063
2023-12-20T16:50:53.677372Z  INFO RPS: 15070
{
  "total": {
    "request_count": 150402,
    "latency_mean": "65us",
    "latency_percentiles": {
      "p95": "80us",
      "p99": "80us",
      "p99.9": "80us",
      "p99.99": "80us"
    }
  }
}

So, I guess there's runtime overhead and we can't do it like it is in this PR.


ValueError: setting an array element with a sequence.

Hi Dr. Zhang，
When I execute Higashi's higashi_model.train_for_imputation_nbr_0(), I get the following error:
Traceback (most recent call last):
File "/home/zzl/.conda/envs/higashi/lib/python3.9/concurrent/futures/process.py", line 246, in _process_worker
r = call_item.fn(*call_item.args, **call_item.kwargs)
File "/home/ygc/Higashi/higashi/Higashi_wrapper.py", line 324, in one_thread_generate_neg
to_neighs = np.array(to_neighs)[:-1]
ValueError: setting an array element with a sequence. The requested array has an inhomogeneous shape after 1 dimensions. The detected shape was (2515,) + inhomogeneous part.
I tried to change the Numpy version, but when I changed to 1.22.0, 1.19.2, 1.24.6, the problem still did not resolve.
Could you help me solve this problem? Thank you very much

Ah, I think it's from numpy stop autobroadcasting for dtype='object'. So the fix should be to_neighs = np.array(to_neighs, dtype='object')[:-1]
But I think that fix has been updated in the repo, just not in the conda version. Could you try to git clone the repo and do pip install ./ instead to see if the latest version fix that error? Thx!


Function for isConversionComplete not integrated

The library interface class has a function called isConversionComplete. However this function is not implemented in the library itself, hence it does not compile when used.

Duplicate of #12  (solution can be found there)

@milesburton
Can be closed


Feature flag & rollout bucket decision

Feature flag & Rollout models parsing commit will be removed once its PR approved

P.R. #206 is for OASIS-1838 [Objective-C] Feature flags and rollouts bucketing decision

38 XCODE ANALYZE WARNINGS DETECTED
Xcode Clean / Build / Analyze the OptimizelySDKiOS / "iPhone X" .
The "master" branch currently generates ZERO compiler warnings (green check mark,
"No Issues"). However, P.R. #206 branch "oakbani:arafay/feature-flag-&-rollout-bucket-decision"
is currently generating 38 Xcode Analyze warnings.
We ought to keep Xcode Clean / Build / Analyze the OptimizelySDKiOS / "iPhone X"
at ZERO Xcode Analyze warnings if possible. Can you take a look and fix these warnings?
A similar more detailed comment was put on P.R. #205 (https://github.com/optimizely/objective-c-sdk/pull/205).

P.R. #206 depends on P.R. #205
P.R. #205 = OASIS-1847 Feature variable APIs
"Feature flags & rollout parsing" commit (poorly named?)
P.R. #206 = OASIS-1838 Feature flags and rollouts (includes P.R. #205 commit)
+ "Feature flag & rollout bucketing decision" commit
P.R. #207 = OASIS-1842 isFeatureEnabled (includes P.R. #205 and P.R. #206 commits)
+ "isFeatureEnabled API" commit
+ "Fixed crash with nil check of completion block" commit
Therefore, P.R. #205 will need approval first.


Update documentation

Add using the user guide and command session history section

Codecov Report

Merging #185 (225f6e7) into master (1a03869) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #185   +/-   ##
=========================================
  Coverage     57.06%   57.06%
  Complexity      701      701
=========================================
  Files           122      122
  Lines          2795     2795
  Branches        326      326
=========================================
  Hits           1595     1595
  Misses         1066     1066
  Partials        134      134

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 1a03869...225f6e7. Read the comment docs.

I see that you added information on ## 2 Using the user guide, thanks for making the user guide more comprehensive!


Create proposal for port detection optimizations

Which area/kind this issue is related to?
/area cli
/area library
/area documentation
Issue Description
This issue is part of #250 EPIC and focuses on the creation of the proposal. That said a document containing all the details about this feature should be added under docs/proposals.
A related issue to this one could be #225  or #244 we have already created in the past.

Target date: 7 July 2023

I've drafted the proposal and is currently under review. After the draft is reviewed I'll create the PR needed.

Closing as moving to https://github.com/devfile/api/issues/1152


Luigi cleanup

Shifting things around a bit. Created separate directories for config and common functions / classes (utils). Open to renaming any of these directories / files. But I think the organization helps to clean things up.

Overall looks very good. Just a few points of discussion above


Improvements

@CatalinStratu here are my 2 cents advices:

As a base rule, always make limited changes when you are proposing a PR. Stay focused and avoid any changes not directly related to the problem at hand

Also you need to work on your commit messages: "Improvements" without a body and explanation is well... not really informative.  It tells me zero thing about the PR

Do not change the .gitignore. Do a separate PR for this

Do not change their core code for no reason. None would ever accept this.

Only suggest changes that help you integrate as a library, not one extra thing

And you will need to sign the CLA.

Please keep in mind that submitting a PR needs to bring value and requires significant time from the maintainers to review and accept. So please be mindful and make sure you get things properly prepared before submitting a PR.
I would suggest that for now, that you close this PR, and work out something on your fork first.

So if this were a PR on one of my projects I would reject it outright. :)

@pombredanne @CatalinStratu  thanks both for you discussion and suggested changes.
@CatalinStratu I agree with the need to keep PRs minimal and feature specific. If you'd like to contribute larger changes let's chat first so you don't accidentally do work I wouldn't be willing to merge :)
The main focus for this project is to mirror the upstream go internal code https://github.com/golang/go as much as possible. I've diverged already in some necessary ways for correct recovery for malicious binaries, but when possible we'd like to be 1-1 with what the upstream code does. This includes naming, comments, indents, etc.


docs: Fixes parameter name for round/group

Fixes #4

Thank you, that was quick!

Thank you both!


Feature/accept regex query

Allows users to query using basic /.../ format regular expressions .

@Tom2277 can you send it to master?

@Tom2277 can you push to master?


"Capture and Crawl" fail on CaptureFailedError: Sent SIGKILL to item

To reproduce:

Set up Depicted Server on Ubuntu as per instruction on setting up Local Depicted server from Readme on https://github.com/bslatkin/dpxdt
Run in console
(depicted)ubuntu@ip-10-224-91-168:~/depicted$ ./run_site_diff.sh  --upload_build_id=1  --crawl_depth=1   http://www.carsales.com.au

Consold Output:
Scanning for content
Scanning 1 pages for good urls
Found 0 new URLs from http://www.carsales.com.au/
Finished crawl at depth 0
Found 1 total URLs, 1 good HTML pages; starting screenshots
Requesting run for http://www.carsales.com.au/
Marking runs as complete
Issue 1:
Crawl fails to grab any urls on www.carsales.com.au.
This may have to do with regular expression in matching URLs.
I can go in and have a look, but I think the author knows more about all implications on this regex and is the best one to look at changing regex
Issue 2:
Screenshot fails. When I go to Depicted server on :5000,
I saw
Failed after max attempts
CaptureFailedError: Sent SIGKILL to item=dpxdt.client.capture_worker.CaptureWorkflow({parent: dpxdt.client.capture_worker.DoCaptureQueueWorkflow#139980265969552, config_path: '/tmp/tmp8CiiLV/config.json', args: ('/tmp/tmp8CiiLV/log.txt',), interrupted: False, output_path: '/tmp/tmp8CiiLV/capture.png', kwargs: {timeout_seconds: 20}})#139980268763856, pid=8203, run_time=20.2134301662
Full log and config in attachment.

config.json.txt
full.log.txt

Sorry for the delay.
In the log you can see:
Still waiting for: https://googleads.g.doubleclick.net/pagead/viewthroughconversion/1017754493/?random=30626000&cv=8&fst=1457502374558&num=1&fmt=3&adtest=on&value=0&label=f015CJuTmgIQ_eam5QM&bg=666666&hl=en&guid=ON&eid=317150504&u_h=768&u_w=1024&u_ah=768&u_aw=1024&u_cd=32&u_his=1&u_tz=0&u_java=false&u_nplug=0&u_nmime=0&frm=0&url=http%3A//www.seek.com.au/&tiba=SEEK%20-%20Australia's%20no.%201%20jobs%2C%20employment%2C%20career%20and%20recruitment%20site&ctc_id=CAIVAgAAAB0CAAAA&ct_cookie_present=false&convclickts=0&ocp_id=o7jfVqOpG4m38gXvjK7YBg
Still waiting for: https://googleads.g.doubleclick.net/pagead/viewthroughconversion/1017754493/?random=1128608494&cv=8&fst=1457502374558&num=1&fmt=3&value=0&label=f015CJuTmgIQ_eam5QM&bg=666666&hl=en&guid=ON&eid=317150504&u_h=768&u_w=1024&u_ah=768&u_aw=1024&u_cd=32&u_his=1&u_tz=0&u_java=false&u_nplug=0&u_nmime=0&frm=0&url=http%3A//www.seek.com.au/&tiba=SEEK%20-%20Australia's%20no.%201%20jobs%2C%20employment%2C%20career%20and%20recruitment%20site&ctc_id=CAIVAgAAAB0CAAAA&ct_cookie_present=false&convclickts=0&ocp_id=o7jfVtLXG9Ou8AX_kqGQBg
Still waiting for: https://s.tribalfusion.com/i.cid?c=628673&d=30&page=landingPage
Still waiting for: https://googleads.g.doubleclick.net/pagead/viewthroughconversion/996179779/?random=1457502374811&cv=8&fst=1457502374811&num=1&fmt=3&label=DOw6CLX60QkQw_6B2wM&guid=ON&u_h=768&u_w=1024&u_ah=768&u_aw=1024&u_cd=32&u_his=1&u_tz=0&u_java=false&u_nplug=0&u_nmime=0&frm=0&url=http%3A//www.seek.com.au/&tiba=SEEK%20-%20Australia's%20no.%201%20jobs%2C%20employment%2C%20career%20and%20recruitment%20site&async=1
Still waiting for: https://www.google.com/ads/user-lists/1017754493/?label=f015CJuTmgIQ_eam5QM&fmt=3&bg=666666&num=1&ct_cookie_present=false&cv=8&frm=0&url=http%3A//www.seek.com.au/&eid=317150504&random=320667780
Still waiting for: https://www.google.com/ads/user-lists/1017754493/?label=f015CJuTmgIQ_eam5QM&fmt=3&bg=666666&num=1&ct_cookie_present=false&cv=8&frm=0&url=http%3A//www.seek.com.au/&eid=317150504&random=449884493
Still waiting for: https://www.google.com/ads/user-lists/996179779/?label=DOw6CLX60QkQw_6B2wM&fmt=3&num=1&cv=8&frm=0&url=http%3A//www.seek.com.au/&random=2116758165
Still waiting for: https://cm.g.doubleclick.net/pixel?google_nid=exp&google_cm&google_sc&google_ula=2786954&google_hm=18072662552493448202

That means the browser is just taking forever to load those Ad URLs. What I'd do is add those URLs to your "resourcesToIgnore" list in the config.json. That will cause those URLs to be blocked when PhantomJS runs, and allow the page to finish loading.
Please reopen if my suggestion doesn't work!


feat: skip_path option in watch

This PR adds support for specifying a skip_path option that support either a path or a list of paths that shouldn't result in adding the trigger step as part of the dynamically generated pipeline.
Note even in cases where a line in the diff is skipped due to skip_path and there are other paths in the diff that match path but doesn't match skip_path, the step will still be added to the dynamically generated pipeline. i.e. for the step to be effectively ignored, the paths in skip_path should match all of those in the given diff.
Motivation
The motivation for this is the lack of support for negation cases in doublestar (the package used for glob pattern matching) See https://github.com/bmatcuk/doublestar/issues/49.
I had a use case where I needed to avoid changes in certain subdirectories to trigger a step (if there were the only changes in the diff) and I tried to use the following pattern: path: "/main/{*,!(subdir1|subdir2)/**/*}" which should be a valid glob for filtering out subdir1 and subdir2, but didn't work.
With this, I could instead do something like:
- path: "main/"
  skip_path:
    - "main/subdir1"
    - "main/subdir2"

and the result would be the same.

@xzyfer could you take a look at this please? 🙂

@voluntadpear the capability proposed is valuable but a better approach would be to use a more robust globbing library with support for pattern negation i.e. https://github.com/gobwas/glob. That way we can consolidate all the matches in the path field.

@

Codecov Report

Merging #88 (8e87cc1) into master (bbda0a1) will decrease coverage by 1.07%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master      #88      +/-   ##
==========================================
- Coverage   78.48%   77.40%   -1.08%
==========================================
  Files           4        4
  Lines         158      177      +19
==========================================
+ Hits          124      137      +13
- Misses         22       27       +5
- Partials       12       13       +1

Impacted Files
Coverage Δ

pipeline.go
68.42% <71.42%> (-0.16%)
:arrow_down:

plugin.go
88.88% <100.00%> (-4.34%)
:arrow_down:

Continue to review full report at Codecov.

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

@xzyfer I've taken a look at https://github.com/gobwas/glob/ and there's also a similar issue to the one of doublestar, as reported in https://github.com/gobwas/glob/issues/47 negation only works on a character range or single character basis rather than a character group.
I've tried something like "/main/{*,!(subdir1|subdir2)/**/*}" and many variations but I couldn't find any way to negate subdir1 and subdir2 as desired for this use case here.
I saw that the turborepo team faced the same issue (https://github.com/vercel/turborepo/issues/445) with gobwas/glob and added a --exclude flag to specify paths to exclude, similar to what I'm proposing in this PR (btw, excludes sounds like an excellent alternative to skip_path), so this seems like a valid alternative.
What do you think?

@voluntadpear Sorry for delay. how about we do something as below.
Option 1: add a new property we do something like
- path:
  - "main/"
  - "!main/subdir1"
  - "!main/subdir2"

Basically allow the path to be either string value of array.
Option 2: add a new property like you suggested but rename it to exclude.
I prefer option1 though

Just to prod things along - this would be really useful to have! 🙏

Hi! Any news on this? We'd greatly need it, let me know if I can contribute to anything in order to speed up the integration


Could not create the task (Open the Browser Console to get details)

My actions before raising this issue
Installing CVAT with the Installation Guide under Windows 10 (https://opencv.github.io/cvat/docs/administration/basics/installation/)
Install the Semi-Automatic and Automatic Annotation (https://opencv.github.io/cvat/docs/administration/advanced/installation_automatic_annotation/)

Steps to Reproduce (for bugs)

Open localhost:8080
Log in and create a project
Paste my labels in the required format from a text file
Create a task with a specific name and the labels from the project (no new labels created)
Press Upload and wait until the error message occurs

Expected Behaviour
That everything works fine, the health check of the containers passed succesfully.
I try to upload around ~6300 HQ .png images, but every time I try the upload fails. The other issues with the same issue title didn't helped me. Which specific logs should I provide for more detailed information?
Maybe the RAM is a limited Source (got 11,9GB) and I checked, if any image of the dataset is broken.

please provide logs from cvat_Server container

@azhavoro solved it, with providing more memory for wsl it seems, that every time I uploaded images the max of the memory was used and leads to this failures.


Change Default ErrorPolicy to abort-job

Version: -feature
CUPS.org User: solutions
The default error policy, unless modified by the user in cupsd.conf, is stop-printer.
In the default configuration, this means that if there is an error, the local cups printer will automatically be stopped. Resuming the printer requires manual intervention; even if the printer subsequently reports that it is working, users are unable to print unless the resume the printer.
This is a little bit counter intuitive; if a user job automatically causes a printer error and stoppage - the generally needs to be resolved by an administrator - why doesn't cups automatically resume when the printer reports good health?
Alternatively, why doesn't it simply abort the job?
The only use case we might see this being of benefit would be in a large networked printer environment. But in this case, there would be a very limited amount of machines that need to be configured (especially as the client machines would likely only see a "single" virtual printer).
This is especially frustrating for two reasons:

Cups doesn't recognize a difference between a filter error (or something caused by a malformed pdf) vs an out-of-paper or any other kind of error, instead choosing to stop the printer whenever something might possibly go wrong. Why not abort the job instead? (Holding the job might causes people to print the same thing multiple times, but is an equally valid option).

For individual or small network users using a remote printer, this can cause the local cups printer to stop, even though it may work for everyone else. This is, again, a frustrating default to keep.

Judging from the number of web results, this seems to be a common problem.
Rather than configuring every single computers cupsd.conf file with a new ErrorPolicy directive, can we instead change the internal default to "abort-job" in order to provide a more useful out-of-box experience for more users?

In Debian, we have now changed the default ErrorPolicy to be retry-job with the following patch:
Description: Set default job error policy to "retry-job", since it is less
 confusing and a better default on most machines.
 .
 Amend documentation accordingly.
Author: Martin Pitt<EMAIL_ADDRESS>Author: Didier Raboud<EMAIL_ADDRESS>Origin: vendor
Last-Update: 2016-07-03

--- a/scheduler/conf.c
+++ b/scheduler/conf.c
@@ -785,7 +785,7 @@
   cupsdSetString(&LPDConfigFile, CUPS_DEFAULT_LPD_CONFIG_FILE);
   cupsdSetString(&SMBConfigFile, CUPS_DEFAULT_SMB_CONFIG_FILE);

-  cupsdSetString(&ErrorPolicy, "stop-printer");
+  cupsdSetString(&ErrorPolicy, "retry-job");

   JobHistory          = DEFAULT_HISTORY;
   JobFiles            = DEFAULT_FILES;
@@ -1307,8 +1307,8 @@
       strcmp(ErrorPolicy, "retry-job") &&
       strcmp(ErrorPolicy, "stop-printer"))
   {
-    cupsdLogMessage(CUPSD_LOG_ALERT, "Invalid ErrorPolicy \"%s\", resetting to \"stop-printer\".", ErrorPolicy);
-    cupsdSetString(&ErrorPolicy, "stop-printer");
+    cupsdLogMessage(CUPSD_LOG_ALERT, "Invalid ErrorPolicy \"%s\", resetting to \"retry-job\".", ErrorPolicy);
+    cupsdSetString(&ErrorPolicy, "retry-job");
   }

  /*
--- a/doc/help/man-cupsd.conf.html
+++ b/doc/help/man-cupsd.conf.html
@@ -99,11 +99,11 @@

ErrorPolicy abort-job

Specifies that a failed print job should be aborted (discarded) unless otherwise specified for the printer.

ErrorPolicy retry-job
-
Specifies that a failed print job should be retried at a later time unless otherwise specified for the printer.
+
Specifies that a failed print job should be retried at a later time unless otherwise specified for the printer. The 'retry-job' error policy is the default.

ErrorPolicy retry-this-job

Specifies that a failed print job should be retried immediately unless otherwise specified for the printer.

ErrorPolicy stop-printer
-
Specifies that a failed print job should stop the printer unless otherwise specified for the printer. The 'stop-printer' error policy is the default.
+
Specifies that a failed print job should stop the printer unless otherwise specified for the printer.

FilterLimit limit

Specifies the maximum cost of filters that are run concurrently, which can be used to minimize disk, memory, and CPU resource problems.
 A limit of 0 disables filter limiting.
--- a/man/cupsd.conf.man.in
+++ b/man/cupsd.conf.man.in
@@ -148,13 +148,13 @@
 Specifies that a failed print job should be aborted (discarded) unless otherwise specified for the printer.
 .TP 5
 \fBErrorPolicy retry-job\fR
-Specifies that a failed print job should be retried at a later time unless otherwise specified for the printer.
+Specifies that a failed print job should be retried at a later time unless otherwise specified for the printer. The 'retry-job' error policy is the default.
 .TP 5
 \fBErrorPolicy retry-this-job\fR
 Specifies that a failed print job should be retried immediately unless otherwise specified for the printer.
 .TP 5
 \fBErrorPolicy stop-printer\fR
-Specifies that a failed print job should stop the printer unless otherwise specified for the printer. The 'stop-printer' error policy is the default.
+Specifies that a failed print job should stop the printer unless otherwise specified for the printer.
 .\"#FilterLimit
 .TP 5
 \fBFilterLimit \fIlimit\fR

I don't see us changing the default we ship to either abort-job or retry-job. We provide a choice for a reason, and after careful consideration we won't be making either change to the main CUPS sources.
The problem with abort-job is that it gives up too quickly, which is not the best solution for users.
The problem with retry-job is that it can make the (unfortunately common) wrong driver failure even worse (more spewed pages), and will hide a DoS of a printer when the issue is that the PDL is crashing the printer's interpreter and causing the printer to reboot.
"hold-job" might be an interesting compromise - then the job isn't immediately tossed nor retried, and subsequent jobs can continue without stopping the queue.
But for now we want to stick with "stop-printer" as the default, out of the box policy. This yields a user notification on most platforms so that the user can act accordingly.

Michael, you write that with "stop-printer" as the default, this yields a user notification on most platforms so that the user can act accordingly. This may be appropriate for a single user system when the printer is only for personal use. But in a networked, administrated environment (for example university environment), even if users are notificated, they usually have no rights to re-enable the stopped printer queue. They can do nothing but wait for an administrator that can re-enable the printer queue. Users can clear paper jam or some other reason that may cause stop the printer - but the printer queue remains disabled, the printer queue doesn't re-check periodically if the printer is ready again.
This is a big fail of cups!
Everything which could be done automatically should be done this way. If the printer queue was enabled by an administrator at some time, it should stay in this state. Why do you think it is worth that an administrator should be enter an admin command (and the users have to wait for this), as cups can detect the printer ready state itself?

Edgar,
Most systems running CUPS are desktops, with users in control of the print queues. Recognizing that some people do still run print servers (by far the minority), we provide a configuration option (both a global default and the per-printer setting) to choose an alternate policy.
That said, all of these error policies only kick in if the backend exits with status 1 (error happened, use default policy), which (for the standard CUPS backends) only happens in exceptional situations that cannot be automatically retried because it requires administrative attention. (It is possible that some third-party backends do not follow the CUPS guidelines, thus the error policy setting...)

I just wanted to say, this is still really annoying.
Making someone have to resume a printer because one job failed is an extremely annoying default

@james-portman See https://github.com/OpenPrinting/cups/commit/956623c7efe5dbbf7a95fed1089fc15a96c6d76f from OpenPrinting/cups (available in 2.3.3op1).

I agree with @james-portman , I also find this annoying.
Why not add a configuration directive DefaultErrorPolicy and use its value as default for new printers?

@dmitrydonskih OpenPrinting CUPS supports the "ErrorPolicy" directive in cupsd.conf to specify the default error policy for new printers.


Need freebsd_port resource

freebsd_port_options drops in options but then doesn't run (cd /usr/ports/#{port_path} && make install clean clean-depends)

The package resource has a port resource. You can use the port_options to add additional options you cannot add with package. this functionality maybe should be added into the freebsd::port provider. We will look into it

Anybody can explain something? Where the freebsd::port provider is defined? I found this http://www.rubydoc.info/github/opscode/chef/Chef/Provider/Package/Freebsd/Port and I see a lot of code is similar to what is inside this cookbook and in some places it is much better written. But there is no documentation, no examples on the internet, so I don't know if it is possible to install a FreeBSD port by Chef itself. I can add a port provider here, the make install/deinstall code is not difficult to implement, but should I do it or it is better to contribute to Chef documentation? Implementing the same features in different classes is a violation of DRY principle.

I tried this using my fork but Chef installed packages, not ports:
freebsd_port_options 'lang/php56-extensions' do
  options bcmath: true, bz2: true
end

freebsd_package 'lang/php56-extensions' do
  provider Chef::Provider::Package::Freebsd::Port
end
Options were set correctly but bcmath and bz2 were not installed, also it finished very fast, means no compilation happened. But if I manually run make install clean it starts to fetch the source and so on, everything correct.


⚠ Bofrost.at has degraded performance

In bb5d1f0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2426 ms

Resolved: Bofrost.at performance has improved in cb7c4a9.


Can't connect to the server

If I use "https://my.server.com/", it becomes "https://my.server.co" and does.not connect.
If put the adress without the last /,the app can't connect.
If I use the same adress by copy/paste in my browser, it works.
I use version 1.1 on fdroid.org.

Strange.

When I don't put the last /, it said
Connection failed. Check if

You have Internet access
the URL is correct

Yes of cource:
https://github.com/theScrabi/OCBookmarks/blob/master/app/src/main/java/org/schabi/ocbookmarks/LoginAcitivty.java#86
-2
Who gave me the right to program?

Sorry, english is not my native langage and I'm not a developer.
Is it humor? :-/

It is :)

Ok, you can continue tu program ;-)

Closing in favour of https://gitlab.com/derSchabi/OCBookmarks/issues/8

I think the given link below is bad because the issue #8 can't refer to itself ;-)


Support for new libgfortran

Hi.
I use Archlinux, and now it seems libgfortran.so.3 is not available anymore (it's libgfortran.so.4 instead).
The configure and build of jblas works fine, but then when using jblas it won't work because it complains of missing libgfortran3.
symlink of libgfortran.so.3 to the libgfortran.so.4 caused "/usr/lib/libgfortran.so.3: version `GFORTRAN_1.0' not found"

Hey axeldavy,
have you tried going into the configure.out and replacing the library there. Still the GFORTRAN_1.0 bug?

With the configure options "--libs=openblas --download-lapack --build-type=openblas"
I get the following configure.out
BUILD_TYPE=openblas CC=gcc CCC=c99 CFLAGS=-fPIC -DHAS_CPUID F77=gfortran FOUND_JAVA=true FOUND_NM=true INCDIRS=-Iinclude -I/usr/lib/jvm/java-8-openjdk//include -I/usr/lib/jvm/java-8-openjdk//include/linux JAVA_HOME=/usr/lib/jvm/java-8-openjdk/ LAPACK_HOME=./lapack-lite-3.1.1 LD=gcc LDFLAGS=-shared -L/usr/lib LIB=lib LINKAGE_TYPE=dynamic LOADLIBES=-lopenblas MAKE=make NM=nm OS_ARCH=amd64 OS_ARCH_WITH_FLAVOR=amd64/sse3 OS_NAME=Linux RUBY=ruby SO=so
There doesn't seem to be a way to specify the version of libgfortran.

Hey, sorry for the very late reply. I just released 1.2.5 which bumps dependencies to libgfortran.so.4, but more importantly now also has that in the jar and copies it from there if it cannot find it. Let me know if that works for you.
I'm closing the issue now because it is so old, feel free to reopen if it still matters.


Azure App Service fails with MSI to access Key Vault

Issue:
Attempting to use a User Assigned Managed Identity in App Service fails when trying to access a secret from KeyVault. Tried both the NewAuthorizerFromEnvironment() and Authorizer() implementations. The same container and MSI configuration works running in Azure Container Instances but fails in App Service (custom container).
Version:
v0.11.10
Fails with:
azure.BearerAuthorizer#WithAuthorization: Failed to refresh the Token for request to https://aggolang-msi-old-LNWC-kv.vault.azure.net/secrets/test-secret/?api-version=2016-10-01: StatusCode=400 -- Original Error: adal: Refresh request failed. Status Code = '400'. Response body: {"statusCode":400,"message":"Unable to load requested managed identity.","correlationId":"51942452-3a05-4c1e-8571-2d93e6a7e6af"}
App Service Logs:

Code & Infra config for repro:
https://github.com/sgettys/azure-go-msi
@sgettys @robece @catalinaperalta

Fixed in autorest/adal/v0.9.6


All release notes are gone

I'm trying to look at what is new in each version of react-native to see which I should upgrade to and every one of them seem to have the release notes erased so I'm not sure what is new and what I would need to do to upgrade.

I know Github was having some issues this morning so that could be the problem, but the release notes are there:
https://github.com/facebook/react-native/releases
All of the release notes for a version get bundled together under the latest patch version of a release.  So for example, instead of looking at the release notes for v0.46.0-3, you would find all of the release notes under v0.46.4

yeah, github was having some issues but i can see all the release notes that were created.

I still cannot see any of the Release Notes. Click any Release Notes link on this page: https://facebook.github.io/react-native/versions.html and you will see nothing, when not to long ago there were notes for every single version. This should be reopened until this is actually fixed because everywhere on the react-native site points at the versions page and tells you to read the release notes to find the one you need.

i see. seems like release notes are attached to the latest version but in docs we are not linking to latest version. cc @hramos

This is because the versions page links to the .0 release notes, but we move them over to the latest patch. I think this makes for a good first task for anyone interested in getting familiar with the website generation code.

@hramos Where I can find the source code? Is the gh-pages branch generated from elsewhere?

The docs have now moved to https://github.com/facebook/react-native-website
We'd still like to fix this, feel free to re-open there.


Datepicker modal won't appear on IE 11 [v.1.0.0]

[Materialize 1.0.0-alpha.2]
IE 11 won't show up 'datepicker' modal.
I clicked input field, but nothing happened (even no errors or warnings!).
Other browsers are just fine.
Here is my code

HTML5

...
<form method="post" action="">

            <input type="text" class="datepicker validate" id="date_picker" name="date_picker" placeholder="Choose a date" />
            Pick a date

</form>
...

JS (using jQuery 3.2.1)

$(document).ready(function(){
    $('.datepicker').datepicker();
});

1.0 docs' example also doesn't work on ie 11...
Need help.

This error is thrown at line 11208 of materialize.js
this.wrapper = document.createElement('div');
this.wrapper.classList.add();
On Chrome/FF this creates an element of the shape

 but on IE11 the error Argument not optional is thrown. I am assuming this is not intentional because I can't think of a reason to call classList.add() without arguments. Immediately after it is called, $(this.wrapper).addClass('select-wrapper') is called. If the line this.wrapper.classList.add() is removed the code seems to behave the same way. Ideally, this is an easy fix and I'm happy to make a PR

Fixed in 7c4fc588f5ae3d4d3e838354ab5195905a2a4184


Allow to force to do not use -j as make argument

Close #828 (hopefully)

I think I can delete NO_PARALLEL_MAKE option, which is replaced by MAKE_NB_JOBS=1.


feat: GPU jenkins support

Also, please share successful build URL in description. Would be helpful for future reference


Failed to parse source map from ...

Hello and thanks for your work!
After having installed your library I get this warning:
WARNING in ./node_modules/boring-avatars/build/index.js [1] Module Warning (from ./node_modules/source-map-loader/dist/cjs.js): [1] Failed to parse source map from '/Users/User/Work/list/project/client/node_modules/boring-avatars/build/index.js.map' file: Error: ENOENT: no such file or directory, open '/Users/User/Work/list/project/client/node_modules/boring-avatars/build/index.js.map'
The library works even with that warning, still I wondered if there's a workaround to fix this.
Thank you again :)

Hey @ariwoot, can't reproduce it. Have you tried to delete node_modules folder and re-run npm install (or yarn)?

Hello,
Having the same problem here on a fresh create-react-app with only boring-avatars installed.
WARNING in ./node_modules/boring-avatars/build/index.js     Module Warning (from ./node_modules/source-map-loader/dist/cjs.js): Failed to parse source map from 'C:\Users\trist\Documents\prog\boringavatar-test\node_modules\boring-avatars\build\index.js.map' file: Error: ENOENT: no such file or directory,  open 'C:\Users\trist\Documents\prog\boringavatar-test\node_modules\boring-avatars\build\index.js.map'

@josepmartins have tried deleting node_modules folder and re-running npm install to no avail - the error still persists.

Same here.

I'm experience the same issue on a react project with plain js.
This commit https://github.com/boringdesigners/boring-avatars/commit/834303e27405b109bfcd8a6681886c8db3c1ff8c does remove the file after the build process. Using an pretty old version https://github.com/boringdesigners/boring-avatars/tree/v1.4.2 works for me.

Seem the last Create React App 5.0 throws this type of warnings by source-map-loader and there's a PR opened to fix it https://github.com/facebook/create-react-app/pull/11752, other packages are getting the same warnings https://github.com/facebook/create-react-app/discussions/11767.
Anyways, I've just included the sourcemap in the build again 👍 and release and new 1.6.2 patch version. Tested with a new React Create App and worked without any warnings.
Thanks everyone 👋


[Bug] [API] Badly formatted multipart request when I upload jar file

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
There is a similar issues that has not been solved
I can't upload jar file

What you expected to happen
above.
How to reproduce
above.
Anything else
I can upload any type of file except jar
Version
2.0.3
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

I have checked this in ds1 environment (dev and new UI) and it's okay.
Will check this in version 2.0.5 lately.


Inspector UI Enhancement

Hey, developers. I know feature/enhancement requests are not accepted for the time being. But, I wanted to suggest an UI enhancement for the future, if possible.
Godot is a great game engine and has a great potential for competing with giants in near future. With that being said, I would like to tell that the "Inspector" tab in Godot seems little obstructive (please, don't be offended by use of the adjective) in my view. I don't know much about others, but the UI of the inspector breaks my attention while I am working in Godot. In the inspector tab, there are some attributes for certain nodes which have different height from others. For instance, the Sprite2D node has a texture attribute and a normal map attribute and they are much more bigger in term of their height than others. And, the texture attribute when you put some texture in it, it gives a preview and textures usually have a mixer of colors. So, I get my attention easily diverted from level designing to the inspector.
So, I would like to suggest if you make the height each of the attributes in the Inspector tab equal and add something like preview toggling thing to disable the preview of the texture, then I think it will fix the attention breaking aspect.
Please pardon me if I talk something in a manner that I am not supposed to talk.

Hey, just to say that features/enhancements are encouraged, just not on this repository. There is a dedicated repo just for that: godot-proposals
I don't know how strict this rule is, but if your issue gets closed, post it on the other repo instead.

As @Ev1lbl0w, we now track feature proposals on the Godot proposals repository. This is to keep feature proposals actionable, so we know exactly what needs to be done to improve a feature.


WIP on new migration tests

This is a total draft on #19039 (migration tests which work on the database) to get feedback on the general approach before investing more time. It works as follows:

The test provides a source and target model (much like the model differ tests)
We migrate to the source, and scaffold a "snapshot"
We then migrate to the target, and scaffold another snapshot - and execute the test-provided asserter against it
We then migrate back down to the source, snapshot again and compare with the initial snapshot. If they aren't equal, that means that the up and down migrations aren't symmetrical
We finally migrate back down to an empty database, scaffold and make sure it's empty
If any exception was thrown, we clean the database.

The target model can also be specified as an incremental addition over the source model, to avoid repetition in case we're just adding stuff on top.
Notes:

All these operations are always executed against the same database, which is shared between all tests. This should hopefully mean the tests run quickly (it's very similar to the existing SqlServerDatabaseModelFactoryTest in that sense).
Do we think it's interesting enough to do SQL assertions? Assuming the scaffolded model corresponds exactly to what we're looking, I'm not sure asserting on DDL has much additional value...

If people like this, I'll convert all the existing migration tests to this new framework.

BTW Running the four tests in this draft suite shows around 100-150ms running time per test, which seems quite reasonable.

Thanks @bricelam, will start out by porting the current MigrationSqlGeneratorTestBase tests, and then we can compare actual times
PS what do you think about SQL assertions? Any value there? There's something nice about being able to see the actual DDL produced in each scenario.

Assert the SQL. It will catch aesthetic issues like weird CASTs or spacing that might not be caught executing the SQL

I've just pushed another update. Almost all tests from MigrationSqlGeneratorTestBase have been ported to the new test suite (but not specific ones from SqlServerMigrationSqlGeneratorTest). Some work still remains on making the tests provider-independent etc.
Just wanted to touch base again and report on build time. The new test suite has 39 tests for now, which perform DDL on the database. When only that suite is executed, the tests take 9 seconds. However, when running the entire SqlServer test suite I can only see 2 seconds of difference:
Current test suite (without my new suite):
Total tests: 16213
     Passed: 15867
     Failed: 3
    Skipped: 343
 Total time: 2.3762 Minutes (~142 seconds)

With my test suite and without SqlServerMigrationSqlGeneratorTest:
Total tests: 16122
     Passed: 15776
     Failed: 3
    Skipped: 343
 Total time: 2.4141 Minutes (~144 seconds)

As @bricelam suggested, this is mostly likely because the long DDL statements are being executed asynchronously, freeing the thread to run other tests at the same time.
I'm assuming everyone's OK with me continuing this work - the idea is to port all of the SqlServerMigrationSqlGeneratorTest / SqliteMigrationSqlGeneratorTest / MigrationSqlGeneratorTestBase (it will take a bit of work).
/cc @aspnet/efteam

Superceded by #19353


Missing most varient of the DashboardPart union  in Microsoft.Portal/preview/2020-09-01-preview/portal.json

Pulumi has received a few user reports (https://github.com/pulumi/pulumi-azure-native/issues/1696, https://github.com/pulumi/pulumi-azure-native/issues/3015, https://github.com/pulumi/pulumi-azure-native/issues/3023) of missing types for the DashboardPart union. EG.

Extension/HubsExtension/PartType/MonitorChartPart
Extension/HubsExtension/PartType/ClockPart

Full metadata part types can be found here. At the moment only Extension/HubsExtension/PartType/MarkdownPart appears to be defined.

@msHich  @majastrz  can you check this issue, thanks! Let me know if you have any question!

Any further updates here?


Allow usage of @GraphQLRepository in native mode

In order to optimise application, attempting to generate native image of application (spring  3 aot).
Declared the class annoted with @GraphQLRepository as a proxy. The application will not start in native mode as it cannot find bean of the annoted class autowired into an other bean.
Is it possible to add support for native mode ? Or is suggested configuration to use @GraphQLRepository in spring native mode.

Hello,
I actually didn't test that.
I'll add an integration test for this case.


Modify UnitButton to display charges, stack count, lock button under the icon

This effort is about improving visual concept of a UnitButton.

Appears to be complete.
Unit buttons display charges, stack count and lock icon.


Value of this when debugging Typescript

VSCode Version: 1.1
OS Version: Windows

Link to original issue
I'm using the NativeScript extension for VisualCode and I have the following issue when debugging:
Lambda/arrow functions that have this inside their body can be confusing.
Here is and example TS code.
promise.then((value) => {
  console.log("message: " + this.message);
  // ...
})

I stop on break point after the console.log() and add a watch expression for this.message and here is the conflict:

watch expression result: undefined
console output: message: hi there

The reason for this is that TS code gets transpiled to the following:
var _this = this;
promise.then(function (value) {
  console.log(_this.message);
});

Now its obvious now that my watch expression should have been _this.message. However, this can get quite confusing is you forget that you are currently debugging a lambda function.
I am wondering if there is someway to handle that.

see discussions in #23143 and #13967


[Chore]: Offboard Mario

Garden
Mailing lists<EMAIL_ADDRESS>Lastpass groups: Shared-Garden
GitHub Teams in each org
cloudfoundry: CF Garden
cloudfoundry-incubator: CF Garden
GCP: CF-Garden Core
Pivotal Tracker: CF Garden Public; CF Garden/GrootFS Private
Wavefront: https://longboard.wavefront.com/u/NpYmkFnwVT?t=pivotal-garden
GitHub Org: master-of-cats
Slack: #garden-core, #garden-notifications; @gardencore, @gardencipair
Eirini
Mailing lists<EMAIL_ADDRESS>Calendar Invites: Standup, IPM, Retro, Conv Street etc.
Pairup: pair board and your email from the [firebase access rules](https://console.firebase.google.com/u/0/project/cff-eirini-peace-pods/database/cff-eirini-peace-pods-defa
ult-rtdb/rules)
GitHub: CF Eirini team; Eirininauts Team
Pass: GGP key from pass
Git Authors: git authors and github handles
SSH key: remove from eirini-home
Eirini-station: remove VM from GCP
Pivotal Tracker: Eirini Public
Add new ci-bot integration in #eirini-ci
GCP: cff-eirini-peace-pods
CF-K8s
GCP project
GitHub Teams in each org

Should be all done, let me know if I've missed anything. Since I removed all my permissions I can't actually close this issue anymore, so please do that for me @georgethebeatle


$isHomePage broken by Hugo 1.8

Since the home page is just a normal page now, comparing titles is broken (since the home page's title is "_index").
There is now page variable to determine if this page is the home page, .IsHome (see https://gohugo.io/templates/variables#page-variables), which works well. I'm making changes in my theme which I will share with you when I have finished them.

Check out https://github.com/UM-Fencing/club-theme/commit/c85f84853e1f4d18a6935b43d989dc031b56e76e.
The changes to header.html should be compatible, but bootie-docs doesn't have the other two partials I made changes to.

@ethanmad
Thank you for your reporting.
It's true title handling is failing at http://key-amb.github.io/bootie-docs-demo/ , too.
I'll check the information above and do what to be done.
Maybe we should change min_version of this theme which is 0.14 currently.

@key-amb Just apply changes similarly to how I did in UM-Fencing/club-theme@c85f848. You can probably do it all using sed or find-and-replace and then add in the logic clean-ups by hand.
(By the way, you'll notice from my changes that {{ if variable }} works the same as {{ if eq variable true }}, just like in C: if (variable) is equivalent to if (variable == true)).
If only my fork had not diverged so much from yours, I could have submitted a PR for you to merge with one click.
This breaks backward compatibility with Hugo versions less than v0.15.


CA-205586: Reserve orginal IP settings before set IP by agent

Signed-off-by: Cheng Zhang<EMAIL_ADDRESS>

I don't think that this is sufficient: CLM is - I presume - quite likely to want to be able to reboot the VM while the static ip address is set.  As far as I can see, this code is only storing the network details in memory - I think they need to be stored in the registry

Hi ben,
Actually, The static IP address information is stored on the disk, the file path is:
private static string iniFile = System.IO.Path.GetDirectoryName(Application.ExecutablePath) +  "\ipsetting.ini";
It seems storing the message on the disk can work as well even the machine is restart.
If I misunderstand anything, please let me know.
Regards!
Lin

Oh yes - you're right - it is writing to an ini file.
I think I would still prefer to see this persisted in the registry - there is a good article here (only 9 years old) about why the use of .ini files was deprecated in favour of using the registry for config info
https://blogs.msdn.microsoft.com/oldnewthing/20071126-00/?p=24383

@benchalmers, Thanks for your comments,
I also prefer your suggestion which store the ip information in the registry.
The coding is done and a new pull request is submitted,
Could you help to review the code? Thanks and Regards!


[hotfix][no ticket] strip comments from registered meta (APIv1)

Purpose
Follow-up to #9170 -- apply the same to APIv1

Changes
Strip out prereg challenge comments from registrations' registered_meta

QA Notes

Documentation

Side Effects

Ticket

Build fail unrelated, that test breaks whenever fake.word() returns "home"


Cypress Testing Integration

Description

To implement Cypress for automated E2E testing across modules, starting with primary features, to ensure consistent workflow validation, enable early bug detection, and enhance overall release reliability.

Acceptance Criteria

[ ] Add Cypress as a project dependency to enable E2E testing capabilities.
[ ] Develop essential Cypress tests to cover modules (such as apps, services, user management, etc.).
[ ] Integrate Cypress tests into our CI/CD pipeline for seamless automated execution with every deployment.

Additional Information

Cypress stands out as a powerful and efficient test automation tool, perfectly suited for modern web applications. By implementing this solution, we can achieve faster release cycles and significantly improve error detection.
We can also configure the cypress plugin @cypress/code-coverage: To saves the code coverage collected during Cypress tests

@charmi-v if you need support from us contributing you can connect to @gopalreddy-bmw  please as he is supporting us with testing and wants to contribute with test-automation

Sure @MaximilianHauer, we have an internal sync scheduled for tomorrow (at 2:15 IST) to plan the test automation alignment.
@GopalReddy-BMW, could you please share your email so we can include you in the meeting? This will help us all gain clarity on the feature integration.

@charmi-v<EMAIL_ADDRESS>


Adding double-conversion package.

Google's double-conversion: Efficient binary-decimal and decimal-binary conversion routines for IEEE doubles.
https://github.com/google/double-conversion

Hi @ZeroCrunch, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@ZeroCrunch, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

OK. I've done name change and archive source change.
I agree with you and others that the CMake for Double-Conversion needs  to be changed. Until I can change the Double-Conversion code and get my PR accepted, I don't see any harm in the MSVC route for now.
NB: I'm doing this for Pixar's USD (https://github.com/PixarAnimationStudios/USD) as a native alternative to Nick Porcino's USD-build-club (https://github.com/vfxpro99/usd-build-club)
[https://avatars3.githubusercontent.com/u/19143841?v=3&s=400]https://github.com/vfxpro99/usd-build-club
vfxpro99/usd-build-clubhttps://github.com/vfxpro99/usd-build-club
github.com
Contribute to usd-build-club development by creating an account on GitHub.
[https://avatars2.githubusercontent.com/u/1672744?v=3&s=400]https://github.com/PixarAnimationStudios/USD
GitHub - PixarAnimationStudios/USD: Universal Scene ...https://github.com/PixarAnimationStudios/USD
github.com
Universal Scene Description (USD) is an efficient, scalable system for authoring, reading, and streaming time-sampled scene description for interchange ...

From: Robert Schumacher<EMAIL_ADDRESS>Sent: 11 October 2016 16:11
To: Microsoft/vcpkg
Cc: Jamie Kenyon; Mention
Subject: Re: [Microsoft/vcpkg] Adding double-conversion package. (#139)
@ras0219-msft requested changes on this pull request.
I'd be happy to merge this after the name change and archive source change, though I'd greatly appreciate it if you'd take a look at using CMake instead of their MSBuild projects.
It looks like the MSBuild projects only offer static library builds, so using CMake is essentially a requirement eventually.

In ports/doubleconversion/CONTROLhttps://github.com/Microsoft/vcpkg/pull/139#pullrequestreview-3693884:

@@ -0,0 +1,3 @@
+Source: doubleconversion

Looking at how the CMake scripts are deployed, it seems like this package needs to be named double-conversion.

In ports/doubleconversion/portfile.cmakehttps://github.com/Microsoft/vcpkg/pull/139#pullrequestreview-3693884:

@@ -0,0 +1,71 @@
+# Common Ambient Variables:
+#   VCPKG_ROOT_DIR = <C:\path\to\current\vcpkg>
+#   TARGET_TRIPLET is the current triplet (x86-windows, etc)
+#   PORT is the current port name (zlib, etc)
+#   CURRENT_BUILDTREES_DIR = ${VCPKG_ROOT_DIR}\buildtrees${PORT}
+#   CURRENT_PACKAGES_DIR  = ${VCPKG_ROOT_DIR}\packages${PORT}_${TARGET_TRIPLET}
+#

+include(${CMAKE_TRIPLET_FILE})
+include(vcpkg_common_functions)
+set(SOURCE_PATH ${CURRENT_BUILDTREES_DIR}/src/double-conversion-master)
+vcpkg_download_distfile(ARCHIVE

URLS "https://github.com/google/double-conversion/archive/master.zip"

Using the master archive is problematic because if a new commit is pushed, the zip file will no longer match the recorded SHA512 below. It's best to use either a release tag or a specific SHA, such as https://github.com/google/double-conversion/tree/d4d68e4e788bec89d55a6a3e33af674087837c82.

In ports/doubleconversion/portfile.cmakehttps://github.com/Microsoft/vcpkg/pull/139#pullrequestreview-3693884:

+include(${CMAKE_TRIPLET_FILE})
+include(vcpkg_common_functions)
+set(SOURCE_PATH ${CURRENT_BUILDTREES_DIR}/src/double-conversion-master)
+vcpkg_download_distfile(ARCHIVE

URLS "https://github.com/google/double-conversion/archive/master.zip"
FILENAME "doubleconversion-201.zip"
SHA512 8ce810f9957a99b761e2058d00a17def65ba52e55c8ab95e96947a98a31c199748dc707c9d1883783d970e8f19ac9593ae20a5376e9cfdd53a12cf88eccdbb81
+)
+vcpkg_extract_source_archive(${ARCHIVE})

+vcpkg_apply_patches(

SOURCE_PATH ${SOURCE_PATH}
PATCHES ${CMAKE_CURRENT_LIST_DIR}/mscv_vers.patch
+)

+vcpkg_build_msbuild(
I noticed that this project uses CMake for other platforms; does it work on Windows as well? If so, it's preferable to use CMake since it tends to be better maintained and handles multiple triplets better.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vcpkg/pull/139#pullrequestreview-3693884, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEAf-sVbHoAtyNLp5pkPe0ZdYohmoH7Zks5qy6cKgaJpZM4KTllT.

If you use the CMake build, there is no need for an upstream patch, it already adds the library correctly as add_library(double-conversion and doesn't explicitly specify static/shared. That means that all you have to do to get a shared-lib build is define BUILD_SHARED_LIBS for CMake.

Thanks for making those fixes!
I've opened issue #150 to track the static/shared issue and the eventual switch to CMake.


Confirm Available in eastUS2 ?

From a prior comment - GA for Availability Zones was announced on March 30th,  however, can you confirm that  eastus2 is included?  (centralus vm's show as being available)
Looking at three distinct azure accounts - all show eastus2 as unavailable - so not sure if it's just being rolled out still, or there is something else up?
...
Standard_A0             NotAvailableForSubscription  eastus2    ['1', '2', '3']
Standard_A1             NotAvailableForSubscription  eastus2    ['1', '2', '3']
Standard_A2             NotAvailableForSubscription  eastus2    ['1', '2', '3']
Standard_A3             NotAvailableForSubscription  eastus2    ['1', '2', '3']
Standard_A5             NotAvailableForSubscription  eastus2    ['1', '2', '3']
Standard_A4             NotAvailableForSubscription  eastus2    ['1', '2', '3']
Standard_A6             NotAvailableForSubscription  eastus2    ['1', '2', '3']
Standard_A7             NotAvailableForSubscription  eastus2    ['1', '2', '3']
Basic_A0                NotAvailableForSubscription  eastus2    ['1', '2', '3']
Basic_A1                NotAvailableForSubscription  eastus2    ['1', '2', '3']
Basic_A2                NotAvailableForSubscription  eastus2    ['1', '2', '3']
Basic_A3                NotAvailableForSubscription  eastus2    ['1', '2', '3']
Basic_A4                NotAvailableForSubscription  eastus2    ['1', '2', '3']
....

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

ID: cca70845-100f-2cfd-aba3-34b7fa4a5264
Version Independent ID: 475b26e5-9e23-f769-3bd5-cbc4a678dbf0
Content: Azure Availability Zones overview
Content Source: articles/availability-zones/az-overview.md
Service: azure
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@jstott Thanks for the question! We are investigating and will update you shortly.

@jstott I am also having issues selecting East US 2. @iainfoulds do you have any information you could share on this?

@iainfoulds - Thanks for the confirmation & details! Closing.

It is referring to Central US specifcally.


Coordination/cross pollination with CVE JSON format

Hi, I'm looking for the person(s) to talk to about coordinating and bouncing ideas around with respect to the JSON data format you are using, and the JSON CVE data format (which I'm largely to blame for =). I can be reached via email at<EMAIL_ADDRESS>I apologize for using the issues to contact you but it wasn't clear from the commits who is best to talk to), thanks.

I'll follow up over email :)

Ok so one question would be around using resource urls, e.g. the
Debian | deb://dist(optional):arch:name:version | deb://lucid:i386:acl:2.2.49-2
I have a similar proposal for the CVE JSON format, essentially "Aliases" that are effectively a key:value store where the key is the namespace name, and the value is whatever, e.g.:
RedHat-RPM:some-rpm-1.2.3-5.el7.x86_64.rpm
github.com:grafeas/grafeas
twitter:somehandle
and so on. Each name space would have defined rules, e.g.: "full file name of RPM supplied by RedHat" or "organization or username, a slash and then repo name in github.com" for example. Generally speaking I imagine namespaces would be defined by either the "owner" of the namespace (e.g. Red Hat/Github) or by the CVE people (board or a working group I guess, details TBD) if it has enough value and the owner isn't available/interested.
My question would be why did you go with a URI format? Is it defined somewhere? Who decides the namespace names/values/rules/etc? Thanks

#65 is open for moving resourceUrl to the purl spec - https://github.com/grafeas/grafeas/issues/65. It seems like your suggestion is similar but different for purl.  Its probably worthwhile to review the purl spec and leave comments in #65 or on the spec itself is you see issues here.
I believe for our beta version we'll adopt purl, so far there haven't been objections to that format.


Task: Show error message if map fails to load

Describe the task
When the map fails to fetch a pmtiles file from Google Cloud, hide loading spinner and show an error message in src/components/PropertyMap.tsx
Currently, the map page shows the loading spinner spins endlessly with the message "Loading properties." This makes for a poor user experience.
Acceptance Criteria

[ ] Hide loading spinner
[ ] Show error message instead of "Loading properties"
[ ] Show error message saying, "We are having technical issues. Please try again later."

Additional context

This ticket is related to #709. While working on that PR, I noticed that if the map page got a 404 error for the pmtiles file, it would get stuck on "Loading properties." The loader would spin endlessly.
Here's a screenshot of what that looks like to a user:

Can I pick up this task?


Topic: Accessibility [++specificity lens]

Creating bilingual design prototype of the Accessibility topic to iterate forward from

https://www.figma.com/file/AVmCvoB3Xg7tX5iRDdPNC2/Alpha-II?node-id=156%3A482&t=QtwCayFAZTCUMXLs-4

Exploring content enhancements:

considering a wider scope of resources that get more specific and fill gaps
categorizing types of resources that might figure within this topic
meeting with Eman (as SME) to dive deeper into options and opportunities
prototyping a future version based on raw materials at disposal

Opportunities/Blockers

Articulate the the value of accessibility within government services
Identify specific in-product examples/exemplars

Transferred to new repo: https://github.com/cds-snc/resources-content-design/issues/5


Make async-std compile for wasm32-unknown-unknown

Addresses the first point of #220: making the crate compile for wasm32-unknown-unknown.
All we have to do is to only depend on mio when appropriate, and to return an error when the user attempts to create a TCP or UDP connection.
I can see mostly three use cases for WASM: no-std, browers, and desktop. In the first two situations, TCP and UDP aren't available. In the third situation, the only way we could implement TCP/UDP are through some custom syscalls, which is exactly what WASI is.
In other words, to me, if you're compiling for wasm32-unknown-unknown, there is no situation where you would have TCP/UDP available to you.
It is debatable whether we should return an error at runtime or make TcpListener, TcpStream and UdpSocket unavailable at compile-time, but I went for erroring at runtime in order to mimic what the standard library does.
I'm opening this PR as a draft. I've updated async_std::net::udp to return an error when the operating system is "unknown", but since the changes are a bit opinionated, I wanted some feedback before doing the same for TCP.

It seems to fail on a missed cfg (TcpListener) and a warning about unused code, which we should deactivate for those locations.
I'm not sure if I agree with the strategy: libstd to my knowledge does it for compatibility of legacy codebases, which we don't have. On the other hand, I see this legacy building, because people may not start with WASM support immediately.
https://travis-ci.com/async-rs/async-std/jobs/237796226

It seems to fail on a missed cfg (TcpListener) and a warning about unused code, which we should deactivate for those locations.

I know it's broken, the PR isn't finished :sweat_smile:
Before finishing it I wanted to ask if I'm doing the right thing, notably w.r.t. disabling at runtime vs at compile-time.

@tomaka Yeah, I mainly got into the habit of documenting what's currently broken, as Travis interface got really slow to click through... Should have marked it as such.

This is now ready for review.
From a usability perspective, I tend to prefer the "panic at runtime" strategy.
This way, people can compile their existing code to wasm32-unknown-unknown without having to add tedious cfg_if! blocks.
Additionally, when it comes to sockets and file descriptors, even on Linux you can't rely on the fact that they're going to work. The OS might just refuse them to you for whatever reason pleases it.
Returning an error that says "TCP and UDP aren't available on this platform" on WASM isn't very different from returning an error that says "the kernel has decided to not allow you to open a socket" on Windows or Linux.

Would it make sense to return io::Error of kind "Other" in that case?

That's what I'm doing. I don't really see any kind that's more appropriate. Maybe "PermissionDenied".

I suppose that this PR is blocked on hesitations about the design?

@tomaka sorry about the delay; I guess between flu and travel everyone kind of fell off the map. I'm meeting up with @stjepang tomorrow, and we should probably chat about how to move this forward. WASM support is definitely something we want, and being able to move this forward would be fantastic!

I would like to get that landed, soon, to make sure we still have some time to best it before release.

I would like to get that landed, soon, to make sure we still have some time to best it before release.

This PR is kind of the starting point to supporting WASM, but we need a couple more changes before it actually works.
If the 1.0 release is planned for November 7th, it's almost a bit too late.

@tomaka sorry about this PR being held up. This def feels like it's been on me.
So in its current form this changes the code around quite a bit by delegating to specific methods. Which usually would be fine, but we have a lot of code, and I fear this might complicate it somewhat.
I think ideally we would have an attribute to blank out internal impls in WASM, somewhat like this:
impl PathBuf {
    #[not_browser]
    pub async fn canonicalize(/* args */) -> io::Result<()>;
}

But for compilation performance reasons we don't really want to depend on proc macros. So instead I've been thinking about is perhaps we could write a macro_rules macro similar to our extension_trait! macro in src/utils.rs that would stub out implementations for WASM.
io_struct! {
    struct PathBuf {}
    impl PathBuf { /*impl goes here */ }
}

Currently I believe all IO structs' methods become no-ops. If we wanted more fine-grained control we could perhaps follow pin-project-lite's lead and introduce a similar attribute (#[no_browser] or similar).
How does this sound?

I'm not sure how to implement that without introducing more complexity in the code than what this PR introduces.
For example we need to override the From<std::net::...> implementations, the Incoming iterator of the TcpListener, and the Read/Write traits. Doing so through a macro that wraps around everything is far from being easy.

@tomaka ah yeah, that's really fair.
Alternative suggestion: let's model this directly like std:
src/
    sys/
        wasm/
            net.rs
            fs.rs
            os.rs
        windows/
            # etc.
        unix/
            # etc.

Perhaps windows  and unix should be merged into a single file (common?, native?), or perhaps re-export from each other. But by following the way std is setup it might make this nicer to work with overall, perhaps?
I guess my current thinking is that the cfg_if blocks inside the different files don't feel great. If someone wants to find out a TcpListener is created, the implementation will live somewhere in the middle of a file together with all other platform code, perhaps hidden behind an else statement. Rather than having a logical place in the file hierarchy (e.g. src/sys/native/net.rs).
Does this make sense?

I've been thinking about his a little and I think there's an opportunity for a different design here. Currently, we're approaching this like libstd, where cargo or our build tooling can't help us. We're not in the sysroot, though.
How about having a feature flag wasm32, which switches everything that we can't support off? I'm not sure how feasible this is maintenance wise or if there's a better approach to reach this.
Essentially, the goal would be that users that want to make their application compatible with WASM environments could rely on async-std with the wasm feature on, so that they will never accidentally use API that isn't intended for WASM.
The danger I see is having to label a lot of async-std as "not compatible with wasm", but we already kinda have to do that?

Thank you, fixed in #757


PAM authentication issue

I prematurely closed #318, (see 2 below) and PAM authentication remains an issue.
Some other symptoms/behaviors:

user remains logged in while interrupting and restarting JupyterHub (no login required after hub restart). Not sure that this is unintended, just sayin.

in the situation above (restarting JupyterHub after interupt, with user remaining logged in by default) allows for one subsequent login after logout. But only one.

logging out after login results in PAM error on subsequent login.

Seems like it should be relatively easy to reproduce/confirm if it's not peculiar to running on OS X, or my particular settings.

user remains logged in while interrupting and restarting JupyterHub (no login required after hub restart).

Yes, that's intended. Restarting the Hub shouldn't have any effect on who is logged in; that state is persisted to the database. If you clear the login state of the Hub, users will be logged out, but restarting does not do this.
My guess is the other issues are related to the recent session changes, where it opens a PAM session but doesn't close it. I cannot actually reproduce the issue, though. What system are you running on with what config? I've tested current master on OS X and Linux with no issues so far. Is yours a managed system that might do clever things on login?

Thanks for checking. I'm running OS X 10.10.5 out of the box, without any management.
Just checked that jupyterhub is current:
haze:~/python/jupyterhub$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
Also checked on pamela:
haze:~/python/pamela$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
Here's my config, also seemingly straightforward.
c = get_config()
c.JupyterHub.ssl_key = '/path/to/key'
c.JupyterHub.cookie_secret_file = '/path/to/jupyterhub_cookie_secret'
c.JupyterHub.ssl_cert = '/path/to/cert'
c.JupyterHub.port = 443
c.Authenticator.whitelist = {'mate','jt',}
c.Authenticator.admin_users = {'mate'}

PAM sessions are now closed in single-user shutdown


Accept-Encoding not preserved when following redirects

See: https://github.com/guzzle/guzzle/issues/541
Note: this is fixed in Guzzle 4

Looks like Accept-Encoding is not preserved even for normal requests as well. I'm seeing this issue when using the Cache plugin with a Vary: Accept-Encoding response header. Example:
$client->get('a-url)->addHeader('Accept-Encoding', 'gzip')->send(); // a-url returns a 'Vary: Accept-Encoding' header
$client->get('a-url)->addHeader('Accept-Encoding', 'gzip')->send();

CURL output is:
* Connected to ....
> GET ... HTTP/1.1
Host: ....
Accept: */*
Accept-Encoding: gzip
User-Agent: Guzzle/3.9.2 curl/7.44.0 PHP/5.6.12
Via: 1.1 GuzzleCache/3.9.2

< HTTP/1.1 200 OK
< Date: Mon, 28 Sep 2015 15:20:07 GMT
< Server: Apache/2.4.16 (Unix) OpenSSL/1.0.2d mod_fastcgi/mod_fastcgi-SNAP-0910052141
< X-Powered-By: PHP/5.6.12
< Expires: Tue, 29 Sep 2015 15:20:07 GMT
< Vary: Accept-Encoding
< Cache-Control: max-age=86400
< Content-Encoding: gzip
< Last-Modified: Mon, 28 Sep 2015 15:20:05 GMT
< ETag: "..."
< Content-Length: 28326
< Content-Type: text/css; charset=utf-8

Although in both requests I set the same Accept-Encoding, the Cache plugin reported a cache MISS. Digging into the cache plugin's code I found out that both requests don't contain Accept-Encoding so there's nothing to compare between them.


add configuration file for solarshed.server

There are several things that are currently constants within the project.
It would be helpful to allow folks the ability to easily override these things via environment variables and/or a solarshed configuration file.    Please introduce support to adjust configuration settings for things like:

USB port to use for Renogy Rover connection
time delay in between metric collection from the connected solar charge controller

this should help to address some of the items that popped up in #5