eth_feeHistory invalid cached response

Signed-off-by: nikolay<EMAIL_ADDRESS>Description:

Related issue(s):
Fixes #881
Notes for reviewer:

Checklist

[x] Documented (Code comments, README, etc.)
[x] Tested (unit, integration, etc.)

Codecov Report
Base: 73.88% // Head: 73.91% // Increases project coverage by +0.02% :tada:

Coverage data is based on head (c5fa20f) compared to base (a7cecc6).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #882      +/-   ##
==========================================
+ Coverage   73.88%   73.91%   +0.02%
==========================================
  Files          29       29
  Lines        1815     1817       +2
  Branches      336      338       +2
==========================================
+ Hits         1341     1343       +2
  Misses        375      375
  Partials       99       99

Impacted Files
Coverage Δ

packages/relay/src/lib/eth.ts
82.19% <100.00%> (+0.06%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Progress Indicators

Currently, we only supported determinate progress indicators (ProgressBar and ProgressRing)

We should also support indeterminate progress indicators:

Indeterminate ProgressBar was implemeneted in version 1.3.1 (courtesy of @raitonoberu)

Indeterminate ProgressRing was implemented in version 1.3.3. (courtesy of @raitonoberu) <3


Error: buildx failed with: ERROR: denied: permission_denied: write_package

I tried to release at https://github.com/reproio/send-alb-metrics-to-datadog/actions/runs/7578216166/job/20640443143 , but it failed with following message:
------
 > pushing ghcr.io/reproio/send-alb-metrics-to-datadog:latest with docker:
------
ERROR: denied: permission_denied: write_package
Error: buildx failed with: ERROR: denied: permission_denied: write_package

I investigated this error I found a reason. We need add permission to write package by package settings in this organization.
For example: https://blog.yukirii.dev/github-action-ghcr-push-error/

@okkez @YAMASHITAHiroki @akihiro17 Could you add permission to write to this repository?

Or, we can discussion to migrate this repository to my account from this org to reduce cost of review or operation.

@takaishi Can you try again?

Pushing image was successfull! But goreleaser didn't push artifacts to release, so I'm going to investigate. Thank you.


[FP]: CVE-2023-22551 on org.springframework.integration:spring-integration-ftp

Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:vmware:spring_integration:5.5.7:*:*:*:*:*:*:*
CVE
CVE-2023-22551
ODC Integration
None
ODC Version
8.2.1
Description
The above CPE seems to match library that has actually been scanned.
The report also lists cpe:2.3:a:ftp_project:ftp:*:*:*:*:*:*:*:*, which does not seem to match the scanned library at all, but might be a better match for the CVE.
This FP Report looks related to the one in #5593. I suspect that similar problems may exist for many other libs that have FTP in their name.

approved


Improve C/C++ color scheme

Look in the image, C/C++ comments are shown brighter than onedark does. In my opinion (no an expert on colors schemes), comments should be more obscure, like onedark is showing. (vim one at the left, onedark at the right)

Also there are color difference in C language keywords, like if and return. I think they should have the same color. These are all the C keywords: http://en.cppreference.com/w/c/keyword

@rakr: I tested with severals C and C++ files and they look good. Thanks!
In my initial issue post, a just put just the C keywords. These are C++ keywords: http://en.cppreference.com/w/cpp/keyword. Are they considered as well?

Hi @jetm, yes I think we could consider them, bear in mind that by default these keywords are linked with C keywords.
I like to use this command before making any change to see if the links do make sense (Including my mapping in init.vim)
" Display highlighting groups
nnoremap <leader>hi :so $VIMRUNTIME/syntax/hitest.vim<cr>


[5.0.0] require() of a non-existing package in a try-catch block is broken

Bug report
What is the current behavior?
require() of a non-existing package in a try-catch block doesn't behave like in Webpack 4.
try
{
	require('preact').cloneElement; // when preact not available emits an error
	require('preact'); // when preact not available emits a warning
}
catch(e) {}

What is the expected behavior?
Webpack should always emit a warning. This worked fine in Webpack 4.
Other relevant information:
webpack version: 5.0.0
Node.js version: 12.18.4
Operating System: Linux

Please create reproducible test repo, it was fixed

https://github.com/siilike/webpack11639
$ pnpm i
Packages: +682
Resolving: total 683, reused 683, downloaded 0, done
node_modules/.pnpm/registry.npmjs.org/ejs/2.7.4/node_modules/ejs: Running postinstall script, done in 38ms

devDependencies:
+ webpack 5.0.0
+ webpack-cli 4.0.0

$ node_modules/.bin/webpack-cli ./bug.js
assets by status 176 bytes [cached] 1 asset
./bug.js 93 bytes [built] [code generated]

ERROR in ./bug.js 3:1-31
Module not found: Error: Can't resolve 'preact' in '/data1/tmp/webpacktest'

webpack 5.0.0 compiled with 1 error in 142 ms

$ node_modules/.bin/webpack-cli ./works.js
asset main.js 310 bytes [emitted] [minimized] (name: main)
./works.js 140 bytes [built] [code generated]

WARNING in ./works.js 5:9-26
Module not found: Error: Can't resolve 'preact' in '/data1/tmp/webpacktest'

webpack 5.0.0 compiled with 1 warning in 175 ms

Thanks, yes, it is bug


have all the outputs be piped to less and have colour output

Thank you for writing this tool, it is really incredible.
One thing I like though is to have all the outputs be shown in less but I don't want to pipe every single query I make with borg to less manually myself, can I make it as default output somehow?
Also it would be nice to have some colour in these outputs.
Thank you for any help.

Hi, @nikitavoloboev!
Thank you for your kind words.
Both of those are good ideas. Making something 'default' requires some way to configure borg which does not exist yet but it will be implemented not too far away in the future.
I will also look into syntax highlighting!
Cheers

@nikitavoloboev it's in latest master. Let me know if it works for you.

Piping to less is implemented. In fact you can pipe to anything - thing that does syntax highlight.


Random crash on game load - MissingMods screen

Issue Description:
I'm the dev of DNS Techpack. Reporting an issue a couple of users have had that is extremely odd. Starting the game, on certain instances causes a crash. The main menu should output a message of Error: Missing Mod or something along those lines. On most instances the pack will load fine, but so far I've had 2 reports of this issue.
This is not 100% reproducible. For some odd reason, the same installation of mods and configs on most machines works. On some however, it causes this crash. Removing EnderIO fixes the issue but is not an ideal fix.
Removing CoreChickenCore, CodeChickenLib, EnderStorage, NEI and ChickenChunks brings the main menu error back, saying that Brandon's Core relies on CCL to be installed.
Installing CCL brings the issue in question back.
Affected Versions:

EnderIO: 1.10.2-<IP_ADDRESS>_beta
EnderCore: 1.10.2-<IP_ADDRESS>-beta
Minecraft: 1.7.10
Forge: <IP_ADDRESS>1

Crash log
This issue was not present (as far as I know) with version <IP_ADDRESS>_beta of EnderIO.

Congratulation on naming those instances exactly the same as a popular Russian cracked launcher.
Next build will do a better check for that, sorry.

Wait, they're using a cracked launcher?

they may, but your crash log just used the same directory name by accident

I'm just forwarding their crash logs to here. It runs fine for me and most other players. It was just 2 instanced that had this issue. I'll investigate and get back to you.
Thanks for bringing this to my attention, I neglect to check for cracked launchers as it's not a common occurrence for us.

The directory listing /Instances/ is from ATLauncher. They are using the correct launcher for the modpack download. I don't believe this is a cracked version.

as I said, that crash log is from an installation that is using the same name by accident (and our code doing a check that is a tad too wide). The next build will fix that and only engage for a full name match, not a partial one.

Oh sorry, I misunderstood. Thanks for the help. I'll pass the information on.

build 138 should fix this, plz test, thx!

Already on it! One user has reported back and it seems like it's done the job.  Thanks for the quick fix!


Unable to install mamba-ssm on Linux with CUDA 12.1 and PyTorch 2.5.1

I'm trying to install mamba-ssm with pip install mamba-ssm but it doesn't work. I need help
These are my systems
CUDA : 12.1
PyTorch : 2.5.1
Python : 3.11.10
os : Linux 5.15.0-10-generic
Architecture : x86-64

I checked all the mamba-ssm released version(https://github.com/state-spaces/mamba/releases) and there was nothing for mine.
Is this the reason why I can't install it?
Below is my errored bash code
(eom_hymba) pcn_u8@localhost:~$ pip install mamba-ssm
Collecting mamba-ssm
  Using cached mamba_ssm-2.2.2.tar.gz (85 kB)
  Preparing metadata (setup.py) ... done
Requirement already satisfied: torch in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from mamba-ssm) (2.5.1+cu121)
Requirement already satisfied: packaging in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from mamba-ssm) (24.2)
Requirement already satisfied: ninja in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from mamba-ssm) (<IP_ADDRESS>)
Collecting einops (from mamba-ssm)
  Using cached einops-0.8.0-py3-none-any.whl.metadata (12 kB)
