Getting setState() or markNeedsBuild() called during build.

I'm getting setState() or markNeedsBuild() called during build when i use PaginatedDataTable2. Please help

I don't have an idea what you are talking about...

When I'm using PaginatedDataTable2, the android studio returning "setState() or markNeedsBuild() called during build" error in the console

I don't get such errors

This error i am getting with pagination when i am setting up the initalRowIndex

Minimal reproduction example?


This version of ModSecurity was not compiled with GeoIP or MaxMind support

This version of ModSecurity was not compiled with GeoIP or MaxMind support
nginx version: nginx/1.16.1

Hi @mhrznamn068 how can we help you?

Hi, I also got this error. Can help me to solve it?
Im using nginx 1.16.1

Hi @Piju99,
Have you compiled ModSecurity from GitHub or are you using a package from your distribution?

yes, I have compiled that. But still got the error. Also checked and update GeoIP
nginx: [emerg] "modsecurity_rules_file" directive Rules error. File: /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-910-IP-REPUTATION.conf. Line: 75. Column: 22. This version of ModSecurity was not compiled with GeoIP or MaxMind support.  in /etc/nginx/nginx.conf:50

@Piju99 you need to make sure that you have GeoIP and/or MaxMind development packages in your server. Notice the summary after the execution of ./configure. There will be detailed info on the dependencies support.


429 Request Error with Langchain Huggingface Endpoint

[x] I have checked the documentation and related resources and couldn't resolve my bug.
I want to create synthetic test data. Using the OpenAI or Anthropic API is very expensive so I want to use the HuggingFaceEndpointAPI and run it with Llama3-70B. I am running it on a GPU Compute Cluster and would assume that my compute is sufficient to load and run the model. However, I always run into rate limit error 429. Immediately when the script starts.
Ragas version: newest release (5th July)
Python version: 3.10
Please find below the code. I tripe-checked it and it should be correct. Assume we have langchain document artifact for this of course. I excluded the data loading for better visibility.
Code to Reproduce
import pandas as pd
from ragas.testset.generator import TestsetGenerator
from ragas.testset.evolutions import simple, reasoning, multi_context, conditional
from langchain_community.document_loaders import UnstructuredMarkdownLoader
from langchain_text_splitters import (
    TokenTextSplitter)

from langchain_huggingface import HuggingFaceEndpoint, HuggingFaceEmbeddings

import os
import re
import torch

import time
import random
import logging

device = "cuda:0" if torch.cuda.is_available() else "cpu"
print(f'running on device: {device}')

if __name__ == '__main__':

    def make_request_with_backoff(max_retries=10, max_wait_time=300):
        for attempt in range(max_retries):
            try:
                logging.info(f"Attempt {attempt + 1} of {max_retries}")
                testset = generator.generate_with_langchain_docs(docs, 50, distributions, raise_exceptions=False)
                logging.info(f"Successfully generated {len(testset)} items")
                return testset
            except Exception as e:
                if "429" in str(e):
                    wait_time = min((2 ** attempt) + random.uniform(0, 1), max_wait_time)
                    logging.warning(f"Rate limit hit. Waiting {wait_time:.2f} seconds.")
                    time.sleep(wait_time)
                else:
                    logging.error(f"Unexpected error: {str(e)}")
                    raise e
        raise Exception("Max retries reached")

    #load models
    llm = HuggingFaceEndpoint(
        repo_id="meta-llama/Meta-Llama-3-70B",
        task="text-generation",
        max_new_tokens=512,
        repetition_penalty=1.03,
    )

    embeddings = HuggingFaceEmbeddings(model_name="sentence-transformers/all-mpnet-base-v2")

    generator_llm = llm
    critic_llm = llm
    embeddings = embeddings

    generator = TestsetGenerator.from_langchain(
        generator_llm,
        critic_llm,
        embeddings
    )

    # Change resulting question type distribution
    distributions = {  # uniform distribution
        simple: 0.1,
        reasoning: 0.35,
        multi_context: 0.2,
        conditional: 0.35
    }

    # Configure logging
    logging.basicConfig(level=logging.INFO)

    # Use the function
    testset = make_request_with_backoff()

    testset.to_pandas()

    #store data
    testset.to_parquet('synthetic_data/ragas_llama3_qa.parquet')

Error trace
File "/usr/local/lib/python3.10/dist-packages/aiohttp/client_reqrep.py", line 1005, in raise_for_status
    raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 429, message='Too Many Requests', url=URL('https://api-inference.huggingface.co/models/meta-llama/Meta-Llama-3-70B')
**Expected behavior**

I except the script to be running and use Llama3 to generate the test data.
Additional context
I am running this on 6 Nvidia A10s using a Pytorch Image and Python 3.10.
Specifications from the job script below:
#!/bin/bash

set -xe

srun \
  --gpus=6 \
  --mem=144GB \
  --container-image=/data/enroot/nvcr.io_nvidia_pytorch_23.06-py3.sqsh \
  --container-workdir=`pwd` \
  --container-mounts=/my_path...\
  ./job.sh

from ragas.run_config import RunConfig, add_async_retry, add_retry
Configure run_config for docstore
run_config = RunConfig(max_retries=15, max_wait=90)
generator.set_run_config(run_config)
Use the function with retry logic
testset = make_request_with_backoff()
Hi @dosu where does generator come from

@jonas-nothnagel were you able to figure it out?


docs: blockquote anchor color

As noted in #1094

This also revealed a css usability issue regarding anchor tags in blockquote elements. As the colors of the a elements are being inherited. Currently that would be gray, :visited is unaffected.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.24.0-next.4 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Line numbers for encoding errors?

When Biber encounters a file with bad encoding, currently the error is similar to
[202] Utils.pm:209> ERROR - Data file 'fghjk.bib' cannot be read in encoding 'UTF-8': Can't decode ill-formed UTF-8 octet sequence <F6> at C:\Users\Moritz\AppData\Local\Temp\par-4d6f7269747a\cache-9d6b46fefde4bd584f892f8159e8daefd64788a3\inc\lib/File/Slurper.pm line 63.

Would be it be possible to make the error message point to the line number in the .bib file? (Maybe by reading the file line by line if the module does not support line numbers. If there are performance impacts maybe that could be solved by catching that error and reading the file again line by line to isolate the problematic line.) That would make it much easier for users to spot the problematic character.
MWE (saved in latin1)
\documentclass[british]{article}
\usepackage[T1]{fontenc}
\usepackage[latin1]{inputenc}
\usepackage{babel}
\usepackage{csquotes}

\usepackage[style=authoryear, backend=biber, bibencoding=utf8]{biblatex}

\usepackage{filecontents}
\begin{filecontents}{\jobname.bib}
@book{appleby,
  author  = {Humphrey Appleby},
  title   = {Röstaroma Schloß €úrô},
  date    = {1980},
}
\end{filecontents}

\addbibresource{\jobname.bib}
\addbibresource{biblatex-examples.bib}

\begin{document}
\cite{sigfridsson,appleby}
\printbibliography
\end{document}

It's a pain to do for what seems to be a minor gain ...

I think it's hardly worth it. I'm using a fast library for reading whole files at once which means there are no "lines" that it really recognises. Switching to a line-based library would be slower for very little gain.

@plk I would like to use biber -V as a linter tool in my text editor.
If I understand you correctly, there is no possibility that biber could add line numbers to the messages.
This would increase the speed people fix bibfile issues which I consider is a good enough gain. There is a reason why vim has a quickfix list and similar functionality exists in most text editors.
Right now I have 50 warnings returned by biber, going through them takes some time. I would like to step through them within vim which is not possible without line numbers.
What about having a switch to enable line numbers with the warning that biber becomes slower?


Update rector.php

Description
See https://github.com/codeigniter4/CodeIgniter4/pull/8919
Checklist:

[x] Securely signed commits
[] Component(s) with PHPDoc blocks, only if necessary or adds value
[] Unit testing, with >80% coverage
[] User guide updated
[x] Conforms to style guide

Thank you @kenjis


App crashes when the send feedback button inside the settings view is clicked

Thank you very much for reporting this @skeuomorf

Actually, could you let us know what version of iOS you're using?

Thank you very much for reporting this @skeuomorf
No prb :)

Actually, could you let us know what version of iOS you're using?
Version 9.3.2 on an ipad air.

Thanks @skeuomorf

I see the problem here... we're not checking if MFMailComposeViewController.canSendMail.  I've fixed it and will send over a pull request ASAP.

@skeuomorf the crash is likely occurring you probably don't have any mail accounts set up in the Apple Mail app.  A temporary workaround would be to set up an email account - that will let you send email from most other applications that use the built-in iOS share-to-email function.  Please let me know if that doesn't sound like the issue.

@sreilly Thanks for pushing a fix! I've also tried the workaround and it works.


Added the none() method to lazy.js definitions.

@chrootsu thanks mate!

note
http://danieltao.com/lazy.js/docs/#Sequence-none


Bot Proposal: Remove duplicate search

Since a while GH has duplicate search (while filing an issue) and we kinda compete with that now
Our duplicate search is rarely successful often adds noise like this: user files issue, bot adds duplicate comments, user adds replies to that comment saying its not a dupe.

If we do not want to remove it I would increase the threshold when we decide to comment, so the bot would comment more rarely.

@chrmarti owns duplicate search


Drop bots support

Was never used actively and complicates cs\Session as well as administration frontend significantly

Done in bc3d456


Build for CentOS

Create a role for CentOS. Bashrc for all users can be found here: /etc/bashrc

Will test this tomorrow


GSoC: NuttX support for pysimCoder (info thread)

Dear NuttX community,
as was already mentioned in the mailing list, my project NuttX support for pysimCoder (proposal can be found here) has been accepted for Google Summer of Code under Apache Foundation. I would like to express my gratitude to Apache and NuttX admins for this opportunity as well as to my project mentors Roberto Bucher, Pavel Píša and Brennan Ashton. We are currently discussing details about the implementations as part of a pre coding period.
I will use this GitHub issue for providing regular updates about the project progress once the coding period starts on 7th June. We can also use this thread to discuss some further ideas regarding the NuttX support for pysimCoder. The integration has a great potencial to allow more comfortable NuttX usage in control systems.

