Sharing button?

What benefit will it provide if there is a sharing button?

How

Email (Gmail)
Embedded link

Content

Plain text/ Rich text
Gist link

I don't see a point for the sharing button. Users can easily copy&paste the snippet to their IM or email.

That said, a "copy gist link" button would be nice.

@tmr232 I can reopen it if it deserves a discussion.

Share options:

GitHub Gist link
website embedded link
plain text
html tag
pdf

Personally, my preferred way to share this would be a gist link. I spent a while searching the UI to make sure there was no such option.

@tmr232 Sorry. Yes, it a gist link is useful.

@tmr232 Something like this?

This looks great!
Haven't had time to test it though (changed some files for the Enterprise integration, so I need to build it myself).


Separate thread pool for blocking publish operations

Seems that the current implementation of message publishing has some deficiencies. It uses native Rabbit MQ client as a transport and its basicPublish operation can block a thread what can lead to several problems like API freezing (in case if it uses the same thread pool), overall performance degradation, etc... So i suggest either moving all operations related to basicPublish to a separate thread pool (fixed?) or try to use NIO rabbit MQ client API (not sure whether it will help) in order to resolve the problem.

In the meantime, I think you can get away by wrapping the publishing call in a blocking execution context. Either using ContextShift or Blocker if using a newer version of cats-effect. Something like:
def publishSimpleMessage[F[_]: Sync](blocker: Blocker[F], publisher: String => F[Unit]): F[Unit] =
  blocker.blockOn(publisher("Hello world!"))

Or in older versions:
def publishSimpleMessage[F[_]: ContextShift: Sync](publisher: String => F[Unit]): F[Unit] =
  ContextShift[F].evalOn(publisher("Hello world!"))


How to query a search?

Hey, can you make an example on how to use the q (regex) query?

Hi @UrbanSwati
Could you clarify what regex are you meaning ?
do you mean about querymen ?
In this case, you should check the documentation of this plugin.
Let me know if you have a problem.

Can you make an example of this


Prevent floating navigation from blocking the text header in fragmented urls

partials/floating-header.hbs blocks the H1-H6 header texts in fragmented urls. So, as a workaround, we will need to delegate a few space above the header.
Without this PR, the page would look something like this:

With this PR, the page would look something like this:

Nice fix 👍  - if you can make this specific to .post-full-content rather than global, just below line 668 then would be happy to merge

@JohnONolan done! 😉

haha, and you found a more sane place for it, too! Thanks! 🥇


Library name change request

Library repository URL
https://github.com/m5stack/M5-Ethernet

@Gitshaoxiang He will finish the work.

Hi @IcingTomato. I see the tag has been made and am now confirming your request.
Unlike submissions, this type of request is still handled manually. The Library Manager index maintainer occasionally comes through to clear all the outstanding requests. They will close this issue when it is done. You will get a notification from GitHub at that time.
After that, you can monitor the indexing of the library via its dedicated logs web page.
Information about that here:
https://github.com/arduino/library-registry/blob/main/FAQ.md#can-i-check-on-library-releases-being-added-to-library-manager


makefile

you can put this into repo if you want.
everything works.... your description in the readme make it easy to make this work.
MAC only. can make it work on Windows and Linux with a bit more work.

BIN_NAME=deeplx
BIN_FSPATH_NAME=.bin
BIN_FSPATH=$(BIN_FSPATH_NAME)
BIN=$(BIN_FSPATH)/$(BIN_NAME)

build:
	go build -o $(BIN) .
	# .bin
build-cross:
	chmod +x ./.cross_compile.sh
	 ./.cross_compile.sh
	# dist

WEB_URL=http://<IP_ADDRESS>:1199
build-run: $(BUILD)
	$(BIN) -h
	# http://localhost:1199/

run-test:
	@echo ""
	@echo "GET"
	curl -H "Content-Type: application/json" -X GET $(WEB_URL)/

	@echo ""
	@echo "POST"
	curl -d '{"text":"hello", "source_lang":"EN", "target_lang":"DE"}' -H "Content-Type: application/json" -X POST $(WEB_URL)/translate
	# {"code":200,"data":"hallo","id":157799001}%

## install to bin

BIN_MAC_INSTALL_FSPATH=/usr/local/bin/$(BIN_NAME)
BIN_MAC_INSTALL_WHICH=$(shell which $(BIN_NAME))

bin-print:
	@echo ""
	@echo "BIN_MAC_INSTALL_FSPATH:        $(BIN_MAC_INSTALL_FSPATH)"
	@echo "BIN_MAC_INSTALL_WHICH          $(BIN_MAC_INSTALL_WHICH)"

bin-install:
	#sudo mv deeplx_darwin_amd64 /usr/local/bin/deeplx
	sudo cp $(BIN) $(BIN_MAC_INSTALL_FSPATH)
bin-install-del:
	rm -f $(BIN_MAC_INSTALL_WHICH)
bin-start:
	$(BIN_MAC_INSTALL_WHICH)
bin-test:
	$(MAKE) run-test

### install as service

SERVICE_MAC_PLIST_NAME=me.missuo.deeplx.plist
SERVICE_MAC_LAUNCH_AGENTS_FSPATH=$(HOME)/Library/LaunchAgents
SERVICE_MAC=$(SERVICE_MAC_LAUNCH_AGENTS_FSPATH)/$(SERVICE_MAC_PLIST_NAME)

service-print:
	@echo ""
	@echo "SERVICE_MAC_LAUNCH_AGENTS_FSPATH:    $(SERVICE_MAC_LAUNCH_AGENTS_FSPATH)"
	@echo "SERVICE_MAC_PLIST_NAME:              $(SERVICE_MAC_PLIST_NAME)"
	@echo "SERVICE_MAC:                         $(SERVICE_MAC)"
	@echo ""
service-print-list:
	# check ours is there
	ls -al $(SERVICE_MAC_LAUNCH_AGENTS_FSPATH)
service-install:
	cp $(REPO_NAME)/$(SERVICE_MAC_PLIST_NAME) $(SERVICE_MAC)
	launchctl load $(SERVICE_MAC)
service-install-del:
	launchctl unload $(SERVICE_MAC)
	rm -f  $(SERVICE_MAC)
service-test:
	$(MAKE) run-test
service-start:
	@echo "service start"
	launchctl start $(SERVICE_MAC)
service-stop:
	@echo "service stop"
	launchctl stop $(SERVICE_MAC)

Thanks. @gedw99

https://github.com/gedw99/sc-make/blob/main/assets/.sc-make/make/go.mk#L113 Shows one way to switch based on OS.
You can then modify the BIN names based on the OS . Like needing .exe for windows

I don't seem to need this makefile, I can implement it via Action to compile all versions automatically every time I push.

All the the GitHub Workflows can just call your make targets too.
example: https://github.com/gedw99/sc-make/blob/main/.github/workflows/ci.yaml
The CI is calling this: https://github.com/gedw99/sc-make/blob/main/makefile#L17

I don't seem to need this makefile, I can implement it via Action to compile all versions automatically every time I push.

It’s better imho to do the opposite.
the GitHub action I gave you is generic and calls the makefike.
the advantage is that whatever working on your laptop is exactly what happens on GitHub CI

Can you create a new pull request? I can learn it.


Break a test on purpose

Pull Request Test Coverage Report for Build 82

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 58.747%

Totals

Change from base Build 80:
0.0%

Covered Lines:
225

Relevant Lines:
383

💛  - Coveralls


migrate-formula-pr: new command

