cmake executable path is saved and works from shell but Bad CMake executable error remains

Brief Issue Summary
after adding settings.json with the content below to the project, the plugin does still not find cmake but the same path works from the shell.
{
"cmake.cmakePath": "/opt/apps/resif/iris/2020b/broadwell/software/CMake/3.18.4-GCCcore-10.2.0/bin/cmake"
}
The bug happens in a university cluster environment where I have no sudo permissions. Cmake is loaded as software module (easybuild) from within the terminal of a vscode remote session
CMake Tools Diagnostics

(base) 0 [ggg@ggg bin](2644620 N/T/CN)$ module load devel/CMake/3.18.4-GCCcore-10.2.0
(base) 0 [gggy@ggg bin](2644620 N/T/CN)$ `CMake: Log Diagnostics`
bash: CMake:: command not found
(base) 127 [ggg@ggg bin](2644620 N/T/CN)$ CMake: Log Diagnostics
bash: CMake:: command not found
(base) 127 [ggg@ggg bin](2644620 N/T/CN)$ which cmake
/opt/apps/resif/iris/2020b/broadwell/software/CMake/3.18.4-GCCcore-10.2.0/bin/cmake
(base) 0 [ggg@ggg bin](2644620 N/T/CN)$

Debug Log

<!-- Paste the debug log contents HERE -->

I updated settings.json as follows (added cmake logging):
{
"cmake.cmakePath": "/opt/apps/resif/iris/2020b/broadwell/software/CMake/3.18.4-GCCcore-10.2.0/bin/cmake",
"cmake.loggingLevel": "debug"
}
Loaded the cmake module on the remote node via a tunnel (from ubuntu terminal outside vscode)
Opened a local vscode instance and use the remote development plugin to connect to the compute node
Opened the project folder
Vscode printed output:
[main] Safe constructing new CMakeTools instance
[variant] Constructing VariantManager
[main] Constructing new CMakeTools instance
[main] Starting CMakeTools second-phase init
[variant] Loaded new set of variants
[main] CMakeTools instance initialization complete.
[kit] Reading kits file /home/users/pantony/.local/share/CMakeTools/cmake-tools-kits.json
[kit] Successfully loaded 1 kits from /home/users/pantony/.local/share/CMakeTools/cmake-tools-kits.json
[kit] Not reading non-existent kits file: /home/users/pantony/vscodeRemote/cppRemote/.vscode/cmake-kits.json
[main] Injecting new Kit into CMake driver
[extension] Configuring workspace on open file:///home/users/pantony/vscodeRemote/cppRemote
[main] Configuring folder: cppRemote
[main] Saving open files before configure/build
[cache] Reading CMake cache file
[cache] Cache file does not exist: Returning empty cache data
checking from vscode terminal if cmake is available (and seeing that it is not available):
(hcs_20220301) 0 [ggg@ggg](2645404 N/T/CN)$ which cmake
/usr/bin/which: no cmake in (/mnt/irisgpfs/users/pantony/.vscode-server/bin/c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1/bin/remote-cli:/home/users/pantony/miniconda3/envs/hcs_20220301/bin:/home/users/pantony/miniconda3/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/share/lmod/lmod/libexec:/home/users/pantony/.local/bin:/home/users/pantony/bin:/usr/share/lmod/lmod/libexec)
checking from ubuntu terminal if cmake is available in tunnel (yes it is)
(hcs_20220301) 0 [ggg@ggg ~](2645404 N/T/CN)$ which cmake
/opt/apps/resif/iris/2020b/broadwell/software/CMake/3.18.4-GCCcore-10.2.0/bin/cmake
Anyway trying to build project in vscode cmake tool
Error1: Build failed: Unable to configure the project
Error2: Bad CMake executable: "/opt/apps/resif/iris/2020b/broadwell/software/CMake/3.18.4-GCCcore-10.2.0/bin/cmake". Check to make sure it is installed or the value of the "cmake.cmakePath" setting contains the correct path
Loading module again in vscode terminal (now vscode can find it at least in the terminal)
(hcs_20220301) 0 [ggg@ggg cppRemote](2645404 N/T/CN)$ module load devel/CMake/3.18.4-GCCcore-10.2.0
(hcs_20220301) 0 [ggg@ggg cppRemote](2645404 N/T/CN)$ which cmake
/opt/apps/resif/iris/2020b/broadwell/software/CMake/3.18.4-GCCcore-10.2.0/bin/cmake
Trying again to build with cmake plugin in vscode
Error1: Build failed: Unable to configure the project
Error2: Bad CMake executable: "/opt/apps/resif/iris/2020b/broadwell/software/CMake/3.18.4-GCCcore-10.2.0/bin/cmake". Check to make sure it is installed or the value of the "cmake.cmakePath" setting contains the correct path
Sharing thoughts with you:
-It seems that the cmake module loaded outside of vscode is not visible from vscode
-Loading the module from the vscode terminal does not fix the problem and that let's me believe that vscode needs to find cmake at vscode instance launch
-Are my thoughts correct?
-How can we make the loaded cmake module visible to the remote vscode session at the moment of it's initialization?

Unfortunately, changing the environment in the VS Code Terminal so that it can find your version of CMake does not update the environment that the extension runs in.  Does updating your .bash_rc or .profile to load the module allow the environment to be set up initially when VS Code connects remotely?
I'm not sure that there's anything we can do in our extension to fix this.  This looks more like an issue for the Remote extension to try to help you with.  I would recommend asking the question here: https://github.com/microsoft/vscode-remote-release/issues/new/choose

Good news: Loading the cmake module via .basrc on the remote machine solves the problem and cmake is now found at startup of the remote vscode session. Thanks for the fast and helpful feedback.
Status and next steps:

Building and running a simple hello world program now works fine via cmake-tools
Triggering debugging from the cmake-tools plugin gives the following error:

The program '/home/users/ggg/vscodeRemote/cppRemote/build/main' has exited with code 42 (0x0000002a).
ERROR: Unable to start debugging. Unexpected GDB output from command "-interpreter-exec console "set env BASH_FUNC_module() () {  eval $($LMOD_CMD bash "$@") && eval $(${LMOD_SETTARG_CMD:-:} -s sh)
}"". Problem parsing arguments: interpreter-exec console "set env BASH_FUNC_module() () {  eval $($LMOD_CMD bash "$@") && eval $(${LMOD_SETTARG_CMD:-:} -s sh)

Please let me know if you prefer that I edit the github issue title ("Setting up vscode-cmake-tools for remote debugging on a cluster") or if you prefer me to open another issue ("gdb cannot start debugging in cmake-tools remote session").
PS: gdb version on remote machine: GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7

Could it be that some more environment variables need to be set on the remote machine via .bashrc for enabling remote debugging via cmake-tools?

For the time where you are going to working on #2442, I will use the following workaround for debugging:

build with cmake-tools
use the following launch.json for Run>StartDebugging:
{
"version": "2.0.0",
"configurations": [
{
"program": "${workspaceRoot}/build/main",
"name": "Debug",
"type": "cppdbg",
"request": "launch",
"cwd": "${workspaceRoot}",
"preLaunchTask": ""
}
]
}
see also:
https://vector-of-bool.github.io/docs/vscode-cmake-tools/debugging.html#debugging-launch-json


Groceries marked as personal care

Great tool, thanks!
My groceries (a lot of Amazon Fresh these days) are all being marked Personal Care. Including really obvious things like apples.
I looked a little at category.py and saw that you had a note about it. Do you have suggestions for modifying category.py? Right now I'm stuck manually reclassifying ~1000 items and I don't want to do that.

Hi @nchernia, glad your finding this tool to be useful!
The good news is that this should be pretty easy to fix! I don't use Amazon fresh, so I don't really have any good sample data to reference when I was revamping the categories. If possible, would you be able to send me<EMAIL_ADDRESS>an anonymized version of your items amazon report? Feel free to delete all your personal details from the relevant columns. You can also delete any rows that are private. I really only need the UNSPSC and description columns.
Thanks!

Hi @nchernia, glad your finding this tool to be useful!
The good news is that this should be pretty easy to fix! I don't use Amazon fresh, so I don't really have any good sample data to reference when I was revamping the categories. If possible, would you be able to send me<EMAIL_ADDRESS>an anonymized version of your items amazon report? Feel free to delete all your personal details from the relevant columns. You can also delete any rows that are private. I really only need the UNSPSC and description columns.
Thanks!

Okay, release 1.33 should do the trick! I'm not sure how you were using the tool, but if it's a prebuilt version, take a look at the releases page. I would recommend reusing the same orders/items files you've already downloaded, but then selecting the retag option, which should try to recategorize these for you (otherwise, the tool will try to skip things it thinks it has already tagged).

Okay, release 1.33 should do the trick! I'm not sure how you were using the tool, but if it's a prebuilt version, take a look at the releases page. I would recommend reusing the same orders/items files you've already downloaded, but then selecting the retag option, which should try to recategorize these for you (otherwise, the tool will try to skip things it thinks it has already tagged).

The pre built binary (dmg) is not working - opens then immediately closes. I'm going to try from source.

OK going through pip didn't work either. Even just running help returns an error.
mint-amazon-tagger --help
Traceback (most recent call last):
File "/Users/nchernia/anaconda3/bin/mint-amazon-tagger", line 6, in
from mintamazontagger.main import main
File "/Users/nchernia/anaconda3/lib/python3.6/site-packages/mintamazontagger/main.py", line 30, in
from mintamazontagger import tagger
File "/Users/nchernia/anaconda3/lib/python3.6/site-packages/mintamazontagger/tagger.py", line 36, in
None, None, None, None, None, None))
TypeError: namedtuple() got an unexpected keyword argument 'defaults'

Well that is certainly not helpful :-P Thanks for the report!
I probably won't have a chance to look into this until this evening, but it appears to all be self contained within the tool.

Might be Python 3.6 vs 3.7

That seems to be the problem, I changed the Python 3.7 after some amount of work and it's fine. Found it referenced in another repo. https://github.com/yzhangcs/parser/issues/15

@nchernia , you're right on the money re: Python 3.7. However, I'm still surprised the dmg didn't work for you. It should contain its own python version, which should prevent these sorts of issues or for people who think python is a snake.
Would you mind reporting back if the dmg version works now that you also updated to 3.7?

