[SecretsManagement][Design] Set-Secret should support -Force

Summary of the new feature/enhancement
As a developer of vault extensions
In order to support overwriting
My Set-Secret implementation should be able to SupportsShouldProcess
Specifically, as a PowerShell developer, I am not comfortable shipping a function named Set-Secret that automatically overwrites secrets by default -- even if it is "hidden" in a specially named folder. Someone, somewhere is going to use that command without using SecretsManagement. So although SecretsManagement may implement logic to prevent acidental overwriting, I cannot rely on that particular implementation being the only one that calls this code.
As a C# developer, I'm not totally comfortable with that model for critical secrets either, and would prefer to write explicit Add and Update functions. I can live with Set, but would prefer it to have a bool overwrite = false parameter so I can be sure that all callers understands what is expected.
Proposed technical implementation details (optional)

Implementing script vault extensions would have a [switch]$Force parameter in Set-Secret which SecretsManagement would set (only) when appropriate.
Implementing compiled/binary vault extensions would have a bool overwrite = false parameter which SecretsManagement would set (only) when appropriate.

Hmm, when we discussed this internally, we thought '-Force' would be annoying and that the default behavior should be overwrite (with optional '-NoClobber').  I am fine either way, but to maintain consistency across all vaults I feel it should be implemented in the 'Set-Secret' cmdlet and not each individual vault implementation.  The internal vault implementation should assume 'force' and just write or overwrite the secret, returning an error only if the operation fails.

@PaulHigin as long as it has SupportShouldProcess so I can do set-secret -whatif (and maybe make the ConfirmImpact High since it has the potential to "delete" a secret), I'm cool with "Force" as the default and -noclobber as the alternate behavior.