Hello all,
the first week of GSoC coding period is about to end and I´d like to refer about the progress we made during the first week and during pre coding period.
During pre GSoC period I extended pysimCoder CAN support for NuttX with SocketCAN support so pysimCoder now supports both characteristic device dev/can0 and socketcan. This was integrated into pysimCoder mainline last week. This week was mainly about incremental encoder and DC motor control, which has been done on STM32 Nucleo F446RE and presented to the mentors during our weekly meeting. DC motor control required support for GPIO driver for Nucleo F446RE which was implemented to NuttX in PR 3880 . This implementation also required new pysimCoder block for relational operation.
The main platform of the project is iMXRT 1060 MCU so the goal is also to get the DC motor control running there, but I am currently having some troubles with encoder driver for imxrt. I already did some fixes to xbar driver (added missing clock), but still some work is to be done in encoder driver (as it stands now, the driver registers the device but do not update the position value).
Yesterday I created a wiki page about the project on pysimCoder git. We agreed during the meeting that the goal would be to store links to commits to pysimCoder and NuttX there as well as the content of our meetings. The page can be found here.

Hello,
another week of GSoC is behind me so I´d like to post some updates since the last week. I extended project wiki from pysimCoder github to NuttX wiki subfolder few days ago, which can be found here. Proper documentation containing information about compiling NuttX with pysimCoder then will be created under Documentation by the end of GSoC period.
The problem with the encoder driver for iMXRT MCU was succesfully solved thanks to my mentor dr. Píša´s help during the debugging session and the changes have been merge to NuttX mainline. I mainly focused on the support for sensors and DAC for pysimCoder then. Support for DHTXX sensor was added as an sensors example yesterday and block for DAC driver was also tested with Nucleo board (iMXRT does not support DAC for external signals).

Hi @michallenc thank you for reporting the status and the issues you faced. About the DAC are you planing to create a driver to iMXRT or just testing on Nucleo board is enough?

Hi @acassis. Unfortunately there is no digital/analog converter output on the iMXRT 1060 chip at all. There is just a 6 bit DAC for on chip internal signals only, but it´s not routed to the external pins (chapter 65 in the reference manual). So DAC can be tested just on Nucleo board.
DAC support should be in newer series iMXRT11xx chips though, but those are not supported by NuttX yet.

Hmm, understood to point. In fact it is sad they didn't included the DAC support in the board!

Hello,
last week of GSoC was mainly about multiple channel PWM support in pysimCoder and PWM support for iMXRT (this was originally by the end of GSoC but I decided to create the driver now so it can be properly tested on iMXRT instead of just STM32). Both multiple channel support in pysimCoder and PWM driver for iMXRT where merged to pysimCoder and NuttX mainline, respectively. I plan to create a single block in pysimCoder which would be able to control DC motor connected to the board with NuttX this week. Current sensing application is also planned.
Last week I also forgot to mention that I had applied for 2021 NuttX Worshop with my presentation about pysimCoder integration with NuttX, so I am looking forward to that, if my presentation gets to the workshop ofcourse.

Hello,
during this weekend, I´ve dedicated most of my time into putting into practice my lasts commits regarding the changes to iMXRT driver and also getting running the TCP sender to a real time plotter. The result of the effort is a short demo of DC motor control uploaded by @acassis on NuttX YouTube channel. List of the new commits to pysimCoder that introduced TCP block, PID control and some other smaller changes can be found on NuttX wiki or pysimCoder wiki.
I had to make some changes into serRTScope.py programm in pysimCoder library so the plotter can support TCP data, the result can be found in my fork repository. There are still some changes to do, mainly on the graphic side, but it is a solid working example.
I did some tests of current sensing using ADC, although I am a little bit behind the schedule with that one. That is mainly caused by the implementation of PWM driver to iMXRT which was originally planned to take place during the last weeks of GSoC but was done during the previous week. But since iMXRT is the main platform target, I think it was right to make the implementation much earlier so the demos can be done with iMXRT based boards. This will make some free space during the next weeks where the current sensing can be finished.

Hello,
the fifth week of Google Summer of Code coding period was mainly about tickless mode support for iMXRT MCU. The source code can be found here . I still need to do some coding style changes before putting this to the mainline as well as some further testing. I run into some troubles with inaccuracies when I was using 32.7 kHz clock source as this frequency cannot be properly represented by CONFIG_USEC_PER_TICK. After discussion in NuttX mailing list, I switched to 16.6 MHz peripheral clock source, which divisions like 100 kHz or 10 kHz can be represented by CONFIG_USEC_PER_TICK. This change seems to fix the inaccuracies in the timer.
I also did some tests of ADC on iMXRT for current sensing and run into to problems when using multiple channels. There seems to be no DMA support available when using multiple channels, but I need to check my foundings with the chip´s reference manual and ADC driver source code. This might be crucial for the control of PMSM motors.

Hello,
my implementation of tickless mode for iMXRT MCU mentioned above was tested on real time DC motor control application and merged into mainline during the past week. A problematic pattern in my code and in STM32 tickless mode code has been later noticed by @ppisa and described in NuttX mailing list in detail. This problem does occur minimally as the overflow of the timer does not occur to often, but still should be prevented to happen. I plan to introduce a fix for both iMXRT and STM32, but firstly I need to do some tests of tickless mode with STM32.
After finishing the work on tickless mode, I started getting into the ADC support for iMXRT. As I mentioned last week, there are some problems when using multiple channels. It seems that sometimes the wrong channel is read and/or saved. The DMA support is missing in this case, but first option was to try avoid the problem by using multiple trigger control and read registers. That didn´t work out as only the first trigger register supports software trigger, the others support only hardware trigger. Althought this might not be a problem in the future as the ADC triggering should by done by PWM for the control of PMSM motor, it seems that using multiple channels with software trigger will need the DMA support.

Hello all,
during the last meeting, we discussed some changes to PWM and ADC drivers that would help the external application using them. All of them have already been merged to NuttX mainline. PR #4231 introduces ioctl command ANIOC_GET_NCHANNELS that returns the number of configured channels. This gives the applications the opportunity to be more flexible when it comes to multiple channel ADCs and they does not have to rely on user to specify the correct number of configured channels.
PR #4227 adds option to PWM drivers to prematurely leave the loops when -1 channel number occurs. This number can be used in applications at the end of channel list and indicate that all following channels are not used so the driver can skip them.
The changes that take the advantage of those updates are presented in pysimCoder PR NuttX: update PWM and ADC blocks with recently added NuttX functionalities.

Hello,
this is going to be the last week of my Google Summer of Code 2021 coding period. During this week I plan to present documentation for running NuttX with pysimCoder, which would be placed in Guides section. I will also create representative configurations for some boards, probably Teensy 4.1 and Nucleo F446RE, so they can be easily used with pysimCoder.
During this week, I would also like to finish an examle with PMSM and do a similar video as was done with DC motor last month. I am currently finishing external ADC triggering with iMXRT MCU, the progress can be watched in my forked repo. I´ve created Clarke and Park transformations blocks for pysimCoder which will be useful when it comes to PMSM control. There is still some optimalization tasks to be done before this gets merged into pysimCoder mainline, but it should be working.
My presentation about NuttX and pysimCoder has been approved to this year NuttX Workshop so I am looking forward to fully present to you the results of NuttX and pysimCoder colaboration in a few weeks.


Minor rephrasing of the lesson's description

Since we already said in the last lesson that bootstraps col-xs-* classes can be used on all form elements it sounds silly to repeat the exact same phrase in this lesson too.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

@kevindelsh Please review the Style Guide for Guide Articles.  The point of view should be second person.

Hey @RandellDawson, thank you for letting me know. Just made the edits. Please, let me know if there are other shortcomings.

Hey @RandellDawson, just made the required changes!

I approve of this PR's verbiage change and I have tested it locally to validate it displays correctly.

Thank you @kevindelsh for your contribution and congratulations on your first PR merge to this repo! 🎉
Hope to see more contributions from you in the future.


hasMany not assignable to field type 'upload'