The DMG still doesn't work, it fails to open. I changed my Python environment using pyenv; would make sense that Python should be included in DMG.
Some other notes:

the CLI Mint tagger says it will prompt for Mint email and password if not given, but does not; I'd rather be prompted for a password, especially
I'm still having trouble with the retag and I wonder if it's because the software thinks that I put those categories in? Things like apples and Pepperidge Farm goldfish crackers are still listed as Personal Care.

"Transactions with personalize categories: 1309" <--- I think it's not retagging these?

Thanks for all the detailed info! This is all very useful. What version mac OS are you running? I'm on big sur and concerned I won't be of much help trying to get the dmg to work.
I'll look closer at the CLI issue in a bit.
Good catch on the personalized categories! I'm impressed you noticed that. Please try:

GUI: check booth the "retag" checkbox and the "Do not predict categories" checkbox
CLI: add both --retag_changed --do_not_predict_categories

Since I changed the "system default" categories for the tool, it's noticed that your mint data doesn't match what the tool now thinks they should be by default, and therefore thinks you personally chose those categories. As such, it's trying to predict what you'd want instead based on your past behavior. In this case it's a bit odd, as it's not really your behavior. Anyway, those flags should actual nuke it by disabling the category prediction logic.


Update azure-vmware-solutions-limits.md

Added VMware SRM configuration limits to this central location from https://docs.microsoft.com/en-us/azure/azure-vmware/disaster-recovery-using-vmware-site-recovery-manager

@rvandenbedem : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Error uploading data from Github

Overview
I'm not sure if this is an error or not, but I think there was last of warning in a process that could lead to problems.
I tested uploading this CSV table to ODE: https://github.com/anacarolinamoreno/educacao_infantil_pandemia/raw/refs/heads/master/data/matriculas_por_escola_2020.csv
I got an error saying it was a valid file.
I tried a second time. Same error.
On neither attempt there was a new table showing on the left column
But then I saw that ODE saved a copy of that table to the local folder. So I had two copies there. When I closed and reopened ODE, both tables showed up on the left column, but with a black dot (not green or red). When I click to preview on ODE it just loads eternally and I have to shut it down and start over.
My files aren't small but not very large (34,4Mb). But if I was trying to do this with a larger file, then probably I could run into disc space problems by trying several times to open an online file while ODE is making copies of it on every single attempt.

@romicolman
Can confirm that problem but it's specific to this exact file, in-general, uploading works fine. We need to investigate

Ok, perfect. I'll add it to our next sprint.


Measurement prober unit test

Draft
TODO:

update BUILD
rebase after metric creation and publication logic is merged
how to mock privateKeyDerFile
do we want to verify metrics or OpenTelemetry for each test case
does it make sense to make run() return Measurement?
what other cases and functions need to be tested? remember we want to test the interface, not the implementation

This change is


fix: ensure correct balance per account is shown

This PR addresses some issues with incorrect STX account balances being shown

add filtering to signers by account index
ensure we update the accountIndex for stacks when initialising stacks signers
roll back update to new market data service for STX as price is incorrect precision

I will add unit tests for account generation but opening for initial review
Here is a demo of loading the dev wallet and creating some accounts:
https://github.com/user-attachments/assets/c737e6b3-d480-48ce-9e69-50d0c52e324e
NOTE
There is still some weird janky and false positive balances appearing when switching accounts which seems to be related to BTC balances. Here you can see an empty account having a $0.06 cent balance when another account is entered
https://github.com/user-attachments/assets/fc69b963-f402-4095-ba44-c7934ea55652

Tagging this with needs:build to create a demo for QA. Ideally I will first merge https://github.com/leather-io/mono/pull/645 then this PR and have a demo of both available


Move CI to GitHub Actions

Pull Request Test Coverage Report for Build 415479887

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 32.422%

Totals

Change from base Build 7833:
0.0%

Covered Lines:
2320

Relevant Lines:
6594

💛  - Coveralls


RFC: Support dynamic reconfiguration of "buckets"

/area API
/kind feature
I mentioned this in slack, but given that we already support being promoted to and demoted from "leader" dynamically, could we support dynamically changing the bucket count by:

Demoting all the current buckets,
Promoting new buckets as we gain ownership of them.

I haven't looked deeply into what this would entail at a code level yet, but I wanted to float the idea for broader discussion.

@mattmoor @dprotaso could we re-open that issue ? I think it's still a valid thing to work on 👼🏼

/reopen
/lifecycle frozen


babi_rnn and babi_memnn example failed in python3.7

I have Python version 3.7.0. When I run babi_rnn and babi_memnn examples, this function is failed:
def tokenize(sent):
    '''Return the tokens of a sentence including punctuation.
    >>> tokenize('Bob dropped the apple. Where is the apple?')
    ['Bob', 'dropped', 'the', 'apple', '.', 'Where', 'is', 'the', 'apple', '?']
    '''
    return [x.strip() for x in re.split(r'(\W+)?', sent) if x.strip()]

In Python 3.7,
re.split(r'(\W+)?', 'Bob dropped the apple. Where is the apple?')

returns
['', None, 'B', None, 'o', None, 'b', ' ', '', None, 'd', None, 'r', None, 'o', None, 'p', None, 'p', None, 'e', None, 'd', ' ', '', None, 't', None, 'h', None, 'e', ' ', '', None, 'a', None, 'p', None, 'p', None, 'l', None, 'e', '. ', '', None, 'W', None, 'h', None, 'e', None, 'r', None, 'e', ' ', '', None, 'i', None, 's', ' ', '', None, 't', None, 'h', None, 'e', ' ', '', None, 'a', None, 'p', None, 'p', None, 'l', None, 'e', '?', '', None, '']

and will raise an AttributeError: 'NoneType' object has no attribute 'strip'

I ran into the same issue and just changed the return statement to the following:
return [x.strip() for x in re.split(r'(\W+)?', sent) if x and x.strip()]

Hi @NaNAGISaSA and @anthonyhsyu, if you check keras website and documentation, it's written: "Keras is compatible with: Python 2.7-3.6.".
I guess that's the reason why you are facing those issues, the frameworks was not test, neither supports Python 3.7. Could you check if this is the reason? If yes, should we close this issue as it works as expected?

@fbdo Thank you, I will close the issue.


Allow a list of additional systemd dependencies

... /requirements for e.g GPFS or other storage services
Testing:
An example test would be to take the ansible public user example like: https://github.com/ome/ansible-examples-omero/tree/master/public-user
And apply the following diff:
     - role: openmicroscopy.omero-server
       omero_server_release: 5.4.1
+      omero_server_systemd_limit_nofile: 16384
+      omero_server_systemd_after:
+      - gpfs.service
+      - another.service

Then check that the systemd unit file generate includes:
(/etc/systemd/system/omero-server.service)
After=another.service
After=gpfs.service

Ref docs: https://www.freedesktop.org/software/systemd/man/systemd.unit.html#[Unit] Section Options

Think there's a slight copy-n-paste error in your description if you'd like to take a look. (One +      omero_server_systemd_limit_nofile: 16384 too many)
In general, this makes sense to me. How do we go about actioning the tests? and then, propose as 2.1.0?

Thanks for noticing. If you think it's something I could add to Travis, happy to learn that then all we'd need would be for someone to eyeball Travis?
I do use a very heavyweight method when developing these (i.e. spinning up a Vagrant and running the whole playbook).

Created a sibling PR for https://github.com/openmicroscopy/ansible-role-omero-web/pull/14 so we can make similar customizations to the OMERO.web systemd unit file.

Looks fine. You've got an ansible-lint error.


Left Arrows displayed improperly while Right Arrows

environment

vim: 8.1
vim-airline: git a0e9b38
OS: Arch Linux
Have you reproduced with a minimal vimrc: yes
What is your airline configuration:

set encoding=utf-8
set fileencoding=utf-8
set fileencodings=ucs-bom,utf-8,cp936,gb18030,big5,euc-jp,euc-kr,latin1
set nobomb
set fileformat=unix
set fileformats=unix,dos,mac
set ambiwidth=double

call plug#begin()
Plug 'vim-airline/vim-airline'
Plug 'vim-airline/vim-airline-themes'
call plug#end()

" Airline
let g:airline_theme='luna'
let g:airline_solarized_bg='dark'
let g:airline#extensions#tabline#enabled = 1 "Show tabs if only one is enabled.
let g:airline#extensions#tabline#show_splits = 1 "enable/disable displaying open splits per tab (only when tabs are opened). >
let g:airline#extensions#tabline#show_buffers = 1 " enable/disable displaying buffers with a single tab
let g:airline#extensions#tabline#tab_nr_type = 1 " tab number
let g:airline#extensions#tabline#formatter = 'default'
let g:airline#extensions#tabline#switch_buffers_and_tabs = 1
let g:airline_powerline_fonts = 1

if you are using terminal:

terminal: terminator
$TERM variable: xterm-256color
color configuration (:set t_Co?):256
if you are using Neovim:no
does it happen in Vim: yes

actual behavior
Left Arrows display improperly while Right Arrows
The first character after the left arrow has weird color.

When I selected the first character after the left arrow, the color display properly.
I suppose the first character after the left arrow has reversed color.
expected behavior

I have confirmed that this problem reproduces.

@Sicalxy
I think that this problem can be solved by turning off set ambiwidth=doubleor  setting set ambiwidth=single.
Please try this.

Thx a lot! @kazukazuinaina
I found set ambiwidth=double should be set with left/right separators of double byte characters
set ambiwidth=double
let g:airline_left_sep = '⮀'
let g:airline_left_alt_sep = '⮁'
let g:airline_right_sep = '⮂'
let g:airline_right_alt_sep = '⮃'

However, since the fonts do not always fit, so I just turned off set ambiwidth=double.

@Sicalxy Thanks
Resolved.


Feature request - Simple CLI access for specifying files

I'd love to be able to use this as a rename utility from a file browser such as nemo.
In nemo in particular, you can select multiple files to rename, then press F2 and then the list is populated with those files/folders.
It requires something like this command:
szyszka %F

where %F would be a list of N items.
Some examples of other rename utilities which work like this are thunar --bulk-rename, krename and gprename.
I'm not asking for a full CLI interface as I see there currently isn't one.
Instead I was hoping this would be relatively simple to implement.
Thanks!