I guess part of my problem is that (as I said in my comment on #42), I would rather these commands be (able to be) part of the public interface to my module.
If I was going to expose the command at all, then it's interface needs to make sense. The way these are written right now, they have to be hidden because they're not "usable" by human standards (we need the wrapper with -Force that checks before overwriting).
I guess it's fine if we're forcing people to hide them anyway, but it forces me to write a Set-MyVaultNameSecret wrapper that copies the logic of SecretManagement\Set-Secret ...

@jaykul looks like Paul already commited the change for now, so we can probably close this issue as a quick fix, and have a more involved conversation about the extensions interface in #42. What do you think?

Since we already made the change to be Set-Secret, we agree that -NoClobber makes the most sense as a switch..in terms of extension interface design, agree that we should continue to use #42 for that discussion


[Bug]: terminal keeps disconnecting

Error Message and Logs
I get a popup saying
Connection to terminal lost, please refresh the page.

It keeps popping up like every 500ms or so
Steps to Reproduce
Not sure, it happened as soon as I upgraded to v4.0.0-beta.338
Example Repository URL
No response
Coolify Version
v4.0.0-beta.338
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
ubuntu 24.04
Additional Information
Full out put of cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

I'm not able to connect to the terminal. Get that error every time I click Connect

Please update to v340, and let me know if it still exists.
If it still exists, please let me know how do you host your Coolify instance (normally, through Cloudflare Tunnels, etc).

Still doesn't work, different error though, when I click connect nothing happens and I see this in the console
VM790:137 WebSocket is already in CLOSING or CLOSED state.

Can someone access Coolify server and executes a docker command to get terminal logs?
run docker logs coolify-realtime
that would be helpful to debug this, thanks!

Please update to v340, and let me know if it still exists.
If it still exists, please let me know how do you host your Coolify instance (normally, through Cloudflare Tunnels, etc).

am having the same issue and am using Cloudflare Tunnels

I upgraded to v340 and it's still happening

347 works fine


BUG: dhcpcd 10.0.6 - in if_setup_inet6() check for DHPCD_IPV6RS needs to occur BEFORE disabling the kernel

void
if_setup_inet6(const struct interface *ifp)
{
struct dhcpcd_ctx *ctx = ifp->ctx;
int ra;
char path[256];
/* The kernel cannot make stable private addresses.
* However, a lot of distros ship newer kernel headers than
* the kernel itself so sweep that error under the table. */
if (if_disable_autolinklocal(ctx, ifp->index) == -1 &&
errno != ENODEV && errno != ENOTSUP && errno != EINVAL)
logdebug("%s: if_disable_autolinklocal", ifp->name);
=======> this check needs to get moved before the call to if_disable_autolinklocal()
* If not doing autoconf, don't disable the kernel from doing it.
* If we need to, we should have another option actively disable it.
*/
if (!(ifp->options->options & DHCPCD_IPV6RS))
return;

You've not said what the current code is doing wrong and what the correct outcome looks like for your use case.

And I quote: "in if_setup_inet6() check for DHPCD_IPV6RS needs to occur BEFORE disabling the kernel"

FYI:  This comment is out of date, as the linux kernel has supported stable private for quite a while now.
/* The kernel cannot make stable private addresses.

However, a lot of distros ship newer kernel headers than
the kernel itself so sweep that error under the table. */


Way to replace panels with each other when dragged

Let's say I have 4 panels in my layout.
What I want to accomplish: when I move panel 1 in the position of panel 4 (for example), I want them to switch places instead of the current drag and resize functionality that the Golden-Layout provides.

This would result in a complete different behaviour respect of standard one. I don't think that could be reachable without an heavy re-write of the code.....

As @ldetomi mentioned, I am not sure how this behaviour would work or how to implement such a feature without large code changes.

I also thought of this feature.  This is possible but requires changing how the drop zone highlighting works, and then swapping the contents of a dropped element with the other.  It is non-trivial but I do think it could be a useful feature.


Add more Cocoa bindings

This adds two new classes NSViewController and NSPopover. It also adds some new methods on other classes and updates the NSWindow's *WindowLevel to match MacOSX 11.3.

ahn, I didn't see this before. That would be perfect. :)
I'll update my branch to use those, to make sure everything that I need is there and update this PR.
Thanks. :)

Done all changes above.


Entering new line is slow in all cells except last

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
When entering new line with Enter there is a few seconds lag before it appears. This happens less in the last cell for some reason. This coincided with updating the VS Code, but I am not sure if it was direct cause. By slow I mean it takes 5-6 seconds to move the cursor to the next line.
VS Code Version
1.77.3
Jupyter Extension Version
v2023.3.1201040234
Jupyter logs
(My folder path changed to <path> for privacy)

Visual Studio Code (1.77.3, undefined, desktop)
Jupyter Extension Version: 2023.3.1201040234.
Python Extension Version: 2023.6.1.
Workspace folder <path>
User belongs to experiment group 'jupyterEnhancedDataViewer'
User belongs to experiment group 'jupyterTestcf'
info 16:28:27.474: LSP Notebooks experiment is enabled
info 16:28:29.681: Starting Jupyter Session startUsingPythonInterpreter, .jvsc74a57bd0f08154012ddadd8e950e6e9e035c7a7b32c136e7647e9b7c77e02eb723a8bedb.c:\Users\User\anaconda3\python.exe.c:\Users\User\anaconda3\python.exe.-m#ipykernel_launcher (Python Path: c:\Users\User\anaconda3, EnvType: Conda, EnvName: 'base', Version: 3.9.13 (main, Aug 25 2022, 23:51:50) [MSC v.1916 64 bit (AMD64)]) for '<path>' (disableUI=true)
warn 16:28:30.613: Failed to get activated env vars for c:\Users\User\AppData\Local\Programs\Python\Python37\python.exe in 2062ms
info 16:28:30.646: Process Execution: > ~\AppData\Local\Programs\Python\Python37\python.exe -c "import site;print("USER_BASE_VALUE");print(site.USER_SITE);print("USER_BASE_VALUE");"
> ~\AppData\Local\Programs\Python\Python37\python.exe -c "import site;print("USER_BASE_VALUE");print(site.USER_SITE);print("USER_BASE_VALUE");"
info 16:28:31.083: Process Execution: > ~\AppData\Local\Programs\Python\Python37\python.exe -m pip list
> ~\AppData\Local\Programs\Python\Python37\python.exe -m pip list
warn 16:28:39.757: No interpreter with path c:\Users\User\Anaconda3\envs\cs224n\python.exe found in Python API, will convert Uri path to string as Id c:\Users\User\Anaconda3\envs\cs224n\python.exe
warn 16:28:39.908: No interpreter with path c:\Users\User\Anaconda3\envs\cs224n\python.exe found in Python API, will convert Uri path to string as Id c:\Users\User\Anaconda3\envs\cs224n\python.exe
info 16:28:56.557: Process Execution: > ~\anaconda3\python.exe -m pip list
> ~\anaconda3\python.exe -m pip list
info 16:28:56.711: Process Execution: > ~\anaconda3\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
> ~\anaconda3\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
info 16:28:57.427: Process Execution: > ~\anaconda3\python.exe ~\.vscode\extensions\ms-toolsai.jupyter-2023.3.1201040234\pythonFiles\vscode_datascience_helpers\kernel_interrupt_daemon.py --ppid 21852
> ~\anaconda3\python.exe ~\.vscode\extensions\ms-toolsai.jupyter-2023.3.1201040234\pythonFiles\vscode_datascience_helpers\kernel_interrupt_daemon.py --ppid 21852
info 16:28:57.427: Process Execution: cwd: ~\.vscode\extensions\ms-toolsai.jupyter-2023.3.1201040234\pythonFiles\vscode_datascience_helpers
cwd: ~\.vscode\extensions\ms-toolsai.jupyter-2023.3.1201040234\pythonFiles\vscode_datascience_helpers
info 16:28:57.683: ipykernel version & path 6.15.2, ~\anaconda3\lib\site-packages\ipykernel\__init__.py for c:\Users\User\anaconda3\python.exe
info 16:28:57.847: Process Execution: > ~\anaconda3\python.exe -m ipykernel_launcher --ip=<IP_ADDRESS> --stdin=9008 --control=9006 --hb=9005 --Session.signature_scheme="hmac-sha256" --Session.key=b"6f919b89-d5c0-4328-aea0-c76da2c1457f" --shell=9007 --transport="tcp" --iopub=9009 --f=c:\Users\User\AppData\Roaming\jupyter\runtime\kernel-v2-21852MIv4OG1BEoIt.json
> ~\anaconda3\python.exe -m ipykernel_launcher --ip=<IP_ADDRESS> --stdin=9008 --control=9006 --hb=9005 --Session.signature_scheme="hmac-sha256" --Session.key=b"6f919b89-d5c0-4328-aea0-c76da2c1457f" --shell=9007 --transport="tcp" --iopub=9009 --f=c:\Users\User\AppData\Roaming\jupyter\runtime\kernel-v2-21852MIv4OG1BEoIt.json
info 16:28:57.847: Process Execution: cwd: <path>
cwd: <path>
info 16:29:02.712: Started Kernel base (Python 3.9.13) (pid: 12028)
info 16:29:02.914: Process Execution: > ~\anaconda3\python.exe ~\.vscode\extensions\ms-toolsai.jupyter-2023.3.1201040234\pythonFiles\printJupyterDataDir.py
> ~\anaconda3\python.exe ~\.vscode\extensions\ms-toolsai.jupyter-2023.3.1201040234\pythonFiles\printJupyterDataDir.py
warn 16:29:03.125: Got a non-existent Jupyer Data Dir file:///c%3A/Users/User/AppData/Roaming/Python/share/jupyter
info 17:09:00.285: Cancel all remaining cells true || Error || undefined
info 17:09:31.068: Cancel all remaining cells true || Error || undefined
info 17:10:48.811: Cancel all remaining cells true || Error || undefined
info 19:41:28.629: Cancel all remaining cells true || Error || undefined
info 19:46:04.678: Cancel all remaining cells true || Error || undefined
info 19:49:20.024: Cancel all remaining cells true || Error || undefined
info 20:06:45.130: Cancel all remaining cells true || Error || undefined

Coding Language and Runtime Version
Python 3.9.13
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

Related on Stack Overflow: Jupyter Notebook in VSCode entering new line in a cell is slow

More precisely, I add a new markdown cell, and press enter, it works all fine. But it's really slow when I press Enter in python cell.

@rebornix  @DonJayamanne

@aqlkzf sorry for reaching out late, can you please follow the troubleshooting guide https://github.com/microsoft/vscode/wiki/Performance-Issues and provide more details to help us troubleshoot?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


nixos-container, deterministic-uname, lsb-release: use substitute rather than substituteAll, fix cross-compilation

Description of changes
This change fixes cross-compilation of the deterministic-uname, lsb-release, and nixos-container scripts, all of which used the stdenv environment variable shell instead of runtimeShell string as the shebang... leading to a cross-compilation mess.
There's no other change in produced output. Rationale for using substitute instead of substituteAll is here:

https://github.com/NixOS/nixpkgs/issues/237216

Previously:

https://github.com/NixOS/nixpkgs/pull/300308

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

The shell substitutions look like the value would come from buildPlatform, not hostPlatform (the default) like the other substitutions. Does it really exist? hello.drvPath doesn't have it. Otherwise I wouldn't be surprised if these packages were broken when cross-compiled.

The shell substitutions look like the value would come from buildPlatform, not hostPlatform (the default) like the other substitutions. Does it really exist? hello.drvPath doesn't have it. Otherwise I wouldn't be surprised if these packages were broken when cross-compiled.

Right you are. I did the following on master:
nix-build -A pkgsCross.aarch64-multiplatform-musl.deterministic-uname

Then looked at the shebang at the top of the result (which is where @shell@ expands):
/nix/store/a1s263pmsci9zykm5xcdf7x9rv26w6d5-bash-5.2p26/bin/bash

Then used file:
$ file /nix/store/a1s263pmsci9zykm5xcdf7x9rv26w6d5-bash-5.2p26/bin/bash
/nix/store/a1s263pmsci9zykm5xcdf7x9rv26w6d5-bash-5.2p26/bin/bash: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /nix/store/ddwyrxif62r8n6xclvskjyy6szdhvj60-glibc-2.39-5/lib/ld-linux-x86-64.so.2, BuildID[sha1]=1098c4d83aff81fd6ddd5bc06fb9442388f4f51d, for GNU/Linux 3.10.0, not stripped

Definitely wrong.
It looks like the correct thing to do is use runtimeShell.

while substituteAll implementation may be terrible, the interface is much nicer than using substitute. couldn't substitueAll be re implemented so that the key / value pairs just passed to substitute using  the --subst-var-by flag? like:
# some nix code
substituteAllish {
 src = ./the/file;
 substitutions = {
   inherit coreutils;
   stuff = someComputation;
   etc.
 };
};

# substituteAllish mock implementation
{ lib, src, substitutions):
let
subs =  lib.flatten ( map (pair:  [ "--subst-var-by" pair.name pair.value ]) (lib.attrsets.attrsToList substitutions ));
in
substitute { inherit src; substitutions = subs; etc. }

?

I've been cooking exactly that patch @a-n-n-a-l-e-e. My hope is that I'll get through enough of these substituteAll refactorings to get a sense of how often there's a defect embedded in them to recommend a secondary approach. So far, there's basically a defect per patch.

Let's collaborate on what better would look like on #237216.


Fix: duplicate paragraph depends_on

Proposed changes
Amend duplicate paragraph depends_on in Compose file reference doc.

Deploy preview for docsdocker ready!
Built with commit bfbca254acc4aaf983adbf3a58ecfe6f4f804e5c
https://deploy-preview-8539--docsdocker.netlify.com

Deploy preview for docsdocker ready!
Built with commit 433064d2694962c1f99d0ebdb34f846ae2ed4e80
https://deploy-preview-8539--docsdocker.netlify.com

Hello team. Is anything else needed for this PR to get reviewed? Thanks!

Hello team. Is anything else needed for this PR to get reviewed? Thanks!

@thaJeztah @bermudezmt   Hi Maria/Sebastiaan - I'm not sure who the best person is for this - Chris Crone perhaps?

Hey @paigehargrave - I think all of us are in SF now. I'll see if I can find @ulyssessouza and get this resolved while we're here. :wink:


method设置restore模式后，直接发送请求缓存不生效

Discussed in https://github.com/alovajs/alova/discussions/289

Originally posted by wwwylo February 29, 2024
使用method直接调用send发送请求不会走缓存的逻辑，套上一个useRequest后生效，这是有意为之的吗？

:tada: This issue has been resolved in version 2.17.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


failed to run custom build command for `openai_trtllm v0.2.1 (/root/openai_trtllm)

Caused by:
process didn't exit successfully: /root/openai_trtllm/target/release/build/openai_trtllm-728705c75e096edb/build-script-build (exit status: 1)
--- stdout
cargo:rerun-if-changed=/root/openai_trtllm/triton_common/protobuf
cargo:rerun-if-changed=/root/openai_trtllm/triton_common/protobuf/grpc_service.proto
cargo:rerun-if-changed=/root/openai_trtllm/triton_common/protobuf/health.proto
cargo:rerun-if-changed=/root/openai_trtllm/triton_common/protobuf/model_config.proto
cargo:rerun-if-changed=/root/openai_trtllm/triton_common/protobuf/grpc_service.proto
cargo:rerun-if-changed=/root/openai_trtllm/triton_common/protobuf/health.proto
cargo:rerun-if-changed=/root/openai_trtllm/triton_common/protobuf/model_config.proto
cargo:rerun-if-changed=/root/openai_trtllm/triton_common/protobuf
--- stderr
Error: unable to compile Protocol Buffers for the Triton client

Please follow the protobuf installation (https://grpc.io/docs/protoc-installation/) to install protoc before compilation.

Please follow the protobuf installation (https://grpc.io/docs/protoc-installation/) to install protoc before compilation.

cool, it works!Thx!


NoClassDefFoundError happened when use  spring boot 2.2.6

ValueExtractorManager NoClassDefFoundError happened when use spring boot 2.2.6 . But work well with oracle jdk and zulu jdk.

platform : Windows 10 x64

jdk info

openjdk version "1.8.0_242"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_242-b08)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.242-b08, mixed mode)

variant : hotspot

test with other verdors :  oracle jdk , zulu jdk

just simple example with spring boot,

Log in detail as below ,
Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2020-04-21 12:11:38.522 ERROR 19280 --- [           main] o.s.boot.SpringApplication               : Application run failed

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'defaultValidator' defined in class path resource [org/springframework/boot/autoconfigure/validation/ValidationAutoConfiguration.class]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.validator.internal.engine.valueextraction.ValueExtractorManager
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1796) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:595) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:882) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:878) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:550) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
	at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:140) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
	at org.github.helixcs.myspringboot.examples.c5.redis.JwtAppBootstrap.main(JwtAppBootstrap.java:18) [classes/:na]
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.validator.internal.engine.valueextraction.ValueExtractorManager
	at org.hibernate.validator.internal.engine.ValidatorFactoryImpl.<init>(ValidatorFactoryImpl.java:140) ~[hibernate-validator-6.0.18.Final.jar:6.0.18.Final]
	at org.hibernate.validator.HibernateValidator.buildValidatorFactory(HibernateValidator.java:38) ~[hibernate-validator-6.0.18.Final.jar:6.0.18.Final]
	at org.hibernate.validator.internal.engine.ConfigurationImpl.buildValidatorFactory(ConfigurationImpl.java:364) ~[hibernate-validator-6.0.18.Final.jar:6.0.18.Final]
	at org.springframework.validation.beanvalidation.LocalValidatorFactoryBean.afterPropertiesSet(LocalValidatorFactoryBean.java:310) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1855) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1792) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
	... 15 common frames omitted

I ran the full test suite of Spring Boot 2.2.6 with AdoptOpenJDK 8u242 on Windows 10. Everything's green. Please provide a minimal sample that reproduces the problem and that we can run (e.g. sample project on GitHub).

Also, try 8u252 (just released)

Sample project is attached. Happens with adopt-openjdk-1.8.0_282.
configuration-backend.zip
output.txt

@ant-druha Your project starts without problems on my machine. Furthermore, org.hibernate.validator.internal.engine.valueextraction.ValueExtractorManager is not part of the JDK, but Hibernate Validation. So it's unclear why you blame the JDK.

So it's unclear why you blame the JDK.

Because it fails with this error only when running under this JDK. And works with others JDKs.

mvn spring-boot:run works for me. You're launching through IntelliJ, so maybe something goes wrong when declaring the classpath.

I do not understand then why the same classpath is working with any other 1.8 JDKs.

Thank you for checking. Hmm. It works for me with all other 1.8 JDK, including Zulu and Liberica except AdoptOpenJDK though.

@ant-druha did you find any fix for this issue? I'm facing this one, too. Except I am using Spring-Boot 2.2.2 and the project works on Oracle and Corretto JVM. The error occurs in a deployed version of the project.

Thank you for checking. Hmm. It works for me with all other 1.8 JDK, including Zulu and Liberica except AdoptOpenJDK though.

Also got the same issue when using AdoptOpenJDK1.8.  It works as normal when I change to Oracle JDK1.8/Corretto-1.8.

I solved the same problem by replacing it with oracle jdk 1.8.
Install the oracle jdk.

Why was this marked invalid?
I am getting in an environment that is locked down with a Security manager, not saying that the presence of the Security Manager does it but I get the same stack YET I can't reproduce it in a similar, local, environment that is not locked. Runs as standalone boot app and as app deployed on a local tomcat.
It's on openjdk8 but will upgrade to openjdk11 - there is no other trace/exception !

Why was this marked invalid?
I am getting in an environment that is locked down with a Security manager, not saying that the presence of the Security Manager does it but I get the same stack YET I can't reproduce it in a similar, local, environment that is not locked. Runs as standalone boot app and as app deployed on a local tomcat.
It's on openjdk8 but will upgrade to openjdk11 - there is no other trace/exception !

See the various comments above, upgrading to latest Adopt binaries solved the issue for various users.

Why was this marked invalid?
I am getting in an environment that is locked down with a Security manager, not saying that the presence of the Security Manager does it but I get the same stack YET I can't reproduce it in a similar, local, environment that is not locked. Runs as standalone boot app and as app deployed on a local tomcat.
It's on openjdk8 but will upgrade to openjdk11 - there is no other trace/exception !

See the various comments above, upgrading to latest Adopt binaries solved the issue for various users.

Yes, I saw all of that but just curious what is happening, the underlying case in important, no errors, no traces, no info. the class cannot be created. I have openjdk8, one of the latest, I will what happens when move to 11 today.

OK, so this issue is not invalid nor springboot related
What happens is when hibernate gets to be register as the JPA implementation and when a security manager is set, that class, ValueExtractorManager, would not get initialized and it would result in a weird exception that never seems to get logged or fired during the class defintion/creation
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.validator.internal.engine.valueextraction.ValueExtractorManager
	at org.hibernate.validator.internal.engine.ValidatorFactoryImpl.<init>(ValidatorFactoryImpl.java:173) ~[hibernate-validator-6.2.0.Final.jar:6.2.0.Final]
	at org.hibernate.validator.HibernateValidator.buildValidatorFactory(HibernateValidator.java:38) ~[hibernate-validator-6.2.0.Final.jar:6.2.0.Final]
	at org.hibernate.validator.internal.engine.AbstractConfigurationImpl.buildValidatorFactory(AbstractConfigurationImpl.java:451) ~[hibernate-validator-6.2.0.Final.jar:6.2.0.Final]
	at javax.validation.Validation.buildDefaultValidatorFactory(Validation.java:103) ~[jakarta.validation-api-2.0.2.jar:?]
	at org.hibernate.cfg.beanvalidation.TypeSafeActivator.getValidatorFactory(TypeSafeActivator.java:502) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.hibernate.cfg.beanvalidation.TypeSafeActivator.activate(TypeSafeActivator.java:84) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
	at org.hibernate.cfg.beanvalidation.BeanValidationIntegrator.integrate(BeanValidationIntegrator.java:131) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:283) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:468) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1259) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider.createContainerEntityManagerFactory(SpringHibernateJpaPersistenceProvider.java:58) ~[spring-orm-5.3.8.jar:5.3.8]

Adding this permission
("java.util.PropertyPermission" "org.hibernate.validator.force-disable-javafx-integration" "read")
or a wildcard "org.hibernate.*" should fix it.
Now, not a lot of tests are performed with the security manager enabled and lots of teams don't even bother to enable it ...
Hope this would help someone, one day!

@cmoisei Hi, we are facing the same issue on Azul JDK. Was wondering how to add the permission as you mentioned in your post when we start a spring boot application?

You can add them in the policy file that you specified at startup - that if
you run with a security manager.
On Thu, 18 Nov 2021 at 20:32, Aging @.***> wrote:

@cmoisei https://github.com/cmoisei Hi, we are facing the same issue on
Azul JDK. Was wondering how to add the permission as you mentioned in your
post when we start a spring boot application?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/adoptium/adoptium-support/issues/89#issuecomment-973671935,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAUAPP4RRW74MRDGRZQSAS3UMWZLDANCNFSM4MM7O36Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

OK, so this issue is not invalid nor springboot related
What happens is when hibernate gets to be register as the JPA implementation and when a security manager is set, that class, ValueExtractorManager, would not get initialized and it would result in a weird exception that never seems to get logged or fired during the class defintion/creation
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.validator.internal.engine.valueextraction.ValueExtractorManager
	at org.hibernate.validator.internal.engine.ValidatorFactoryImpl.<init>(ValidatorFactoryImpl.java:173) ~[hibernate-validator-6.2.0.Final.jar:6.2.0.Final]
	at org.hibernate.validator.HibernateValidator.buildValidatorFactory(HibernateValidator.java:38) ~[hibernate-validator-6.2.0.Final.jar:6.2.0.Final]
	at org.hibernate.validator.internal.engine.AbstractConfigurationImpl.buildValidatorFactory(AbstractConfigurationImpl.java:451) ~[hibernate-validator-6.2.0.Final.jar:6.2.0.Final]
	at javax.validation.Validation.buildDefaultValidatorFactory(Validation.java:103) ~[jakarta.validation-api-2.0.2.jar:?]
	at org.hibernate.cfg.beanvalidation.TypeSafeActivator.getValidatorFactory(TypeSafeActivator.java:502) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.hibernate.cfg.beanvalidation.TypeSafeActivator.activate(TypeSafeActivator.java:84) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
	at org.hibernate.cfg.beanvalidation.BeanValidationIntegrator.integrate(BeanValidationIntegrator.java:131) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:283) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:468) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1259) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider.createContainerEntityManagerFactory(SpringHibernateJpaPersistenceProvider.java:58) ~[spring-orm-5.3.8.jar:5.3.8]

Adding this permission ("java.util.PropertyPermission" "org.hibernate.validator.force-disable-javafx-integration" "read")
or a wildcard "org.hibernate.*" should fix it.
Now, not a lot of tests are performed with the security manager enabled and lots of teams don't even bother to enable it ...
Hope this would help someone, one day!

Thank you so much for this comment, when I removed javafx from my pom, the error went away.

好的，所以这个问题不是无效的，也不是springboot相关的
发生的情况是，当 hibernate 注册为 JPA 实现并且设置安全管理器时，该类 ValueExtractorManager 将不会被初始化，并且会导致一个奇怪的异常，该异常在类定义期间似乎永远不会被记录或触发/创建
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.validator.internal.engine.valueextraction.ValueExtractorManager
	at org.hibernate.validator.internal.engine.ValidatorFactoryImpl.<init>(ValidatorFactoryImpl.java:173) ~[hibernate-validator-6.2.0.Final.jar:6.2.0.Final]
	at org.hibernate.validator.HibernateValidator.buildValidatorFactory(HibernateValidator.java:38) ~[hibernate-validator-6.2.0.Final.jar:6.2.0.Final]
	at org.hibernate.validator.internal.engine.AbstractConfigurationImpl.buildValidatorFactory(AbstractConfigurationImpl.java:451) ~[hibernate-validator-6.2.0.Final.jar:6.2.0.Final]
	at javax.validation.Validation.buildDefaultValidatorFactory(Validation.java:103) ~[jakarta.validation-api-2.0.2.jar:?]
	at org.hibernate.cfg.beanvalidation.TypeSafeActivator.getValidatorFactory(TypeSafeActivator.java:502) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.hibernate.cfg.beanvalidation.TypeSafeActivator.activate(TypeSafeActivator.java:84) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
	at org.hibernate.cfg.beanvalidation.BeanValidationIntegrator.integrate(BeanValidationIntegrator.java:131) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:283) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:468) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1259) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final]
	at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider.createContainerEntityManagerFactory(SpringHibernateJpaPersistenceProvider.java:58) ~[spring-orm-5.3.8.jar:5.3.8]

添加此权限（“java.util.PropertyPermission”“org.hibernate.validator.force-disable-javafx-integration”“read”）
或者通配符“org.hibernate.*”应该修复它。
现在，在启用安全管理器的情况下执行的测试并不多，许多团队甚至懒得启用它......
希望有一天这会对某人有所帮助！

非常感谢您的评论，当我从我的 pom 中删除 javafx 时，错误就消失了。

是的，当我删除gs-ui-javafx时，我的错误也消失了，感谢提醒


publish stex to npm

Stex is not yet published on the public npm repository. Would it be possible to add it ?

@FredericHeem definitely.  I'll publish it momentarily

Done!  I just bumped to 0.2.0 and published to npm.


Embed on small screens, consider wrapping up menu

Would it be to much trouble to wrap up the menu system into a native dropdown like jsfiddle does when the jsbin appears on smaller devices?
https://www.dropbox.com/s/td6d97ecpbtxkmv/Screenshot 2014-09-25 09.01.50.png?dl=0

What about rearranging items with CSS for now?
Not create a complex dropdrown system, but only make sure there is no superposition. It's such a pain when using jsbin embedded in small screens.
I can make PR quickly if anyone agree.

I'd be happy to review a PR.
On Tue, 18 Aug 2015 14:25 Vincent De Oliveira<EMAIL_ADDRESS>wrote:

What about rearranging items with CSS for now?
Not create a complex dropdrown system, but only make sure there is no
superposition. It's such a pain when using jsbin embedded in small screens.
I can make PR quickly if anyone agree.
—
Reply to this email directly or view it on GitHub
https://github.com/jsbin/jsbin/issues/1955#issuecomment-132203915.


Controller button to UI

Describe your changes
What is the purpose of this part of the project? Which assets and/or scripts are you adding or editing? Describe below.
Checklist before requesting a review
Fill in by placing an x between the brackets below.

[X] I have performed a self-review of my code
[X] I have merged the master branch into my branch so it is up to date
[X] I have verified that the code will build and run
[X] I have checked that my changes do not conflict with other team members' work
[X] I have added or edited pages on the wiki to reflect these changes

Anything else we should know?
N/A
A grad student will review your changes and either approve and merge them or request changes. Please be responsive if changes are requested. Thanks!

Hi @imngui , In unity editor, can you click on the SetupUI script and in the public space from pressA, pressB, pressX, pressY, put the respective actions (PressA, PressB, PressX, PressY) by clicking on the circle button on the right side of the empty space and searching them? I created these action in the branch from unity editor. We can make a call if it doesn’t work

I did some updates, now you can just pull the changes and don't need to worry about the last comment

I did some updates, now you can just pull the changes and don't need to worry about the last comment

I pulled the latest updates. The UI is back and it the mirror button seems like it is working. Good work!
The other two buttons do not seem to work. When I press the A button it outputs:
NullReferenceException: Object reference not set to an instance of an object. NullReferenceException while executing 'performed' callbacks of 'XRIRightHand/PressA[/OculusTouchControllerRight/primarybutton]'

Hi @imngui , I updated the code with the mirror, replay and record button working. Can you check it please?


Add config to lazily recover cursors when recovering a managed ledger.

Fixes #7404
Motivation
Currently, we have to wait until all cursors to be recovered before completing opening a managed ledger. This results in very long recovery time for the managed ledger. Pulsar is a messaging/streaming system. Write availability is critical to a lot of core business applications. We need to make it always writable. Hence we should decouple loading cursors from loading managed ledger. This ensures producers can move forward immediately once the data ledgers are ready.
Modifications
Add config to lazily recover cursors when recovering a managed ledger.
Will initial cursor recovery and put it into uninitializedCursors map.
This can speed up managed ledger recovery and write availability,
but with the caveat that when topic is recovered we're not sure if all old cursor can be recovered or not.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change added tests and can be verified as follows:

Added unit test to verify ledger is ready before cursor fully recovered

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? ( docs / JavaDocs )

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot rerun unit-tests

/pulsarbot rerun unit-tests


TypeScript dynamic module loading issue using typeof

I am dynamically loading modules I have created like so:
myModule.ts
export class SomeClass {  ... } export type SomeType = {...}
In another file, I do:
  import * as MyModuleType from "./myModule"   if(...) {     let loadedModule: typeof MyModuleType = require("./myModule");      ...   }
(Sorry the code isn't formatted correctly. See http://stackoverflow.com/q/43938280/3867175)
The type of MyModuleType has both SomeClass and SomeType (as expected). Whereas the type of loadedModule has only SomeClass (incomplete type!). How can I solve this issue?
Version of typescript: 2.3.2
editor: atom, using atom-typescript v10.1.15
Thank you.

Replied to your post.

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


Added VK_EXT_sampler_filter_minmax extension support

Hi!
These manually defined extension structs are used to provide safe(r) wrappers around extension functions. VK_EXT_sampler_filter_minmax does not seem to contain any, hence all this does is re-export the name which is also available to your application as ash::vk::ExtSamplerFilterMinmaxFn::name(). What is your use-case for this struct?

Hi!
These manually defined extension structs are used to provide safe(r) wrappers around extension functions. VK_EXT_sampler_filter_minmax does not seem to contain any, hence all this does is re-export the name which is also available to your application as ash::vk::ExtSamplerFilterMinmaxFn::name(). What is your use-case for this struct?

Hi 👋🏽 Yeah I figured that this struct was not really useful, but I saw that ray_query was implemented the same way. I just thought it was a common nomenclature to expose an extension.

Hi 👋🏽 Yeah I figured that this struct was not really useful, but I saw that ray_query was implemented the same way. I just thought it was a common nomenclature to expose an extension.

@FuriouZz Right, and it was added by me without noticing :facepalm:
I'm removing it before a new crate version is released: https://github.com/MaikKlein/ash/pull/364

@FuriouZz Right, and it was added by me without noticing :facepalm:
I'm removing it before a new crate version is released: https://github.com/MaikKlein/ash/pull/364

Haha no worry @MarijnS95. I am going to close my PR 😅.
At the begining I wanted to work on the implemention for gfx and wgpu and I just discovered behind bunch of codes that the gfx part was already implemented and just the wgpu side is required. I lost some time too.
I was glad to contribute but finally it will be for a next time 😅🙄.

Haha no worry @MarijnS95. I am going to close my PR 😅.
At the begining I wanted to work on the implemention for gfx and wgpu and I just discovered behind bunch of codes that the gfx part was already implemented and just the wgpu side is required. I lost some time too.
I was glad to contribute but finally it will be for a next time 😅🙄.

This eye-opener was worth it :tada: . There are always open issues if you feel like contributing  :wink:

This eye-opener was worth it :tada: . There are always open issues if you feel like contributing  :wink:


Improve documentation

This pr contains reworked README with the following changes:

extended notes on compatibility with Hive/Impala drivers
enhanced installation notes
described using the extension with a standalone liquibase as well as with a Maven plugin
described extra configuration parameters supported by the extension
general formatting overhaul + useful links

:+1:

@eselyavka done


feat(SPV-XXX): update dependencies and go version

Pull Request Checklist

[ ] 📖 I created my PR using provided  : CODE_STANDARDS
[ ] 📖 I have read the short Code of Conduct: CODE_OF_CONDUCT
[ ] 🏠 I tested my changes locally.
[ ] ✅ I have provided tests for my changes.
[ ] 📝 I have used conventional commits.
[ ] 📗 I have updated any related documentation.
[ ] 💾 PR was issued based on the Github or Jira issue.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 48.98%. Comparing base (76c2208) to head (23e5518).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #624   +/-   ##
=======================================
  Coverage   48.98%   48.98%
=======================================
  Files         259      259
  Lines       12193    12193
=======================================
  Hits         5973     5973
  Misses       5621     5621
  Partials      599      599

Flag
Coverage Δ

unittests
48.98% <ø> (ø)

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

Continue to review full report in Codecov by Sentry.

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


Bugfix: Couldn't subclass Panel

I was trying to create a subclass from Panel and came into this snag. I'm not sure if there was a reason Panel was using a hard coded _constructor method, but I changed it to be more generic. I'm new to open source, so constructive criticism is welcome. Am I doing this right?

Welcome to open source! You're on the right lines, I've just highlighted a few potential problems. Other people who're more familiar with the design of panel may give you more suggestions. Remember, although the comments might come across as quite terse, we are grateful that you're using and improving the code.

Thanks for the feedback. I changed _constructor to return type(self), and the _constructorGroupBy thing was a consequence of sloppy search and replace, so I fixed that. Should I submit another request or keep this one?


delete-actor

additions to sqlite/record.clj, appropriate additions to delete.sql and query.sql, addition to backend/protocol.clj

Remember that SQLite is only half of the SQL LRS backend; there's also the Postgres version that will need to be implemented.

I also noticed that you did not use any instances of ON DELETE CASCADE. Which is fair, since that would require changes to the DDL which will require SQL migrations, and those are always inherently dodgy (at least moreso than just adding cascades manually like you have here).

Remember that SQLite is only half of the SQL LRS backend; there's also the Postgres version that will need to be implemented.

let him get a working SQLite first, then go back. TBH this is almost all ANSI and one-liners so that port is going to be 30 minutes once all is said and done.


Limitations of Page Extension Objects

Can you please provide content on what you cannot do through Page Extension Objects?
My concern is both as to which properties can be modified for existing controls (and which not), as well as assigned to new controls.
Also, the first phrase on this link indicates that you can add or override page functionality but it's not very clear how to achive this. Please note I'm not referring to layout in this context, but subscribing to triggers, adding functions, etc.
2 practical examples:

Customer wants to change the Style on "Lot No. Information List": if a lot is blocked, certain fields should change to 'unfavorable'. Can this be achieved through an extension, or must the page be substituted with a new page object?
New fields are added to Item Tracking (T336, T337, etc.). Of course they should only be editable on Inbound Entries (basically following the same principle as Expiration Date) on Page 6510. How should this be done?

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

ID: cdda7e30-30d9-ac83-abf7-267a7f634c6d
Version Independent ID: 5bf5ce87-f59a-d2ae-10b3-05eda02406b5
Content: Page Extension Object - Business Central
Content Source: dev-itpro/developer/devenv-page-ext-object.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Please - it's been 2 months already since I opened this thread - any comments?

Hello, sorry for the long wait on a reply. There are a number of questions in this issue, and I am not sure that I am giving you a fulfilling reply, but I can try to address some of the issues. At the moment, we do not have any guidance or best practice on when to do what. After the October´19 release, we might be able to provide some based on our experiences. For what's allowed and what is not allowed, IntelliSense and the compiler should be able to give you guidance. Specifically, for the . OnInit Trigger on PAG6510 or OnFindRecord Trigger on PAG9126, these two triggers are not available on page extensions. Objects related to item tracking are not extensible at the moment and would need a big redesign in the product. I hope this helps. Thanks.


Poor interaction between workspace dependencies and default-features

Problem
Apologies in advance if this is categorized incorrectly, I can see how this could be either a bug or feature request.
Recently introduced to Cargo is the ability to specify dependencies at the workspace level. Crates within that workspace can specify their dependencies as { workspace = true }, which results in that crate inheriting the dependency from their parent workspace.
With respect to features the inheritance works in a purely additive way, which I believe works well in general, but not in the case of default features.
For example say you have a workspace with two crates, foo and bar, both of these crates depend on tracing. You want to make sure foo and bar depend on the same version of tracing, so you define it in your workspace and have crates inherit from it. In the crate bar you want to disable default-features for tracing, but you cannot since when you inherit from a workspace it's in a purely additive way. The only way to disable default-features in bar is to disable it at the workspace level, this has the adverse effect of also disabling default-features for foo. In the crate foo you could specify default-features = true, but this feels like an anti-pattern.
Scaling this example up a bit and you can better see how this is an issue. Say you have a workspace of 50 crates, 10 of which depend on tracing. In 1 of the 10 crates you want to disable default-features, to do that it requires you to specify default-features = true for the other 9, and any crates in the future that depend on tracing.
Steps

Create a new Rust project, make it a workspace, add a workspace.dependency of tracing = 0.1.37 (or any other crate).
Add a new crate foo, add a dependency of tracing = { workspace = true }.
Add a new crate bar, add a dependency of tracing = { workspace = true, default-features = false }.
Observe a compiler warning when building bar, indicating that the default-features flag is ignored.

Possible Solution(s)
Allow inherited dependencies within a workspace to disable default features.
Notes
No response
Version
$ cargo version --verbose
cargo 1.69.0 (6e9a83356 2023-04-12)
release: 1.69.0
commit-hash: 6e9a83356b70586d4b77613a6b33f9ea067b9cdf
commit-date: 2023-04-12
host: aarch64-apple-darwin
libgit2: 1.5.0 (sys:0.16.0 vendored)
libcurl: 7.86.0 (sys:0.4.59+curl-7.86.0 system ssl:(SecureTransport) LibreSSL/3.3.6)
os: Mac OS 13.2.0 [64-bit]

Note: I tried a workaround of specifying default-features = true at the workspace level, and then default-features = false within bar at the crate level. That did not produce a compiler warning but bar still depended on default features, specifying false at the crate level had no impact.

Thanks for the detailed report!
Totally understand the inconvenience. I am sorry for telling you that this is an intentional behavior for following the additive rule of Cargo features. Please see this table from this comment https://github.com/rust-lang/cargo/pull/11409#issuecomment-1374225756. Changing the behavior could lead to a breakage.
Besides the intentional design, do you feel anything can be documented better in this chapter in Cargo Guide?

Thanks for linking the comment! I had searched through the various PRs and RFCs to see if this was covered, I missed that one though 🙂
Could I propose changing the behavior then? What would be the right process for this, submitting an RFC maybe?
I totally understand that features within Cargo need to be additive, without this property any projects with a decent number of dependencies could fail to compile because the same crate could be depended on twice, but with conflicting feature sets, making the project impossible to compile. Because this additive property exists, having a crate opt out of a feature that the workspace enables should be entirely possible? In other words, it shouldn't cause any compilation issues? I don't believe the ability to generically opt out of a feature is needed, but without the ability to disable default features at the crate level, workspace inheritance is much less useful of a feature.
Recently I worked on migrating a decently large codebase to use workspace inheritance, https://github.com/MaterializeInc/materialize/pull/19375, but ran into this issue with default features. Without the ability to disable default-features at a crate level, I don't think we'll go through with this switch. Which is disappointing because having a single location to define all of our dependency versions would be super useful!
Thanks for chatting about this 🙂

FWIW, https://github.com/rust-lang/cargo/issues/3126 has more discussions about the future of default-features and some syntax to subtract a feature. Maybe this would help?
For proposing a change, I currently have no idea which route can fix this issue, as changing the behavior leads to another breakage. However, I think you can draft your idea here and if you can think of any transition to alleviate the potential breakage, please include them!

I've had a growing feeling that being able to inherit things besides dependency sources was a mistake.  Rarely do implementation requirements mean every package needs the same set of features, optional, public, etc.  Instead, they diverge.  The one exception is workspace hacks but workspace.dependencies alone is insufficient to support that.
If I felt confident enough in this stance, we could move to only allow inheriting source information in the next Edition (the wording is so that the package's Edition is in control since workspaces don't have an Edition).  However, I am not confident enough at this time to move in that direction.
People can do it themselves (or with the help of a clippy lint) except for this issue.
I wonder if what we could do on an Edition boundary is to make it so that the lack of default-features in workspace.dependencies doesn't apply the default when inheriting but is ignored.
@Muscraft thoughts?

We talked about this in today's cargo team meeting.
Its a bit unclear if we'd want to go the full way and deprecate features, default-features in workspace.dependencies, removing them in an Edition.

We gave users a tool and might be hard to claw it back, even if its "correct"
We theorize most uses are for implementation focused and not requirements focused but its hard to say for sure

If we want to consider that, likely the best route is a short-term solution to this issue with a lint to discourage default-features / features.  If the lint were in an opinionated linter like clippy, it could even be warn by default one day (ie be promoted from pedantic to style).  Whether its allow or warn by default, we could search github to see how much it is used (while recognizing the bias that open source might be doing things differently than corporate).
For a short-term solution, it would likely be to make default-features in a workspace.dependencies be a Option<bool> where the None case means "unset" (compared to today where its "true")
One concern with this short-term route is that is isn't  as consistent in behavior across cargo.  If we deprecated default-features / features, then we would become consistent again, but instead of being consistent with dependencies, it would be patch.  However, sometimes user expectations don't favor consistency and the more intuitive route is inconsistent.  Maybe this is one of those cases.
We do need to recognize the cost of ecosystem churn with any of this.  This would be a subtle behavior change that people would need to migrate through, both in code and in education.  We'd also need to make the docs more complicated to cover the cases for each Edition.

To summarize the proposal, quoting from @Muscraft  who built this on top of the work of @ehuss in #11409

Workspace
Member
1.64 behaviour
1.69 behavior
proposed 202X Edition behavior
Reasoning

nothing
df=false
Enabled
Enabled, warning that it is ignored
Disabled
Basically means let the package control default features when not specified

df=true
df=false
Enabled
Enabled, warning
Enabled, warning
Should have been an error in the past since the field is ignored. May change to an error in the future.

nothing
df=true
Enabled
Enabled
Enabled
There is no conflict about default being enabled.

df=true
df=true
Enabled
Enabled
Enabled
^Same

nothing
nothing
Enabled
Enabled
Enabled
No ambiguity.

df=true
nothing
Enabled
Enabled
Enabled
Enabled

df=false
df=false
Disabled
Disabled
Disabled
No ambiguity.

df=false
df=true
Disabled
Enabled
Enabled
This allows members to decide whether or not they want default features. The workaround of features=["default"] seems unnecessary.

df=false
df=nothing
Disabled
Disabled
Disabled
Natural way to write "give me whatever was written in workspace".

The proposal looks good to me @epage.
I'd prefer an error in scenario no. 2, since we have the freedom to do that at an edition boundary.

Hey @epage, thanks for reconsidering this! The behavior table you listed above makes sense to me and fixes the original concerns I had.
FWIW I also like the idea that workspace dependencies should only be able to inherit source information, but I think the correct long term solution is a lint guiding users away from it, instead of disallowing it entirely. An example of where it would be nice to inherit features from the workspace is when it's a performance related feature, e.g. smallvec's union feature. You might want to enable union for all uses of smallvec in your workspace, and workspace dependencies seems like the right tool for that. All of this to say, if a lint is created it would be nice if users could exclude specific crates.

I'd prefer an error in scenario no. 2, since we have the freedom to do that at an edition boundary.

I left that out because its being talked about as part of #13629

A way to reframe this: instead of merging a package dependency into a workspace dependency, keeping the workspace dependency's defaults, we could switch to merging a workspace dependency into a package dependency, keeping the package dependency's defaults.


fix(esl-mixin-element): major fix for nested hierarchy mixin disconnection

Closes: #2505

:tada: This issue has been resolved in version 4.18.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 5.0.0-beta.24 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


issue with input component in safari

Bug, feature request, or proposal:
BUG
What is the expected behavior?
Input placeholders should move up
What is the current behavior?
Input placeholders remain there and actual input is overwritten
What are the steps to reproduce?
open the official plunkr in safari
https://material.angular.io/components/component/input ( see plunkr in this link on safari)
Which versions of Angular, Material, OS, browsers are affected?
angular 2.x
material 2.0.0 beta
browser: safari
Is there anything else we should know?
I am using ng-cli. the official docs page renders the input correctly but the official plunkr when opened in safari is having the same issue.

you should perhaps be more specific with the version of safari, works fine on mine (latest)

Please make sure that you have included the animation package for angular core. You can find more information about implementing the animation package here https://github.com/angular/angular/blob/master/CHANGELOG.md#400-rc1-2017-02-24

input animations are done with just css, this shouldn't be the issue

@bmrinal As fxck suggested, can you provide more info? I checked the official plunker on Safari version 10, but it's working as expected. Did you change the plunker code at all?

@kara No I didn't changed anything...I shall provide more details by today....safari version specifically....

Closing as input styling has been rewritten/changed and this no longer applies.


Preact calls onChange handler when using dispatchEvent while React does not

Hello!
For one of my projects i'm using a library which, in the onChange handler, uses dispatchEvent to dispatch a change event on the changed element. This works fine with React since React doesn't call callbacks when the event was dispatched via dispatchEvent. However Preact seems to call it's onChange handler even when the event was triggered by dispatchEvent. This causes an infinite loop which in turn causes Uncaught RangeError: Maximum call stack size exceeded.
An example:
import React, {Component, PropTypes} from 'react';

class App extends Component {
  constructor () {
    super();
    this.state = {val: ''};
    this.onChange = this.onChange.bind(this);
  }
  onChange (evt) { // This will be called recursively with Preact while with React it will only be called once per change
    this.setState({val: evt.target.value});
    console.log('Changed!');
    evt.target.dispatchEvent(new Event('change', {
      bubbles: true,
      cancelable: true
    }));
  }
  render () {
    return (
      <div>
        <input type="text" onChange={this.onChange} value={this.state.val}/>
      </div>
    );
  }
}

When having react & react-dom aliased as preact-compat this will throw an exception. If you comment out the aliases so that React is used then there is no error and the code works as expected.
I will try to look into this to find out where it happens but i would appreciate some help from someone who have more experience with the code-base

To me it seems that React adds an oninput listener to textfields when a user specifies onChange events on them instead of adding onchange listeners(See: https://github.com/facebook/react/blob/e3131c1d55d6695c2f0966379535f88b813f912b/src/renderers/dom/shared/eventPlugins/ChangeEventPlugin.js)
So i'm guessing something similar should be done with Preact?

I did something like this:
-    name = toLowerCase(name.substring(2));
+    if (name === 'onChange' && node.nodeName === 'INPUT' || node.nodeName === 'TEXTAREA') {
+      // onchange -> oninput if node == input/textarea
+      name = 'input';
+    } else {
+      name = toLowerCase(name.substring(2));
+    }

and it works for my use case. React did some browser-compat checking before which is a good idea.

Hi @linde12 - looks like we'll want to do that transformation, yup. Want to submit the PR, or should I add you as a reviewer on one?

Hey!
If you have time it'd be nice if
I wouldn't mind throwing up a PR but i'm this diff doesn't contain any backwards-compatible solution. IE9 doesn't fully support the input event even if it claims so, and i guess you want to keep on supporting it.
If you're fine with the way it is now or want to add some code to make it IE9-compatible then i'd be happy to review!
Tell me if you're busy and i'll have a look as soon as i get some more time!

Open to suggestions here!

The above should work but IE9 doesn't properly fire the input event when removing text. Instead it fires selectionchange. So if we have some polyfill for input i think the above should work fine for IE9 as well

I don't think there is a way around that. Preact intentionally relies on the browser's event system. That's one of the key differences between Preact and React.


0-100kmh logging

What would you like to be added:
A table showing the 0-100kmh time if any is present in a drive. Perhaps also 0-60kmh and 0-130kmh. Table should include SOC and max KW. The table could be part of the drive details dashboard
Why is this needed:
Because it is interesting, the streaming API is quick enough for the data. :)
Additional context:

I don't think it would be very valid. Thats like using a 1hz GPS 0-60 app... not really useful when your accuracy is 1 second and your measure 3.2, 3.8, 4.3 etc....

Well it is ok fine resolution - not proper equipment precise, but reasonably good. I get data at 250 ms intervals at worst - and 75 ms at best.

one thing I'd like to see if I can find a trend for - as how much a low SOC affects the 0-100 time. It has a massive effect on the power - but how does that translate to 0-100. (I know it will be lower..)


Zoom events

Description
setScopePlayer(Player, level)
setUnscopePlayer(Player)
Configuration

scoping can only be done via triggers (e.x. Player Sneak and Unsneak)


Fix typos, add missing output and update deprecated shift() call in chapter 3 notebook

Hi @ageron,
Please check out several typos for chapter 3 notebook.
In the Solutions section I added missing output for augmented_accuracy and updated the call of shift() function from the appropriate module both in the exercise description and in the code. According to the deprecation message scipy.ndimage is a correct place to call shift() function, not scipy.ndimage.interpolation. I confirmed that it's present in scipy 1.0.0 documentation.

Thanks again, @vi3itor ! 🥇


Vue frontend

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: chereseeriepa:x: stevenrooseYou have signed the CLA already but the status is still pending? Let us recheck it.


Errors compiling under OSX

Hi I am trying to compile your game sample under OSX but I am getting some errors.
I have enabled C++11 using set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11")
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/memory:1462:36: No matching constructor for initialization of 'std::__1::unique_ptr<game_state, std::__1::default_delete<game_state> >'
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/memory:2424:27: Invalid application of 'sizeof' to an incomplete type 'player'
/Users/sabotage3d/DEV/Urho-Sample-Platformer/Source/main.cpp:121:42: No member named 'emplace_back' in 'std::__1::vector<std::__1::unique_ptr<game_state, std::__1::default_delete<game_state> >, std::__1::allocator<std::__1::unique_ptr<game_state, std::__1::default_delete<game_state> > > >'

Solved with:
```set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11 -stdlib=libc++")``

Hi,
Oh yeah I know that issue from my job. That's because the default STL used on Mac OS X (libstdc++? usually used by GCC) is so outdated that it doesn't properly support C++11. It needs to be switched to libc++ (usually used by clang) with "-stdlib=libc++".
I'll add that tomorrow to a build instruction site and also update the Urho build tutorial in the wiki with the non CMake-GUI variant of activating C++11 and switching the STL for Mac OS X.
Where did you find USP? In the Urho wiki which I was still extending? (it's mostly done now) I thought the wiki had like no visitors because it wasn't that active for a while. I'm still like the only one doing something on it. (I plan on advertising it a bit by writing about USP on the Urho forum, maybe it'll get more active again).

Hey man,
Everything works now. I found your wiki on google where was the USP sample link. It is very cool example if you make a breakdown of the sample I would be awesome. It is a lot more useful than the Ninja example as it is more self contained.

The current Urho wiki is at http://urho3d.wikia.com/wiki/Unofficial_Urho3D_Wiki and got more topics recently about stuff that I found out during the development of USP. The wiki was (accidentally) started by me, see http://urho3d.prophpbb.com/topic778.html for the whole story. Urho had a wiki long time ago but that one was closed because of inactivity.
The features of USP are listed here http://urho3d.wikia.com/wiki/USP_-_Urho_Sample_Platformer with links to wiki articles describing details.
There is also a USP wiki with more game related stuff (like possible tricks, ideas, ...) here: https://github.com/gawag/Urho-Sample-Platformer/wiki
Write me if you find something badly written, missing, improvable or add/improve things yourself, help would be welcome ;-). The Wikia Urho Wiki had multiple contributors as it started but that slowed down over time. I'm like the only regular contributor. I try to write about everything new that I make with Urho and also have two new Urho sample projects planned, which will be integrated into the wiki (and earlier as USP did).
There's also my "Urho Blog", the Wikia Message Wall, where I'm writing about stuff I'm currently doing, new stuff in the wiki, upcoming projects, issues with Urho and so on at: http://urho3d.wikia.com/wiki/Message_Wall:Gawag
Oh do you know of some better GUI system which can be used with Urho? That's one of the next things I want to look into as Urho's own UI system is so minimal. I know CeGUI and MyGUI but nothing which has already been combined with Urho.