Requirement already satisfied: triton in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from mamba-ssm) (3.1.0)
Requirement already satisfied: transformers in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from mamba-ssm) (4.46.3)
Requirement already satisfied: filelock in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (3.13.1)
Requirement already satisfied: typing-extensions>=4.8.0 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (4.12.2)
Requirement already satisfied: networkx in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (3.2.1)
Requirement already satisfied: jinja2 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (3.1.3)
Requirement already satisfied: fsspec in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (2024.2.0)
Requirement already satisfied: nvidia-cuda-nvrtc-cu12==12.1.105 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (12.1.105)
Requirement already satisfied: nvidia-cuda-runtime-cu12==12.1.105 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (12.1.105)
Requirement already satisfied: nvidia-cuda-cupti-cu12==12.1.105 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (12.1.105)
Requirement already satisfied: nvidia-cudnn-cu12==<IP_ADDRESS> in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cublas-cu12==<IP_ADDRESS> in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cufft-cu12==<IP_ADDRESS> in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-curand-cu12==<IP_ADDRESS> in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusolver-cu12==<IP_ADDRESS> in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusparse-cu12==<IP_ADDRESS> in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-nccl-cu12==2.21.5 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (2.21.5)
Requirement already satisfied: nvidia-nvtx-cu12==12.1.105 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (12.1.105)
Requirement already satisfied: sympy==1.13.1 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from torch->mamba-ssm) (1.13.1)
Requirement already satisfied: nvidia-nvjitlink-cu12 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from nvidia-cusolver-cu12==<IP_ADDRESS>->torch->mamba-ssm) (12.1.105)
Requirement already satisfied: mpmath<1.4,>=1.1.0 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from sympy==1.13.1->torch->mamba-ssm) (1.3.0)
Requirement already satisfied: huggingface-hub<1.0,>=0.23.2 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from transformers->mamba-ssm) (0.26.3)
Requirement already satisfied: numpy>=1.17 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from transformers->mamba-ssm) (1.26.3)
Requirement already satisfied: pyyaml>=5.1 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from transformers->mamba-ssm) (6.0.2)
Requirement already satisfied: regex!=2019.12.17 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from transformers->mamba-ssm) (2024.11.6)
Requirement already satisfied: requests in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from transformers->mamba-ssm) (2.32.3)
Requirement already satisfied: tokenizers<0.21,>=0.20 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from transformers->mamba-ssm) (0.20.3)
Requirement already satisfied: safetensors>=0.4.1 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from transformers->mamba-ssm) (0.4.5)
Requirement already satisfied: tqdm>=4.27 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from transformers->mamba-ssm) (4.67.1)
Requirement already satisfied: MarkupSafe>=2.0 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from jinja2->torch->mamba-ssm) (2.1.5)
Requirement already satisfied: charset-normalizer<4,>=2 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from requests->transformers->mamba-ssm) (3.4.0)
Requirement already satisfied: idna<4,>=2.5 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from requests->transformers->mamba-ssm) (3.10)
Requirement already satisfied: urllib3<3,>=1.21.1 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from requests->transformers->mamba-ssm) (2.2.3)
Requirement already satisfied: certifi>=2017.4.17 in /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages (from requests->transformers->mamba-ssm) (2024.8.30)
Using cached einops-0.8.0-py3-none-any.whl (43 kB)
Building wheels for collected packages: mamba-ssm
  Building wheel for mamba-ssm (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [152 lines of output]

      torch.__version__  = 2.5.1+cu121

      running bdist_wheel
      Guessing wheel URL:  https://github.com/state-spaces/mamba/releases/download/v2.2.2/mamba_ssm-2.2.2+cu122torch2.5cxx11abiFALSE-cp311-cp311-linux_x86_64.whl
      Precompiled wheel not found. Building from source...
      running build
      running build_py
      creating build/lib.linux-x86_64-cpython-311/mamba_ssm
      copying mamba_ssm/__init__.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm
      creating build/lib.linux-x86_64-cpython-311/mamba_ssm/modules
      copying mamba_ssm/modules/mlp.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/modules
      copying mamba_ssm/modules/mamba2.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/modules
      copying mamba_ssm/modules/mamba2_simple.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/modules
      copying mamba_ssm/modules/ssd_minimal.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/modules
      copying mamba_ssm/modules/mamba_simple.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/modules
      copying mamba_ssm/modules/__init__.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/modules
      copying mamba_ssm/modules/mha.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/modules
      copying mamba_ssm/modules/block.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/modules
      creating build/lib.linux-x86_64-cpython-311/mamba_ssm/models
      copying mamba_ssm/models/config_mamba.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/models
      copying mamba_ssm/models/__init__.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/models
      copying mamba_ssm/models/mixer_seq_simple.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/models
      creating build/lib.linux-x86_64-cpython-311/mamba_ssm/utils
      copying mamba_ssm/utils/generation.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/utils
      copying mamba_ssm/utils/__init__.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/utils
      copying mamba_ssm/utils/hf.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/utils
      creating build/lib.linux-x86_64-cpython-311/mamba_ssm/distributed
      copying mamba_ssm/distributed/tensor_parallel.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/distributed
      copying mamba_ssm/distributed/__init__.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/distributed
      copying mamba_ssm/distributed/distributed_utils.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/distributed
      creating build/lib.linux-x86_64-cpython-311/mamba_ssm/ops
      copying mamba_ssm/ops/selective_scan_interface.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops
      copying mamba_ssm/ops/__init__.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops
      creating build/lib.linux-x86_64-cpython-311/mamba_ssm/ops/triton
      copying mamba_ssm/ops/triton/layer_norm.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops/triton
      copying mamba_ssm/ops/triton/ssd_chunk_state.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops/triton
      copying mamba_ssm/ops/triton/layernorm_gated.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops/triton
      copying mamba_ssm/ops/triton/selective_state_update.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops/triton
      copying mamba_ssm/ops/triton/k_activations.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops/triton
      copying mamba_ssm/ops/triton/ssd_bmm.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops/triton
      copying mamba_ssm/ops/triton/ssd_combined.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops/triton
      copying mamba_ssm/ops/triton/ssd_chunk_scan.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops/triton
      copying mamba_ssm/ops/triton/__init__.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops/triton
      copying mamba_ssm/ops/triton/ssd_state_passing.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops/triton
      copying mamba_ssm/ops/triton/softplus.py -> build/lib.linux-x86_64-cpython-311/mamba_ssm/ops/triton
      running build_ext
      /home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/torch/utils/cpp_extension.py:426: UserWarning: There are no g++ version bounds defined for CUDA version 12.1
        warnings.warn(f'There are no {compiler_name} version bounds defined for CUDA version {cuda_str_version}')
      building 'selective_scan_cuda' extension
      creating /tmp/pip-install-9abbcbav/mamba-ssm_a2ee6f3b2a12458fa60d9ef8c70cd385/build/temp.linux-x86_64-cpython-311/csrc/selective_scan
      Emitting ninja build file /tmp/pip-install-9abbcbav/mamba-ssm_a2ee6f3b2a12458fa60d9ef8c70cd385/build/temp.linux-x86_64-cpython-311/build.ninja...
      Compiling objects...
      Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
      ninja: error: '/tmp/pip-install-9abbcbav/mamba-ssm_a2ee6f3b2a12458fa60d9ef8c70cd385/csrc/selective_scan/selective_scan.cpp', needed by '/tmp/pip-install-9abbcbav/mamba-ssm_a2ee6f3b2a12458fa60d9ef8c70cd385/build/temp.linux-x86_64-cpython-311/csrc/selective_scan/selective_scan.o', missing and no known rule to make it
      Traceback (most recent call last):
        File "/tmp/pip-install-9abbcbav/mamba-ssm_a2ee6f3b2a12458fa60d9ef8c70cd385/setup.py", line 318, in run
          urllib.request.urlretrieve(wheel_url, wheel_filename)
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/urllib/request.py", line 241, in urlretrieve
          with contextlib.closing(urlopen(url, data)) as fp:
                                  ^^^^^^^^^^^^^^^^^^
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/urllib/request.py", line 216, in urlopen
          return opener.open(url, data, timeout)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/urllib/request.py", line 525, in open
          response = meth(req, response)
                     ^^^^^^^^^^^^^^^^^^^
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/urllib/request.py", line 634, in http_response
          response = self.parent.error(
                     ^^^^^^^^^^^^^^^^^^
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/urllib/request.py", line 563, in error
          return self._call_chain(*args)
                 ^^^^^^^^^^^^^^^^^^^^^^^
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/urllib/request.py", line 496, in _call_chain
          result = func(*args)
                   ^^^^^^^^^^^
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/urllib/request.py", line 643, in http_error_default
          raise HTTPError(req.full_url, code, msg, hdrs, fp)
      urllib.error.HTTPError: HTTP Error 404: Not Found

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/torch/utils/cpp_extension.py", line 2104, in _run_ninja_build
          subprocess.run(
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/subprocess.py", line 571, in run
          raise CalledProcessError(retcode, process.args,
      subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

      The above exception was the direct cause of the following exception:

      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-9abbcbav/mamba-ssm_a2ee6f3b2a12458fa60d9ef8c70cd385/setup.py", line 337, in <module>
          setup(
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/__init__.py", line 117, in setup
          return distutils.core.setup(**attrs)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/core.py", line 183, in setup
          return run_commands(dist)
                 ^^^^^^^^^^^^^^^^^^
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/core.py", line 199, in run_commands
          dist.run_commands()
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 954, in run_commands
          self.run_command(cmd)
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/dist.py", line 950, in run_command
          super().run_command(command)
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 973, in run_command
          cmd_obj.run()
        File "/tmp/pip-install-9abbcbav/mamba-ssm_a2ee6f3b2a12458fa60d9ef8c70cd385/setup.py", line 335, in run
          super().run()
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/wheel/_bdist_wheel.py", line 378, in run
          self.run_command("build")
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
          self.distribution.run_command(command)
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/dist.py", line 950, in run_command
          super().run_command(command)
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 973, in run_command
          cmd_obj.run()
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/command/build.py", line 135, in run
          self.run_command(cmd_name)
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
          self.distribution.run_command(command)
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/dist.py", line 950, in run_command
          super().run_command(command)
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 973, in run_command
          cmd_obj.run()
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/command/build_ext.py", line 98, in run
          _build_ext.run(self)
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/command/build_ext.py", line 359, in run
          self.build_extensions()
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/torch/utils/cpp_extension.py", line 868, in build_extensions
          build_ext.build_extensions(self)
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/command/build_ext.py", line 476, in build_extensions
          self._build_extensions_serial()
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/command/build_ext.py", line 502, in _build_extensions_serial
          self.build_extension(ext)
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/command/build_ext.py", line 263, in build_extension
          _build_ext.build_extension(self, ext)
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/setuptools/_distutils/command/build_ext.py", line 557, in build_extension
          objects = self.compiler.compile(
                    ^^^^^^^^^^^^^^^^^^^^^^
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/torch/utils/cpp_extension.py", line 681, in unix_wrap_ninja_compile
          _write_ninja_file_and_compile_objects(
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/torch/utils/cpp_extension.py", line 1784, in _write_ninja_file_and_compile_objects
          _run_ninja_build(
        File "/home/pcn_rns/anaconda3/envs/eom_hymba/lib/python3.11/site-packages/torch/utils/cpp_extension.py", line 2120, in _run_ninja_build
          raise RuntimeError(message) from e
      RuntimeError: Error compiling objects for extension
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for mamba-ssm
  Running setup.py clean for mamba-ssm
Failed to build mamba-ssm
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (mamba-ssm)

Would you be able to provide guidance on how to resolve this issue?
Thank you in advance!

I have the same exact error:
CUDA : 12.4
PyTorch : 2.5.1
Python : 3.12.3
os : Linux 5.4.0-198-generic
Architecture : x86-64

I solve this problem!! I tried 3 ways.

Update CUDA Version
Actually, I'm using an external server with my colleagues, so I haven't tried this method. But if it's a server using alone, I think it's well worth trying.

Install Wheel file in local
https://github.com/state-spaces/mamba/releases
Go into the url, and find approriate version which fit with your system. Below is what you have to check,

CUDA Version(cu)
PyTorch Version(torch)
Python Version(cp)
os(x86-64)

Unfortunately, my system doesn't fit with them. So I have to find another method.

Clone the git and install
This works for me.

git clone https://github.com/state-spaces/mamba.git
cd mamba
pip install -e .

If you got same error, try another one.
git clone https://github.com/state-spaces/mamba.git
cd mamba
python setup.py install

Good Luck!! :D

I solve this problem!! I tried 3 ways.
1. Update CUDA Version
   Actually, I'm using an external server with my colleagues, so I haven't tried this method. But if it's a server using alone, I think it's well worth trying.

2. Install Wheel file in local
   `https://github.com/state-spaces/mamba/releases`
   Go into the url, and find approriate version which fit with your system. Below is what you have to check,

* CUDA Version(`cu`)

* PyTorch Version(`torch`)

* Python Version(`cp`)

* os(`x86-64`)

Unfortunately, my system doesn't fit with them. So I have to find another method.
3. Clone the git and install
   This works for me.

git clone https://github.com/state-spaces/mamba.git
cd mamba
pip install -e .

If you got same error, try another one.
git clone https://github.com/state-spaces/mamba.git
cd mamba
python setup.py install

I hope this method helps you resolve your errors as well. Good Luck!! :D

I met the same error. Could you please provide the version of torch, cuda, and causal_conv1d, thanks


v1.10.0-rc quadcopter doesn't take off in HITL/jMAVsim

Describe the bug
Set up HITL simulation with jMAVsim on Ubuntu 18.04,  Pixhawk 4 with v1.10.0-rc, locally built px4_fmu-v5-multicopter.
To Reproduce
Steps to reproduce the behavior:

Follow the recipe from px4 website
Using Manual/Stabilized mode, arm vehicle and apply throttle
Vehicle does not take off
Mavlink shell (listener command) shows actuator_outputs_1 with valid values and actuator_outputs_0 with 0 values

Expected behavior
SERVO_OUTPUT_RAW or HIL_ACTUATOR_CONTROLS should follow actuator_outputs_1 and the vehicle should take off in simulation
Log Files and Screenshots
Flight Review Link
Add screenshots to help explain your problem.
Drone:

Pixhawk4 running in HITL Quad Mode
Photo of the IMU / autopilot setup if possible.

That's not good but thanks for the detailed report!

Originally I stated : "MAVLink inspector in QGC shows no HIL_ACTUATOR_CONTROLS, and SERVO_OUTPUT_RAW values are all 0".
But this is misleading. The MAVLink Inspector in QGC can only show the messages forwarded by jMAVSim. What's more interesting is:

Once the problem is happening, kill the simulator
Connect QGC to the Pixhawk via USB
Use the MAVLink inspector

This shows:

HIL_ACTUATOR_CONTROLS is generated by the Pixhawk, but it is all zeros
SERVO_OUTPUT_RAW flips back and forth between all-zeros sometimes and correct (or at least sensible) values other times

It seems to me that the publication of uOrbs actuator_outputs instance 0 and instance 1 is confusing the mavlink module's generation of HIL_ACTUATOR_CONTROLS and SERVO_OUTPUT_RAW.
listener actuator_outputs

TOPIC: actuator_outputs 2 instances

Instance 0:
 actuator_outputs_s
	timestamp: 712451977  (0.010010 seconds ago)
	noutputs: 8
	output: [0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000]

Instance 1:
 actuator_outputs_s
	timestamp: 712226919  (0.236525 seconds ago)
	noutputs: 12
	output: [1358.0000, 1408.0000, 1515.0000, 1323.0000, 1500.0000, 1500.0000, 900.0000, 900.0000, 1500.0000, 1500.0000, 1500.0000, 1500.0000, 0.0000, 0.0000, 0.0000, 0.0000]

If only instance 0 was published, and it had the correct values, I bet it would work.
Also, I tested a Pixhawk 2.1 (Cube) running px4_fmu-v3_default, and the behavior was 100% identical.

This change causes the HIL_ACTUATOR_CONTROLS mavlink message to have non-zero values, and now the drone takes off in jMAVSim and I can fly around Zurich crashing into virtual trees:
langrind@nik:~/Firmware$ git diff
diff --git a/src/modules/mavlink/mavlink_messages.cpp b/src/modules/mavlink/mavlink_messages.cpp
index 61a55b8b22..4e258c6165 100644
--- a/src/modules/mavlink/mavlink_messages.cpp
+++ b/src/modules/mavlink/mavlink_messages.cpp
@@ -3065,7 +3065,7 @@ private:
 protected:
        explicit MavlinkStreamHILActuatorControls(Mavlink *mavlink) : MavlinkStream(mavlink),
                _status_sub(_mavlink->add_orb_subscription(ORB_ID(vehicle_status))),
-               _act_sub(_mavlink->add_orb_subscription(ORB_ID(actuator_outputs))),
+              _act_sub(_mavlink->add_orb_subscription(ORB_ID(actuator_outputs), 1)),
                _act_time(0)

I wonder if this is the correct fix?

https://github.com/PX4/Firmware/pull/13488 is my proposed fix


AsyncStorage Set/get issue

I am working on redux form there i used asyncstorage for set data but there async storage not working ... i don't know what's issue ...

Please see code to understand more your problem.


Add to Getting Started doc recommendation to use --shallow-submodules

From our review for the Journal of Open Source Software, https://github.com/openjournals/joss-reviews/issues/5236, it was recommended that we suggest to users to clone the BridgeStan repository with --shallow-submodules since we don't necessarily need the git histories associated with Stan and Stan Math and this will save much disk space.
On my machine cloning BridgeStan using --shallow-submodules reports
$ du -hs bridgestan
698M	bridgestan

and without --shallow-submodules
$ du -hs bridgestan
1.2G	bridgestan

We can just mention the current sizes doing it both ways.  I had no idea you could do that.

Also, how does this compare to downloading the .zip file or one of our releases?

We create the release using tar --exclude-vcs, which completely removes the .git folders (including from the submodules). By not saving any history it gets quite small.

The equivalent for a git clone would be something like
git clone --recurse-submodules --shallow-submodules --depth=1 https://github.com/roualdes/bridgestan.git


Replaced "parsers" option in configuration documentation to "parser"

A required option is not "parsers" but "parser".

@tkawachi Sorry to be late. Let us merge this. Thanks for your contribution!


Ilkeston (ILN)

Trains what runs through Ilkeston from Nottingham/Liverpool/Leeds the station annoucements don't annouce this station.

Because there are no audio snippet for that station.

Hello,
I didn’t know this ststjon had no audio for it thank you for that :)
many thanks
On Sun, 18 Aug 2024 at 13:31, LX9702.UV6921 @.***>
wrote:

Because there are no audio snippet for that station.
image.png (view on web)
https://github.com/user-attachments/assets/84186b65-c04a-46bf-9a36-b0fc042288aa
image.png (view on web)
https://github.com/user-attachments/assets/7dfe3626-875d-4603-b591-fc65eb6cf78a
—
Reply to this email directly, view it on GitHub
https://github.com/davwheat/rail-announcements/issues/262#issuecomment-2295245337,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKTHFO7VZF7D4OK23F66MNLZSCHZVAVCNFSM6AAAAABMVYNAGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGI2DKMZTG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

This name is difficult to bodge due to its many vowels and sounds. Therefore, we are probably better off without it.


Typeerror："NoneType" object is not iterable

Typeerror："NoneType" object is not iterable

Hi, @eduo97 . Could you provide more details, like your config and all the error messages?

Hi, @eduo97 . Could you provide more details, like your config and all the error messages?

This is related to the data I use and I have solved it

the same issue, how did you solve it?

I also encountered this problem, can you tell me how to solve this problem?

Cloud you share how to solve this？thanks a lot！


Get error when using it with Dressing(pcall(require, "cmp"))

dressing.nvim have this code
https://github.com/stevearc/dressing.nvim/blob/master/lua/dressing/input.lua#L493
  -- Configure nvim-cmp if installed
  local has_cmp, cmp = pcall(require, "cmp")
  if has_cmp then
    cmp.setup.buffer({
      enabled = opts.completion ~= nil,
      sources = {
        { name = "omni" },
      },
    })
  end

When using blink.compact, this code throws an error. Is there any way to work around it?

The error itself should be simple to fix. I can add a dummy cmp.setup.buffer function that does nothing. However, blink.cmp does not currently have a way to set a per-buffer configuration, so implementing the functionality of cmp.setup.buffer is not feasible. In this case, it looks like dressing.nvim is only enabling the omni source, so it shouldn't have much impact.


Add custom properties to INDEXED_PROPERTIES

Enhancement. The ability to add custom properties to the index.
algolia:
  applicationID: 'ID'
  apiKey: 'Key'
  indexName: 'index'
  properties:
    - featured_image
    - something_else

Good idea 👍
Would not it be easier to index all the properties though? It would spare us the need to configure things out.

Indexing everything  could work, but customization might be desirable in certain cases. I needed this feature for a project, so here's a pull request that has been tested #29

I just met this problem, and there is a link do not want to be indexed.

@lanpangzhi if I understand well, there is a post/page you would not like to index? I have not thought about that, that's a good idea.
Do you write specific metadata in your post/page already that could be used to put them aside from the indexing process?


Road to 1.0.0

Goals

Remove need for Swift index JSON file.
Move Gazelle plugin to its own repository.
Create release 1.0.0.

Tasks

[x] Process SPM Package.swift and Package.resolved in the repository rule.

[x] Stop reading the index file in the repository rules.
[x] Be sure to return the correct repository info so that mod tidy will update the MODULE.bazel file with the correct use_repos declaration.
[x] Remove all of the index files in the examples.
[x] Remove all of the swift_deps START and swift_deps END comments.
[x] Update bzlmod/workspace to use from_package().

[x] Update the Gazelle plugin to not use the Swift index JSON file.
[x] Update //:swift_update_pkgs to just run SPM commands without using Go. Be sure to use the Swift toolchain, not the Swift installed on the system. (Possibly, create a new macro that creates the commands for running Swift package commands.) For now, I removed swift_update_packages. If people would like a way to update Swift packages using Bazel, we will do it as a separate feature.
[x] Fix examples

[x] grpc_package_example
[x] symlink_example
[x] ios_sim

[ ] Move Gazelle plugin to its own repository.

[ ] Create a repository for the Gazelle plugin.
[ ] Publish to BCR.
[ ] Remove Gazelle plugin from rules_swift_package_manager.

[ ] #1079
[ ] Create release 1.0.0.

Notes regarding Gazelle plugin

No more update_repos.
rules_swift_package_manager will define a repository called swift_deps_info. It will contain the list of direct dependencies for the workspace (i.e., those defined in the Package.swift).
The plugin

It will use repo.FindExternalRepo to find the swift_deps_info and read the information written there. (NOTE: We could just read the list of repo names by parsing the MODULE.bazel. However, I think that we want to support non-bzlmod a bit longer.)
It will then read the pkg_info.json file that lives at the root of every Swift package repository.
This will populate the DependencyIndex.

What do we need DependencyIndex for anymore? Aren't product names deterministic now?

What do we need DependencyIndex for anymore? Aren't product names deterministic now?
The Gazelle plugin needs to resolve module names to Bazel labels.

Ahh, so that won't be in this repo in the end? Got it.

For anyone following along at home, this branch has the examples working if you run bazel test //..., no index file required. 🙂 I started updating the Gazelle plugin to work properly in this new world. Here is the basic plan:

Provide a swift_deps_info repository rule that generates a JSON file with the module/product/package information that is needed to resolve modules to Bazel targets.
Update the Gazelle plugin to read this file and load it as the DependencyIndex.
I anticipate keeping the existing API for the DependencyIndex. So, I hope that there won't be any other major changes to the resolve and generate portions of the Gazelle plugin.
Remove the update repos portion of the Gazelle plugin.

Can we add https://github.com/cgrindel/rules_swift_package_manager/issues/1079 to this?

Done.

Just a quick update regarding the v1 release. I have been working on #1079. I have a draft PR (#1217) with everything working except the rules_xcodeproj no-sandbox build. Unfortunately, that fails with duplicate definitions. I see and mostly understand why this is happening. Unfortunately, I am struggling to prevent the duplicate module map files causing the errors.
I put together #1266 which attempts to prevent objc_library from creating its own module map file by specifying the one that rules_swift_package_manager creates. Unfortunately, this causes an error:
In file included from external/rules_swift_package_manager~~swift_deps~swiftpkg_firebase_ios_sdk/FirebaseInstallations/Source/Library/FIRInstallations.m:25:
external/rules_swift_package_manager~~swift_deps~swiftpkg_firebase_ios_sdk/FirebaseCore/Extension/FirebaseCoreInternal.h:15:1: error: use of '@import' when modules are disabled
@import FirebaseCore;
^
1 error generated.

Looking through the actual command-line, I do not see the -fmodules flag. I thought that this was added by setting enable_modules = True.
If anyone has any thoughts or suggestions, please send them my way.


Deprecate default AbstractFileCollection constructor and nag about its use

In Gradle 6.3 we've introduced a new PatternSet factory that must be passed to the constructor of AbstractFileCollection (and thus those of all its subclasses). We should stop using the default constructor that was kept for backwards compatibility.
Unfortunately, a number of internal subtypes still rely on the default constructor. These should be refactored to use the constructor that takes an explicit Factory<PatternSet>.
Note that it is likely that there are FileCollection implementations in the wild. That's why we need to add publicly visible nagging and observe a proper deprecation cycle, even though AbstractFileCollection is internal API.

@lptr pls. label this issue as you see fit.


Feat/add mutation testing

Type of changes

[ ] Bug fix
[ ] New feature
[ ] Documentation / docstrings
[ ] Tests
[ ] Other

Checklist

[ ] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[ ] I've added tests for new code.
[ ] I accept that @willmcgugan may be pedantic in the code review.

Description
Please describe your changes here. If this fixes a bug, please link to the issue, if possible.

Codecov Report

Merging #3 (18d8ea8) into master (31ceb88) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #3   +/-   ##
=======================================
  Coverage   99.72%   99.72%
=======================================
  Files          55       55
  Lines        4812     4812
=======================================
  Hits         4799     4799
  Misses         13       13

Flag
Coverage Δ

unittests
99.72% <ø> (ø)

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

Continue to review full report at Codecov.

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


less obtrusive colors for terminal stl

In vim, :terminal has a bright green StatusLineTerm and
StatusLineTermNC. This update guaruntees that both vim and neovim have
consistent StatusLine[NC] and StatusLineTerm[NC] colors.

before:

after:

No problem, take your time and do not stress, my study time is also eating all my weekends 😐

Superseded by #108


langle and rangle missplaced, dagger renders box

With Makie master text(L"a \langle c^\dagger \rangle b") renders as

The same issue is happening on Luxor, where we just implemented a rendering of LaTeX.

So this had been fine for a while with MathTeXEngine v2.1 for me, but with https://github.com/JuliaPlots/Makie.jl/pull/1785 it's broken again.
I messed around a bit and now I have the suspicion that
https://github.com/Kolaru/MathTeXEngine.jl/blob/b3a224f9b4a7380f91ebb7c8f931bd13c387c45a/src/engine/layout.jl#L202
or something similar needs to apply to \langle and \rangle, or maybe even cmex10 symbols in general. Because with that applied \langle and \rangle they look well placed to me.

@ffreyer did you have any luck with getting \langle and \rangle to render correctly with what you mention above? I am just at the last step of getting some plots ready and have not had any luck. I was hoping to have a look around in MathTeXEngine.jl over the weekend but if you have a good place to start I might be able to save some time!

Ah ok! With a bit of post-figure-making editing I managed to get everything looking ok but made no progress on fixing this issue. As you mention above it was all working fine with a previous version of MathTexEngine.jl so I was going to trawl back and see if there were any obvious differences with the layout for the files in cmex10.ttf.

Fixed by #67


Verify if current pharo9 branch is working on Pharo 7 and Pharo 8 - then switch to master

Slot trait support since Pharo 7:
https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/Traits.md#stateful-trait.

[x] Pharo 8
[ ] Pharo 7

Molecule (pharo9 branch) tested on Pharo 8 (Pharo-8.0.0+build.1124.sha.0932da82f08175e906b0e2a8052120c823374e9f 64 Bit) : tests passed and examples (Clock and GPS) are running good.

Creating a 1.2 release to start 1.2.x Molecule versions => Will be swith to "master" branch.
Creating a 1.1.1 release for previous 1.1 Molecule version and manage legacy support => Will be swith to an old branch.


Added 3.0 new proj screenshot to first-mvc.

Fixes #15138
Internal Review
Updated start-mvc.md to use new 3.0 screenshot for the the new project dialog.
Included the new screenshot new_project30.png

Ready for review.


CVE Alert DHCP

What:
This ticket sits inside the CVE alerts epic. It is specifically for reviewing the alerts in DHCP.
There are three alerts to review. The findings from the three alerts needs to be captured on this ticket.
This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes. If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there. The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with.

CVE-2023-38545 - curl
Finding ID: arn:aws:inspector2:eu-west-2:473630360727:finding/865c12f226c11df2339ecd882efe136d

all these CVE found in above AWS inspector findings has been addressed

Need further discussion if we need to address High as a part of this ticket?

All critical CVE addressed in development,Pre-production and Production environment


[Suggestion] Being able to edit inputs for crafts

It would be nice if we could edit recipes on the website. A lot of servers make modifications to vanilla recipes by changing the input. I might push my luck, but it would also be nice if we could also add recipe ourself by making a selection of the type and amount of ingredient needed (that would help for modded stuff).
Beside that, I really love the platform and use it on every vanilla server where I play! Thanks a lot.

I support this.
However being able to manually select inputs would also work well. Having different prices for different woods at a Carpenter's store, such as a high price for Redwood, and a lower price for Oak or Cedar, instead of clumping all "wood tags" together in the Input section.


Question: Does the css parser implement the css-3 parsing algorithm?

Hi, this is a question I've been asked to answer, since I'm recommending the use of AngleSharp as a css parser.
"Does the css parser implement the parsing algorithms exactly as described in http://dev.w3.org/csswg/css-syntax-3/#parser-algorithms? In particular, does the error handling match the specification?"
I'd appreciate a clear answer to this so that I can communicate it.

Yes, this was the specification after which I've built the parser.


crash when starting godot under Linux4Tegra

Godot version:

3.1 release tarball
OS/device including version:

Ubuntu 18.04.2 Linux4Tegra running on Jetson Nano
Issue description:

godot crashes on startup with this error:
./godot.x11.tools.64
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] linux-vdso.so.1(__kernel_rt_sigreturn+0) [0x7f7ba876c0] (??:0)
[2] /usr/lib/aarch64-linux-gnu/libGLX.so.0(+0xd670) [0x7f7afb2670] (??:0)
-- END OF BACKTRACE --
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] linux-vdso.so.1(__kernel_rt_sigreturn+0) [0x7f7ba876c0] (??:0)
[2] /usr/lib/aarch64-linux-gnu/libGLX.so.0(+0xd670) [0x7f7afb2670] (??:0)
-- END OF BACKTRACE --
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] linux-vdso.so.1(__kernel_rt_sigreturn+0) [0x7f7ba876c0] (??:0)
[2] /usr/lib/aarch64-linux-gnu/libGLX.so.0(+0xd670) [0x7f7afb2670] (??:0)
-- END OF BACKTRACE --
Aborted (core dumped)

Note that I had to use qemu-user-static / systemd-nspawn on my laptop to build godot. L4T freezes part way through building godot on my Nano.
How much RAM is required to build godot under ARM64 Linux? 8GB seems to be enough as it builds on my laptop.

dan@dan-desktop:/usr/lib/aarch64-linux-gnu/tegra-egl$ ls -l
total 1244
-rw-r--r-- 1 root root      37 Jan 28  2018 ld.so.conf
-rwxr-xr-x 1 root root 1075704 Mar 13 10:03 libEGL_nvidia.so.0
-rwxr-xr-x 1 root root   67800 Mar 13 10:03 libGLESv1_CM_nvidia.so.1
-rwxr-xr-x 1 root root  116952 Mar 13 10:03 libGLESv2_nvidia.so.2
-rw-r--r-- 1 root root     107 Mar 13 10:03 nvidia.json
dan@dan-desktop:/usr/lib/aarch64-linux-gnu/tegra-egl$
The GL include files are in the usual place, apart from that.

The exact same bug occurs when running Godot on the Nintendo Switch after booting Linux4Tegra. Because being able to directly test on the Nintendo Switch is important here a workaround until this bug is fixed. Just build it by following the X11 building guide and enter the following command to launch it:
LD_PRELOAD=/usr/lib/aarch64-linux-gnu/libgtk3-nocsd.so.0:/usr/lib/aarch64-linux-gnu/libXcursor.so.1:/usr/lib/aarch64-linux-gnu/libXinerama.so.1:/usr/lib/aarch64-linux-gnu/libXrandr.so.2:/usr/lib/aarch64-linux-gnu/libXrender.so.1:/usr/lib/aarch64-linux-gnu/libX11.so.6:/usr/lib/aarch64-linux-gnu/libXi.so.6:/usr/lib/aarch64-linux-gnu/libfreetype.so.6:/usr/lib/aarch64-linux-gnu/libpng16.so.16:/usr/lib/aarch64-linux-gnu/libasound.so.2:/usr/lib/aarch64-linux-gnu/libpulse.so.0:/lib/aarch64-linux-gnu/libz.so.1:/usr/lib/aarch64-linux-gnu/libGL.so.1:/lib/aarch64-linux-gnu/libpthread.so.0:/lib/aarch64-linux-gnu/libdl.so.2:/usr/lib/aarch64-linux-gnu/libstdc++.so.6:/lib/aarch64-linux-gnu/libm.so.6:/lib/aarch64-linux-gnu/libgcc_s.so.1:/lib/aarch64-linux-gnu/libc.so.6:/lib/ld-linux-aarch64.so.1:/usr/lib/aarch64-linux-gnu/libXfixes.so.3:/usr/lib/aarch64-linux-gnu/libXext.so.6:/usr/lib/aarch64-linux-gnu/libxcb.so.1:/usr/lib/aarch64-linux-gnu/pulseaudio/libpulsecommon-11.1.so:/lib/aarch64-linux-gnu/libdbus-1.so.3:/usr/lib/aarch64-linux-gnu/libGLX.so.0:/usr/lib/aarch64-linux-gnu/libGLdispatch.so.0:/usr/lib/aarch64-linux-gnu/libXau.so.6:/usr/lib/aarch64-linux-gnu/libXdmcp.so.6:/lib/aarch64-linux-gnu/libsystemd.so.0:/lib/aarch64-linux-gnu/libwrap.so.0:/usr/lib/aarch64-linux-gnu/libsndfile.so.1:/usr/lib/aarch64-linux-gnu/libasyncns.so.0:/lib/aarch64-linux-gnu/librt.so.1:/lib/aarch64-linux-gnu/libbsd.so.0:/lib/aarch64-linux-gnu/liblzma.so.5:/usr/lib/aarch64-linux-gnu/liblz4.so.1:/lib/aarch64-linux-gnu/libgcrypt.so.20:/lib/aarch64-linux-gnu/libnsl.so.1:/usr/lib/aarch64-linux-gnu/libFLAC.so.8:/usr/lib/aarch64-linux-gnu/libogg.so.0:/usr/lib/aarch64-linux-gnu/libvorbis.so.0:/usr/lib/aarch64-linux-gnu/libvorbisenc.so.2:/lib/aarch64-linux-gnu/libresolv.so.2:/lib/aarch64-linux-gnu/libgpg-error.so.0`` ./godot.x11.tools.64

I tested the above workaround on latest master commit 2dc7be505a2b7bc803d3a3b2d6311d4a435a4234 on the Nintendo Switch using Linux4Tegra Ubuntu 18.04. In case the above workaround doesn’t work on newer versions because more libraries where added just add them to LD_PRELOAD at their intended position which you can see using ldd godot.x11.tools.64.
Why does this workaround work? I assume the problem is libGLX_nvidia not loading before/while loading libGLX and so libGLX not being able to get the GPU information. I tried preloading libGLX_nvidia using LD_PRELOAD=/usr/lib/aarch64-linux-gnu/tegra/libGLX_nvidia.so.0 ./godot.x11.tools.64 but that caused: Error initializing GLAD at drivers/gles3/rasterizer_gles3.cpp:141 and drivers/gles2/rasterizer_gles2.cpp:166 because of OpenGL not being able to initialize for some reason. I figured out that by using LD_PRELOAD libraries load properly so I just used ldd ./godot.x11.tools.64 and put them all in the same order and without any modifications inside LD_PRELOAD where they all getting preloaded properly before starting Godot and so overrides all wrongly loaded libraries.
I have no idea why Godot doesn’t load them properly even though they are all there when checking ldd ./godot.x11.tools.64 but other projects had similar issues with Linux4Tegra like for example https://github.com/hrydgard/ppsspp/issues/12001 which solved it by hardcoding libGLX_nvidia inside their Linux4Tegra build configuration.
Even though there’s now a workaround I really hope this issue is getting fixed soon because Linux4Tegra on the Switch got a quite popular Linux gaming configuration with a lot of developers not knowing this workaround also there are other platforms using Linux4Tegra like the Jetson Nano mentioned in the issue report.
In the end it’s absolutely awesome the Godot Editor works on arm64 at all and especially with good enough performance to run at usable speed on the Nintendo Switch.
Just write if you need any Linux4Tegra specific information or help testing potential fixes of this issue.

Thanks @nicoboss, I'll try your workaround soon, if one of the the devs doesn't fix it first.

I did some more testing and my assumption of libGLX_nvidia not loading seems right. When launching godot normally libGLX_nvidia doesn't get loaded at all while when preloading all the shared libraries libGLX_nvidia is the first detected dependency of shared library that gets loader right after transferring the control of shared libraries to godot.x11.tools.64.
Also, I figured out that my workaround only seems to work if every single required first degree dependent library will be preloaded. Even if only a single one is missing it won't be loaded properly by godot.x11.tools.64 and it crashes. You most likely have to write you own LD_PRELOAD command based on the output of ldd ./godot.x11.tools.64 if you don't have all the libraries at the exact same location or godot compiled other than the default build configurations.
What’s also interesting is that setting LD_BIND_NOW = 1 will result in godot having the same error as when launched normally even though it’s quite similar to preloading everything using LD_PRELOAD.
Here the DEBUG_LD of normally loaded failing and LD_PRELOAD loaded working godot.x11.tools.64 startup log in order to help further investigation of this issue:
godot_L4T_LD_DEBUG_normal_failing.log
godot_L4T_LD_DEBUG_LD_PRELOAD_working.log

Can anyone still reproduce this bug in Godot 3.2.3 or any later release?

@KoBeWi I just tested Godot 3.2.3 and latest master on latest Linux4Tegra on the Nintendo Switch (Switchroot Ubuntu 3.2.0 build with 18.04 LTS [Bionic Beaver] and a 4 GB swap file).
I was successfully able to compile and run Godot 3.2.3 in booth GLES2 and GLES3 mode and latest master https://github.com/godotengine/godot/commit/3dc8aaaccc642cddbd8d5c1841fef079db5c7edf in Vulkan mode without any issues.
This issue seems to be fixed and can be closed – thanks for your awesome work.


Set default timeout for all the HTTP requests

This will avoid having hanging connections when using Google API calls.
In case the user have set default socket timeout, that value is used instead of default.

I signed it!

@fabriziodemaria

@jonparrott Could you take a look at this PR please?

5 minutes seems way too high. App Engine will terminate requests after 60 seconds.

@jonparrott I wanted to be conservative.
I've changed it to 60s now.

@i-maravic I guess my concern here is that I don't like the idea of using any library-specific timeout that the user doesn't explicitly set. It's surprising behavior. What prompted this change? Can I get some more context to better understand what problem this is trying to solve?

@jonparrott We're using google-api-python-client when running periodic (hourly or daily) batch jobs for uploading to BigQuery and reading/writing to Google Cloud Storage. All the periodic jobs are being executed in Docker containers.
Recently we've experienced issues with those jobs hanging forever without making any progress. After doing some investigation we detected that the code making requests to Google APIs (aka. google-api-python-client) is hanging forever while waiting something to read from TCP socket. This was surprising behaviour for us.
After doing even more digging we discovered that Docker had some weird networking issues, which were causing this in the first place. We're not 100% sure how to reproduce Docker issue though, but restarting the Docker service mitigated a lot of problems we're experiencing.
I fell that library doing HTTP requests should set a sane default timeout for doing HTTP requests, because we could easily avoid issues like this in the future. I would argue that this is what most of the users would like to have any how.
I would also like to point out that you already have code in your lib, which is dealing with Timeout exceptions that might be thrown from the HTTP requests and do the retries accordingly.
I know that you're not using requests library, but there is very nice explanation why all production code using it should set timeouts for all the HTTP requests it's doing.

@i-maravic I see, okay.
I need the CLA bot to verify your signature status before I can merge.

I work for Spotify. Spotify should have signed the CLA.

@i-maravic gotcha.
@lukesneeringer @landrito I'd appreciate if one of you could chime in and let me know your thoughts before I merge this.

A 60 second default timeout seems reasonable to me, and it is easy enough to override. LGTM.

@lukesneeringer thanks for chiming in!
@i-maravic okay, so it looks like this is going to happen, can I ask two things of you:

Is it possible to add tests or assertions to existing tests to cover this?
This timeout only applies to the http object used to fetch discovery documents. Do you want to apply the timeout to the http object used to make actual API requests as well?

@jonparrott Sounds like reasonable asks.
Could you point me out where is the http object for actual API requests constructed?

@i-maravic just below in build_from_document: https://github.com/google/google-api-python-client/pull/320/files#diff-bceb3b293cf7c789403d137d70ef8dd3R370

@jonparrott Now the default timeout is applied to all discovery and API requests (auth or not)
Hopefully I didn't miss and httplib2.Http() instantiation in the lib

@i-maravic this looks good, one last question:
Do you want to pass in timeout to authorized_http here? Otherwise, the authorized http instance won't have the timeout.

@jonparrott authorized_http gets timeout set here

@i-maravic gotcha. Alright, this LGTM. Thanks!


Build fails on php-fpm

Info:

Docker version ($ docker --version): 18.03.1-ce, build 9ee9f40
Laradock commit ($ git rev-parse HEAD): 154249a08f59197703649245461d30d51789f94b
System info (Mac, PC, Linux): Mac
System info disto/version: macOS High Sierra Version 10.13.5

Issue:
Running docker-compose up -d nginx mariadb workspace fails on php-fpm.
The following error occurs:
Digest: sha256:eec0f2bc08e949ebb6a5dc0b118e8f9409a9198a830db202778baadfe1736ecd
Status: Downloaded newer image for laradock/php-fpm:2.2-7.2
---> eb15f92a08af
Step 3/72 : LABEL maintainer="Mahmoud Zalt<EMAIL_ADDRESS>ERROR: Service 'php-fpm' failed to build: error creating overlay mount to /var/lib/docker/overlay2/25b85177dd62dd6df83785e8ec575310f7c98fe892c9ea248c7ff963e72841fc-init/merged: no such file or directory
Expected behavior:
The expected behavious is that the images are build and the environments run.
Reproduce:
See issue
Hopefully this is enough information and someone can help fix this.
Thanks in advance!

rebuild images with no cache option:
docker-compose down
docker-compose build --no-cache php-fpm nginx mariadb workspace
docker-compose up -d nginx mariadb

@bestlong This does not seem to help. I still get the same error. Any other ideas?

I just found the solution.
Apparently it's a thing with Docker on mac.
https://github.com/docker/for-mac/issues/1396

@mquellhorst
maybe hard disk free space not enough.


Add learning rate scheduler, refactor to clean up train loop a bit

Closes #22. Makes progress toward #19 although doesn't actually implement early stopping.

merging by executive order


Age-restricted videos return no audio streams with only some cookies.

Hi,
I'm trying to access age-restricted videos such as this one with ytcog. However, on every one of my account cookies, it returns no audio streams except on my main one. I am wondering why this may be.
While it's acceptable to simply use my primary account's cookies for this, I'm worried it will influence my YouTube recommendations and watch history. Any help would be appreciated and thank you so much for making this library!!
Also- I'm happy to provide the cookies themselves via email or something if needed.

I will check this out.  I have not experienced this.
I have seen no indication that using ytcog with a cookie influences recommendations and watch history (because I think the trackers that compile these are bypassed).  I have noticed with extensive use I sometimes get 429'd accessing channel content directly in a browser (This channel has no videos). But no issues watching videos/playlists via browser search.

Alright perfect! Thanks for the quick reply. If it doesn't hit those trackers, then all is good. Would still like to use an alt account for it just to keep everything separate but certainly very low urgency.

Hey, noticed recently that search queries seem to be saved and logged and appear as recent searches on the YouTube mobile app.
1/ Do you know if there's any way to avoid this?
2/ Have you been able to reproduce the age restriction issue? I will do some more testing tomorrow as well.

Well, you could be right. I went to check on my YT account and I have search history turned off.  I guess that's why it is not affecting me.  Is that an option for you, or do you rely on your browser search history?
I still have my watched videos history on and those do not include anything I download via ytcog.
I haven't experienced any issues with missing sound. That said, I only have the one YouTube account.
Re: Age Restricted videos:
I haven't experienced any issues with missing sound. That said, I only have the one YouTube account.
When you encounter this problem, you can paste the videoStream[n].url and audioStream[n].url into your browser after video.fetch().   At least it can tell us if the problem is a) passing the YouTube challenges in ytcog, b) getting the sound from youtube, or c) muxing it with the video in ytcog.

I've tried my best but I can no longer reproduce the issue I was facing a couple of weeks ago- the alternate account cookie seems to work now.

When you encounter this problem, you can paste the videoStream[n].url and audioStream[n].url into your browser after video.fetch(). At least it can tell us if the problem is a) passing the YouTube challenges in ytcog, b) getting the sound from youtube, or c) muxing it with the video in ytcog.