I'd like to use it from thunar custom actions, we need that feature.
Thanks!


[20.09] php74: 7.4.11 -> 7.4.12

Motivation for this change
Backport of #102715
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Thanks @etu :tada:


Curve filling issue

Hi,
I am not sure if this changed after I made an upgrade. Now the curves are filled below the graph in the label area.. Not OK in this way?

BR,
Ilkka

This was already reported in #4450 and already fixed in master so it will be in the next release.


Default Reply

Hi
As of now chatbot repeats the statement which it can't map to the database. Suppose it doesn't have a mapping for "Hello", it would throw back hello in reply as well. What I want to do is, for all the matches it can't find, it should give a default reply like "not found" or something. Any help ?
P.S. I've turned off the learning.

There is not currently a way to set a default response. Having a default response prevents the chat bot from learning new responses (even when it responds incorrectly). It is not likely that this is something that will be added in the future.

Since there's an option to turn off the learning, I thought this is something that's achievable. Can you at least tell me, how does it give the same response if it can't find the map to it. Let's say there is no map for "Mercedes", it returns "Mercedes" back, how does it do that ?

If no responses are known, there is an internal logic adapter that returns the input statement: https://github.com/gunthercox/ChatterBot/blob/master/chatterbot/adapters/logic/no_knowledge_adapter.py


Additional characters in JSON exports for colors

Hi Lukas!
I'm noticing an extra ff at the end of colors in the json on exports. In the example, the red #c13434 is exported to JSON as "value": "#c13434ff"
Any idea where the extra ff is coming from? Is it my Figma setup, or something with the plugin? Is it possible to export without the trailing ff?
Apologies if I've set something up wrong, but here is a link to a reduced test case: https://www.figma.com/file/Yc6mVikcSKhhEcqqWzeXVa/Color-Tokens-Test?node-id=0%3A1
And the json:
{
  "color": {
    "red": {
      "description": null,
      "type": "color",
      "value": "#c13434ff"
    },
    "blue": {
      "description": null,
      "type": "color",
      "value": "#34b9c1ff"
    }
  }
}

Thanks!

Thanks, @lukasoppermann and @devilcoders
We’ll find a way to show hex6—appreciate y’all


Failed to parse SourceMap in production mode

I'm using
Angular CLI: 7.3.2
Node: 8.12.0
OS: win32 x64
Angular: 7.2.6
There is a warning about source map in production mode that does not appear in development, I have followed the setup guide to create a diff-editor, additionally I have added in as monaco configurations:
const monacoConfig: NgxMonacoEditorConfig = {   baseUrl: '.assets',  };
What is shown in the console:

Also after creating the build inside dist/assets seems that min-maps folder is not there when it should be

What I could do to solve it?
Thank you,

I'm encountering the same  issue. Did you by anychance already found a solution?

In the 'node_modules/ngx-monaco-editor/' folder we can find the 'assets/min-maps/vs/editor'

The problem is that they are not copied in the angular application build.
Have you found any solution?

In the 'node_modules/ngx-monaco-editor/' folder we can find the 'assets/min-maps/vs/editor'

The problem is that they are not copied in the angular application build.
Have you found any solution?

In https://www.npmjs.com/package/ngx-monaco-editor in the setup installation it says to add in the angular.json file the following:
{
  "options": {
    {
      "assets": [
        { "glob": "**/*", "input": "node_modules/ngx-monaco-editor/assets/monaco", "output": "./assets/monaco/" }
      ],
      ...
    }
    ...
  },
  ...
}

What I did instead and for instance seems to work correctly:
{ "glob": "**/*", "input": "node_modules/ngx-monaco-editor/assets", "output": "./assets" },

The 'node_modules/ngx-monaco-editor/assets' folder contains the 'min-maps' folder.

There is no folder "min-maps" in my node_modules directory.

please any solution for this?
i am facing the same problem

why is in "min" files  looking for maps??


NIFI-5628 Added content length check to OkHttpReplicationClient.

Added unit tests.
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Will review...

@alopresto  @mcgilman   Looks good to me. Ran tests and confirmed in the logs that the DELETE request is re-written as Content-Length = 0 when replicated to the rest of the cluster. Still hangs on the node that receives the request but does not forward the bad DELETE request.

Thanks @thenatog! I'll also have a look.

Thanks @alopresto! This has been merged to master.


Data Race During --race Test

Probably needs proper mutexing - this one periodically causes flaking in CI for me. The items hitting it are:
github.com/gocql/gocql.(*tokenAwareHostPolicy).Init()  vs github.com/gocql/gocql. (*tokenAwareHostPolicy).updateReplicas()

It seems this is something that should be fixed in upstream gocql/gocql as it seems that upstream is affected too. I'll be happy to merge the fix upstream.

I've checked the code, but it seems gocql does not spawn goroutines using the policy before calling Init, so there shouldn't be any race. Do you by any chance reuse the policy instance between multiple sessions? Unfortunately I don't see from the screenshot where goroutine 61 was spawned, but it seems that it was spawned somewhere in Session.init, which is called after returning from tokenAwareHostPolicy.Init.

The issue is the assignment of the logger on line 401 during Init() can race with a use of the logger in the updateReplicas where it passes to getStrategy. The updateReplicas is getting called concurrently with the Init() because the schema event listener debouncer starts further up in the sequence, and if you do per-test schema operations, its possible to get into a state where one arrives during the race, because it's seeing stuff like the previous tests keyspace getting torn down.
	s.schemaEvents = newEventDebouncer("SchemaEvents", s.handleSchemaEvent, s.logger)

In short, if a schema update arrives during startup, you can get this. I believe without the race detector, it'll probably nil-pointer as the logger wasn't assigned.

The issue is the assignment of the logger on line 401 during Init() can race with a use of the logger in the updateReplicas where it passes to getStrategy.

But what leads to that? It seems that Init is called and returns before any connections are created, so how do you reach the Session.handleEvent that ultimately leads to updateReplicas?
Init is called in NewSession:
https://github.com/scylladb/gocql/blob/6aca262598eadfc2c433ac6f790fd8b6abf86f88/session.go#L161
There are no goroutines that gocql spawns until this point.
First connection is made in Session.init:
https://github.com/scylladb/gocql/blob/6aca262598eadfc2c433ac6f790fd8b6abf86f88/session.go#L181
The only explanation I have right now is that the policy instance is used with multiple sessions. Is that the case? Or why do we reach handleEvent? Could you please provide example code that reproduces the issue?

Multiple sessions, but each only created after the previous has been .Closed()'d. However, I can't share the entire body of the application - but it seems like the thrashing during my unit tests (creating and deleting lots of keyspaces, as each test uses its own) makes this exponentially more likely.

Reusing host selection policies between multiple sessions (even after closing the old session) is not supported as the old session might still be using the policy. Adding a lock to Init won't fix the fact that the old session is still using the policy. I suggest you use a new instance of the policy every time you create a session. I guess we need to document that reusing policies is not supported and panic in tokenAwareHostPolicy.Init if the policy was already initialized.

Sounds like it’s a more along the lines of a defective design pattern - and the strategies should be passed as a factory so that each session the driver summons can get its own.
However that boat has probably sailed in terms keeping things compatible with todays world. It’d be a fairly breaking change to fix.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Martin Sucha @.>
Sent: Wednesday, January 26, 2022 4:30:56 PM
To: scylladb/gocql @.>
Cc: Steve Gray @.>; Author @.>
Subject: Re: [scylladb/gocql] Data Race During --race Test (Issue #94)
Reusing host selection policies between multiple sessions (even after closing the old session) is not supported as the old session might still be using the policy. Adding a lock to Init won't fix the fact that the old session is still using the policy. I suggest you use a new instance of the policy every time you create a session. I guess we need to document that reusing policies is not supported and panic in tokenAwareHostPolicy.Init if the policy was already initialized.
—
Reply to this email directly, view it on GitHubhttps://github.com/scylladb/gocql/issues/94#issuecomment-1021905431, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADPDTP46JG5ZHUB75FZGHHDUX6IKBANCNFSM5MOREHVQ.
You are receiving this because you authored the thread.Message ID: @.***>

Sounds like it’s a more along the lines of a defective design pattern - and the strategies should be passed as a factory so that each session the driver summons can get its own.
However that boat has probably sailed in terms keeping things compatible with todays world. It’d be a fairly breaking change to fix.

Yes, I agree. Unfortunately the policy interface is like this for a long time and there could be external implementations, so we can't easily change it.


Unable to convert caffemodel and prototxt files to .blob file using the blob converter for QR code models

I was trying to follow the QR code model on the Luxonis depthai documentation. However upon using the blob converter to convert the caffemodel and prototxt files to .blob file, it gave me a conversion error. So i tried 2 other methods that managed to load the QR code model from opencv zoo and  WeChatQRcode repos.
Luxonis QR code model (Old weights):
https://docs.luxonis.com/en/latest/pages/tutorials/deploying-custom-model/#qr-code-detector
New weights:
https://github.com/WeChatCV/opencv_3rdparty/tree/wechat_qrcode

Error from converting caffemodel and prototxt files to .blob file

This seems like OpenVINO problem (Model optimizer), not a problem with blobconverter itself. Closing due to inactivity.


Why The Key Vault Networking must be set to allow access from All networks?

[Enter feedback here]
Why The Key Vault Networking must be set to allow access from All networks?
This settings will bring risk if customer does not want to expose KV to all networks.

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

ID: ef9f0dbe-23c4-5c17-56fd-ee40ff803cdd
Version Independent ID: d7ec7ba5-2933-8d42-9891-8f78aa2d73b9
Content: Azure Firewall Premium certificates
Content Source: articles/firewall/premium-certificates.md
Service: firewall
GitHub Login: @vhorne
Microsoft Alias: victorh

@yinoa , thank you for your query. We'll review this and get back to you shortly!

@GitaraniSharma-MSFT  Any update of this ask？ thank you.

@yinoa , this is a limitation that is being worked on by the Product group team to fix.
As mentioned in the Azure Firewall Premium known issues, Azure Firewall is not currently listed as a trusted service and can't access the Key Vault. Hence, the Key Vault Networking must be set to allow access from All networks. A fix is being investigated by the PG team and the current ETA is Q3/CY22 (subject to change).

We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


dart 2.1

About the PR
The behaviour of the Dart shuttle was not ideal since I just copied over the old dart shuttle prototype and components. This removes the BecomesStation component so that it no longer shows up in the late join list if spawned in.  Also removes the availableJobs and replaces it with 1 captain, similar to the other shuttles infiltrator and pirate ship.
Ive had reports that light fixtures arent filling when admins are spawning the shuttle in but I cant reproduce it, its working fine locally with loadmap, loadgamemap, and mapping/mapinit commands
Changelog

stops the Dart ERT shuttle from showing up in the latejoin menu

looks like the tests come back as not happy when it doesn't have the BecomesStation component, but that's the one that causes it to show up in the latejoin menu and it confuses people.

alright the yml was tidied up but the tests are still angry because I took off the BecomesStation component because it wants dart to have a station grid

tests are still failing, have you figured out why?

tests are still failing, have you figured out why?

its because it doesn't have a station component. I will try to mess with it tomorrow, see if I can save it as a grid while keeping it available for admins to spawn via loadgamemap.  The issue is that it originally was a station with jobs for auto spawning, after it was reworked it requires the station component still.  The problem is, it shows up in the late join menu as an empty entry which confuses people.

tests are still failing, have you figured out why?

its because the tests are trying to run LoadGameMap tests, which is trying to ensure a playable station. This is just a shuttle and needs to be tested with LoadGrid, like the evac shuttles and stuff are but I don't know what to do to fix

This is just a shuttle and needs to be tested with LoadGrid, like the evac shuttles and stuff are but I don't know what to do to fix

Thats the problem, the evac shuttles arent gameMaps, the test fails because as you said its trying to ensure the map is valid, so you should just ditch the map prototype in here and the wizard shuttle since loadgrid doesnt take a map id as argument anyways, it takes the path to the grid prototype.
Not to say this shouldnt be supported but as things are now you have to either make them proper game maps or grids as expected by tests

Ditching the prototype means it cannot be spawned by admins.... defeating the entire purpose of having the shuttle to begin with

loadmap command takes a path

loadgrid command takes a path

The admins don't use load grid, they don't have access to load arbitrary grids, they use loadgamemap
This is like the 4th time I've had to explain this!


Bug, Subqueries losing parethesis causing bad mysql

Hey there,
ran into a bug trying to upgrade from 0.1.1 to 0.3.0, for some reason the .ast call is causing the subqueries to come out without '(' and ')' causing mysql to moan
SQL Error [1064] [42000]: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'SELECT
	'SomeClass' AS `discriminator`,
	id AS `id`,
	name AS `name`' at line 12

i.e
0.3.0
SELECT
	discriminator,
	id,
	name,
	active
FROM
	SELECT
	'SomeClass' AS `discriminator`,
	id AS `id`,
	name AS `name`,
	active AS `active`,
FROM
	`some_class
WHERE
	`some_class`.`archived` = FALSE AS `union`

vs 0.1.1
SELECT
	discriminator,
	id,
	name,
	active
FROM
	(SELECT
	'SomeClass' AS `discriminator`,
	id AS `id`,
	name AS `name`,
	active AS `active`,
FROM
	`some_class
WHERE
	`some_class`.`archived` = FALSE) AS `union`