I read all of these man. Pretty interesting stuff. I would advertise it better it would draw more people to urho3d. In this topic: http://urho3d.prophpbb.com/topic838-20.html  I suggested : https://github.com/ocornut/imgui . Another interesting thing is I suggested bgfx as it supports Metal now: http://urho3d.prophpbb.com/topic1067.html and it has natural support for imgui .

Added build instructions to the readme https://github.com/gawag/Urho-Sample-Platformer/blob/master/Readme.md and added a note for Mac OS X to http://urho3d.wikia.com/wiki/Creating_a_new_Urho3D_Project . This "issues" should be "fixed" now.
Also the last USP feature I wanted to do is done (recording of best times) and commited.
Haven't looked into imgui into such details yet but the thread mentioned it also having issues. Seems like the "better GUI for Urho" is a bigger issue. I hope there is a general good solution which can be advertised and explained in the wiki.


Ansible 2.7 Newly supported module

A record
AAAA record
CNAME record
MX record
NAPTR record
PTR record
SRV record
TXT record

@sganesh-infoblox This PR contains all the example for newly supported modules with Ansible 2.7. Please review and if it looks ok to you we can go ahead and merge the same for the users to refer these examples.

@s-giri Can you please review and merge the newly added module playbook example.

@justjais, changes are ok. Just one point. We're not mentioning the "view" in which we're creating the records. Do you think this should be added?

