Skip AWS cred. validation in self-update pipelines

What
We are using IAM profile on concourse for AWS credentials. We thus want to
skip STS token and user credential validation that we normally want to run
when running make locally.
How to review
Deploy this branch to your concourse. Run self update pipelines task (in the 1st pipeline-lock job). It should pass.
Who can review
not @mtekel

updated

@mtekel should this PR re-apply the change that was reverted in #797?

well, I need to check what everything was added/changed in makefile since I made the original PR as well...

updated

This doesn't successfully deploy without manual intervention. On the first run of self-update-pipelines, the pipeline hasn't been updated to include the SKIP_AWS_CREDENTIAL_VALIDATION parameter, so it attempts to check the AWS creds and fails.

We could do 2 PRs then. Alternatively, temporarily check if PIPELINES_TO_UPDATE is set, indicating that this is run inside pipeline. But cleanup would require 2nd PR...

I can't think of a way of doing this without needing 2 PRs. I'm not sure I feel strongly about which way to go.

¯\_(ツ)_/¯
Let's go with the first option of one PR to set SKIP_AWS_CREDENTIAL_VALIDATION and 2nd to implement the check because I think it's slightly more explicit.

I have created https://github.com/alphagov/paas-cf/pull/803

I've merged #803. This can now be rebased on master to pick up that change.

rebased

This now works for the create pipeline, but we need the same flag added for all the other pipelines.

Good point: https://github.com/alphagov/paas-cf/pull/804

ok, so to apply this, we need to run those pipelines :| not sure we want to....

diff --git a/scripts/validate_aws_credentials.sh b/scripts/validate_aws_credentials.sh
index 941e1d59..d55f2759 100755
--- a/scripts/validate_aws_credentials.sh
+++ b/scripts/validate_aws_credentials.sh
@@ -1,6 +1,11 @@
 #!/bin/bash
 SCRIPT_DIR=$(cd "$(dirname "$0")" && pwd)

+if [ ! -z "${PIPELINES_TO_UPDATE+x}" ] ; then
+  echo "PIPELINES_TO_UPDATE set to ${PIPELINES_TO_UPDATE}. Assuming run in pipeline, skipping STS credentials check."
+  exit 0
+fi
+
 if [ "${SKIP_AWS_CREDENTIAL_VALIDATION:-}" == "true" ]  ; then
   exit 0
 fi

@mtekel I don't think we need to worry about those pipelines. They're not deployed anywhere other than dev.

I think this is good to merge. I'm going to leave it until Monday to merge so that #803 and #804 have applied everywhere.


"dot" ALPN token MUST be negotiated for XoT (according to RFC9103, Section 7.1)

The XoT specification requires dot ALPN token to be negotiated for zone transfers:

7.1. Connection Establishment
During connection establishment, the Application-Layer Protocol Negotiation (ALPN) token "dot" [DoT-ALPN] MUST be selected in the TLS handshake.

At the very least, version 4.3.8 of NSD does not appear to do that, which on practice leads to interoperability problems with the current development release of BIND (9.17.19) and dig, which require that for zone transfers according to the spec (details).

We currently have Bind as a primary to some NSDs as secondaries, and wish to deploy XoT, but this issue is holding us back

Thanks for the report @arbv. Sorry this didn't get picked up sooner, but luckily @cesarkuroiwa helped out :sweat_smile: I'll merge his PR ASAP after which I'll close this issue. Thanks to both of you :+1:

I am glad to hear that the problem is solved! :+1:

There is a catch, though. Judging from the MR, the case when NSD acts as a primary and BIND as a secondary is still not supported.

Let's re-one this one then. I'll have a look at the server side, see how easy/hard it'd be to get that in.


[url_launcher] launch(tel:<phone_number>) does not work on iOS 14

Not able to launch phone number with formate((509) 551-3103) in dial pad in iOS.
Code:
void launchCaller(String phone) async {
  String url = 'tel:$phone';
  if (await canLaunch(url)) {
    await launch(url);
  } else {
    throw '${'Could not launch'} $url';
  }
}

Added below keys in Info.plist:
<key>LSApplicationQueriesSchemes</key>
      <array>
            <string>googlechromes</string>
            <string>comgooglemaps</string>
            <string>tel</string>
       </array>
<key>LSRequiresIPhoneOS</key>
        <true/>

Your tel URI contains a space, which makes it invalid per the spec. iOS does not generally tolerate invalid URIs.


feat!: converted EvaluationContext to an interface with MutableEvaluationContext implementation

Signed-off-by: Skye Gill<EMAIL_ADDRESS>

Codecov Report

Merging #92 (ca29060) into main (9fbed88) will increase coverage by 0.49%.
The diff coverage is 83.14%.

@@            Coverage Diff             @@
##             main      #92      +/-   ##
==========================================
+ Coverage   69.24%   69.74%   +0.49%
==========================================
  Files           7        8       +1
  Lines         569      618      +49
==========================================
+ Hits          394      431      +37
- Misses        158      170      +12
  Partials       17       17

Impacted Files
Coverage Δ

pkg/openfeature/evaluation_context.go
80.35% <80.35%> (ø)

pkg/openfeature/client.go
68.59% <87.09%> (-0.79%)
:arrow_down:

pkg/openfeature/hooks.go
40.90% <100.00%> (ø)

pkg/openfeature/openfeature.go
90.69% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Superseded by https://github.com/open-feature/go-sdk/pull/91


Why I has fobiddened tls 1.3 with SSL_OP_NO_TLSv1_3, openssl(1.1.1c) still take tls1.3 cipher suit when client hello?

SSL_CTX_set_options  wtith SSL_OP_NO_TLSv1_3, I has fobiddened tls 1.3 with SSL_OP_NO_TLSv1_3, openssl(1.1.1c) still take tls1.3 cipher suit when client hello in android 10?
0x13,0x02 - TLS_AES_256_GCM_SHA384
0x13,0x03 - TLS_CHACHA20_POLY1305_SHA256
0x13,0x01 - TLS_AES_128_GCM_SHA256

Version negotiation is orthogonal to cipher selection as currently implemented, and it's not clear there's a good reason to make the code more complicated.
You can use SSL_{CTX_,}set_ciphersuites to cause them to not be sent.


Bug 2281580: core: fix missing env in svg cleanup job

SVG cleanup job uses the cephSubvolumeGroup env name from spec.Name. But sometimes it can be empty. In that case rook should use the CR name.
Signed-off-by: sp98<EMAIL_ADDRESS>(cherry picked from commit 33ce8f0c8e31ba7f5acf24c7854465ff32eca437)

Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
[ ] Reviewed the developer guide on Submitting a Pull Request
[ ] Pending release notes updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.

/bugzilla refresh


Allow trusted hosts to be added to cluster.

When deploying a RoR application which used Bundler, and which attempted to fetch some dependances via git, the following error resulted:
Fetching git@github.com:rails-sqlserver/tiny_tds.git
Host key verification failed.
fatal: Could not read from remote repository.

The issue involved ssh not trusting the github.com, as the host key had not been added. The immediate, stop-gap resolution was to tell Bundler to fetch the repo by HTTPS.
Discussion on IRC with @lmars resulted in the suggestion that, similar to flynn add key, a command is added to allow the addition of trusted hosts to the cluster, eg: flynn trust host-key github.com. Such a command could then fetch the key from github.com, allow the user to confirm it, and then store it.
Credit to @patcoll for the CLI command name.

This appears to be a relatively broad thing: have a generic trust store for public keys/certificates, and apply that to all components of the system. It's not just SSH host keys but CA certificates, TUF keys, etc.

This might be of interest @titanous, https://square.github.io/keywhiz/

I solved this using a buildpack that lets you give your slug it's own SSH keys.


GitHub Action: max-parallel 1 to avoid db conflicts?

This cannot be it.  These are separate Docker images.

NOTE: repowgknn2pe does not support Python 3.6.
Py37 failed even with just one job at a time.


Unknown error from using module.predict()