If I remember correctly, printing video.audioStreams would just print [] if it helps. Anyhow, the search history effect is not an issue for me anymore since I can just use a different account for ytcog. Thanks for your help!


Rename Actions to Tasks, replace Prototypes with Classes

Oof. I did it. This commit renames Actions to Tasks. It also does a few other things
while I was at it:
Replace Prototypes with Classes
Originally I avoided using classes because of Bloat bloat, however using Buble for transpilation appears to have no effect on the end gzipped size.
Glossary document
I've also added a glossary of terms for Microcosm. This should help us keep things straight, and aid us in identifying areas where we can decrease the amount of Microcosm specific stuff you need to know.
Actions aren't going away
Just to clarify, the idea of actions isn't gone. I just want a stronger distinction between what you pass to repo.push() and what you get as a result. Eventually, I want to be able to have Tasks manage multiple actions. A Task is composed of actions, and tracks their progress.

Related issues: https://github.com/vigetlabs/microcosm/issues/268

Codecov Report

Merging #271 into master will not change coverage.
The diff coverage is 100%.

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

I'm going to close this out and send out some more focused PRs. There's no way I'll ask anyone to review 100 files.


PCC Vivace

Is the Vivace code in the master branch, or should I work from the NSDI-2018 branch to review Vivace utility implementation?