Bug Report
hasMany does not seem to be assignable to to the field type "upload".
Expected Behavior
According to the docs (https://payloadcms.com/docs/fields/upload) hasMany should be available for the uploads field.
Current Behavior
Error: Object literal may only specify known properties, and 'hasMany' does not exist in type 'UploadField'.
Detailed Description
{
    label: 'Gallery',
    name: 'gallery',
    type: 'group',
    fields: [
        {
            label: 'Add images',
            name: 'galleryImage',
            type: 'upload',
            relationTo: 'gallery-images',
            hasMany: true,
        }
    ]
},

Hey @mo7orh3ad — this is actually just an error with the docs. Uploads are not meant to support multiple, but this could potentially be a future enhancement if you would find value out of it.
If you want to support multiple uploads, you could nest an upload field within an array field and that would also do the trick. That's what we do when we need data like sliders of images, galleries, etc.
Thoughts?

Hi @jmikrut, thanks for getting back - using an array field would have been my next approach. I agree, it would be great if this enhancement would find its way into a future release.

Docs have been updated. We'll keep this one open for now until we publish our roadmap—at which time we will be moving all enhancement issues to the Roadmap instead of tracking them here.


I put a test in there. (MAKES ERROR)

it wasn't being tested and i thought: Well... they need to fix this issue!
by the way: it creates a failed test.

i've got a different pull request coming up


Bower badge shows void instead of alpha

Actual result: "void"
Expected result: "v1.0.0-alpha7"
There's the v1.0.0-alpha7 tag: https://github.com/vaadin/vaadin-checkbox/releases/tag/v1.0.0-alpha7

Hi, this is for your package on pre-release version. (not stable version).
I've made a PR #1099 on it.
You can access it through /bower/vpre/vaadin-checkbox.svg  (BTW, on Bower, it is "v1.0.0-alpha6").

Seems like there is also a usability issue here. Instead of displaying void when there are no releases, we should display something more user-friendly, like no releases. @ritwickdey Maybe you could test that case in your pull request, possibly using a mocked server response, and add a fix.

Hi @paulmelnikow , I've made changes & added 9 tests (including for invalid packages). But Is it possible to test for this 'no releases' label ? beacuse if I test it from any real package, soon or later that package may get official release. That time, it test will be failed.

The way to accomplish that is using the intercept() method in your test. It lets you intercept the request that would be made to the server, and provide a fake response. Then the test doesn't hit the server at all! It's not perfect, since the fake response can get out of skew with what the real server would return, though it helps you test that your code is working as intended. There's some commentary in the service test readme and a working example in the cran tests.

Added 😄


Need advice on custom data with poor result

Hi,
Thank you for amazing work.
I have used instant-ngp, nerfstudio to generate mesh. However, sdfstudio impress me by mesh generation.
When I use sample data, I always get good render and mesh.
However, when I use custom data, results were always poor although I have done experiments and follow all discussions in this page.
Could you give me advice to process with this data: https://drive.google.com/file/d/1hLnwXon29bc4SiyuxiV32VAfQnZY2gTd/view?usp=share_link
As screen shot of above shared data like this:

The steps I have done as followings:

Used colmap to generate transforms.json file as usual in instant-ngp
Tested with instant-ngp, give a very good result (video 1 below)
Tested with nerfstudio by:
ns-train neus-facto --pipeline.model.sdf-field.inside-outside False --vis viewer instant-ngp-data --data D:\Hung\sdfstudio\data_cu\elephantNERFSDF\PNG_colmap
Give a not good render
I also use scripts ns-process-data, then render with nerfstudio, give a good result
used script process_nerfstudio_to_sdfstudio.py to convert from nerfstudio json file to meta_data.json file, and run with sdfstudio (neus-facto), got a very poor result (video 2).

I have checked very careful discussion in #2 (https://github.com/autonomousvision/sdfstudio/issues/2), and #49 (https://github.com/autonomousvision/sdfstudio/issues/49), but rendering result is very poor like #49.
Below videos are rendering with instant-ngp
Video 1: https://user-images.githubusercontent.com/110378166/222356933-3112bdb8-3c96-4c30-a516-fc3af3e88706.mp4
And rendering with sdfstudio
video 2: https://user-images.githubusercontent.com/110378166/222357045-c8175d1c-f59c-49db-82ab-1f9c5b81f6fa.mp4
The mesh I got from sdfstudio like this:

Highly appreciate with any help.

Hi, I don't have access permission to your data, could you update your link?

Hi, I don't have access permission to your data, could you update your link?

Thank you in advance @niujinshuchong , I have corrected the link. Please help download again.
Note that if I use ns-process-data and process_nerfstudio_to_sdfstudio.py, cannot see anything at rendering.

Hi, the main object in your scene is not centered after nerfstudio-data parser. You could try to add the code here https://github.com/autonomousvision/sdfstudio/blob/master/nerfstudio/data/dataparsers/nerfstudio_dataparser.py#L196 to roughly center the object
# center the objects
poses[:, 0, 3] += 1.0

And you could run with following command
ns-train volsdf --pipeline.model.sdf-field.use-grid-feature False --pipeline.model.sdf-field.hidden-dim 256 --pipeline.model.sdf-field.num-layers 2 --pipeline.model.sdf-field.num-layers-color 2 --pipeline.model.sdf-field.use-appearance-embedding False --pipeline.model.sdf-field.geometric-init True --pipeline.model.sdf-field.inside-outside False  --pipeline.model.sdf-field.bias 0.5 --pipeline.model.sdf-field.beta-init 0.1 --pipeline.datamanager.train-num-rays-per-batch 2048 --pipeline.model.background-model mlp --pipeline.model.near-plane 0.1 --pipeline.model.far-plane 2.0 --pipeline.model.overwrite-near-far-plane True --vis wandb --experiment-name volsdf-dtu106 nerfstudio-data --data  data/PNG_colmap/

I run it for 10k iterations and got something like this

Maybe you could try to tune the network architecture/batch size/image resolutions to get better results.

Hi, the main object in your scene is not centered after nerfstudio-data parser. You could try to add the code here https://github.com/autonomousvision/sdfstudio/blob/master/nerfstudio/data/dataparsers/nerfstudio_dataparser.py#L196 to roughly center the object
# center the objects
poses[:, 0, 3] += 1.0

And you could run with following command
ns-train volsdf --pipeline.model.sdf-field.use-grid-feature False --pipeline.model.sdf-field.hidden-dim 256 --pipeline.model.sdf-field.num-layers 2 --pipeline.model.sdf-field.num-layers-color 2 --pipeline.model.sdf-field.use-appearance-embedding False --pipeline.model.sdf-field.geometric-init True --pipeline.model.sdf-field.inside-outside False  --pipeline.model.sdf-field.bias 0.5 --pipeline.model.sdf-field.beta-init 0.1 --pipeline.datamanager.train-num-rays-per-batch 2048 --pipeline.model.background-model mlp --pipeline.model.near-plane 0.1 --pipeline.model.far-plane 2.0 --pipeline.model.overwrite-near-far-plane True --vis wandb --experiment-name volsdf-dtu106 nerfstudio-data --data  data/PNG_colmap/

I run it for 10k iterations and got something like this
Maybe you could try to tune the network architecture/batch size/image resolutions to get better results.

So wonderful!
Thank you for your help, @niujinshuchong
I will try to follow your guidance and update my result.

Hi, the main object in your scene is not centered after nerfstudio-data parser. You could try to add the code here https://github.com/autonomousvision/sdfstudio/blob/master/nerfstudio/data/dataparsers/nerfstudio_dataparser.py#L196 to roughly center the object
# center the objects
poses[:, 0, 3] += 1.0

And you could run with following command
ns-train volsdf --pipeline.model.sdf-field.use-grid-feature False --pipeline.model.sdf-field.hidden-dim 256 --pipeline.model.sdf-field.num-layers 2 --pipeline.model.sdf-field.num-layers-color 2 --pipeline.model.sdf-field.use-appearance-embedding False --pipeline.model.sdf-field.geometric-init True --pipeline.model.sdf-field.inside-outside False  --pipeline.model.sdf-field.bias 0.5 --pipeline.model.sdf-field.beta-init 0.1 --pipeline.datamanager.train-num-rays-per-batch 2048 --pipeline.model.background-model mlp --pipeline.model.near-plane 0.1 --pipeline.model.far-plane 2.0 --pipeline.model.overwrite-near-far-plane True --vis wandb --experiment-name volsdf-dtu106 nerfstudio-data --data  data/PNG_colmap/

I run it for 10k iterations and got something like this
Maybe you could try to tune the network architecture/batch size/image resolutions to get better results.

I wondered how you determined if the scene is centered or not.

This would fix the centering issue ("focus" method) https://github.com/nerfstudio-project/nerfstudio/pull/1543

@suptimq I manually checked the camera poses in the viewer with --vis viewer.  Thanks @f-dy for the suggestion. It would be great to have an automatic pose centering method.

I just submitted a PR.

Is this what the code looks like?


[web]: Support for backend proxy

On the traditional web frameworks such as Angular, React, and Vue, they tend to provide a way to automatically proxy requests to the backend. For instance, in Angular, simply providing a proxy.conf.json does the trick. All 3 seem to achieve this using an express server with a proxy middleware.
As of the moment, the flutter docs seem to hint that the only way is to allow CORS on the server-side. While this is doable, it still is not as pretty as it requires you to put a CORS-during-dev condition on the server.
Is this feature on the roadmap for the stable release?
$ flutter --version
Flutter 1.14.6 • channel beta • https://github.com/flutter/flutter
Framework • revision fabeb2a16f (4 weeks ago) • 2020-01-28 07:56:51 -0800
Engine • revision c4229bfbba
Tools • Dart 2.8.0 (build 2.8.0-dev.5.0 fc3af737c7)

P.S.: I'm also interested in contributing to flutter, so if the team sees this fit to be prioritized, please guide me accordingly!

Hi @devcsrj - there are no plans to implement this feature anytime soon, but I would certainly review a patch that added this functionality to the flutter tool.
I would consider introducing this as a flag to flutter run, perhaps --web-proxy-server ? (Taking other suggestions for names). This would live alongside the other web specific flags in the tool, like --web-hostname: https://github.com/flutter/flutter/blob/b34046903b527ed401ff84c23651680593bea86f/packages/flutter_tools/lib/src/commands/run.dart#L348
The second change would be to update the development server (https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/build_runner/devfs_web.dart#L53) to consume this option and perform the proxying of requests.

I would consider introducing this as a flag to flutter run, perhaps --web-proxy-server

Sounds good to me!
Another thing to consider though - the npm-based middleware is flexible, as it supports proxying only certain paths, path rewrites, web sockets (and SSE, I think). While a command-line flag is enough for my use case as of the moment, I'm not exactly sure how many users require the above flexibility. Might get unwieldy (or become too limiting) when implemented as a flag.
Just additional notes to consider!

If the function is dead ,To debug web app is just a JOKE!

The designers of flutter without any experience of web devleopment ,So the function is very important for debug web app

Anything new about this case? I am really looking forward to get a backend proxy for web.

I was able to serve both my flutter web app and another server on the same port using a proxy server in nodejs.
proxy.js
const express = require("express");
const { createProxyMiddleware } = require("http-proxy-middleware");

const EXT_PORT = 801;

const app = express();

app.use(
  createProxyMiddleware({
    changeOrigin: true,
    target: "http://localhost:8000", // shouldn't matter
    router: {
      [`localhost:${EXT_PORT}/api`]: "http://localhost:8081", // API on 8081 should support /api/* paths
      [`localhost:${EXT_PORT}`]: "http://<IP_ADDRESS>:8082" // everything else will be proxied to flutter on 8082
    }
  })
);

app.listen(EXT_PORT, () => {
  console.log(
    "Server listening on: " +
      EXT_PORT +
      "\nRun flutter with: flutter run -d chrome --web-port 8082 --web-hostname <IP_ADDRESS>"
  );
});

In this example, open browser on http://localhost:801
Calls to http://localhost:801/api/* will be proxied to the backend

Any nginx configuration is easier than write yourself a proxy server

Any updates about this topic, as it is extremely important for WEB development process to be able to send the cookie with each request to any public URL.

I noticed that this issue is still open. I am new to flutter web development so I was surprised that there is no easy way to proxy calls made to the backend. The surprise is motivated by the fact that any web developer knows how CORS is problematic to deal with during development, so it sounds strange not so much that a web framework such as flutter 2.0 is is missing this feature but that there is no plan to implement it.
Out of curiosity, is there a way that doesn't involve a flutter-level proxy but instead some configuration (on retrofit, for example)?
My issue with the proxy shared by @elisherer is that I am still having CORS issues because I run flutter on a port and the proxy on another. Is there a better way to do this?

I had to write my own little node proxy server using the http-proxy-middleware. A bit wasteful if every team needs to do it themselves.

Also, the problem with the backend proxy is debugging, because original flutter app running on another port, hot reload is not working on proxied app.

I've made a example patch for /packages/flutter_tools/lib/src/isolated/devfs_web.dart which routes all traffic from the devservers /api path to https://example-api-service.com/
corsproxypatch.patch
Apply the patch using
PATCH=pwd/corsproxypatch.patch; (cd dirname $(which flutter)/../; git apply $PATCH --verbose); rm dirname $(which flutter)/cache/flutter_tools.stamp; flutter precache;
Remove the patch again using
(cd dirname $(which flutter)/../; git checkout HEAD --progress -- packages/flutter_tools/lib/src/isolated/devfs_web.dart)

@tecteun – that's an AMAZING work-around.
I really want CLI support for this. Will look into it soon!

Cool! Yes, would be really nice to have this in the CLI, tried to implement it, but ran into issues trying to run the middleware handler  in a deferred isolate, so it could be individually configured for each program in a project local .dart file. (I really don't know what would be the best pattern for local configuration in combination with flutter/dart)

@tecteun Maybe open a PR for this ?

If only CORS is your issue, you can apply the flutter run argument --web-browser-flag=--disable-web-security.


Fix argument list too long in manage controller

What type of PR is this?

/kind cleanup
What this PR does / why we need it:
Fix argument list too long in manage controller in https://github.com/kmesh-net/kmesh/pull/679
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

An alternatrive maybe make these functions as a method of KmeshManageController, tehn you donot need to pass these args

This seems to be more reasonable

@hzxuzhonghu Please review


Homepage

Help to read my code and leave comments! thank you.
I will be focusing on the legend for easier navigation next sprint.

Rmb to pull from master first as your's is not updated (i can see the old version of top toolbar)


Face detection doesn't work probably on IOS

this is warning. the image taken from camera with selfi cam.
WARNING]The specified colorspace format is not supported. Falling back on Libyuv.

Facing the same issue

Hi guys, sorry for the delay. Thanks for using our plugin. @bharat-biradar and I have been maintaining this plugin, but sometimes we cannot provide all the support you need. Both of us are busy with school, work and family. We created this plugin as an open source project. We do not have an ETA for this fix, too busy with so many things, but you are welcome to fork our repo, fix whatever is broken and sent the PR. We will review PRs as soon as possible and release a new version.

Hello Guys !
pls check it. It is working well
https://stackoverflow.com/questions/73292337/flutter-google-ml-kit-plugin-facedetector-not-working-in-iphone-cameras

Use ImageFormatGroup.nv21 for Android and ImageFormatGroup.bgra8888 for iOS as in this example.
In this comment: https://github.com/flutter-ml/google_ml_kit_flutter/issues/287#issuecomment-1549828057
Someone reported that the native apps are using that for MLKit and when doing the same in Flutter solved the issue for Android. That was merged in this PR https://github.com/flutter-ml/google_ml_kit_flutter/pull/454. Update to the latest plugin version.


Retry on Expectation Failures

Background
PactumJS supports retry mechanism where an user can define when to retry (strategy), how many times to retry & the delay between retries.
await pactum.spec()
  .get('/some/async/operation')
  .retry({
    count: 2,
    delay: 2000,
    strategy: ({res}) => { return res.statusCode === 200 }
  })
  .expectStatus(200);

Description
Enhance the retry mechanism to retry when there are expectation failures.
Retry on expectations failure
If the endpoints returns a status code other than 200, PactumJS should retry the API request.
await pactum.spec()
  .get('/api/endpoint')
  .expectStatus(200)
  .retry();

The retry logic should apply for other expectation failures as well.
Support multiple options in retry() method
Retry with default options
retry()

Retry with a custom retry count
retry(3);

Retry with a custom retry count & custom delay
retry(3, 5000);

AC

PactumJS should retry on expectation failures.
Add tests.

Hello @ASaiAnudeep could you assign this issue to me


feat: Generate code explanations on selected text

What is this?
Today we have code refactoring on selected text, but we should really provide explanations of that code along with the refactoring.
Another option
General explanations of selected code would also be a welcomed addition to our feature set.
The davinci model would be leveraged for this.
https://platform.openai.com/examples/default-explain-code

We'll be having a dropdown to maintain extensibility of the features.

We'll be having a dropdown to maintain extensibility of the features.

This is the ideal path @Anush008


Stay in touch form is just a dummy

[x] Store user's info
[ ] Change button's text when it's clicked
[x] Display a confirmation message
[ ] Check if the email is already register

The form is going to be based on the Mautic open source platform.
A working form is added to this commit f1f70ddeca352f2d2addab4cccac88a4f000bfec which stores the data in the Mautic platform.

We need to investigate if the Mautic platform has a feature to check if an email address is registered.


Unexpected normalization: a.b.com gets protocol

normalizeUrl("a.b.com"); // expected a.b.com, got http://a.b.com

Default for stripProtocol is false, but i didn't expect it to add a protocol for me - esp when other urls don't do that

ah maybe i just misunderstand how normalization is supposed to work, guess it adds a protocol if one isn't present?


Adding Alerting Comments and Correlation Alerts system indices

Description
Adding Alerting Comments and Correlation Alerts system indices to SecuritySettingsConfigurer.
To be backported to 2.15 and 2.16.
Separate PRs within our respective Alerting and Security Analytics plugins are being raised to update getSystemIndexDescriptors(), which will cover the >= 2.17 cases of allowing these indices to be registered in Security as system indices.
Issues Resolved
[List any issues this PR will resolve]
Is this a backport? If so, please add backport PR # and/or commits #, and remove backport-failed label from the original PR.
Do these changes introduce new permission(s) to be displayed in the static dropdown on the front-end? If so, please open a draft PR in the security dashboards plugin and link the draft PR here
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] New Roles/Permissions have a corresponding security dashboards plugin PR
[ ] API changes companion pull request created
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@toepkerd This list has been made redundant in 2.17. The security plugin can now determine if a request matches system indices directly from a registry of system indices from the core: https://github.com/opensearch-project/security/issues/4535
Plugins can register system index patterns through the SystemIndexPlugin.getSystemIndexDescriptors extension point
Example from this repo: https://github.com/opensearch-project/security/blob/main/src/main/java/org/opensearch/security/OpenSearchSecurityPlugin.java#L2090-L2098

Closing as the list is redundant with a 2.17 change


Update Atlassian documentation link

As per discussion in https://github.com/github/github-services/issues/1145#issuecomment-209806132

ping @mikemcquaid: CLA signed, and travis green

@glasnt Thanks for your contribution! You rock!


Add notification in renderer if lens protocol handler fails to find any routes

Signed-off-by: Sebastian Malton<EMAIL_ADDRESS>fixes #2747
Some screenshots:

Those logs I assume are in main, so that is expected.
As for the renderer side, sure good idea.

As for the renderer side, sure good idea.

I guess it's not actually a failure to find a route, but from the user's perspective it's the same thing: no navigation, and no failure notification.

I think you are confused by the log line. What it is reporting is that it cannot find a handler for the route lens://app/cluster/minikube on the main side.
On the renderer side it does find a handler and you should see a log line there saying:
[APP-HANDLER]: cluster with given ID does not exist { clusterId: "minikube" }

Yes, see above


idf.py: error: too few arguments (IDFGH-756)

I read the installation instructions are my steps, proper installation of esp-idf-tools-setup-1.2.exe, I set environment variables, PySerial, future, Cryptography, in python2.7 and response to command idf.py menuconfig is
idf.py: error: too few arguments.
I only have python27 installed on my system, vs code and esp-idf-tools-setup-1.2.

@AGPisland Could you help share if any updates for this issue? Thanks.

Hi @Alvin1Zhang  unfortunately, i wasn't able to make the idf.py work properly; i think i may have misconfigured the build environment. Becouse of the upcoming due date on my project, I have decided to work with micropython, and if that doesn't work, i'll go back to idf.py

Hi there!
I wish to re-open this issue.
Win10;
Toolchain installation instructions for windows 10 (CMake version);

Issue reopened.

I did some more digging into the issue and I believe the problem is with the argparse usage. I haven't been able to figure out where exactly but here's what I did to check it:
I opened idf.py and made the actions argument optional and passed a default value "all".
This led to a KeyError indicating it couldn't find the key "a" in ACTIONS. I realized that it was only taking the first character of default value I gave and therefore duplicated some keys with names having single character.
After doing this, it went ahead with compilation but stopped for another irrelevant bug for which I would open a separate issue.

At the moment, I have got reasons to believe that native Windows compilation is far from finished. WSL still works fine for me and I was just trying this out of curiosity and I'm really looking forward to good windows support.

Hi @souryavarenya,
Glad you found a workaround for now.
If you are still set up to reproduce the Windows situation, can you please let me know:

Are you use Windows Command Prompt or some other terminal?
If you run python %IDF_PATH%\tools\idf.py --help or python %IDF_PATH\tools\idf.py menuconfig, does this work?
What is the output of python --version?
If you type ftype | findstr -i python, what does it show? (context)

Thanks,
Angus

Hello @angus,
Here are the details you requested:

I was using CMD when this error occurred. Powershell throws the same issue.
Yes python %IDF_PATH%\tools\idf.py --help (or python $env:IDF_PATH\tools\idf.py --help in PowerShell) works. I still wonder why it's different from directly calling idf.py --help
The issue is the same, both with 2.7 and 3.6. Tried both.
Here's what it shows as of now. I don't suspect any issue with the file type associations.

C:\Users\varen>ftype | findstr -i python

Python.ArchiveFile="C:\WINDOWS\py.exe" "%L" %*
Python.CompiledFile="C:\Python27\python.exe" "%1" %*
Python.File="C:\Python27\python.exe" "%1" %*
Python.NoConArchiveFile="C:\WINDOWS\pyw.exe" "%L" %*
Python.NoConFile="C:\Python27\pythonw.exe" "%1" %*

From what I am able to catch here, calling the python script directly (idf.py menuconfig) is causing trouble while python %IDF_PATH%\tools\idf.py menuconfig is working fine. Seems like just a small issue with the way cmd/powershell/windows treats arguments passed by directly calling the python script.

As I concluded on my previous comment, I have been able to isolate the issue to the way these commands are treated in CMD/PowerShell/Windows. I have done this my making an argparse test script and it throws the same issue when test.py my_args is used, which otherwise doesn't show up while executing python test.py my_args.

Hello,
After some more research, I have found no solution to this issue, which seems to be due to the way argparse works with windows.
Here's a StackOverflow thread that talks about this exact issue but in the solution suggests that it could be due to an incomplete setup of Python on Windows. There's no further progress from here.
This thread here talks about not including python before the script name. My sample python scripts run without having to prefix python in the command with an exception of argparse. So the described problem is not what I am facing, although I have also tried the following:

Added .PY in the global PATHEXT variable
Checked for file associations and have tried both 2.7 and 3.4

I guess this is the end of the road for this issue.

UPDATE: idf.py somehow works now when used from PowerShell, unlike before where it used to throw the error. It still doesn't work with CMD however.
Amidst this bizarre exploration, I find myself totally unsure of what might have got this to work. (I am guessing it could be because of the PATHEXT variable)

I guess this is the end of the road for this issue.

From our point of view, we'd like idf.py to work for all Windows users. So it would be good to figure out what the root cause is here. Although you're not obliged to keep helping us, of course. :)
Windows Command Prompt runs idf.py fine on my Windows machine (standard Python installation), and colleagues' Windows machines. So there is some particular Windows configuration which is breaking it.
If you run the assoc command as mentioned here, do you see anything unusual? There should be something like .py=Python.file in the output.
A second thing, if you have a test Python program that uses argparse can you please put the following code in it and see what it says:
import sys
print(repr(sys.argv))

