Rename json.py in outlines/generate

Describe the issue as clearly as possible:
I am trying to debug outlines in PyCharm using pydev debugger (build 233.11799.298).
Upon running the debugger, I get the following error
AttributeError: partially initialized module 'json' has no attribute 'loads' (most likely due to a circular import)
which results from the naming of the json.py file. Renaming this file to anything other than the default python library resolved the issue.
Steps/code to reproduce the bug:
from transformers import MixtralForCausalLM, MixtralConfig, AutoTokenizer
import outlines
import tracemalloc

tracemalloc.start()

# Initializing a Mixtral 7B style configuration
configuration = MixtralConfig(
    hidden_size=256,
    intermediate_size=896,
    num_hidden_layers=8,
    num_attention_heads=8,
    num_key_value_heads=8,
    num_local_experts=4,
    num_experts_per_tok=1
)

# Initializing a model from the Mixtral 7B style configuration
model = MixtralForCausalLM(configuration)

# Accessing the model configuration
configuration = model.config

print(tracemalloc.get_traced_memory()[1])

tok = AutoTokenizer.from_pretrained("mistralai/Mixtral-8x7B-v0.1")
print(tracemalloc.get_traced_memory()[1])

prompt = "My favourite condiment is"

model_inputs = tok([prompt], return_tensors="pt")

generate_ids = model.generate(**model_inputs, max_length=30)
print(tok.batch_decode(generate_ids, skip_special_tokens=True, clean_up_tokenization_spaces=False)[0])

print(tracemalloc.get_traced_memory()[1])

# Outline part
arithmetic_grammar = """
    ?start: expression

    ?expression: term (("+" | "-") term)*

    ?term: factor (("*" | "/") factor)*

    ?factor: NUMBER
           | "-" factor
           | "(" expression ")"

    %import common.NUMBER
"""
outline_model = outlines.models.Transformers(model, tokenizer=tok)
generator = outlines.generate.cfg(outline_model, arithmetic_grammar)
sequence = generator("Alice had 4 apples and Bob ate 2. Write an expression for Alice's apples:")
print(sequence)
print(tracemalloc.get_traced_memory()[1])