I am working on using a simple lenet-style conv net to predict some values, similar to the kaggle-ndsb2 example. However, after I fit the model and tried to using predict(), a "key error 0" pops out and I am not sure what it means, as no information is provided. As I have successfully fitted the model, I attempted to run predict with the train data iterator and the same error appears, so I am pretty sure it is not due to the construction of the data iterator.
Below is the error information.
`---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
 in ()
----> 1 con_model.predict(eval_data = data_val)
/Users/Sen/anaconda/lib/python3.5/site-packages/mxnet-0.9.1-py3.5-macosx-10.6-x86_64.egg/mxnet/module/base_module.py in predict(self, eval_data, num_batch, merge_batches, reset, always_output_list)
289             if num_batch is not None and nbatch == num_batch:
290                 break
--> 291             self.forward(eval_batch, is_train=False)
292             pad = eval_batch.pad
293             outputs = [out[0:out.shape[0]-pad].copy() for out in self.get_outputs()]
/Users/Sen/anaconda/lib/python3.5/site-packages/mxnet-0.9.1-py3.5-macosx-10.6-x86_64.egg/mxnet/module/module.py in forward(self, data_batch, is_train)
450         """
451         assert self.binded and self.params_initialized
--> 452         self._exec_group.forward(data_batch, is_train)
453
454     def backward(self, out_grads=None):
/Users/Sen/anaconda/lib/python3.5/site-packages/mxnet-0.9.1-py3.5-macosx-10.6-x86_64.egg/mxnet/module/executor_group.py in forward(self, data_batch, is_train)
311
312         """
--> 313         _load_data(data_batch, self.data_arrays, self.data_layouts)
314         if is_train is None:
315             is_train = self.for_training
/Users/Sen/anaconda/lib/python3.5/site-packages/mxnet-0.9.1-py3.5-macosx-10.6-x86_64.egg/mxnet/module/executor_group.py in _load_data(batch, targets, major_axis)
41 def _load_data(batch, targets, major_axis):
42     """Load data into sliced arrays"""
---> 43     _load_general(batch.data, targets, major_axis)
44
45
/Users/Sen/anaconda/lib/python3.5/site-packages/mxnet-0.9.1-py3.5-macosx-10.6-x86_64.egg/mxnet/module/executor_group.py in _load_general(data, targets, major_axis)
28                     end[axis] = slice_idx.stop
29                     # pylint: disable=no-member,protected-access
---> 30                     if d_src.context == d_dst.context:
31                         nd.crop(d_src, begin=tuple(begin), end=tuple(end), out=d_dst)
32                     else:
/Users/Sen/anaconda/lib/python3.5/site-packages/mxnet-0.9.1-py3.5-macosx-10.6-x86_64.egg/mxnet/ndarray.py in context(self)
462         check_call(_LIB.MXNDArrayGetContext(
463             self.handle, ctypes.byref(dev_typeid), ctypes.byref(dev_id)))
--> 464         return Context(Context.devtype2str[dev_typeid.value], dev_id.value)
465
466     @property
KeyError: 0`
Environment info
Operating System:
MacOS, version 10.12.2

Please post a reproducible example

I encountered this problem too and this seems to happen only when I execute predict in IPython shell.
https://github.com/chaonan99/mxnet-play/blob/master/deeplearningbook/xor/config/xor.py
After training, copy and run L124 in IPython will cause the error above.

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!


Templates cannot be selected yet

https://github.com/bitsensor/elastalert-kibana-plugin/issues/56
https://github.com/bitsensor/elastalert-kibana-plugin/issues/71
https://github.com/bitsensor/elastalert-kibana-plugin/issues/142

Official repository is not maintained anymore.
Aim of this fork is to support new versions of Kibana (after migration to Kibana New Platform starts from 7.10).

For nearest future I do not have plan to implement new features.
Contribution is welcome 😉


[backport-19.09] yubioath-desktop: 4.3.6 -> 5.0.2

Motivation for this change
Backporting #81162
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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] 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.

cc @Mic92

What was the reason for this backport?

What was the reason for this backport?

Being able to use the new version while being on the 19.09 channel.

We usually only backport bugfixes and security fixes. There are ways of using unstable channels in a stable channel as well or you could add it to an overlay.

According to the release notes [1], there have been no security fixes, but there have been some bugfixes
[1] https://developers.yubico.com/yubioath-desktop/Release_Notes.html

Should I close this then?


Add example gst-v4l2-alsa

gst cli with v4l2 video and alsa audio example

Merged with ecb027acd4d58a92b24547782d9c126c4a1f4df6, thank you very much @xsephiroth
I wasn't able to confirm the example is working (don't have access to Linux laptop today) but excited to try this! I made some minor changes to make the linter happy :)


Protect against hung subprocesses with inactivity timeouts