https://github.com/kddnewton/active_record-union_relation/compare/v0.1.1...v0.2.0#diff-47adbb2bbca246dbac44f2bca68ef94a45c91ae6a08abeef5b2b691411a16f22L116-R147
i also confirmed by monkey patching that it does work again if i remove .ast
Just wanted to check if there wasn't something else on my end that may cause this logic to breakdown? if not ill look at making a pr with a test at some point
Thanks!

https://github.com/kddnewton/active_record-union_relation/pull/127
I was able to replicate though im not sure how/why this happens but https://github.com/kddnewton/active_record-union_relation/pull/127/files#diff-40822d3ce62238e7a2518e9702da9aee1937baf6c98c798d10a589cece71ffd1R87
If you comment out this line it will pass OR if you remove the .ast core over in https://github.com/phyzical/active_record-union_relation/blob/fa709707dafcac613113a98edb4a13eaadd22fff/lib/active_record/union_relation.rb#L201

Thank you! The test case was very helpful. I've opened a fix for this.

Confirmed our tests pass without the monkey patch in 0.3.1 thanks again!


mkimage-alpine.sh: Allow to change ARCH from the environment

It is more convenient to be able to change the automatically resolved ARCH variable
On Armada XP processors, uname -m returns armv7l and the corresponding alpine ARCH on their repository is armhf.
You can also want to build a x86 alpine image on a x86_64 server.

Seems reasonable; LGTM cc @jfrazelle

LGTM


Update gen2 ocr example

I tried to migrate this example to latest DepthAI Gen2 API (commit hash 45765d01ad9c7d8d9ae99ca0f76c5b03b706a1c4), and got the following error after running against this version
Traceback (most recent call last):
  File "/home/vandavv/dev/luxonis/depthai-experiments/gen2-ocr/main.py", line 12, in <module>
    colorCam.setAutoFocusMode(depthai.RawCameraControl.AutoFocusMode.AUTO)
AttributeError: 'depthai.ColorCamera' object has no attribute 'setAutoFocusMode'

Fixed by bec6e6b6c5ab9eba9c2d97cd1f46cbba9e4df22b.

Thanks!


[docs][Radio] Fix color diff

[x] I have followed (at least) the PR section of the contributing guide.

Good catch! Thanks for the fix


[FLOC-3414] No-op @flaky decorator

Part of the work to add a @flaky decorator to flocker.
This patch adds a decorator that does absolutely nothing, and then applies that decorator to all of the tests for which we have bugs saying they are flaky.
It has been a worthwhile exercise in that it has taught me about which tests are actually flaky (I already had a sense of it, but it's surprisingly clear once you look at what actually needs to import flaky), and also because it has made the uses for the @flaky decorator more clear (see XXX notes in the diff).
I think having these markers in the code will help people with debugging (esp. @Azulinho with the Jenkins migration), so even though there's no behavioural change, I think there's enough added value to land.

thanks for @exarkun for stepping in and clarified some of my doubts
thanks for @jml for starting some work on this well needed @flaky
thanks @azulinho for looking into hypothesis (cool stuff)
quite a few failures due to timeouts and friends, I clicked rebuild on all the failed ones.
gerge it when mreen
or when you're happy with it

oh, and your jenkins builds is here btw:
http://ci-live.clusterhq.com:8080/job/ClusterHQ-flocker/job/no-op-flaky-decorator-FLOC-3414/job/__main_multijob/2/

Sole remaining failure is a known flaky test. Merging.


[stable/external-dns] Support Digital Ocean

FEATURE REQUEST
The stable/external-dns helm deployment does not currently support Digital Ocean as a provider. However, external-dns does support Digital Ocean. We should add that ability to the external-dns helm chart.
Version of Helm and Kubernetes: helm client v2.12.1 / server v2.12.1, kubernetes client v1.10.11 / server v1.13.1
Which chart: stable/external-dns
What happened: No support for Digital Ocean

FEATURE REQUEST
The stable/external-dns helm deployment does not currently support Digital Ocean as a provider. However, external-dns does support Digital Ocean. We should add that ability to the external-dns helm chart.
Version of Helm and Kubernetes: helm client v2.12.1 / server v2.12.1, kubernetes client v1.10.11 / server v1.13.1
Which chart: stable/external-dns
What happened: No support for Digital Ocean

+1


[1.12] Custom Fluid Dict Converter help

Forge: <IP_ADDRESS>54
Industrial Foregoing Version: 1.12.2-1.12.13-237
TeslaCoreLib Version: 1.12.2-1.0.17
Not sure if this is a script issue or an actual block mechanic issue. Basically I am trying to convert between Immersive Petroleum oil and Thermal Foundations crude oil. If I look in JEI for the recipe it shows the 2 being able to convert back and forth, however when I put the liquids and cycle through the fluid types the 2 oil buckets don't exist. So the fluids won't convert.
oil -> crude with respective bucks below in the converter: https://puu.sh/GttGh/585a738663.png
Ct with buckets containing fluids names: https://puu.sh/GttHZ/0c610aabfc.png
Gif showing JEI: https://puu.sh/GttLu/7048e5b913.gif
Script: https://pastebin.com/qSamAwBh

:wave: Sorry but Industrial Foregoing has ended support for version 1.12. I'm closing this issue as it will no longer be updated for that version. Thanks for playing with the mod.


Update connect-to-exchange-online-powershell-v2.md

Updating minor errors

Docs Build status updates of commit 19cc93e:
:clock10: Full build: the average full build time is 11 min(s) 48 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 19cc93e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

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


Revert "[flutter_tools] Disable analytics for more bots"

Reverts flutter/flutter#50579
Crashing for folks locally. I'll need to widen the SocketException check.

Landing revert on red.


Device Security Baseline for Cross-Tenant Access

💡 Summary
Section 2.17 of the Microsoft Azure Active Directory Baseline states that the device claim (compliance status of the device) from the home tenant should be trusted for guests in the resource tenant. When conditional access policies are evaluated during authentication, it only renders a binary answer of whether a device is compliant or not. While this type of policy provides a rudimentary filter for blocking access to non-compliant devices, it does not yield that a guest user's device complies with the resource tenant's security requirements and fundamentally goes against the ZT concept of not allowing implicit trust across boundaries.
Motivation and context
Let's consider a simple scenario of a resource tenant and home tenant have differing security requirements for HAADJ/AADJ devices. If the resource tenant requires BitLocker to be enabled for a device to be marked as compliant, but the home tenant does not require BitLocker to be enabled to mark a device as compliant, then a user from the home tenant (with whom a resource has been shared) can access a resource as a guest user within the resource tenant without meeting the BitLocker requirements of the resource tenant. This carries a significant security risk if there were no other DLP policies applied to the resources. This yields the question, what is the real value of section 2.17 in the context of guest users as it stands today? While general guidance for securing devices has been laid out through a lot of publications from NIST and CISA, there has to be consensus and a shared understanding of what is considered secure before the implementation steps 2 and 3 under section 2.17.4 are executed. This is confounded by the fact that CISOs and CIOs may have opposing opinions on the on this topic.
We also have to consider that sharing real-time device configuration across two tenants is probably not a capability that Microsoft can (or will) implement for the conditional access policy feature set any time soon. If and when they do, it can be incorporated into the baseline. In the meantime, to be pragmatic, CISA should also provide a framework for how device trust should be established.
This would be helpful so that CISOs and CIOs can follow guidance from a single authoritative source and build consensus on the absolute minimum required device configuration to meet the security thresholds for cross-tenant collaboration.
Implementation notes
The framework could include the following:

Publishing a security baseline for Windows Devices (or use an existing one that defines the bare minimum required).
Developing scripts that can generate reports about whether security baselines for a tenant have been implemented or not.
Providing guidance on how home tenant ISOs should supply their security baseline reports as evidence to resource tenant ISOs through Interagency agreements (or some other medium).

Acceptance criteria
Resource tenant implementers have a shared understanding with home tenant implementers on the minimum security/configuration requirements for devices, before cross-tenant access is enabled.

Thanks for your feedback! We will review your feedback and take it into consideration for the next baseline update.
Closing all baseline-document issues to make it easier to track outstanding code issues. If we have questions on your feedback, we'll re-open this issue.


Use task queue to evacuate cloud instances

This will allow the UI to queue host evacuation operations that are currently synchronous.

D'oh, needs rebase @mansam

@blomquisg fixed :)