@s-giri, I didn't got the exact doubt as for all the modules plays view is not mandatory parameter.

@s-giri can you please merge the respective PR.


DEMO: uses height, DOCS: uses thickness

Desc
In the demo, your options use height for the height option, but in the documentation, it uses thickness, which is the correct property to affect the height of the progress bar.
Dev options
Choose thickness as the property name and make the change on the documentation instead of breaking tons of applications.
Notes
Related to #67

I noticed it too!


Move Result type out of the prelude

The Result type exposed by quicli::prelude conflicts with the Result type that's in the default Rust namespace, since it has a different type signature. This makes it inconvenient to drop quicli into existing projects. It'd be great to move this out of the prelude and make it an optional import instead.
For example, here's a PR where I'm switching from bare clap to quicli. I ended up tossing a use std::result::Result right after the quicli prelude import, which is the kind of thing which makes me think this should work the other way around.

Yeah, I regret adding it to the prelude in retrospect. In addition to your case with existing code, error handling is one of the less obvious things to many people coming to Rust from other languages, so this is also needlessly confusing them further.
I imagine fix here that is two-fold. First:

[ ] Change the name of the type alias to QuickResult (or something like that, feel free to bikeshed)
[ ] Document this type alias thoroughly

And then:

[ ] Write a guide that covers error handling in more detail (and that also links to failure's docs)

Change the name of the type alias to QuickResult (or something like that, feel free to bikeshed)

I'd also really like to see it moved out of the prelude and made into an optional import. Compared to the other items in the prelude, it's much more tenuously connected to this crate's main features.


Progress bar doesn't respect borders of tmux pane

Progress bar goes out of tmux pane border
Describe you environment

Mac OS high sierra
Python version: 3.6.2
Pipenv version: 8.2.7

Expected result
Progress bar works as in the real terminal
Actual result

Steps to replicate
Run tmux, split vertically, go to the right pane, run pipenv install

Out of curiosity; what is the function of Apple's logo in prompt?

@piotr-dobrogost I believe it's information about file format (like unix), don't care much about that so can't say for sure, I think if you install vim-airline and vim-devicons then this works automatically.

I’m guessing this relates to how we are retrieving terminal size info. It seems reasonably likely this would be a bug, although I never vsplit my tmux session.

On Oct 27, 2017, at 9:26 AM, Konstantin Alekseev<EMAIL_ADDRESS>wrote:
@piotr-dobrogost I believe it's information about file format (like unix), don't care much about that so can't say for sure, I think if you install vim-airline and vim-devicons then this works automatically.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@kalekseev Out of curiousity, what happens if you resize the tmux split pane after you create it.  We have code in there to adjust layouts when the terminal is resized and I'm wondering if the split isn't considered a resize.

  Based on your progress bar this looks like an old version of pipenv.  @kalekseev can you try upgrading pipenv and test again?

I can confirm that the issue seems to be non existent to me.  Closing issue due to probable old version!  Let us know if that's not the case @kalekseev

@erinxocon  upgraded to pipenv 8.3.1, removed custom tmux.conf the problem still exists in iterm 3.1.4, though it works as expected in the Terminal.app

@kalekseev  huh, I was using iterm as well.  Different config?  That's weird.

Thanks for the info. This isn’t super high priority and supporting this kind of progress bar on multiplexers may not even be realistic but it’s not really my area of expertise. Would be interested in feedback

Yeah, not a very serious bug.  Although there could be a hidden cost if it affects people's perception of the tech and, therefore, the adoption rate.  For example, I've never experienced similar terminal-breaking behavior with the package managers from other languages/platforms.    I had a conversation just the other day with a department manager who seemed to believe, for some reason, that Python's package management solutions were not up to par compared with other languages.  I didn't agree but, somehow, this person had come to hold this opinion.

@davesque Out of curiosity, do you know what the manager considers good package management solutions? Python’s packaging has been drastically improved recently to become acceptable, but I understand people still maintaining it being bad if they don’t stay on the cutting edge. The situation is still being discussed a lot and improved upon, and any advices would be welcomed. It’d be interesting to hear what people thinks pip-related tooling can learn from other package managers.

@uranusjr
I think it was a node.js/Ruby developer I was speaking to although I don't think I could say with any certainty what motivated that person to hold that position.  My loose impression that it was something like what you say---that this person formed their opinion a while back when there really was more friction in Python's package management process but is now holding on to it just because it was a first impression.
Again, I don't share their views on the matter since I have been using Python and all of its tooling for a while now and I've become aware of the professionalism that goes into the design of all the resources used by the community.
Anyway, my point was just that little polish issues like this can have a surprising amount of importance when you consider them from a certain point of view.

It’d be helpful if we can narrow this down: is this Mac only? Iterm only? Locale setting specific? What configurations are in play for fonts, terminal, tmux etc? Are all of the things up to date?

I played around a bit and this seems to have something to do with how iTerm2 reports Unicode character widths. Setting “Use Unicode Version 9 Widths” in Preferences → Profiles → (The profile you use) → Text fixes it for me.
iTerm2’s documentation seems to suggest you should set it unless you have faulty legacy application that malfunctions. New versions of Tmux built with recommended configurations use the new width table.
So to summarise:

Check the aforementioned checkbox.
Consider filing an issue to iTerm2 to make this the default.
If for whatever reason you can’t use the up-to-date width table, set environment variable PIPENV_HIDE_EMOJIS to workaround the issue.

Is there any way we can tell if the checkbox is checked?

You can tell you’re in iTerm2 with TERM_PROGRAM, Tmux with TMUX (or TERM if you want to consider GNU Screen as well, which could also be affected, though I didn’t try), and iTerm preferences with defaults. So yes, you can. I don’t think it would be appropriate in practice though.
Also you can’t actually tell what mode the terminal is in, only guess. The output is identical from the program’s perspective; it’s iTerm rendering things differently.

@uranusjr Thanks for the insight into this.  Created an issue in iTerm's gitlab repo here: https://gitlab.com/gnachman/iterm2/issues/6601

iTerm2 defaults you to unicode 9 if you're on macOS 10.13, but if you've ever fiddled with the setting before it'll stay at what you set it to.

@gnachman I'll assume that's why this happened.  I've been a user of iTerm for a while now so I probably had an old config sitting around.


transmission: 2.94 -> 3.00

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This commit made Transmission fail to detect all of my old torrents. I will try and roll it back with some override jankery.

Hmm, the new version does migrate the *.torrent files to a new naming scheme, but that worked for me without a problem.  Perhaps it would be best to discuss your case with upstream.

This deleted all of my torrents!!

Could you two be running into this issue? https://github.com/transmission/transmission/issues/1325  In any case those problems will probably be best take upstream.  I hope they will be rare enough.

Could you two be running into this issue? transmission/transmission#1325
In any case those problems will probably be best taken upstream (like that link above). I hope they will be rare enough.

No. The torrent files were just deleted; the directory was completely empty


Profiler

Closes #1173.
This is done on top of #3267, so merging to that branch.
profile flag is implemented as the field in Environment and as a setting in configuration.

This is really neat, though kind of confusing. Can you at add an explanation of it in the docs?
https://www.squiggle-language.com/docs/Guides/Debugging
I imagine later, if this gets used, it would be pretty useful to provide more information here - like info on the actual time these parts take, or a flame graph. Right now I'm not sure what to make of this, as a user.

This is really neat, though kind of confusing. Can you at add an explanation of it in the docs?
https://www.squiggle-language.com/docs/Guides/Debugging

Will do.

I imagine later, if this gets used, it would be pretty useful to provide more information here - like info on the actual time these parts take, or a flame graph.

Yep. The potential UI I have in mind is:

show a new panel at the bottom when profiling mode is on
change the behavior of hovers when it's active - show the percentage and absolute times, and highlight AST nodes if possible (this is somewhat hard, both UI-wise and because the current profiling behavior is per-character, but doable)
allow to switch between "number of calls" and "time spent" submodes
also, show per-line times in the gutter (I tried to do this but couldn't quickly figure out how to highlight the gutter lines separately, lineNumbers() is not very customizable)


Add RBIs for missing definitions in stdlib

We have a few more definitions for stdlib that do not have signatures but I think it still can be useful as:

The constants and methods are defined which allow more code to be typed: true
The documentation can popup in the editor

Here's the list of modules included in this PR:

dbm
fiddle
gdbm
getoptlong
nfk
obersable
readline
openuri
prime
pstore
rinda
shellwords
thwait
weakref

I'm seeing the same errors you see on buildkite on Stripe's codebase. Do you mind taking a look? It looks like the current PR causes Sorbet's own payload RBIs to not type check.

This one needed to be rebased on master to get BRb.

Updated exp files with tools/scripts/update_exp_files.rb

https://go/builds/bui_HJZRPaaMb9Bt0d

These changes were included via #3043


Firewalld support

Added code so that the role configures firewalld (if present), otherwise
it configures the default iptables rules for forwarding.

The general layout looks fine, but I'm wondering if all scenarios have been tested? I would assume firewall-cmd would give you a clear error when you pass a flag it doesn't recognize ("--peramanent").

Good catch. firewalld-cmd doesn't give an error with that flag, and it seems to set the forwarding with the command, just not permanently. I'll fix the typo.

Updated code to fix typo.

Updated logic in main.yml, so that both versions can't run at the same time


Testing Pipeline Bitkit

@pwltr?

What? :)

Sorry, this is for the new DevOps. A task to look into the Bitkit Testing to see if there is anything he can improve. Probably should have tagged James not you. @catch-21

At this stage, we're not in a bad place wrt Bitkit test pipelines.
Things will get more complicated over time, such as there could be a requirement for external trigger events for the system-level tests.
Prioritise Pubky and Blocktank over Bitkit for now and leave it with me to identify anything we need in the near future.

Do you want me to close this issue?

Closing due to no immediate tasks required.


Fix possible OnceCell panic in Proxy::connection()

When multiple tasks are trying to create proxies simultaneously, another task may initialize the zbus-Connection-OnceCell while the connection is initialized.
This ensures that only the first task to establish a connection initializes the OnceCell
Fixes #185

I am not particularly happy with this solution, ideally we turn the entire fn into a get_or_init, but you need to get the session in an async way which is incompatible with Lazy and OnceCell... I wonder if using std::sync::Once helps here.

I understand what you mean but I don't think there is a trivial solution to this problem that would ensure the connection is initialized only once.
To do it more cleanly, one would need to atomically check if the cell is already being initialized and then wait for the initializing task to finish somehow. And then there is the potential problem of that task being cancelled as well.
Basically an async get_or_init I guess.
There is https://github.com/danieldg/async-once-cell which does all of that but it seems a bit complex and I'm not sure if it is worth pulling in this dependency just for this.

Rustfmt is complaining


Test and upgrade three.js r99

[x] test r99 in TensorSpace
[ ] upgrade examples lib
[ ] upgrade website lib

It has been test that TensorSpace can work well with three.js r99.


I can't register a custom ValueUnboxer

I can't or I don't know how to define a custom ValueUnboxer (to handle vavr Option).
There is a way to do this with graphql-java in the GraphQL.Builder but this not seems to be exposed in spring.
May be spring graphql could handle bean of type ValueUnboxer and add them in the builder ?
If someone has a work around, I take it !

There is a method on GraphQlSource.Builder called configureGraphQL that gives you direct access to GraphQL.Builder. You should be able to use that.

Yes, I noticed that. At the moment I have copy paste the declaration of the grapqlSource from spring graphql project and just add my unboxer.
Is there a way to just update partially the builder without the whole definition ?

works fine ! thanks !


pull request for e2e test at 01/15/2017 20:15:08

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


.env file location - not specific enough - after clone of repo - no .env found - where is it?

Sorry - I little of a flow/kitty items newbie here - but in following the instructions - got stuck in VSCode - not knowing where the .env file was.  Do I need to create this file?  Please fix the doc so that the user knows specifically what to do here on this step.
I believe we are to take .env.example and create a .env from this example placing our values for flow_address and flow_private_key into the file and save .env back to the api folder where .env.example is located - is that correct?  If so - pls update the doc, if different- pls update the doc, instructions, etc.

doing a search on this repo - there is no .env file - so it is not supplied - so it must be generated by some step.
at a minimum - pls fix the doc and be specific about where this file "goes"
Save your keys
After your account has been created, save the address and private key in the .env file:
Replace these values with your own!
FLOW_ADDRESS=0xabcdef12345689
FLOW_PRIVATE_KEY=aaaaaa...aaaaaa

Solved in #82