Central install still requires flameTimewarpML/locks to be world writeable

Is there an alternative to flameTimewarpML/locks being world writeable?  We have our deployments centralized, and non-admins should not be able to, or have to, write into the central repository.

https://github.com/talosh/flameTimewarpML/pull/82 should fix that @alanmcseveney  @talosh

Hi guys, I’d like to give you an access to the repository in order for you to be able to improve current v0.4 branch.
I’m quite focused on v0.5 now and don’t have much time at the moment to look through pull requests.
If you happen to know someone else from Flame community who would like to have it please let me know

On 11 Jul 2023, at 15:20, Dave Young @.***> wrote:
@alanmcseveney https://github.com/alanmcseveney have you updated to the referenced PR #82 https://github.com/talosh/flameTimewarpML/pull/82 ? im sure you can close this issue out @talosh https://github.com/talosh if so.
—
Reply to this email directly, view it on GitHub https://github.com/talosh/flameTimewarpML/issues/79#issuecomment-1630924219, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMBGYKGSEXRUNAKUW7HART3XPVOLVANCNFSM6AAAAAAURGAJGI.
You are receiving this because you were mentioned.


add command for draining a worker

makes a table, with a handler to indicate tasks shouldn't go to a specific bot, and querying on assignments.

i think once we go to rotate a few times we'll have a much better sense of expiring / removing draining


[release][website] Add release notes for Release 2.1.0

@merlimat  I have fixed the headline

retest this please


Fixup CI

Thanks @nonara, I'll try to get CI fixed up before merging your changes, and then republish

Coverage remained the same at 100.0% when pulling 5591609faf63abb1598a8326802501531ad3d061 on FixupCI into 201898d06cc3329e499d1230548b0b57a47e05eb on master.


fix: remove the test we already have coverage for

Description
This test is testing a case we already have coverage in the repository where the code resides[1]. We don't want to be testing the behaviour of EC in e2e tests but integration points between components.
This test started failing because it uses the up-to-date acceptable task bundles data and in those the policy rule no longer emits a warning because another rule in the same package emits a violation of using out-of-date (non acceptable) bundle.
See https://github.com/redhat-appstudio/infra-deployments/pull/2357
[1] https://github.com/enterprise-contract/ec-policies/blob/2d4adcbc0befbbc3e04c93a599dba4f89e581e82/policy/release/attestation_task_bundle_test.rego#L89-L107
Issue ticket number and link
Ref. https://issues.redhat.com/browse/HACBS-2592
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Made the code change without testing
Checklist:

[X] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

The test failed because the integration test related to one of the tests (unrelated to this PR) failed, I have my eyes on it.
/test redhat-appstudio-e2e

/retest

/test redhat-appstudio-e2e


HTTP service stop method doesn't do anything

Describe the bug
The HTTP service's Stop() method doesn't do anything. Its body just returns nil and there's a TODO comment indicating the functionality still needs to be implemented. This means that application blocking waiting for their dapr HTTP service to shutdown will wait indefinitely.
Here's the link to the TODO - https://github.com/dapr/go-sdk/blob/main/service/http/service.go#L49
To Reproduce
package main

import (
        "fmt"
        "time"

        daprd "github.com/dapr/go-sdk/service/http"
)

func main() {
        service := daprd.NewService(":8080")

        go func() {
                if err := service.Start(); err != nil {
                        // This should print, but it never does
                        fmt.Println("Service start completed")
                }
        }()

        service.Stop()
        time.Sleep(200 * time.Millisecond)
}

Expected behavior
Calling an HTTP service's stop method should stop the server and cause its Start method to return http.ErrServerClosed.

I also run into this issue and PR https://github.com/dapr/go-sdk/pull/210 with the fix.
Feel free to review and comment

/assign

I also opened #209 with a fix. I have test cases in that PR that might be useful in your #210 as well

@mnussbaum , right, I saw your PR after sending mine.
I've closed my PR in favor of yours!

Ah gotcha, thanks!


NFS / FsEvents failed to run

dinghy up
Starting the dinghy VM...
Starting NFS daemon, this will require sudo
Waiting for NFS daemon...
NFS mounting failed
Starting the FsEvents daemon
Starting DNS and HTTP proxy
Unable to find image 'codekitchen/dinghy-http-proxy:2.5' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:53424-><IP_ADDRESS>:53: read: connection refused.
See 'docker run --help'.
   VM: running
  NFS: stopped
 FSEV: stopped
  DNS: stopped
PROXY: stopped

NFS failed to run
details available in log file: /usr/local/Cellar/dinghy/4.6.5/local/var/dinghy-NFS.output

FsEvents failed to run
details available in log file: /usr/local/Cellar/dinghy/4.6.5/local/var/dinghy-FsEvents.output

To connect the Docker client to the Docker daemon, please set these environment variables.
You can set them by running:
    eval $(dinghy env)
It's recommended to add this to your shell config such as ~/.bash_profile

    export DOCKER_HOST=tcp://<IP_ADDRESS>:2376
    export DOCKER_CERT_PATH=/Users/qkdreyer/.docker/machine/machines/dinghy
    export DOCKER_TLS_VERIFY=1
    export DOCKER_MACHINE_NAME=dinghy

cat /usr/local/Cellar/dinghy/4.6.5/local/var/dinghy-*.output
=== Starting FsEvents at 2019-03-18T11:43:35+01:00 ===

/usr/local/Cellar/dinghy/4.6.5/cli/fsevents_to_vm/lib/fsevents_to_vm/ssh_install_gnu_touch.rb:33:in `install!': Failed to install GNU touch into VM: Unable to find image 'codekitchen/dinghy-http-proxy:2.5' locally (RuntimeError)
Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:39881-><IP_ADDRESS>:53: read: connection refused
	from /usr/local/Cellar/dinghy/4.6.5/cli/fsevents_to_vm/lib/fsevents_to_vm/cli.rb:17:in `start'
	from /usr/local/Cellar/dinghy/4.6.5/cli/thor/lib/thor/command.rb:27:in `run'
	from /usr/local/Cellar/dinghy/4.6.5/cli/thor/lib/thor/invocation.rb:126:in `invoke_command'
	from /usr/local/Cellar/dinghy/4.6.5/cli/thor/lib/thor.rb:359:in `dispatch'
	from /usr/local/Cellar/dinghy/4.6.5/cli/thor/lib/thor/base.rb:440:in `start'
	from /usr/local/Cellar/dinghy/4.6.5/cli/dinghy/fsevents_to_vm.rb:39:in `run'
	from /usr/local/Cellar/dinghy/4.6.5/cli/daemons/lib/daemons/application.rb:270:in `call'
	from /usr/local/Cellar/dinghy/4.6.5/cli/daemons/lib/daemons/application.rb:270:in `block in start_proc'
	from /usr/local/Cellar/dinghy/4.6.5/cli/daemons/lib/daemons/daemonize.rb:84:in `call_as_daemon'
	from /usr/local/Cellar/dinghy/4.6.5/cli/daemons/lib/daemons/application.rb:274:in `start_proc'
	from /usr/local/Cellar/dinghy/4.6.5/cli/daemons/lib/daemons/application.rb:300:in `start'
	from /usr/local/Cellar/dinghy/4.6.5/cli/dinghy/daemon.rb:73:in `start'
	from /usr/local/Cellar/dinghy/4.6.5/cli/dinghy/daemon.rb:14:in `up'
	from /usr/local/Cellar/dinghy/4.6.5/cli/dinghy/fsevents_to_vm.rb:14:in `up'
	from /usr/local/Cellar/dinghy/4.6.5/cli/cli.rb:283:in `start_services'
	from /usr/local/Cellar/dinghy/4.6.5/cli/cli.rb:93:in `up'
	from /usr/local/Cellar/dinghy/4.6.5/cli/thor/lib/thor/command.rb:27:in `run'
	from /usr/local/Cellar/dinghy/4.6.5/cli/thor/lib/thor/invocation.rb:126:in `invoke_command'
	from /usr/local/Cellar/dinghy/4.6.5/cli/thor/lib/thor.rb:359:in `dispatch'
	from /usr/local/Cellar/dinghy/4.6.5/cli/thor/lib/thor/base.rb:440:in `start'
	from /usr/local/bin/_dinghy_command:12:in `<main>'
=== Starting NFS at 2019-03-18T11:43:24+01:00 ===

UNFS3 unfsd 0.9.23 (C) 2009, Pascal Schmidt<EMAIL_ADDRESS>bind: Address already in use
Couldn't bind to udp port 19091

docker-machine ls dinghy
NAME     ACTIVE   DRIVER   STATE     URL                       SWARM   DOCKER     ERRORS
dinghy   -        xhyve    Running   tcp://<IP_ADDRESS>:2376           v18.09.3

dinghy ssh nslookup google.com
Server:    <IP_ADDRESS>
Address 1: <IP_ADDRESS>

nslookup: can't resolve 'google.com'
exit status 1

Do you get the same error if you create a machine directly using docker-machine create -d xhyve? In the past this has been an issue with either docker-machine or the xhyve driver, I'm not sure which, and it doesn't seem to affect everybody. It might be worth checking if there's a related issue open with either of those projects.

docker-machine create -d xhyve --xhyve-memory-size 4096 --xhyve-cpu-count 4 --xhyve-disk-size 20000 dinghy
Running pre-create checks...
Creating machine...
(dinghy) Copying /Users/qkdreyer/.docker/machine/cache/boot2docker.iso to /Users/qkdreyer/.docker/machine/machines/dinghy/boot2docker.iso...
(dinghy) Creating VM...
(dinghy) /dev/disk2          	                               	/Users/qkdreyer/.docker/machine/machines/dinghy/b2d-image
(dinghy) "disk2" ejected.
(dinghy) Generating 20000MB disk image...
(dinghy) created: /Users/qkdreyer/.docker/machine/machines/dinghy/root-volume.sparsebundle
(dinghy) Creating SSH key...
(dinghy) Fix file permission...
(dinghy) Generate UUID...
(dinghy) Convert UUID to MAC address...
(dinghy) Starting dinghy...
(dinghy) Waiting for VM to come online...
(dinghy) Waiting on a pseudo-terminal to be ready... done
(dinghy) Hook up your terminal emulator to /dev/ttys000 in order to connect to your VM
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env dinghy

dinghy ssh nslookup google.com
Server:    <IP_ADDRESS>
Address 1: <IP_ADDRESS>

nslookup: can't resolve 'google.com'

dinghy restart
Stopping the FsEvents daemon
Stopping the dinghy VM...
Stopping NFS daemon, this will require sudo
Starting the dinghy VM...
Starting NFS daemon, this will require sudo
Waiting for NFS daemon...
NFS mounting failed
Starting the FsEvents daemon
Starting DNS and HTTP proxy
setting up DNS resolution, this will require sudo
Unable to find image 'codekitchen/dinghy-http-proxy:2.5' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:57201-><IP_ADDRESS>:53: read: connection refused.
See 'docker run --help'.
   VM: running
  NFS: stopped
 FSEV: stopped
  DNS: stopped