Shouldn't cruft-based actions in repos built with this template be wrapped in poetry?

update-template:
	poetry run cruft update

In the Makefile, instead of
update-template:
	cruft update

They should not. Following the current recommendation, if you've installed cruft with pipx then cruft update should work just fine. I've you've chosen to go the pipx run cruft ... route that's perfectly fine, but I think it's up to the end user to adjust their Makefile accordingly at that point.


docstrings/sphinx: Support cross-refs for types in "Warns" sections

Is your feature request related to a problem? Please describe.
The goal is to have a common set of features between all parsers.
Describe the solution you'd like
The Sphinx parser should be able to parse the types in "Warns" section in order to enable automatic cross-references.
from griffe.docstrings.utils import parse_annotation

# annotation is a string
annotation = parse_annotation(annotation, docstring)
# annotation is unchanged, or becomes a Name or Expression! cross-refs enabled

Closing for cleanup, but if you'd like to work on this, just ask and I'll reopen!


Handle some shortcuts

Add support to [index] syntax.

Codecov Report

Merging #6 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #6   +/-   ##
=======================================
  Coverage   95.45%   95.45%
=======================================
  Files           1        1
  Lines          22       22
=======================================
  Hits           21       21
  Misses          1        1

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 05ee124...3663688. Read the comment docs.


Correct format for datetime.timedelta parsing

Change Summary
Correct format for datetime.timedelta parsing
Related issue number
Fix #7650
Checklist

[x] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[x] Tests pass on CI
[x] Documentation reflects the changes where applicable
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Please review


Update legacy unit tests

Summary
Update some legacy tests by changing PendingDeprecationWarning with DeprecationWarning due to deprecation opflow.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 92.176%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
4359

Relevant Lines:
4729

💛  - Coveralls

Yes, the legacy tests intentionally use opflow and contain a lot of deprecation warnings. I will investigate how to mitigate deprecation messages in another PR.


Add support for functions with multiple inputs and outputs

This should/could include support for things like BiFunction as well as anything that can clearly communicate the fact that its a function. For example
public class MyFunction {
    public String apply(String arg1, String arg2, Integer arg3){..}
}

Function3<...>

Function<Tuple2<..>, Tuple3<..>>

etc...

Initial support has been added https://github.com/spring-cloud/spring-cloud-function/commit/93f7a248a52e102de5e9abd6f032fe8e2d0cee84


Clarify handshake options in SignalR

See https://github.com/aspnet/Docs/issues/7691

I clarified one additional statement, as per comments on the original issue.

Derp, forgot the verb change you mentioned, thanks for grabbing that :). I'm good!


% Drop Chance

Under the main config.yml there is:
drops:
item-chance: 0.25
socket-gem-chance: 0.2
identity-tome-chance: 0.1
custom-item-chance: 0.1
unidentified-item-chance: 0.1
and in the creatureSpawning.yml there is:
spawnWithDropChance:
CREEPER: 1.0
SKELETON: 1.0
SPIDER: 1.0
GIANT: 1.0
ZOMBIE: 1.0
GHAST: 1.0
PIG_ZOMBIE: 1.0
ENDERMAN: 1.0
CAVE_SPIDER: 1.0
SILVERFISH: 1.0
BLAZE: 1.0
MAGMA_CUBE: 1.0
ENDER_DRAGON: 1.0
WITHER: 1.0
WITCH: 1.0
Does that mean that by default every mob has 100% chance to drop:
an item 25% of the time?
a socket gem 20% of the time?
an identity tome 10% of the time?
a custom item 10% of the time?
an unidentified item 10% of the time?
If so does that mean if i changed only the creatureSpawning.yml file config for skeleton from 1 to .5 then that would mean out of 100 skeletons 50 of them would then have a chance to drop:
an item 25% of the time?
a socket gem 20% of the time?
an identity tome 10% of the time?
a custom item 10% of the time?
an unidentified item 10% of the time?
Im not sure if my question makes sense to you or not.  If it doesn't i will try to clarify it.

Essentially, it takes the values from the config.yml and multiplies them against the values from the creatureSpawning.yml. Using the above configuration, a CREEPER has a 0.25 (25%) chance of spawning with an item AT ALL. If it does successfully spawn with an item, it has a 0.1 chance of that item being an identity tome, a 0.1 chance of it being a custom item, a 0.1 chance of it being an unidentified item, and a 0.2 chance of it being a socket gem.
If you wanted CREEPERs to drop twice as frequently while maintaining the rest, you would set the CREEPER value to 2.0. If you wanted to halve the drop rate of the others while maintaining CREEPERs, you'd set everything else to 0.5. It allows you to have more fine-grained control over certain mobs dropping items.

Is there a Wiki in regards to this plugin?

There is not a wiki at the moment, no. That's been planned for a while and just never gotten around to.


DecimalArray Benchmarks

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

We lack any benchmark coverage of DecimalArray and DecimalBuilder
Describe the solution you'd like

Some basic benchmarks of constructing, iterating and filtering decimal arrays
Describe alternatives you've considered

Additional context

Perhaps @liukun4515 you might want to pick this up in advance of making any changes?

There are some benchmarks in https://github.com/apache/arrow-rs/pull/2360 -- see https://github.com/apache/arrow-rs/pull/2360#issuecomment-1209180343 from @liukun4515

pick up this issue. thanks @tustvold @alamb

we have many case using the decimal data type, the benchmark and improvement for decimal are important for us.

I have added the benchmark for validation decimalarray for decimal128 and decimal256 in https://github.com/apache/arrow-rs/pull/2360.
In the pr https://github.com/apache/arrow-rs/pull/2360, I doesn't refactor the validation of decimal128 because I got wired benchmark result.
After the pr merge, I will submit a new pr or issue to discuss this.
@alamb @tustvold

[ ] add test for decimal decoder from primitive reader: https://github.com/apache/arrow-rs/issues/2408
[ ] add benchmark for reading primitive data to decimal

The performance of reading decimal data from bytes or fixed length bytes improves by https://github.com/apache/arrow-rs/pull/2528 https://github.com/apache/arrow-rs/pull/2522

🌮

Closing as we have fairly good benchmark coverage now, and decimal array is now a primitive array yielding additional coverage


[Bug] Resurrect pandera support for the good of pandas :panda_face:

The following does not work, despite pandas-stubs claiming some sort of PEP-compliance:
from __future__ import annotations

from typing import TYPE_CHECKING

import pandas as pd
from beartype import beartype

@beartype
def some_func() -> pd.Series[int]:
    return pd.Series([1, 2, 3])

some_func()

if TYPE_CHECKING:
    reveal_type(some_func())  # Mypy: Revealed type is "pandas.core.series.Series[builtins.int]"

This raises
beartype.roar.BeartypeDecorHintForwardRefException: Function __main__.some_func() return stringified type hint 'pd.Series[int]' syntactically invalid (i.e., TypeError("type 'Series' is not subscriptable")).

Maybe this is a problem of the pd.Series type not having a __getitem__? If we then add that, based on this completely random comment I found on the internet:
https://stackoverflow.com/questions/77697685/python-generic-type-annotation-for-pandas-series#comment136990299_77697685
like so:
pd.Series.__class_getitem__ = lambda cls, *_: cls

But now I've unlocked a whole new level of pain:
beartype.roar.BeartypeCallHintReturnViolation: Function __main__.some_func() return "0    1
1    2
2    3
dtype: int64" violates type hint <class 'int'>, as <protocol "pandas.core.series.Series"> "0    1
1    2
2    3
dtype: int64" not instance of int.

And changing the generic form int to, say, np.int or whatever will now upset mypy as well (which expects int). beartype will not be satisfied by any attempts at salvaging the hints.

...heh. pandas-stubs, huh? Yeah. About that.
The First Rule of Beartype Club is that nobody knows how to implement type hints. The Second Rule of Beartype Club is that two projects actually do know how to implement type hints. They are unsung heroes whose names shall be entered into the Akashic Records housed at Valhalla, Asgard:

@patrick-kidger's jaxtyping, covering JAX, NumPy, PyTorch, and TensorFlow tensors (i.e., multidimensional arrays).
@cosmicBboy's pandera, covering pandas DataFrames.

That's it. All other type hints should be assumed to be insane, because they are. This includes type hints published by:

The standard typing module, which @beartype only supports because it has to. The standard typing module is still insane, though. CPython devs have no idea what they're doing at all. Truth or dare? Mostly truth.
The jax.typing subpackage. Ditto.
The numpy.typing subpackage. Ditto.
The pandas-stubs package. Ditto.
And everybody else, too.

Thankfully, you're in luck! @beartype officially supports pandera. I may be crabby, but there's no reason you need to suffer:
from __future__ import annotations

from pandas import Series
from pandera.dtypes import Int64
from pandera.typing import Series as SeriesBusiness  # <-- get it, "series business"? ...i'll stop now
from beartype import beartype

@beartype
def some_func(dataframe: SeriesBusiness[Int64]) -> None:
    print(dataframe)

some_func(Series([1, 2, 3]))
some_func("Pretty sure this ain't a dataframe.")

...which prints:
  from pandas import Series