... this will show us exactly what command line arguments are being passed to the python interpreter.
Here it is on my machine (also running idf.py clean in the wrong directory, to prove argparse can work!)

Hi Angus,
I can't express how much I appreciate your efforts in addressing the community with such diligence. Your suggestions have helped me resolve this bit of the issue finally.

Here's what it shows up on checking the associations:

Safe to conclude that the issue isn't with this.
The second test you suggested is what takes us ahead and has links to this issue and the given solution works. The issue is indeed with the argument-handling in CMD and how a python registry dictates its functioning.
It's also important to understand the root cause of this issue and one of the comments on the above SO thread suggests the follows:

On a side note: The root cause of this might be due to an initial file association with .py files prior to the Python install.  On Windows 10 BTW. – g4m3c0d3r May 24 '16 at 22:32

The issue is potentially because of an improper/overlapping installation or association of .py files.

To consolidate the solution for the visitors in future, here it is:

[x] Check in system path if the desired Python directory is present there in the highest order
[x] Uninstall irrelevant Python installations that came bundled with anything else
[x] Check the associations of ,py files. More info here.
[x] Add .PY to PATHEXT global variable
[x] Check the registry entry to be as follows in order to accept arguments. More info here.

NOTE: The directory would depend on the default installation of python being used or even the OS itself.