Press the debug button on the top right of the UI in pycharm.
Expected result:
No circular imports
Error message:
Traceback (most recent call last):
  File "/home/simon/.local/share/JetBrains/Toolbox/apps/pycharm-professional/plugins/python/helpers/pydev/pydevd.py", line 45, in <module>
    from _pydevd_bundle import pydevd_utils
  File "/home/simon/.local/share/JetBrains/Toolbox/apps/pycharm-professional/plugins/python/helpers/pydev/_pydevd_bundle/pydevd_utils.py", line 6, in <module>
    import pydevd_file_utils
  File "/home/simon/.local/share/JetBrains/Toolbox/apps/pycharm-professional/plugins/python/helpers/pydev/pydevd_file_utils.py", line 48, in <module>
    import json
  File "/home/simon/PycharmProjects/outlines/outlines/generate/json.py", line 7, in <module>
    from outlines.fsm.json_schema import build_regex_from_schema, get_schema_from_signature
  File "/home/simon/PycharmProjects/outlines/outlines/__init__.py", line 2, in <module>
    import outlines.generate
  File "/home/simon/PycharmProjects/outlines/outlines/generate/__init__.py", line 6, in <module>
    from .json import json
  File "/home/simon/PycharmProjects/outlines/outlines/generate/json.py", line 7, in <module>
    from outlines.fsm.json_schema import build_regex_from_schema, get_schema_from_signature
  File "/home/simon/PycharmProjects/outlines/outlines/fsm/json_schema.py", line 6, in <module>
    from jsonschema.protocols import Validator
  File "/home/simon/PycharmProjects/outlines/.venv/lib/python3.11/site-packages/jsonschema/__init__.py", line 16, in <module>
    from jsonschema.validators import (
  File "/home/simon/PycharmProjects/outlines/.venv/lib/python3.11/site-packages/jsonschema/validators.py", line 20, in <module>
    from jsonschema_specifications import REGISTRY as SPECIFICATIONS
  File "/home/simon/PycharmProjects/outlines/.venv/lib/python3.11/site-packages/jsonschema_specifications/__init__.py", line 10, in <module>
    REGISTRY = (_schemas() @ _EMPTY_REGISTRY).crawl()
                ~~~~~~~~~~~^~~~~~~~~~~~~~~~~
  File "/home/simon/PycharmProjects/outlines/.venv/lib/python3.11/site-packages/referencing/_core.py", line 384, in __rmatmul__
    for resource in new:
  File "/home/simon/PycharmProjects/outlines/.venv/lib/python3.11/site-packages/jsonschema_specifications/_core.py", line 37, in _schemas
    contents = json.loads(path.read_text(encoding="utf-8"))
               ^^^^^^^^^^
AttributeError: partially initialized module 'json' has no attribute 'loads' (most likely due to a circular import)

Outlines/Python version information:
Version information
Outlines: 0.1.dev587+g4f8433d
Python3: Python 3.11.8 (main, Feb 12 2024, 14:50:05) [GCC 13.2.1 20230801]

```
aiohttp==3.9.5
aiosignal==1.3.1
annotated-types==0.6.0
attrs==23.2.0
certifi==2024.2.2
charset-normalizer==3.3.2
cloudpickle==3.0.0
datasets==2.19.1
dill==0.3.8
diskcache==5.6.3
filelock==3.14.0
frozenlist==1.4.1
fsspec==2024.3.1
huggingface-hub==0.23.0
idna==3.7
interegular==0.3.3
Jinja2==3.1.4
jsonschema==4.22.0
jsonschema-specifications==2023.12.1
lark==1.1.9
llvmlite==0.42.0
MarkupSafe==2.1.5
mpmath==1.3.0
multidict==6.0.5
multiprocess==0.70.16
nest-asyncio==1.6.0
networkx==3.3
numba==0.59.1
numpy==1.26.4
nvidia-cublas-cu12==<IP_ADDRESS>
nvidia-cuda-cupti-cu12==12.1.105
nvidia-cuda-nvrtc-cu12==12.1.105
nvidia-cuda-runtime-cu12==12.1.105
nvidia-cudnn-cu12==<IP_ADDRESS>
nvidia-cufft-cu12==<IP_ADDRESS>
nvidia-curand-cu12==<IP_ADDRESS>
nvidia-cusolver-cu12==<IP_ADDRESS>
nvidia-cusparse-cu12==<IP_ADDRESS>
nvidia-nccl-cu12==2.20.5
nvidia-nvjitlink-cu12==12.4.127
nvidia-nvtx-cu12==12.1.105
-e git+https://github.com/sorgfresser/outlines.git@4f8433d8d6633b0780c3a6c27981f9adffbe49f5#egg=outlines
packaging==24.0
pandas==2.2.2
pyairports==2.1.1
pyarrow==16.0.0
pyarrow-hotfix==0.6
pycountry==23.12.11
pydantic==2.7.1
pydantic_core==2.18.2
python-dateutil==2.9.0.post0
pytz==2024.1
PyYAML==6.0.1
referencing==0.35.1
regex==2024.4.28
requests==2.31.0
rpds-py==0.18.1
safetensors==0.4.3
six==1.16.0
sympy==1.12
tokenizers==0.19.1
torch==2.3.0
tqdm==4.66.4
transformers==4.40.2
triton==2.3.0
typing_extensions==4.11.0
tzdata==2024.1
urllib3==2.2.1
xxhash==3.4.1
yarl==1.9.4
```

Context for the issue:
See this stack overflow issue for a similar problem
https://stackoverflow.com/questions/20082730/module-object-has-no-attribute-loads-while-parsing-json-using-python

Oh and btw, if I resolve this one, same happens with the types module
Fatal Python error: init_import_site: Failed to import the site module
Python runtime state: initialized
Traceback (most recent call last):
  File "<frozen site>", line 195, in addpackage
  File "<string>", line 1, in <module>
  File "/home/simon/PycharmProjects/outlines/.venv/lib/python3.11/site-packages/__editable___outlines_0_1_dev587_g4f8433d_finder.py", line 4, in <module>
    from importlib.util import spec_from_file_location
  File "<frozen importlib.util>", line 14, in <module>
  File "/usr/lib/python3.11/contextlib.py", line 7, in <module>
    from functools import wraps
  File "/usr/lib/python3.11/functools.py", line 22, in <module>
    from types import GenericAlias
  File "/home/simon/PycharmProjects/outlines/outlines/fsm/types.py", line 2, in <module>
    from enum import EnumMeta
  File "/usr/lib/python3.11/enum.py", line 3, in <module>
    from types import MappingProxyType, DynamicClassAttribute
ImportError: cannot import name 'MappingProxyType' from partially initialized module 'types' (most likely due to a circular import) (/home/simon/PycharmProjects/outlines/outlines/fsm/types.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<frozen site>", line 626, in <module>
  File "<frozen site>", line 609, in main
  File "<frozen site>", line 541, in venv
  File "<frozen site>", line 394, in addsitepackages
  File "<frozen site>", line 236, in addsitedir
  File "<frozen site>", line 205, in addpackage
  File "/usr/lib/python3.11/traceback.py", line 5, in <module>
    import linecache
  File "/usr/lib/python3.11/linecache.py", line 8, in <module>
    import functools
  File "/usr/lib/python3.11/functools.py", line 22, in <module>
    from types import GenericAlias
  File "/home/simon/PycharmProjects/outlines/outlines/fsm/types.py", line 2, in <module>
    from enum import EnumMeta
  File "/usr/lib/python3.11/enum.py", line 3, in <module>
    from types import MappingProxyType, DynamicClassAttribute
ImportError: cannot import name 'MappingProxyType' from partially initialized module 'types' (most likely due to a circular import) (/home/simon/PycharmProjects/outlines/outlines/fsm/types.py)

This seems to be an issue with the way PyCharm is configured on your machine. Could you please try the solution from this similar issue and report back?
https://github.com/Tribler/py-ipv8/issues/981#issuecomment-817865339

It is related to PYTHONPATH for me. Agreed that this issue only happens with Pycharm due to the way they handle Pythonpath, but I still think that naming modules similar to native python modules is a bit confusing.


Response [Text] from Gemini split into several parts

Hi,
I have run several of the notebooks and codes in this repository (thanks a lot) and have the following question: Why is the response text received from Gemini so fragmented?
Example:
with the chapter03 code I obtained the following output text (I have changed the system instruction to prepend 'I hear you, Jerome' to each model's response) :
Connected to Gemini

You: Hello! Are you there?

Gemini: I

Gemini: hear you, Jerome. Yes, I am here. How can I help you

Gemini: today?

Why is the response server content split into three chunks ['I', 'hear you, Jerome. Yes, I am here. How can I help you', 'today?'] ?
Remark: same behavior without customized system instruction.
Thanks for the help
Jerome

I have checked and as expected each 'Gemini: ...' corresponds to a distinct server response. So why so many server responses for generating a single sentence?

Hi Jerome, the Live API is, by design, a streaming API. That means it will always stream responses at a given interval, that is why you will see text responses being chunked up. For complete text responses I would suggest the REST API instead.
Let me know if that answers your question.

Thanks for your comment. Yes, it confirms my thoughts about the Streaming API behavior. I was unsure if the high frequency of "chunks" was a feature or an issue. The queue management makes the audio output transparent. For the text output, as you mentioned, the standard non-streaming API seems more appropriate if I do not want to badly post-process the text chunks :)

The provided information is consistent. The issue is closed. Thanks


Remake metismenu sidebar css/js animations

Metismenu used js trickery to create the feeling of expanding/collapsing a section in the sidebar.
This should somehow be recreated to have a proper collapse/expanding animation instead of only fading in/out the section contents

Maybe a wrapper div can be made that uses an overflow and dynamically set height (required content height) to give the same illusion


Create deprecatedExport utility function

This idea was introduced in #2476. Also related to #1793.
This function will assist us with deprecating modules with "kebab-case" names in favor of more React compatible "PascalCase" names (for example TextField.jsx instead of text-field.jsx).
It would be used like this:
/* material-ui/lib/text-field.jsx */

import TextField from './TextField'; // new location
import deprecatedExport from './utils/deprecatedExport';

export default deprecatedExport(TextField, 'material-ui/lib/text-field', 'material-ui/lib/TextField');

@newoga I'm ok with this :smile:

@subjectix I guess that we should wait 0.14.0 before deprecating the current location of component.

@oliviertassinari Yeah this is gonna be a huge change! and must be eased into. let's just merge this for now. And wait for the right time before dropping the change :D

Sounds good to me! :)


Reproduce ApeX paper results for continuous action

Distributed Prioritized Experience Replay
Hyper parameters are shown in appendix D

Critic: [400, 300]
Actor: [300, 200]
Gradient clipping [-1, 1], element-wise
Adam with learning rate of 0.0001
The target network is copied from the online network every
100 training batches
Priority experience replay

alpha_sample = 0.6
alpha_evict = -0.4

Noise is added to DDPG with sigma = 0.3

Waiting for cpprb implementation of NStepReplayBuffer.


Fix link rendering

This fixes the issue of links not being clickable by adding support for rich text content. Links were currently rendered as plain text, because a TextBlock was used instead of a RichTextBlock, which will render plain text by default. Not fully sure if this is the way we want to go, as it also allows html to be entered from the receivers. The html is whitelisted according to the default rules specified for the project.
Tests are also converted to expect rich text from being used instead of normal text. Since RichText objects unfortunately don't support equality testing on text content, the tests are changed to test for the source value of the RichText instead of the RichText object.
Another small issue with Telegram links was fixed were links without protocol (e.g. www.example.com instead of https://www.example.com) were interpreted as relative urls to the page where they were rendered. To fix this, two slashes are prepended to the url, so that the browser can figure out the protocol by itself.

Codecov Report

Merging #113 (fc86ff6) into main (6919766) will decrease coverage by 0.14%.
The diff coverage is 84.61%.

@@            Coverage Diff             @@
##             main     #113      +/-   ##
==========================================
- Coverage   96.72%   96.57%   -0.15%
==========================================
  Files          41       41
  Lines        1100     1111      +11
  Branches      104      106       +2
==========================================
+ Hits         1064     1073       +9
- Misses         30       31       +1
- Partials        6        7       +1

Impacted Files
Coverage Δ

src/wagtail_live/receivers/telegram/utils.py
91.66% <50.00%> (-8.34%)
:arrow_down:

src/wagtail_live/blocks.py
100.00% <100.00%> (ø)

src/wagtail_live/receivers/telegram/receivers.py
100.00% <100.00%> (ø)

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 6919766...fc86ff6. Read the comment docs.


SAK-41705 Bunched bullhorn alerts into 10 minute intervals

![Uploading Screen Shot 2019-04-24 at 11.14.32.png…]()
![Uploading Screen Shot 2019-04-24 at 11.14.14.png…]()


Cannot connect to host <IP_ADDRESS>:80 ssl:default [[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1091)]

After installing the pool-reference I've got issue connecting to it.
When using 80 port I've got an error:

Exception from 'wallet' Error connecting to pool https://<IP_ADDRESS>:80: Cannot connect to host <IP_ADDRESS>:80 ssl:default [[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1091)]

trying with no port or default 443 gives connection error:

Exception from 'wallet' Error connecting to pool https://<IP_ADDRESS>: Cannot connect to host <IP_ADDRESS>:443 ssl:default [Connect call failed ('<IP_ADDRESS>', 443)]

It seems I'm missing setup for secure connection...

indeed. mainnet pools need to be https - you need to install nginx or something to handle httos for you, you also need to get a certificate and figure out how to renew it.
Please observe that pool-reference is not really intended to be run on production. It's to show how to implement a pool. There are many features of a pool that every production pool will want to have, such as leaderboards, making sure you don't violate the US law by sending rewards to countries which US forbids to interact with, making sure you don't do something silly if someone sends 1 mojo to the pool NFT, implementing some kind of a "user area" where they can see things private to their account, actually showing them something (like their current estimated capacity) or even just being able to tell how much effective capacity does your pool have in total. That's all not in the reference pool. You can either ignore those, implement them yourself or hire someone to do it. Maybe one day someone will create an opensource production-quality pool and you can use that, but so far it doesn't look like it's going to happen.

https support for reference https://github.com/Chia-Network/pool-reference/pull/170


Annotate vectorized lines

Made a version that will take an seletonized binary image and vectorize the first connected lines it finds.


Use ShaderBuilderTester more consistently across Model specs

Some tests were written before ShaderBuilderTester was created, so they were accessing shaderBuilder._fragmentShaderParts and other private variables.
This PR simply updates the usage everywhere for consistency.

Thanks for the pull request @ptrgags!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.


Navbar/next page button/page accessibility update for refactor

Closes #315 and #317
Some agent in the tool must be responsible for indicating that a page is accessible to the user (on the page via user action, or at some higher level like the navbar or layout, etc.) Previously, actions on a page by a user would manually change the accessibility status of the next page (via an action call to change pageData.<pageName>.accessible).
The navbar now keeps a watch on the store for changes, updating the accessible status of pages via updatePageDataAccessibility as the relevant changes are made to the store that would unlock them. This has the side effect of also keeping the next page button status on each page up to date with the state of the store.
The more complex Vuex getter isPageAccessible could not be reactive because it currently returns a boolean. Vue recalculates computed values based on whether or not values used in the computed function to create the return value have changed.. In the case of a primitive like a boolean with one return statement, isPageAccessible would only be calculated once. However, page accessibility state depends on multiple variables in the store depending on which page is being checked as accessible. Even a re-implementation of the function with multiple return statements does not produce the desired reactivity.
There are at least two methods for making sure that store changes trigger a check for page accessibility. The agent (in this case the tool-navbar component) can either place a watch on the specific store variables that may be involved in a state change OR it may deeply watch $store.state itself. (Suggestion for solution found here.)
This is accomplished via the placement of a watch in the created hook:
        created() {

            this.$store.watch(
                () => { return this.$store.state; },
                this.updatePageDataAccessibility,
                { deep: true }
            );
        },

The latter is the one implemented with this PR. A change in $store.state triggers a call to new store action updatePageDataAccessibility. The disabled attribute in the navbar and next page button are then simply tied to the pageData.<pageName>.accessible field which will always reflect the current state of the store.

Hey @jarmoza, thanks for the PR. I think I'm either missing a piece of info or I disagree here. I'll quickly reply on your explanation.

Some agent in the tool must be responsible for indicating that a page is accessible to the user (on the page via user action, or at some higher level like the navbar or layout, etc.) Previously, actions on a page by a user would manually change the accessibility status of the next page (via an action call to change pageData.<pageName>.accessible).

Agree. My understanding is that the isPageAccessible getter replaces the pageData.<pageName>.accessible attribute.

The more complex Vuex getter isPageAccessible could not be reactive because it currently returns a boolean. Vue recalculates computed values based on whether or not values used in the computed function to create the return value have changed.. In the case of a primitive like a boolean with one return statement, isPageAccessible would only be calculated once. However, page accessibility state depends on multiple variables in the store depending on which page is being checked as accessible. Even a re-implementation of the function with multiple return statements does not produce the desired reactivity.

Agree about vue-computed reactivity in general (as in your link). But the isPageAccessible getter doesn't just return a boolean. There is a good bit of logic in it to decide whether a page is accessible or not, given the current store.state (I think you are even the one who wrote it) - and we're making sure that all changes we make to the store.state are done in a way that doesn't break reactivity. So any reactive update to the dependencies of isPageAccessible should trigger the getter to be recomputed. And we have been using getters in this way (i.e. relying on them to be reactive) in the past too and this fits with the docs. I did a quick experiment to use the getter directly and the app also behaves reactively - here is a patch that you can apply if you want to see what I'm talking about (didn't want to push to your PR branch).
Let me know if there is something else I'm missing about the getter, but if not, I would say let's use the getter we already have here and avoid adding the extra actions and watchers.

@surchs I think the short answer to this is that while I understand what you're saying the reactivity for isPageAccessible just does not work on my end. I will try out your code and let you know.

@surchs So, in summary. Your code "works" for the nav as does the current code in the dev branch. In fact, we can currently navigate between the pages using the appropriate nav item even though it appears disabled (gray). Hovering over the activated nav item reveals a finger pointer which allows a click and pass through to the next page.
There was just one more step to make it fully work – and that's the line you have added in your patch above. With the check to isPageAccessible in the getNavItemColor function, now the nav item correctly turns green (bootstrap color variant success).
So agreed with your changes in the patch. We no longer need the accessible flags in pageData in the store nor the watch solution I came up with as a workaround for the above. I will commit those changes now.


feat: implements loading a Privacy Manager on demand

Description
We need a way to load the privacy manager on demand, like for example to allow users to change consent
The android flow is described here https://github.com/SourcePointUSA/android-cmp-app#loading-a-privacy-manager-on-demand
At this point we already need the SourcepointEventDelegate mechanism to be implemented, to be able to propagate consent changes to the app

This is depending on #6


Modbus ASCII Serial not working

I'm submitting a ...  (check one with "x")
Problem

(x ) bug report => please search github for a similar issue or PR and test Modbus problems with the modbus-serial package before submitting
( ) unexpected behavior => please visit the Wiki before

Current behavior
I have a connection to an RS-485 device that supports both Modbus ASCII and Modbus RTU (depending on a dispswitch). In Modbus RTU connection, the device answers and I am able to read out all registers. In ModBUS ASCII mode I do not receive any data form the device (with the correct dip switch set). When I try the same with ModbusPoll (https://www.modbustools.com/modbus_poll.html) I can read out the registers.
Expected behavior
Modbus ASCII should function as well.
Minimal reproduction of the problem with instructions

Connect to a Mdobus ASCII device
Read out regsiters
You will get a timeout

Your Environment
Please tell us about your environment:

( x) I am using just the Node-RED package and got modbus-serial package installed with it
( ) I have installed modbus-serial package global from source (using git clone)
( ) I have installed modbus-serial as a global package (using npm i -g)

Yes, modbus-serial is the name but it does all, TCP and Serial.
The node-modbus package is just for the Modbus Server node.

Device :

( ) macOS: v
( x) Linux: v10 (buster) - Debian
( ) Windows: v
( ) Raspbian: v
( ) Other:

Name:
Version:

Description of the connecting Modbus system:

Name   : ApexR5
Version: 1.05
Vendor : Lighthouse
Link   : https://www.golighthouse.com/en/airborne-particle-counters/apex-r5

node-red-contrib-modbus version: v5.14.0

Node: (v12.22.1)
node --version = v12.22.1

Duplicate: #277 already fixed


Fix heap enumeration on arm64e devices

This was previously discussed here: https://github.com/NSExceptional/FLEXing/issues/7
This solution seems to work 100% of the time, so I am assuming that locking and unlocking the zones is no longer needed on arm64e. It might be a good idea to confirm it however.
(Only applies for apps that have an arm64e slice, arm64 apps running on an arm64e device are not affected)

So, the issue, like you pointed out originally, is that PAC uses those high order bits, so the "max realistic address" check is probably failing. Instead of getting rid of the check entirely, we just need to make the check work properly knowing that PAC uses those high bits.
My first idea is to check out the PAC APIs and see if there's a function to mask out the PAC bits.
My second idea is to use a function I forgot I added that checks if a memory address is valid and readable. This is the problem I was trying to solve in the first place, so this seems perfect for what we need.
See if you can modify the check to use that function instead of a < comparison. (You'll need to add it to FLEXObjcInternal.h as it isn't exposed publicly right now).
As for why we need the check, it's my understanding that without locking the heap there is a race condition while we enumerate it. We might be given an address that is freed on another thread while we're about to read it, which causes nondeterministic and somewhat rare crashes. So it's no surprise to me that it would appear removing the check works 100% of the time. It probably just exposes you to the rare chance of crashing, though.

Yes, such a function exists, I previously used it to mask out the PAC, but even then, as I pointed out in the comment, it caused the thread to freeze up when calling (un)lock_zone. I will try to use it in addition to that function and see if that improves it.

I've fixed it all, thank you for this!


Deprecate IGListStackedSectionController

Changes in this pull request
Issue fixed: #1099
Checklist

[x] All tests pass. Demo project builds and runs.
[x] I added tests, an experiment, or detailed why my change isn't tested.
[x] I added an entry to the CHANGELOG.md for any breaking changes, enhancements, or bug fixes.
[x] I have reviewed the contributing guide

hi, in the CI tasks, the build Example task fails to use the updated IGListKit code. (IGListStackedSectionControllerInternal.h is already deleted by the PR)

I suggest run pod install or pod update before xcodebuild, so the Examples always use the latest IGListKit code :)

I was about to delete this guy too, glad that you are on it! thanks!

hi @lorixx , the PR is rebased to the latest master for resolving the merge conflict :)


Cut face vertices doesn't perfectly match the mesh

Hi,
First, thanks for the package, it is really cool !
I am facing an issue, and I am in trouble to resolve it. The cut face doesn't match exactly the original mesh (see picture bellow) :
Original mesh :

Fractured mesh :

The main issue is that the mesh is concave, so the vertices go straight to point A to point B. Do you see a way to fix this behavior ?
Thanks in advance !
Have a nice day.

I finaly found a workaround,
I set the material transparent while it's frozen, then I change it to opaque as soon as it is unfrozen.

@GSoftcaze The algorithm can handle concave meshes. The artifact you are seeing means your mesh has open or self-intersecting geometry. Please see the README for more information.


Only set valid fields when building SiweMessage with dictionary

When building a SiweMessage instance from an input dictionary, only set valid fields.
Resolves #15

Initially, I thought we should raise a ValueError when building from a dictionary if there was an invalid field. However, I'm now leaning more towards the idea of passively skipping invalid fields since any missing attributes / invalid attributes should be caught when validating... What are your thoughts @sbihel and @twinsant?

That's fine.


Make save_dir if doesn't exist

Before:
$ python train.py --save_dir save/some_sub_dir/another_sub_dir
loading preprocessed files
Traceback (most recent call last):
  File "train.py", line 116, in <module>
    main()
  File "train.py", line 48, in main
    train(args)
  File "train.py", line 79, in train
    with open(os.path.join(args.save_dir, 'config.pkl'), 'wb') as f:
IOError: [Errno 2] No such file or directory: 'save/some_sub_dir/another_sub_dir/config.pkl'

After:
$ python train.py --save_dir save/some_sub_dir/another_sub_dir
loading preprocessed files
0/22300 (epoch 0), train_loss = 4.828, time/batch = 3.988
...

@sherjilozair Can this be merged?

seems reasonable, i'll give a quick test


Ability to set --assets-dest for static images (RN 0.14+)

Since RN 0.14 static images can be required from within project files, however this requires an additional build step in Xcode which bundles the index.ios.js file complete with all other assets. (Same goes for android, but this is specified in the android/app/react.gradle file).
So is there a possibility to set the --assets-dest for react-native bundle during the buildprocess of react-native-webpack-server (as it's done in node_modules/react-native/packager/react-native-xcode.sh)?

+1


What do we do when a stats key (or name) exists in multiple data sets?

Currenly I believe we allow api designers to do this if they want, though if the names are the same the user obviously has no idea what the difference between the two options is. On the backend we keep track of path so shouldn't cause any issues (untested)


Set initial type of filter if creating a copy

When creating a new filter from an existing global filter it was saved as a local even when Global Search was checked. Initial search_type was set to nil (to local) for all.
@miq-bot add_label ui, bug
Links
https://bugzilla.redhat.com/show_bug.cgi?id=1356035
Steps for Testing/QA [Optional]
Compute -> Infrastructure -> Virtual Machines -> VMs -> Advanced Search
Create a new global filter using an existing one -> filter is in Global Filters tree (don't check/uncheck Global search)
Create a new local filter using an existing one -> filter is in My Filters tree (don't check/uncheck Global search)

Restarting the build

Euwe Backport details:
$ git log
commit 5c81d69905fe7fd0b8fe2e6af4b0899be0ac14ab
Author: Milan Zázrivec<EMAIL_ADDRESS>Date:   Tue Oct 4 13:54:27 2016 +0200

    Merge pull request #11658 from ZitaNemeckova/bz1356035

    Set initial type of filter if creating a copy
    (cherry picked from commit 6969246e2fabef17adca4bbdf86f907f73b15284)

@simaishi need Darga BZ

Darga BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1382834

Darga Backport details:
$ git log
commit 6a097d3338968c43961aa0bc372f30f8e14b015d
Author: Milan Zázrivec<EMAIL_ADDRESS>Date:   Tue Oct 4 13:54:27 2016 +0200

    Merge pull request #11658 from ZitaNemeckova/bz1356035

    Set initial type of filter if creating a copy
    (cherry picked from commit 6969246e2fabef17adca4bbdf86f907f73b15284)

    https://bugzilla.redhat.com/show_bug.cgi?id=1382834


Apphash failure - height: 6241714 - expected A630501E2FBAC8846FCB5A6530550ECFC204B527B9061CB2DFB2A1333335F103 got D448D7022BE2B1850DF10E4E3537D1730759594D5C260F2751BD7D7F8970C32D

Hello,
Our nodes have failed few hours ago with an apphash failure (see below)
I was able to recover them by using your 4.1.4 tag, changing the upgrade handler and get past startup error.
Regardless, Can you confirm the current code version / commit id?
Looking at node_info of some of the validators - it shows commit 8e48e6189160e59bbd086716225dad2a228ab486, but this commit is not present in your white-whale-core repository
Can you please advise?
{"level":"error","module":"server","module":"consensus","height":6241714,"round":0,"err":"wrong Block.Header.AppHash.  Expected A630501E2FBAC8846FCB5A6530550ECFC204B527B9061CB2DFB2A1333335F103, got D448D7022BE2B1850DF10E4E3537D1730759594D5C260F2751BD7D7F8970C32D","time":"2024-04-02T22:50:14Z","message":"prevote step: consensus deems this block invalid; prevoting nil"}
2024-04-02 22:50:14,054 DEBG 'cosmovisor' stdout output:
{"level":"error","module":"server","module":"consensus","height":6241714,"round":0,"err":"wrong Block.Header.AppHash.    Expected A630501E2FBAC8846FCB5A6530550ECFC204B527B9061CB2DFB2A1333335F103, got D448D7022BE2B1850DF10E4E3537D1730759594D5C260F2751BD7D7F8970C32D","time":"2024-04-02T22:50:16Z","message":"prevote step: consensus deems this block invalid; prevoting nil"}
2024-04-02 22:50:16,835 DEBG 'cosmovisor' stdout output:
{"level":"error","module":"server","module":"consensus","height":6241714,"round":1,"err":"wrong Block.Header.AppHash.  Expected A630501E2FBAC8846FCB5A6530550ECFC204B527B9061CB2DFB2A1333335F103, got D448D7022BE2B1850DF10E4E3537D1730759594D5C260F2751BD7D7F8970C32D","time":"2024-04-02T22:50:16Z","message":"prevote step: consensus deems this block invalid; prevoting nil"}

{"level":"error","module":"server","module":"consensus","err":"precommit step; +2/3 prevoted for an invalid block: wrong Block.Header.AppHash.  Expected A630501E2FBAC8846FCB5A6530550ECFC204B527B9061CB2DFB2A1333335F103, got D448D7022BE2B1850DF10E4E3537D1730759594D5C260F2751BD7D7F8970C32D","stack":"goroutine 1015 [running]:\nruntime/debug.Stack()\n\truntime/debug/stack.go:24 +0x5e\ngithub.com/cometbft/cometbft/consensus.(*State).receiveRoutine.func2()\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:736 +0x46\npanic({0x2e1d500?, 0xc0157e3380?})\n\truntime/panic.go:914 +0x21f\ngithub.com/cometbft/cometbft/consensus.(*State).enterPrecommit(0xc001020000, 0x5f3db2, 0x1)\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:1463 +0x15d9\ngithub.com/cometbft/cometbft/consensus.(*State).addVote(0xc001020000, 0xc02ca9e820, {0xc0018840c0, 0x28})\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:2195 +0x140f\ngithub.com/cometbft/cometbft/consensus.(*State).tryAddVote(0xc001020000, 0xc02ca9e820, {0xc0018840c0?, 0xc02833bc08?})\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:2012 +0x26\ngithub.com/cometbft/cometbft/consensus.(*State).handleMsg(0xc001020000, {{0x4144660, 0xc02ac49538}, {0xc0018840c0, 0x28}})\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:865 +0x3ce\ngithub.com/cometbft/cometbft/consensus.(*State).receiveRoutine(0xc001020000, 0x0)\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:772 +0x3d1\ncreated by github.com/cometbft/cometbft/consensus.(*State).OnStart in goroutine 268\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:383 +0x10c\n","time":"2024-04-02T22:50:17Z","message":"CONSENSUS FAILURE!!!"}
2024-04-02 22:50:17,342 DEBG 'cosmovisor' stdout output:
{"level":"error","module":"server","module":"consensus","err":"precommit step; +2/3 prevoted for an invalid block: wrong Block.Header.AppHash.  Expected A630501E2FBAC8846FCB5A6530550ECFC204B527B9061CB2DFB2A1333335F103, got D448D7022BE2B1850DF10E4E3537D1730759594D5C260F2751BD7D7F8970C32D","stack":"goroutine 1015 [running]:\nruntime/debug.Stack()\n\truntime/debug/stack.go:24 +0x5e\ngithub.com/cometbft/cometbft/consensus.(*State).receiveRoutine.func2()\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:736 +0x46\npanic({0x2e1d500?, 0xc0157e3380?})\n\truntime/panic.go:914 +0x21f\ngithub.com/cometbft/cometbft/consensus.(*State).enterPrecommit(0xc001020000, 0x5f3db2, 0x1)\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:1463 +0x15d9\ngithub.com/cometbft/cometbft/consensus.(*State).addVote(0xc001020000, 0xc02ca9e820, {0xc0018840c0, 0x28})\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:2195 +0x140f\ngithub.com/cometbft/cometbft/consensus.(*State).tryAddVote(0xc001020000, 0xc02ca9e820, {0xc0018840c0?, 0xc02833bc08?})\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:2012 +0x26\ngithub.com/cometbft/cometbft/consensus.(*State).handleMsg(0xc001020000, {{0x4144660, 0xc02ac49538}, {0xc0018840c0, 0x28}})\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:865 +0x3ce\ngithub.com/cometbft/cometbft/consensus.(*State).receiveRoutine(0xc001020000, 0x0)\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:772 +0x3d1\ncreated by github.com/cometbft/cometbft/consensus.(*State).OnStart in goroutine 268\n\tgithub.com/cometbft/cometbft@v0.37.4/consensus/state.go:383 +0x10c\n","time":"2024-04-02T22:50:17Z","message":"CONSENSUS FAILURE!!!"}

Hello please join the White Whale Discord and open a ticket there


Docs: Correct arg offsets to offset in tooltips & popovers

Tooltips & Popovers accept offset as arg, not offsets.

Thanks!


Allow maps to be in sub-folders and Update TDM scoreboard, Fixes #692 & #698

This update allow to you to manage your maps in diffrent sub-folders.
Example:

maps/ctw
maps/destroy/dtc
maps/destroy/dtm
...

Any suggestions ?

:+1:

Sorry for the double commit but I didn't know that was going to add it to this one.

These need to be in separate pull requests, use branches. Refer to my points in #728 for the criteria I am looking for.


RuntimeError: CUDA out of memory

I've added model.half() underneath model = instantiate_from_config(config.model)
and init_image = init_image.half() underneath init_image = repeat(init_image, '1 ... -> b ...', b=batch_size)
I get this error:
RuntimeError: CUDA out of memory. Tried to allocate 1024.00 MiB (GPU 0; 4.00 GiB total capacity; 2.56 GiB already allocated; 183.30 MiB free; 2.58 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
What should I do?

maybe is because your GPU has only 4GB of VRAM, what image size was your prompt made with?

I was trying with 512 x 512

i seem to be having the same problem with a 10gb 3080 card. even if i just boot linux right into cmd with zero usage of gfx ram i still have it complaining about memory. and that is with a 512 x 512 pic...

I tried this instead: https://github.com/AUTOMATIC1111/stable-diffusion-webui
with --medvram --opt-split-attention in the webui-user.bat file, which works for me just fine. You might not need that command though, since you have 10gb vram

Line 62, replace   model.cuda() by  model.cuda().half()

for me the parameters --medvram are not available on txt2imghd.py - did i miss a step during "installation"? i tried recreating it from copying parts of the optimized/webui but without success. Any ideas on how to get it running on low VRAM GPUs yet?

for me the parameters --medvram and --opt-split-attention are not available on txt2imghd.py - did i miss a step during "installation"? i tried recreating it from copying parts of the optimized/webui but without success. Any ideas on how to get it running on low VRAM GPUs yet?

Those parameters are for a different one, you need to download this first.
Follow the install instruction and then in the webui-user.bat file you'll put --medvram --opt-split-attention in the commandline_args


Feature/685 lead convert

Warning
Information

NPSP's Lead Convert page has been enhanced to support specifying an Account model Account and Affiliation, when the lead has an Organization account in its Company field.  This gives more flexibility to convert leads with companies, into the account model you want.

Issues
Fixes #1471
Fixes #965
Fixes #685

@njjc ready for review and merge.  let me know if you want to go through it together.  thanks!


bug fix: wrong prompt when pull non-existent repo

when we try to pull a non-existent repo, docker client will show us wrong format error prompt like this:

and docker daemon will show log like this:

The reason why docker client show wrong format error message is that docker daemon doesn't reply with correct json format error message;
the reason why docker daemon print http: Multiply response.WriteHeader calls is that when daemon use out.Write() function to reply a message to client, it will call WriteHeader() to write a default status code of 200, then after error happens, it will call httpError() which tries to call WriteHeader() again to write a error StatusCode.

My patch is written based on those two reasons above.
After fixing this bug, docker client will show errors like this:

and daemon show errors like:

Hope you will be satisfied with its final look. :)
Signed-off-by: Zhang Wei<EMAIL_ADDRESS>

@jlhawn I just read your code in PR #12649, it seems I miss the scenario of import. But after this, problem multiple response.WriteHeader calls still exists because the httpError logic.
Though this is not a critical bug and seems won't cause serious problem, it seems go language is telling us we are using this in a wrong way.
Is this what you want and are you fine with this?
@jfrazelle @jlhawn

we need an integration test like the ones i wrote for the other PR

@WeiZhang555 @jfrazelle The multiple response.WriteHeader calls is probably not an issue that can be fixed because of the way we stream responses (many docker API endpoints behave this way). As you described above, we start writing the response before we know whether or not the operation failed and simply writing a response uses a default header/status of 200 OK.

@WeiZhang555 @jfrazelle it looks like we meant to close this issue/PR with https://github.com/docker/docker/pull/12649#issuecomment-95321034 what do you think?


It's not possibile to load_database (format cdd)

Hello guys,
I'm trying to open and parse CDD but I get this error
File "C:\Users\gaia.littarru\AppData\Local\Programs\Python\Python37\lib\site-packages\cantools\database_init_.py", line 228, in load_string
raise UnsupportedDatabaseFormatError(e_dbc, e_kcd, e_sym, e_cdd)
cantools.database.UnsupportedDatabaseFormatError: CDD: "invalid literal for int() with base 10: '2,0,0'"
It seems there is a problem with data type.
Have you already noticed this issue?
Thanks for the help,
Gaia

No. If you provide a CDD-file that fails as above I can have a look at it and hopefully add support for it.

Closing in a few days if there is no answer.


Add a way to retrieve location from diagnostics

We should add a mapping from AST nodes to locations (objects may cause problems here) and a common superclass for all diagnostics containing AST nodes with an abstract method/property to retrieve these nodes (which could then be used to retrieve the location).

Good enough. (Although I still maintain the opinion that we shouldn't convert AST nodes to strings, but display and highlight the actual code.)


avro-tools: 1.11.3 -> 1.12.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/avro/versions.
meta.description for avro-tools is: Avro command-line tools and utilities
meta.homepage for avro-tools is: https://avro.apache.org/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.12.0 in filename of file in /nix/store/bmdnh5wx9i88775w2scl9s3nk725nyyw-avro-tools-1.12.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

avro-tools

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bmdnh5wx9i88775w2scl9s3nk725nyyw-avro-tools-1.12.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A avro-tools https://github.com/r-ryantm/nixpkgs/archive/320122395bdb7d3530acdce26e308f7555371cd0.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/320122395bdb7d3530acdce26e308f7555371cd0#avro-tools

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bmdnh5wx9i88775w2scl9s3nk725nyyw-avro-tools-1.12.0
ls -la /nix/store/bmdnh5wx9i88775w2scl9s3nk725nyyw-avro-tools-1.12.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

avro-tools

Maintainer pings
cc @momeemt for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Include automatic formatting in CI

This could be done with GH actions but may be better suited to a git pre-commit hook.

Implemented by using pre-commit to run black b60e938 still nothing for docstrings or markdown.

Fully resolved with #11


Added entry for google-kubernetes-engine-plugin.yml

Description
Google Kubernetes Engine Plugin
Plugin repo: https://github.com/jenkinsci/google-kubernetes-engine-plugin
Hosting request issue: https://issues.jenkins-ci.org/browse/HOSTING-691
Submitter checklist for changing permissions
Always

[X] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[X] Add link to resolved HOSTING issue in description above

For a new permissions file only

[X] Make sure the file is created in permissions/ directory
[X] artifactId (pom.xml) is used for name (permissions YAML file).
[X] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[X] Check that the file is named plugin-${artifactId}.yml for plugins

It was changed two hours ago, not sure why @craigatgoogle
https://github.com/jenkinsci/google-kubernetes-engine-plugin/commit/4d270a868e66cd446136385b53625fe1f1946540

That was my mistake. It's changed back now.

To keep the commit log clean I'll close this and re-submit.


Migrating ESP32-BLECollector

hello and thank you for this great library!
It totally removed the burden of having to deal with "does not fit in ram" situations.
So after migrating my code to the new NimBLE syntax, I found out I was initially using a modified version of the official BLE library and manually applied a few patches.
I was pleasantly surprised to see that most of those changes are already adressed in your library :+1:
However I couldn't find a matching method for one missing method pChar->getDataLength().
In my project getDataLength() is used for file transfer situations with variable MTU.
In order to get my sketch working and go on with more tests, I added this to src/NimBLECharacteristic.h.
size_t getDataLength() { return m_value.getLength(); }

So my question is: do I really need to modify src/NimBLECharacteristic.h to get the lenght of the data or is there a way to do that more elegantly ?

That's great, i'm glad you find it useful 😄 .
As this project was derived mainly from the original library the only intent so far was to replicate it for NimBLE as best as possible and make changes/fixes that I thought made sense.
As there was not existing API for that particular function in the original I have not created a more elegant solution.
I'd be glad to add it as a feature as others may find it useful also. I'm currently working on an update to address a few other issues as well so I could incorporate this at the same time. Feel free to submit a PR if you'd like.

PR #14 it is :-)


Static array UFCS-style

This is #6178 rebooted, so most of this is work of @timotheecour  , not mine. It tries to address the last review @andralex made of it, and also some feedback made to #6214, which is my pull request aiming for same functionality.

Circleci crashed. Trying to restart...

Anybody know how I can fix the Circleci seqfault?

@andralex exceptions and destructor thing addressed.
Good catch btw! I think no-one else noticed.

@andralex  "Looked" once more.

@wilzbach CircleCI fails to compile but my local version and the autotester does not. What is happening?

I think the issue is that object._ArrayDtor!(CopyPreventer) does not have a scope attribute in it's parameter. It's either in DRuntime or dmd itself, so fixing it here is out of question. I just wrapped the function call complained about in @trusted. I try to produce a test case so I can file a bugzilla Issue to refer to in comment.
Otherwise, ready for review! @andralex

Thanks for the comments. All explained and/or fixed.

@andralex  Tests pass and it's ready for another try.

ping @andralex

Okay, addressed.

ping @andralex

@wilzbach Docs corrected. But I don't want to squash, because I don't know how to squash commits by others. I don't want to accidently remove all credit to Timothee!
I let you to do that, if you want.

But I don't want to squash, because I don't know how to squash commits by others. I don't want to accidently remove all credit to Timothee!
I let you to squash them, if you want. But please do not remove Timothee.

Okay squashed them down to two commits (i.e. all your commits into one and commits of Timothee into one commit).

Auto-merge toggled on


No author in output

I cannot get authors in the output PDF.
$ asciidoctor-pdf --version
Asciidoctor PDF 1.5.4 using Asciidoctor 2.0.12 [https://asciidoctor.org]
Runtime Environment (ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu]) (lc:UTF-8 fs:UTF-8 in:UTF-8 ex:UTF-8)

Test file:
= Test Document
Author<EMAIL_ADDRESS>
Contents

The authors are only shown when the document has a title page. You can add a title page either by setting the title-page attribute in the document header or setting the doctype to book.

OK, but I think it is also a valid use to have author displayed without a title page. When I have a one-page document, I don't necessarily want a separate title page. Maybe turn this into a feature request?

This has already been reported as #988. Feel free to follow-up there. Note, however, that it is not a feature I will be working on, so the implementation will have to come from the community.

Based on https://github.com/asciidoctor/asciidoctor-pdf/issues/66#issuecomment-1128562591, https://github.com/asciidoctor/asciidoctor-pdf/issues/988#issuecomment-1128579996 and quite some trail and error, I've come up with
pdf-converter-article-title-with-author-and-date.rb
class PDFConverterArticleTitleWithAuthorAndDate < (Asciidoctor::Converter.for 'pdf')
  register_for 'pdf'

  def ink_general_heading doc, title, opts
    return super unless opts[:role] == :doctitle
    theme_font :heading_doctitle do
      ink_prose title, align: :center
    end
    revremark = doc.attributes['revremark']
    if doc.author or doc.revdate or revremark
      theme_font :base do
        author_date_separator = (doc.author and doc.revdate) ? " – " : ""
        revremark_separator = ((doc.author or doc.revdate) and revremark) ? " | " : ""
        ink_prose "#{doc.author}#{author_date_separator}#{doc.revdate}#{revremark_separator}#{revremark}", align: :center
      end
    end
    theme_margin :heading_doctitle, :bottom
  end
end

which adds author, revdate and revremark information to articles without a separate title page.
Does this look reasonable? Can it be improved or be made more general (e.g. to support multiple authors)?
Would it make sense to add something like this to https://docs.asciidoctor.org/pdf-converter/latest/extend/use-cases/ ?

I'd certainly be open to including this example on the use cases page. Would you like to submit a pull request?

Would you like to submit a pull request?

Sure. Where on that page should it go? Is there any particular order to the sections there?

I would recommend using your best judgement. Probably near an extension that works on a similar aspect. That's what I would end up doing. Maybe after Custom title page?

PR filed: #2439


CMake layouts not being honoured for CMake commands

Tested this with Conan Center zlib.
That recipe uses this layout:
    def layout(self):
        cmake_layout(self, src_folder="src")

and I see the CMake cache file in build/Release.
When using the layouts, this is different behaviour to earlier Conans which would, by default, place the build output folder beside the recipe.
If I remove the use of layouts, and the patching, then the cruiz CMake buttons work again.
This may also be an effect of old vs new generators.

The layout folder seems to be harder to extract than just querying the inputs passed to Conan.
It seems to be related to this call
    if hasattr(conanfile, "layout") and not test:
        conanfile.folders.set_base_folders(conanfile_path, output_folder)
    else:
        conanfile.folders.set_base_install(install_folder)
        conanfile.folders.set_base_imports(install_folder)
        conanfile.folders.set_base_generators(base_folder)
        conanfile.folders.set_base_source(base_folder)
        conanfile.folders.set_base_build(base_folder)

    if hasattr(conanfile, "layout") and test:
        install_folder = conanfile.generators_folder

which is similar in a number of places in the Conan source tree.

The above is not entirely true, as there is an earlier call to run_configure_method including this
        # Once the node is configured call the layout()
        if hasattr(conanfile, "layout"):
            with conanfile_exception_formatter(str(conanfile), "layout"):
                conanfile.layout()

which does a lot of the setup. In the previous comment, that was more about expanding to absolute folder paths.

This is accessible after lockfile creation, in depsgraph.root.conanfile.folders.build as a relative path.


Add support for MessageInput, MessageList and MessageListItem

These components are also in Vaadin 14

Implemented MessageInput._submit(), however no idea what kind of support to introduce for MessageList. If anyone has an idea, please file a new request ticket.


GORM Changelog

Your Question
Is there any changelog for Gorm? When I click on the version on the Docs, I go to "GORM 2.0 Release Note", but I would need more granular version changes because I am using v1.20.12 and I would like to know what changed up to v1.21.8.
The document you expected this should be explained
https://gorm.io/docs/v2_release_note.html
Expected answer
If possible, could you add a link to a changelog of minor versions (if it exists somewhere)? Thanks by advance

Maybe helpful.
https://github.com/go-gorm/gorm/releases
https://github.com/go-gorm/gorm/compare/v1.20.12...v1.21.8

Thanks! There should be a link to this page from the documentation 😉


Upgrade OC packages and drivers

@Piedone @sarahelsaig

@sarahelsaig @Piedone hold off on merging this PR until we first merge https://github.com/OrchardCMS/OrchardCore/pull/16530 . Once merged, I'll fix any other warnings here before merging it

@sarahelsaig @Piedone this PR is ready with all the changes from the drivers.


Isn't working on mozilla support pages

Not working on mozilla support pages. Try this one https://support.mozilla.org/en-US/questions/1261804
I checked all my settings and I don't have any custom settings for support.mozilla.org

Yes, browser vendors do a very pure job conveying to users where they can use extensions and where it is forbidden due to security reasons. Basically all browser system pages, web store and other parts the of vendor website are forbidden by each vendor. For that specific reason I do use Chrome to browse Firefox add-ons and vice versa😂


Automate command output in docs

/area documentation
/kind epic

What mistake did you find / what is missing in the documentation / what is the relevance of it?

Store the current output for all the commands in separate mdx files.
Write integration/unit tests comparing the real time output of a command with the one stored in the mdx files.
If the test fails, it means that we need to update the output in mdx files.
The tests will be run in the CI for every PR.

For reference - https://www.youtube.com/watch?v=AQDILnknTJ0&list=PLUJzERpatfsWYhMH0NOjSXemQh5Tu9g1W&index=32&t=3s (it is in french)
Acceptance Criteria

[x] #6517
[ ] Every command output should be put inside a docs-mdx/.mdx file.
[ ] Command Reference

[ ] odo dev
[x] odo init (#6442)
[ ] odo preference view
[ ] odo add binding
[ ] odo remove binding
[x] #6675
[x] odo delete namespace #6724
[ ] odo build-images
[ ] odo list
[ ] odo list namespace #6724
[ ] odo list component
[ ] odo list binding
[ ] odo deploy
[ ] odo describe binding
[ ] odo describe component
[ ] odo logs
[ ] odo set namespace #6724
[ ] odo registry

[ ] User Guides

[x] Quickstart (WIP)
[ ] Test Quickstart guides on Podman
[ ] Advanced Guide
[ ] Connecting to a service
[ ] Experimental Mode

Example PR: #6442

LGTM. I agree there is a lot of repetitive data, but since the Devfiles are quite different, it might be hard to factorize, IMO. Not an expert with MDX / JSX stuff, but there might be some room for reusability. So I am not sure it would be worth spending time right now trying to optimize this.
However, this makes me think of 2 things:

Based on a recent discussion, maybe we could use each of those Devfiles as input in E2E tests, and import them as is in these docs. This way, we would be able to test them as well. And for line highlighting in the Docs, I can imagine some generic MDX Component accepting the path to the Devfile along with line numbers as input properties, so as to keep highlighting the relevant lines.

These Advanced Guides could be simplified further now that we support parsing multi-document YAML in a single K8s component (#6372)

But that's another story that can be handled in separate PRs.

https://github.com/redhat-developer/odo/pull/6388#pullrequestreview-1209842454

As discussed, this low-priority item (from the 2023Q1 goal) has been moved back into the backlog.

/reopen
/remove-lifecycle stale
/remove-lifecycle rotten
/lifecycle frozen


Create housing category and add housing unit (by race) charts

Trying to see how we can make a unified json format through lint..

I've updated my editor to only format lines that have changed.

good to know!


Change task counter AtomicU64 to AtomicU32

cross compile with mipsel-unknown-linux-uclibc(32bit) error:
root@8bc5bd79cb06:/opt/liukai/rust/async-t# xargo build --target mipsel-unknown-linux-uclibc --release
   Compiling async-std v0.99.4
error[E0432]: unresolved import `std::sync::atomic::AtomicU64`
 --> /root/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/async-std-0.99.4/src/task/task.rs:6:25
  |
6 | use std::sync::atomic::{AtomicU64, AtomicUsize, Ordering};
  |                         ^^^^^^^^^
  |                         |
  |                         no `AtomicU64` in `sync::atomic`
  |                         help: a similar name exists in the module: `AtomicU16`

error[E0432]: unresolved import `std::sync::atomic::AtomicU64`
 --> /root/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/async-std-0.99.4/src/task/blocking.rs:5:25
  |
5 | use std::sync::atomic::{AtomicU64, Ordering};
  |                         ^^^^^^^^^
  |                         |
  |                         no `AtomicU64` in `sync::atomic`
  |                         help: a similar name exists in the module: `AtomicU16`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0432`.
error: Could not compile `async-std`.

To learn more, run the command again with --verbose.

I worry that 32 bits might not be enough and that one could easily spawn tasks in a loop and overflow the counter. Perhaps we could "simulate" 64-bit atomics on platforms that don't support them with a mutex or some kind of trick with two 32-bit atomic numbers?

I worry that 32 bits might not be enough and that one could easily spawn tasks in a loop and overflow the counter. Perhaps we could "simulate" 64-bit atomics on platforms that don't support them with a mutex or some kind of trick with two 32-bit atomic numbers?

emmm... Can we use AtomicUsize?  Just like tokio_timer

I worry that 32 bits might not be enough and that one could easily spawn tasks in a loop and overflow the counter. Perhaps we could "simulate" 64-bit atomics on platforms that don't support them with a mutex or some kind of trick with two 32-bit atomic numbers?

Can we set it to AtomicU64 on 64-bit and AtomicU32 on 32-bit?

I still worry that the IDs could be overflowed on 32-bit platforms.

Perhaps we could "simulate" 64-bit atomics on platforms that don't support them with a mutex or some kind of trick with two 32-bit atomic numbers?

Perhaps like this:
cfg_if::cfg_if! {
    if #[cfg(target_pointer_width = "64")] {
        pub(crate) use std::sync::atomic::AtomicU64;
    } else {
        #[derive(Debug)]
        pub(crate) struct AtomicU64(std::sync::Mutex<u64>);

        impl AtomicU64 {
            pub(crate) fn load(&self, _: Ordering) -> u64 {
                *self.0.lock().unwrap()
            }
            // .. some methods
        }
    }
}

@taiki-e Yes, although I suggest using Mutex on mips platforms only rather than on all 32-bit platforms.

@stjepang Ah, Indeed. I missed that AtomicU64 is #[cfg(target_has_atomic = "64")], not #[cfg(target_pointer_width = "64")].

IMO DYNAMIC_THREAD_COUNT can be replaced with AtomicUsize.

IMO DYNAMIC_THREAD_COUNT can be replaced with AtomicUsize.

I thought so before, but it seems that they want to find a better solution.
std::sync::atomic

It's totally fine for DYNAMIC_THREAD_COUNT to be an AtomicUsize :)

The new PR is here: https://github.com/async-rs/async-std/pull/451


Typo in repo description

Delightful Hpyerterm packages and resources
should be
Delightful HyperTerm packages and resources
Thanks!
PS: you could also add a space between the emoji and Delightful, would be 💯

There are actually several instances of this - thanks for pointing it out!

Ah, actually misunderstood what the typo was. Dyslexia 🙄
Looks like there is a space there to me - could you give a screenshot or copy and paste of what you mean?

Looks good
Thanks


Replace 'imageClickHandler' with event emitter

Replace the configuration elements for 'imageClickHandler' with an angular event emitter.
This (breaking) change would make MatImageOverlay more consistent (no mix of functions as configuration parameters and event handlers) and improve the conformance with the angular programming style.

Solved with version 15.1.0


Insights on additional potential breakages

Feature Request
Description:
Detect more libraries that may have potential breakages and guide the user to verify the site's CUJs using those libraries.
List of libraries to add

[x] Facebook comment widget
[x] Facebook like button
[x] Disqus widget
[x] Jetpack comments & likes
[x] reCAPTCHA

Addressed and released in v0.6


Issue with page navigation in 20.0.3

Hello, I have updated PuppeteerSharp to 20.0.3 recently and faced issue with navigation to url. I use this code:
var navigationTask = page.WaitForNavigationAsync(new NavigationOptions
{
    Referer = referer,
    WaitUntil = new[] { WaitUntilNavigation.Networkidle0 },
    Timeout = 40000
});
await page.GoToAsync(link);
try
{
    await navigationTask;
}
catch
{
}

and sometimes nothing happen, not even single try to load page, just default chrome page. If reconnect to browser and try again it can make navigation. But sometimes everything work properly without reconnection. I have not any idea what is wrong...

Networkidle0 can be flaky sometimes.


[Common] Use nvtx3

Description
nvtx3 is a newer nvtx API and it is header-only, where old nvtx requires to link.
PaddlePaddle is using the newer nvtx3 library which conflicts with the current old nvtx used in TE. This PR is to use the newer nvtx3 as the header to address the compatible issue.
https://github.com/NVIDIA/NVTX?tab=readme-ov-file#c-and-c
Fixes # (issue)
Type of change

[ ] Documentation change (change only to the documentation, either a fix or a new content)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Infra/Build change
[ ] Code refractor

Changes
Please list the changes introduced in this PR:

Change to use nvtx3 header

Checklist:

[x] I have read and followed the contributing guidelines
[x] The functionality is complete
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/te-ci

The failure of te-ci/L0_paddle_unittest--L40_1GPU seems not related to this PR.


Save classifications to csv

This was another idea I had. Not sure if it's the most canonical way of taking the data once evaluation is finished, but it worked for me. I just saved it to a csv and was able to get a more qualitative sense of where the algorithm hit and missed.

Looks good, thanks!


SEPARATOR syntax (to create long scalar string value) for *** Variables *** table works inconsistently

Used RF Version: 3.0.2
Scalar variable ${CATENATE_VAR} from resource file, it has been created using catenation syntax with empty SEPARATOR argument, has different values:

proper string aaabbbcccddd for the first test suite
and aaa bbb ccc ddd for the second suite (for some reasons it contains spaces!).

Though that variable has just one initialization in common resource file.
Example:
first_suite.robot suite file content:
*** Settings ***
Resource          ${CURDIR}${/}common.robot

Default Tags      check_catenate
Suite Setup       Suite Setup
Suite Teardown    Suite Teardown

*** Variables ***

${SHOULD_BE}    aaabbbcccddd

*** Test cases ***
Check Catenate Functionality
    [Setup]    Should Be Equal    ${CATENATE_VAR}    ${SHOULD_BE}
    Should Be Equal    ${CATENATE_VAR}    ${SHOULD_BE}
    [Teardown]    Should Be Equal    ${CATENATE_VAR}    ${SHOULD_BE}

*** Keywords ***
Suite Setup
    Log  ${CATENATE_VAR}
    Should Be Equal    ${CATENATE_VAR}    ${SHOULD_BE}

Suite Teardown
    Should Be Equal    ${CATENATE_VAR}    ${SHOULD_BE}

second_suite.robot suite file content:
*** Settings ***
Resource          ${CURDIR}${/}common.robot

Default Tags      check_catenate
Suite Setup       Suite Setup
Suite Teardown    Suite Teardown

*** Variables ***

${SHOULD_BE}    aaabbbcccddd

*** Test cases ***
Check Catenate Functionality
    [Setup]    Should Be Equal    ${CATENATE_VAR}    ${SHOULD_BE}
    Should Be Equal    ${CATENATE_VAR}    ${SHOULD_BE}
    [Teardown]    Should Be Equal    ${CATENATE_VAR}    ${SHOULD_BE}

*** Keywords ***
Suite Setup
    Log  ${CATENATE_VAR}
    Should Be Equal    ${CATENATE_VAR}    ${SHOULD_BE}

Suite Teardown
    Should Be Equal    ${CATENATE_VAR}    ${SHOULD_BE}

common.robot resource file content
*** Settings ***

*** Variables ***
${CATENATE_VAR}    SEPARATOR=
            ...    aaa
            ...    bbb
            ...    ccc
            ...    ddd

*** Keywords ***

Results:
Both suites work perfect in case separated run.
But in case run together (at one time) it fails:
Parent suite setup failed: aaa bbb ccc ddd != aaabbbcccddd
PS: I didn't check it for the latest RF version.

I have no idea what's going on here, but I can reproduce the problem with RF 3.1.1 as well. Don't have time to debug this more now (or in the immediate future) but I'll add this to RF 3.1.2 scope so that it won't be forgotten.

I'm not working with RF 3.1.2 with a plan to have at least a release candidate out in April. I was able to find the root cause for this problem and after that the fix was pretty trivial.
In practice this issue meant that it wasn't possible to create scalar variables in resource files using the SEPARATOR= syntax. I consider that pretty severe and raised the priority.


Swapspace option not properly configured out of box?

Describe the bug

When I set services.swapspace.enable to true in my configuration.nix, the Swapspace daemon starts, but nothing happens. When I run swapspace --inspect, it returns:
Error: Could not get filesystem information for swap directory '/nix/store/sagyf11l27503hidpz6vy0iwgqwgis0n-swapspace-1.18.1/var/lib/swapspace': No such file or directory
The filesystem holding swapspace's swap directory isn't big enough to hold useful swapfiles.
Please try to expand this partition or relocate it to a larger one, if possible; or if all else fails, choose a different swap directory in your swapspace configuration.

Basically, no matter what path you set in the config, Swapspace will always try to create its swap file at /<nix store path>/<configured path>.
Steps to reproduce
Steps to reproduce the behavior:

Add services.swapspace.enable = true; to your configuration.nix.
Rebuild.
Run swapspace --inspect and see error.

Expected behavior
The default path that Swapspace creates its swap file at should be /usr/local/var/lib/swapspace, and setting swappath in the Swapspace module settings should apply properly.
Additional context
I asked for help with this on Discourse and was told to make a bug report.
Metadata

system: "x86_64-linux"
host os: Linux 6.11.0, NixOS, 25.05 (Warbler), 25.05.20241219.d70bd19
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.24.11
channels(root): "home-manager-24.11.tar.gz, nixos-24.11"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Notify maintainers

@Luflosi
@phanirithvij
Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

swapspace needs to know the configuration file. so for now you can use the generated config.
$ systemctl status swapspace.service
● swapspace.service - Swapspace, a dynamic swap space manager
     Loaded: loaded (/etc/systemd/system/swapspace.service; enabled; preset: ignored)
    Drop-In: /nix/store/m4xyzg4796qdilh66wncv82vk626gj7m-system-units/swapspace.service.d
             └─overrides.conf
     Active: active (running) since Thu 2024-12-26 15:11:24 IST; 20h ago
 Invocation: 573e8503e7b14e0ea0d11e7c405e05af
       Docs: man:swapspace(8)
   Main PID: 1155697 (swapspace)
         IP: 0B in, 0B out
         IO: 160K read, 40K written
      Tasks: 1 (limit: 18852)
     Memory: 160K (peak: 1.5M swap: 40K swap peak: 40K)
        CPU: 17.234s
     CGroup: /system.slice/swapspace.service
             └─1155697 /nix/store/sagyf11l27503hidpz6vy0iwgqwgis0n-swapspace-1.18.1/bin/swapspace -c /nix/store/74ijqs40fz19f89341lm4dwjqvk3hapy-swapspace.conf -P -v

from above, swapspace -c /nix/store/74ijqs40fz19f89341lm4dwjqvk3hapy-swapspace.conf
I will add a wrapper in the meanwhile, as services.swapspace.installWrapper = true; # default.


Synpatics touchpad missing with kernel 5.19

Describe the bug
Putting this out here in case anybody else is seeing this.
On am Acer Swift SF314-43, the touchpad goes missing with kernel 5.19. Works again with kernel 5.18 and no other changes.
Steps To Reproduce
Steps to reproduce the behavior:

upgrade to kernel 5.19
observe that it's broken

Additional context
With kernel 5.18:
$ journalctl -k -b-1 | grep SYNA
Aug 08 11:18:45 midge kernel: input: SYNA7DAB:00 06CB:CD40 Mouse as /devices/platform/AMDI0010:03/i2c-5/i2c-SYNA7DAB:00/0018:06CB:CD40.0001/input/input7
Aug 08 11:18:45 midge kernel: input: SYNA7DAB:00 06CB:CD40 Touchpad as /devices/platform/AMDI0010:03/i2c-5/i2c-SYNA7DAB:00/0018:06CB:CD40.0001/input/input8
Aug 08 11:18:45 midge kernel: hid-generic 0018:06CB:CD40.0001: input,hidraw0: I2C HID v1.00 Mouse [SYNA7DAB:00 06CB:CD40] on i2c-SYNA7DAB:00
Aug 08 11:18:45 midge kernel: input: SYNA7DAB:00 06CB:CD40 Mouse as /devices/platform/AMDI0010:03/i2c-5/i2c-SYNA7DAB:00/0018:06CB:CD40.0001/input/input11
Aug 08 11:18:45 midge kernel: input: SYNA7DAB:00 06CB:CD40 Touchpad as /devices/platform/AMDI0010:03/i2c-5/i2c-SYNA7DAB:00/0018:06CB:CD40.0001/input/input12
Aug 08 11:18:45 midge kernel: hid-multitouch 0018:06CB:CD40.0001: input,hidraw0: I2C HID v1.00 Mouse [SYNA7DAB:00 06CB:CD40] on i2c-SYNA7DAB:00

With kernel 5.19:
$ journalctl -b -k | grep SYNA

Metadata
nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.19.0, NixOS, 22.11 (Raccoon), 22.11.20220807.e7cc56e`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.10.3`
 - nixpkgs: `/nix/store/3xxgfpsdmjnavbflp7hgl8myiifkb5fm-yachiv88197s4v5ssvqcr8njafgina19-source`

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/touchpad-not-recognizable/19198/10

This happended to me as well, on a Tuxedo Aura Gen 1 with an ElanTech clickpad and NixOS 22.05.
Comparing the output of lsmod between kernel 5.18 and 5.19 I found three modules, which haven't been loaded on 5.19: hid_generic, hid_multitouch and pinctrl_amd. I added them to boot.kernelModules, ran nixos-rebuild switch and after  rebooting the touchpad is working again.

Ah, on 5.19:
$ zgrep PINCTRL_AMD /proc/config.gz
# CONFIG_PINCTRL_AMD is not set

Kernel rebuilding time. Haven't done that in a while...

So that did it. I didn't need to specify the list of modules, only add the
kernel option.

That fixed it on my Tuxedo as well.


[Bug]: The style of callout is not working properly

Bug Description
All types of callout, e.g. note, caution, tip, etc, revert back to a plain style with only border colorized.
Relevant Screenshot

To Reproduce
Just regular ways to add a callout, like

[!note]
blabla

Sample Text
No response
Obsidian Version
v1.4.12
Installer Version
v1.3.7
In which mode(s) does the problem occur? (if applicable)

[X] Source (Edit)
[X] Reading (Preview)
[ ] Live Preview

Which operating system?

[ ] macOS
[X] Linux
[ ] Windows
[ ] iOS
[ ] Android

Checklist

[X] I updated to the latest version of the theme (Settings → Appearance → Check for updates).
[X] If your installer version is much lower your app version, you should update it by re-downloading Obsidian from the Obsidian website. The installer version can be seen in the Obsidian settings (About → App → Installer Version).
[X] I made sure that the issue is related to this theme by checking that the problem does not occur with the default theme.
[X] In case I am missing an UI element, I have checked that it cannot be re-enabled with the Style Settings plugin.
[X] My issue concerns Obsidian version 1.0+ and I am not using the Legacy Editor (CM5). (Older Obsidian versions and the Legacy Editor are not supported by this theme anymore.)
[X] This issue concerns the theme in general and is not related to a specific plugin, for which there is the plugin-support form.

thx, fixed


Gateway data source credentials cannot be added

Hi,
I am facing an issue where I cannot add gateway data source credentials. Getting error:

Details:

Using MEZ connector, data in PowerBI Desktop syncs successfully.
Added MEZ connector to on-prem PowerBI Gateway.
I can add PowerBI Gateway from the service, but cannot add the credentials, I am specifyig the same Clockify API key, which works for PowerBI Desktop.

Any suggestions?

Actually, I was able to solve the issue with the help of these to article and a bit of community:
https://docs.microsoft.com/en-us/power-query/handlinggatewaysupport
https://docs.microsoft.com/en-us/power-query/samples/trippin/9-testconnection/readme
I added TestConnection line to the connector:

Hey @Peteris-E , thanks a lot for the solution! I've modified the code in the project and the MEZ file.


[TASK] rewrite dataExtension to use generic retrieve

related to #95

already done months ago? just needed to upgrade the central method to handle this new connection reset problem


Site Recovery  didn't created availability set in the target region with the suffix "asr" for the VM's which are replicated

As per the article below
https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-architecture
Site Recovery creates a availability set(AS) in the target regions with the suffix "asr" for the VM's which are located in AS in the source location, but when i did testing i did noticed AS was not created after fail over in the target region. In my case i am doing the testing from West Europe to South India ASR replication.

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

ID: 77b55957-eb46-c35a-5f31-66ca20ad4390
Version Independent ID: 10500bf3-d343-0bc9-cc16-642c5116a131
Content: Azure to Azure replication architecture in Azure Site Recovery
Content Source: articles/site-recovery/azure-to-azure-architecture.md
Service: site-recovery
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks for the feedback! We are currently investigating and will update you shortly.

I managed to fix the issue by adding some lines to the script.. Below is the overall script.
None of the MS document had mentioned on how to migrate the VM's between geographic cluster(may be i missed out). In this case i am migrating from West Europe to South India Azure regions.
Note: The below script is intended to use when you have below points
1)You already have ASR fabric  created.
2) Single Subscription Model
connect-AzAccount
$RSV = "Resource Group Name of where vault is created"
$RecoveryVaultName = "Vaultname"
$TargetRegion = "South India"
$CacheStorageAccoutnName = "testsg"
$CacheStorageAccoutnResourceGroupName= "TEST-ASR"
$SourceRGList = @("TEST-ASR", "TEST-ASR")
$SourceVMList =  @("ASR05", "ASR06")
$FailoverRGList = @("SouthIndia-App", "SouthIndia-App")
#Add the name of the Availbility Set"
$TargetAS = "SouthIndia-AS"
for ($i=0; $i -lt $SourceVMList.length; $i++) {
$SourceVmResourceGroup = $SourceRGList[$i]
$SourceVMName = $SourceVMList[$i]
$FailoverResourceGroupName = $FailoverRGList[$i]
Write-Output "Replication Process for the VM " +$SourceVMName
$vm = Get-AzVM -ResourceGroupName $SourceVmResourceGroup -Name $SourceVmName
$WestEuorpeCacheStorageAccount = Get-AzStorageAccount -ResourceGroupName $CacheStorageAccoutnResourceGroupName -Name $CacheStorageAccoutnName
$RecoveryRG = Get-AzResourceGroup -Name $FailoverResourceGroupName -Location $TargetRegion
$RecAvailabilitySetID = Get-AzAvailabilitySet -ResourceGroupName "RG Name" -Name "Availbility Set Name"
$vault = Get-AzRecoveryServicesVault -Name $RecoveryVaultName -ResourceGroupName $RSV
Set-AzRecoveryServicesAsrVaultContext -Vault $vault
$PrimaryFabric = Get-AsrFabric -Name "Primary Fabric Name"
$RecoveryFabric = Get-AsrFabric -Name "Secondary Fabric Name"
$PrimaryProtContainer = Get-ASRProtectionContainer -Fabric $PrimaryFabric -Name "PrimaryProtectionContainer"
$RecoveryProtContainer = Get-ASRProtectionContainer -Fabric $RecoveryFabric -Name "SecondaryProtectionContainer"
$ReplicationPolicy = Get-ASRPolicy -Name "ASRPolicyName"
$EuToUaePCMapping = Get-ASRProtectionContainerMapping -ProtectionContainer $PrimaryProtContainer -Name "A2APrimaryToRecovery"
#OsDisk
$OSdiskId = $vm.StorageProfile.OsDisk.ManagedDisk.Id
$OSDiskReplicationConfig = New-AzRecoveryServicesAsrAzureToAzureDiskReplicationConfig -ManagedDisk -LogStorageAccountId $WestEuorpeCacheStorageAccount.Id     -DiskId $OSdiskId -RecoveryResourceGroupId  $RecoveryRG.ResourceId -RecoveryReplicaDiskAccountType Premium_LRS
-RecoveryTargetDiskAccountType Premium_LRS
#Create a list of disk replication configuration objects for the disks of the virtual machine that are to be replicated.
$diskconfigs = @()
$diskconfigs += $OSDiskReplicationConfig
Data disk
foreach ($md in $vm.StorageProfile.DataDisks) {
$DataDiskReplicationConfig = New-AzRecoveryServicesAsrAzureToAzureDiskReplicationConfig -ManagedDisk -LogStorageAccountId $WestEuorpeCacheStorageAccount.Id     -DiskId $md.ManagedDisk.id -RecoveryResourceGroupId $RecoveryRG.ResourceId -RecoveryReplicaDiskAccountType Premium_LRS
-RecoveryTargetDiskAccountType Premium_LRS
$diskconfigs += $DataDiskReplicationConfig
}
$TempASRJob = New-ASRReplicationProtectedItem -AzureToAzure -AzureVmId $VM.Id -Name (New-Guid).Guid -ProtectionContainerMapping $EuToUaePCMapping -AzureToAzureDiskReplicationConfiguration $diskconfigs -RecoveryResourceGroupId $RecoveryRG.ResourceId -RecoveryAvailabilitySetId $RecAvailabilitySetID.Id
Write-Output "Please check the replciation status on Azure portal"
}

@pabbinedi thanks for this! I will assign this to the content author to review and see about updating the doc.

@pabbinedi Thanks for your feedback. I don't see a script in the article for which this issue was opened - https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-architecture. Can you tell me where you see the original script? thx!

@pabbinedi. Hi, I'm going to close this issue unless you have some more feedback concerning the article in question. Please comment and we'll reopen in that case. thx
#please-close


create postgres indexes

eventually we should have some SQL indexes in order to speedup selects and a GIN index for the jsonb field.  We don't have any at the moment.

Closing we will notice when we run into problems here and then reopen / create new issue.


Sample code for sandbox manipulation?

Describe what did you try to do with TM1py
I'm working with the new sandbox functionality with the aim of identifying sandbox content created by non-admin (using Impersonate) then manipulating it eg by updating the base data (potentially to a different element). I am struggling with the objects returned by the sandbox methods and properties. It would be good to see some samples.
eg:
sbs = tm1a.sandboxes.get_all
print (sbs)
returns
<bound method SandboxService.get_all of <TM1py.Services.SandboxService.SandboxService object at 0x215E6418>>
with no obvious way to move to picking up sandboxes and identifying content.
Version

TM1py 1.6
TM1 Server Version: <IP_ADDRESS>-0

For the SandboxService you can find samples in the test suite  here
For the write, execute_mdx..., execute_view... functions you can just pass the additional sandbox_name argument
I hope this helps.

It does, many thanks. I will check out the test suite more closely in future.


404 error page on ASP.NET Core

I'm new to development, currently I'm following the guide on the link mention below.
https://docs.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/adding-view?view=aspnetcore-2.1#comments-container
However there are many pages that has 404 error page when clicked on them.
Although I can download the PDF file to continue the tutorial, but I am stuck as I'm not able to understand I read the comments section to solve my bugs!
Please fix the pages that redirect to 404 error pages.

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

ID: 0193ed76-3eec-18ac-512f-45f8118dde34
Version Independent ID: 8e693833-3e45-2bb8-ddc2-d0c54936c3c1
Content: A New Feedback System Is Coming to docs.microsoft.com
Content Source: teamblog/a-new-feedback-system-is-coming-to-docs.md
Service: unspecified
GitHub Login: @EisenbergEffect
Microsoft Alias: EisenbergEffect

I had the same problem. need to help!

@GoodJeans @cosmictinydust this should be resolved, thank you for the feedback!


this.canvas.ownerDocument is undefined

I encoutered this error when using html2canvas :
this.canvas.ownerDocument is undefined
Solved by changing this line :
--> var canvas = this.canvas.ownerDocument.createElement('canvas');
to
--> var canvas = this.canvas.ownerDocument?this.canvas.ownerDocument.createElement('canvas'):document.createElement('canvas');
in the source code at line 6587 of html2canvas.js latest version

I created fork and applied fix for this issue.
Here is fix: https://github.com/Yogoort/html2canvas/commit/061c6ecdb627c0b3dcc4cf895b9552a5706117dd
command for installing forked html2canvas package
npm install https://github.com/Yogoort/html2canvas/tarball/master


Inititate branch to get travis to build pytables using pip

Description

Motivation and Context

Have you tested this? If so, how?

Current coverage is 30.96% (diff: 100%)

No coverage report found for hdf5-target at 3da360e.

Powered by Codecov. Last update 3da360e...0d798e4


Fix authentication issues

Closes #158.
While investigating #158, I've encountered the following four authentication issues:

Git in some cases will ask IDEA to provide the authentication information (see more about that in my last comment in #158). The IDEA Git infrastructure will pass the request to TfGitHttpAuthDataProvider: in IDEA 2018.1 and earlier, it will receive an URL like getAuthData("https://username@dev.azure.com").
This breaks the HTTP API request that will be sent to the server based on the URL (in this case, the API request will be sent to<EMAIL_ADDRESS>or something like that, which is invalid), because our infrastructure expects the URL to include a username in an usual place (e.g. https://dev.azure.com/username), thus TfGitHttpAuthDataProvider has to fix the URL before passing it into the authentication infrastructure (because verifying the URL passed is one of the authentication steps, and that requires HTTP API access).

IDEA 2018.2+ has broken the GitHttpAuthDataProvider API: a new method overload was introduced that has three arguments (namely, getAuthData(Project project, String url, String login)), and old method (that was implemented by us) will now receive the URL without a username. This doesn't work because we need to know the username to solve the previous issue.
Another problem is that the Azure DevOps plugin is currently compatible with IDEA 2017.1, so it cannot implement an interface method that was added only in 2018.2, and we don't want to drop the support for IDEA 2018.1 and older right now. So I had to use a little trick to implement that interface method (Java will consider an override even without an @Override keyword if interface has the same method with the same signature as our class).
I've thoroughfully documented this hack in the comments to make sure people won't drop this seemingly "unused" method from our TfGitHttpAuthDataProvider.

Next issue I've encountered was in ServerContextManager.Validator::validateGitUrl which is used e.g. when receiving a list of work items. This method may receive a Git remote URL (such as<EMAIL_ADDRESS>and should perform an API request to get the repository info. To perform a request, we use Apache HTTP library and pass a Client instance to it. Client has HTTP credentials baked into it, but there's a trouble: credentials that are present at the URL itself (e.g. https://username:password@server) has priority over the Client's backed credential manager, so it just uses username and password=null for a request (and that will result in an authentication error even if the credential manager has the right credentials).

The last issue discovered was caused by this code in ServerContextManager:
https://github.com/microsoft/azure-devops-intellij/blob/35673c4667b6a2db5f6b73f93a52e643ecc14794/plugin/src/com/microsoft/alm/plugin/context/ServerContextManager.java#L737-L739
The serverUrl returned by Azure API always already contained the account information in every case I've tested (e.g. it could return https://dev.azure.com/username), so there is no need to add the organization/account name to it, because it will result in erroneous https://dev.azure.com/username/username, which will result in 404 error being thrown.
I've decided to delete this piece of code. The logging that has been added will help us to investigate the cases when it could've been necessary, if any.

Each of the issues gets solved by a corresponding commit in this PR, and I've done my best to make the commit messages descriptive and concise.

@kaylangan hello, I believe this is ready for merge :)
Thanks!

@kaylangan Could I merge this PR?

@mfilippov go ahead! 👍

When will this be available? It's a high critical patch, as the whole plugin is not working.

Thanks for fixing!  I echo @Tom4U urgency. :)

Would really like to see this make it into a new release soon.  I'm in the process of migrating our Java team over to using Azure DevOps and without a working IntelliJ plugin it's going to be a really hard sell.

The issue is not fixed in 1.151.2
still getting

getAuthenticationInfoAsync failed
com.microsoft.alm.plugin.exceptions.TeamServicesException: KEY_VSO_AUTH_FAILED
at com.microsoft.alm.plugin.authentication.facades.VsoAuthInfoProvider.getAuthenticationInfoAsync(VsoAuthInfoProvider.java:100)
at com.microsoft.alm.plugin.authentication.VsoAuthenticationProvider.authenticateAsync(VsoAuthenticationProvider.java:69)
at com.microsoft.alm.plugin.authentication.AuthHelper.getAuthenticationInfoSynchronously(AuthHelper.java:59)
at com.microsoft.alm.plugin.idea.git.extensions.TfGitHttpAuthDataProvider.getAuthData(TfGitHttpAuthDataProvider.java:39)
at git4idea.remote.GitHttpAuthDataProvider.getAuthData(GitHttpAuthDataProvider.java:41)

I ran a local compile of the master branch and it is functioning correctly once loaded from disk into IntelliJ.

@jason-edstrom we have finally released the 1.152.0 yesterday, and it includes these changes, so you could install the update from the usual channel. Sorry for the pause, we'll try to follow more strict schedule from now on :)

I can confirm - it's working now.

Awesome!  Thanks a lot guys.  This has really helped me.

@ForNeVeR No worries! Thanks for the hard work and reply!  I was just wanted to confirm the fix and proposing a workaround if people needed the plugin before the release. :)

To me, after I close and reopen PHPStorm it asks to login again (and a new token is generated). Am I the only one?

@fmonts no, you're definitely not the only one. If the issue reproduces, then please:

Please check if the password storage is enabled in IDE settings: Appearance & Behavior | System Settings | Passwords (it could sometimes be sporadically disabled on Windows in some cases).
If it is, then raise a new issue with additional data listed in this comment.

I'm afraid it's not fully working. Error still exists when trying to push to remote repository.

@Tom4U to fix your problem, we'll need much more details, could you please open a new issue?

@ForNeVeR sure I could. But I'm pretty sure it's related to this issue here. It's the same behaviour. My doubt is that the fix didn't made it into the function that is used to login and push. Because anything else is working now. Are you sure I have to invest the time for a totally new report/issue?!

@Tom4U yes, I think that you should raise a new issue.
I have tried to reproduce your problem just as I read your first comment and wasn't successful. It means I'm missing something, and thus I need more details from you to be able to reproduce and fix the problem.


IPTT results table popover: Super stretchy

Since the recent updates to the results table, the popover version on the IPTT reports have become super stretched out, to where they take over most of the page and veer off the right edge of the window. We don't want to touch the fragile results table layout, but could we make the popover a fixed width?

Also, see the pointy thing on the far right edge... I'd expect it to be flipped so that it's pointing at the dots you use to activate the popover:

@axoplasm Can you please remove the "Add results" button from the popover? We had intentionally hidden it before. (The IPTT isn't intended to compete with the Indicators List page as a place to add results, and it links to version of the form that isn't user-friendly.)

In a similar vein, this "Add targets" link takes you to a full-page version of the Indicator setup form, and out of the context of the IPTT report.

Ideally, it would launch the pop-up version of the form, with the Targets tab open. If that's difficult to do from the popover doodad, then let's chat about alternatives.

I like the blue table icon! More intuitive and easier to click on than the three dots.
What do you think about using the icon to either open or close the popover? My instinct was to click it once to open, again to close.

I worked out the stretchy issue as a side effect of 1a54242 (in #285) which I think is deployed now. You might need to dump your cache to see the change.
This popover is the exact same code as the results popup on the indicators table. So if we don't want "add results" here it won't be there either. I can hide it with css. Not sure how to resolve the issue of it taking you to another page.

We're changing the error messaging "Organize your data for this indicator" to "This indicator has no targets."
And then hiding the "Add targets" button in the popover.

Wording updated. "Add results" hidden in the IPTT popover.


Implementation of filtering of favorites for timetable items

Kind (Required)

Improvement

Overview (Required)

It is not in the design, but you can refer to the feed for almost the same functionality.

blocked by #624

Links

If there's no one else, I wanna do this. 🤚

Thanks! Assigned!👍

@t-yusaku
This issue has a milestone date of 10/4. If you have any problems, please let me know! 🙏

@takahirom
Sorry I'm late 💦
I'm working on this assignment now. Please give me a few more hours 🙇


Force WidgetExt to show up as re-export in crate root docs.

WidgetExt shows up as a regular trait in the crate root docs right now, leading to broken links. This PR forces it to work the same way as Widget and WidgetId.

huh, I didn't know about these attributes. In my ideal world, we would inline all the druid types that are currently reexported; is there any reason this doesn't make sense?

We can inline them in the root, but then we should hide them in the widget module. Otherwise the docs will be available at two different URLs which will break the relative links. The rust doc linking system is extremely fragile right now, as you know.

That sounds okay to me; I dislike that these types aren't included in the main list of traits. Do you see any downside? If not, would you like to give that a try instead of this solution? If not I'm happy to merge this for now and then open an issue for that other change.

Sure, I'll give it a go, probably tomorrow.

but what if we do,
#[doc(inline)]
pub use widget::{Widget, WidgetExt, WidgetId};

is the problem that the docs can be linked from two places? because I don't think thats totally the end of the world, they'll be the same docs.

Then there are two files trait.Widget.html and widget/trait.Widget.html. The problem is exactly that they have the same docs - they even have the same relative links! Which means that currently all links in trait.Widget.html would be broken. If we fix those then all links in widget/trait.Widget.html are broken.

hm, but can we just ensure that we never link to one of them?

I guess not. :/

How badly do we need Widget and WidgetId to be part of the public API in the widget module? One solution could be to move those two into a non-public sub-module (like WidgetExt) and then re-export it from the root crate with inline docs.

sounds good.

Okay, things are looking better now.

Widget, WidgetExt, WidgetId, Lens, LensExt, LensWrap docs live exclusively in the root now.
kurbo and piet re-exports are now also inlined with their docs.
Lens derive macro docs live only in the root.
widget::prelude module docs no longer link to doc pages with broken links.
Region docs are now properly available in the root.
Fixed a few random broken links I ran into.

Yeah this is 99% docs orientated changes, as far as code is concerned all imports will continue to work as they did previously.
The only exception could be the druid_derive::Lens macro for which the export was moved from the widget module to the root to remove duplicated docs. However tests all seems to still be working, including one which uses this macro. In any case that's a one line change if it ends up needing to be reverted.


when page1 with TickerProviderStateMixin jump to page2 ,then page1 cause rebuild

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

Hello @chenchunhao9125 ,
Could you please post the outputs of flutter run -v and flutter doctor -v and a complete minimal reproducible code sample?
Thank you!

@chenchunhao9125
There's no description / details in the issue you created. When opening an issue, please provide a minimal reproducible code sample that we can use to replicate the issue you are facing along with a description of what you are trying to do along with expected behavior. Also provide flutter doctor -v.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Using ollama models on a vercel deployment

I want to allow the use of locally running ollama models onto my vercel deployment, I tried forwarding the port into a public URL using ngrok but no local models are even shown I cannot seem to fix it any suggestions?

you need to stop ollama and then start uit via OLLAMA_HOST=<IP_ADDRESS> OLLAMA_ORIGINS=* ollama serve so that ollama can be reached from another computer

This works for the local build and not for the vercel deployment unfortunately my issue is still not resolved

@Bortus-AI @mckaywrigley
using
curl http://<IP_ADDRESS>:11434/api/generate  -d '{
  "model": "llama2",
  "prompt":"Why is the sky blue?"
}'

on a different computer generates a resposnce so ollama works but no models how up on vercel

In my experience vercel like the IP address for ollama to be a domain.

@Bortus-AI I tried setting that up by forwarding the port through ngrok but that doesn't work do you have any suggestions?

Any sugestions? I Have the same problem...