0    1
1    2
2    3
dtype: int64
Traceback (most recent call last):
  File "/home/leycec/tmp/mopy.py", line 15, in <module>
    some_func("Pretty sure this ain't a dataframe.")
  File "<@beartype(__main__.some_func) at 0x7f8766fbc4a0>", line 30, in some_func
beartype.roar.BeartypeCallHintParamViolation: Function __main__.some_func() parameter
dataframe="Pretty sure this ain't a dataframe." violates type hint
pandera.typing.pandas.Series[pandera.dtypes.Int64], as str "Pretty sure this ain't a
dataframe." not instance of <protocol "pandas.core.series.Series">.

See also @beartype's official FAQ entry on pandas type-checking. Now, if everyone will excuse me, I must some crab apples sprinkled with 20 year-old cinnamon to feel better. I didn't know that 20 year-old cinnamon could still be edible. But... it can.
 As if that wasn't bad enough, the punishment even intensifies as you age. Thanks, Business Insider. You have taught me I narrowly dodged a cultural bullet.

Oh, Gods. I double-checked this and... something is busted. Looks like pandera "improved" itself at some point and I failed to notice. This is bad. Although @beartype does still nominally support pandera type hints, @beartype no longer appears to correctly type-check pandas DataFrames against pandera type hints. pandera unit tests in the @beartype test suite are currently passing – but they shouldn't be. Badness continues.
Let's revive this issue under a new header: "Resurrect pandera support for the good of pandas"! :panda_face:

uh oh, curious to learn what's causing this issue pandera-side

It's probably us – but it might be you. But it's probably us. Regardless of who it is, thanks so much for chiming in so readily. You're the pandas chef's kiss, @cosmicBboy. :panda_face:
Since you're up and about, would you mind you confirm that the following minimal-reproducible example is expected to pass rather than raise an exception? Something doesn't seem quite right. We've cited something similar in @beartype's official FAQ entry promoting pandera. So, I'd really like to get this right:
from pandas import Series
from pandera import check_types as pandera_check_types
from pandera.dtypes import Int64
from pandera.typing import Series as SeriesBusiness  # <-- get it, "series business"? ...i'll stop now

@pandera_check_types
def some_func(dataframe: SeriesBusiness[Int64]) -> None:
    print(dataframe)

some_func(Series([1, 2, 3]))  # <-- this passes. *GOOD*
some_func(Series(['ok', 'ko', 'yo']))  # <-- this also passes. that can't be right? *BAD*
some_func(Series([1.2, 2.3, 3.4]))  # <----- this also passes. that can't be right? *BAD*

...which prints:
0    1
1    2
2    3
dtype: int64
0    ok
1    ko
2    yo
dtype: object
0    1.2
1    2.3
2    3.4
dtype: float64

Basically, everything passes – but I kinda only expected the first call to some_func() to pass. Clearly, I'm confused.
There's just a veritable ton of different pandera decorators. That's not a bad thing per say. But I'm unclear which one I should be calling. @pandera.check_types seems right, but maybe I want @pandera.check_input or @pandera.check instead or whatevahs? Also, how actually do you type-check pandas Series objects? I couldn't quite tell from the documentation. I assumed pandera.typing.Series[int] or whatevahs would do the trick, but now I'm getting no treats.
Clearly, I have no idea what I'm doing here. Help a @beartype bro help pandera.

@komodovaran: In theory, pandera is the answer. In practice, let's see how unionai-oss/pandera#1527 pans out. :smiling_face_with_tear:
@cosmicBboy: Because I'm clueless, I've upstreamed this into your court at unionai-oss/pandera#1527. I'm out of my league and playing with a half-empty deck. It's not a great feeling.


Codebase cleanup

Between rustfmt's requirements being... bad... and our need to develop quickly, we have accumulated a fair amount of ugliness in the repo already.  Suggestions on how to fix this are welcome, but my guess is we need an actual style document and more than one reviewer on each PR, as well as dropping rustfmt.

Indeed, rustfmt doesn't fix up all the style problem. There is an official style guideline here, but it looks like still in working progress. More than one reviewer is a good idea.
Once there is a style doc, can we follow the guide style and go through our code base to clean up as much ugly code as we can?

I will make an effort to review more, been a little busy over on the python side, but we are getting in good order now. I wonder if now might be a good time to migrate the repo over to keylime GitHub org. Charlie and Nabil are regularly reviewing patches and that would be beneficial for the 2.0 port. We can retain the exact same permissions and do a whole sale migration?


Bug: Submitter does not open UI if there is no output path is specified

Expected Behaviour
Click Extensions > Deadline Cloud Submitter
Submission window appears
Click the "Job Specific Settings" tab and edit my output directory
The "Job Specific Settings" tab overwrites the output directory, so we shouldn't need to have a valid output directory before setting it here.
Current Behaviour
Click Extensions > Deadline Cloud Submitter
Nothing happens.
The following error shows up in the console:
Failed to watch these AWS Deadline Cloud configurations: ['C:\\Users\\Administrator\\.aws\\sso\\cache']
Deadline UI launch failed
Traceback (most recent call last):
  File "C:\Program Files\Python310\Lib\site-packages\deadline\cinema4d_submitter\cinema4d_render_submitter.py", line 54, in show_submitter
    w = _show_submitter(None)
        ^^^^^^^^^^^^^^^^^^^^^
  File "C:\Program Files\Python310\Lib\site-packages\deadline\cinema4d_submitter\cinema4d_render_submitter.py", line 273, in _show_submitter
    output_directories = Scene.get_output_directories(take=take)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Program Files\Python310\Lib\site-packages\deadline\cinema4d_submitter\scene.py", line 152, in get_output_directories
    path = render_data.GetFilename(c4d.RDATA_MULTIPASS_FILENAME)
           ^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'c4d.documents.RenderData' object has no attribute 'GetFilename'

Reproduction Steps
Install submitter
Create a new C4D scene with no output directory specified
Click Extensions > Deadline Cloud Submitter
Code Snippet
n/a

Workaround is to ensure you have an output set in the render settings before opening.

We may just need to call .GetData() on the render_data object before calling GetFilename()
See this Deadline10 submitter it stores the render_data.GetData() object and then calls GetFilename() on that


Dex 17120

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
Test URLs:

Before: https://main--www-landing-pages--bitdefender.hlx.page/drafts/test-page/
After: https://DEX-17120--www-landing-pages--bitdefender.hlx.page/drafts/test-page/

don't forget to update the snapshot tests and add in sidekick new variation


"daswetter has an invalid jsonConfig" with Version 3.2.0