PROXY: stopped

NFS failed to run
details available in log file: /usr/local/Cellar/dinghy/4.6.5/local/var/dinghy-NFS.output

FsEvents failed to run
details available in log file: /usr/local/Cellar/dinghy/4.6.5/local/var/dinghy-FsEvents.output

To connect the Docker client to the Docker daemon, please set these environment variables.
You can set them by running:
    eval $(dinghy env)
It's recommended to add this to your shell config such as ~/.bash_profile

    export DOCKER_HOST=tcp://<IP_ADDRESS>:2376
    export DOCKER_CERT_PATH=/Users/qkdreyer/.docker/machine/machines/dinghy
    export DOCKER_TLS_VERIFY=1
    export DOCKER_MACHINE_NAME=dinghy

Doesn't seem to change anything :(

Can I check if setting up DNS resolution, this will require sudo succeded ?

I'm wondering why I'm not seeing https://github.com/codekitchen/dinghy/blob/1a4270ec8cd36ce7e465338943fd3decfe06c1d4/cli/dinghy/http_proxy.rb#L92
https://github.com/codekitchen/dinghy/blob/1a4270ec8cd36ce7e465338943fd3decfe06c1d4/cli/dinghy/http_proxy.rb#L93
https://github.com/codekitchen/dinghy/blob/1a4270ec8cd36ce7e465338943fd3decfe06c1d4/cli/dinghy/http_proxy.rb#L94
dinghy ssh cat /etc/resolv.conf
nameserver <IP_ADDRESS>

Darn yeah, this is what I've seen a couple times before. I wish I knew what was causing it, or even whether it was docker-machine vs the xhyve driver.
That resolver file isn't installed on the VM, it is installed on the MacOS host in /etc/resolver/docker, this is why you can reach *.docker domains from your host machine (e.g. Safari) and not just from other Docker containers.

Can't you think about anything you want me to test to find out where that problem is ?

I'm not in a great position to figure this one out, I'm afraid. It might be useful to test with Virtualbox, see if you get the same problem with docker-machine create -d virtualbox. That won't guarantee whether it's a problem with the specific driver vs docker-machine itself, but it could still be a useful data point.
Then I'd file an issue with either the docker-machine-driver-xhyve project or the docker-machine project, or look for an existing issue.

Doing a macOS reboot handled the NFS issues (port 19091 was still used by a dead process, invisible using lsof, shown using netstat)
I was still having issues with DNS, which I solved by using <IP_ADDRESS>.1 instead of <IP_ADDRESS> as resolver.
dinghy ssh nslookup docker.io                                                                                 ✔  10013  16:34:06
Server:    <IP_ADDRESS>
Address 1: <IP_ADDRESS>

nslookup: can't resolve 'docker.io'
exit status 1

dinghy ssh "echo 'nameserver <IP_ADDRESS>' | sudo tee /etc/resolv.conf"

dinghy ssh nslookup docker.io                                                                                 ✔  10016  16:34:30
Server:    <IP_ADDRESS>
Address 1: <IP_ADDRESS>

Name:      docker.io
Address 1: <IP_ADDRESS> ec2-3-91-211-1.compute-1.amazonaws.com
Address 2: <IP_ADDRESS> ec2-52-54-178-62.compute-1.amazonaws.com
Address 3: <IP_ADDRESS> ec2-52-207-42-240.compute-1.amazonaws.com

I've just found out what the real DNS problem was.
I had already a local dnsmasq installed, which was not listening to docker interfaces.
After running these commands, no more DNS issues inside dinghy :
echo 'listen-address=<IP_ADDRESS>' >> /usr/local/etc/dnsmasq.conf
echo 'listen-address=<IP_ADDRESS>' >> /usr/local/etc/dnsmasq.conf
sudo brew services restart dnsmasq


Export as an ES module

It would be helpful if this package exposed the measure control as an ES module for use with tools such as Rollup.

@rbrtmrtn I didn't have any issues using this in a webpack environment and treating it as an ES6 module.
Have you tried importing Leaflet in the same module, like this:
import Leaflet from 'leaflet'
import 'leaflet-measure'

By doing so, leaflet-measure will look for the Leaflet object and attached itself to it like in the README:
Leaflet.Control.Measure

You can even be diligent and do something like this:
import Leaflet from 'leaflet'
import Measure from 'leaflet-measure'
import { isEmpty} from 'lodash'

// and when you need leaflet-measure, make sure it exists

// using lodash.isEmpty to simplify example
if (isEmpty(Leaflet.Control.Measure)) {
  Leaflet.Control.Measure = Measure
}

Not sure if that last example works 100%, but the idea is there.

Thanks @matt-e-king, I didn't try importing it that way but I'll give it a shot. Somehow the module way feels a little more future-proof, but I'm fine with whatever works :)

Hi @matt-e-king, question about this -- it looks like the code in src/leaflet-measure.js patches the L global without importing it. Is there some way to configure webpack so it knows how to find L?

Hey @rbrtmrtn, that is a little bit of a loaded question. I'm not as well versed on webpack/babel as I'd like to be either, but I'll break this into two sections with my best educated guess:
it looks like the code in src/leaflet-measure.js patches the L global without importing it.
At it's core, babel-loader is just transpiling "Javascript" into "backwards compatible Javascript". It is not going to catch everything that would normally trigger an exception, e.g. L is not defined.  Then it would throw an error because L is not defined.
The author of this leaflet-measure plugin designed this in a way that we, the developers, who are ingesting the plugin are responsible to provide the global L object.
That is why you don't see an import for L inside of src/leaflet-measure.js
With that said...
Is there some way to configure webpack so it knows how to find L?
This answer is now under a slightly different context. If you as the developer are trying to use leaflet-measure within a module environment, you will need to import Leaflet. Or at least provide it at a global level outside of your webpack build, BUT webpack will need to be aware of that scenario.
Try looking into the following things:
https://webpack.js.org/configuration/externals/
https://webpack.js.org/guides/shimming/

@matt-e-king has the right idea.
The plugin guidelines for Leaflet suggest appending any new classes to the L namespace https://github.com/Leaflet/Leaflet/blob/master/PLUGIN-GUIDE.md#plugin-api and not packaging up Leaflet in the plugin source. This is reasonable, I think, because Leaflet plugins don't really make sense without the existence of Leaflet.
To use this or any other plugins following this pattern, you will first need to import Leaflet, load Leaflet from a CDN, or some other means of globally creating L.Control as @matt-e-king suggested.

Thanks @matt-e-king and @brandoncopeland for shedding light on this.
I feel like I might be missing something. This is what I tried doing:
import leaflet from 'leaflet';
import 'leaflet-measure';

and I get an error that L is not defined. That makes sense, because I'm not doing anything that would expose the L global -- I'm importing it as leaflet. However, as I mentioned earlier, there's a reference to L hardcoded in leaflet-measure.
The approach of appending to L (i.e. L.Control.Measure) makes sense to me for a browser build, but I'm not grasping how it would work via imports. It seems like there is a hard requirement to have a copy of Leaflet, as L, available in the global namespace, which seems like something of an anti-pattern in the ES module age.

I see. We could probably update to something like the following to resolve.
import { Control } from 'Leaflet';
Control.Measure = ...

@brandoncopeland that seems like the right direction, but I think you might run into similar issues patching Control. I would suggest something like:
import { Control } from 'leaflet';

export default class MeasureControl extends Control {
  // override things here
}

Feel free to submit a PR if you like. If not, I'll try to get to it when I can. The ideal solution would continue to support users relying on global L.