This issue can be closed now!

@souryavarenya Thanks for the comprehensive explanation. I'm glad you figured this out!
It's unfortunate that because our entry point is in Python it's not easy for us to check any of this at runtime to provide helpful hints (chicken & egg problem). This is a very useful reference for anyone who runs into this in the future, though.


Project environment

Hi, should we create a separate .yaml file with project dependencies? I think it would be required if someone wants to run the project later on.

I'm fairly certain that this will be a part of the later requirements of the project. I believe we are going to use docker to do this.

The environment file with all dependencies has been added. Regardless of if its needed it will be nice to have, ensuring everyone can run all scripts.


feat(websocket): add ws instrumentation

Added ws instrumentation to incoming messages.
Upgrade epsagon version.

Please update readme here and in the node one

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update the 1.4 release docs

Merge master into the release-1.4 branch so that the 1.4 docs are up to date after we release 1.5

/override dco

/lgtm

/approve


[RFR] Correctly handle Sass units in _variables.scss

What does your change do? Also thanks for helping me out

It does nothing in particular. It simply handles Sass units the way they should be.


Simulated characteristics monitoring

Extracting change requests to separate issue and merging.

We wait for [example](https://github.com/Polidea/FlutterBleLib/pull/283 to be merged to develop and then we will merge develop to blemulator


Idiot's guide for installation & use?

Is there a novice's guide for installation & use? Or is someone willing to take me under their wing?

Following, I have tried the step by steps, but no luck ...


⚠ GLDDNS Server (ns2.glddns.com) has degraded performance

In 396b134, GLDDNS Server (ns2.glddns.com) (ns2.glddns.com) experienced degraded performance:

HTTP code: 200
Response time: 491 ms

Resolved: GLDDNS Server (ns2.glddns.com) performance has improved in adb311d after 7 minutes.


[$150] Web - Workspace - Invite new members" field is not focused

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: 9.0.0-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:

Log in to an account
Go to workspace(Or create one) > Members
Click on the "Invite member" button at the top. Notice the field is focused
On the Invite members page click on the Question mark button to go to the "Get assistance"
Click back to return to the Invite Members page

Expected Result:
Invite members page field is focused
Actual Result:
The invite members page field is not focused
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
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/f1c864c8-e283-4738-ba75-83cf8967f78a
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01bda364df69d71d2a
Upwork Job ID:<PHONE_NUMBER>395622118
Last Price Increase: 2024-06-24
Automatic offers:

tsa321 | Contributor | 102885241

Issue OwnerCurrent Issue Owner: @rushatgabhane

@adelekennedy  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Proposal
Please re-state the problem that we are trying to solve in this issue.
Web - Workspace - Invite new members" field is not focused
What is the root cause of that problem?
Because of the newly added focusTrap and the Workspace_Invite screen isnot included in, SCREENS_WITH_AUTOFOCUS
https://github.com/Expensify/App/blob/b021195b864211efbaaefe188226b2830b91b7d8/src/components/FocusTrap/FocusTrapForScreen/index.web.tsx#L51-L55
What changes do you think we should make in order to solve the problem?
We should add the Workspace_Invite screen in SCREENS_WITH_AUTOFOCUS

I can reproduce, and while this is a small bug I think it's worth it to fix

@rushatgabhane already three proposals above to review

@rushatgabhane PR is ready

It looks like this was deployed to prod on the 15th and payment is due!

Payouts due:

[ ] Contributor: $150 @tsa321 (Upwork)
[ ] Contributor+: $150 @rushatgabhane (NewDot)

Do we need a regression test here @rushatgabhane?

@adelekennedy this was caught by QA so I don't think we do. And it's a very minor edge case bug.

$150 approved for @rushatgabhane


mindustry: 141.2 -> 142

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Your maintainer entry should be added in alphabetical order

Please squash the commits

Sorry for delay, squashed

I'm not sure why the bot tried to backport this to 22.11?

This doesn't need to be backported to release-22.11 because it already was: https://github.com/NixOS/nixpkgs/pull/220024
If release-22.11 really needs a mindustry update, it would be https://github.com/NixOS/nixpkgs/pull/225703 142 -> 143.1 and then https://github.com/NixOS/nixpkgs/pull/233553 143.1 -> 144.3

But release-22.11 probably doesn't need a mindustry update because 22.11 is only supported for another two weeks

release-23.05 is at 143.1 and master/unstable is at 144.3.  If any backports are needed, it would be https://github.com/NixOS/nixpkgs/pull/233553 143.1 -> 144.3 into release-23.05
144.3 is currently the latest upstream release.

The same happened in https://github.com/NixOS/nixpkgs/pull/235817#issuecomment-1589767924
Maybe it's a bug in the bot: when labels are updated it runs again, cc @Janik-Haag


Add unshare to podman

This command lets the user run a command in a new user namespace like unshare -u.
It uses the implementation of unshare in buildah. ( fixes #1388 )

/ok-to-test
/approve

Hi @weirdwiz, thanks for the contribution!
I did not check the code yet but we also need to add a man page and bash completions for the new command.

Need update commands.md

Would be nice to have some tests too if possible

I see I'll add the man pages, bash completions and update the commands.md
Sure @rhatdan I'll make some tests.

we need to re-use the unshare implementation of Podman, where we join the existing namespace if it already exists.  This should happen automatically if you just implement unshare to setup the shell or execute the specified command without caring of setting up the userns.

We still need to add tests.

@vrothberg yes I'm currently working on the tests and bash_completions.

Needs a rebase to get the SELinux fixes.

The unshare-specific test seems to be failing, and I'd like a head nod from @giuseppe - but otherwise this seems good to go.

Might push this to 1.4 so @giuseppe can give an ack

Rebased

I have no idea why this is failing, and the logs seem to be useless.
You might need to add
podmanTest.CgroupManager = "cgroupfs"
podmanTest.StorageOptions = ROOTLESS_STORAGE_OPTIONS
But I am not sure.
@giuseppe @baude PTAL
These tests pass for me when run locally.

we should disable the tests when running as remote with SkipIfRemote().
@weirdwiz can you please take care of it?

@giuseppe I have added SkipIfRemote()

could you please rebase?

tests are happy.  LGTM

Nice work, @weirdwiz!
/lgtm


Chore: Update walletconnect sdk

Description
Received message that our wallet-connect sdk is outdated.
this means the @walletconnect/client (deprecated)
Since documentation explains that to migrate from 1 > 2 is implementing the @walletconnect/web3wallet (we already do)
I believe the work is basically getting rid of v1 implementation.

[ ] - remove v1 flow
[ ] - verify if any functionality is not yet migrated over

Im closing this as it was badly looked into, and only requires a bump of @walletconnect/web3wallet


必须要php8.1才能运行吗？能不能向下兼容下

7以上或者5.6以上

7以上或者5.6以上

最低要求php8.0。要向下兼容的话你可以fork下来去掉强类型应该就可以了。

不会啊

不会啊

hi, 目前已经向下兼容至php7.4。

Your requirements could not be resolved to an installable set of packages.
Problem 1
- haozi-team/chatgpt-php[1.0.0, ..., 1.5.3] require php >=8.0 -> your php version (7.4.33) does not satisfy that requirement.
- haozi-team/chatgpt-php[1.6.0, ..., 1.7.0] require guzzlehttp/guzzle ^7.2.0 -> found guzzlehttp/guzzle[7.2.0, ..., 7.5.0] but it conflicts with your root composer.json require (~6.0).
- Root composer.json requires haozi-team/chatgpt-php * -> satisfiable by haozi-team/chatgpt-php[1.0.0, ..., 1.7.0].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require haozi-team/chatgpt-php:*" to figure out if any version is installable, or "composer require haozi-team/chatgpt-php:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Your requirements could not be resolved to an installable set of packages.
Problem 1 - haozi-team/chatgpt-php[1.0.0, ..., 1.5.3] require php >=8.0 -> your php version (7.4.33) does not satisfy that requirement. - haozi-team/chatgpt-php[1.6.0, ..., 1.7.0] require guzzlehttp/guzzle ^7.2.0 -> found guzzlehttp/guzzle[7.2.0, ..., 7.5.0] but it conflicts with your root composer.json require (~6.0). - Root composer.json requires haozi-team/chatgpt-php * -> satisfiable by haozi-team/chatgpt-php[1.0.0, ..., 1.7.0].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions. You can also try re-running composer require with an explicit version constraint, e.g. "composer require haozi-team/chatgpt-php:*" to figure out if any version is installable, or "composer require haozi-team/chatgpt-php:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.

guzzlehttp冲突了

唉


Update diag_backup.php

cant download with turkish..

Please send Pull Requests on branch master, and then we can cherry-pick them

Closing per @rbgarga


pydeck widgets not show up

Environment Information
Mac M1 chip
followed GEE tutorial #37 How to use Earth Engine with pydeck for 3D terrain visualization
view_state = pdk.ViewState(
    latitude=36.15, longitude=-111.96, zoom=10.5, bearing=-66.16, pitch=60
)

r = pdk.Deck(layers=[ee_layer], initial_view_state=view_state)

r.show()

Description
I already followed your instruction to create a new conda environment and install the needed package but still get this problem

the detail in the red box:
Failed to create view for 'JupyterTransportView' from module<EMAIL_ADDRESS>with model 'JupyterTransportModel' from module<EMAIL_ADDRESS>TypeError: Cannot read properties of undefined (reading 'length')
at n.updateTooltip (http://localhost:8888/nbextensions/jupyter-js-widgets/extension.js?v=20230111103133:2:766603)
at n.initialize (http://localhost:8888/nbextensions/jupyter-js-widgets/extension.js?v=20230111103133:2:765694)
at n.value (http://localhost:8888/nbextensions/pydeck/index.js?v=20230111103133:18:454591)
at new t.View (http://localhost:8888/nbextensions/jupyter-js-widgets/extension.js?v=20230111103133:2:248055)
at new C (http://localhost:8888/nbextensions/jupyter-js-widgets/extension.js?v=20230111103133:2:755696)
at new k (http://localhost:8888/nbextensions/jupyter-js-widgets/extension.js?v=20230111103133:2:763285)
at new O (http://localhost:8888/nbextensions/jupyter-js-widgets/extension.js?v=20230111103133:2:764935)
at n. (http://localhost:8888/nbextensions/pydeck/index.js?v=20230111103133:18:454155)
at new n (http://localhost:8888/nbextensions/pydeck/index.js?v=20230111103133:18:454303)
at http://localhost:8888/nbextensions/jupyter-js-widgets/extension.js?v=20230111103133:2:742192
and the detail in the chrome console said:

the bug has stuck me for several hours. do you have any ideas of how to solve this?
Best Regards

This is a pydeck issue rather than geemap. Try running some examples from https://pydeck.gl/. If it does not work, then it is a pydeck problem.
Also, the pydeck earth engine package no longer works. See https://github.com/UnfoldedInc/earthengine-layers/issues/133. It is not something that can be resolved by geemap. Don't waste your time trying this.

ok, thank you for the reply


Datetime Conversion

I believe Autotask API is returning all time data in EST or EDT, and the python-atws is converting it to UTC.
I'm not sure if there have been recent changes to the code but seems like the script doesn't respect daylight savings.
For example:
I have a ticket opened on 04/21/2020 12:24 PM(PDT) but after the conversion to UTC I'm getting 2020-04-21 20:24:24 (GMT), where it should be 2020-04-21 19:24:24 (GMT).

This is handled by just a few functions:
https://github.com/MattParr/python-atws/blob/6515a193d88009f97cf61f6bba52730bf594aaa4/atws/constants.py#L9-L15
https://github.com/MattParr/python-atws/blob/6515a193d88009f97cf61f6bba52730bf594aaa4/atws/helpers.py#L154-L174
I don't know if anything has changed on the Autotask side.
I should have made the wrapper default to UTC and allow setting a local time zone if desired.
However I didn't.
The conversion is correct.  My tracing of these times in a world gantt view looks like what you have said is happening.
PDT 1224 -> EST 1424 -> London 2024
Why do you think it should come out an hour earlier?

You are right, the conversion is correct. I just thought you were converting to UTC, no I know its LOCAL_TZ='Europe/London'. Thanks for the update.


rip  info return error

Good day  Mr ebaauw   ,
I have   a issue configuring  home bridge -rpi  on my  local raspberry .
$rpi info return this  :
pi@homebridge:/var/lib/homebridge $ rpi info
rpi info: error: /sys/class/leds/PWR/brightness: cannot open: ENOENT no such file or directory
the file PWR does not  exist  . I have  a  Pi 3B .
Can you pleas help ?

See #157

thks  you  very much for your reply .

On 7 May 2023, at 13:38, Erik Baauw @.***> wrote:
See #157 https://github.com/ebaauw/homebridge-rpi/issues/157
—
Reply to this email directly, view it on GitHub https://github.com/ebaauw/homebridge-rpi/issues/160#issuecomment-1537431659, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7TKAUSYQRE4X5ON2HX574DXE6JT3ANCNFSM6AAAAAAXYWFCG4.
You are receiving this because you authored the thread.


Last version 2.5.0 often crashes with huge memory usage

Hi
in the past AbracaDABra worked without any problems, neither with the RTL-SDR dongle nor via rtl_tcp. System = Windows 11.
But since the last update to 2.5.0 often the Windows freezes with "no memory available", although my system has 16 GByte. (Intel i9 on a Lenovo Tiny PC) . The last time I saw this I could see via task manager, that the AbracaDABra consumed nearly 30 GByte of memory that caused the Windows to swap the memory on the SSD and then to crash.

That is very bad, thanks for reporting.
For sure I do not have this problem on macOS and nobody else has reported it so far. I have few questions:

How long does this take to happen? Is it after hours of listening or within tens of minutes? Could you please try to monitor memory consumption from the start? Does it start to grow immediately? I do not have W11, but on Windows 10 it uses typically < 200MB.

Are there specific steps to reproduce this behaviour?

Does it happen with all ensembles of with specific one?

Could you please try to disable SPI application is setting to see if it still happens.

I can't confirm it. In the past days I was working on Win 11 for several hours without problems.

I am afraid there is some hidden problem on W11, issue #136 was also reported by one user while other stated it does not happen.

It seems to happen for all ensembles  and in the mode with USB SDR dongle directly or using rtl_tcp on an raspberry remotely.
If you could share the deployment version I would try it again.

I can share the development version by email. I do not want to make it publicly available yet. My email address is in About dialog of the application.

I wrote you an email.
Regards

Lasted development build shared, please report the status here.

Thank you. I am now several days not at home, I will test it when l'm back.Regards Friedhelm Von meinem iPhone gesendetAm 04.07.2024 um 08:51 schrieb KejPi @.***>:
Lasted development build shared, please report the status here.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

The problem is still there. Even the fixed version is still running after closing the application and consuming 10 GBytes of memory, and raising and raising. To prevent that the PC crashes I killed this process with the tast manager.

Thanks for the test.
Unfortunately I do not know how to fix it because I cannot reproduce any problem under Windows 10.
This is how it looks like on Windows 10 after 7 hours of continuous reception:

What was the last working version?
Can you disable SPI application to see if it happens too?

What is the " SPI application" ?

It did not help. As long as Abracadabra is running, everything is fine. After closing it the foreground process (mentioned as "App") in the German windows is running fine, using only about 80 KByte. After closing the app it becomes a background process using more and more memory.

https://github.com/KejPi/AbracaDABra/assets/84860874/47302ed9-2248-471e-bb89-1ac6037ded46

The official and you developer version behave the same way, but the developer version has an additional bug: It often does not start or it takes about 10 seconds to start. the official last version starts immediately, but both a suffering from this memory consuming zombie process after stopping the application.

OK, so we finally move forward. So to sum it up: Application runs without problems but when yoiu try to stop it, it is not stopping but instead it keeps running and eating memory. But the window disappears, correct?
And the problem happens when you decode from RTL-SDR USB stick directly connected to W11 PC as well as when application processes data from RTL-TCP source, correct?
Could you please try to make some recording and then try to play the recording and exit the application while it plays from the recorded file? Is the problem happening too?
Windows 11 behaves somehow inconsistently - there was another user stating that official version starts exteremly slowly
(issue #136) while it was fixed by development version :-(

Yes, you are right, the windows of the application closes correctly, but often, not always, this "zombie" will be created. Therfore, the first time I saw this I had started Abracadabra, then stopped it, did sonething different, started it again and then when the PC crashed I did not recognize, that the problematic background process is not caused by the actual running process but by the process started and stopped BEFORE. See this example in the screenshot: I started Abracadabra, stopped it, stated it again and you can see zombie and the running app in parallel. And of course you might think, the background process WAS the child process of the application, but is is not. It came from the last time before Abracadabra was running. But obviously this does not happen using the dongle directly, only with the tcp method. Using the dongle direct method the process becomes a background process and then it dies correctly. I tested it now several times.
Because I often switched between with dongle and with tcp I THOUGHT it would happen in both cases, but OBVIOUSLY the zombie was created in THOSE cases I started it with tcp_rtl. After terminating you can not distinguish how the process was started simply with the task manager.
Example: Zombie and app running in parallel.

Another interesting information, thank you! This narrows the problem. What was the last version working correctly?

The same behavior, using tcp_rtl the zombie is created after stopping the application.  Where do you have older versions to check when the problem started?

This is strange, I was somehow able to reproduce the issue on company laptop with Windows 10 and in high CPU load condition (but not on my build machine) and after the fix I did, I am no longer able to reproduce it. I was able to track the issue back to 2.3.5 so it is there for very long time. I have also fixed the the issue that app was sometimes not starting.
Older versions are available on Github release page (https://github.com/KejPi/AbracaDABra/releases)
Maybe I did a mistake when building the app, I will share updated build, if this is not helping then I do not know what to do next. I will check again on Monday.
If you have MinGW shell (or any terminal application that shows the output log), you can try to run the app from that shell to see the output log. In the case of zombie I saw endless output of single errror message.

Now it works perfectly.  :-) I tested both modes: tcp_rtl and dongle USB mode. Both is working. And the application seems to start much quicker and needs less memory during running: only about 45 MByte in case of tcp_rtl and about 55 Mbyte in case of USB dongle mode.

That's a good new finally! Thanks for your feedback. I am closing the issue.


screenshot for app main window only

I am working on a project that use Appium-for-mac for automation as well as screenshot comparison against base images (using a tool called Applitools Eyes). Current screenshot implementation makes this impossible because it takes the whole screen. Any machine change or background windows change will fail the image comparison test.
Without making my app full screen or apple Scriptable, I tried a different implementation that will take screenshot of the app windows only, using CGWindow API. This is a caveat, I also lose the ability to take screenshot of the menu.
Would you be willing to take a look?
https://github.com/fangmobile/appium-for-mac/tree/appOnlyScreenshot
Any feedback and suggestions?

in which release I can get the fix, I am using beta3 release of AppumForMac, but still get the screenshot of full screen. Thanks!


newspaper.build(...) error

Hi,
I'm new to python and I don't know how to fix this.
Traceback (most recent call last):
TypeError: get_request_kwargs() missing 1 required positional argument: 'headers'
  File "/usr/local/lib/python3.5/dist-packages/newspaper3k-0.2.2-py3.5.egg/newspaper/mthreading.py", line 38, in run
    func(*args, **kargs)
  File "/usr/local/lib/python3.5/dist-packages/newspaper3k-0.2.2-py3.5.egg/newspaper/network.py", line 105, in send
    self.resp = requests.get(self.url, **get_request_kwargs(self.timeout, self.useragent, self.proxies))
TypeError: get_request_kwargs() missing 1 required positional argument: 'headers'

Can someone help me please?

Hey @GitHubSuperHero, this was a bug that happened last night for one hour - i have since pushed a fix.
can you please uninstall and reinstall newspaper3k?
pip uninstall newspaper3k
pip install newspaper3k

If you are using master, please pull the latest commits with
git pull

I solved the problem using
pip3 install git+https://github.com/codelucas/newspaper.git
Thanks codelucas


IPClaim is associated with incorrect IPPool when multiple IPPools exist within namespace

During deployment of a CAPV cluster, cluster-api-provider-vsphere-static-ip consistently associates control plane machine IPClaims with the specified cluster.x-k8s.io/ip-pool-name. Worker node MachineDeployments, however are associated with seemingly random IPPools that happen to exist within the same management cluster namespace default.
Example of incorrect IPClaim to IPPool association for a MachineDeployment VSphereMachineTemplate below:
IPPool for cluster: ts-kubeflow-sac-prod (target of machine template)
apiVersion: ipam.metal3.io/v1alpha1
kind: IPPool
metadata:
  name: ip-pool-ts-kubeflow-sac-prod
  namespace: default
spec:
  clusterName: ts-kubeflow-sac-prod
...

IPPool for cluster: ts-kubeflow-rck-dev (different cluster and not the desired target)
apiVersion: ipam.metal3.io/v1alpha1
kind: IPPool
metadata:
  name: ip-pool-ts-kubeflow-rck-dev
  namespace: default
spec:
  clusterName: ts-kubeflow-rck-dev
...

vSphereMachineTemplate used within cluster: ts-kubeflow-sac-prod
apiVersion: infrastructure.cluster.x-k8s.io/v1alpha3
kind: VSphereMachineTemplate
metadata:
  name: ts-kubeflow-sac-prod-md1-v1
  namespace: default
  labels:
    cluster.x-k8s.io/ip-pool-name: ip-pool-ts-kubeflow-sac-prod
...

IPClaim associated with incorrect IPPool at spec/pool/name:
apiVersion: ipam.metal3.io/v1alpha1
kind: IPClaim
metadata:
  name: ts-kubeflow-sac-prod-md1-v1-srxbl-0
  namespace: default
spec:
  pool:
    apiVersion: ipam.metal3.io/v1alpha1
    kind: IPPool
    name: ip-pool-ts-kubeflow-rck-dev
    namespace: default
status:
  address:
    name: ts-kubeflow-rck-dev-10-7-5-155
    namespace: default

capv-static-ip-controller-manager output:
I1231 01:04:34.235684       1 vspheremachine_controller.go:84] controllers/VSphereMachine "msg"="waiting for machine controller to set ownerRef on VSphereMachine" "vspheremachine"={"Namespace":"default","Name":"ts-kubeflow-sac-prod-md1-v1-srxbl"}
I1231 01:04:34.381432       1 vspheremachine_controller.go:115] controllers/VSphereMachine "msg"="reconcile IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.482634       1 metal3io_ipam.go:116] controllers/VSphereMachine "msg"="IPPool ip-pool-ts-kubeflow-rck-dev is available" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.482814       1 metal3io_ipam.go:34] controllers/VSphereMachine "msg"="get IPAddress ts-kubeflow-sac-prod-md1-v1-srxbl-0" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.583548       1 metal3io_ipam.go:138] controllers/VSphereMachine "msg"="waiting for IPClaim ts-kubeflow-sac-prod-md1-v1-srxbl-0" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.583633       1 metal3io_ipam.go:46] controllers/VSphereMachine "msg"="allocate IP ts-kubeflow-sac-prod-md1-v1-srxbl-0" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.583675       1 metal3io_ipam.go:168] controllers/VSphereMachine "msg"="create IPClaim ts-kubeflow-sac-prod-md1-v1-srxbl-0" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.598704       1 metal3io_ipam.go:207] controllers/VSphereMachine "msg"="created IPClaim ts-kubeflow-sac-prod-md1-v1-srxbl-0, waiting for IPAddress to be available" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.599510       1 vspheremachine_controller.go:162] controllers/VSphereMachine "msg"="waiting for IP address to be available for the VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.599743       1 vspheremachine_controller.go:115] controllers/VSphereMachine "msg"="reconcile IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.601003       1 metal3io_ipam.go:116] controllers/VSphereMachine "msg"="IPPool ip-pool-ts-kubeflow-sac-prod is available" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.601322       1 metal3io_ipam.go:34] controllers/VSphereMachine "msg"="get IPAddress ts-kubeflow-sac-prod-md1-v1-srxbl-0" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.601396       1 metal3io_ipam.go:138] controllers/VSphereMachine "msg"="waiting for IPClaim ts-kubeflow-sac-prod-md1-v1-srxbl-0" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.601431       1 metal3io_ipam.go:46] controllers/VSphereMachine "msg"="allocate IP ts-kubeflow-sac-prod-md1-v1-srxbl-0" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.601472       1 metal3io_ipam.go:168] controllers/VSphereMachine "msg"="create IPClaim ts-kubeflow-sac-prod-md1-v1-srxbl-0" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.636264       1 metal3io_ipam.go:207] controllers/VSphereMachine "msg"="created IPClaim ts-kubeflow-sac-prod-md1-v1-srxbl-0, waiting for IPAddress to be available" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:04:34.636385       1 vspheremachine_controller.go:162] controllers/VSphereMachine "msg"="waiting for IP address to be available for the VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:05:04.603433       1 vspheremachine_controller.go:115] controllers/VSphereMachine "msg"="reconcile IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:05:04.603535       1 metal3io_ipam.go:116] controllers/VSphereMachine "msg"="IPPool ip-pool-rck-nonprod-corp-nonpci-1 is available" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:05:04.603548       1 metal3io_ipam.go:34] controllers/VSphereMachine "msg"="get IPAddress ts-kubeflow-sac-prod-md1-v1-srxbl-0" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:05:04.703930       1 vspheremachine_controller.go:170] controllers/VSphereMachine "msg"="static IP for VSphereMachine is ts-kubeflow-rck-dev-10-7-5-155" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:05:04.703966       1 vspheremachine_controller.go:174] controllers/VSphereMachine "msg"="assigning IP address <IP_ADDRESS> to VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:05:04.713373       1 vspheremachine_controller.go:198] controllers/VSphereMachine "msg"="successfully reconciled IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:05:04.714026       1 vspheremachine_controller.go:115] controllers/VSphereMachine "msg"="reconcile IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:05:04.723723       1 vspheremachine_controller.go:198] controllers/VSphereMachine "msg"="successfully reconciled IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:05:06.445087       1 vspheremachine_controller.go:115] controllers/VSphereMachine "msg"="reconcile IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:05:06.464530       1 vspheremachine_controller.go:198] controllers/VSphereMachine "msg"="successfully reconciled IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:05:29.796114       1 vspheremachine_controller.go:115] controllers/VSphereMachine "msg"="reconcile IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:05:29.812420       1 vspheremachine_controller.go:198] controllers/VSphereMachine "msg"="successfully reconciled IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:06:18.317444       1 vspheremachine_controller.go:115] controllers/VSphereMachine "msg"="reconcile IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:06:18.326339       1 vspheremachine_controller.go:198] controllers/VSphereMachine "msg"="successfully reconciled IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:06:18.334197       1 vspheremachine_controller.go:115] controllers/VSphereMachine "msg"="reconcile IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:06:18.348064       1 vspheremachine_controller.go:198] controllers/VSphereMachine "msg"="successfully reconciled IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:06:18.350894       1 vspheremachine_controller.go:115] controllers/VSphereMachine "msg"="reconcile IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"
I1231 01:06:18.378199       1 vspheremachine_controller.go:198] controllers/VSphereMachine "msg"="successfully reconciled IP address for VSphereMachine" "namespace"="default" "vsphereMachine"="ts-kubeflow-sac-prod-md1-v1-srxbl"

Is there perhaps some issue with cluster.x-k8s.io/ip-pool-name label matching amongst multiple IPPools within the same namespace?

The IPPool label is propagated from the VSphereMachineTemplate to the VSphereMachine only in case of worker nodes. So, in case of worker machines, the label is retrieved from the VSphereMachine while in case of CP machines, the IPPool labels are retrieved from the VSphereMachineTemplate. Can you please update the IPPool-label values set in all the worker VSphereMachines ?

The IPPool label is propagated from the VSphereMachineTemplate to the VSphereMachine only in case of worker nodes. So, in case of worker machines, the label is retrieved from the VSphereMachine while in case of CP machines, the IPPool labels are retrieved from the VSphereMachineTemplate. Can you please update the IPPool-label values set in all the worker VSphereMachines ?

In our setup the Worker VSphereMachineTemplate label cluster.x-k8s.io/ip-pool-name is not automatically applied downstream to the VsphereMachines objects. Only the cluster.x-k8s.io/cluster-name and cluster.x-k8s.io/deployment-name labels are applied. Presumably the CAPI controller is performing the latter. Is this different in your setup, or do you have an external process that applies the cluster.x-k8s.io/ip-pool-name label to the subordinate VsphereMachines?
component versions:
NAME                     NAMESPACE                           TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm        capi-kubeadm-bootstrap-system       BootstrapProvider        v0.3.12           Already up to date
control-plane-kubeadm    capi-kubeadm-control-plane-system   ControlPlaneProvider     v0.3.12           Already up to date
cluster-api              capi-system                         CoreProvider             v0.3.12           Already up to date
infrastructure-vsphere   capv-system                         InfrastructureProvider   v0.7.1            Already up to date

Also, the issue is not that no IPClaim is never gets created, but rather the IPClaim is created (sometimes almost immediately) just with a random IPPool.
Is there a use-case or reason why we're querying the IPPool label from the VsphereMachine objects themselves and not just using the VsphereMachineTemplates IPPool label for both CP nodes and Workers?

In our setup the Worker VSphereMachineTemplate label cluster.x-k8s.io/ip-pool-name is not automatically applied downstream to the VsphereMachines objects. Only the cluster.x-k8s.io/cluster-name and cluster.x-k8s.io/deployment-name labels are applied. Presumably the CAPI controller is performing the latter. Is this different in your setup, or do you have an external process that applies the cluster.x-k8s.io/ip-pool-name label to the subordinate VsphereMachines?
component versions:
NAME                     NAMESPACE                           TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm        capi-kubeadm-bootstrap-system       BootstrapProvider        v0.3.12           Already up to date
control-plane-kubeadm    capi-kubeadm-control-plane-system   ControlPlaneProvider     v0.3.12           Already up to date
cluster-api              capi-system                         CoreProvider             v0.3.12           Already up to date
infrastructure-vsphere   capv-system                         InfrastructureProvider   v0.7.1            Already up to date

Also, the issue is not that no IPClaim is never gets created, but rather the IPClaim is created (sometimes almost immediately) just with a random IPPool.
Is there a use-case or reason why we're querying the IPPool label from the VsphereMachine objects themselves and not just using the VsphereMachineTemplates IPPool label for both CP nodes and Workers?

Yes, we have an external flow that copies the template labels to MD. Let me add a fix to fetch IPPool label from VSphereMachineTemplate, for both CP nodes and workers.

Yes, we have an external flow that copies the template labels to MD. Let me add a fix to fetch IPPool label from VSphereMachineTemplate, for both CP nodes and workers.

This is working well.

This is working well.


Samples update

I would suggest the readme.md to be aligned with our other clients readmes.
You can see examples at:
https://github.com/Azure/azure-kusto-node
https://github.com/Azure/azure-kusto-python


fix: remove inconsistent PII filtering from rust_tracing integration

the PII filtering in the merged version treats span data set in on_new_span() as safe but span data set in on_record() as sensitive. in actuality, they're two different ways to set the same thing, so they should be treated the same
below i lay out my reasoning for removing this PII filtering. there is a tiny bit more work to do either way:

if that approach is accepted, i will update my docs branch to direct the user at the "Scrubbing Sensitive Data" page and i can update the docs for pyo3-python-tracing-subscriber to call out the tracing docs for excluding specific fields that the developer knows are sensitive
if we instead do want all-or-nothing PII filtering on by default to be conservative, i will update this PR to apply the filtering to both on_new_span() and on_record() and then update my docs branch to document the send_sensitive_data argument and filtering behavior

(the aforementioned docs branch)
the full scoop
some detail on `tracing` behavior
the #[tracing::instrument(fields(extra1=5, extra2)] attribute at the top of a function adds all of the function's arguments + extra fields listed in the attribute arguments as span data. when on_new_span() is called it will include all of the function arguments and fields, with one exception: fields without default values are not "recorded", so extra2 in this example will be omitted.
during the span, Span::current().record(field, val) can be called to set a value for extra2 after the function starts. it can also overwrite a value for an already-assigned field. on_record() will be called with the recorded fields/values.
to summarize, on_new_span() and on_record() are setting the same data, but on_new_span() sets the data to its default value at the beginning of the function and on_record() can set the data to new values after the function has begun.

the data we get from tracing amounts to stack-local variables and log statements which the Python "Scrubbing Sensitive Data" page list in the section for before_send / before_send_transaction. the python SDK also has event_scrubber for this.
additionally, this integration is basically a port of the Rust SDK's tracing integration which does not use the Rust SDK's version of should_send_default_pii() in this way (on_record() link). the Rust "Scrubbing Sensitive Data" page also describes tracing data in the section for before_send / before_send_transaction
it seems our SDKs typically don't use all-or-nothing filtering for data like this. instead they allow the user to provide targeted filtering at the SDK level with before_send/before_send_transaction/event_scrubber. this PR takes that approach for this integration

the web framework CI failures do not appear related to my change but maybe they will go away with a re-run or a merge later

replaced by https://github.com/getsentry/sentry-python/pull/3780


WIP: Begin crate smashing

Not a merge candidate until release 0.29 is done. Throwing it up for early feedback please.
This is my most recent attempt to understand the 'crate smashing' thread and split out a few crates. Specifically this PR currently creates the following crates, as a workspace:

bitcoin: main crate
bitcoin-str: hex, and re-exports (optional dependencies) of bech32, and base64
endian: the endian module turned into a crate
base58: the base58 module turned into a crate

It all builds locally but I doubt I have CI sorted correctly yet.

Stale, closing.


automate login ping tests

Count ping test attempts when you are logging it.
If you get an acceptable ping test on attempt N, only complete login/timein when you unwind back to attempt 1.
When timing in to try for a better connection, via timein command or equivalent, only issue logout request if you are currently logged in.
When you log in for the first time, if you are in stealth mode (/q), remove that for the purpose of saving actual user name and reading Preferences, as always.
If you did NOT log in with /q, add that to the name field of the LoginRequest, so that all subsequent timeins are done in stealth mode.
When doing a ping test at login, if it you got redirected away from api.php (afterlife.php, for example), do not compare the measured ping time with saved historical ping times, which are only api.php.
Add 2 new properties:

pingLoginCount (defaults to 0) the number of times you are willing to let KoLmafia automatically retry ping tests, looking for a successful goal or threshold average. If 0, no automation; a failed test will pop up the usual yes/no/cancel dialog asking if you want to accept, retry, or bail.
pingLoginFail - logout or login - the action taken if we cannot get a successfull average ping time after pingLoginCount attempts have been made. login means "accept it and remain logged in". logout means "log out in despair" and try again when you timein.

These properties are configurable on the Connection Options panel in both the Login Frame and Preferences/General
In preferences, that panel has two more lines:
Latest ping test average time was 35 msec.
(That auto-updates each time you execute a ping test - when attempting to timein, for example.)
Try for a better connection: [Time In]
(Press the button to logout (if needed) and time in, using all the options as configured above.

I also disabled and enabled the "Time In" button around executing it.
I'm not sure exactly how multiple threads running timeins with ping tests would work, but I'm sure it can't be good.

Tangentially, ran with this today and the login script only ran once in spite of multiple retries so that has been addressed.  Thank you.

Tangentially, ...

Considering that point 1 was specifically intended to address that, it's not exactly a tangent. 🙃
So, do approve this PR?

Tangentially, ...
So, do you approve this PR?

Real life got in the way and I wasn't 100% certain "only complete login/timein when you unwind back to attempt 1" addressed the issue when I skimmed things.
But now I will make time to review :-)


fix(deps): update icr.io/appcafe/open-liberty/samples/getting-started:latest docker digest to fd04ce5

This PR contains the following updates:

Package
Update
Change

icr.io/appcafe/open-liberty/samples/getting-started
digest
b99e5af -> fd04ce5

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

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

GitHub release
v1.4.6

Your semantic-release bot :package::rocket:


typescript error in node_modules

i'm using razzle typescript. and i get error from node_modules by typescript.
sample error:
ERROR in /home/hamid/my/www/with-typescript/node_modules/@types/react-redux/index.d.ts(118,29):
TS2370: A rest parameter must be of an array type.

I have tried to change tsconfig.json configs to exclude node_module files but it was not successful.
how can i disable it forever?

This is not a Razzle issue but a TypeScript one.

according to an issue in fork-ts-checker-webpack-plugin package i solved this problem by this reply:
https://github.com/Realytics/fork-ts-checker-webpack-plugin/issues/128#issuecomment-407371617
unfortunately, lots of packages have problems in their typescript and possible to you get them as errors and stops you from building razzle.
I say this for anybody has this problem
add "skipLibCheck": true in compilerOptions in tsconfig.json in your project's root.
@jaredpalmer I can open a pull request for default examples in the master branch.