Admin v7.4.1
When trying to configure the instance.
2024-12-05 23:06:23.236  - warn: admin.0 (260) daswetter has an invalid jsonConfig: [{"instancePath":"/items/MainSettings/items/alive/instance","schemaPath":"#/definitions/aliveProps/properties/instance/type","keyword":"type","params":{"type":"string"},"message":"must be string"},{"instancePath":"/items/MainSettings","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/9/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]

Fixed with v3.2.1. Thanks!


[v2] Build failed in Release mode

It seems working well in Debug mode, but in Release mode build fails
Steps to reproduce

Create new project by react-native cli

Install react-native firestack

Commands for reproduce
$ react-native init AwesomeProject
$ cd AwesomeProject
$ npm install react-native-firestack --save
$ react-native link react-native-firestack
$ cd ios && pod update --verbose
$ cd ..
$ react-native run-ios --configuration Release

Build fail error that I got finally
/Users/phoenix/Documents/Workspace/AwesomeProject/ios/build/Build/Intermediates/AwesomeProject.build/Release-iphonesimulator/AwesomeProjectTests.build/Objects-normal/i386/AwesomeProjectTests

Undefined symbols for architecture i386:
  "___gxx_personality_v0", referenced from:
      _RCTDefaultLogFunction_block_invoke in libReact.a(RCTLog.o)
      _RCTFormatLog in libReact.a(RCTLog.o)
      ___RCTAddLogFunction_block_invoke in libReact.a(RCTLog.o)
      _RCTPerformBlockWithLogFunction in libReact.a(RCTLog.o)
      _RCTPerformBlockWithLogPrefix in libReact.a(RCTLog.o)
      RCTGetLocalLogFunction() in libReact.a(RCTLog.o)
      ___RCTPerformBlockWithLogPrefix_block_invoke in libReact.a(RCTLog.o)
      ...
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Does anyone know how to solve this issue?
Thanks
Versions of packages that I use for test

OS: macOS Sierra
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

@sujameslin can you try manually setup firestack without using react native link

@Salakar It works with manual installation.
But you have to update the readme since cocoapod installation is not working by following doc.
Please check my PR.
https://github.com/fullstackreact/react-native-firestack/pull/211


public-vm: more flexible interface to proof system

@Maddiaa0 as you said, it might help to start by implementing PIL & witness generation for some basic opcode (maybe SUB?). This should give you a sense of where the friction lies in this development process.

@Maddiaa0 Is this done?


Ability to have a max height controlled by CSS.

Changing to use a div in place of the previous span since it is a nice
block level element replacement.
Added the ability to have a max-height on the expanding textarea for
browsers that support the max-height CSS property.

Looks good!


Show line colors like SEU does

Also fix the issue with character sizing for non visable characters. Can't do much about those special ones though.


Start task does not require input

I have the following task defined:
apiVersion: tekton.dev/v1alpha1
kind: Task
metadata:
  creationTimestamp: "2020-05-13T15:12:32Z"
  generation: 1
  name: foo
  namespace: tekton
  resourceVersion: "1804"
  selfLink: /apis/tekton.dev/v1alpha1/namespaces/tekton/tasks/foo
  uid: 1f82e7d8-9851-4a85-8629-abe03b77b9c7
spec:
  inputs:
    params:
    - name: parm1
      type: string
    - name: parm2
      type: string
    - name: parm3
      type: string
    - name: parm4
      type: string
    - name: parm5
      type: string
    - name: parm6
      type: string
    - name: parm7
      type: string
    - name: parm8
      type: string
    - name: parm9
      type: string
    - name: parm10
      type: string
    resources:
    - name: workspace1
      type: git
    - name: workspace2
      type: git
    - name: workspace3
      type: git
    - name: workspace4
      type: git
    - name: workspace5
      type: git
    - name: workspace6
      type: git
    - name: workspace7
      type: git
    - name: workspace8
      type: git
    - name: workspace9
      type: git
    - name: workspace10
      type: git
  outputs:
    resources:
    - name: buildImage1
      type: image
    - name: buildImage2
      type: image
    - name: buildImage3
      type: image
    - name: buildImage4
      type: image
    - name: buildImage5
      type: image
    - name: buildImage6
      type: image
    - name: buildImage7
      type: image
    - name: buildImage8
      type: image
    - name: buildImage9
      type: image
    - name: buildImage10
      type: image
  steps:
  - args:
    - -c
    - echo hello world
    command:
    - /bin/bash
    image: fedora
    name: build-sources
    resources: {}

When starting the task, no input (parameters / resources) are required and the task is started.

The ext only supports v1beta1


Transaction record

Describe the feature request
I suggest to have a transaction record to download from taiko website as so many people doesnt how to check thru website.
Spam policy

[X] I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.

Your source of truth will be the explorer or wallet.


Fix whatsnew

🚀 Pull Request
Description

The Iris 3.0 whatsnew referred explicitly to a renamed page. I've also reverted an accidental change to the permissions I made to the whatsnew file in my previous PR

Consult Iris pull request check list

I'm now wondering whether I should be using _iris_whatsnew instead of the full URL so that it doesn't break again in future, but that's already referenced in the whatsnew message so seems pointless repeating?

New docs build here: https://www-avd/~wbenfold/iris/whatsnew/latest.html
I think the linkcheck will be broken until this fix is merged, so we'll have to merge with that failing

Cirrus is asleep, but I'm confident that the linux: py3.8 tests result will be unchanged. Merging.


Candidate party corrections are not connecting as part of our get_party method

I added some logging to our get_party method on the Candidate proxy models. Then I analyzed the results in this notebook. It looks like we made zero corrections despite having some records in the corrections file.

I think I got it.


How to properly debug "Some attributes failed to be mapped into session tags" error?

Hello Folks!
I'm try to test the AWS Roles anywhere, but I'm receiving the following error:
2024/06/30 03:48:56 AccessDeniedException: Unable to assume role for arn:aws:iam::000000000000:role/local-vault. Some attributes failed to be mapped into session tags. Issuer: [  ]; Subject: [  ]; SAN: [ DNS/2 ]

Based on https://docs.aws.amazon.com/pt_br/rolesanywhere/latest/userguide/workload-identities.html I've also tried to check my client certificate attrs using openssl:
root@vault:/etc/ssl# openssl x509 -noout -issuer -in host.pem
issuer=C = BR, ST = Brazil, L = SaoPaulo, O = Dev Environments, OU = Sidecloud Vault Root CA, CN = Sidecloud Local Vault CA
root@vault:/etc/ssl# openssl x509 -noout -subject -in host.pem
subject=CN = abdalla

Btw my profile is using the default attribute mapping configuration:

And I can see my requests on the console:

I tried with versions 1.1.0 and 1.0.6 on Linux and both returns the error.
Can you folks point me to some method to debug or details why it is not working?

I plan to test SPIFFE formats next, but I 'd like to at least make this simple test pass before proceeding.

Thanks in advance!

Well, whatever was the error, by recreating the CA and certificates using the default CFSSL worked for me this time.


 Delete the others, including these Instructions.
{{cask_file}} represents the cask file you’re submitting/editing (if applicable).
If there’s a checkbox you can’t complete for any reason, that’s OK. Just explain in detail why you weren’t able to do so.

Changes to a cask
Editing an existing cask

[ ] Commit message includes cask’s name (and new version, if applicable).
[ ] brew cask audit --download {{cask_file}} is error-free.
[ ] brew cask style --fix {{cask_file}} left no offenses.

Adding a new cask

[ ] Checked there aren’t open pull requests for the same cask.
[ ] Checked there aren’t closed issues where that cask was already refused.
[ ] When naming the cask, followed the token reference.
[ ] Commit message includes cask’s name.
[ ] brew cask audit --download {{cask_file}} is error-free.
[ ] brew cask style --fix {{cask_file}} left no offenses.
[ ] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.

Changes to the core

[ ] Followed hacking.md.

The application version is 3103 (the latest) and is tested on the latest OSX version.

Closing it as the same cask was rejected before.


Moderate Rev Changes + Weight Change

About the PR
Changes revs to make them funner and more balanced. 3 Changes are included: New Kit (Recharge Flash (3 Charges 180 recharge), Sec shades and synd enc key) Midround revs (Max 2, 30 Players per headrev 1.5 weight),  and revs/survival chances are swapped (10% Revs, 5% Surv)
Also my 1st PR so... yeah.
Why / Balance
New Kit - Recharge Flash nerfs blitz and buffs stealth, makes the start slower, paces revs better and makes converting decently often more important. shades grant sechud and chameleon over the old ones, preventing 1 pretty bad scenario (Not gonna flash someone shielded) and the enc key lets headrevs coordinate. Plan a strategy TOGETHER! For once.
Midround Revs - They are much weaker than a normal revolt with normally half the revs for the player count. Zombs have also been lowered to 1.5. They can start spawning 10m earlier than zombs to offset the much higher time to get ready than zombs. All in all, less likely to turbofuck the round compared to zombs and adds some more flavor to rounds, especially survival. (Also helps prevent "We already have synds!!!" when headrevs are called!)
 Pretty easy change, and it's somewhat of a compromise between the old weights on both goob and den and the current.
Technical details
No C#
Media
Added very soon :3

[] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
Changelog
:cl:

add: Midround revs can spawn rarely, at 1 Headrev per 30 players and a max of 2. They do not have encryption key to talk to the other headrev however!  Coordinate, Comrades!
tweak: Revs now roll at a 10% chance, and Survival at 5%!

Also i moderately goofed while making the texture changes so... yeah, 10+ commits from my goof.

Looks good other than you should attempt to comment all lines you change with # Goobstation, and the new gamerule should be in a new yml inside of /Prototypes/Goobstation/GameRules

Added comments and moved the rev yml to goobstation.
Do i need to change anything else?

Also moved the gamerule, sorry forgot about that.

Realised i made oopsies, they have been unfucked and everything's now # Goobstation commented or under Prototypes/Goobstation.

Additionally make sure this doesnt fire during revs

Additionally make sure this doesnt fire during proper revs

Don't know how to do that exactly, any tips to make that well, work? Pretty sure no other event does the same so I'm not exactly sure how. (Only reason outbreak never happens on zombs is those rounds being too short for example- very very rarely happens on ops too, but only seen that happen twice when they had a higher weight on lowpop stealth op rounds back like a year ago on den) But, if that doesn't exist yet at all, i can just set the weight lower/start later or both. Don't know how I'd code for a check for that- but don't mind any help for that.
(Definitely gonna add a Max Occurrences of 1 to prevent survival from barfing out a 4 headrev or even 6 headrev game after long enough however)

can do all of that.

Actually, revert your commits that changed the file location of the rev icon texture. Any texture changes of preexisting prototypes should stay in their original folder.

New rev icons are too large to work, gonna revert to the old ones.
Also apparently synd shades are totally broken, totally odd they worked a month ago or so. Gonna make them normal sec glasses.

PR's TOTALLY fucked- No matter what, the rev component doesn't work at all.
Fuck.
Gonna close and make a new PR that only adds the synd key and secret weights, something went REALLY wrong with the PR somehow. Tested by the way, any flash doesn't work.


Improvements to to_gds() and Cell.copy() methods.

The proposed changes include the following:

Performance improvement in object conversion to GDS (to_gds methods) for layouts with a large number of polygons.
Enhancement to Cell.copy() method to include / exclude specified layers in the copied cell.

The changes were implemented in Python 3.4, which is a requirement for our chip design workflow.

At some point we'll probably drop python 2 support, but I believe there are many users who still need it (specially considering python 2 is still the default in some OSes).
So, I'll try to filter only the core changes and skip the ones introduced by 2to3, but it will probably take some time.
Thanks for the contribution!

Having worked exclusively with Python 3.4 version of gdspy, the current approach to keep Python 2 as the base branch appears to pose a challenge for us: should we now build on top of @okianus Python 3.4 performance enhancing branch? In the event of a new gdspy release, is the best way to rebase our version onto its 2to3 converted version? Has there been a new release scheduled in the next 6 months or so? If possible, please advise on the long-term strategy. Thanks.

Ideally I would like to keep both versions alive, so it's better if you worked on the python 2 codebase to avoid these conflicts.
I don't have a fixed release schedule. As soon as a new feature becomes stable I usually release a new version. The improvements here could be a new release as soon as we are able to merge them in version 2.

I've gone ahead and manually introduced you changes relative to polygon serialization into master.
I did not include the new Cell.copy method with layers_to_include and layers_to_exclude. The issue there is the following: some tools use datatypes instead of layers for process identification and others use a combination of both datatype and layer. So it's preferable to keep a symmetry in the treatment of those properties (that means having a datatypes_to_include and datatypes_to_exclude at least).
How do we deal with intersections? For example, if layers_to_include = [1,2] and datatypes_to_exclude = [1], how do we deal with elements in layer/datatype 1/1 and 3/0?
Can we think of other argument names to make this specification less confusing?


Fix typos

Just thought I'd contribute some typo fixes that I stumbled on. Nothing controversial (hopefully).
Use the following command to get a quick summary of the specific corrections made:
git diff HEAD^! --word-diff-regex='\w+' -U0 \
  | grep -E '\[\-.*\-\]\{\+.*\+\}' \
  | sed -r 's/.*\[\-(.*)\-\]\{\+(.*)\+\}.*/\1 \2/' \
  | sort | uniq -c | sort -n

FWIW, the top typos are:

admininstrator (22)
requestor (18)
paramter (9)
succeded (8)
complated (6)
adminstrator (5)
refreh (5)
creatation (4)
terrafrom (4)
neeeded (3)
subscibres (3)

Understandable @goruha, what if I split the PR into breaking (higher risk) vs non-breaking (comments only) fixes?
FYI, this PR is about half the size now that #1114 has been merged (209 -> 107 fixes).


Roll engine 49445ce4949b..0f6229ab1d39 (6 commits)

https://github.com/flutter/engine/compare/49445ce4949b...0f6229ab1d39
git log 49445ce4949bf0d28506a6b22e28b4264f624e5f..0f6229ab1d3915bac6967f08a8074d58ebfeb656 --no-merges --oneline
0f6229ab1 Roll fuchsia/sdk/core/mac-amd64 from lKQ0yBPnk1oXLyNM7XhqSDl5llP6Cx2GWkQjS0ExozcC to XOXaWqvr4OuJ6O3uPefSwSFjZMaEmDHy5JQm3Q8Oc0wC (flutter/engine#9786)
e40149eaf Roll src/third_party/skia af4e7b6cf616..f9fcf7ffa89a (33 commits) (flutter/engine#9784)
009b1d5a9 Roll fuchsia/sdk/core/mac-amd64 from 1F71B9KuZAVZz0LDQW_g0bbfWsxEgQkDpHPKrkc97xYC to lKQ0yBPnk1oXLyNM7XhqSDl5llP6Cx2GWkQjS0ExozcC (flutter/engine#9779)
fbe50c6a6 Roll fuchsia/sdk/core/mac-amd64 from bYFmlYp6Mc82r7dw58IaEny3_mnq-yZW06Ccr19j0lIC to 1F71B9KuZAVZz0LDQW_g0bbfWsxEgQkDpHPKrkc97xYC (flutter/engine#9778)
51c3c11b8 fix objcdoc generation (flutter/engine#9772)
f076a60c9 Roll fuchsia/sdk/core/mac-amd64 from EYnRdXFT9l-d8Qkz4zeTRXnqfV3KQzpQhoPs1r0-740C to bYFmlYp6Mc82r7dw58IaEny3_mnq-yZW06Ccr19j0lIC (flutter/engine#9771)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (garyq@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


any idea how to use it in redux-form?

I have tried to use it with redux-form but it simply does not reflect the selected values in the redux-form state. it would be great if there was an example of using it with redux-form.

I fixed this issue please review my PR

@thg303 Merged. THX.


Makes code compatible with elastic 7.x

Description
This update adds a flag to two key elastic search calls that make it compatible with ElasticSearch 7.x.
Motivation and Context
There are no official docker images for users of OSX on M1 chips (ARM).  The ARM builds started after 7.x  Instead of adding a Dockerfile for ARM that we have to maintain, I've changed two lines of code which enables the circulation manager and scripts to work with ElasticSearch 7.x.  So we're effectively killing two birds with one stone:  smoothing the path for a future elastic search upgrade and allowing M1 users  to use docker to bring up ES.

How Has This Been Tested?
All tests pass, so we know it this change didn't break anything.
I manually tested using ES 7.17.5
docker run -p <IP_ADDRESS>:9200:9200 -d --name es-7.17.5  -e "discovery.type=single-node" docker.elastic.co/elasticsearch/elasticsearch:7.17.5

Checklist

[ ] I have updated the documentation accordingly.
[x ] All new and existing tests passed.

Haven't gotten a chance to test this in AWS, but taking a quick look at the PR, it would be nice to be testing against ES7 (as well as ES6) in CI since we're adding ES7 support here.

I'm going to close this one, as we're close to merging https://github.com/ThePalaceProject/circulation/pull/411 and that will allow running tests and development on a M1 machine.


Dynamic linking stops working for version forge 0.2.0 (fd87888 2024-06-17T00:19:40.934209349Z)

Component
Forge
Have you ensured that all of these are up to date?

[x] Foundry
[x] Foundryup

What version of Foundry are you on?
forge 0.2.0 (fd87888 2024-06-17T00:19:40.934209349Z)
What command(s) is the bug in?
script deployment
Operating System
None
Describe the bug
Previously, I used a old version of forge (can't remember the version). and I used 0.8.20 solc and set shanghai as evm_version in toml.
Under the previous setup, dynamic linking to external library worked.  I had a main contract and a external library with public function as its dependency. When I deploy the main contract using foundry script, the external library was deployed first and then the main contract second. The linking worked without me having to specify anything in the toml
After upgrade to the new version and using 0.8.24 and set cancun as evm_version. dynamic linking stops working.
I deployed the previous setup.  the the first transaction foundry send ( supposed to be external contract deployment) ends up to be some random transaction (interaction with some shitcoin).  The main contract was still deployed as part of the 2nd transaction.
I have tried to deploy the external library separately and link it back to the main contract. But i am seeing  Error (1130): Invalid use of a library name.
The actual transaction can't be shared here due to privacy concern. But I'd happy to share the problematic txns via private chat
TG is @NakedKoalaCapital.
Minimum Example displaying this issue
// SPDX-License-Identifier: MIT
pragma solidity >=0.8.0;

library ExecutionLibStub {
    // This contract is just a wrapper to deploy the library
    function F() external {}
}

// SPDX-License-Identifier: MIT
pragma solidity >=0.8.0;

import "src/onchain/ExecutionLibStub.sol";

contract ExecutorStub {
    // This contract is just a wrapper to deploy the library
    function F() public {
        ExecutionLibStub.F();
    }
}

contract DeployExecutionStub is Script {
    function run() external {
        uint256 deployerPrivateKey = vm.envUint("ADMIN_EOA_PK");
        vm.startBroadcast(deployerPrivateKey);
        ExecutorStub executor = new ExecutorStub();
        vm.stopBroadcast();
    }
}

forge script script/utils.s.sol:DeployExecutionStub  --rpc-url local_geth_node --with-gas-price<PHONE_NUMBER>  --broadcast

[profile.default]
src = "src"
out = "out"
libs = ["lib"]
via_ir = true
optimizer = true
optimizer_runs = 2000
evm_version = 'cancun'
solc = "0.8.24"

With this minimum setup, 2 transaction are created.  1st one interacts with 0x4e59b44847b379578588920cA78FbF26c0B4956C and has method id of 0x00000000
2nd contract is a contract creation
Update: Now using forge 0.2.0 (d7eac74 2024-06-21T00:16:53.812858792Z). The weird interaction with 0x4e59b44847b379578588920cA78FbF26c0B4956C went away but then external library ExecutionLibStub wasn't deployed.  Only ExecutorStub was deployed.

0x4e59b44847b379578588920cA78FbF26c0B4956C is a CREATE2 deployment factory - https://github.com/foundry-rs/foundry/blob/d7eac74cfd786447cec9650048e2d2fac63fba0c/crates/evm/core/src/constants.rs#L41
since #7711 forge routes all library deployments through it, if it's available on the current network. This allows it to only deploy library once, and then just reuse it if it was already deployed.
So what you see is that first time, library was deployed through CREATE2 factory, and then the contract itself was deployed, thus resulting in 2 transactions.
But on the second time, forge detected that library was already deployed and skipped it, thus resulting in a single deployment transaction of a contract.
This should also show up in script artifacts under run/


Fatal error: Unexpectedly found nil while unwrapping an Optional value: file ComposableArchitecture/ForEachStore.swift, line 143

Describe the bug
When filtering a ForEachStore we sometimes get a Fatal error: Unexpectedly found nil while unwrapping an Optional value: file ComposableArchitecture/ForEachStore.swift, line 143
The bug seems to appear in the Todos example as well.
We did not see this behavior before the ForEachStore-fixes.
To Reproduce
Tested on device iPhone 7 and simulator iPhone 11:
In the Todos project:
Add 20 Todos
mark 2 of them completed
press the Active segment and directly after the Completed segment.
Expected behavior
No Fatal error
Screenshots
If applicable, add screenshots to help explain your problem.
https://user-images.githubusercontent.com/23285231/111308354-dd206b00-865a-11eb-8597-070421171394.mov
Environment

Xcode 12.4
OS (if applicable): iOS 14.4.1

I get this too, using Example add "Todos", here are reproduction steps (100% of the time):
received action:
  AppAction.addTodoButtonTapped

received action:
  AppAction.todo(id:, action: .textFieldChanged)

Fatal error: Unexpectedly found nil while unwrapping an Optional value: file ComposableArchitecture/ForEachStore.swift, line 143
2021-04-03 07:45:54.603460+0200 Todos[35003:6441170] Fatal error: Unexpectedly found nil while unwrapping an Optional value: file ComposableArchitecture/ForEachStore.swift, line 143

(I use TCA commit: 1ce105f8bf7457d94385056a1946c6dc6f338556)

In my app I have something similar, but which is probably the result of using ScrollView together with two ForEachStore on the same data. Probably the update issue? I'm working around it with a .deleted flag on each data and excluding them on rendering, which sometimes looks ugly though and sometimes okay.

Thanks @fabstu for the report and PR. I've opened up an alternate fix in #471 that tries to contain it in the view layer. Can anyone experiencing this issue give that branch a try and see if it works for them? If so we'll merge it soon :smile:


Update some of the crypto to be more secure.

These changes do two things: use the order of cipher suites that Intel recommends (https://readthedocs.intel.com/cryptoteam/crypto_bkms/tls.html) and uses the most powerful hash available in OpenSSL at this moment for the certificate generation.


Youtube changed something on "https://www.youtube.com/youtubei/v1/player?prettyPrint=false" url

I suppose Youtube changed the way of accessing this URL
_https://www.youtube.com/youtubei/v1/player?prettyPrint=false_
causing a 400 error
if i try to copy/paste this url on the browser it says:

That’s an error.
The request method GET is inappropriate for the URL /youtubei/v1/player.
That’s all we know.

this behaviour changed more or less yesterday, and only when using allow_oauth_cache=True and use_oauth=True
to reproduce the error i used simply:
from pytubefix import YouTube
yt = YouTube(, allow_oauth_cache=True, use_oauth=True)
stream = yt.streams.filter(only_audio=True).order_by('abr').desc().first()
this piece of code was working without any errors since a month, but suddenly stopped giving me a 400 error
code is working on:

OS: Linux,OSX and also under Docker
Python 3.9.11
pytubefix 8.3.2

Same problem too

Same issue

Same issue, setting allow_oauth_cache and use_oauth to False resolves the issue, besides not being able to download some videos due to not being authenticated

yeah the same for me. i need to make it work  allow_oauth_cache and use_oauth set to True

The version that corrects this has been released, 8.4.1 and taking advantage of the use of oauth, I made a PR to reset the cache, if you can leave your opinions on whether or not I should launch it, if it will help... I tested it and it made it a lot easier , if you want to test this in the "reset_cache" branch, see the PR on how to use it -> https://github.com/JuanBindez/pytubefix/pull/333