The PCC-Vivace code is in the master branch. The CalculateUtility function in https://github.com/PCCproject/PCC-Uspace/blob/master/src/pcc/pcc_monitor_interval_queue.cpp is where you can see the exact utility computation. I'm working to move this to a separate file so it's easier for others to view, understand and modify.

Thank you @nathanhjay


refactor: introduce new feature loading mechanism

Brief Information
This pull request is in the type of (more info about types):

[ ] build
[ ] ci
[ ] docs
[x] feat
[ ] fix
[x] perf
[x] refactor
[ ] test

Related issues (all available keywords):

resolve #534

Details

As discussed in #534, the mechanism underpinning the feature managing of refined-github sets a good example for Hypercrx so I decided to get the best of the mechanism by looking into the codebase and trying my best to find out which part of the code is necessary for Hypercrx and which is not.
Actually it is not an easy task because there are so many issues and PRs as well as much code that should be read and understood to figure out exactly how the mechanism works. At the moment (when this draft PR is created), I have wrote a basic feature-manager that is derived from refined-github and half-refactored one of the features in Hypercrx. Both the feature-manager and the half-refactored feature are not complete and they will be improved in following commits, while I think it's not a bad time to explain a bit on the code changes.
Before the code explanation, which will be provided as review comments, I want to give some information on how GitHub handles page navigations after this summer. The concept is really important and all extensions trying to work with GitHub should take it into consideration. After all, the sudden change of page navigations this summer strongly affected both Hypercrx(#382) and Refined GitHub(https://github.com/refined-github/refined-github/issues/5895).
Let's get started. When you navigate between GitHub pages, such as from a repo page to a profile page, or Issues tab to Pull requests tab, have you ever noticed a blue progress bar at the top:

The progress bar indicates that you are experiencing a turbo:visit rather a page reload. There is a high chance that GitHub uses hotwire/turbo to speed up their websites. Turbo in short:

Turbo is fast because it prevents the whole page from reloading when you follow a link or submit a form. Your application becomes a persistent, long-running process in the browser.

The screenshot below can help you figure out what does it mean:

Conclusion 1: navigating from Code tab to Issues tab doesn't mean a page reload so your extension(contentscript especially) will not be rerun.
What if going forward/back in browser history? The truth is, if you go to Issues tab from Code tab then click the "go back" button in browser, the cached Code tab page will be restored from memory and shows up right away, which behaves differently compared with clicking Code tab link to go back to Code tab page. The former restores the preserved DOM elements while the latter starts a new request to get the content from servers.
Conclusion 2: clicking "go back" button to visit a tab is not the same as clicking a tab link to visit that tab.
The two conclusions form the way we think and the way we do, which should be always kept in mind. The feature-manager should handle these gracefully.
Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA

Others

At this point, repo-activity-openrank-trends has been refactored with a new feature manager and I think the new mechanism is also applicable to other features that will be soon refactored in this way (in new PRs, otherwise this PR will be too big to read).
There is another thing should be pointed out: the user configuration mechanism is still in its old way, in which each feature instantiates its own settings to control options like zh/en. The idea is bad I think, there should be only one instance of Settings and it should be controlled by the feature manager rather each feature itself.
A more proper configuration mechanism will be worked out later.

Hi @wxharry, it could be great if you can read and review this PR for every technical detail. Since the PR is really important and it is also a refinement of the AVC strategy.
If you have any question, please leave a comment here or even message me directly at Slack/Wechat.

I think this pr is more like a refacting, not a feature. I suggest we change the title to:refactor: introduce new feature loading mechanism. What do you think? @tyn1998

Sure, thanks for your advice. I've changed it.


ERROR: USER_NOT_FOUND

Hello,
I try to go in localhost:8080/login but i have "WRONG_CREDENTIALS"
so i tried with this link localhost:8080/login?name=Admin and the same thing happens "WRONG_CREDENTIALS"
what did i miss ?

Hey,
You need to send a form-data payload with a POST request to /login
You can use https://www.postman.com/ to create such a request, for example, but curl should also work: https://davidwalsh.name/curl-post-file

Hey,
You need to send a form-data payload with a POST request to /login
You can use https://www.postman.com/ to create such a request, for example, but curl should also work: https://davidwalsh.name/curl-post-file

Ok ty, it's all good :)

Ok ty, it's all good :)


IOCTL_ATA_PASS_THROUGH_DIRECT

[Enter feedback here]

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

ID: 4076dd23-433e-2ec1-789a-e70b2e447fb7
Version Independent ID: c9a5dc47-62e4-bdb9-b28d-aa1d6d0c78d1
Content: IRP_MJ_DEVICE_CONTROL
Content Source: windows-driver-docs-pr/kernel/irp-mj-device-control.md
Product: windows-hardware
GitHub Login: @windows-driver-content
Microsoft Alias: windowsdriverdev

Hi, @wanghao19901024
Was there a question or comment about this topic?


chore: update workflow

???

PR-Codex overview
This PR focuses on updating the GitHub Actions workflow for npm package management, specifically enhancing package information retrieval and installation verbosity.
Detailed summary

Added a step to list package information using npm info in JSON format.
Changed the npm install command to include the --verbose flag for more detailed output.
Removed the previous step for installing the npm package without verbosity.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

the description would be the why


⚠ Bofrost.be has degraded performance

In 677aac2, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1966 ms

Resolved: Bofrost.be performance has improved in c9e1219.


C++ interop

I guess you should mention extern(C++).  You can use dpp to #include C++ headers if you blacklist STL and Boost types and it will work for quite a lot.  It's still not complete yet but it keeps getting better and in a year or two STL should be fine.  It's used in production but it's not something I would say is easy for just anyone to use and expect to work immediately.  For C++ - C mostly just works.
Can you do that now using Nim?  Just include c++ headers and use them?
How about generating c++ headers from Nim code?  We do that in D but the available options aren't yet polished.

PR's welcome to update this section (especially with the latest D work on extern(C++), but it deserves a whole entry on its own; this is something I've been very interested in myself, and for which I contributed both in D (see https://github.com/Syniurge/Calypso) and in Nim (see https://github.com/nimterop/nimterop: Nimterop is a Nim package that aims to make C/C++ interop seamless)
the answer is a bit complicated and more nuanced than https://github.com/timotheecour/D_vs_nim/issues/30.
For example you can do the same as for https://github.com/timotheecour/D_vs_nim/issues/30 but with C++ (importcpp and emit still apply to C++):
proc foobar() {.importcpp.}
{.emit:"""
#include <stdio.h>
void foobar(){
  printf("in foobar\n");
}
""".}

however this won't work with templates (unless explicitly instantiated); and also still requires defining headers manually;
this is what nimterop (and to a lesser extend the "official" c2nim) aim to fix: wrapper free interop. Templates (that aren't instantiated) aren't yet supported in nimterop. My understanding is this isn't also supported in D (unless you use Calypso)
relevant links

https://github.com/nim-lang/Nim/issues/10578
https://github.com/nim-lang/Nim/issues/8327
https://github.com/Syniurge/Calypso
https://github.com/nimterop/nimterop


Implement graceful shutdown for http3 servers.

Fix 6195 for caddy.

@marten-seemann Do you time to take a look at this draft?

@marten-seemann When do you think this patch is ready to be reviewed? I haven't updated it in a while, and several of those enhancements already landed in the latest release. If you think it's ok to add graceful shutdown, I'll update this patch against the latest release.

Sorry, I dropped the ball on this PR. Let's get this into the next release! I'll review it later.

I refactored the tests in https://github.com/quic-go/quic-go/commit/e933c80ada58eba408722e912f0a9cf094f27ecf. Also, it looks like we should probably merge #4689 first. Does this make sense @WeidiDeng?


Instructions to override semantic ui theme in target

Allow a target to load a new theme for semantic ui.

[ ] setup custom theming for target (in sample target)
[ ] document procedure to setup new theme

@pelikhan This is done right?


The leaderboard is missing in https://paperswithcode.com/sota/text-classification-on-yelp-polarity

The leaderboard is found to be removed already by officials, closed...


Backports to 1.1.latest

Description
Backports two commits to 1.1.latest.

Use insert overwrite for the first batch of seed (#149)
Explicitly close cursors (#163)

Thanks! merging.


Reflect the parsing rules for src and alt attributes on img elements

Parsing a u- property should return the result of "parse an img
element for src and alt" in case the element is a img tag with a
src attribute. Based on this sub section img tags with a alt
attribute should result in a new structure, containing a value and
alt property.

http://microformats.org/wiki/microformats2-parsing

This mr updates all tests subject to this rule in order to reflect this.
!!! This mr does not include any updates to the v1 tests nor did i
check if any changes to are needed, as i'm not be familiar with v1
parsing rules !!!

See discussion about the spec change and experimental test in mf2py.

Looks good. Thanks, @jansauer!


Tour of F#

This is the first article/tutorial which addresses some of the holes we have in our F# conceptual content.  The code sample which is extensively pulled from in the article is a modified version of the F# Tutorial project that ships in VS.
I'd love to get feedback, particular on the flow of the content.
/cc @BillWagner @dsyme

I really like this.
I left some comments so we have consistent style between F# and C# docs, and some questions that rose in my mind as an F# n00b while reading.

OPS build error is very strange here:

It doesn't give me a line number, and from what I can tell, all my links adhere to the code snippet guidelines.

@cartermp Can you add that information here: https://github.com/dotnet/docfx/issues/450

I haven't added snippets yet so don't know what could be wrong. :cry:

Looks like the build is successful now. @mairaw @cartermp

There's still one warning about a snippet

@mairaw @cartermp can you stage this and see if it shows or not?

Since this was done on a fork, we have to merge to stage. I recommend that we work from the repo branches to be able to stage the content earlier for future changes.

Then I would just merge this into master and then update from there. The same pattern we used for visualfsharpdocs.

@dend sounds good.


[Key Request] Table 6651 "Return Shipment Line" - Two new keys

For page sorting we need two new keys with Standard fields only. Currently it is not passible to use a table Extension to create new keys on existing tables.
The new keys are:
1. First key
Buy-from Vendor No.,Type,No.
2. Second key
Pay-to Vendor No.,Type,No.

In general we do not add keys for partner extensions. Please provide justification why do you need this key.

We are going to deliver possibility for partners to add table keys soon. Closing this old request for now.


Geolocator.getCurrentPosition() not returning location sometimes

🐛 Bug Report
Sometimes, Geolocator.getCurrentPosition() returns location and sometimes not. Even though I tried to add null check but I am getting warning.
Expected behavior
Either it should not be null at any cost or there must be a way to check if function returned null or not.  How to handle if locations are not fetched. How to perform null check?
Reproduction steps
final curLoc = await Geolocator.getCurrentPosition();
     if (curLoc != null ) {
       // perform further stuff
     }else{
   print("Unable to fetch location");
    }

Configuration
Flutter Doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.3.10, on macOS 12.6 21G115 darwin-x64, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✗] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
        sudo xcodebuild -runFirstLaunch
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To install see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] VS Code (version 1.72.2)
[✓] VS Code (version 1.72.2)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

! Doctor found issues in 1 category.

Version: 9.0.2
Platform:

[ ] :iphone: iOS
[ ] :robot: Android

I also faced this issues. Do i need to setup Geocoding API KEY ?

I just commented on a similar issue. Maybe you can check it out if it work for you?
https://github.com/Baseflow/flutter-geolocator/issues/1191#issuecomment-1386359620

I face it too, even though I have added timeLimit ,  it will just timeout but never return position from native

I face it too, even though I have added timeLimit , it will just timeout but never return position from native

You can use getLastKnownPosition if TimeOutException was thrown.

For me this is occurring only on the IOS build.
I don't how but calling the same function twice fixed the issue for me in the IOS build
For ex -
log(await Geolocator.getCurrentPosition(           desiredAccuracy: LocationAccuracy.best).toString());     Position pos = await Geolocator.getCurrentPosition(           desiredAccuracy: LocationAccuracy.best);

Had the same issue. Works fine on android but while running on iOS getCurrentPosition() doesn't return anything.

get same problem, this occurred after migrating to latest

I had this problem too. any fix?

In my case, I had to use Geolocator.getLastKnownPosition() instead

Hi @chirag-chopra and other people that provided helpful comments, thank you for taking the time to open and discuss this issue!
Extra information helps to speed up investigation into issues. A minimal code example would be ideal. You can create one by creating a new flutter project, editing main.dart so it showcases your issue, and adding the contents of main.dart in a comment here. It is also interesting to find out under what circumstances you are experiencing this problem exactly. I see OP has not set up iOS development, so I am assuming that you are using Android. Other commenters have mentioned iOS having the problem, instead of Android. I would like to confirm whether this issue exists on both platforms, or whether there are two separate issues that occur on any one platform. Also, are you running your application on an emulator or on a physical device?
Looking forward to hearing from you!

My project started 2-3 months ago or so.
Justr came back to develop and update something.
One of the libraries asked for Android 19 min version. I gave it.
After that I see I don't get the location.
Now I am testing with Android 13 phone, with permissions given ( and no code change)
Here is where the code is waiting:

For me this is not really acceptable: one of the basic functionality of the app is broken by a library.
So better get out from Flutyter and go native, because the development price it is less than debugging libraries!!!

Possible duplicate of #731, #949, #1114

getLastKnownPosition

Yes, this is the answer since apple doesn't want us to getCurrentPosition twice


hasFlowFinishedSuccessfully can return false?

Hi,
On InAppReview.RequestInAppReview will hasFlowFinishedSuccessfully return false if the user has already rated the app?
I'm not seeing this information explicitly anywhere... sorry if it's duplicate...

No problem,
same issue here:
https://github.com/MinaSamir11/react-native-in-app-review/issues/8
You have to save date when flow launched and prompt dialog from time to time, if user rate or not and ask user to review according to guidelines for each platform avoiding limited quota issue please read doc.
https://github.com/MinaSamir11/react-native-in-app-review#system-rating-and-review-prompts
https://github.com/MinaSamir11/react-native-in-app-review#quotas

Ah yes! I missed that one.
Thank you for pointing it.
And thank for the reply!


Added Nested Comments Project #416

Title and Issue number

Title : Nested Comments
Issue No. : #416
Code Stack : React
Close #<issue_no>

# Checklist:

[X] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md
[] I have updated the Index.html file for my contribution

@Akshayone8 can we also have reply & delete options

@sadanandpai Added reply and delete feature.

There are conflicts. The comments reply is not working properly. Some comments after adding are not showing up but shows after cancel click

@sadanandpai "Thank you for your patience. I've addressed the issue with the comments reply functionality and made the necessary changes. Please try using it again, and let me know if the problem persists or if you have any further feedback. Your input is valuable in ensuring a smooth user experience."
https://github.com/sadanandpai/frontend-mini-challenges/assets/62467248/5d398220-0264-45f9-a981-8818f6d59a05

Title : Navbar
Issue No. :
Code Stack : React
Close #<issue_no>
@sadanandpai Added new React challenge - Navbar

conflicts @Akshayone8

@Akshayone8 conflicts

Hi @sadanandpai I have resolved the conflicts can u verify now.

@Akshayone8 There is a major bug
https://github.com/sadanandpai/frontend-mini-challenges/assets/12962887/c1f40b6c-b2dc-4976-a288-c637466fecf8
Also can you plz make enter key to work after typing

A squash and merge could keep the commit history clean...


Do not display primary uri in related content.

Fixes
Issue Number: https://github.com/lbryio/lbry-desktop/issues/6434

What is the current behavior?
The primary uri (content being played) can appear as related.
What is the new behavior?
The primary uri is filter out from related.
Other information

PR Checklist

Toggle...
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[ ] I added a line describing my change to CHANGELOG.md
[x] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

wanna take another stab at this?


scapy-python3 -> scapy

That's not obvious, but this is scapy: https://pypi.org/project/scapy/
and this isn't: https://pypi.org/project/scapy-python3/ (that's scapy3k undercover 😄 )

Thanks, fixed!


Release Rust crates

Can you please release magika crate for rust soon? We have a project on container image that needs to experience this dependency library. Thank you for your commitment to open source! (:з」∠)

@Menguozi: we are getting there! We should be able to release the first -rc release by next week, and we'd love to get some feedback :-)

This commit has been published to crates.io.
Because it is a pre-release, one needs to explicitly ask for this version (cargo doesn't select pre-releases):

To install the CLI: cargo install --locked<EMAIL_ADDRESS>To use the library: magika = "0.1.0-rc.0"

Note that there should be a 0.1.0-rc.1 coming up by next week (which should be a non-breaking change because only the model would change).


feat: update lowcode-engine version to 1.0.8

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.liujuping seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.