I love the idea here but I'm concerned we'd have three dev-cmd/*-formula-pr.rb with pretty similar code. Any chance you could get some code sharing going on between them?

boneyard-formula-pr is a special case of migrate-formula-pr as far as I can tell.

@zmwangx yup, it can be replaced with something that runs brew migrate-formula-pr --tap=boneyard, or an equivalent api.

@ilovezfs Any news here? Given we're trying to pull things from taps rather than the other way around will this still be useful?

It would be used as
brew migrate-formula-pr --tap=core foo

so the question would be whether those migrations are likely to be done in bulk, or one at a time.

@ilovezfs Probably a couple at a time until we're confident then en masse.

Let's pass on this given we're migrating things in here rather than out there now.


polymake: 4.6 -> 4.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/polymake/versions.
meta.description for polymake is: "Software for research in polyhedral geometry"
meta.homepage for polymake is: "https://www.polymake.org/doku.php"
meta.changelog for polymake is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.7 with grep in /nix/store/wsbpjkpsa2k60s08n55lvx54dj99qsnk-polymake-4.7
found 4.7 in filename of file in /nix/store/wsbpjkpsa2k60s08n55lvx54dj99qsnk-polymake-4.7

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
polymake

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wsbpjkpsa2k60s08n55lvx54dj99qsnk-polymake-4.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A polymake https://github.com/r-ryantm/nixpkgs/archive/999e37a21a34ce911dea9bf0b08ee6bf1acd73ab.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wsbpjkpsa2k60s08n55lvx54dj99qsnk-polymake-4.7
ls -la /nix/store/wsbpjkpsa2k60s08n55lvx54dj99qsnk-polymake-4.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

polymake

Maintainer pings
cc @timokau @omasanori @7c6f434c @collares for testing.

You're totally correct, but I still haven't added polymake as a Sage dependency :( I've been meaning to do it for ages.
I think polymake is broken on master due to the Perl upgrade, and this seems to fix it.

I see, then it is probably fine. Thank you!


Adapt NetworkPolicys according to recent refactorings

How to categorize this PR?

/area dev-productivity ops-productivity networking security
/kind enhancement
What this PR does / why we need it:
This PR adapts the NetworkPolicys according to the recent refactorings in gardener/gardener
See also https://github.com/gardener/gardener/pull/7589 and https://github.com/gardener/gardener/blob/master/docs/concepts/resource-manager.md#networkpolicy-controller.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/7352
Special notes for your reviewer:
/cc @rfranzke @oliver-goetz @timuthy
Depends on<EMAIL_ADDRESS>to create the expected network policies in the extension namespace.
Release note:

Adapted extension components to support the [FullNetworkPoliciesInRuntimeCluster](https://github.com/gardener/gardener/blob/master/docs/deployment/feature_gates.md#list-of-feature-gates) feature gate introduced by `gardener/gardener` v1.66, see [here](https://github.com/gardener/gardener/blob/master/docs/concepts/resource-manager.md#networkpolicy-controller) and [#7352](https://github.com/gardener/gardener/pull/7589) for more information.

I guess we need here to also set the metrics port on the svc.

We could also explicitly define the metrics port in the service. However, also other extensions do not specify the metrics port, e.g. https://github.com/gardener/gardener-extension-provider-aws/pull/714/commits/f028217278575cae3c296430b5d6840f81a23778. For extensions with a webhook usually that port is explicitly exposed.
Do you want to also expose the metrics port (unlike some other extensions)?


[Snyk] Fix for 4 vulnerabilities

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements.txt

⚠ Warning
celery 5.3.0 requires kombu, which is not installed.

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

611/1000  Why? Recently disclosed, Has a fix available, CVSS 6.5
Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5914629
cryptography:  41.0.3 -> 41.0.4
No
No Known Exploit

711/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.8
Untrusted Search Path SNYK-PYTHON-GITPYTHON-5871282
gitpython:  3.1.32 -> 3.1.35
No
Proof of Concept

586/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Directory Traversal SNYK-PYTHON-GITPYTHON-5876644
gitpython:  3.1.32 -> 3.1.35
No
Proof of Concept

980/1000  Why? Currently trending on Twitter, Mature exploit, Recently disclosed, Has a fix available, CVSS 9.6
Heap-based Buffer Overflow SNYK-PYTHON-PILLOW-5918878
pillow:  9.5.0 -> 10.0.1
No
Mature

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)
🦉 Directory Traversal

Checkmarx One – Scan Summary & Details – d8c400cf-a6fb-42e0-b6bf-ce220f98bd65
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

XPath_Injection
/dojo/tools/qualys_webapp/parser.py: 152
Attack Vector

XPath_Injection
/dojo/tools/qualys_webapp/parser.py: 154
Attack Vector

XPath_Injection
/dojo/tools/qualys_webapp/parser.py: 152
Attack Vector

XPath_Injection
/dojo/tools/qualys_webapp/parser.py: 154
Attack Vector

CSRF
/dojo/finding/views.py: 484
Attack Vector

CSRF
/dojo/finding/views.py: 481
Attack Vector

CSRF
/dojo/test/views.py: 83
Attack Vector

CSRF
/dojo/test/views.py: 81
Attack Vector

CSRF
/dojo/finding/views.py: 481
Attack Vector

CSRF
/dojo/finding/views.py: 626
Attack Vector

CSRF
/dojo/finding/views.py: 945
Attack Vector

CSRF
/dojo/finding/views.py: 1022
Attack Vector

CSRF
/dojo/test/views.py: 379
Attack Vector

CSRF
/dojo/test/views.py: 396
Attack Vector

CSRF
/dojo/test/views.py: 379
Attack Vector

CSRF
/dojo/jira_link/views.py: 359
Attack Vector

CSRF
/dojo/test/views.py: 280
Attack Vector

CSRF
/dojo/engagement/views.py: 218
Attack Vector

CVE-2007-2379
Npm-jquery-3.7.0
Vulnerable Package

CVE-2014-6071
Npm-jquery-3.7.0
Vulnerable Package

Filtering_Sensitive_Logs
/dojo/api_v2/views.py: 1263
Attack Vector

Filtering_Sensitive_Logs
/dojo/api_v2/views.py: 1263
Attack Vector

Filtering_Sensitive_Logs
/dojo/api_v2/views.py: 1263
Attack Vector

Filtering_Sensitive_Logs
/dojo/api_v2/views.py: 1263
Attack Vector

Filtering_Sensitive_Logs
/dojo/api_v2/views.py: 1263
Attack Vector

Filtering_Sensitive_Logs
/dojo/api_v2/views.py: 1263
Attack Vector

Filtering_Sensitive_Logs
/dojo/api_v2/views.py: 1263
Attack Vector

Filtering_Sensitive_Logs
/dojo/api_v2/views.py: 1263
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 166
Attack Vector

Object_Access_Violation
/dojo/reports/views.py: 809
Attack Vector

Object_Access_Violation
/dojo/finding/views.py: 163
Attack Vector

Privacy_Violation
/dojo/benchmark/views.py: 77
Attack Vector

IAM Access Analyzer Not Enabled
/_config.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/detect-merge-conflicts.yaml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/Unusual Behaviors-User-Persistence IAMUser-NetworkPermissions.json: [43](https://github.com/TheRedHatter/django-DefectDojo/blob/snyk-fix-c1ddf8db5b5318e813e23874cf9e8874//unittests/scans/asff/guardduty/Unusual Behaviors-User-Persistence IAMUser-NetworkPermissions.json#L43)
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/JIRAImportAndPushTestApi.test_import_with_groups_twice_push_to_jira.yaml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/core-team.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/repeated_findings.json: 44
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/bundlewatch.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/JIRAImportAndPushTestApi.test_import_with_push_to_jira_update_tags.yaml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/JIRAImportAndPushTestApi.test_import_with_push_to_jira_epic_as_issue_type.yaml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/release-2-tag-docker-push.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/docker-compose.override.integration_tests.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/shims.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/docker-compose.override.unit_tests.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/docker-compose.override.dev.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/k8s-tests.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/release-x-manual-helm-chart.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/JIRAImportAndPushTestApi.test_import_add_comments_then_push_to_jira.yaml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/release_drafter_valentijn.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/vulnerabilityreport_no_vuln.json: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/unit-tests.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/dependabot.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/release-x-manual-docker-containers.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/JIRAImportAndPushTestApi.test_import_no_push_to_jira_reimport_push_to_jira_is_false_but_push_all_issues.yaml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/docker-compose.override.debug.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/release-drafter.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/JIRAImportAndPushTestApi.test_engagement_epic_mapping_disabled_create_epic_and_push_findings.yaml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/sidebar.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/labeler.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/JIRAImportAndPushTestApi.test_engagement_epic_mapping_enabled_create_epic_and_push_findings.yaml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/refresh_helm_lock_file.yaml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/browser-bugs.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/one_finding.json: 44
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/JIRAImportAndPushTestApi.test_import_no_push_to_jira_reimport_no_push_to_jira_but_push_all_issues.yaml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/browserstack.yml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/JIRAImportAndPushTestApi.test_import_with_groups_push_to_jira.yaml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled
/JIRAImportAndPushTestApi.test_import_with_push_to_jira_add_comment.yaml: 1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions

IAM Access Analyzer Not Enabled

More results are available on AST platform


Not being able to open Notion pages.

Hi there. I can't open anything from Notion with this extension. For example, this page. I can open it in browser, but the VSCode just shows VSCode Notion: Loading... in the bottom right corner for 2-3 seconds and dissapears. Nothing else happens. Maybe I need to provide some additional info?

Hmmm, that page loads and works perfectly well for me though.

It might not be related to the webview if the tab doesn't open at all. If so can you check and share the error log in the console if any exists? You can open the console from Help > Toggle Developer Tools.

Hmmm, that page loads and works perfectly well for me though.

It might not be related to the webview if the tab doesn't open at all. If so can you check and share the error log in the console if any exists? You can open the console from Help > Toggle Developer Tools.

I'm having a similar problem. The test page opens just fine, but a non-test page doesn't do anything.

I'm having a similar problem. The test page opens just fine, but a non-test page doesn't do anything.

It gives me this:

It gives me this:

I'm having the same problem!

I'm having the same problem!

Does the error persist? I mean

Is the error happening to only certain pages?
Do you still have that error after trying multiple times?
Is the error happening to all pages and the extension is not usable at all?

And can you guys open this URL https://notion-api.frenco.dev/v1/page/320213fb70ba48169059a17fa9dc195c? To check if it's caused by the server in your VPN area or not.

Does the error persist? I mean

Is the error happening to only certain pages?
Do you still have that error after trying multiple times?
Is the error happening to all pages and the extension is not usable at all?

And can you guys open this URL https://notion-api.frenco.dev/v1/page/320213fb70ba48169059a17fa9dc195c? To check if it's caused by the server in your VPN area or not.

No, error is happening to all pages. I tried like 10 of different ones, same result.
Yes, the error is the same after a lot of tries.
Yes, it basically adds two commands to comand pallette, you give it a link, it shows a message of loading and then never does anything else.

And yes, the link is openable in any browser. It returns a JSON with info about the page.

No, error is happening to all pages. I tried like 10 of different ones, same result.
Yes, the error is the same after a lot of tries.
Yes, it basically adds two commands to comand pallette, you give it a link, it shows a message of loading and then never does anything else.

And yes, the link is openable in any browser. It returns a JSON with info about the page.

It is definitely a weird bug, it's not reproducible on my machine, and according to the log, the error comes from this line
if (Object.keys(res.data).length < 1) {
  throw new Error("Couldn't load the data from API.")
}

which is only the case when the data return from API looks like this,
{}

If viewing the API in the browser doesn't look like that, it's super weird. Then, the only case possible would be that res.data is null. I have no idea why it would be though.
May I know your VSCode version, and basic information about your machine model so that I can go through VSCode issues and check for one similar to the case? You can get the version from code -v.

It is definitely a weird bug, it's not reproducible on my machine, and according to the log, the error comes from this line
if (Object.keys(res.data).length < 1) {
  throw new Error("Couldn't load the data from API.")
}

which is only the case when the data return from API looks like this,
{}

If viewing the API in the browser doesn't look like that, it's super weird. Then, the only case possible would be that res.data is null. I have no idea why it would be though.
May I know your VSCode version, and basic information about your machine model so that I can go through VSCode issues and check for one similar to the case? You can get the version from code -v.

Results from code -v:
1.52.1
ea3859d4ba2f3e577a159bc91e3074c5d85c0523
x64

Here is my VSCode about text.

My machine is Huawei MateBook D14, AMD Ryzen 5 3500U.
Though, there are other people who has the same bug, I doubt there is something to do with the machine.

Results from code -v:
1.52.1
ea3859d4ba2f3e577a159bc91e3074c5d85c0523
x64

Here is my VSCode about text.

My machine is Huawei MateBook D14, AMD Ryzen 5 3500U.
Though, there are other people who has the same bug, I doubt there is something to do with the machine.

Omg I think I know what the error is. I parse the notion URL to get the ID using a regex something like this,
const pattern = /(?:https?:\/\/)?(?:www\.)?notion\.so\/([\w\.-]*)*\/?/

so it only matches public links without a username, so you have to use it as
# like this
https://www.notion.so/Test-page-for-VSCode-notion-extension-320213fb70ba48169059a17fa9dc195c
# not like this
https://www.notion.so/yaripey/Test-page-for-VSCode-notion-extension-320213fb70ba48169059a17fa9dc195c

You can get the absolute URL from the Share > Copy Link in Notion.

Omg I think I know what the error is. I parse the notion URL to get the ID using a regex something like this,
const pattern = /(?:https?:\/\/)?(?:www\.)?notion\.so\/([\w\.-]*)*\/?/

so it only matches public links without a username, so you have to use it as
# like this
https://www.notion.so/Test-page-for-VSCode-notion-extension-320213fb70ba48169059a17fa9dc195c
# not like this
https://www.notion.so/yaripey/Test-page-for-VSCode-notion-extension-320213fb70ba48169059a17fa9dc195c

You can get the absolute URL from the Share > Copy Link in Notion.

v1.0.1 will contain a fix for this, by parsing URLs containing usernames. Feel free to reopen the issue if you think it's not the culprit after trying in v1.0.1.

v1.0.1 will contain a fix for this, by parsing URLs containing usernames. Feel free to reopen the issue if you think it's not the culprit after trying in v1.0.1.

Yes! Without username it works fine. The only note I would like to make is that Share > Copy Link still adds username to the path, at least for me. So the only way to obtain a working absolute link is to remove the username from the path manually. Good to hear that it will be fixed in v1.0.1, waiting for it. Thanks.

Yes! Without username it works fine. The only note I would like to make is that Share > Copy Link still adds username to the path, at least for me. So the only way to obtain a working absolute link is to remove the username from the path manually. Good to hear that it will be fixed in v1.0.1, waiting for it. Thanks.

GETTING ERROR AGAIN!
error is = "Couldn't load the data from API. "

Same

Currently getting the same issue, but when copying the link in notion there is no user or file path to change. I copy and paste to VScode and I get the "Couldn't load the date from API" or "Request failed with status code 404" errors in the bottom right corner. I am not running a VPN. I tried to publish the page and add it to a workgroup neither resolved the issue.


[BUG]: very long shtter lag after cheeeeese

Describe the bug
i installed the script after a fresh bookworm installation on a raspberry pi 4. The webui works fine, the load is always under 5%, the pi has nothing to do.
If i take a picture (gphoto2 with Sony Alpha 7C or another Sony Alpha) it requires 15-20 seconds to the shutter! If i tke the picture from the terminal with the gphoto2 command, it takes 2-3 seconds.
I see in htop, that after 3-2-1-cheeese 10-15 seconds pass away before the job of gphoto2 appears! The load of the pi is always under 5%.
After gphoto2, the animation with the circle appears, processing of the picture requires 20-30% load.
What can i do that photobooth starts gphoto2 immediately?
Thank you, its a nice software.
Steps to reproduce the behavior
fresh raspberry os on rpi 4
Sony Alpha 7c
Expected behavior
taking a picture immediately or starting gphoto2 immediately
Photobooth Version
4.5.1
Browser and browser version
firefox on windows, firefox on android
Operating System
raspberry os debian 12
Did it work before?
No
Latest working version
No response
Additional context
No response

You can try one of the alternative capture commands mentioned in the FAQ.
Please also take a look at the browser console while Loglevel is set to 2.
https://photoboothproject.github.io/faq/#alternative-capture-commands
Photobooth v4 stable branch only gets compatibility updates, bugs won't be looked at.
If the issue persist please install latest development version and check there.

I am currently having similar issues with a fresh installation. I tried to debug the problem with a system of a 5-second countdown with a live view of the DSLR camera.
After clicking on the take picture button, the countdown starts, and the live view is shown immediately in the background (which is great). After 5 seconds, "Cheeeeeeese" is displayed on the screen, and the Console log shows the Capture image. message. Just afterward, the camera makes the picture with the flash (also directly after the countdown ends, without a long waiting time). Until now, everything works as expected. After this, the photobooth stays in the "Cheeeeeeese" screen, even if the picture is taken. After a waiting time (which is the problem and too long), the console says Taking picture took 12860ms. The rest of the process is as expected. The processing screen is shown for a short time and the image is correctly shown on the screen. So the problem must be related while "Cheeeeeese" is shown, right after the Capture image. message. The 12860ms for taking a picture is way too long.
https://github.com/PhotoboothProject/photobooth/blob/fe24e40ed73715e122eef29171b4a50f54ff66f5/assets/js/core.js#L575
Maybe it is also a configuration problem. Any idea why it takes so long?

@mhellmeier like mentioned, try one of the mentioned commands. If using go2rtc for preview simply replace the word gphoto2 with the word capture.
The JavaScript is waiting for the response of the capture command to continue and end the cheese.

And also use a cheese time of 0 if using live preview


Remove redundant calls to .OrTimeout()

Pulled up the calls to .OrTimeout() into the WatchableApp.
The main problem was .StartWatcherAsync().OrTimeout(). This applies a 30 second timeout to a piece of the test that calls dotnet-restore. Tests on CI often timeout because of this. The dotnet-restore is already gated by a timeout of 120 seconds, so the .OrTimeout() is unnecessary in most places.
Should resolve #336

:shipit:
FYI @Eilon


Improve Error Logging for deserialization during event batch parsing

Is your feature request related to a problem? Please describe.
It's been seen that, in some unknown ways, alien events can pop up in Nakadi event types and as expected they do not comply with event type schema therefore deserialization issues occur. When investigating these issues the log doesn't tell us what partition, offset nor provides the alien events making investigation and resolution much harder.
Describe the solution you'd like
Improve error logging for Nakadi Reader to provide as much information as possible in case of issues during batch parsing.
Describe alternatives you've considered
Considered a localized workaround in the client though it'd leave fahrschein same behaviour across projects.

Closed via https://github.com/zalando-nakadi/fahrschein/pull/466 . Thanks @as-belcastro


Update aws-core, http-client-spi, ... to 2.17.250

Updates

software.amazon.awssdk:aws-core
software.amazon.awssdk:http-client-spi
software.amazon.awssdk:netty-nio-client

from 2.17.249 to 2.17.250.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #929.


Add github workflow to build library

I created this PR to validate this issue as I am not able to build the library on my machine.
We could add this to the project to validate the builds from this point onwards.
Link to a run of the workflow

Thanks for this!


Archive the old -pubsub repo

Archive the repository, with a prominent note in the README explaining where the development will continue.

Archived. https://github.com/googleapis/google-cloud-cpp-pubsub


Chunk doesn't get forceloaded if it's already loaded

Cause:
forceload add ~ ~ is only executed after the return that's run when the chunk is already loaded

Fixed in v1.1.1


static_src and image_not_found.jpg

In oscar 3.0 (beta & master), when image_not_found.jpg is not found, I am getting

ImproperlyConfigured("Please copy/symlink the 'missing image' image at /path/to/project/public/media/image_not_found.jpg into your MEDIA_ROOT at /path/to/project/public/media. This exception was raised because Oscar was unable to symlink it for you.")

The message is illogical.
Digging around I find my existing symlink is broken, pointing to /path/to/oscar_repo/../static/oscar/img/image_not_found.jpg when it should be pointing to static_src.
It would be nice if the MissingProductImage was able to detect a broken symlink and deletes it before trying to recreate it.

The message is illogical.

Yeah, the first argument to that string is wrong - I'll fix that shortly.

When it should be pointing to static_src.

No, the path it's trying to use is correct - all of static_src is copied into oscar/static when the build is packaged for PyPi (or if you run make assets on a local copy of Oscar, which you need to do to access any of it's static assets).

It would be nice if the MissingProductImage was able to detect a broken symlink and deletes it before trying to recreate it.

I'm not sure that it is a good idea for Oscar to make potentially desctructive changes to the host filesystem - even if the symlink is broken we cannot assume that it used to point to Oscar's image instead of something else. I think we should still just report an exception in this case (and hopefully a corrected exception message will help).

The message is illogical.

Yeah, the first argument to that string is wrong - I'll fix that shortly.

When it should be pointing to static_src.

No, the path it's trying to use is correct - all of static_src is copied into oscar/static when the build is packaged for PyPi (or if you run make assets on a local copy of Oscar, which you need to do to access any of it's static assets).

It would be nice if the MissingProductImage was able to detect a broken symlink and deletes it before trying to recreate it.

I'm not sure that it is a good idea for Oscar to make potentially desctructive changes to the host filesystem - even if the symlink is broken we cannot assume that it used to point to Oscar's image instead of something else. I think we should still just report an exception in this case (and hopefully a corrected exception message will help).


Noscript still seems to not be working

Implementing the noscript as commented here does not seem to be loading the iframe properly
Loading on the standard way, we can see the source and the network requesting the content

When using the:
useHead({
        noscript: [
          {
            children: `<iframe src="https://www.googletagmanager.com/ns.html?${serialize(params)}" height="0" width="0" style="display:none;visibility:hidden"></iframe>`,
            tagPosition: 'bodyOpen'
          }
        ]
      })

Besides seeing the iframe being loaded as a string, we don't see any network activity at all

I have added a stackblitz to show this is not working properly.
I'm loading both iframes, but I can only find the first one as a real element
https://stackblitz.com/edit/nuxt-starter-v3etsl?file=app.vue

I tried your reproduction, it looks like it loads correctly when you disable javascript?

Not sure why you're trying to test it using scripts :upside_down_face:. If you can provide a reproduction where it doesn't work with scripts disable I'm happy to investigate


[CH-367] fix CH will continue to execute after JNI call fail

Changelog category (leave one):

Bug Fix (user-visible misbehavior in official stable or prestable release)

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
This pr fix the problem invoked by #305 , if don't throw CH exception, CH will continue to execute after JNI call failed. So it should throw a Clickhouse Exception with the JNI exception message so the root cause will be shown in spark.
It close #367 .

Can one of the admins verify this patch?

test this please

test this please

test this please


HBASE-27819 10k RpcServer.MAX_REQUEST_SIZE is not enough in Replicati…

…onDroppedTable related tests
Also modified the tests so we will only start the cluster once instead of start it in setUpBeforeClass and then restart it when running the actual test method

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 17s
Docker mode activated.


How to use the updateProfileImageWithHttpInfo function?

Trying to update a profile image for a User using the api, found this function but can really figure out how to use it to send the profile picture? The documentation here is also not clear: https://docs.docusign.com/esign/restapi/Users/Users/updateProfileImage/
I understand I should PUT the image, but under which name is the API expecting it?
Regarding the SDK, I can see there are two variables for the httpBody (function is declared here: https://github.com/docusign/docusign-php-client/blob/master/src/Api/UsersApi.php#L3062):

$formParams: which is declared inside the function as an empty array.. thus its always empty.
and $_tempBody, which is never declared thus isset($_tempBody) is always false.

See here for a reference of the above: https://github.com/docusign/docusign-php-client/blob/master/src/Api/UsersApi.php#L3106
Any ideas?

I apologize for the slow response to questions and issues. We have reorganized to give you responses sooner.
Please advise if this is still an open issue for you.
Thank you,
Larry

Hey Larry, thanks for your answer. I'm no longer participating in that project so I'm gonna close the thread now.
Best,
Juan


Fix #60: duplicate field status on pnpm mock-data

Resolves #60 by updating foundry docker image:

this project already uses a nightly image, so simply updating to the      latest nightly (and pinning it) is enough to mitigate the issue.

Have tested with pnpm@latest with node 18 on all three projects:

smart-turret
smart-storage-unit
smart-gate

Thanks for the fix :-)


Operation Serenity Ledger

closing since this was just used for experimenting with github projects. thanks again @vfrsilva :raised_hands:


Remove some dead code related to Env Vars

Related to https://github.com/microsoft/vscode-jupyter/issues/10359

Codecov Report

Merging #10816 (650fdf9) into main (b1eaca7) will increase coverage by 0%.
The diff coverage is 100%.

@@          Coverage Diff           @@
##            main   #10816   +/-   ##
======================================
  Coverage     63%      63%
======================================
  Files        481      481
  Lines      33628    33625    -3
  Branches    5488     5487    -1
======================================
+ Hits       21250    21273   +23
+ Misses     10327    10309   -18
+ Partials    2051     2043    -8

Impacted Files
Coverage Δ

src/platform/interpreter/activation/types.ts
100% <ø> (ø)

...ommon/process/environmentActivationService.node.ts
72% <100%> (+<1%)
:arrow_up:

src/kernels/jupyter/baseKernelConnectionWrapper.ts
30% <0%> (-3%)
:arrow_down:

src/standalone/api/kernelApi.ts
72% <0%> (-2%)
:arrow_down:

src/kernels/helpers.ts
61% <0%> (-1%)
:arrow_down:

src/kernels/common/baseJupyterSession.ts
78% <0%> (-1%)
:arrow_down:

src/platform/msrCrypto/msrCrypto.js
16% <0%> (-1%)
:arrow_down:

src/kernels/variables/debuggerVariables.ts
68% <0%> (+<1%)
:arrow_up:

...lPythonAndRelatedNonPythonKernelSpecFinder.node.ts
71% <0%> (+<1%)
:arrow_up:

.../notebooks/controllers/vscodeNotebookController.ts
82% <0%> (+1%)
:arrow_up:

... and 9 more


calculator: "PalmDetectionCpu"

Hi, calculator: "PalmDetectionCpu" is not available in source code but it has been used in hand_detection_desktop.pbtxt,
Could you please let me know when it will be available?

Hi @sambath-krian , did you get a chance to check this issue.


"associated type Output not found for C" on Nightly 2024-10-30

Compile error on the latest nightly:
error[E0220]: associated type `Output` not found for `C`
   --> src/concurrent_stream/mod.rs:104:48
    |
104 |     async fn drive<C>(self, consumer: C) -> C::Output
    |                                                ^^^^^^ associated type `Output` not found

For more information about this error, try `rustc --explain E0220`.
error: could not compile `futures-concurrency` (lib) due to 1 previous error

Nightly 2024-10-29 builds without issue.

Thanks for filing this! I just tried to repro this on cargo 1.84.0-nightly (69e595908 2024-11-16) and it seems to have been resolved. Let me know if there are still any issues on recent nightlies and we can reopen this.


Eliminating dependence on jquery

There are some issues with sorting inside elements in your version (Chrome, FF, Edge). Please fix them and then I'll merge your pull request. Thanks!

You could tell me if the error persists. or if you find more? Thank you

It seems to work well in viewer, but there are still issues with ordering available items/options in questions builder, eg in:
src/builder/question-offered-answer-list-builder.directive.js
src/builder/question-division-builder.directive.js
src/builder/question-grid-builder.directive.js
In src/builder/question-priority-list-builder.directive.js ordering still works strange, eg try dragging first item to last position.

waiting for next release for strange behavior in question-priority-list-builder.directive PR(https://github.com/RubaXa/Sortable/pull/624) when used drag-handle.


nitter: unstable-2021-07-18 -> unstable-2021-12-31

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[x] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Flatty update breaks Pixie, but I will fix that.


[FLINK-26119][connectors/common] AsyncSinkWriterStateSerializer to @PublicEvolving

What is the purpose of the change
AsyncSinkWriterStateSerializer is annotated @Internal, however downstream modules need to extend this class. Therefore it should be marked @PublicEvolving.
Brief change log

AsyncSinkWriterStateSerializer swtiched from @Internal to @PublicEvolving

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? n/a

ArchitectureTest passes on CI.


Error with getLanguageId on latest version

Hey @CGNonofr, it looks like the latest changes from #301 are breaking for me.
Relevant installed versions:
@codingame/monaco-jsonrpc: 0.3.1
@codingame/monaco-languageclient: 0.17.0
monaco-editor: 0.30.1
@monaco-editor/react: 4.3.1
@monaco-editor/loader: 1.2.0

Here's a stack trace, appears the problem is in onDidChangeTextDocument
helpers.ts:111 Uncaught TypeError: model.getLanguageId is not a function
    at MonacoWorkspace.setModel (monaco-workspace.ts:71)
    at MonacoWorkspace.addModel (monaco-workspace.ts:48)
    at new MonacoWorkspace (monaco-workspace.ts:23)
    at create (monaco-services.ts:30)
    at Object.install (monaco-services.ts:35)
    ...

Oh, looks like there's a 0.28 cached Monaco somewhere...
editor@0.28.1/min/vs/editor/editor.main.js:60:13525)
    at https://cdn.jsdelivr.net/npm/monaco-editor@0.28.1/min/vs/editor/editor.main.js:573:12639
    at Array.map (<anonymous>)
    at https://cdn.jsdelivr.net/npm/monaco-editor@0.28.1/min/vs/editor/editor.main.js:573:12628
    at Generator.next (<anonymous>)
    at https://cdn.jsdelivr.net/npm/monaco-editor@0.28.1/min/vs/editor/editor.main.js:60:13728
    at new Promise (<anonymous>)
    at ke (https://cdn.jsdelivr.net/npm/monaco-editor@0.28.1/min/vs/editor/editor.main.js:60:13525)
    at s (https://cdn.jsdelivr.net/npm/monaco-editor@0.28.1/min/vs/editor/editor.main.js:573:12526)
    at https://cdn.jsdelivr.net/npm/monaco-editor@0.28.1/min/vs/editor/editor.main.js:639:1471
    at S (https://cdn.jsdelivr.net/npm/monaco-editor@0.28.1/min/vs/editor/editor.main.js:60:14204)
    at r.runner (https://cdn.jsdelivr.net/npm/monaco-editor@0.28.1/min/vs/editor/editor.main.js:639:1445)
    at r.doRun (https://cdn.jsdelivr.net/npm/monaco-editor@0.28.1/min/vs/editor/editor.main.js:60:17977)
    at r.onTimeout (https://cdn.jsdelivr.net/npm/monaco-editor@0.28.1/min/vs/editor/editor.main.js:60:17943)
    ...

Problem solved: my dependency @monaco-editor/loader was pinned to load 0.28.1


Feature Request: standard two-way communication pipe between puppeteer ←→ target

Hey folks, there's been quite a few times where I've been wanting a way to do 2-way communication between puppeteer and the page.
Right now it's possible to do but seems quite ad-hoc, these are the ways I can think of:
Puppeteer → Page:

create a custom function on the page, then use puppeteer to evaluate it
use the low-level "sendMessageToTarget" method to send a custom command (untested)
add a JS script to the page.

Puppeteer ← Page:

have puppeteer intercept requests, make a custom request from the page
have puppeteer listen for console events and utilize console.log on the page

Maybe I'm missing a better way to set this up? Thanks!

As for Puppeteer ← Page, there is also page.exposeFunction().

Got it, thanks for clarifying!


⚠ Jenkins Plugins Artifactory has degraded performance

In 21afa23, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1943 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 753f5a4 after 12 minutes.


[refactor](dynamic table) remove dynamic table

This is the first step for variant type
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.34 seconds
stream load tsv:          543 seconds loaded<PHONE_NUMBER>9 Bytes, about 131 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.3 seconds inserted 10000000 Rows, about 341K ops/s
storage size:<PHONE_NUMBER>6 Bytes

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.19 seconds
stream load tsv:          541 seconds loaded<PHONE_NUMBER>9 Bytes, about 131 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.2 seconds inserted 10000000 Rows, about 342K ops/s
storage size:<PHONE_NUMBER>7 Bytes

run buildall

run buildall

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 45.47 seconds
stream load tsv:          538 seconds loaded<PHONE_NUMBER>9 Bytes, about 132 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.2 seconds inserted 10000000 Rows, about 342K ops/s
storage size:<PHONE_NUMBER>6 Bytes

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 45.81 seconds
stream load tsv:          540 seconds loaded<PHONE_NUMBER>9 Bytes, about 132 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.3 seconds inserted 10000000 Rows, about 341K ops/s
storage size:<PHONE_NUMBER>3 Bytes


@MongoId and @MongoObjectId test coverage improvements.

In Jongo 1.2, @MongoId and @MongoObjectId only work under a few specific conditions.  This PR aims to make @MongoId and @MongoObjectId more general, using a parameterized test (org.jongo.marshall.jackson.IdSpecTest).
Goal
Get all of the following to be generally true:

If Jackson sees a property named _id, that is the id property for Mongo.
If Jackson sees @MongoIdon a property, that property is named _id according to Jackson.
If Jackson sees @MongoObjectId on a property, that property is serialized as an ObjectId.
@MongoId and @MongoObjectId will not alter other ObjectMapper instances that see them.

What has changed

Reflection is no longer used to inspect instances for the _id property and its value.  Instead, Jackson's view of the type is used to determine the property's value and type in Mongo.  The implementation can be found in org.jongo.marshall.jackson.JacksonObjectIdUpdater.
The Serializer and Deserializer were widened, so that property/annotation combinations like public @MongoObjectId ObjectId _id; will just no op.
The *@*MongoId and *@*MongoObjectId annotations are no longer AnnotationBundles, as these were not getting applied for MixIns.  This functionality is now supported directly by org.jongo.marshall.jackson.JongoAnnotationIntrospector.
JUnit rules org.jongo.util.JongoEmbeddedRule and org.jongo.util.MongoEmbeddedRule have been introduced with the same functionality as JongoTestCase.
Several other tests were added to the test suite dealing with IDs and MixIns.

Fixes #272

@bguerout this PR still needs to be squashed, but it should be in good enough shape for review.

@bguerout If these changes look good as is, give me one more day to clean up the few issues I am aware of (author annotations and formatting) and I will squash this into a clean commit.

Be aware, the way I structured this PR is confusing.  There are relevant notes on #273 that are not showing up here.

Not sure why, but it looks like the project previously had an embedded mongo rule and it was converted into a subclass of JongoTestCase.  No clue why.  https://github.com/bguerout/jongo/commit/4184d320f255e5e552a76a7e935938b9f7958839

The way that MongoId and MongoObjectId are handled in this project may not be the best.  Jackson's BeanSerializationModifier and BeanDeserializationModifier are better for tasks like this.

@bguerout I have implemented all of your notes and squashed this into a single commit.  I believe it is now complete.

Thanks for the great work

Thanks for the great project!
On Nov 4, 2015, at 12:31 AM, Benoit Guérout<EMAIL_ADDRESS>wrote:

Thanks for the great work
—
Reply to this email directly or view it on GitHub.

This fix can be tested in an early version.
This version must be considered as a SNAPSHOT of future 1.3 release
<dependencies>
  <dependency>
    <groupId>org.jongo</groupId>
    <artifactId>jongo</artifactId>
    <version>1.3-early-20151113-0140</version>
  </dependency>
</dependencies>
...
<repositories>
    <repository>
       <id>cloudbees-jongo-early-release</id>
        <url>http://repository-jongo.forge.cloudbees.com/release</url>
        <releases>
            <enabled>true</enabled>
        </releases>
        <snapshots>
            <enabled>false</enabled>
        </snapshots>
    </repository>
</repositories>


Graphics Output Converters

gridGraphics: Redraw Base Graphics Using 'grid' Graphics
Functions to convert a page of plots drawn with the 'graphics' package into identical output drawn with the 'grid' package. The result looks like the original 'graphics'-based plot, but consists of 'grid' grobs and viewports that can then be manipulated with 'grid' functions (e.g., edit grobs and revisit viewports).


Allow empty commits in HL Python Wrapper

Similar to this: https://github.com/treeverse/lakeFS/pull/7186

@treeverse/product

@itaiad200 this is a quick win and I'd like to take advantage of the SDK release tomorrow


in onRequest method, some one maybe has eq logic like method === 'post'

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

in my project code like this:
onRequest({ options }) {
        // ...
        let { method } = options;

        if (method === "post") {
          options.body.traceId = "xxxxxxxxxxxx"
        }
        // ...
}

If the toUpperCase method is executed before
context.options.onRequest(context)

Then the parameters will never be added to options.body or options.params
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Hi dear @mythshuazi thanks for the pull request but actually this behavior is to make sure you write your logic to check method against upper case always and reduce chances of not working code.

Hi dear @mythshuazi thanks for the pull request but actually this behavior is to make sure you write your logic to check method against upper case always and reduce chances of not working code.

@pi0 Thank you for your guidance


Replace rubocop with govuk-lint

This Pull Request:

Removes the Rubocop config files (.rubocop.yml and .disabled-rubocop.yml) from our repo
Removes the "rubocop" Gem from our Gemfile
Adds the "govuk-lint" Gem to our Gemfile

The "govuk-lint" Gem contains both Rubocop and a number of Cops that help enforce the GOV.UK Styleguide.
We weren't actively using Rubocop so I'm hoping this'll be a fairly uncontroversial change. Assuming this is OK, I'll open another PR to get govuk-lint-ruby added to jenkins.sh and Rake.

LGTM :+1:


added error messages for bulk and get

Error messages were not send for some use cases

small refactor
added sending missing error messages

Codecov Report

Merging #132 (8773daa) into develop (5489b56) will decrease coverage by 0.34%.
The diff coverage is 12.50%.

@@             Coverage Diff             @@
##           develop     #132      +/-   ##
===========================================
- Coverage    63.32%   62.97%   -0.35%
===========================================
  Files           35       35
  Lines         1524     1537      +13
===========================================
+ Hits           965      968       +3
- Misses         559      569      +10

Impacted Files
Coverage Δ

..._connect_for_snmp_poller/manager/task_utilities.py
22.67% <12.50%> (+0.02%)
:arrow_up:

Continue to review full report at Codecov.

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

:tada: This PR is included in version 1.5.0-develop.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Saved search initial-pull limit

When you create a new saved-search, the plugin pulls in some amount of "initial content".  (Content that already existed when you created the search).  Then it checks for new content on a cron.
I think we've started with a default of something like "25" for the initial-pull limit.  This ticket is to make that value configurable when you're creating a new saved-search.  (But you can't edit the value on existing saved-searches, since it's no longer applicable).

This done in 777dace270088b260293b062b366ff79bc021e72.
Example of the UI:

Left: before saving a search query, the user can specify an initial pull limit.
Right: after the search query is saved and the cron task runs, the entire "Initial pull limit" area of the form is disabled, but displayed for posterity.

One qualm: the default isn't really the default - you have to explicitly fill it in.

Snuck in a fix for this with #94. See here.

Need to QA this one.

Confirmed!


@/codeforafrica client side search

Description
This PR implements client side search using Fuse.js. Search is available on the following pages:

[x] Our work,
[x] Stories,
[x] About, and
[x] Opportunities

Type of change

[x] New feature (non-breaking change which adds functionality)

Screenshots

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas

What if rather than filtering all item based on the search text, display the title and maybe context of the searched text under the search bar, i.e display a few words next or after the text searched.

Good suggestions @kelvinkipruto but for MVP we try to stick close to the design so that we can give comprehensive feedback and make any/necessary improvements afterwards.


Question not issue: ASP.NET Core 1.1 Identity dependencies and all Data Access in a separate class library project

I have extracted most of the Database related code from an ASP.NET Core Web Application project with Individual User Accounts, ie. Identity into an ASP.NET Class Library project. I am now stuck in the final pieces which is to remove the concrete assignment to EF Core and moving the connection strings to the Data project.
Here is what I have done so far:
Created a blank solution
Created an ASP.NET Core web application (TestPatterns.Web) with Individual User Accounts
Updated all the Nuget packages
Created a Class Library Core package
In the Class Library Project (TestPatterns.Data) Nuget -> Removed the NetStandard Library 1.6, replaced with Microsoft.NetCore.App 1.1.0
In the Class Library Project (TestPatterns.Data), added all the EF and Identity Nuget Packages
Nuget Packages
https://i.stack.imgur.com/N9cxF.png
Moved over of the 'Data' folder from the Web application to the class library project
Moved over the ApplicationUser.cs file from the Web Application to the class library project folder Models
I end up with a structure like this:
https://i.stack.imgur.com/ZYe93.png
To run a migration I execute the following on the Data project folder:
dotnet ef --startup-project ../TestPatterns2.Web migrations add First
Looking for some help on removing all dependencies of EF Core 1.1 from the Web project and moving the connection strings over to the Class Library Project. Also, would the DI remain in the Web project or should that move to the Data project also? If so, how?
Asked the same question in Stack Overflow: http://stackoverflow.com/questions/42054438/asp-net-core-1-1-identity-dependencies-and-all-data-access-in-a-separate-class-l

You probably won't be able to remove the dependencies from the web project, since the code in controllers and views is going to make use of ASP.NET Identity and EF.
You would also typically leave the registration of services in the web project (i.e. these lines from Startup.cs):
            // Add framework services.
            services.AddDbContext<ApplicationDbContext>(options =>
                options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection")));

            services.AddIdentity<ApplicationUser, IdentityRole>()
                .AddEntityFrameworkStores<ApplicationDbContext>()
                .AddDefaultTokenProviders();

So I think the answer to your question is that you've done about as much separation as you would really want to do. You could look at moving connection strings, but then you'd be breaking away from the typical ASP.NET Core pattern of reading config in Startup.cs etc.


index.md

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

I'm update the index.md, with add the source link to learn intro og computer science from edx.org.

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Reason: We do not accept PRs which only add links when there are already valid reference links for the article.  Instead of just adding a link, it would be great if you can add original content. Paraphrased content from another source should be referenced.
Thank you and happy coding.


Routes, feature flag, stub views and initial API request spike for Workload Metrics page

Implements the following stories (I know... the next PR will be smaller!):

https://issues.redhat.com/browse/RHOAIENG-2535 - Stub for new page
https://issues.redhat.com/browse/RHOAIENG-2567 - Context architecture / data fetching spike
https://issues.redhat.com/browse/RHOAIENG-2850 - Data fetching for status overview donut chart
https://issues.redhat.com/browse/RHOAIENG-2851 - Data fetching for status trends line chart
https://issues.redhat.com/browse/RHOAIENG-2853 - Data fetching for workloads table

Description

This PR establishes the following new things:

StackComponent.KUEUE, for the new kueue DataScienceCluster component
A disableDistributedWorkloads feature flag in the OdhClusterConfig CRD
SupportedArea.DISTRIBUTED_WORKLOADS, which requires both of the above in order to enable the new page via useIsAreaAvailable()
The new "Workload Metrics" page and nav item, corresponding to...
...the new route /distributedWorkloads/* and its subroutes, which are dynamically generated based on...
...the useDistributedWorkloadsTabs hook, which returns a config object that defines the tabs at the top of the new page.

The isAvailable property here for both tabs is currently just whether the new SupportedArea is available, but can also be used to restrict individual tabs by RBAC or other logic. The root /distributedWorkloads route redirects to the first available tab based on this logic.
The projectSelectorMode here dictates whether there is a project dropdown on each tab, and if so, whether it allows the "all projects" selection or not. Currently both tabs are set to singleProjectOnly (if no project is selected when you reach the page, one will be selected automatically).
isAvailable and projectSelectorMode were originally implemented because we had a "Data science cluster metrics" tab that was going to be for admins only and was not going to have a project selector, and because the "Workload status" tab was originally also going to allow "all projects". I considered removing these two features as they are no longer currently leveraged, but they seem useful in case we need them later. If reviewers prefer, we could just remove them (and perhaps the whole useDistributedWorkloadsTabs hook in favor of hard-coded routes/tabs).

New components in frontend/src/pages/distributedWorkloads/global (the "Workload Metrics" page):

GlobalDistributedWorkloads - The page's root component. Determines what to render or redirect based on whether there are projects, which tab corresponds to the current route and whether that tab needs a valid selected project. If all is well, renders the DistributedWorkloadsContextProvider (see below) wrapped around...
...GlobalDistributedWorkloadsTabs - Renders the tab bar and the active tab's ContentComponent (based on useDistributedWorkloadsTabs). Retains the selected project if present when navigating between tabs that have a project selector.
GlobalDistributedWorkloadsProjectMetricsTab - The content for the "Project metrics" tab. Currently renders some raw placeholder JSON from the projectMetrics data provided by the new context (see below).
GlobalDistributedWorkloadsWorkloadStatusTab - The content for the "Workload status" tab. Currently renders some raw placeholder JSON from the workloadCurrentMetrics and workloadTrendMetrics data provided by the new context (see below).
DistributedWorkloadsToolbar - The toolbar at the top of each of these tab content components, with the project dropdown and placeholders for refresh interval and time range dropdowns.

As stated in a TODO comment here, this should probably be replaced with the existing MetricsPageToolbar which could be decoupled from model metrics and moved somewhere common in a future PR.

A new frontend/src/concepts/distributedWorkloads directory, where we can put DW-related things that could possibly be used in other places in the UI other than the "Workload Metrics" page (like future settings pages, or anywhere else that wants to show a few of these metrics). In here we have:

DistributedWorkloadsContext, which wraps each of the rendered routes that need to consume DW-related API data. This is similar to other React context providers in the UI: it provides state like the current refresh rate, last update time for charts, and fetched API data.
useClusterQueues and useWorkloads, described below.

Two new backend prometheus routes /api/prometheus/query and /api/prometheus/queryRange, which came from a discussion with @andrewballantyne (the existing /pvc, /bias and /serving routes here are repetitive and all could be replaced with one of the two generic endpoints). There is a TODO comment for this.
A few Cypress tests to ensure that the new nav item and route exist if and only if both the kueue component is installed and the feature is turned on.

More tests will come in a future PR -- I will open a Jira task for this and it will be required for the feature epics to be considered done. (Jira issue TBD)

Types, models, API functions and hooks for listing k8s CRs from Kueue:

ClusterQueueKind/listClusterQueues/useClusterQueues - Not currently used. This was implemented when I thought we needed it for "Data science cluster metrics", but I left it in because we will need it for future admin settings pages and we may need it for the "project metrics" tab as well.
WorkloadKind/listWorkloads/useWorkloads - For the future table of individual workload statuses at the bottom of the "Workload status" tab.

Types, functions and hooks for Prometheus queries related to Distributed Workloads (in frontend/src/api/prometheus/distributedWorkloads.ts):

getDWProjectMetricsQueries / useDWProjectMetrics - Part of the spike for loading individual number values for the "project metrics" tab. Not currently comprehensive, we will need more single- and range-value queries for that tab.
getDWWorkloadCurrentMetricsQueries / useDWWorkloadCurrentMetrics - The single number value metrics for the future donut chart on the "Workload status" tab.
getDWWorkloadTrendMetricsQueries / useDWWorkloadTrendMetrics - The time-series range queries for the future status trends line chart on the "Workload status" tab.
For each of these 3 groups of metrics, there is a *MetricsValues type which defines keys and data types for the underlying metrics we want to load, a *MetricType type derived from those keys, and a mapped *Metrics type. This last type is what is returned by the use*Metrics hooks, and it is a FetchStateObject (data, loaded, error, refresh) whose data property is a mapping of *MetricTypes to inner FetchStateObjects for each individual metric. This allows us to define the names and types of data we need in one place and have TypeScript enforce that we are using those same keys everywhere we work with each of these groups of metrics. The outer FetchStateObject also encapsulates the loading/error/refresh state so each group of metrics is simpler to consume via context (no need to || all the loading booleans in rendering logic), while the inner FetchStateObjects still allow us to look inside and see the loading/error state of an individual metric or call the refresh function for an individual metric.
Note: I was originally going to copy the pattern used by get[Server|Model]MetricsQueries and the [Server|Model]MetricType enums. I went with this alternative pattern for two reasons:

Based on discussions with @andrewballantyne, I wanted to keep all of the queries and prometheus-related logic in ~/api/prometheus/* and out of ~/pages to avoid coupling the data structures to a specific page. The existing metrics stuff in ~/pages/modelServing is more coupled with page-specific code.
With the data source decoupled from the page where it is initially used, I saw value in grouping queries and metrics that are likely to be used together into separate nested objects so you can consume only what you need. It made sense to separate the source of truth for what data is in each of these groups of metrics and what their queries are and define them next to each corresponding hook using mapped types instead of enums.

If we prefer to stick to the enum pattern and/or a single flat bundle of metrics, I am totally happy to conform to that pattern instead. I also just have a general preference against enums that are 1:1 with the keys of an object when a keyof will suffice 😉 and I might have been trying to be too clever here.

A new usePrometheusNumberValueQuery helper hook to simplify the use of prometheus queries that return a single numeric value.
A new useMakeFetchObject utility hook which turns the [data, loaded, error, refresh] tuple returned by useFetchState into an object with named properties, which is easier to work with for our purposes. Note that this is factored out of the existing useContextResourceData which provided both this and a refresh interval implementation, but I wanted to be able to rely on the refreshRate option of useFetchState instead. Based on a discussion with @andrewballantyne , we probably want to eventually replace usages of useContextResourceData with useMakeFetchObject and that refreshRate option.

To correspond with this, a new type FetchStateObject and new constants DEFAULT_LIST_FETCH_STATE (for fetching arrays, value defaults to []) and DEFAULT_VALUE_FETCH_STATE (for fetching any type, value defaults to undefined) have been added.
I really am not sure about the name of useMakeFetchObject, suggestions are welcome.

There are also a few changes to existing code:

usePrometheusQuery now accepts an optional third parameter fetchOptions, which can be used to pass a refreshRate or initialPromisePurity option down into the underlying useFetchState call. This simplifies things when using refreshRate with useFetchState directly alongside these prometheus queries in the context provider.

The new parameter is optional and this change does not affect any existing consumers of usePrometheusQuery.

useFetchState.ts now exports its previously private FetchOptions type for use in usePrometheusQuery or elsewhere.
The defaultResponsePredicate and prometheusQueryRangeResponsePredicate that were previously in frontend/src/api/prometheus/serving.ts (as useCallbacks inline) have been moved to usePrometheusQueryRange.ts (as static exports). They are generically useful for any consumer of usePrometheusQueryRange, and the useCallbacks they were using were unnecessary (they had no dependencies, so the memoized functions didn't rely on anything from their upper scope and were effectively static already).

This change has no effect on the behavior of the original model serving code.

The useContextResourceData utility has been refactored to lift the tuple-to-object functionality out into useMakeFetchObject, described above.

The behavior is identical and this change does not affect any existing consumers of useContextResourceData.

The ProjectSelector component has been enhanced with an aria-label for better accessibility. This came up when I was consulting with the PatternFly team on how best to accessibly render labels for each of the toolbar dropdowns on the new page, and it will also make the other pages that use it more accessible. It has no visual effect on the rendered page.

I would be fine with removing this from this PR if desired, since it is the only thing that actually modifies the HTML output of existing pages.

There are various // TODO mturley comments in here for things beyond the scope of this PR that need to be addressed in future changes before the feature is released. I left them in order to have reminders in context (with my name on them for accountability, as opposed to open-ended TODOs that could be picked up by anyone in the future).

In particular, there are a few places where I said these imports from ~/pages/modelServing/* should be moved somewhere page-agnostic, which would have resulted in bloating this diff even more. It makes more sense to me to do that when we get to the point of abstracting out other reusable code from model serving metrics (coming up soon!)

How Has This Been Tested?

The majority of the development was done in local dev mode using @Fiona-Waters 's cluster. The data fetching has all been manually tested this way, including all of the prometheus queries (using past data from test workloads Fiona ran).
I have also fully deployed the image generated by CI for this PR on a new AWS cluster (dw-dashboard) set up for me by @anishasthana. On that cluster we properly set up the kueue component and set the feature flag in the DashboardConfig CR, and verified that the SupportedArea logic is working as expected (and that the new page is not accessible if either the feature is turned off or the kueue component is not installed).
For the things mentioned above under "a few changes to existing code", I poked around on other pages that consume the relevant code and confirmed that there are no changes to the behavior of existing consumers of those few small utilities I touched.
Test Impact

Currently, the only tests I wrote here are in frontend/src/__tests__/cypress/cypress/e2e/distributedWorkloads/GlobalDistributedWorkloads.cy.ts, where the tests verify that the SupportedArea logic works correctly and that none of the new code will leak to any users who don't have the kueue component installed and the new feature flag enabled.
As mentioned above, more unit and integration tests should be added in a future PR. The only reason I am not writing more tests in this PR is because it has run too long and that would risk not merging it in the current sprint, and because none of the untested code is exposed to any users who don't use the feature flag. I will follow up to open a Jira task and ensure more tests for this PR's code are added in future PRs.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[x] The developer has tested their solution on a cluster by using the image produced by the PR to main

Note that there is still an open question about RBAC for the kueue_* Prometheus metrics. @Fiona-Waters is working on that while I'm on PTO next week. I'll open another Jira issue to follow up and make sure a non-admin user can get data from all these queries.

@christianvogt addressed your feedback and rebased.

I've done an initial test to confirm that when the feature is disabled via feature flag there are no issues with leakage into the core dashboard features. Working on a bit deeper testing / review now.


libdatachannel: 0.21.0 -> 0.21.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/paullouisageneau/libdatachannel/releases.
meta.description for libdatachannel is: C/C++ WebRTC network library featuring Data Channels, Media Transport, and WebSockets
meta.homepage for libdatachannel is: https://libdatachannel.org/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.21.1 in filename of file in /nix/store/ad4s1z4yjdkh723917a24blyys6xk1k5-libdatachannel-0.21.1

Rebuild report (if merged into master) (click to expand)

40 total rebuild path(s)

40 package rebuild(s)

First fifty rebuilds by attrpath

libdatachannel
obs-studio
obs-studio-plugins.advanced-scene-switcher
obs-studio-plugins.droidcam-obs
obs-studio-plugins.input-overlay
obs-studio-plugins.looking-glass-obs
obs-studio-plugins.obs-3d-effect
obs-studio-plugins.obs-backgroundremoval
obs-studio-plugins.obs-command-source
obs-studio-plugins.obs-composite-blur
obs-studio-plugins.obs-freeze-filter
obs-studio-plugins.obs-gradient-source
obs-studio-plugins.obs-gstreamer
obs-studio-plugins.obs-hyperion
obs-studio-plugins.obs-livesplit-one
obs-studio-plugins.obs-move-transition
obs-studio-plugins.obs-multi-rtmp
obs-studio-plugins.obs-mute-filter
obs-studio-plugins.obs-nvfbc
obs-studio-plugins.obs-pipewire-audio-capture
obs-studio-plugins.obs-replay-source
obs-studio-plugins.obs-rgb-levels-filter
obs-studio-plugins.obs-scale-to-sound
obs-studio-plugins.obs-shaderfilter
obs-studio-plugins.obs-source-clone
obs-studio-plugins.obs-source-record
obs-studio-plugins.obs-source-switcher
obs-studio-plugins.obs-teleport
obs-studio-plugins.obs-text-pthread
obs-studio-plugins.obs-transition-table
obs-studio-plugins.obs-tuna
obs-studio-plugins.obs-vaapi
obs-studio-plugins.obs-vertical-canvas
obs-studio-plugins.obs-vintage-filter
obs-studio-plugins.obs-vkcapture
obs-studio-plugins.obs-webkitgtk
obs-studio-plugins.obs-websocket
obs-studio-plugins.waveform
obs-studio-plugins.wlrobs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ad4s1z4yjdkh723917a24blyys6xk1k5-libdatachannel-0.21.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libdatachannel https://github.com/r-ryantm/nixpkgs/archive/37132004622bd278fa33d3b2a2a5e8c01f599c25.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/37132004622bd278fa33d3b2a2a5e8c01f599c25#libdatachannel

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ad4s1z4yjdkh723917a24blyys6xk1k5-libdatachannel-0.21.1
ls -la /nix/store/ad4s1z4yjdkh723917a24blyys6xk1k5-libdatachannel-0.21.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

41 packages built:

libdatachannel
libdatachannel.dev
obs-studio
obs-studio-plugins.advanced-scene-switcher
obs-studio-plugins.droidcam-obs
obs-studio-plugins.input-overlay
obs-studio-plugins.looking-glass-obs
obs-studio-plugins.obs-3d-effect
obs-studio-plugins.obs-backgroundremoval
obs-studio-plugins.obs-command-source
obs-studio-plugins.obs-composite-blur
obs-studio-plugins.obs-freeze-filter
obs-studio-plugins.obs-gradient-source
obs-studio-plugins.obs-gstreamer
obs-studio-plugins.obs-hyperion
obs-studio-plugins.obs-livesplit-one
obs-studio-plugins.obs-move-transition
obs-studio-plugins.obs-multi-rtmp
obs-studio-plugins.obs-mute-filter
obs-studio-plugins.obs-ndi
obs-studio-plugins.obs-nvfbc
obs-studio-plugins.obs-pipewire-audio-capture
obs-studio-plugins.obs-replay-source
obs-studio-plugins.obs-rgb-levels-filter
obs-studio-plugins.obs-scale-to-sound
obs-studio-plugins.obs-shaderfilter
obs-studio-plugins.obs-source-clone
obs-studio-plugins.obs-source-record
obs-studio-plugins.obs-source-switcher
obs-studio-plugins.obs-teleport
obs-studio-plugins.obs-text-pthread
obs-studio-plugins.obs-transition-table
obs-studio-plugins.obs-tuna
obs-studio-plugins.obs-vaapi
obs-studio-plugins.obs-vertical-canvas
obs-studio-plugins.obs-vintage-filter
obs-studio-plugins.obs-vkcapture
obs-studio-plugins.obs-webkitgtk
obs-studio-plugins.obs-websocket
obs-studio-plugins.waveform
obs-studio-plugins.wlrobs

Maintainer pings
cc @erdnaxe for testing.

Result of nixpkgs-review pr 311961 run on x86_64-linux 1

40 packages built:

libdatachannel
libdatachannel.dev
obs-studio
obs-studio-plugins.advanced-scene-switcher
obs-studio-plugins.droidcam-obs
obs-studio-plugins.input-overlay
obs-studio-plugins.looking-glass-obs
obs-studio-plugins.obs-3d-effect
obs-studio-plugins.obs-backgroundremoval
obs-studio-plugins.obs-command-source
obs-studio-plugins.obs-composite-blur
obs-studio-plugins.obs-freeze-filter
obs-studio-plugins.obs-gradient-source
obs-studio-plugins.obs-gstreamer
obs-studio-plugins.obs-hyperion
obs-studio-plugins.obs-livesplit-one
obs-studio-plugins.obs-move-transition
obs-studio-plugins.obs-multi-rtmp
obs-studio-plugins.obs-mute-filter
obs-studio-plugins.obs-nvfbc
obs-studio-plugins.obs-pipewire-audio-capture
obs-studio-plugins.obs-replay-source
obs-studio-plugins.obs-rgb-levels-filter
obs-studio-plugins.obs-scale-to-sound
obs-studio-plugins.obs-shaderfilter
obs-studio-plugins.obs-source-clone
obs-studio-plugins.obs-source-record
obs-studio-plugins.obs-source-switcher
obs-studio-plugins.obs-teleport
obs-studio-plugins.obs-text-pthread
obs-studio-plugins.obs-transition-table
obs-studio-plugins.obs-tuna
obs-studio-plugins.obs-vaapi
obs-studio-plugins.obs-vertical-canvas
obs-studio-plugins.obs-vintage-filter
obs-studio-plugins.obs-vkcapture
obs-studio-plugins.obs-webkitgtk
obs-studio-plugins.obs-websocket
obs-studio-plugins.waveform
obs-studio-plugins.wlrobs


Compatibility with jwst pipeline v1.8.5

extract1d routines need to be updated to be compatible with latest jwst pipeline version.

 Update extract1d code using jwst v1.8.5

Addressed in #14.


Python: Fix bug in multi_assignment_points_to.

This turned out to be a fairly simple but easy to make bug. When we want to
figure out the value pointed-to in a multi-assignment, we look at the left hand
side to see what value from the right hand side we should assign. Unfortunately,
we accidentally attempted to look up this information in the left hand side of
the assignment, resulting in no points-to information at all. The only thing
needed to fix this was to properly link up the left and right hand sides: using
the left hand side to figure out what index to look at, and then looking up the
points-to information for the corresponding place in the right hand side.
This may not be the end of the road for how we handle tuples, but it's clearly an improvement on what we had, and I don't see any reason to not merge this as a unit.

I ended up doing both. :wink:

I shouldn't think so. The test that failed is looking at what nodes are unreachable (in a specific large-ish test file). This number went from 1185 to 1183, meaning that more nodes are reachable now. That doesn't strike me as unreasonable. Figuring out which nodes are now reachable is doable, but will be a bit of a hassle.

Tests are still failing :( does it also require performance evaluation?

Here's the dist-compare: https://git.semmle.com/gist/taus/c7118cf0d80ddbdb6fad091f57945440
Performance is mostly unchanged. :tada:
I need to look at the alert changes before we merge this.
Oh, and I was sure I'd fixed that Pruned.ql test, but I guess I didn't. At any rate, this particular test failure is nothing to worry about -- it's the same as above.

I've looked through the alert changes, and there are a bunch of false positives, but none that I think were caused by this PR. Rather, I think they were simply revealed by the less aggressive pruning that this PR produces. I'll create an issue to track these FPs, but I don't think they should block this PR (though I invite you to form your own judgement on this).

Here's a slightly dist-compare using a more recent master: https://git.semmle.com/gist/taus/2af791dce154bb01cfae59cf20c6992c

I think the variance on the Azure worker is large enough that we cannot rely on the timings in the dist-compare. I'm also pretty sure that this PR in no way makes analysis on salt faster, and yet that's what the numbers claim. Rather, the fact that the number of tuples has increased by a modest amount for each project seems reasonable to me.
(Also, intuitively I would expect smaller projects to exhibit larger variance wrt. timing, which is another reason to take these results with a grain of salt.)


GH158: Update to Cake 2.0 RC2

fixes #158

Can we back this out?
This should have targeted the release branch that is open.
I can get this sorted out later this afternoon.

Yip. I can fix it into the release branch.

@gep13 sorted.


button click copies undefined instead of the expected text

random page has this issue on the code snippet area when you click the "Copy" button

dips

Fixed in #323


Bot is not working anymore?

Today using the bot I try send_fleet() method, and is not working.
Can you fix it please?
Thanks!

I just tried it, and it works fine.
My test code looks like this:
bot = OGame(UNIVERSE, USERNAME, PASSWORD)
ids = bot.get_planet_ids()
ships = [(Ships['SmallCargo'], 1)]
speed = Speed['100%']
where = {'galaxy': 4, 'system': 208, 'position': 8}
mission = Missions['Transport']
resources = {'metal': 1, 'crystal': 2, 'deuterium': 3}
fleetID = bot.send_fleet(ids[0], ships, speed, where, mission, resources)
print("Fleet id:", fleetID)

Hi @alaingilbert,
I'm testing the code but is not working (fleetId is set to None). Any solution? How can I send you logs?
Thanks in advance!

Are you on discord ?
Feel free to add me, it'll be easier to communicate
agilbert
#2967

Hello i am trying to do the following:
ogame = OGame('Zibal', USER, PASW, domain="de.ogame.gameforge.com")
But i get a strange error, am i doing something wrong?
Traceback (most recent call last):   File "<pyshell#5>", line 1, in <module>     ogame = OGame('Zibal', USER, PASW, domain="de.ogame.gameforge.com")   File "C:\Python27\lib\site-packages\ogame\__init__.py", line 56, in wrapper     res = method(self, *args, **kwargs)   File "C:\Python27\lib\site-packages\ogame\__init__.py", line 39, in wrapper     return some_fn(ogame, *args, **kwargs)   File "C:\Python27\lib\site-packages\ogame\__init__.py", line 119, in __init__     self.login()   File "C:\Python27\lib\site-packages\ogame\__init__.py", line 56, in wrapper     res = method(self, *args, **kwargs)   File "C:\Python27\lib\site-packages\ogame\__init__.py", line 39, in wrapper     return some_fn(ogame, *args, **kwargs)   File "C:\Python27\lib\site-packages\ogame\__init__.py", line 125, in login     self.server_url = self.get_universe_url(self.universe)   File "C:\Python27\lib\site-packages\ogame\__init__.py", line 56, in wrapper     res = method(self, *args, **kwargs)   File "C:\Python27\lib\site-packages\ogame\__init__.py", line 39, in wrapper     return some_fn(ogame, *args, **kwargs)   File "C:\Python27\lib\site-packages\ogame\__init__.py", line 619, in get_universe_url     servers = self.get_servers(self.domain)   File "C:\Python27\lib\site-packages\ogame\__init__.py", line 56, in wrapper     res = method(self, *args, **kwargs)   File "C:\Python27\lib\site-packages\ogame\__init__.py", line 39, in wrapper     return some_fn(ogame, *args, **kwargs)   File "C:\Python27\lib\site-packages\ogame\__init__.py", line 611, in get_servers     for opt in select.findAll('option'): AttributeError: 'NoneType' object has no attribute 'findAll'
Thank you :)

obsolet


About multi-crop strategy.

Hi @HobbitLong ,
Thank you for your inspiring work.
I want to know did you attempt multi-crop strategy like SWaV in your experiments ?  And do you think it will work well under the supervised setting ?
Thanks.

We did not try (because SupCon is a work prior to SwAV). I am not sure how the multi-crop strategy would work for SupCon.


Error 404

An error has occurred.
404
ElectricityPriceApi.Exceptions.FailedToGetDayAheadPricesException
 at ElectricityPriceApi.HttpClients.EntsoeHttpClient.GetHourPrices(GetHourPricesArgs args) in D:\a\ElectricityPriceApi\ElectricityPriceApi\ElectricityPriceApi\HttpClients\EntsoeHttpClient.cs:line 44 at ElectricityPriceApi.Services.Prices.PriceService.GetAveragePrices(GetAveragePricesArgs args) in D:\a\ElectricityPriceApi\ElectricityPriceApi\ElectricityPriceApi\Services\Prices\PriceService.cs:line 64 at ElectricityPriceApi.Functions.PriceFunctions.RunAveragePrices(HttpRequest req, ILogger log) in D:\a\ElectricityPriceApi\ElectricityPriceApi\ElectricityPriceApi\Functions\PriceFunctions.cs:line 80

I'm not sure what's going on! Getting the same on all examples from entsoe as well. Maybe their api is down..
Going to do som research stay thuned!

Looks like they have change the api url. A fix is coming now

The service is up again


emby: 3.0.6060 -> 3.0.6070

Motivation for this change
New release: https://github.com/MediaBrowser/Emby/releases/tag/3.0.6070
Things done

[x] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Travis failed due to time limit :(
I built it locally without problems.


[FEATURE] Add bombadil watch to automatically sync configs on changes

Is your feature request related to a problem? Please describe.
Currently the default bombadil process is a bit annoying as on every config change, you have to remember to type bombadil link -p stuff.
Describe the solution you'd like
It would be nice for rapid config changes to be able to do just bombadil watch -p stuff and it would detect changes automatically on the dotfiles dir and then run bombadil link -p stuff. I think this would be easy to do when using watchexec as a lib.

That's a great idea !
Do you want to work on this @svenstaro ?

Sure, can do.

@oknozor @svenstaro Hi, it seems watch feature is finished, but there is no docs for it?