Noticed today that trying to bzr branch with the bzr:// protocol ended up causing the child process to just...sit, generating no output.
We need some basic protection against this (there's no general solution, because halting problem). Sadly, we can't just use a simple timeout, as there are times when we absolutely expect these processes to take a while (e.g., cloning kubernetes). However, if we can watch stdout/stderr for output and update a timer every time we see activity, then we should be able to set an "inactivity" timeout, where we kill the command only if a certain window has elapsed since progress was reported. That'll work for most git, hg, and bzr operations at least, I think.

I can take this one, as said in #159!

Awesome. Please don't hesitate AT ALL to ask questions. Here, or in slack - whatever. Meantime, here's some starting thoughts:

I think you're likely to run into a blocker right from the start the start, as Masterminds/vcs does not offer an interface for direct control over executing processes. I can't imagine a way of doing this without direct access to the running exec.Command object and using Start(), as everything else will just block until the command completes. So, you may need to start with a patch to Masterminds/vcs that creates a companion to RunFromDir that returns the assembled exec.Command object instead of calling CombinedOutput(). (/cc @mattfarina)
We do know we plan to be passing down cancellation channels eventually (per #159) into the command loop, so design with that in mind.
Be warned, I plan to convert gps from glide to dep tonight. (This is risky, because https://github.com/golang/dep/milestone/1)
The *SourceMgr side of the code (as opposed to the solver) has been devolving towards spaghetti, and the path by which these objects get created/managed is kinda long and winding. I like grokking bigger-picture context before I work, so in case you do, here's how I recommend you go about grokking the flow:

All the logic you'll be changing is inside source types, which are called from pretty much all the public interface methods, returned from SourceMgr.getSourceFor()
You can mostly skip the deducer stuff there - just see how a maybeSource gets set up, and how it interweaves with baseVCSSource
There's tons of logic that tries to "lazily" determine when it needs to do work. Much of the refactor I need to do is bringing some sanity and order to that, so try to ignore it. Just focus on the calls that are made against the baseVCSSource.crepo.r - that's the actual Masterminds/vcs object.

Tests, please! 😄 This part of gps isn't nearly as well-tested as the solver, but it's time to impose discipline.

I'd also be happy to find time for a an hour pairing session on this, if you think it'd be helpful.

Nice, let me grok a bit with the code and I'll ping you when I have some questions!

Both of these ideas sound 👍!
I don't have any name suggestions for MonitoredCmd - it seems fine. Though, unless there's some reason it needs to be exposed via the public interface, it can just be monitoredCmd for now. That'll give us more leeway in renaming it in the future.
Of course, if we're inferring from stdout/stderr outputs, it may require a bit of research to pick sane numbers for these inactivity timeouts.

Thanks! Will start working on the implementation then

Just checking in on this :)

I'm working on implementing the monitored cmds on all operations right now. The issue with this is that all operations that are not RunFromDir can't be trivially changed to use monitoredCmd.
For example, when vcs.Repo.Update is used, internally that cmd is not monitored. The solution to that is reimplement the Update (or any other method being used) for all possible VCSs using monitored cmds instead.
What are your thoughts about this?

Unfortunately, I think you're right - there's no magical way around that design of the interface. And now that you say it, I'm picturing just how much work that is ☹ Thanks for sticking with it!
The only real thought I'd have about it is that I'd love to see the WIP as you go in a PR, as the e.g. vcs_source.go file is already poorly organized, but still bloated. I don't know exactly what that SHOULD look like, but I'd rather avoid having you get to the end of the work and finding myself wanting to ask for a bunch of reorganization.

I think this can be marked as done now. There are some improvements needed for handling on windows, but that's not the original scope here.
Would you agree, @erizocosmico ?

:+1:
On Sun, 16 Apr 2017 at 17:42, sam boyer <notifications<EMAIL_ADDRESS>wrote:
I think this can be marked as done now. There are some improvements needed for handling on windows, but that's not the original scope here.
Would you agree, @erizocosmicohttps://github.com/erizocosmico ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/sdboyer/gps/issues/84#issuecomment-294358165, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABQFF-aFI9FEkigxu8nnctVBcwv3WB8xks5rwjaQgaJpZM4JnEYL.


Crash on get_physical_device_surface_capabilities() on wayland surface.

Hi,
I currently try to get my ash based application to create a surface on wayland via winit.
The creation process succeeds, but every time I try to access the surface capabilities via
surface_loader.get_physical_device_surface_capabilities(pdevice, surface) the application crashes with Result(-3) which is "Initialization of a object has failed".
So I tried to find the problem by enhancing the example's lib.rs like this:
SurfaceLoading:
#[cfg(all(unix, not(target_os = "android"), not(target_os = "macos")))]
unsafe fn create_surface<E: EntryV1_0, I: InstanceV1_0>(
    entry: &E,
    instance: &I,
    window: &winit::Window,
    events_loop: &EventsLoop
) -> Result<vk::SurfaceKHR, vk::Result> {
    use winit::os::unix::WindowExt;
    use winit::os::unix::EventsLoopExt;

    //Check if we are on wayland, if not, use x11
    if events_loop.is_wayland(){
        use ash::extensions::khr::WaylandSurface;

        let way_display = window.get_wayland_display().expect("failed to get wayland display!");
        let way_surface = window.get_wayland_surface().expect("fauked to get wayland surface");

        let way_create_info = ash::vk::WaylandSurfaceCreateInfoKHR::builder()
            .display(way_display)
            .surface(way_surface);
        //Create the surface loader
        let way_surface_loader = WaylandSurface::new(
            entry,
            instance
        );
        way_surface_loader.create_wayland_surface(&way_create_info, None)
    }else{
        let x11_display = window.get_xlib_display().unwrap();
        let x11_window = window.get_xlib_window().unwrap();
        let x11_create_info = vk::XlibSurfaceCreateInfoKHR::builder()
            .window(x11_window)
            .dpy(x11_display as *mut vk::Display);

        let xlib_surface_loader = XlibSurface::new(entry, instance);
        xlib_surface_loader.create_xlib_surface(&x11_create_info, None)
    }
}

I also added the WaylandSurface extension like that:
#[cfg(all(unix, not(target_os = "android"), not(target_os = "macos")))]
fn extension_names() -> Vec<*const i8> {
    vec![
        Surface::name().as_ptr(),
        XlibSurface::name().as_ptr(),
        WaylandSurface::name().as_ptr(),
        DebugReport::name().as_ptr(),
    ]
}

However, the lib.rs also crashes when trying to get the capabilities with the same error.
My question now: am I missing something in the creation process?
I tested this on gnome-wayland and sway, both with intel-anv and radeon-mesa drivers.

I am not sure what is going on. -3 is also not a legal error code. Have to tried to run https://github.com/SaschaWillems/Vulkan? Afaik they also have wayland support.
I can't see an obvious mistake in your code.

I compiled SaschaWillems's examples two time, once with USE_WAYLAND_WSI enabled and once with it disabled.
When started on gnome+wayland the the examples work when USE_WAYLAND_WSI is disabled, but crash with the following error when enabled:
Fatal : VkResult is "ERROR_INITIALIZATION_FAILED" in /home/user/Code/CPP/git/Vulkan/base/VulkanSwapChain.hpp at line 287
bloom: /home/user/Code/CPP/git/Vulkan/base/VulkanSwapChain.hpp:287: void VulkanSwapChain::create(uint32_t*, uint32_t*, bool): Assertion `res == VK_SUCCESS' failed.
[1]    4827 abort (core dumped)  ./bloom

I guess I'm using Wayland_WSI when creating a wayland surface so it could be the same bug.

I wrote an Issue at the example repo. Let's see if this is somehow related. Maybe I'm missing just some package or something.
https://github.com/SaschaWillems/Vulkan/issues/567

So I found the problem. It seems to be an AMD-Pro driver issue on linux. It works with the open-source RADV driver.
The problem on SashaWillem's examples were actually caused by some wrong configuration of the CMAKE scripts.


Supporting Hetzner CAPI clusters

Working with the Hetzner CAPI Provider community to find a consensus: https://github.com/syself/cluster-api-provider-hetzner/issues/845


Fix sync script for preprod to prod

Issues:

Wasn't diffing against the current date, was diffing against the prod
bucket update time.
Referenced an undeclared var tsMeta
Passing a string with quotes into date caused a parsing error, adding
-r to jq to have a raw string fixes this

Signed-off-by: Hayden Blauzvern<EMAIL_ADDRESS>
Summary

Release Note

Documentation

@dlorenc @asraa


removes unused pressure arg from Irradiance.liujordan function

[x] Closes issue #386
[ ] Fully tested. Added and/or modified tests to ensure correct behavior for all reasonable inputs. Tests must pass on the TravisCI and Appveyor testing services.
[ ] Code quality and style is sufficient. Passes git diff upstream/master -u -- "*.py" | flake8 --diff and/or landscape.io linting service.
[x] New code is fully documented. Includes sphinx/numpydoc compliant docstrings and comments in the code where necessary.
[ ] Updates entries to docs/sphinx/source/api.rst for API changes.
[x] Adds description and name entries in the appropriate docs/sphinx/source/whatsnew file for all changes.

I don't like that tests fail on python 3.
When I run on my local windows machine I've got: 457 total, 1 failed, 5 ignored, 451 passed

INSTALLED VERSIONS
commit: None
python: 3.6.3.final.0
python-bits: 64
OS: Windows
OS-release: 10
machine: AMD64
processor: Intel64 Family 6 Model 94 Stepping 3, GenuineIntel
byteorder: little
LC_ALL: None
LANG: None
LOCALE: None.None
pandas: 0.20.3
pytest: 3.2.1
pip: None
setuptools: 36.5.0.post20170921
Cython: 0.26.1
numpy: 1.13.3
scipy: 0.19.1
xarray: None
IPython: 6.1.0
sphinx: 1.6.3
patsy: 0.4.1
dateutil: 2.6.1
pytz: 2017.2
blosc: None
bottleneck: 1.2.1
tables: 3.4.2
numexpr: 2.6.2
feather: None
matplotlib: 2.1.0
openpyxl: 2.4.8
xlrd: 1.1.0
xlwt: 1.3.0
xlsxwriter: 1.0.2
lxml: 4.1.0
bs4: 4.6.0
html5lib: 0.9999999
sqlalchemy: 1.1.13
pymysql: None
psycopg2: None
jinja2: 2.9.6
s3fs: None
pandas_gbq: None
pandas_datareader: None

Looks like we've resolved all the testing issues, so I'm going to go and merge this. Thanks for the fix @KonstantinTr


uv pip install torch fails on Windows

This fails on my windows machine:
$ uv venv --python 3.11
Using CPython 3.11.0 interpreter at: C:\Program Files\Python311\python.exe
Creating virtual environment at: .venv
Activate with: .venv\Scripts\activate

$ uv pip install torch --index-url https://download.pytorch.org/whl/cu124 -v
DEBUG uv 0.4.24 (b9cd54913 2024-10-17)
DEBUG Searching for default Python interpreter in system path or `py` launcher
DEBUG Found `cpython-3.11.0-windows-x86_64-none` at `C:\Users\jeanp\code\tmp\.venv\Scripts\python.exe` (virtual environment)
DEBUG Using Python 3.11.0 environment at .venv
DEBUG Acquired lock for `.venv`
DEBUG At least one requirement is not satisfied: torch
DEBUG Using request timeout of 30s
DEBUG Solving with installed Python version: 3.11.0
DEBUG Solving with target Python version: >=3.11.0
DEBUG Adding direct dependency: torch*
DEBUG No cache entry for: https://download.pytorch.org/whl/cu124/torch/
DEBUG Searching for a compatible version of torch (*)
DEBUG Selecting: torch==2.5.0+cu124 [compatible] (torch-2.5.0+cu124-cp311-cp311-win_amd64.whl)
DEBUG No cache entry for: https://download.pytorch.org/whl/cu124/torch-2.5.0%2Bcu124-cp311-cp311-win_amd64.whl#sha256=270e004f028b2fc6886388ca01b5f22389f3a7babbd2004a1eec82aa7f669c12
DEBUG Released lock at `C:\Users\jeanp\code\tmp\.venv\.lock`
error: Failed to download `torch==2.5.0+cu124`
  Caused by: Failed to unzip wheel: torch-2.5.0+cu124-cp311-cp311-win_amd64.whl
  Caused by: an upstream reader returned an error: an error occurred during transport: error decoding response body
  Caused by: an error occurred during transport: error decoding response body
  Caused by: error decoding response body
  Caused by: request or response body error
  Caused by: error reading a body from connection
  Caused by: stream error detected: unspecific protocol error detected

$ uv --version
uv 0.4.24 (b9cd54913 2024-10-17)

That looks like a transient error. Are you seeing it repeatedly?

I tried again and it works !
I was on my phone wifi when I had the problem. I could install torch from with uv add but not from uv pip as I remember, that was strange


[bal-button]: text in mobile view is not centered

Summary
Should text be centered in this case?

Relevant information

@Gagne87 @clastzoo what about button with icons?

with centre looks strange

duplication #562


FileRef::fonts() would be more handy if Iterator would work like enumerate()

FileRef::fonts() returns:
https://docs.rs/read-fonts/latest/src/read_fonts/lib.rs.html#201-207
pub fn fonts(
&self,
) -> impl Iterator<Item = Result<FontRef<'a>, ReadError>> + 'a + Clone
It would be slightly more handy if this was a flattened list of (FontRef, Option<u32>) containing the collection indices - otherwise one can't tell from each FontRef what it originates from.

Perhaps something like
let (iter_one, iter_two) = match fileref {
        Some(Font(font)) => (Some((Ok(font.clone()), None)), None),
        Some(Collection(collection)) => (
            None,
            Some(
                collection
                    .iter()
                    .enumerate()
                    .map(|entry| (entry.1, Some(entry.0 as i32))),
            ),
        ),
        None => (None, None),
    };
    let fonts = iter_two.into_iter().flatten().chain(iter_one);

But instead, perhaps the collection.iter() should already have the ttc indices so we don't have to generate them with enumerate().


Update installation instruction of pipectl image

What this PR does / why we need it:
Current most users can be supposed to Docker users. Even if they use podman, all flags can be pass-through.
Anyway, the current installation instruction is a little bit unkind.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/lgtm


[CP Staging] Revert "Bump react-fast-pdf"

Reverts Expensify/App#39578
Fixes this deploy blocker: https://github.com/Expensify/App/issues/39833
Details

Fixed Issues

$ https://github.com/Expensify/App/issues/39833
PROPOSAL:
Tests

Navigate to any report
Send two pdf files
Open the last one
Verify the last pdf file is opened

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as Tests

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari
![Screenshot 2024-04-08 at 5 42 00 PM](https://github.com/Expensify/App/assets/7277067/d93cba3a-e621-4f00-8c3b-b62e9e786a82)

MacOS: Desktop

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Hmm the Verify Podfile check is failing on the Setup Node step:
npm ERR! Exit handler never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://github.com/npm/cli/issues>
npm ERR! A complete log of this run can be found in: /Users/runner/.npm/_logs/2024-04-08T22_10_23_665Z-debug-0.log

I'm not really sure what's up with that and also not seeing it fail on other PRs. An npm install did take a very long time for me locally, not sure if that's related. I guess I'll try running it again to see if that helps

Requested CP here: https://expensify.slack.com/archives/C07J32337/p1712628550724549

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

CP deployed, retest on staging looks good to me:
https://github.com/Expensify/App/assets/7277067/a2b55916-30b4-4224-8303-2d1d1d9c3f77

🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.61-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Android build fail

Describe the bug
following this doc: https://renative.org/docs/android
when i try to run on simulator i receive this error

FAILED with ERROR:
FAILURE: Build failed with an exception.
* What went wrong:
Could not open settings remapped class cache for aqvcm0rui3eivqpvn43yjd999 (/home/desi/.gradle/caches/5.5/scripts-remapped/settings_4e81b1yuc4rq7sjft1dn1tn0r/aqvcm0rui3eivqpvn43yjd999/settings74e694b976d6abaa826c8abac43e9de8).
> Could not open settings generic class cache for settings file '/home/desi/del/3/prova/platformBuilds/helloWorld_android/settings.gradle' (/home/desi/.gradle/caches/5.5/scripts/aqvcm0rui3eivqpvn43yjd999/settings/settings74e694b976d6abaa826c8abac43e9de8).

To Reproduce
Steps to reproduce the behavior:

rnv new
rnv start
rnv run -p android

Screenshots

Desktop

OS: arch linux
Node Version 12.12.0
RNV Version 0.28.0-alpha.11

check if jetify has been launched. (see the warning)
This converts your node_modules to gain compatibility with AndroidX.
try to run npx jetify and then run command

I've add in the package.json the entry for jetify already but I still see that warning.
I try to manually launch npx jetify but nothing change.
I'm sending my package.json and renative.json.

Can you try to clear the gradle cache ~/.gradle/caches ?

I've already try to delete ~/.gradle/caches but I've the same problem. I also try only to delete the .lock files

What version of JDK do you have? If it's 13, it's incompatible with current version of gradle:
https://github.com/gradle/gradle/issues/8681
Gradle 6 should fix it but it's not released yet, so downgrading to version 11 is way to go for now.

@hosek You're right, thanks you for the help


WIP: Implement a generic informer

NOTE: This PR is not ready for review until #564 merges.
The generated clients need to be removed as a precondition to implementing HA (due to a client-go dependency), but the generic client intended to replace the generated clients does not support the watch call necessary for informers.  This commit hacks together a generic informer to work around that omission so that the generic client is a viable replacement for the generated clients.

@shashidharatd Hopefully this PR can unblock your efforts to remove the generated clients.

This LGTM, would wait for other reviewers, if they have any comments.

Rebased

Holding for review

/lgtm

/hold cancel


node_modules caching in the github actions doesn't appear to work

npm install consistently takes about 30 seconds, which implies it's downloading all the packages everytime. This probably means the caching (defined here https://github.com/cloudflare/wrangler2/blob/973b8f2dd93a1d5976e650fa5228bf605dd9326d/.github/workflows/prereleases.yml#L25-L30) isn't working.

I will take a look and fix that tomorrow.

fixed in #146, thanks @JacobMGEvans


[consensus] fix the flaky reconfiguration test

Motivation
There may be timeout and more than 3 rounds to commit the reconfiguration, rewrite in a more robust way.
Have you read the Contributing Guidelines on pull requests?
Y
Test Plan
unit tests.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

@bors-libra r=davidiw

:pushpin: Commit bc5351d has been approved by davidiw

:hourglass: Testing commit bc5351dca4cbb75bf193a4465ee43a1642e15b34 with merge 41d2769addb709770f6752c40970ac64bc80ac50...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: davidiw
Pushing 41d2769addb709770f6752c40970ac64bc80ac50 to master...


FileNotFoundError: [Errno 2] No such file or directory: 'zinc.json'

hi,
could you please tell me how to solve the problem? The zinc.json file exists in the folder, but the compiler reports an error when running the code and prompts that the file does not exist.

same problem here, have you eventually solved it?


Update release-notes-ssdt-2019.md

Docs Build status updates of commit 22bd32d:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

Line 0, Column 0: [Error: download-failed] Download failed for file 'https://opdhsblobprod04.blob.core.windows.net/contents/ed9486619cb4489daa42ea135cedccf6/37d3d5608486442d8b613133e277feec'. Try closing and reopening the PR. If you get this Error again, file an issue.
Line 0, Column 0: [Error: download-failed] Download failed for file 'https://opdhsblobprod04.blob.core.windows.net/contents/3da204225a37425ebc2303acb826e049/a1daaff1460356f8c21e95b8262ec3a1'. Try closing and reopening the PR. If you get this Error again, file an issue.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@WendyYes - since you have access to the private repos, you should open all prs in those repositories. The review tools we have there are much more robust.

Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.
We'll close this PR. Thank you.


Go To Def Doesn't Work When There's an Error

@code {
    private int currentCount = 0;

    private void IncrementCount()
    {
        klsdjaflkjiojw
        currentCount++;
        currentCount++;
    }
}

Same thing happens in a C# file. By design.


Email in Guest user invitation might be case-sensitive

Given I am an administrator of Azure AD tenant (non-federated), when I add a guest user from another Azure AD tenant (federated), I have to guess the exact spelling of email address to create a working invitation link. If there is a difference in case, the user receives error "AADB2B_0001 : We cannot create a self-service Azure AD account for you because the directory is federated. Tenant's admin must create an account for you. "
Maybe this behavior is caused by the configuration of AD FS in the federated Azure AD tenant, but I think it is worth mentioning in the documentation.

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

ID: 751889da-f001-117f-d525-3b27d467edf2
Version Independent ID: ce46adec-de86-7c34-45ba-d735cba76d2d
Content: Add B2B collaboration users in the Azure portal - Azure AD
Content Source: articles/active-directory/b2b/add-users-administrator.md
Service: active-directory
Sub-service: b2b
GitHub Login: @msmimart
Microsoft Alias: mimart

@arkein, thank you for reaching out. We are looking into this and would get back to you soon on this thread.

@arkein there is an active feedback regarding this at our feedback portal. You can vote and track for updates here:
https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/38748157-need-some-way-to-deal-with-aadb2b-0001-we-cann


[T3A2][W09-A4]Vu Hai Long

Ready for review

it will be better to use method name getFeedbackToUser rather than showFeedbackToUser. It is a getter method, also show implies display in the UI

@haiilong Some comments added. Please close the PR after reading comments


BED/BEDPE Overwrite rather than create new typed columns + offbyone fix

Original code contained an off by one error in BEDPE path and created new columns rather than replacing existing.

Can one of the admins verify this patch?

add to allow list

add to allowlist


How can I send custom params to my events source?

I want to send some custom params to the events source everytime it is hit to fetch data. One way I can understand is to send it as GET request params like 'events.json.php?id=100'. Is there some other better way to do this.

Yeah, you can set events_source as a function, and fetch your own get/post / ajax call ;)


Extend HOMC to include h > 4

Current HOMC implementation is hardcoded up to h = 4. This should be made scalable to larger values even though these processes will be extremely complex and heavy on memory.
A good clue on the pattern to be automated is found in homc_helpers.py

This was fixed in version 1.1.0


METRICS_TOKEN should be optional

autoupdate can't be run locally without -no-update currently (and I don't want to disable the git commit/push logic) .
2020/07/04 20:38:41 f/fabric.js.json: run /usr/bin/git commit -m Add fabric.js v4.0.0-rc.1
panic: Env METRICS_TOKEN is missing
 [recovered]
	panic: Env METRICS_TOKEN is missing

goroutine 1 [running]:
github.com/cdnjs/tools/sentry.PanicHandler()
	/home/kristian/Hentet/cdnjs/tools/sentry/sentry.go:28 +0x74
panic(0x79c600, 0xc00016a8b0)
	/usr/lib/go/src/runtime/panic.go:969 +0x166
github.com/cdnjs/tools/util.GetEnv(0x82662c, 0xd, 0xc0004dfcf0, 0x5267e1)
	/home/kristian/Hentet/cdnjs/tools/util/env.go:18 +0xf9
github.com/cdnjs/tools/metrics.reportMetric(0x825cf1, 0xb)
	/home/kristian/Hentet/cdnjs/tools/metrics/metrics.go:17 +0x48
github.com/cdnjs/tools/metrics.ReportNewVersion(...)
	/home/kristian/Hentet/cdnjs/tools/metrics/metrics.go:25
main.commitNewVersions(0x8b5d60, 0xc00027e960, 0xc000141650, 0x1, 0x1)
	/home/kristian/Hentet/cdnjs/tools/cmd/autoupdate/main.go:225 +0x31a
main.main()
	/home/kristian/Hentet/cdnjs/tools/cmd/autoupdate/main.go:109 +0x65c

Yes indeed. I suggest that we simply disable metrics if the token is not present (maybe just log something for debugging purposes).

Making changes now

Fixed by #71


[release-1.4] Turn auto mTLS on by default for 1.4

This is an automated cherry-pick of #18030

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_istio_release-1.4
b3c799b3ca33a6425bc6bf04b1feb25f8e86ffeb
link
/test gencheck_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_istio_release-1.4
b3c799b3ca33a6425bc6bf04b1feb25f8e86ffeb
link
/test gencheck_istio_release-1.4

integ-new-install-k8s-tests_istio_release-1.4
b3c799b3ca33a6425bc6bf04b1feb25f8e86ffeb
link
/test integ-new-install-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_istio_release-1.4
b3c799b3ca33a6425bc6bf04b1feb25f8e86ffeb
link
/test gencheck_istio_release-1.4

integ-new-install-k8s-tests_istio_release-1.4
b3c799b3ca33a6425bc6bf04b1feb25f8e86ffeb
link
/test integ-new-install-k8s-tests_istio_release-1.4

pilot-multicluster-e2e_istio_release-1.4
b3c799b3ca33a6425bc6bf04b1feb25f8e86ffeb
link
/test pilot-multicluster-e2e_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio_release-1.4
b3c799b3ca33a6425bc6bf04b1feb25f8e86ffeb
link
/test pilot-multicluster-e2e_istio_release-1.4

integ-new-install-k8s-tests_istio_release-1.4
b3c799b3ca33a6425bc6bf04b1feb25f8e86ffeb
link
/test integ-new-install-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio_release-1.4
b3c799b3ca33a6425bc6bf04b1feb25f8e86ffeb
link
/test pilot-multicluster-e2e_istio_release-1.4

integ-new-install-k8s-tests_istio_release-1.4
b3c799b3ca33a6425bc6bf04b1feb25f8e86ffeb
link
/test integ-new-install-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-new-install-k8s-tests_istio_release-1.4

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio_release-1.4
b3c799b3ca33a6425bc6bf04b1feb25f8e86ffeb
link
/test integ-new-install-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio_release-1.4
b3c799b3ca33a6425bc6bf04b1feb25f8e86ffeb
link
/test integ-new-install-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Close icon is almost invisible on the 'Set schedule' dialog window in dark theme

Initially reported by @albinazs as part of WCAG 2.2 AAA* audit of the Wagtail admin – Nov 2023.
In our dialog modals, Close icon is almost invisible in dark theme
This is failure of 1.4.11 Non-text Contrast:

Visual objects must have a contrast ratio of 3:1 against adjacent color(s)

Code in question:
<button type="button" class="w-dialog__close-button" aria-label="Close dialog" data-action="w-dialog#hide">
                <svg class="icon icon-cross w-dialog__close-icon" aria-hidden="true"><use href="#icon-cross"></use></svg>
            </button>

Solution
Probs an easy fix? Use a different color / correct CSS style override.

Hello there @thibaudcolas,  can I work on this issue..? :)

Is this related to #11306 ?

Thanks @zerolab, yes :) closing as dupe, I missed that one.


How to restore "raspicam" apps?

Hi,
You know, before the bullseye system, the camera applications were raspistill,raspivid, but after the bullseye was released, the original camera applications raspistill,raspivid all failed, and picamera, a python library, could not be used. I want to restore the original camera application so that the picamera library can continue to be used. What should I do? Any help would be greatly appreciated!

Hi, there is a forum post here: https://forums.raspberrypi.com/viewtopic.php?t=323390&sid=65b91e146d233b5282246a4e917fe5f1 or alternatively users can continue to use Buster.

Hi，Thank you very much!!! I have succeeded!

Great, thanks for letting us know.


Add multiply

Summary by Sourcery
This pull request introduces the multiply_add function and its variants for performing element-wise multiplication and addition on images. It also includes comprehensive tests for these new functions and updates the pre-commit configuration to use the latest version of ruff.

New Features:

Introduced multiply_add function and its variants (multiply_add_numpy, multiply_add_opencv, multiply_add_lut) for element-wise multiplication and addition on images.

Tests:

Added comprehensive tests for the new multiply_add function and its variants, covering different data types, factors, values, and image configurations.

Chores:

Updated .pre-commit-config.yaml to use ruff version v0.4.7.

Codecov Report
Attention: Patch coverage is 90.90909% with 7 lines in your changes missing coverage. Please review.

Please upload report for BASE (main@ca8baf1). Learn more about missing BASE report.

Files
Patch %
Lines

albucore/functions.py
82.50%
7 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #13   +/-   ##
=======================================
  Coverage        ?   57.01%
=======================================
  Files           ?       13
  Lines           ?      998
  Branches        ?        0
=======================================
  Hits            ?      569
  Misses          ?      429
  Partials        ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add tests for binary values

This PR adds tests for the binary values introduced in #1662 and fixes some subtle bugs along the way.
Closes #2082.

@OmnipotentEntity Could you please have a look? Maybe I broke something along the way. I am still not 100% sure whether the internal binary type fits as it is right now, but at least now there is better coverage to test some things.

I distinctly remember typing up a response to this thread yesterday.  I guess I forgot to actually click comment.  Whoops.
I clearly didn't understand SAX on my first time through, and I forgot to adjust it as I learned exactly what it was supposed to do, whoops.
Good catch on the binary comparison bug, that one is actually somewhat funny.
I don't quite understand the binary constructor fix, but what I don't understand is why I wrote that code in the first place.  I was probably cribbing off of the array code, but that's entirely not necessary for a single valued function.
Tests look good to me.  New features are smart additions.

Coverage increased (+1.01%) to 99.841% when pulling<PHONE_NUMBER>ffcd430921b29e8201948271a413cf on issue2082 into 1de30bc6111a6c063c4aa2e3eccefce8c09e1c62 on develop.


Address stats redesign

The date string is getting on the same line with the address. I think it will look better if we move it to a new line. What do you think?

Fixed @abarmat's comment

Alternatively, we can fix by CSS with:
.AddressStats .Definition dt a {
  display: block;
  font-weight: normal;
}

@eordano I see the same problem happening with the
I'll push the CSS change.

I think it looks better in a new line.


CLI:  Add gas config to the client.toml config file

Background
Many CLI txs require custom gas configs. This is annoying to write every time and leads to long commands. We can add a config for this in client.toml specifying the default if they are not set
Suggested Design
Base it on https://github.com/CosmosContracts/juno/pull/601
Acceptance Criteria
Txs on the CLI don't require --gas auto --gas-prices 0.1uosmo --gas-adjustment 1.3 as those can be directly picked up from the config

Is anyone working on this?

no, just added it yesterday when I was sick of copy pasting the gas params :p


Fix scroll issue on ios

Changing height to min-height seemed to fix the scroll issue. I know ios safari tends to have issues with vh at times.
Not sure what the purpose of min-height/height: 100vh is though since there doesn't seem to be a background color set (which is what I have seen it used for). I assume min-height works just as well as height for the intended purpose. Could be wrong.
Tested out on the ios simulator via xcode.
I was having issues seeing my changes when I didn't have my console open (which disables caching). Not sure what framework is being used to build but it seemed to be caching the css pretty well. Added in a cache bust so that the changes will propagate to former users if/when this is deployed.
Not sure what your preferred cache busting strategy is. This will always cache bust on each deployment. Didn't think it was a big deal for the clients to download 300 lines of css even if they didn't change and it was a pain to manually cache bust each time I changed the css in development.
And I also committed the lock file to git for stable dependencies across developers.

@ekeric13 ah I just tried this and unfortunately it seems to have broken scrolling for me on desktop (tried chrome and safari on osx).

Modified the fix so I keep the height:100vh, just give it overflow: auto at a lower media query.

Ok cool, looks good to me, thanks for that!


Update Sample Code that are currently using fluent SDK to T2 SDK- AKS

Azure-Samples/aks-dotnet-manage-kubernetes-cluster

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Storage:0.4075168,IoT:0.0352294,Tables:0.021360356'

@ArthurMa1978 is this still a valid concern?


[Suggestion] Use the the default stdout sys.__stdout__ in connection.py in case sys.stdout is overwritten

Heya I think this is a super great tool for me to call JS in python! It really helps me a lot.
I encountered a corner case about the stdout when I used the python package javascript. If the sys.stdout is somehow overwritten, an io.UnsupportedOperation: fileno error could occur. Currently, I fixed this by rewriting the sys.stdout to the default stdout before importing:
def load_javascript():
    import sys
    old_stdout = sys.stdout
    sys.stdout = sys.__stdout__
    from javascript import require
    sys.stdout = old_stdout
    return require

So just a little suggestion here: I think the package could be more robust if we replace sys.stdout by std.__sysout__ by in connection.py:
https://github.com/extremeheat/JSPyBridge/blob/c54d2947086734eaa823975162296d8e1a8ea0b1/src/javascript/connection.py#L6-L9
The following is the detail about my use case:
If I import the require inside a function or class rather than globally in a python file, like in a.py:
# a.py
def func():
    from javascript import require
    js_mod = require('xxx')

If I run a unit test by unittest calling func in PyCharm:
import unittest
from src.a import func

class TestA(unittest.TestCase):

    def test_a(self):
        func()

There would be an error occurred like:
--====--	--====--

Bridge failed to spawn JS process!

Do you have Node.js 16 or newer installed? Get it at https://nodejs.org/

--====--	--====--
Exception in thread Thread-2:
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/threading.py", line 954, in _bootstrap_inner
    self.run()
  File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/threading.py", line 892, in run
    self._target(*self._args, **self._kwargs)
  File "venv/lib/python3.9/site-packages/javascript/connection.py", line 122, in com_io
    raise e
  File "venv/lib/python3.9/site-packages/javascript/connection.py", line 111, in com_io
    proc = subprocess.Popen(
  File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/subprocess.py", line 825, in __init__
    errread, errwrite) = self._get_handles(stdin, stdout, stderr)
  File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/subprocess.py", line 1596, in _get_handles
    c2pwrite = stdout.fileno()
io.UnsupportedOperation: fileno
Timed out get 0 needsNodePatches <Thread(Thread-3, started daemon<PHONE_NUMBER>68000)>

And I believe the reason could be that sys.stdout is somehow overwritten to be a FlushingStringIO (which don't have a method fileno()) by either unittest or PyCharm.

Sounds good can you open a PR with the change?
In the code there is similar special handling for Jupyter notebooks which also overwrite the stdio interface, so we use subprocess.PIPE for stdout and then spin a thread to read the stdout of the node process and manually write to stdout of the python process. Maybe that code could be expanded for situations like this. But this would need to be investigated, for now I think potentially no JS stdout is better than crashing.

0.2.14 was released with some fixes for issues like this. Please re-open if this is still an issue.

This works well for me. Thank you for your update!


sandbox URL

Hey
Currently the URL is hardcoded to this in the code.
// DefaultAPIBaseURL is the default base URL for API requests
const DefaultAPIBaseURL = "https://api.transferwise.com"
Would it be useful to also be able to tell it to use the sandbox URL ?
https://api.sandbox.transferwise.tech/
Maybe best way is to have a config boolean called "useSandbox", and then in pkg/client.go pick the right URL.

Also i noticed that there use different versions in the URL depending on the operation.
https://api-docs.transferwise.com/#exchange-rates-list

GET https://api.sandbox.transferwise.tech/v1/rates

https://api-docs.transferwise.com/#quotes-create

POST https://api.sandbox.transferwise.tech/v2/quotes

saw that your using the old one "/v1/quotes/" for some reason. Maybe the Sandbox and Production use different versions ?

Good idea @gedw99 , sorry I took ages to see this. Have upgraded to v2 quotes

Thanks @jtrotsky.


Plans never get executed

Version
rancher/system-upgrade-controller:v0.7.5
Platform/Architecture
linux/arm64
Describe the bug
For some reason, my plans are no longer getting executed.  Here's my two plans:
 Server plan
apiVersion: upgrade.cattle.io/v1
kind: Plan
metadata:
  name: server-plan
  namespace: system-upgrade
  labels:
    k3s-update: server
spec:
  concurrency: 1
  channel: https://update.k3s.io/v1-release/channels/stable
  nodeSelector:
    matchExpressions:
    - {key: node-role.kubernetes.io/master, operator: In, values: ["true"]}
  serviceAccountName: system-upgrade
  cordon: true
  upgrade:
    image: rancher/k3s-upgrade
---
# Agent plan
apiVersion: upgrade.cattle.io/v1
kind: Plan
metadata:
  name: agent-plan
  namespace: system-upgrade
  labels:
    k3s-upgrade: agent
spec:
  concurrency: 1
  channel: https://update.k3s.io/v1-release/channels/stable
  nodeSelector:
    matchExpressions:
    - {key: node-role.kubernetes.io/master, operator: DoesNotExist}
  serviceAccountName: system-upgrade
  prepare:
    image: rancher/k3s-upgrade
    args: ["prepare", "server-plan"]
  drain:
    force: true
    skipWaitForDeleteTimeout: 60
  cordon: true
  upgrade:
    image: rancher/k3s-upgrade

I'm running a k3s cluster with one master and three worker nodes:
NAME      STATUS   ROLES                  AGE    VERSION
master1   Ready    control-plane,master   131d   v1.21.4+k3s1
worker3   Ready    <none>                 131d   v1.21.3+k3s1
worker2   Ready    <none>                 131d   v1.21.3+k3s1
worker1   Ready    <none>                 131d   v1.21.3+k3s1

I upgraded the master node manually (I've been struggling with this problem for a while).  But the controller never triggers the updates.  I activated debug logging on the controller:
W0916 19:41:04.986567       1 client_config.go:543] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.   Clearly, it's seeing there's a more recent version, but the updates never start.
To Reproduce

Install controller and apply plans as per above
Nodes should be upgraded

Expected behavior
Nodes should be upgraded, or an error should be shown.
Actual behavior
No upgrades occur.
Additional context
Already was seeing this problem with the master nodes (haven't found the root cause, but checked the obvious like the nodeSelector criteria), but now agents are no longer getting upgraded.

@clambin are you sure that the upgrades haven't been applied? can you share the output of kubectl get node --show-labels?
https://update.k3s.io/v1-release/channels/stable currently redirects to https://github.com/k3s-io/k3s/releases/tag/v1.21.4+k3s1

the worker nodes remain on 1.21.3, so yeah, the upgrades aren't getting applied.   Here's the nodes with the labels:
NAME      STATUS   ROLES                  AGE    VERSION        LABELS
worker1   Ready    <none>                 131d   v1.21.3+k3s1   beta.kubernetes.io/arch=arm64,beta.kubernetes.io/instance-type=k3s,beta.kubernetes.io/os=linux,k3s.io/hostname=worker1,k3s.io/internal-ip=<IP_ADDRESS>,kubernetes.io/arch=arm64,kubernetes.io/hostname=worker1,kubernetes.io/os=linux,node.kubernetes.io/instance-type=k3s,plan.upgrade.cattle.io/agent-plan=57eb7803114642f8ff2061b7aee4d0bf7606d79e1eb8454da54e1f41
worker3   Ready    <none>                 131d   v1.21.3+k3s1   beta.kubernetes.io/arch=arm64,beta.kubernetes.io/instance-type=k3s,beta.kubernetes.io/os=linux,k3s.io/hostname=worker3,k3s.io/internal-ip=<IP_ADDRESS>,kubernetes.io/arch=arm64,kubernetes.io/hostname=worker3,kubernetes.io/os=linux,node.kubernetes.io/instance-type=k3s,plan.upgrade.cattle.io/agent-plan=57eb7803114642f8ff2061b7aee4d0bf7606d79e1eb8454da54e1f41
worker2   Ready    <none>                 131d   v1.21.3+k3s1   beta.kubernetes.io/arch=arm64,beta.kubernetes.io/instance-type=k3s,beta.kubernetes.io/os=linux,k3s.io/hostname=worker2,k3s.io/internal-ip=<IP_ADDRESS>,kubernetes.io/arch=arm64,kubernetes.io/hostname=worker2,kubernetes.io/os=linux,node.kubernetes.io/instance-type=k3s,plan.upgrade.cattle.io/agent-plan=57eb7803114642f8ff2061b7aee4d0bf7606d79e1eb8454da54e1f41
master1   Ready    control-plane,master   131d   v1.21.4+k3s1   beta.kubernetes.io/arch=arm64,beta.kubernetes.io/instance-type=k3s,beta.kubernetes.io/os=linux,k3s.io/hostname=master1,k3s.io/internal-ip=<IP_ADDRESS>,kubernetes.io/arch=arm64,kubernetes.io/hostname=master1,kubernetes.io/os=linux,node-role.kubernetes.io/control-plane=true,node-role.kubernetes.io/master=true,node.kubernetes.io/instance-type=k3s,plan.upgrade.cattle.io/server-plan=57eb7803114642f8ff2061b7aee4d0bf7606d79e1eb8454da54e1f41z

hmm, interesting.  I removed the label from one of the worker nodes and got the following event:
time="2021-09-17T07:47:40Z" level=error msg="error syncing 'system-upgrade/agent-plan': handler system-upgrade-controller: failed to update system-upgrade/apply-agent-plan-on-worker1-with-57eb7803114642f8ff2061b7-22b40 batch/v1, Kind=Job for system-upgrade-controller system-upgrade/agent-plan: jobs.batch \"apply-agent-plan-on-worker1-with-57eb7803114642f8ff2061b7-22b40\" not found, requeuing

After that, the upgrade job got queued and the node got upgraded.  Did the same for the other 2 worker nodes and now all nodes are upgraded again.

hmm, interesting. I removed the "plan.upgrade.cattle.io" label from one of the worker nodes and got the following event:
time="2021-09-17T07:47:40Z" level=error msg="error syncing 'system-upgrade/agent-plan': handler system-upgrade-controller: failed to update system-upgrade/apply-agent-plan-on-worker1-with-57eb7803114642f8ff2061b7-22b40 batch/v1, Kind=Job for system-upgrade-controller system-upgrade/agent-plan: jobs.batch \"apply-agent-plan-on-worker1-with-57eb7803114642f8ff2061b7-22b40\" not found, requeuing

After that, the upgrade job got queued and the node got upgraded. Did the same for the other 2 worker nodes and now all nodes are upgraded again.

Sounds like another spotting of #134 in the wild. We should have a fix out soon to address.

Should be fixed. Please see https://github.com/rancher/system-upgrade-controller/issues/134#issuecomment-933734170:

v0.7.7 (arrow_right [backport release-0.7] job parallelism is zero unless in applying list #153)
v0.8.0 (arrow_right job parallelism is zero unless in applying list #145 )


Fix for 'Obserable.fromEvent is not a function'.

This change is

I am very appreciative of this pull request, is there any way to move this review along quicker so that is can be published? Would appreciate it even more :)

on npm run build I still get the error:
• TS2305 - src/lib/core/overlay/scroll/scroll-dispatcher.ts(5,21): Module '"/home/md2/node_modules/rxjs/Rx"' has no exported member 'fromEvent'.

It looks like the MD2 project is dead.
You can follow [https://github.com/ReactiveX/rxjs/issues/4070#issuecomment-428901656](this link) for a hacky workaround for this error

As a work arround :
Go to: node_modules\md2\core\overlay\scroll\scroll-dispatcher.js
line 13 :  import { Observable } from 'rxjs/Observable'; replace with :  import { Observable } from 'rxjs';


Adding acme-domain environment variable

Right now --acme-domain is just a command line option however to get rancher running on azure container service you can just modify environment variables, so it might be useful to add an environment variable for it as well:
https://github.com/rancher/rancher/blob/274d059936b2fd6bc401e38b9da646cf6b58f086/main.go#L101

Thanks @galal-hussein . I tried this one locally and also ran my locally built docker image with ACME_DOMAIN - works great :)

Tested with Rancher server rancher\rancher:master-head version b160c76c8
Deploy with:
docker run -d -e  ACME_DOMAIN=<Domain Name> --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher:master-head
Rancher Logs show environment variable was recognized.
2019/11/15 20:15:58 [INFO] Rancher arguments {ACMEDomains:[Domain Name]AddLocal:auto Embedded:false KubeConfig: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false NoCACerts:false ListenConfig:<nil> AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features:} 2019/11/15 20:15:58 [INFO] Listening on /tmp/log.sock


P1: Users can easily edit and resubmit an existing prompt to get a new response.

Added and closed in https://github.com/sourcegraph/cody/pull/1781


unable to compile this in production mode because of renderToStaticMarkup

First of all, thank you for making this open source!
is there any alternative to renderToStaticMarkup for NextJS?
I keep getting this error when I'm trying to compile it to a production build using NextJs
(Use node --trace-deprecation ...to show where the warning was created)
   Collecting page data  .TypeError: (0 , d.createContext) is not a function
    at 89934 (/Users/alvindivina/Documents/GitHub/webcommerce/.next/server/chunks/2076.js:94:11183)
    at __webpack_require__ (/Users/alvindivina/Documents/GitHub/webcommerce/.next/server/webpack-runtime.js:1:161)
    at 23688 (/Users/alvindivina/Documents/GitHub/webcommerce/.next/server/app/api/trpc/[trpc]/route.js:3:13235)
    at __webpack_require__ (/Users/alvindivina/Documents/GitHub/webcommerce/.next/server/webpack-runtime.js:1:161)
    at __webpack_exec__ (/Users/alvindivina/Documents/GitHub/webcommerce/.next/server/app/api/trpc/[trpc]/route.js:3:15994)
    at /Users/alvindivina/Documents/GitHub/webcommerce/.next/server/app/api/trpc/[trpc]/route.js:3:16046
    at __webpack_require__.X (/Users/alvindivina/Documents/GitHub/webcommerce/.next/server/webpack-runtime.js:1:1707)
    at /Users/alvindivina/Documents/GitHub/webcommerce/.next/server/app/api/trpc/[trpc]/route.js:3:16007
    at Object.<anonymous> (/Users/alvindivina/Documents/GitHub/webcommerce/.next/server/app/api/trpc/[trpc]/route.js:3:16089)
    at Module._compile (node:internal/modules/cjs/loader:1368:14)
unhandledRejection Error: Failed to collect page data for /api/trpc/[trpc]
    at /Users/alvindivina/Documents/GitHub/webcommerce/node_modules/next/dist/build/utils.js:1211:15
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  type: 'Error'
}

I encountered the same error when running inside Next.js (latest version).
After adding "use client" on the top of the tsx file which includes renderToStaticMarkup(CONFIGURATION, { rootBlockId: 'email-builder-root' });, new error encountered:
TypeError: Cannot read properties of undefined (reading 'Component')

> 14 |   const string = renderToStaticMarkup(CONFIGURATION, { rootBlockId: 'email-builder-root' });

I have tried to work with renderToStaticMarkup (from react/server) and it works great, but I have no idea how to continue debugging..

I created an api that separates renderToStaticMarkUp from the next js main codebase. Now my app works fine and calls an api if it needs to convert json to html

Hi @alvindivina08, is it possible to share some details on how to resolve this issue?
Thanks a lot! ❤

I have it in my repo and deployed it using vercel. Feel free to take a look and copy it

Thanks a lot!

I remember us having this issue in the early days of the project and we fixed it in this PR https://github.com/usewaypoint/email-builder-js/pull/91/files that uses react-dom/server as a peer dependency and wraps with this function https://github.com/usewaypoint/email-builder-js/blob/1245bdac807e0989babcd4b2db1bc3a2a3bbf376/packages/email-builder/src/renderers/renderToStaticMarkup.tsx
That PR seemed to solved this issue for a couple of people.


Adds environment variable to allow for passing in jvm args to helios …

…wrapper.

Codecov Report

Merging #1123 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1123      +/-   ##
============================================
+ Coverage     52.09%   52.14%   +0.05%
- Complexity     1581     1582       +1
============================================
  Files           267      267
  Lines         12861    12861
  Branches       1483     1483
============================================
+ Hits           6700     6707       +7
+ Misses         5653     5647       -6
+ Partials        508      507       -1


[Java] support for Arrow's float16

DESCRIPTION

I'm wondering if there's any interest in supporting Arrow's float16 type in Parquet.
There seem to be one or two float16 / halffloat tickets here (e.g., PARQUET-1403) but nothing that speaks to adding half-float support to Parquet in-general.
PLANS
I'm able to spend some time on this, if someone points me  in the right direction.

Add the HALFFLOAT or FLOAT16 enum (any preferred naming convention?) to https://github.com/apache/parquet-format/blob/master/src/main/thrift/parquet.thrift#L32

Add HALFFLOAT to org.apache.parquet.schema.PrimitiveType

Add HALFFLOAT support to org.apache.parquet.arrow.schema.SchemaConverter

Add encoding for new type at org.apache.parquet.column.Encoding

??
If anyone has any interest in this, pointers, or comments, they would be greatly appreciated!

Reporter: The Alchemist
Assignee: Jiashen Zhang / @zhangjiashen
Related issues:

[Format] HALF precision FLOAT Logical type (depends upon)

PRs and other links:

GitHub Pull Request #1142
GitHub Pull Request #1235

Note: This issue was originally created as PARQUET-1647. Please see the migration documentation for further details.

Ben Harkins / @benibus:
I'm currently working on this, so feel free to assign me. Although it's probably worth mentioning that the current plan is to implement this as a logical type in accordance with the proposal PR for PARQUET-758, which deviates from some of the plan in this issue's description.

Freddy Fostvedt:
Thanks for putting effort into this @benibus , this is a very valuable piece at my place of work. It will save very significant costs on data processing / training cost if we can reduce memory usage.

JAVIER ANDRES RECASENS SANCHEZ:
Any updates regarding this issue? We are very interested in float16 support. Thanks!

The Alchemist:
[~jrecasens] , [~orecoupa] :
Unfortunately, I have moved on and don't have the time to work float16 Parquet support.

JAVIER ANDRES RECASENS SANCHEZ:
[~the_alchemist] thanks for the update.

Is there anyone that could help with this?

Orestis:
[~the_alchemist] Thank you for the initiative. Is there any update for this issue?


[$250]  Imported reports become "Hmm... it's not here" in new dot

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v9.0.14-5
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @hannojg
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1722248571855789
Action Performed:

Imported reports in old dot (the attached file, 500 reports)
The reports show up in the workspace chat in new dot after import
clicking on a report in new dot gets you the "Hmm... it's not here" error

Expected Result:
Imported reports are usable in new dot
Actual Result:
Clicking on a report in new dot gets you the "Hmm... it's not here" error
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/1d387d6a-ba67-4964-98bf-5f5373dc7027

View all open jobs on GitHub
https://github.com/user-attachments/assets/f21708d1-2101-4f13-bba2-48a8ed91ba86
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01cad85d32f0e40e56
Upwork Job ID:<PHONE_NUMBER>621252764
Last Price Increase: 2024-09-06

Issue OwnerCurrent Issue Owner: @hoangzinh

I think this is a low priority Control item, because it's covering a backwards compatibility edge case

Proposal for Fixing Issue #46576: "Imported Reports Become 'Hmm... it's not here' in New Dot"
Issue Summary:
The issue occurs when reports imported from the old dot show up in the new dot workspace chat, but when clicked, they display an error message: "Hmm... it's not here." The reports are not accessible, which disrupts the workflow and usability.
Technical Explanation:

Root Cause Analysis:

The issue likely stems from a mismatch or inconsistency in the report IDs or URLs between the old dot and the new dot environments.
During the import process, the reports may retain their old identifiers or metadata that do not match the expected format in the new dot.
The new dot environment likely references reports differently, possibly using a new routing structure or different URL paths, which results in the "not found" error.

Proposed Solution:

Step 1: Investigate the Import Process:

Analyze how the reports are imported from the old dot to the new dot. Identify any discrepancies in the ID mapping, URL formatting, or metadata attached to these reports during the import.

Step 2: Normalize the Report IDs/URLs:

Implement a normalization process during the import to ensure that the report IDs/URLs are correctly translated or mapped to the format expected by the new dot.
This may involve creating a mapping function or service that automatically converts the old dot IDs/URLs to the new format.

Step 3: Update Routing Logic:

Ensure that the routing logic in the new dot is capable of handling reports imported from the old dot. This might involve adding backward compatibility in the routing logic or introducing redirects that point old URLs to their corresponding new locations.

Step 4: Add a Fallback Mechanism:

Introduce a fallback mechanism to handle cases where the report is still not found. This could involve an additional lookup or query to attempt to locate the report based on alternative identifiers or metadata.

Testing Plan:

Test the solution thoroughly across all browsers (Chrome/Safari) to ensure that the imported reports are accessible and do not display the "Hmm... it's not here" error.
Perform regression testing to confirm that the fix does not introduce new issues and that all reports, both old and new, are handled correctly.
Verify that the solution works for a variety of report types and scenarios, including large imports and edge cases.

Documentation and Code Submission:

Document the changes made in the codebase, particularly focusing on how the import process has been adjusted and how the new routing logic works.
Submit the code via a pull request to the Expensify/App GitHub repo, including detailed explanations, screenshots, and confirmation of testing results.

Conclusion:
This solution aims to address the root cause of the issue by ensuring that reports imported from the old dot are correctly mapped and accessible in the new dot environment. By normalizing report IDs/URLs and updating the routing logic, we can prevent the "not found" errors and ensure a seamless user experience.

Please review this proposal and provide feedback or approval. If accepted, I will proceed with the implementation as outlined. Thank you!

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link<EMAIL_ADDRESS>

Proposal
Please re-state the problem that we are trying to solve in this issue.
The problem we are addressing is that when reports are imported from the old dot to the new dot, they initially appear in the workspace chat. However, when users click on these reports, they encounter an error message: “Hmm… it’s not here,” rendering the reports inaccessible.
What is the root cause of that problem?
The root cause of the problem likely stems from discrepancies between the report identifiers, URLs, or metadata used in the old dot versus those expected in the new dot. This mismatch causes the new dot system to fail in correctly locating or displaying the imported reports, leading to the error message.
What changes do you think we should make in order to solve the problem?
To solve this issue, we should implement the following changes:
1.	Normalize Report IDs/URLs: During the import process, ensure that report IDs/URLs are converted to match the format expected by the new dot system. This normalization process will involve mapping old dot identifiers to their corresponding new dot formats.
2.	Enhance Routing Logic: Update the routing logic in the new dot to handle these normalized IDs/URLs properly. This may include adding backward compatibility to ensure that reports are correctly routed and displayed.
3.	Introduce a Fallback Mechanism: Implement a fallback mechanism that attempts to locate reports using alternative identifiers or metadata in cases where the initial lookup fails.

What alternative solutions did you explore? (Optional)
Alternative solutions considered include:
•	Rewriting the Import Logic: Completely rewriting the import logic to align the old dot’s data structure with the new dot’s format. This approach was deemed too complex and resource-intensive.
•	Manual Mapping During Import: Manually mapping each report from the old dot to the new dot during the import process. However, this method was found to be less scalable and prone to errors, especially in large-scale operations.

Hi
Which type of export i need to export the reports inside the OD?

I've tried many of thems but no one work

@hoangzinh Oh sorry, I cannot access the slack chat room, because it's a private.

@hoangzinh Thanks, But did you mean i can create a new layout inside the OD on top of that file CV, I've tried that but some properties when trying to link the value i.e {report:nameHere} are not quite accurate meaning like there is no exact or the property name

Imported reports in old dot (the attached file, 500 reports)

Where is the attached file? how to import?

This happens when clientLastReadTime is not an empty string in the first OpenReport request. It can be reproduced by opening the #announce room from LHN. I think this is a BE issue.
https://github.com/Expensify/App/blob/a506fa44fd45d4948a9bfbd9c83b0a0312721133/src/libs/actions/Report.ts#L963
https://github.com/user-attachments/assets/b13ced5c-5efa-4162-9d5d-bdef16f4b7f9

Sorry I missed the internal assignment @hoangzinh , updated. Looping in another BZ member as well as I'm going OOO. Thanks @zanyrenney !

No worries Kev!

Ioni reported a similar issue

When I click on some old expenses (not all), I get redirected to https://staging.new.expensify.com/search/view/3431960930982529 or https://staging.new.expensify.com/search/view/0 (this same IDs every time, no matter the transaction I click) and see Hmm... it's not here page

waiting for internal

hey @hoangzinh thanks for the ping.

Seems like noone internal has been able to pick this up. Can we confirm the behaviour is still reproducible on the latest build?

If so, I can re-flag this in the #expense room

We are free to find our priorities a little bit so this should become easier to get an internal engineer to fix.

I've added it to Hot Picks.

Good thinking @hoangzinh - changing it now.


automode support

I would like to have Heisenbridge automatically giving ops (or voices in some cases) to users whose hostmasks I specify especially in IRCnet where there is no ChanServ. I think it should have option for width to either do it on specific channels or in case the hostmask belongs to user themself on all channels.

It would be fairly easy to set this up per-channel by adding a command that stores the list of masks and target modes into the room itself. The downside is leaving the room will also lose the list but it would be by design.


Ignore shebang

Luaparse marks following first line of a script (shebang) as an error:
#!/usr/bin/lua
...

This is, however, allowed on the first line, as an exception to the normal syntax, according to the Lua manual: http://www.lua.org/manual/5.3/manual.html#7
I am using Atom's linter-luaparse v0.2.0: https://atom.io/packages/linter-luaparse

Technically this is not up to the parser but as the manual states, the interpreter (or the shell).
That being said, it does sound like a common enough use case. A linter shouldn't really need to care about such things either.. I'll try to get a fix in soon, thanks for the report.

I just published v0.2.1 containing the fix to NPM

Thanks!


1e03

Found on google scholar but not on science library x2

Abadi, M., Chu, A., Goodfellow, I., McMahan, H.B., Mironov, I., Talwar, K. and Zhang, L., 2016, October. Deep learning with differential privacy. In Proceedings of the 2016 ACM SIGSAC conference on computer and communications security (pp. 308-318).
Patel, Neel, Reza Shokri, and Yair Zick. "Model explanations with differential privacy." arXiv preprint arXiv:2006.09129 (2020).

Link to arxiv site as non DAIS authors


store/bucket: use roaring bitmaps for postings list

TODO: description/tests/convert set operations into bitwise ops

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Verification

I think we missed one optimization opportunity here - currently fetching and intersection are two separate processes but we can join those two and reuse the same containers to avoid allocations. Let me try to refactor this and rebase on top of recent changes.

@GiedriusS I am thinking if it is better to build the roaring bitmap postings offline at compactor?
Now we are building roaring bitmap during runtime and we still need to download all postings required (if no cache hit).


Update coding style documentation

Related issue: #15932
This updates the current coding style documentation located under runtime/doc/develop.txt.

There are OK s and Ok s in the provided examples.  The
older examples use OK.  Can you please pick one and use it?

I need the opinion of @chrisbra and @yegappan on removing tabs from the code and if we want to enforce to always add { on operators such as ifs and whiles.

I need the opinion of @chrisbra and @yegappan on removing tabs from the code and if we want to enforce to always add { on operators such as ifs and whiles.

I am not attached to either of those. (Personally I have a strong opinion on the use of tabs and try to avoid as much as possible, but that is just me). If no-one has an issue with changing those, then let's make this change.