@rbrtmrtn I can see now why my original example might be a bit misleading. I wasn't too familiar with the differences between webpack and Rollup, but it sounds like out of the box, Rollup isn't compatible with CommonJS modules. (Please correct me if I'm wrong). But there are plugins for it.
If you look at the top of the leaflet main distribution file, it looks something like this:
/*
 Leaflet 1.0.3, a JS library for interactive maps. http://leafletjs.com
 (c) 2010-2016 Vladimir Agafonkin, (c) 2010-2011 CloudMade
*/
(function (window, document, undefined) {
var L = {
	version: "1.0.3"
};

function expose() {
	var oldL = window.L;

	L.noConflict = function () {
		window.L = oldL;
		return this;
	};

	window.L = L;
}

// define Leaflet for Node module pattern loaders, including Browserify
if (typeof module === 'object' && typeof module.exports === 'object') {
	module.exports = L;

// define Leaflet as an AMD module
} else if (typeof define === 'function' && define.amd) {
	define(L);
}

// define Leaflet as a global L variable, saving the original L to restore later if needed
if (typeof window !== 'undefined') {
	expose();
}

So you can see Leaflet is exposing a window.L, but for Node module patterns (i.e. CommonJS which is used by webpack) it also uses module.exports = L. Since L is a complex type, window.L and the module.export are going to be the same object in memory. Webpack/babel have no problem compiling it and bundling, and by the time I actually need it in runtime, window is available.
I'm fairly certain I got this to work through ignorance :)
(typeof module === 'object' && typeof module.exports === 'object') is probably false when Rollup transpiles it.
@rbrtmrtn at what point do you actually get the L is not defined exception?

would really appreciate if there was a PR / update for this.


Functionality - API fetching

this issue is for establishing a connection with the api and confirm the info has been fetched. this step will not directly affect the web app

DONE! inputting a city name will not produce current and forecasted weather reports when console logging


pip install doesn't find package

python -m pip install mplterm does not find this package. I'm guessing it is not on pypi? If so you might want to update the README with a copyable command instead of "Install with pip, as any Python package." I'd probably also throw in usage via matplotlib.use("module://mplterm")

Thanks for the suggestions, I updated the readme accordingly.


ycmd-close: Invalid function: ycmd--kill-timer  on the latest MELPA

This issue is critical, my Emacs even can't close now if I have enabled ycmd.
Please fix it, thanks.

Are there any suspicious looking messages  in the message buffer? And what version of emacs are you using?

I ask because I don't see how that could be undefined...it's a macro that we just merged in, so it should be there.

Also could you check to see if ycmd--kill-timer is actually defined in the source that melpa is giving you?

It sounds like ycmd.el was somehow evaluated partially after an update or does this happen also after restarting Emacs?
I had the same kind of error already sometimes when I was switching branches while development and I evaluated only parts of the file while other functions and definitions were from a different commit.

@abingham  @ptrv
I deleted the ycmd.elc and call byte-compile-file to re-compile the ycmd.el file. Then the problem gone.
I do switch branches when using Emacs. Maybe that's the problem.
Thanks.

@andyque Great that you could solve the problem.
I meant switching branches of an Emacs package repository (i.e. ycmd.el) while developing it.

I had the same problem in spacemacs, deleting ycmd.elc solved the problem, thanks!

@naseer  I'm also using spacemacs, maybe it's bug in spacemacs.

Interestingly, I've also been trying out spacemacs recently, and I ran into this exact problem yesterday. I agree with @andyque that this really seems like a spacemacs issue, or perhaps a melpa/package.el problem. Has anyone filed an issue with them?

The error was due to the fact that the macro was defined further down in the code then the first usage in ycmd-close. Moving it before first usage fixes the issue.
I could repro the issue with byte-compiling ycmd.el and restarting emacs and loading a c++ file. I don't know whether the issue came up when loading ycmd lazily with eval-after-load or etc.

From the info (elisp) Compiling Macros:

In order for compilation of macro calls to work, the macros must already be defined in Lisp when the calls to them are compiled.


Muzei fast switches bug after long lock time period

I have Muzei set to switch every 15 minutes. I go to sleep and when I unlock my device in the morning Muzei swiftly switches through all supposedly missed switching events.
This is annoying and should not occur.
The switching is also 1 second each for each missed event.
I am using the latest version through the play store (v3.0.2).

What Source are you using?

Source: My Photos

I haven't been able to reproduce this on Muzei 3.2.0 Alpha 1. If you could update and check to see if this is fixed for you, I'd appreciate it.
If not, please send take a bug report immediately after seeing this and send it to<EMAIL_ADDRESS>and we can take it from there.


CON-625: Check for plugin restricted methods in Plugins that have a parent class

http://jira.cinchapi.com/browse/CON-625

@Tylerwbrown You should also create a unit test for this in https://github.com/cinchapi/concourse/tree/develop/concourse-plugin-core-tests/src/test/java/com/cinchapi/concourse/server/plugin
To do so, you'll need to create a Plugin that extends https://github.com/cinchapi/concourse/blob/develop/concourse-plugin-core-tests/src/test/java/com/cinchapi/concourse/server/plugin/TestPlugin.java and annotate one of the methods in TestPlugin as @PluginRestricted (NOTE: You should create a new method with this annotation)
Then create a test class that extends ClientServerTest implements PluginTest and try to invoke the method that is PluginRestricted


Offroad rate

Thanks for the great work and the repository! Can the author provide codes to calculate Offroad rate? Thank you!

Did you solve this problem

Could you mind to share the codes?Thank you.

I haven't been able to solve this problem either, and I really hope the author can provide the code for this part.

Thank you for your response!I also hope that there will be results soon.
十四
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "nachiket92/PGP"                                                                                @.>;
发送时间: 2023年10月3日(星期二) 中午11:15
@.>;
<EMAIL_ADDRESS>主题: Re: [nachiket92/PGP] Offroad rate (Issue #27)
Could you mind to share the codes?Thank you.
I haven't been able to solve this problem either, and I really hope the author can provide the code for this part.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


issue in tariterators.py

In line 244, I think you have written source rather than filesample. In any case, I had an error here because source was not defined.

Thanks for spotting this; it's fixed.


Support <scheme>.sub_plain for OpenFHE backend

Currently, we have bgv.sub_plain and ckks.sub_plain but no way to target them to OpenFHE

I think OpenFHE's EvalMul and EvalAdd are overloaded to support ciphertext-ciphertext and ciphertext-plaintext

I think OpenFHE's EvalMul and EvalAdd are overloaded to support ciphertext-ciphertext and ciphertext-plaintext

Yep, and those the pipeline already supports. But I'm not sure its supported for EvalSub in OpenFHE? If not, that just means we need to translate it to "negate plaintext, then add" (assuming that's the direction the op is defined in, which I don't recall right now 🙈 )

Oh! Gotcha - I think you're right about that and having some kind of rewrite/canonicalization pattern.


fix: position dropdown on first render

The problem was that the position of the dropdown content only got calculated on the first render, or when the window got resized. This is a problem because the React.Refs of the trigger and the content are still null on the first render and the resize event may never get triggered at all.
useClientRect gives you back a Ref and a clientRect, the ref never changes because it is a function, and the rect changes every render so it was impossible to check whether the ref had already attached to a node. That's why I also added the node as a return of useClientRect.

@Stefanwullems can you review the merge conflicts and resolve if possible? then we can merge https://bitbucket.org/exivity/glass/pull-requests/472 (regression bug in glass)


new VPN certificate

I seem to have forgotten my Tunnelblick passphrase.   @nickhurlburt Nick, I hear you may be able to help?
Thanks!

@zeeshan-yoonas -- this is a public repo.  Please file your request at https://github.com/SiftScience/code/issues .


remove

plugin:@typescript-eslint/recommended-requiring-type-checking
as it's too restricting for a sample code

Task linked: CU-2p6k5x1 update eslint typescript config


How to build other dictionaries

Hi,
I cloned you app and I would like to add other languages.
How can i build the CSV files and add them to the raw/ folder?
I tried using the .dict of the original LatinIME and modified the appropriate xml but it seems not to work.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29771570-how-to-build-other-dictionaries?utm_campaign=plugin&utm_content=tracker%2F493413&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F493413&utm_medium=issues&utm_source=github).

You need to build make-keyboard-text binary, from tools/make-keyboard-text and then you can use the source file to build dict files.

Hi built a jar file from tools/make-keyboard-text and now how should i build .dict files??Is this the coreect process to build .dict files if not please suggest

How to build a jar file from tools/make-keyboard-text, I'm an android newbee. @prathyush90


Assertion failed: (err) == (0), file src\agent.cc, line 164

$ node-debug helloworld.js
Node Inspector is now available from http://<IP_ADDRESS>:8080/debug?port=5858
Debugging `helloworld.js`

Debugger listening on port 5858
Hello World
Assertion failed: (err) == (0), file src\agent.cc, line 164

built latest node-inspector from github against:
$ node --version
v0.11.16

helloworld.js
console.log("Hello World");

The assertion failure happens when the tab is closed.

I think this is an issue with node v0.11.16, rather than node-inspector. I've had it multiple times while using the Webstorm debugger. I reported it here https://github.com/joyent/node/issues/9155

It's a Node issue. On Winx64 with node0.10.36, node-inspector0.8.3 works fine. On Node0.12 there's node-gyp error

I think it's relative to https://github.com/iojs/io.js/issues/781

still in latest, checked today:
$ node --version
v0.12.0

$ node-inspector
Node Inspector v0.9.1

$ node --debug-brk simple/hello-world.js
Debugger listening on port 5858
Hello, World!
Assertion failed: (err) == (0), file src\agent.cc, line 164

I have that problem

I can confirm the issue using IntelliJ debugger on Node project.  Debugger starts and executes fine, but when the debugger is stopped this exception is emitted.


Replace Less

Less is a rather dead project which does not support recent CSS features as seen in https://github.com/go-gitea/gitea/pull/15520. I suggest moving to either SCSS or plain CSS.
Thoughts on SCSS:

Supports pretty much everything and more that Less does
Is 4 times more populare then Less
Might be slower to compile with their Dart implementation
Like less, it encourages the bad practice of deeply nesting selectors, resulting in unnecessarily big CSS output

Thoughts on CSS:

Instant build, no compilation required
Obviously supports all CSS features out of the box
Does not support nesting which can be both a blessing (lightweight output) and a curse (impractical sometimes)
Best tooling support

I think plain CSS with https://github.com/csstools/postcss-plugins is the way to go nowadays. Once enough browsers support native CSS nesting, the plugin can just be removed. This is btw also what vite does by default.

I wonder whether we should just convert the Less to CSS and commit the output as-is, without any nesting.
It will produce long selectors for the nesting cases, but personally I prefer no nesting to be used at all because it'll make the selectors from devtools CTRL-F able in the source which is very helpful when searching for specific selectors.
Also, not using nesting encourages developers to write shorter and better selectors. I think it's a net benefit to not have nesting.

Absolutely agreed.
It has another huge benefit: You can tell immediately what style classes will interfere with what you are doing.
At the moment, I simply cannot do anything untested in the frontend, simply because there might be a four times nested selector I of course didn't think about that destroys what I'm trying to do.
Let's use the following hypothetical example:
I add a link somewhere.
Unfortunately, that link is inside a div that is inside an element ui class, and hence there is a selector that hides the link. Yay. Who would've guessed that my link isn't shown at all?


HttpIn-Node: req.headers missing

Current Behavior
No req.headers object is created at all.
No further issues detected.
Expected Behavior
Setting the req.headers normally by parsing the rawHeaders.
Steps To Reproduce
The following installation guide was used: https://nodered.org/docs/getting-started/windows
Within the settings file, the adminAuth and httpStatic was activated. On startup, a custom userDir was defined.
Example flow
[
    {
        "id": "5cdb577d312a6396",
        "type": "tab",
        "label": "Flow 2",
        "disabled": false,
        "info": "",
        "env": []
    },
    {
        "id": "0bd7e4f96e124803",
        "type": "http in",
        "z": "5cdb577d312a6396",
        "name": "",
        "url": "test",
        "method": "get",
        "upload": false,
        "swaggerDoc": "",
        "x": 180,
        "y": 300,
        "wires": [
            [
                "3c158e32afb61dd2",
                "63a1461253731fd5"
            ]
        ]
    },
    {
        "id": "0fa97b2e760bb7d8",
        "type": "http response",
        "z": "5cdb577d312a6396",
        "name": "",
        "statusCode": "",
        "headers": {},
        "x": 490,
        "y": 300,
        "wires": []
    },
    {
        "id": "3c158e32afb61dd2",
        "type": "template",
        "z": "5cdb577d312a6396",
        "name": "",
        "field": "payload",
        "fieldType": "msg",
        "format": "handlebars",
        "syntax": "mustache",
        "template": "This is the payload: {{req.headers}} !",
        "output": "str",
        "x": 340,
        "y": 300,
        "wires": [
            [
                "0fa97b2e760bb7d8"
            ]
        ]
    },
    {
        "id": "63a1461253731fd5",
        "type": "debug",
        "z": "5cdb577d312a6396",
        "name": "",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "true",
        "targetType": "full",
        "statusVal": "",
        "statusType": "auto",
        "x": 350,
        "y": 240,
        "wires": []
    }
]

Environment

Node-RED version: 2.2.2
Node.js version: 16.14.0
npm version: 8.5.4
Platform/OS: Windows Server 2012
Browser<EMAIL_ADDRESS>

Sorry, my mistake.
Seems that the headers-object wasn't being displayed in debug-monitor but can be accessed in a function node.


Belinda_NextJS_Sprint_1_154_Added_Confirm_Password_Textfield

This is related to User Story #140
I added confirm password textfield

@tinpham5614 what is the conflict that I need to resolve for this issue


How to get each error in MultiErrorBuilder?

When using the MultiErrorBuilder and having multiple errors, I'm unable to get to each error. (b *MultiErrorBuilder) ErrOrNil() creates an object of the type multiError - which would allow me to use (e *multiError) Errors(), but is returned as type error (which is good). From outside, I'm unable to cast to this type, as it is not exported.
_ = errs.ErrOrNil().(*emperror.multiError) // cannot refer to unexported name emperror.multiError

I could offer a PR, should I just make the MultiError exported or do you have other plans?

Thanks a lot for the PR, but ideally you should use a custom interface for this:
// Errors returns a list of errors.
type Errors interface {
    Errors() []error
}

Then you can cast an error to this type.
I could imagine such interface added to this package though, so if you are willing to update your PR that would be nice.

Updated PR, I suggest moving the conversation there


Patch haproxy dynmanic config via kind cli as well

Issue #, if available:
Description of changes:
My last patch was technically incomplete, but for eks-a this is not actually necessary since our use of the haproxy loadbalancer is only thru CAPD which does not use this particular kind code path. Patching anyway to be consistent.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/test image-builder-1-24-tooling-presubmit

/test imagebuilder-1-24-presubmit

/test imagebuilder-1-25-presubmit

/lgtm
/approve
/override imagebuilder-1-25-presubmit imagebuilder-1-24-presubmit


Compatible with all OS's (Windows, Linux, OSx, etc..)

You should make this compatible with all operating systems, not just Linux.

I will

Please wait  =D

Sounds good, thank you!


graticule intervals option

It would be nice to have a intervals option to get fix intervals for displaying a graticule.
I don't see this option from:
https://openlayers.org/en/latest/apidoc/module-ol_Graticule-Graticule.html
intervals: [30, 10]
would limit graticules to 30 and 10 degrees intervals only.

does it mean like this?

Thanks for this new option implemented so quickly.
@cs09g: Not what you described but rather intervals that don't depend on zoom level.


WIP: Add implementation of native RekeyDriver

Closes #19
This PR adds a very rough implementation of the Native RekeyDriver. There are some modifications to the api that need to occur in order to fix a few issues related to the underlying NativeSqliteDriver and JdbcSqliteDriver (see #22 & #23).

linux tests seem to be failing (they run successfully locally).. Will override for now and investigate later.


Docs: do not install as Sphinx extension

Closes #1222

Test failure is expected, sphinx-rtd-theme 2.1.0rc1 depends on sphinx<8 and >=5

I don't 100% understand the Sphinx internals, but it seems we cannot remove the installation as an extension: https://github.com/readthedocs/sphinx_rtd_theme/issues/1434#issuecomment-2289443380


fix: security updates

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ISSUE-1086: Ability to view large messages and limit the message size…

… for log search output
UI changes for #1086

Attached screenshots after applying this PR:
UI as per the mocks:

After clicking on "show more" for long log message:

Pagination:


Hijri to Gregorian is not correct

$date = Hijri::convertToGregorian(1, 16, 1401);

// output is "1982-01-25" and it should be "1980-11-24"

According to this website that converts Hijri to Gregorian
https://beseyat.com/calendars/en/date-converter-hijri-gregorian.php

use format (day,month,year) it's work fine.


Add publishing dependency on build package step

Overview
Adds a dependency on the build package step, from the POV of the publishing step.
Apparently, transitive dependencies are not acceptable for Github Actions job outputs, but there's no warning thrown about this during parsing, fun!

This should be good to go, I believe this fixes the build issue.


feature: S3C-3525 Create Tenant-2

Adding necessary Scality specific implementation classes by extending or replacing vmware classes
Modifying application.properties using original vmware suggested properties for Vault and App info

Hello saitharunthodupunuru,
My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.
Status report is not available.

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

2 peers

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

2 peers

The following reviewers are expecting changes from the author, or must review again:

@nicolast

As discussed on Slack, my .02 how this could be structured:

Upstream stubs are imported as-is, as was done, in the VMWare namespace
Within the same JAR, whenever we need a new package/class file, we create it as a package within the com.scality domain
Whenever we need to make changes to existing stub files (we can't work around by inheritance, implementing an interface,...) we copy the file from the VMWare namespace to a Scality-owned one (package name), and add a Scality copyright header (next to the VMWare one, not replacing it!)

This way, we don't claim (pure) VMWare code is Scality's, and we don't pretend Scality (original or modified stubs) code is VMWare's, neither of which we should do (cfr. the Apache-2 license).

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

2 peers

As discussed on Slack, my .02 how this could be structured:

Upstream stubs are imported as-is, as was done, in the VMWare namespace
Within the same JAR, whenever we need a new package/class file, we create it as a package within the com.scality domain
Whenever we need to make changes to existing stub files (we can't work around by inheritance, implementing an interface,...) we copy the file from the VMWare namespace to a Scality-owned one (package name), and add a Scality copyright header (next to the VMWare one, not replacing it!)

This way, we don't claim (pure) VMWare code is Scality's, and we don't pretend Scality (original or modified stubs) code is VMWare's, neither of which we should do (cfr. the Apache-2 license).

@NicolasT
Updated the PR with the suggested changes. Please review

@NicolasT Can you please do a re review and approve this?

/approve

In the queue
The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.
The changeset will be merged in:

:heavy_check_mark: development/1.0

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.
IMPORTANT
Please do not attempt to modify this pull request.

Any commit you add on the source branch will trigger a new cycle after the
current queue is merged.
Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.
The following options are set: approve

I have successfully merged the changeset of this pull request
into targetted development branches:

:heavy_check_mark: development/1.0

Please check the status of the associated issue S3C-3525.
Goodbye saitharunthodupunuru.


Help with the basics

Thanks for the cobol course. I cant help but notice that this course is not being presented for new people trying to learn to program in cobol.  But for people with a wide range of programming knowledge albiet not cobol.
So I've got a few questions I hope you can help with.

How do I link the actual files (which don't have an extension) on my laptop with the JCL and via that to the file referenced in the select statement.
Although I have a zowe profile setup and Java correctly designated I still do not have the functionality of the zowe extension for the cobol programs (floating information block when hovering over code).
Breadcrumb function does not work
-when trying to run a program I get this message back. "cannot find a class with the main method in the folder 'cobol resources'"

which leads me to figuring out what this is--- "Check at least one main class exists in your workspace." -when referencing the help content
Thanks so much for your help on this.
please respond here or email me at<EMAIL_ADDRESS>if you can help out!

I noticed that I have not done any of the Readme file orders. I actually have no idea how to do those things.
IE: copy cobol source members into student id.CBL partitioned data set name

what are source members
what/where are the partitioned data set name.

so on and so forth for .cobol jcl and jclproc files.
Again thank you so much for helping someone so new to programming.

https://www.eventbrite.com/e/a-beginners-practical-approach-to-cobol-tickets-102714511870 listen for announcement of access to z/OS for the COBOL labs - no cost   where labs data sets (COBOL source, JCL, data is provided on the lab system for each participant that enrolls

Thanks Paul.

Although I have a zowe profile setup and Java correctly designated I still do not have the functionality of the zowe extension for the cobol programs (floating information block when hovering over code).
Breadcrumb function does not work
-when trying to run a program I get this message back. "cannot find a class with the main method in the folder 'cobol resources'"

The same happened to me. Using original IBM Java 8 fixed that 👍


feat: more API for the left homology of short complexes

This PR develops the API for the left homology of short complexes: properties of morphisms induced on (left) homology by morphisms of short complexes.

bors merge


Pilot/engine/bin/Linux/meta_parser: error while loading shared libraries: libclang.so.12: cannot open shared object file: No such file or directory

when I run ./build_linux.sh debug on ubuntu 20.04 , It show  some error about   libclang.so.12  .

.

A https://github.com/BoomingTech/Pilot/pull/13 has been provided. If you are hasty, you may use this repository first. The github workflow shows "build linux" is passing.

Same issue on archlinux.
BTW, on macOS, libclang.dylib could be found at /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libclang.dylib
sudo cp /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libclang.dylib /usr/local/lib/libclang.dylib can solve this issue.

A pull request has been provided. If you are hasty, you may use this repository first. The github workflow shows "build linux" is passing.

Same issue on archlinux. BTW, on macOS, libclang.dylib could be found at /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libclang.dylib sudo cp /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libclang.dylib /usr/local/lib/libclang.dylib can solve this issue.

Only Ubuntu is officially supported, and the github workflow shows "build linux" is passing.

刚发现项目文件里就有相应的动态库，Linux在Path_to_Pilot/engine/bin/Linux/libclang.so.12，直接cp到/usr/lib/libclang.so.12完事儿。

Same issue on archlinux. BTW, on macOS, libclang.dylib could be found at /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libclang.dylib sudo cp /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libclang.dylib /usr/local/lib/libclang.dylib can solve this issue.

This is NOT recommended. The version of the libclang.dylib provided by us may be different from the libclang.dylib provided by Xcode, and thus something unexcepted may emerge.

刚发现项目文件里就有相应的动态库，Linux在Path_to_Pilot/engine/bin/Linux/libclang.so.12，直接cp到/usr/lib/libclang.so.12完事儿。

This is NOT recommended.  The version of the libclang.so.12 provided by us may be different from the libclang.so.12 provided by Ubuntu. Some software provided by Ubuntu may not work properly due to the confliction of the libs.

You can use the following command to fix this build error on Linux temporarily.
chrpath -r '$ORIGIN' "./engine/bin/Linux/meta_parser"

刚发现项目文件里就有相应的动态库，Linux在Path_to_Pilot/engine/bin/Linux/libclang.so.12，直接cp到/usr/lib/libclang.so.12完事儿。

By the way, Chinese is NOT welcome. Please use English instead, and thus you comments can be understood by github users from all over the world.

刚发现项目文件里就有相应的动态库，Linux在Path_to_Pilot/engine/bin/Linux/libclang.so.12，直接cp到/usr/lib/libclang.so.12完事儿。

We strongly recommend you change your comments to English.

@BoomingTech-YuqiaoZhang Hello, I know how to solve this.
First, it seems that you have already bundled  engine/bin/Linux/libclang.so.12 in the same directory as meta_parser. The Linux system doesn't support loading shared objects from current directory by default, so we need to specify that path manually. To do so, there are two ways.

Use patchelf to set the RPATH of meta_parser to be the current directory does ($ORIGIN here means current executable path), this make .so works just like .dll on Windows. I think the Pilot maintainer could run this command and then git add it, so that our students will no longer need this step anymore.

patchelf --set-rpath '$ORIGIN' engine/bin/Linux/meta_parser

Use the LD_LIBRARY_PATH to specify the library search path at runtime, this work for MacOS too IIRC.

export LD_LIBRARY_PATH=$PWD/engine/bin/Linux/
./build_linux.sh

@BoomingTech-YuqiaoZhang Hello, I know how to solve this. First, it seems that you have already bundled engine/bin/Linux/libclang.so.12 in the same directory as meta_parser. The Linux system doesn't support loading shared objects from current directory by default, so we need to specify that path manually. To do so, there are two ways.

Use patchelf to set the RPATH of meta_parser to be the current directory does ($ORIGIN here means current executable path), this make .so works just like .dll on Windows. I think the Pilot maintainer could run this command and then git add it, so that our students will no longer need this step anymore.

patchelf --set-rpath '$ORIGIN' engine/bin/Linux/meta_parser

Use the LD_LIBRARY_PATH to specify the library search path at runtime, this work for MacOS too IIRC.

export LD_LIBRARY_PATH=$PWD/engine/bin/Linux/
./build_linux.sh
``"`

patchelf works

@BoomingTech-YuqiaoZhang Hello, I know how to solve this. First, it seems that you have already bundled engine/bin/Linux/libclang.so.12 in the same directory as meta_parser. The Linux system doesn't support loading shared objects from current directory by default, so we need to specify that path manually. To do so, there are two ways.

Use patchelf to set the RPATH of meta_parser to be the current directory does ($ORIGIN here means current executable path), this make .so works just like .dll on Windows. I think the Pilot maintainer could run this command and then git add it, so that our students will no longer need this step anymore.

patchelf --set-rpath '$ORIGIN' engine/bin/Linux/meta_parser

Use the LD_LIBRARY_PATH to specify the library search path at runtime, this work for MacOS too IIRC.

export LD_LIBRARY_PATH=$PWD/engine/bin/Linux/
./build_linux.sh

Hi. "patchelf" does work, but "chrpath" works as well.

@BoomingTech-YuqiaoZhang Hello, I know how to solve this. First, it seems that you have already bundled engine/bin/Linux/libclang.so.12 in the same directory as meta_parser. The Linux system doesn't support loading shared objects from current directory by default, so we need to specify that path manually. To do so, there are two ways.

Use patchelf to set the RPATH of meta_parser to be the current directory does ($ORIGIN here means current executable path), this make .so works just like .dll on Windows. I think the Pilot maintainer could run this command and then git add it, so that our students will no longer need this step anymore.

patchelf --set-rpath '$ORIGIN' engine/bin/Linux/meta_parser

Use the LD_LIBRARY_PATH to specify the library search path at runtime, this work for MacOS too IIRC.

export LD_LIBRARY_PATH=$PWD/engine/bin/Linux/
./build_linux.sh

Hi. "patchelf" does work, but "chrpath" works as well.

Ok, does chrpath work for MacOS btw?

@BoomingTech-YuqiaoZhang Hello, I know how to solve this. First, it seems that you have already bundled engine/bin/Linux/libclang.so.12 in the same directory as meta_parser. The Linux system doesn't support loading shared objects from current directory by default, so we need to specify that path manually. To do so, there are two ways.

Use patchelf to set the RPATH of meta_parser to be the current directory does ($ORIGIN here means current executable path), this make .so works just like .dll on Windows. I think the Pilot maintainer could run this command and then git add it, so that our students will no longer need this step anymore.

patchelf --set-rpath '$ORIGIN' engine/bin/Linux/meta_parser

Use the LD_LIBRARY_PATH to specify the library search path at runtime, this work for MacOS too IIRC.

export LD_LIBRARY_PATH=$PWD/engine/bin/Linux/
./build_linux.sh

Hi. "patchelf" does work, but "chrpath" works as well.

Ok, does chrpath work for MacOS btw?

The official "install_name_tool" provided by APPLE can be used, you can find the discussion on another issue page.

You can use the following command to fix this build error on Linux temporarily. chrpath -r '$ORIGIN' "./engine/bin/Linux/meta_parser"

It works.. Thanks!

You can use the following command to fix this build error on Linux temporarily. chrpath -r '$ORIGIN' "./engine/bin/Linux/meta_parser"

after execute chrpath -r '$ORIGIN' "./engine/bin/Linux/meta_parser",  another error show : tbb/blocked_range.h: No such file or directory.
It need addition lib call libtbb-dev , so I type  "apt install libtbb-dev"  and compile again.
but it show:  "engine/source/runtime/function/animation/utilities.h:16:48: error: no member named 'find' in namespace 'std' ",
in file "engine/source/runtime/function/animation/utilities.h", need "#include ", and again.
finally ,  it work .

You can use the following command to fix this build error on Linux temporarily. chrpath -r '$ORIGIN' "./engine/bin/Linux/meta_parser"

after execute chrpath -r '$ORIGIN' "./engine/bin/Linux/meta_parser", another error show : tbb/blocked_range.h: No such file or directory.
It need addition lib call libtbb-dev , so I type "apt install libtbb-dev" and compile again.
but it show: "engine/source/runtime/function/animation/utilities.h:16:48: error: no member named 'find' in namespace 'std' ", in file "engine/source/runtime/function/animation/utilities.h", need #include "<algorithm"> , and again.
finally , it work .

Hi. Actually, a pull request has been provided. If you are hasty, you may use this repository first. The github workflow shows "build linux" is passing.

A pull request has been provided. If you are hasty, you may use this repository first. The github workflow shows "build linux" is passing.

@vin120


[DO NOT MERGE] Comparison of main + original

This PR is to compare and discuss the matrix-free, stencil version of the original HPCG

Is there a specific reason you've chosen to treat edges/corners/MPI domain edges with separate loops rather than using ghost points?

The reason that edges etc were done in this way, rather than multiplying by zero for e.g., was to replicate the floating point operations exactly. So there are the same number of multiplications, and no reference to precomputed values or changing the indexing of the vectors.
I'm not suggesting that this is what should be done in a real code - it was just to reproduce the HPCG calculation, but implemented in a different way.

To what end? Are we wanting to compare the performance of the matrix and matrix-free versions that precisely?


Ensure tests pass on the beta compiler

Also add a travis matrix entry for emulating the beta tests

Do you know why the idempotence tests require nightly?

Nah sorry I didn't investigate too closely there :(


#370  #421  Copy docs for 5.2.1 while avoiding 404s

Implements #370

There's a link on the README.md called "Release Documentation" that's supposed to go to the 5.2.0 docs.  Would you also update that to point to the new 5.2.0 docs URL?

I wasn't able to find a link in README.md but I did find a couple of links in 6025486.html to update

Minor note: for some reason GitHub doesn't pick up the association when you put the ticket number in the title of the PR, but does if you put it in the description

@tst-mswartz The readme that Lee is referring to is https://github.com/google/earthenterprise/blob/master/README.md, It lists the 5.2.0 release along with links to the release notes and documentation. The way it is now, they'd be pointing to the 5.2.1 docs.

Ah I had an out of date version of README.md without any version info in it.  Made the requested changes and will merge those into my main fork for this PR now.  Should the link to "GEE User/Administrator Documentation" point to geedocs/ though or to geedocs/5.2.0/ ?

@googlebot I approve my changes

The changes I asked for look good, so I'm going to merge this one


TeamCity documentation is missing under CI-Systems

https://cake-contrib.github.io/Cake.Recipe/docs/ci-systems/teamcity still reads
This documentation is currently missing.

sorry. GitHub confused me today.
This is actually a duplicate to #702

Duplicate of #702

sorry. GitHub confused me today.

I know the feeling, been there a few times myself :laughing:


add warnings when changing values

e.g. when running calculatelinelimits...

@claytonpbarrows is this still valid or can we close it?

I think it's still valid. I definitely cannot confirm that it should be closed.

@claytonpbarrows We generate warnings in checkanglelimits and calculatethermallimits.  Do you know of any specific place where we don't?

I just looked through system_checks.jl It looks like everything is covered. Closing


Multiple keys acting as the same virtual/fake modifier

"set_variable" with "to" and "to_after_key_up" can be used to implement fake modifier layers, like it is done in mu_mode or vi_mode and others. However having multiple keys be the same fake modifier doesn't work properly:
For example if you have two keys behave as the same fake modifier (using the same variable, with value 1 signalling modifier down and 0 signalling up), after pressing both and releasing only one of them the variable is back at 0, but it should remain 1 until both are released.
There are many possible ways to fix this, I'm not sure which one fits the grand vision, if there is one:

introduce increment_variable, decrement_variable and variable_if_greater_or_equal
introduce conditions_for_after_key_up (allows to check extra variable to see if other key is pressed). Not very convenient, but maybe there are other use cases for conditions_for_after_key_up.
introduce logical disjunction in conditions (aka "or"), to check multiple variables separately for each modifier key. Is only comfortable in combination with named reusable conditions (#862).
introduce some way to group multiple physical keys into a logical key. logical key release event only occurs when the last physical key is released.

I think 4. is the simplest approach. What about a "from_any_key_code" that defines a list of key codes that act as one?


Spreadsheet Upload Validations Incorrect

There are 3 different errors, but they all stem from the same problem. In each case there is a legitimate value in the field, but errors are being thrown.
Values in template:
EC1 column V: 5500000
EC1 column W: No
Awards > 50K: Family or childcare (capitalization is correct)

You can use a copy of my test file out on Google Drive: https://drive.google.com/file/d/1m5zyYHdWhg2twnHOxJf306CxQjPqfvjC/view?usp=sharing

the primary sector errors are fixed in #382
the problem with the EC1 row 13 cols V/W errors is that those don't have column headers in joe's sheet:

and so we never read them, because when parsing records, we look at the header, here:

and row 3 is set to TBD. we could, instead, use the column headers from the rules -- but i'm not sure what else that might break? like, did we ever insert columns in the middle, and if we use the column mapping from the rules, we'll just end up with totally junk data?

So in the latest version, v20220620, I did add the metadata in for V, W. I also took care of EC2 columns W, X which had the same issue. If you are using the latest template to drive the logic, it should work.
That said, there are still some questionable fields with the (manual entry) in them. I can't actually find these fields in the output template (they came from the partners). In this instance, we could:

ignore validation
or I could add an appropriate data type and max value if appropriate

Lastly, if you look carefully at the last few treasury identifiers above, you will see there's only one underscore '_c' instead of '__c' but also, the names themselves aren't entirely right. The names must be fixed and I'll do that once Treasury releases their guidance tomorrow.
Does this help?


Update documentation following usage

📖 Description
This PR adjusts the required Node.js/NPM version listed in the READMEs to match what is defined in package.json.
This also marks docker-entrypoint.sh as executable to ensure the docker image will run properly after using this template.

🦀 Requesting reviewers for this pull request:

@remi (contributor with 2 commits in the last 90 days and 67 commits overall)


Project Name Conflicts

At the moment I already have an existing Rust project called "Rise" -- the GUI library. For the project there is a registered domain rise.rs, and an organization "rise-ui". I would like to avoid any confusion in the future, so let's discuss how would we solve the problem with name conflicts. I did not reserve the project name on crates.io because rise-ui has github webrender dependency, and crates.io does not allow the publication of a project with git dependencies. Though some independent libs like raqm have already been published on crates.io on behalf of the project, with keywords like "rise, rise-ui".
Proofs

organization on github
commit when the project was named a rise
domain ownership confirmation

Hi @friktor, thanks for the heads up about this! I had searched for web frameworks (in any language) and crates named Rise, but looks like that wasn't enough :joy:
I'll work with @yoshuawuyts and the rest of the WG to figure out an alternative and we can transfer ownership of the name on crates.io

@friktor we've renamed the project to tide, as in "the rising tide" :tada: -- I've also invited you to be an owner of tide on crates.io. The only inconvenience is that the 0.1.0 version is already taken, but hopefully that's not too much of a problem.
All in all I hope this ends up being an adequate resolution. Thanks for raising this; excited to see what comes out of both rise and tide :sparkles:


jenkins plugin for guzzle

Hi
Is there a jenkins plugin for guzzle that provides html report  on dashboard ?

Guzzle and Jenkins don't have much in common. I don't think Guzzle is going to be useful for Jenkins and if any such plugin exists, it could be found by searching through the Jenkins plugins repo.


Export current scene as mp4

We are very close to a full pipeline for Manim development. Crucially, we are missing the final step of actually exporting a scene as an e.g., mp4 of some quality (a thought I came up with as I was writing the "sales pitch demo" #37 for this extension)
At the minimum, we want to expose a command that lets users choose the following from the manimgl tool:

Image quality (low, med, hd, uhd)
fps

(happy to discuss more advanced options like Gif?, Transparent?, background color?, etc., but I was hoping to appeal to the broadest user that would care about the quality of the mp4 they were generating)
Finally, let the user choose which file to save the output video to

For the file picker, see this API.
For the export, I could imagine a gutter icon (similar to the breakpoint) showing on lines where the class is started, e.g. class MyScene(Scene):. Unfortunately, the VSCode issue for on click events on the gutter icon was closed without a solution. The new issue to track this is here. In the meantime, there's also the option to provide a Export scene to the context menu that appears when you right-click on the line numbers or the area where the breakpoints live. See the contribution menus (editor/lineNumber/context).
Note that just checking if a class inherits from Scene or InteractiveScene is not sufficient as seen with some examples in 3b1b's videos repo. E.g. this scene.

UI: Define settings for export
Users could define settings in a multi-step quick pick. If that gets too long, we might want to use a custom webview view even if that is discouraged by VSCode. But they don't specify what you should use instead then since they also advise against using multi step quick picks to create wizards (see my comment).

Maybe you could also vote for this issue at VSCode since they look for issues with high votes to organize their backlog. I think it'd be really cool to be able to use onClick events for gutter icons. With this we could add buttons like the "debug button" as envisioned by bhoov here.

(happy to discuss more advanced options like Gif?, Transparent?, background color?, etc., but I was hoping to appeal to the broadest user that would care about the quality of the mp4 they were generating)

After just revisiting this again: Yes, I think it'd be cool to have a general feature for export. But it's probably really tedious if we want to support every option that manimgl supports for export. And then in the future, other options might be added.
So what do you think about this approach: provide a very basic UI where the most important settings (image quality and fps) can be set. Then, let the user click on a button like Generate command that will open a new terminal and in it just paste the command. The user can then press enter to export the scene.
This approach has some advantages:

Even if manimgl supports more flags in the future, users might just append them at the time they have generated the very basic command. The main advantage I see with our UI is that users will be able to select the output file location from a file browser (which is sometimes tedious to do in the shell).
We save ourselves some (or a lot of) work compared to also implementing the export progress notification and parsing the output for this again. This is just an advantage from the dev perspective and should have the least weight (but then of course we're just a small team, which should also be taken into account).

So far I was always pro-UI à la "Let us support a terminal-free workflow". But totally terminal-free is unrealistic I guess. Users will have to interact with it anyways:

see Manim error messages
Interactively try things out in the IPython shell, e.g. see if a Python snippet works.

And for the export, I actually see the advantages of the terminal as being very flexible and giving the power to the user. But of course, maybe I'm just making up an excuse to not implement all the shell parsing ;)
Let me know what you think. I just want to avoid the situation where we get PRs like "Add this or that as export option", which would be a bit annoying IMHO as I'd rather invest my time in getting the core things right, which is the preview itself (and niceties centered around it). Maybe we should then develop a policy, e.g. that we close such PRs because we only support image quality and fps via the UI.

I fully approve this workflow. It is more than sufficient for a v0.1.0 release.
If we wanted to get fancy down the road, we could automatically parse the manimgl --help docstring to populate the checkboxes (which would help solve your fears of PRs like "Add this or that as export option"), but most options would need to hide behind an "advanced options" dropdown: they do not add to the simple experience we want to create.

we could automatically parse the manimgl --help docstring to populate the checkboxes

Ah, good idea haven't thought about that. However, in the end it's not as easy as just populating checkboxes based on this. Every single step needs custom validation and custom tuning, e.g. sometimes allow users to input a number greater than x, sometimes a number in a range, sometimes with decimals, sometimes without, sometimes allow a string with a dot in the end, sometimes not, sometimes add a custom validation text, sometimes enable/disable a step based on a previous input etc.
That's just to say that every new option we would like to add there needs custom care and maintenance efforts. I just don't want to spend too much time on this and tailor to every user and every obscure export setting that Manim might offer. The few essential ones like quality and fps, yes, but I don't envisage to expand on this in any way ;) Users still have the option to add their custom flags in the terminal in the pasted command.


Example with maps view

Would love to see the example with the maps view (3rd gif) as well.

All the code related to react-native-snap-carousel would be pretty much the same as the first example. I don't think you'd learn much from it.
The trick is to use the prop onSnapToItem to trigger the map's methods to center it. Like so :
[...]

    _centerMapOnMarker (markerIndex) {
        const mapRef = this._mapView;
        const markerData = this.state.markers[markerIndex];

        if (!markerData || !mapRef) {
            return;
        }
        mapRef.animateToRegion({
            latitude: markerData.geolocation.latitude - CENTER_LAT_OFFSET,
            longitude: markerData.geolocation.longitude,
            latitudeDelta: 0.0315,
            longitudeDelta: 0.0258
        });
    }

                <Carousel
                  items={filteredMarkers}
                  renderItem={this._renderSwiperItem}
                  firstItem={firstItem}
                  sliderWidth={sliderWidth}
                  itemWidth={itemWidth}
                  snapOnAndroid={true}
                  showsHorizontalScrollIndicator={false}
                  slideStyle={styles.slide}
                  containerCustomStyle={styles.slider}
                  contentContainerCustomStyle={styles.sliderContainer}
                  inactiveSlideScale={1}
                  inactiveSlideOpacity={0.8}
                  removeClippedSubviews={false}
                  onSnapToItem={(index, marker) => this._centerMapOnMarker(marker.absoluteIndex)}
                />

onSnapToItems arguments are the index of the item you've just scrolled to on the carousel and its data (that you supplied in the items prop). It should be enough to build basically anything you want.
I won't build a specific example, especially since react-native-maps is far from stable, and is subject to breaking changes quite often.

Hi All contributors!! Great work! Just added in a project today! But In prototype on which I am working on have this carousal with continuous slow motion rather than jump from slide to slide..!! Is there any option to do the behavior in that way??

@umer990 Hi! You can use the prop enableSnap to enable/disable the snapping effect. Is it what you're looking for?
By the way, next time you should open a dedicated issue ;)

I couldn't find any difference by using that property as I am using autoplay=true.I am looking for the slider/carousal with motion like rail(move continous instead of jumping from one slide to another) of pics!!

@umer990 I can confirm that we haven't implemented it yet. It's on our to-do list, stay tuned!
Further discussion will take place in the dedicated issue #12

Hi guys, I'm trying to implement the carousel inside of the MapView. Currently I can only implement it underneath, so the carousel doesn't overlay the map. Any pointers on this? Thanks

Hi guys, I'm trying to implement the carousel inside of the MapView. Currently I can only implement it underneath, so the carousel doesn't overlay the map. Any pointers on this? Thanks

  slide: {     width: '100%',     height: 150,     position: 'absolute',     bottom: 3,     zIndex: 2,   },
I use this style to overlay Carousel wrapper on my map -- you may need to change zIndex a bit higher


build wheels on CI

This MR includes the commits from #617, so that one should be merged first.
The purpose of this MR is to build and test wheels on RAPIDS CI infrastructure. Previously, cuCIM was using a custom manual wheel building process based on running:
./run build_python_package

which used dockcross/cibuildwheel. We would then manually upload the resulting wheel to PyPI using twine.
The changes in this MR are to enable automated wheel builds for future RAPIDS releases in a similar way to other RAPIDS projects.
Misc issues/questions for discussion

The build_wheels.sh script installs the YASM and the openslide libraries via system package managers. This is currently hard-coded in that script rather than using the dependencies.yaml mechanism being used elsewhere. Is this reasonable or is there a better way?
Following cuML's example, I added a separate ci/release/apply_wheel_modifications.sh script that updates the pyproject.toml as needed (to fixup version string and the CUDA version strings in the cucim package name and CuPy dependency)
I updated the cuCIM test suite to make a handful of tests that relied on imagecodecs to be skipped if it is not installed. This is because I did not find a pre-compiled wheel for it on aarch64 and when it tried to compile from source instead, it failed due to various missing system packages needed for the compilation.
Unlike most RAPIDS projects, which seem to use scikit-build, this project performs a separate CMake build via run build_local commands and copies the C++ libraries into the Python source tree. The pyproject.toml then just does a standard pure-python build, but will package the previously compiled libraries along with the other files.
The wheel tests are currently taking approximately 35-50 minutes to run. It should be possible to reduce that time by an order of magnitude if the CuPy kernels are cached across runs. Does any RAPIDS projects cache the compiled CuPy kernels in this way? (cached kernels end up in ~/.cupy/kernel_cache/ by default, although an alternative location can be specified via CUPY_CACHE_DIR)

I think this recent failure will be fixed by merging #623:
https://github.com/rapidsai/cucim/actions/runs/6711052263/job/18238149350?pr=619

In discussion with Vyas offline, we've agreed to go ahead and merge. We can follow up on anything else in subsequent PRs/issues

Thanks Greg for the PR and everyone for the reviews! 🙏

/merge


Eclipse style file syntax check status highlighting in the file menu bar

For angular2 projects which contain numerous typescript files, a module/class/function name mismatch in one file causes problems in the dependent files (often during code refactoring).
As of now, VScode highlights the error in the dependent file with a red underline on the imported variable name. Instead of manually going through all the dependent files, it would be nice if VSC can highlight the files which have problems ( like broken file icon in file list menu in eclipse ).
VScode version : 1.13.1

Asks from this feature request is present in VScode Version 1.20.1. Hence closing this issue.


tinymce stores full image path instead of server relative path

refs: #871 (I don't remember linking an issue under 1000, this one is ooooooooold!!!!!)
Problem: When using tinymce with elfinder connector, if you select an image, tinymce would save the relative server path into database thus rendering the usability of the image useless after fetching from database.
Instead of saving https://backpack.com/uploads/image.jpg it would store ../../../uploads/image.jpg
This makes tinymce store the full image path instead of the relative one.

A new inspection was created.

The inspection completed: No new issues

@pxpm I tested, and it's working as expected.
My question is, should we really be storing absolute URLs?
Not so long time ago I had to migrate a domain of a Wordpress site, and Wordpress does the same, it stores absolute paths to images. I had to figure out a way to change hundreds of references in the database, an easy find and replace on the SQL may be enough in our case (on Wordpress it was not), anyway it could be avoided.

@pxpm I tested, and it's working as expected.
My question is, should we really be storing absolute URLs?
Not so long time ago I had to migrate a domain of a Wordpress site, and Wordpress does the same, it stores absolute paths to images. I had to figure out a way to change hundreds of references in the database, an easy find and replace on the SQL may be enough in our case (on Wordpress it was not), anyway it could be avoided.

I agree with you in half of the question, so as we don't store the absolute path when using an image field. But for a WYSIWYG editor I think it makes sense to store the absolute path, otherwise it would not be WYSIWYG, because you can't {!! $entry->content !!} in some blade file, so technically what you see is not what you are going to get if you store relative paths in the database.
In doubt, call master Yoda! ping @tabacitu

Ugh. You both bring some very good points. Any way TinyMCE lets us store absolute URLs, but without the domain? So:

not ../../../uploads/image.jpg
not https://backpack.com/uploads/image.jpg
but instead uploads/image.jpg

This would fix both problems, I think. Right?

Ugh. You both bring some very good points. Any way TinyMCE lets us store absolute URLs, but without the domain? So:

not ../../../uploads/image.jpg
not https://backpack.com/uploads/image.jpg
but instead uploads/image.jpg

This would fix both problems, I think. Right?

Unlikely.
<img src="uploads/img.jpg">

Will render different results if you are in https://backpack.com or in https://backpack.com/admin.

If paths are relative to the origin, that will not be a problem, so; /uploads/image.jpg (note the slash in the beginning)
Will render successfully on https://backpack.com or in https://backpack.com/admin.

A new inspection was created.

If paths are relative to the origin, that will not be a problem, so; /uploads/image.jpg (note the slash in the beginning)
Will render successfully on https://backpack.com or in https://backpack.com/admin.

Sure! Didn't think about that, just looked at @tabacitu example!
Good news for us, tinymce has that option! Just updated the PR!
Thanks

Perfect 👌

The inspection completed: No new issues


Allow to reuse Pylenium instance accross tests

Re-creating the whole Pylenium session per test is really expensive. Since the py fixture is bound to the function scope it encourages to put multiple tests into one test function to improve performance. But this is bad for result reporting if thing go wrong.
For example I sometimes loop over different variables instead of using pytest.mark.parametrize to avoid the performance penalty of recreating the Pylenium session for every parameter. But this has the downside that if one value fails the test will be aborted and the following values won't get tested, so we don't get results for them.
I'm not sure yet how an ideal solution would look like. I experimented locally by having a class scoped def _py fixture which is used by the py fixture:
@pytest.fixture(scope="class")
def _py(_py_config):
    py = Pylenium(_py_config)
    yield py
    py.quit()

@pytest.fixture(scope="function")
def py(_py, test_case, py_config, request, rp_logger):
    ...

This will then reuse the Pylenium instance across tests in the same class. Of course such behavior would need to be documented well and probably there is a better approach that I'm missing.

related to the expensive part of creating a new session with py:
I am wondering if there is a flag or config value that could be added to avoid checking your current browser version, then reaching out to the internet to check if there is a new version every time a py session is created?
It was sort of funny, when I first started using pylenium I ran into an issue with webdriver manager at the beginning of each test taking forever to go through its steps.  It didn't happen all the time.  By the end of the day, it was sooo slow.  I thought it was my network being slow every once in a while, but then figured out it was actually GitHub's API rate limiting coming into effect.  I tried for a while to think of ways to workaround the WDM functionality that in my own pytest framework, but no success.
I realize there are work arounds such as:

pinning the browser version
setting the local key value in the config
using selenium server/grid

@rnestler Sorry for taking so long to get to this. I'm thinking of adding two more Pylenium fixtures:

pys - session-scoped Pylenium instance
pyc - class-scoped Pylenium instance

What do you think?

* `pys` - session-scoped Pylenium instance
* `pyc` - class-scoped Pylenium instance

What do you think?

Sounds reasonable and useful :slightly_smiling_face:


Enable unfocused acrylic

Summary of the Pull Request
Closes #7158
Enabling Acrylic as both an appearance setting (with all the plumbing), allowing it to be set differently in both focused and unfocused terminals. EnableUnfocusedAcrylic Global Setting that controls if unfocused acrylic is possible so that people can disable that behavior.
References and Relevant Issues
#7158 , references: #15913 , #11092
Detailed Description of the Pull Request / Additional comments
Allowing Acrylic to be set differently in both focused and unfocused terminals:
A

B

C

D

"profiles":
{
    "list":
    [
        {
            "commandline": "pwsh.exe",
            "name": "A",
            "unfocusedAppearance":
            {
                "useAcrylic": true,
            },
            "useAcrylic": true,
        },
        {
            "commandline": "pwsh.exe",
            "name": "B",
            "unfocusedAppearance":
            {
                "useAcrylic": false,
            },
            "useAcrylic": true,
        },
        {
            "commandline": "pwsh.exe",
            "name": "C",
            "unfocusedAppearance":
            {
                "useAcrylic": true,
            },
            "useAcrylic": false,
        },
        {
            "commandline": "pwsh.exe",
            "name": "D",
            "unfocusedAppearance":
            {
            },
            "useAcrylic": false,
        },
    ]
}

A: AcrylicBlur always on
B: Acrylic when focused, not acrylic when unfocused
C: Why the hell not. Not Acrylic when focused, Acrylic when unfocused.
D:  Possible today by not using Acrylic.

EnableUnfocusedACrylic global setting that controls if unfocused acrylic is possible
So that people can disable that behavior:

Alternate approaches I considered:
Using _InitializeBackgroundBrush call instead of _changeBackgroundColor(bg)  in ``TermControl::_UpdateAppearanceFromUIThread. Comments in this function mentioned:
// In the future, this might need to be changed to a
// _InitializeBackgroundBrush call instead, because we may need to
// switch from a solid color brush to an acrylic one.

I considered using this to tackle to problem, but don't see the benefit. The only time we need to update the brush is when the user changes the EnableUnfocusedAcrylic  setting which is already covered by fire_and_forget TermControl::UpdateControlSettings
Supporting different Opacity in Focused and Unfocused Appearance???
This PR is split up in two parts #7158 covers allowing Acrylic to be set differently in both focused and unfocused terminals. And EnableUnfocusedAcrylic Global Setting that controls if unfocused acrylic is possible so that people can disable that behavior.
#11092 will be about enabling opacity as both an appearance setting, allowing it to be set differently in both focused and unfocused terminals.
Skipping the XAML for now:
“I actually think we may want to skip the XAML on this one for now. We've been having some discussions about compatibility settings, global settings, stuff like this, and it might be _more- confusing to have you do something here. We can always add it in post when we decide where to put it.”
-- Mike Griese
Validation Steps Performed
When Scrolling Mouse , opacity changes appropriately, on opacity 100 there are no gray lines or artefacts

When Adjusting Opacity through command palette, opacity changes appropriately, on opacity 100 there are no gray lines or artefacts

When opening command palette state goes to unfocused, the acrylic and color change appropriately

Stumbled upon a new bug when performing validation steps #15913

PR Checklist

[ ] Closes #7158
[X] Tests added/passed
[X] Documentation updated

If checked, please file a pull request on our docs repo and link it here: #xxx

[x] Schema updated (if necessary)

There were a lot of commits let me know if you want me to stash them

There were a lot of commits let me know if you want me to squash them

All your commits will be squashed automatically when the pull request merges into main. 🙂

This is very nice, thank you for doing it! We'll review it over the next few days. :smile:

haven't understood yet why EnableUnfocusedAcrylic is necessary if we already have UseAcrylic for the unfocused appearance

Last time we brought this up in team sync (probably >1yr ago), there was discussion of having a global opt-out of unfocused acrylic to revert to the old behavior. Just as a potential compat setting. Or something that we could override with some sort of "battery saver mode" (ala #9600).

This is very nice, thank you for doing it! We'll review it over the next few days. 😄

Okay , thanks for the heads up!
@lhecker @zadjii-msft @DHowett
Let me know if something need to be changed.

@zadjii-msft @lhecker
I got some c++ code working for checking whether battery saver mode is on aswell as if battery charger is plugged in or not.
I could make an override for battery saver mode.
When Batterycharger is unplugged and/or battery saver mode is active EnableUnfocusedAcrylic could be overridden to False?
Not sure where this can be override in the update settings or something in such a way that
_settings->EnableUnfocusedAcrylic() gets overriden to False or whether it will fetch the settings one?
Can take a look

I looked at it and it seems like acrylic is already getting turned off when battery saver mode is active, but when battery is not charging acrylic is still working. I can make it so that enableunfocusedacrylic gets overriden to false when battery is not charging

@zadjii-msft @lhecker
Awesome that it got merged! Am a bit disappointed though to be frank, had expected to get butchered more in the review process and get tons of constructive criticism and learn many things in the process. Like here: https://github.com/microsoft/terminal/pull/15795
Why did that not happen? How can I get that?
@carlos-zamora I think battery saver mode would make it way higher quality for what it's worth.
I assume unfocused Acrylic will really drain the battery.

Am a bit disappointed though to be frank, had expected to get butchered more in the review process and get tons of constructive criticism and learn many things in the process and grow a lot. Like here: #15795
I would like that, why did that not happen? How can I get that? I guess PR's need to have more lines of code? What are some issues that require lots of code to be solved?

Not every code review is going to go the same way! As an example, James Holderness submits huge pull requests that get very few comments. It's because he is comfortable with our code, and we are comfortable with the way that he does his work. Now, not everybody has been working with the team for as long as he has--like tusharsnx (#15795). They are not familiar with our practices, but they ARE still submitting large changes.
The bottom line is:
If you submit small changes, they are less contentious. There is less stuff to talk about, or to be worried about. This is a good thing!
If you submit larger changes, there are more points for discussion. More code, more arguments, more areas. The more stuff you touch at once, the closer the team has to look to make sure it all fits together right.
Sometimes, it goes smoothly. You just do everything perfectly. Sometimes, it goes differently and you get a lot of comments. Maybe there's something you understand very well (and we won't challenge you!) or you've done a lot of research (and the PR goes smoothly)... and sometimes you need to be taught something about how the project fits together or how the language works, etc.

As you submit more and larger pull requests, you'll get more comments. Eventually, you will be so good at it that you will get less and less comments! :smile:

Yea I couldn't have said anything more. If I had anything to add, it might be that we hashed out a lot of the edge cases in the side discussion in #2531 before you even got to the PR 😄

@zadjii-msft  @DHowett @lhecker Are there's any relevant opportunities at Microsoft that would let me work on this project or similar ones to it?

@zadjii-msft @lhecker @DHowett
Checked it out, wanted to point out that
The doc/cascadia/profiles.schema.json changes don't appear to be updated.
https://[raw.githubusercontent.com/microsoft/terminal/release-1.18/doc/cascadia/profiles.schema.json
Doesn't have entree for enableunfocusedacrylic  or the useacrylic for unfocused.


removing limitation bullet

removing metric_time limitation as this was resolved in https://github.com/dbt-labs/metricflow/issues/825
What are you changing in this pull request and why?

thanks @Jstein77 ! folded i your feedback and will merge this now!


add support for res.json and binary data cache

Currently the module only caches on the use of res.send and has issues with binary files and JSON. This PR should help resolve such issues, but might need a little more work.
Tests now use supertest rather than a spawned process, I found this easier to work with. Let me know your thoughts!
Caching occurs on data passed to res.socket.write, not res.send now. This is is the main update that facilitates support for res.json and binary responses. Cached items now represent the data sent to the response stream too, so this is what gets written to the cache:
HTTP/1.1 200 OK
X-Powered-By: Express
Content-Type: text/html; charset=utf-8
Content-Length: 46
ETag: W/"2e-PQ7Dm+NYwzgkRT8czBTdcQ"
Date: Thu, 26 May 2016 03:26:57 GMT
Connection: keep-alive

Now is Wed May 25 2016 22:26:57 GMT-0500 (CDT)

One potential issue is the Date header is cached; we might need to work around this?

I believe this will fix:

#40
#43
#51
#52
#54

The build is failing, but I can't see why. Should I be able to see the output? They pass locally so I'd need the Travis output to figure it out.

I created a new set of module to handle this since I needed more features, it's express-expeditious.
Will leave this PR open in the event it is ever merged 👍

@evanshortiss I understand this is old as hell but can you redo this PR for the dev branch? It would be greatly appreciated.


Feature request: unhardcode blog path

Right now, the "Latest post" feature requires you to have a blog section. It'd be nice if this could be customized (for example, if you wanted to use /posts/ or /articles/ instead).

Fixed by 25020d2


calling expandAll() in the initialized event leads to an error

Hi,
when calling the following command in the initialized event I get an error:
this.treeComponent.treeModel.expandAll();
ERROR TypeError: Cannot read property 'forEach' of undefined
at TreeModel.webpackJsonp.../../../../angular-tree-component/dist/models/tree.model.js.TreeModel.expandAll (tree.model.js:248)
at executeAction (mobx.js:854)
at TreeModel.res (mobx.js:845)
The error is because the treeModel.root property is undefined at that moment... anybody else encountered that problem?
In the documentation of the initialized event it says that this is the event which can be used for expanding the nodes... so at the moment as far as I see this, this is a bug.

@Gerros
Can you try like below
  onInitialized(tree) {
     tree.treeModel.expandAll();
  }

<tree-root   #tree
      [nodes]="nodes"
      [options]="customTemplateStringOptions"
      (onInitialized)="onInitialized(tree)">
      <ng-template #treeNodeTemplate let-node>
        {{ node.data.name }}
        {{ childrenCount(node) }}
      </ng-template>
      <ng-template #loadingTemplate>Loading, please hold....</ng-template>
 </tree-root>

hope this will help,
Please share the output
Cheers
Abhi.

I tried it out with a version where I still had this error and unfortunately this did not help. Still the treeModel.root is undefined. But in the meantime I do not get this error anymore.
The difference to the version where I get the error is that I got rid of some setTimeout calls. These setTimeout calls I have as workaround due to some "detected change after change detection exception". Maybe those setTimeouts were the reason which lead to this error... can not say for sure.
Thanks @AbhiThakare !!

I faced the same error.
It works fine on version < 3.7.0.
I guess the the cause may be that timing of firing initialized event changed.

It works with latest version:
https://plnkr.co/edit/9TrH4W42S0sWFUCyGwYF?p=preview

@AbhiThakare Hi I have tried this and the nodes do not expand. There is no errors.

Hi, has this issue been solved ?
Thanks

I have same issue. My data is combination of static and dynamic. Can someone help me to fix this?

I am on version 7.0.1 and doing in ngAfterViewInit seems to work for me
ngAfterViewInit() {
        if(this.tree && this.tree.treeModel) {
            this.tree.treeModel.expandAll();
        }
    }


@ValidateNested doesn't work

Hi. Dunno where open issue.
async name(
  @Body() params: A,
 ) {
   return "test"
}

export class A {
  @ValidateNested({ each: true })
  myArray: B[]
}

export class B {
  @IsPositive()
  myNumber: number
}

{ "myArray": [ {} ] } doesn't throw error
{ "myArray": [ {"myNumber": -1} ] } same

Hi this issue is related to class-validator and it's tracked there: https://github.com/pleerock/class-validator/issues/83


Ambiguity for "map results" on list view

The options for "map results" and "all results" are really confused to people. We are going to remove this feature for AGU.

fixed


Suggestion: Add MessageBox Samples for "Confirm" and "Alert" in abap2UI5 (Z2UI5_CL_DEMO_APP_008)

Hi guys,
I would like to propose adding two MessageBox samples in abap2UI5, similar to the ones available in the UI5 Demo Kit. The samples are for "Confirm" and "Alert" messages.
Current State in UI5 Demo Kit and abap2UI5:

Updated abap2UI5 Samples:

Result After Execution:

Confirm MessageBox Execution Result:

Alert MessageBox Execution Result:

Adding these examples will allow us to align it closer to the UI5 Demo Kit, and they can serve as a guide for developers to implement similar functionalities in their applications.
I have submitted PR https://github.com/abap2UI5/abap2UI5-samples/pull/226 to implement this change. In case there are any questions or comments, please feel free to reach out.
Thank you for considering this suggestion.
Best regards,
Francisco Milán

i think there are check demo 002 footer

Hi @choper725,
Thank you for your recommendation. I checked the footer of demo 002, and indeed, all the different types of MessageBox are demonstrated there.

However, I would like to suggest that, as much as possible, we align our abap2UI5 examples with those in the UI5 Demo Kit. By doing this, it will be easier for people already familiar with that site to find what they are looking for when they need to work with abap2UI5.
Replicating the examples from the UI5 Demo Kit will facilitate the transition and make it more intuitive for users to adopt abap2UI5.
Thanks again for your input.
Best,
Francisco Milán

Hi @francisco-milan,
good idea! making everything as similar as in the demo kit is a very good plan.
the sample repository grew very fast and i did not expect in the beginning we will end up at a certain point with more than 200. so thank you again also @choper725  ;)
you will find a lot of stuff here and there which needs to be refactored, naming, unused code etc. always feel free to make corrections and bring it closer to the demo kit, this is a big help for us. PRs are merged.
Best regards.

Hi @oblomov-dev,
Thank you for the positive feedback! I appreciate your support and encouragement.
Before closing this issue, I would like to make a few more changes to ensure that Sample 002 aligns more closely with the sample in the UI5 Demo Kit. I will be submitting a new PR soon to address these adjustments.
Best,
Francisco Milán.

New PR has been submitted https://github.com/abap2UI5/abap2UI5-samples/pull/229
Best,
Francisco Milán.

@francisco-milan thank you, merged 🙏


Android: Error:Execution failed for task ':react-native-proximity:compileReleaseJavaWithJavac'.

Hello, thanks for the great RN module.
I'm able to use in iOS but have an issue with Android.
node_modules/react-native-proximity/android/src/main/java/com/RNProximity/RNProximityPackage.java
Error:(19, 5) error: method does not override or implement a method from a supertype
Error:Execution failed for task ':react-native-proximity:compileReleaseJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Thank you for taking the time to take a look at the issue.

@pratih just delete lines:
    @Override
    public List<Class<? extends JavaScriptModule>> createJSModules() {
      return Collections.emptyList();
    }

This has been fixed with https://github.com/williambout/react-native-proximity/pull/8


ORC-1639: [C++] Simplify flags in CMake and fix corresponding compiling errors

What changes were proposed in this pull request?

Remove unnecessary compiler flags and replace -Weverything with -Wall.
Fix warnings and errors that emerge after the flag change.

Why are the changes needed?
The C++ library has added -Weverything which results in a bunch of -Wno-xxx flags. We should reduce them as many as possible.
How was this patch tested?

Tested it locally with clang13, clang17 and gcc13.
Make sure all CIs are passed.

Was this patch authored or co-authored using generative AI tooling?
No.

BTW, @wgtmac , for the following PR description, please note that our CI are running Docker tests already (Debian11/Debian24/Ubuntu24/Fedora37/OracleLinux9)

TODO: verify all the docker images.

BTW, @wgtmac , for the following PR description, please note that our CI has been running Docker tests already (Debian11/Debian24/Ubuntu24/Fedora37/OracleLinux9)

TODO: verify all the docker images.

Sorry for missing that!

No problem at all.

Sorry for missing that!

BTW, we added Apple Silicon test coverage too.

What about the current title? @dongjoon-hyun

Looks nice!

Thank you for update, @wgtmac .

Merged to main.

Could you make a backporting PR to branch-2.0, @wgtmac ?

Thanks @dongjoon-hyun!
Opened https://github.com/apache/orc/pull/1828


Retention and cross-region error message

Description
module "cos" {
  resource_group_id      = module.resource_group.resource_group_id
  region                 = var.region
  cos_instance_name      = "${var.prefix}-cos"
  cos_tags               = var.resource_tags
  bucket_name            = "${var.prefix}-bucket"
  retention_enabled      = true
}

This errors out with the following message.
validate_cross_region_retention = var.cross_region_location != "us" && var.retention_enabled ? tobool("Retention is currently only supported in the US location for cross region buckets.") : true
The issue is that at no point the call is retrying to create a cross region bucket.

Resolved in v8.2.2