Update dependencies.

Most of these are only minor version bumps, but there were a handful of major version changes.
Most notably: the maintainer for shadow has changed, along with the package naming.
Hamcrest 3.0 looks like the main backwards incompatible change is that it's ratcheted up the minimum Java version to require at least Java 8. Since we're building with Java 17, this is a non-issue.
There were a handful of major version changes in dependencies that I'm not sure we're ready for (flatlaf and swingx were the two that I recall), and a couple of dependencies where the latest version is marked as beta or alpha (spotless, slf4j-nop).

For context, the non-latest-milestone results from ./gradlew dependencyUpdates:

The following dependencies have later milestone versions:

com.diffplug.spotless:com.diffplug.spotless.gradle.plugin [6.23.3 -> 7.0.0.BETA2]
com.formdev:flatlaf [1.6.5 -> 3.5.1]
https://github.com/JFormDesigner/FlatLaf
com.formdev:flatlaf-intellij-themes [1.6.5 -> 3.5.1]
https://github.com/JFormDesigner/FlatLaf
com.formdev:flatlaf-swingx [1.6.5 -> 3.5.1]
https://github.com/JFormDesigner/FlatLaf
org.slf4j:slf4j-nop [2.0.16 -> 2.1.0-alpha1]
http://www.slf4j.org
org.swinglabs:swingx [1.0 -> 1.6.1]
http://www.swinglabs.org/

Gradle release-candidate updates:

Gradle: [8.8 -> 8.10]

I'm confused by the test failure. Surely bumping these dependencies shouldn't affect ASH on Windows specifically, right?
(test_finally_return.ash somehow transformed input from 200 -> 0. I'm rerunning the failed tasks to see if this was a flake, although even if it is, we should try to understand how reproducible it is and if it's an indicator of a larger bug.)

Rerunning seems to have addressed the failure.
Deep link, for posterity: https://github.com/kolmafia/kolmafia/actions/runs/10694075396/job/29645403583

That test fails sometimes, I think it's a race.
The last line is
print("I received " + test(200));

This leads into a branch that calls abort: normally this aborts the ASH file and nothing gets printed, but sometimes it acts as though the function returned 0 (the default value for int) and prints "I received 0".


Soul Vials

Dont have a recipe

This issue / recipes will be fixed within the next release of the modpack.


Do not start the UI in case initialisation fails

I have added the naive approach of just closing the app.
Hopefully exit(1) will result in submitting a TestFlight reports (exit with
error).

note: eventhough it seems like a trivial change, I'm a bit worried that this could cause unintended consequences (what if user needs to explicitly enable local network permissions? like @holzeis showed on his screen once - I tried catering for that, but I'm not sure whether they would pop up over the splashscreen).
Ideally I would have guarded it with a feature flag (managed as per feature flag / A/B testing discussion), especially given our TestFlight release cycle.

the alternative approach could involve storing a flag in preferences initialised = false at startup, and setting to true at the end of init, and then adjusting welcome screen based on that.
might be more elegant approach, I'll give it a quick try.

but I'm not sure whether they would pop up over the splashscreen

For me it did pop up over the splash screen.

the alternative approach could involve storing a flag in preferences initialised = false at startup, and setting to true at the end of init, and then adjusting welcome screen based on that.

I think we are fine with the splash screen only being removed once the app is initialised, if we ensure the app crashes in case the initialisation failed.

I guess this change will get the job done in terms of crashing the app if the initialisation fails, but will not result in a crash report thats helpful to us.

it's still a step in the right direction, yes? At least the user cannot due silly things anymore in the app.... we're tightening the constraints.
As a further enhancement, we could either:

send the logs automatically (e.g. via email)
OR
open the Settings screen and disable wallet and trading functionality (so that the user can show / send the logs to help us debug.

I kinda like the second approach listed above.
As such, I consider these out of scope of these PR.

I guess this change will get the job done in terms of crashing the app if the initialisation fails, but will not result in a crash report thats helpful to us.

it's still a step in the right direction, yes? At least the user cannot due silly things anymore in the app.... we're tightening the constraints.

@klochowicz Why not remove the try catch from above? instead of using the exit(1). That way we would also get the correct StackTrace in the Apple Crash Report.

I guess this change will get the job done in terms of crashing the app if the initialisation fails, but will not result in a crash report thats helpful to us.

it's still a step in the right direction, yes? At least the user cannot due silly things anymore in the app.... we're tightening the constraints.

@klochowicz Why not simply remove the try catch from above? instead of using the exit(1). That way we would also get the correct StackTrace in the Apple Crash Report.

I have tested this on native and iOS Simulatar. In both cases the Dart VM displays the backtrace but does not exit the app (crash).
The thing with Dart VM is that it is resilient in face of exceptions, so I'm not sure how we would get the correct StackTrace then? (At least with the exit(1) we catch and display the logs.
am I missing anything here @holzeis ?

I guess this change will get the job done in terms of crashing the app if the initialisation fails, but will not result in a crash report thats helpful to us.

it's still a step in the right direction, yes? At least the user cannot due silly things anymore in the app.... we're tightening the constraints.

@klochowicz Why not simply remove the try catch from above? instead of using the exit(1). That way we would also get the correct StackTrace in the Apple Crash Report.

I have tested this on native and iOS Simulatar. In both cases the Dart VM displays the backtrace but does not exit the app (crash) - we hang on the splashscreen forever.
The thing with Dart VM is that it is resilient in face of exceptions, so I'm not sure how we would get the correct StackTrace then? (At least with the exit(1) we catch and display the logs.
am I missing anything here @holzeis ?

Thanks for the explanation. I hoped a dart exception would have crashed the app.

I don't really understand the improvement in this PR.
Here is my understanding:
Prior to this PR the app would just crash when we run into an error during initialization.
Now the app exits instead of crashing...? How does this make a difference for the user?
Does the app still hang after this PR? (I assume not, it would just close) - Is the fact that the app does not hang anymore the improvement of this PR?

I don't really understand the improvement in this PR.
Here is my understanding:
Prior to this PR the app would just crash when we run into an error during initialization. Now the app exits instead of crashing...? How does this make a difference for the user? Does the app still hang after this PR? (I assume not, it would just close) - Is the fact that the app does not hang anymore the improvement of this PR?

the app would not crash previously.
Now it will crash and exit.
previously, just like in corporate Java-land, we had a giant catch-all exceptions and go-on init 🙈
now we're actually exiting with error code - hopefully trigerring a crash report in the Apple (to be tested in release).

hopefully trigerring a crash report in the Apple (to be tested in release).

We could actually test it. Simply build a TestFlight release using the GitHub action. I would advise to temporarily change the version in pubspec before though, so we do not block a build number on the current release version.

hopefully trigerring a crash report in the Apple (to be tested in release).

We could actually test it. Simply build a TestFlight release using the GitHub action. I would advise to temporarily change the version in pubspec before though, so we do not block a build number on the current release version.

I'll test it when the internal TestFlight release gets deployed.

bors r-

as we don't want to hold off a main TestFlight release, I've opted to merge it only after the new release, so that there's time to revert it easily if it doesn't work as expected without causing any friction.

@klochowicz I looked a little bit into error handling in flutter and found the following.
https://docs.flutter.dev/testing/errors#errors-caught-by-flutter
I think we should do the following.

Add a general handling for any unhandled exception and exit the app.
main.dart

FlutterError.onError = (details) {
    FlutterError.presentError(details);
    if (kReleaseMode) exit(1);
  };

Build our iOS app with the release flag. As otherwise errors will be swallowed by flutter.
ios.yml

      - name: Build iOS Archive
        id: build-ios
        run: |
          BUILD_NAME=${{ steps.version.outputs.data }}
          BUILD_NUMBER=$(git rev-list HEAD --count)
          cd mobile
          flutter build ipa --export-options-plist=ios/exportOptions.plist \
                            --dart-define="ELECTRS_ENDPOINT=$ELECTRS_ENDPOINT" \
                            --dart-define="COORDINATOR_P2P_ENDPOINT=$COORDINATOR_P2P_ENDPOINT" \
                            --dart-define="NETWORK=$NETWORK" \
                            --dart-define="COMMIT=$(git rev-parse HEAD)" \
                            --dart-define="BRANCH=$(git rev-parse --abbrev-ref HEAD)" \
                            --dart-define="COORDINATOR_PORT_HTTP=$COORDINATOR_PORT_HTTP" \
                            --build-name=$BUILD_NAME \
                            --build-number=$BUILD_NUMBER \
                            --release

Remove the big try catch on the main function.
Test by running the Build and release ios app to TestFlight workflow (ios.yml) manually. Throw a simple exception in the startup and check if the app crashes. (We don't have to wait for a release to do that.)
Note, we should just make sure that we adapt the pubspec version for that test. e.g. to 0.0.1 so that we do not block a build number.

Add a general handling for any unhandled exception and exit the app.

I don't think this is a good idea at this stage (eventually, yes). Sometimes exceptions happen just in the UI layer, e.g. the trading screen -  #402 - we absolutely don't want to exit the app on this exception.

FlutterError.onError = (details) {
FlutterError.presentError(details);
if (kReleaseMode) exit(1);
};

I have no idea why wouldn't we exit in debug mode - IMHO we should be even more strict in exiting in debug mode.
I don't mind going eventually in that direction (especially exiting in debug first and foremost, to notice any exception).
anyway, maybe we can spin this discussion off to a separate issue @holzeis? It goes outside of scope of this PR and is a step further.

I have no idea why wouldn't we exit in debug mode - IMHO we should be even more strict in exiting in debug mode.

I copied that from the flutter example. Not sure why they've added it only for release mode, but I think it's because in debug mode error are never unhandled?

I have no idea why wouldn't we exit in debug mode - IMHO we should be even more strict in exiting in debug mode.

I copied that from the flutter example. Not sure why they've added it only for release mode, but I think it's because in debug mode error are never unhandled?

they are unhandled in debug mode - I test locally on debug mode.

I've decided to go with an alternative to this PR that will ensure that we get a crash report #595 .
Basically, it avoids the cunundrum with Flutter exceptions by not emitting one at all  😊(we 'expect' it to initialise).


Example imports fail

Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Operating System:

(catalyst-venv) bash-3.2$ uname -a
Darwin Bens-MacBook-Pro.local 16.6.0 Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64 x86_64

Python Version:

(catalyst-venv) bash-3.2$ python --version
python --version
Python 3.6.1

Python Bitness:

(catalyst-venv) bash-3.2$ python -c 'import math, sys;print(int(math.log(sys.maxsize + 1, 2) + 1))'
64

How did you install Zipline: Installed from source using README.rst.

Python packages:

(catalyst-venv) bash-3.2$ pip freeze
alembic==0.9.3
bcolz==0.12.1
Bottleneck==1.2.1
certifi==2017.4.17
chardet==3.0.4
click==6.7
contextlib2==0.5.5
cycler==0.10.0
cyordereddict==1.0.0
Cython==0.25.2
decorator==4.0.11
empyrical==0.2.1
enigma-catalyst==0.1.dev5
idna==2.5
intervaltree==2.1.0
Logbook==1.0.0
lru-dict==1.1.6
Mako==1.0.6
MarkupSafe==1.0
matplotlib==2.0.2
multipledispatch==0.4.9
networkx==1.11
numexpr==2.6.2
numpy==1.13.1
pandas==0.19.2
pandas-datareader==0.4.0
patsy==0.4.1
pyparsing==2.2.0
python-dateutil==2.6.0
python-editor==1.0.3
pytz==2017.2
requests==2.18.1
requests-file==1.4.2
requests-ftp==0.3.1
scipy==0.19.1
six==1.10.0
sortedcontainers==1.5.7
SQLAlchemy==1.1.11
statsmodels==0.8.0
tables==3.4.2
toolz==0.8.2
urllib3==1.21.1

Now that you know a little about me, let me tell you about the issue I am
having:
Description of Issue
Example

What did you expect to happen?
Expected library to import with no errors.

What happened instead?

Got an error about an invalid literal. Looks like a typo
Here is how you can reproduce this issue on your machine:
Reproduction Steps
(catalyst-venv) Bens-MacBook-Pro:catalyst bkc$ git branch
* master
(catalyst-venv) Bens-MacBook-Pro:catalyst bkc$ git pull
Already up-to-date.
(catalyst-venv) Bens-MacBook-Pro:catalyst bkc$ python
Python 3.6.1 (default, Apr  4 2017, 09:40:21)
[GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.38)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy as np
>>> from catalyst.api import (cancel_order, symbol, record, order_target_value, get_open_orders)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst/__init__.py", line 20, in <module>
    from . import data
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst/data/__init__.py", line 1, in <module>
    from . import loader
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst/data/loader.py", line 36, in <module>
    from catalyst.curate.poloniex import PoloniexCurator
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst/curate/poloniex.py", line 9
    DT_START        = time.mktime(datetime(2010, 01, 01, 0, 0).timetuple())
                                                  ^
SyntaxError: invalid token

What steps have you taken to resolve this already?
Should be a simple fix. Just logging here
Anything else?
Nope
Sincerely,
Ben

Looks like this also affects catalyst ingest:
(catalyst-venv) bash-3.2$ catalyst ingest
catalyst ingest
Traceback (most recent call last):
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst-venv/bin/catalyst", line 7, in <module>
    from catalyst.__main__ import main
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst-venv/lib/python3.6/site-packages/catalyst/__init__.py", line 20, in <module>
    from . import data
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst-venv/lib/python3.6/site-packages/catalyst/data/__init__.py", line 1, in <module>
    from . import loader
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst-venv/lib/python3.6/site-packages/catalyst/data/loader.py", line 36, in <module>
    from catalyst.curate.poloniex import PoloniexCurator
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst-venv/lib/python3.6/site-packages/catalyst/curate/poloniex.py", line 9
    DT_START        = time.mktime(datetime(2010, 01, 01, 0, 0).timetuple())

The fix is straightforward, but then this module starts complaining about mixing tabs and spaces. When that is done I get:
(catalyst-venv) Bens-MacBook-Pro:catalyst bkc$ python
Python 3.6.1 (default, Apr  4 2017, 09:40:21)
[GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.38)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy as np
>>> from catalyst.api import cancel_order
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst/__init__.py", line 20, in <module>
    from . import data
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst/data/__init__.py", line 1, in <module>
    from . import loader
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst/data/loader.py", line 37, in <module>
    from catalyst.utils.calendars import get_calendar
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst/utils/calendars/__init__.py", line 16, in <module>
    from .trading_calendar import TradingCalendar
  File "/Users/bkc/Documents/code/projects/catalyst/catalyst/utils/calendars/trading_calendar.py", line 30, in <module>
    from catalyst.utils.calendars._calendar_helpers import (
ModuleNotFoundError: No module named 'catalyst.utils.calendars._calendar_helpers'

Are we sure that the catalyst source directory is added to PYTHONPATH when the virtualenv is fired up?
If not, I can add the .pth to catalyst-venv site packages.

The formatting and indentation problems were solved by this pull request: https://github.com/enigmampc/catalyst/pull/4
For others who encounter the latter bug, this seems to have been caused by running the python interpreter from the repository's working directory, as this causes it to import the source files directly, instead of the importing the files installed in the virtualenv or in the user's site-packages.  The above error is failing to find one of the compiled classes, _calendar_helpers, that does not get built in the source directory.  It's probably best to avoid importing catalyst from any file repo's working directory to avoid confusion.
Thanks @bkc39 for your help on this issue!


Move note leads to broken images

Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[x] Workspace.  VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings

Describe the bug
If a note is moved between vaults, any images in the note are not moved, and their link is not updated, so they do not work after the note has been moved, they show in the preview as a broken image link.
To Reproduce
Steps to reproduce the behavior:

Create a note
Paste an image into it (or add an image any way you like)
Move the note to a new vault
Show the preview
Note that the image does not appear

Expected behavior
You expect to see the image. Either by the image being moved between vaults (more complicated) or by the note being updated so that its asset url points to the original vault.
Context
Edit: A cross vault link doesn't work for an image like dendron://vault-name/assets/images/... but a relative link does work in my preview:
![](dendron://../../vault-name/assets/images/2022-01-18-17-38-07.png)

Maybe provide an option to copy, move or update links for all and/or each asset?

I believe publishing merges all images into the same folder. If that's correct, I think the preview should replicate the same behavior by looking for the image in all vaults.
For Dendron Team: we already have some code to do exactly this, check the Goto Note code or message me if you need help locating it.

This presumes that all vaults are there in one workspace. But you can have a workspace with only one vault. For example, because this is the advised way to publish a single vault. Or for other reasons. I think it should be possible to manage where the assests are flexibly.

Following up on what @SR-- said, I have multiple vaults and they're used in different contexts. Each one is a separate git repository. The dendron magic urls are cool, but they won't work in other contexts. I expect to use my vaults to run all kinds of other tools against, be that outside-of-dendron publishing, web based task management UI, etc. So personally, the cross vault stuff isn't a good solution for me. In fact, it would be a terrible solution as it would make it appear like images "work" when from my perspective they are actually "broken".
The copying / moving assets would be great. I guess it's a little complex to figure out if the asset is used in multiple locations, etc, but I guess dendron already does this kind of interconnected refactoring already, so hopefully it's not too big an issue.

Related to #525

Related to #525

I think #525 is an exact duplicate and we should close one if favour of the other.

Hi, @chmac, I'm going to close this one as a duplicate in favour of #525. If you think that any parts of the discussion here are relevant and should be preserved, please, repost them under the linked issue.


single eex expression converted to eext1

If I have a template with just a single eex expression in it, for example:
<%= link_to "blah", to: foo %>

It is incorrectly replaced with:
<eext1 />

adding HTML anywhere in the file fixes the issue

Hey @stevencorona  :wave:
Fix is already on master. You can give it a try.
I will release it later this week. Sorry for the trouble :sweat:

@stevencorona I've just released a new version with a fix, let me know if it solves the problem ;)


[cosmetics] Bintray upload/version number

Missing bintray upload of fix to #38, and version number change
Just cosmetics, was able to built it myself, works like a charm.

Version 5.7 released


second

Topic: second

Reviews in this chain:
└https://github.com/yuwei-will-xia/revup_test/pull/2 second


[Bug] Improve kyuubi-ctl output format

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the bug
hadoop@kyuubi:~$ bin/kyuubi-ctl list server
/kyuubinamespacekyuubi01.corp  10010   1.4.0-incubating
/kyuubinamespacekyuubi02.corp  10010   1.3.1-incubating

Affects Version(s)
master
Kyuubi Server Log Output
No response
Kyuubi Engine Log Output
No response
Kyuubi Server Configurations
No response
Kyuubi Engine Configurations
No response
Additional context
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

@pan3793
maybe should set parameter -b, --verbose to default true ?
./bin/kyuubi-ctl list server -zk <IP_ADDRESS>:9218 -b

             Zookeeper service nodes
+----------+-------------+----------+--------------+
|Namespace |    Host     |   Port   |   Version    |
+----------+-------------+----------+--------------+
| /kyuubi  |<IP_ADDRESS>|  10001   |1.5.0-SNAPSHOT|
+----------+-------------+----------+--------------+

maybe should set parameter -b, --verbose to default true ?

verbose also affects other things, but for render service nodes, I think we can always let it render in verbose mode, i mean, we can remove the arg verbose of Tabulator.format. cc @turboFei


[Bug]: MultiModalVectorStoreIndex  image_to_image_retireve on Google Cloud Platform

Bug Description
When passing an image file path to the function image_to_image_retrieve with the VertexMultiModalEmbedding initialized and ran like the following.
# configure embedding model
embed_model = VertexMultiModalEmbedding(
    model_name="multimodalembedding@001",
    project=PROJECT_ID,
    location=REGION,
)

index = MultiModalVectorStoreIndex.from_vector_store(vector_store=vector_store, embed_model=embed_model, image_embed_model=embed_model)

retriever_engine = index.as_retriever(
    similarity_top_k=3, image_similarity_top_k=3
)

retriever_engine.image_to_image_retrieve('test.png')

There is an issue with the parsing of the image file seen in the extract traceback below.
[/usr/local/lib/python3.10/dist-packages/llama_index/embeddings/vertex/base.py](https://localhost:8080/#) in _get_image_embedding(self, img_file_path)
    210         else:
    211             image = Image(image_bytes=img_file_path.getvalue())
--> 212         embeddings = self._model.get_embeddings(
    213             image=image, dimension=self.embed_dimension, **self.additional_kwargs
    214         )

[/usr/local/lib/python3.10/dist-packages/vertexai/vision_models/_vision_models.py](https://localhost:8080/#) in get_embeddings(self, image, video, contextual_text, dimension, video_segment_config)
   1199             parameters["dimension"] = dimension
   1200
-> 1201         response = self._endpoint.predict(
   1202             instances=[instance],
   1203             parameters=parameters,

Since I am getting the following error:
InvalidArgument: 400 Invalid input image string with the following error message: Provided image is not valid.

For image parsing google recomends base64 encoding.
Version
0.10.56
Steps to Reproduce

Create a Vertex AI Vector Store
Populate Vector Store
Initialize Vector Store and Multimodal Retrieval
Run image_to_image_retrieve

Relevant Logs/Tracbacks
No response

The proposed solution did result in an in an additional problem here is the error:
OSError: [Errno 36] File name too long: 'UklGRs4QA....'

Which makes sense since the function image_to_image_retrieve is expecting a file_path and parsing the base-64 string as such.

A couple of resolution notes this occurred when I was using a .png. A resolution was reached by reducing the size of the image, although it was not clear in error. I used the following code to reduce the image:
from PIL import Image

def resize_image(input_path, output_path, width, height):
    """
    Resizes an image to the specified dimensions and saves it.

    Args:
        input_path (str): Path to the input image.
        output_path (str): Path to save the resized image.
        width (int): Desired width of the resized image.
        height (int): Desired height of the resized image.
    """

    try:
        # Open the image
        img = Image.open(input_path)

        # Resize the image
        resized_img = img.resize((width, height))

        # Save the resized image
        resized_img.save(output_path)

        print(f"Image resized and saved as '{output_path}'")

    except FileNotFoundError:
        print(f"Error: Input image not found at '{input_path}'")
    except Exception as e:
        print(f"Error: An unexpected error occurred: {e}")

The reduction allowed for the image to embedded but the image_to_image_retrieve would still return an empty list. I resolved to use the following in lieu of this function. To use the
from llama_index.core.vector_stores.types import VectorStoreQuery

query = VectorStoreQuery(query_embedding=embed_model.get_image_embedding(img_file_path='image.png'),similarity_top_k=3)
query_result = vector_store.query(query)

This method allowed me to successfully retrieve images from images.


Add support for "spectra for each note" operation

Right now spectra operation is valid only as a one-shot operation or a simply-repeating operation regardless of note on/offs. It is often very convenient to fire spectra on every note on (such as spectrum modulation changes by note on).

Some ideas:

add "__ON_MIDI_NOTE_ON" operation and "apply" any "registered spectra" operators.
add "__BREAK" operation that breaks the rest of MML inside a macro (or track, if doable).
at "__ON_MIDI_NOTE_OFF" that triggers __BREAK above, within existing spectra MML definition.

Needs some consideration on how to "register" spectra. A simple and dumb idea is to use __LET to certain variables.

related but not mandatory: we need MPE support

After examining MPE specification, I'm not going to give high priority on that. It is only to provide pitch bend (and its sensitivity) per note. (CC74 is supported too, which has nothing to do with any standard MIDI device, and CAf can be just PAf in the traditional messaging.)


Cursor flash in scintilla editors

There is a problem with the cursor in editors that are using scintilla.
The cursor changes from iBeam to arrow all time while the mouse pointer is over the client area of the control.
This is with the last image and Windows 10 insider edition. Have anyone noticed the same?
I think that it should be easily solved defining in the right place something like:
onGetCursor: aSymbol
	"The named area of the view associated with the receiver has been hit. Answer the
	appropriate mouse cursor or nil to accept the default."

	^Cursor iBeam

But I don't know why this started to happen because previous versions doesn't requires anything special. Maybe the new scintilla requires this or a change made in somewhere causes this.

I have the same problem in Windows 10 professional.

It's actually caused by the "SeeingTheObjectsInside" splash window, which sets the global cursor to the arrow when it is dismissed. This then causes the Dolphin cursor handling to continually try and override any other cursor that has been set back to the arrow.
You can temporarily fix this problem by clearing the global cursor - not entirely easy to do since it is set/restored when evaluating an expression. However this will work:
[Cursor current: nil] postToInputQueue
I'll send a PR to fix it properly.


cookie cutter Jupyter widget on nbviewer

Hi,
Is it possible to view an interactive widget made with cookiecutter on nbviewer? My widget (built using cookiecutter) works when run locally on a notebook
repo: https://github.com/MaayanLab/clustergrammer-widget
notebook example: https://github.com/MaayanLab/clustergrammer-widget/blob/master/Running_clustergrammer_widget.ipynb
but I cannot see the widget in nbviewer
http://nbviewer.jupyter.org/github/MaayanLab/clustergrammer-widget/blob/master/Running_clustergrammer_widget.ipynb
I know that as of ipywidgets 6.0 they are supposed to work on nbviewer, but I do not know if the cookiecutter template is also supported. Thanks.

I think it it resolved, I needed to upgrade ipywidgets to 6.0, then I could see the
'Save Notebook with Widgets'
option on the Widgets dropdown in the notebook. I have a new error now with nbviewer but it is unrelated.


typeshare: 1.9.2 -> 1.11.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/1password/typeshare/releases.
meta.description for typeshare is: Command Line Tool for generating language files with typeshare
meta.homepage for typeshare is: https://github.com/1password/typeshare
meta.changelog for typeshare is: https://github.com/1password/typeshare/blob/v1.11.0/CHANGELOG.md
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.11.0 with grep in /nix/store/r796x5mxq9ywq0vwlzjqslcznkw1qqks-typeshare-1.11.0
found 1.11.0 in filename of file in /nix/store/r796x5mxq9ywq0vwlzjqslcznkw1qqks-typeshare-1.11.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

typeshare

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r796x5mxq9ywq0vwlzjqslcznkw1qqks-typeshare-1.11.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 typeshare https://github.com/r-ryantm/nixpkgs/archive/c025b7fc8175cf6a082de3bd134fbc8d242c93a4.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c025b7fc8175cf6a082de3bd134fbc8d242c93a4#typeshare

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r796x5mxq9ywq0vwlzjqslcznkw1qqks-typeshare-1.11.0
ls -la /nix/store/r796x5mxq9ywq0vwlzjqslcznkw1qqks-typeshare-1.11.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.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

typeshare

Maintainer pings
cc @figsoda 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.

Result of nixpkgs-review pr 339401 run on aarch64-darwin 1

1 package built:

typeshare


[New Feature]: Logo of the website should be on appear with the name of the website in the header

🎮 feature Request
I will set the logo of the website aside the name of the website in the header .

Point down the features
I will also make this responsive so that it will give best user experience in all the devices.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created seprate chennals for all projects...
Thank you :)

Please assign me this issue under GSSoc'24.

I have generated a pr request so please review it and tell if any changes are required or if it is ok then please approve it.


Automatically Build Solution before Start and Debug

Currently it is missing for some reason

In Rider 2020.2, you'll be able to implement a com.jetbrains.rider.build.tasks.SolutionRunConfiguration marker interface in your run configuration, and it will automatically get the corersponding before-launch task.

@ForNeVeR Can you explain how do you do that?

Just add com.jetbrains.rider.build.tasks.SolutionRunConfiguration to the list of interfaces implemented by GodotDebugRunConfiguration.
(Please note that this interface is only available in Rider 2020.2, and the plugin, as I can see, still targets Rider 2020.1, so this may be impossible to do at the moment without bumping the Rider version – which may be problematic, since there're no publicly available Rider builds from 2020.2 (yet).)

fixed in plugin .36, which targets 2020.2 EAP5+


Enable customization of text for both the "Incoming Video Call" and its associated actions.

Hello,
Could we have the text customisation for the notifications? This feature would enable us to tailor the text to better fit our specific context. Thanks.

@lowminchien  the Android system allows to change only the Content text dynamically for this type of notification. we will think about how to provide the setting of this text on the client side. the text on the buttons is default and it is configured in the string resources, you can try to override these string resources in your Android project:
<string name="call_notification_decline_action">Your Decline text</string>
<string name="call_notification_answer_video_action">Your Accept video text</string>
<string name="call_notification_answer_action">Your Accept audio text</string>

but I'm not sure it will work, I didn't check it

also, pay attention, you should place these strings for all localisations you used on your device. I mean the case if you add to the universal resources folder but the device used not the eng localization, the system will use integrated string without overriding. Can it be your case? please check, the overriding of resources should work

no activity for a long time. closing...


takes too much memory

repoz takes too much memory on mac

Whoa.
Can you add some details like (approx.) repo count and program execution time?

macOS 10.14.6, 30+ repos.
Normally it takes little memory. But if I didn’t shut down macOS and just let it sleep, the next day when I open the computer, it will take lots of memory. Seems to be related to mac’s sleep  wake up.
原始邮件
发件人:Andreas<EMAIL_ADDRESS><EMAIL_ADDRESS>抄送:Zhou<EMAIL_ADDRESS><EMAIL_ADDRESS>发送时间:2019年8月1日(周四) 15:43
主题:Re: [awaescher/RepoZ] takes too much memory (#82)
Whoa.
Can you add some details like (approx.) repo count and program execution time?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I sent my mac to sleep for 3 days now. Unfortunately, I can't see higher memory consumption in RepoZ. Are you able to reproduce this? If so, would you upload a spindump for me to analyse?

Sorry, I cannot reproduce that behavior.


deferRender appears to be broken

I've done as much due diligence as I can and I still hold that I may be missing something here, but deferRender appears to not be working as I would expect it.
I'm running 1.10.6-dev branch though I was on 1.10.5 with the same behavior.
I have a largish dataset of 7,430 objects.  The problem is it would appear all of cells are being rendered prior to the actual render of the page.  The page size is 10 and the column size is 11, so I would expect 110 renders.  Here is the output when I console.debug in the render function (I will show that later).
46908 datatable render called
7430 datatable render called
110 datatable render called

That output comes from this:
        this.table = $(this.refs.table.getDOMNode()).dataTable({
            pagingType: "full_numbers",
            pageLength: 10,
            deferRender: true,
            processing: true,
            data: this.props.rows || [],
            columnDefs: [
                {
                    targets: '_all',
                    render: function(data, type, row) {
                        console.debug("datatable render called");
                        return (data != null ? data['f'] : void 0) || (data != null ? data['v'] : void 0) || data || '';
                    }
                }
            ]
        });

The this.props.rows is an array of objects that conform to the google table format, that let's me be pretty flexible with the output and should have no effect here.
The console.debug definitely slows things down, so removing that and adding a counter variable on this speeds things up, but still: counter: 54448
It would appear the array size * columns are being rendered, then not sure what 7430 is, then the 110 makes sense, that is the 10 page * 11.
I have also tried an alternative way described here: http://www.nowherenearithaca.com/2015/03/avoiding-performance-gotcha-with-jquery.html but that didn't change anything, and led me to use 1.10.6-dev which had no difference in the # of render calls.
The big question I have, why is the render function ever invoked more than 110 times on the initialization of DataTable?

I think you are misunderstanding the connection between deferRender and columns.render - the names are a bit confusing but they basically are not connected!
deferRender will tell DataTables not to create tr and td nodes until they are needed for the display. However, columns.render is required in order to figure out what rows are going to be displayed (as the information from that function will be used for sorting and filtering information).
columns.render is called every time DataTables needs to access data for that cell - that included sorting, filtering, type detection, etc. Hence why it is called multiple times.
A real test of if deferRender is working or not is to use columns.createdCell or createdRow to see when DataTables creates the cells / rows.


Log panics in apply_document_changes

This doesn't necessarily help (because of https://github.com/rust-analyzer/rust-analyzer/issues/4263#issuecomment-623078531), but maybe we could leave it in there for a while in case it catches something.

bors r+
Let's see if I can fish out something today


Oauth2 Middleware fix for Bearer token header

Description
Fixes issue where the Bearer token is not being added to Authorization request header.
Issue reference
close: #2615
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
[N/A] Created/updated tests
[N/A] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

Thanks, I left a comment on the associated issue.


libColorSettings causing an exception (in CoC7e system)

Have narrowed down the following exception to occurring when libColorSettings is enabled:

what other modules are enabled? I'm not able to reproduce with just colorsettings enabled. (character.js is also not a file from colorsettings)

I was able to bring the issue up with the system author(s) and they believe it is their issue (they indicated a fix will be in their next release). I will update later.

On Sep 5, 2021, at 11:52 AM, ardittristan @.***> wrote:
what other modules are enabled? I'm not able to reproduce with just colorsettings enabled. (character.js is also not a file from colorsettings)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/ardittristan/VTTColorSettings/issues/20#issuecomment-913189115, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADGQAEBTLCHRSL3QQCE3YTUAON5BANCNFSM5DNPMXJQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


[2.0] Pass the message along with the error

I really need the ability to inspect the linting error.

Will this error be used anywhere ?

It would be nice to show the exception message me on a higher verbosity level (https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/1176). It might make issues reporting/debugging more easy as well.

If we want to use it in the future for reporting more detailed errors on output (with -vvv) and for ErrorReporter then I think it would be better to pass full exception object here.
ref https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/1247#discussion_r33820515


Securing kubernetes-ro use cases

We'd like all communications to the apiserver to be over https and with authorization.
Kubernetes-ro does not meet these standards.
This bug is about things that use the kubernetes-ro service or the KUBERNETES_RO_* env vars.
kube-proxy is discussed separately in #5917 since it explicitly uses port explicitly 7080 and has a straightforward fix.
Existing Uses
Use cases for kubernetes-ro

cluster/addons/dns/kube2sky/kube2sky.go
cluster/addons/fluentd-elasticsearch/logging-demo/README.md
examples/cassandra/java/io/k8s/cassandra/KubernetesSeedProvider.java
examples/phabricator/cloudsql-authenticator/run.sh
examples/rethinkdb/image/run.sh
examples/rethinkdb/image/run.sh
contrib/for-tests/network-tester/webserver.go
users have said they use kubernetes-ro.

Backwards Compatibile or Breakage?
In order to make this be https, we have to break some uses cases, because some existing use cases assume it is http.  So, we could either have a breakage day, or have it be configurable at cluster setup time, and just move GCE/GKE to the https option.  The latter seems expedient but it would force some code like kube2sky and elasticsearch to handle both options.  Better to just break it.
Decision: breakage.
Credential distribution
We need to distribute credentials to clients.  The use cases are in pods, so we need a way to distribute credentials to all pods that need them.  Credentials would probably be in the form of a kubernetes_auth file.
We could use secrets to distribute the kubernetes_auth files.  This does make some of the pod descriptions quite a bit mode verbose.  But we can address that later using service accounts or config templates/expansions.
credential creation

In the place where we create a "kubelet" token, also create a token for user "readonlyuser".
Put this token into a kubernetes_auth file.
Put the kubernetes_auth file along with the master's certificates into a secret object.
Post this secret to the master in cluster/saltbase/salt/kube-addons/kube-addons.sh.

credential use

Change all pods that currently reference kubernetes-ro/KUBERNETES_RO to have a secret volume source.
Change all the go code that references KUBERNETES_RO to instead take a --kubernetes_auth flag.
change the java code and shell code to extract master address and the auth token and the certs from the kubernetes_auth file and use https.
change all the shell code that uses KUBERNETES_RO and curl to extract the auth token from the kubernetes_auth

Cleanup

Stop advertising kubernetes-ro service (remove from pkg/master/publish.go)
fix docs to never speak of it again.

As an initial step, every cluster should be built with a secret with user readonly-user
Alternative
Run a proxy on each node which listens on each netns's localhost address, or one some other address visible to all netnses.  Listen for http.  Proxy via HTTPS to the master. See #2209
Advantages:

no credentials to distribute to pods, and to perhaps be compromised
no verbosity in pods for the secret volume source
no breakage for users
Disadvantages:
fixing urls in proxies
unforseen complexity with proxying.
uses a special mechanism for kubernetes auth, instead of the the more general option we expect users to use (Secrets).
more moving parts.  more magic, instead of well-understood, composable mechanisms.

@deads2k - I thought we were trying to get rid of kubernetes_auth files ;-)

@liggit - FYI

.kubeconfig files can be made portable so they could serve the same purpose.  Using .kubeconfig files means that they can be manipulated and inspected using the command line tooling we have already developed.  They also make it easy for users to be sure that the credentials they are going to provide to pods have the permissions they expect.  The user simply creates the .kubeconfig file and runs the normal osc commands with the --kubeconfig flag.
I know there's been some difficulty understanding the merge order and the like, but a single self-container .kubeconfig file that holds all the secrets with a single set of entries isn't too bad to reason about.

Do we really need breakage?  Can't we just define a different port or
service and deprecate kubernetes_ro?
On Thu, Mar 26, 2015 at 1:56 PM, David Eads<EMAIL_ADDRESS>wrote:

.kubeconfig files can be made portable so they could serve the same
purpose. Using .kubeconfig files means that they can be manipulated and
inspected using the command line tooling we have already developed. They
also make it easy for users to be sure that the credentials they are going
to provide to pods have the permissions they expect. The user simply
creates the .kubeconfig file and runs the normal osc commands with the
--kubeconfig flag.
I know there's been some difficulty understanding the merge order and the
like, but a single self-container .kubeconfig file that holds all the
secrets with a single set of entries isn't too bad to reason about.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/5921#issuecomment-86710901
.

Another alternative: Instead of creating a proxy on each node, create a proxy that we build into a docker image that can (optionally) be deployed in a pod along with a service that exposes a read-only http endpoint. This gives folks an easy transition path from http -> https but makes the default cluster installation only use secure communications to the master.

@liggitt FYI (take 2, hopefully spelled correctly this time)

@cjcullen  and anyone else following along:
Make secrets at cluster startup. #5470 is in.
That creates the following user accounts, which are relevant to this Issue:

system:logging
system:monitoring
system:dns

It also makes secrets at cluster startup in the default namespace with names:

token-system-logging
token-system-monitoring
token-system-dns

You can see these if you start a cluster and then kubectl get secrets token-system-logging, etc.
So, dns needs to use the token-system-dns token and talk to the apiserver on port 6443, rather than using 7080.  The code that sets up its client is in cluster/addons/dns/kube2sky/kube2sky.go.
So:

change newKubeClient in cluster/addons/dns/kube2sky/kube2sky.go to read a kubeconfig file.  Follow the example in  #6969.
change the pod definition, at cluster/addons/dns/skydns-rc.yaml.in, so that the pod has a secret volume and the kube2sky container mounts that volume and has an argument to read the kubeconfig file.

Then, do the same for  cluster/addons/fluentd-elasticsearch/... with the token-system-logging.
Then, decide if it is worthwhile to do:

examples/cassandra/java/io/k8s/cassandra/KubernetesSeedProvider.java
examples/phabricator/cloudsql-authenticator/run.sh
examples/rethinkdb/image/run.sh
examples/rethinkdb/image/run.sh
contrib/for-tests/network-tester/webserver.go

If we don't change those, the demos won't work on on a system without port 7080.
We maybe don't need to use a different token for every component.  We could just define a "default pod user", and make a token for that user, and use that token in all of the above examples.

#7154 updated skydns/kube2sky to use port 6443 w/ the token-system-dns.
I'm taking a look at fluentd/elasticsearch now.

It looks like fluentd/elasticsearch doesn't actually use kubernetes-ro. Am I missing something?

I can't find fluend/elasticsearch either now.

@vishh  changed heapster to support kubernetes_auth files.  https://github.com/GoogleCloudPlatform/heapster/pull/232/files
But then I settled on kubeconfig format instead.
So, heapster needs to change again.

@etune: Here is the heapster logic that I was hoping would handle secrets.

@vishh You really want @erictune, not @etune. He seems a lot smarter than me.

For the examples that use KUBERNETES_RO, would it make sense to create a readonly user/token pair? We'd need to get the policy right to block that user from reading other secrets...
#7101 might make this easier: If we had service accounts, we could just have demos create a "my-demo-sa" service account, and then create a pod that used that service account.

@vishh since you made that change, we moved the bar, so another PR is needed.

@cjcullen in response to your previous comment, I filed a more detailed proposal, #7444

How it relates to #4567?

@gmarek this is a prereq for #4567.

@lavalamp @cjcullen
"Readonly" isn't actually a particularly useful protection since you can read a secret that contains a credential for accessing in a readwrite fashion.
So, I suggest that we deprecate the readonly port, and just use the per-namespace default service account (#7101) as the way to access the apiserver in all examples and contribs.   We can leave it unspecified what permissions this account has (currently read-write, but evolving once the Policy feature is merged).

@erictune SGTM-- and since #7101 has merged I can get right to it.

I'm gonna say that #9233 will fix this; there may be more, but this is the last piece I'm aware of.

Looks like #9233 merged.  @erictune @lavalamp to sanity check where we are and whether this is now closable?

I think this is fixed.


it didn't run after initial set up

So I set it up using files under dist folder but am getting the following error:
hostReportError.ts:8 Uncaught TypeError: Cannot read property 'trim' of undefined
at Object.w [as normalize] (dojo.js:471)
at Object.h._sanitizeUrl (IdentityManager.js:197)
at Object.h.findOAuthInfo (IdentityManager.js:181)
at IdentityManager.js:178
at Array.filter ()
at Object.h.registerOAuthInfos (IdentityManager.js:178)
at Object.t._registerOauthInfos (ApplicationBase.js:465)
at Object.t.load (ApplicationBase.js:146)
at e.project (portal.ts:13)
at e._next (switchMap.ts:104)

@Michael-coc load your app using encrypted protocol -> https://

I am new to hosting configurable apps from my own web server, so help is appreciated.  I downloaded this app to my web server.
I have gone in to the application.json file and adjusted the group id that I want to show in the gallery.  This is a group that is public on ArcGIS Online.  However, I am not able to get this to work.
I know the readme file lists those items that can be adjusted but which items are absolutely necessary to adjust to get this to work?
Also, to access this it mentions to serve the contents of the /dist/ directory from my web server.  Does that mean the link would look something like this https:///FilterGallery/dist/index.html ?


Small fixes for JavaDoc in Body.java

Spell checking and some in-file consistence for the method headers.

I don't think that this javadoc is ever used, since it's an emulation for gwt.

Yeah, probably. I just had to fix it.


Auto-sort items by name then date

This will resolve #41.

This is only for auto sort right? The sort command not done yet right?


Remove hard coding of Chicago for city on tester signup

Currently Patterns hard codes "Chicago" when creating new person from wufoo in People controller. This needs to be changed to allow other cities for Cook County Expansion.
Wufoo form will either need to ask for City or Patterns function needs to be added to map zipcode to city.

For clarification, the hardcoding is in Person model Function self.initialize_from_wufoo(params)

This is complete in Staging.

This was implemented in Production with https://github.com/smartchicago/kimball/commit/d660a8e1a2482386146e2b4bc7e55486507f7018


Looses connection with PIC

With some time in between (most of the time around a day or two) OTGW firmware seems to loose connection with PIC. As this happens the Home page of the OTGW webserver does only show header and buttonbar. So no single row with the name of the sensor and the value of that sensor. Also values are not passed through over MQTT to HA.
While in error on the homepage I am able to read PIC firmware versions using Advanced - PIC Firmware of the OTGW Webserver. So communication with the PIC doesn't seem to be the issue. Values here are:
Firmware name	Version	Size
diagnose.hex	        2.1	9196
gateway.hex	        6.5	26124
interface.hex	        2.0	10488
Resetting PIC with the reset button on the OTGW PCB (I am using the one sold in the Nodo shop) combined with ESP8266 for MQTT communication with HA) makes that within a few seconds the values are available again on the home page of the OTGW webserver Home page and within HA.
What goes wrong? Is is possible to monitor on the OTGW software on failing to retrieve sensor values and then reset the PIC? Is it possible to do a reset of the PIC remotely through OTGW (monitor myself if I still retrieve values and then do a remote reset from out of HA)?
Firmware Version0.10.2+50c3ed2
PIC Availabletrue
PIC Firmware Version6.5
PIC Device IDpic16f1847

Hi @ArJay60
Could you supply some logging using port 23.
Check the wiki: https://github.com/rvdbreemen/OTGW-firmware/wiki/How-to-debug-the-OTGW-firmware
That will help analyse your situation.
And yes, you can reset using the GW=R command. But before you go that route let's try to analyse what going on.
Thanks
Robert

OK. I will do that the next time I have the problem.
Regards
Richard

Still waiting for it to fail. Will keep monitoring.

Once you have it. The. Share. Btw did you know there is a new release available? 0.10.3
There a whole lot of small thinks that got fixed after a year of collecting small patches.
Robert

@ArJay60 Well, the ESP firmware works, but there are not responses or message from the PIC anymore.
So could you try the following:

Logon to port 23 (where you got the logging)
Hit the 'p' to do a manual reset of the pic
See if PIC is rebooted.

Let me know the result please.
Thanks
Robert

Reboots with 'p'. below the log directly after booting:
8:16:00.899064 (  16064| 14104) doTaskMinute( 279): Minute changed:
p18:16:09.917746 (  16064| 14104) sendMQTTupti( 157): Uptime seconds: 1737955
p
18:16:30.595982 (  15824| 14104) handleDebug (  22): Manual reset PIC
18:16:30.765409 (  15744| 14104) detectPIC   ( 122): ETX found after reset: Pic                                                                                detected!
18:16:30.770059 (  13136| 12160) handleDebug (  22): Manual reset PIC
18:16:31.937884 (  15824| 14104) detectPIC   ( 122): ETX found after reset: Pic                                                                                detected!
18:16:32.027417 (  15904| 14104) fwreportinfo(1967): Callback: fwreportinfo
18:16:32.029910 (  13216| 12160) fwreportinfo(1970): Current firmware version: 6                                                                                .5
18:16:32.031134 (  13216| 12160) fwreportinfo(1972): Current device id: pic16f18                                                                                47
18:16:32.031874 (  13216| 12160) fwreportinfo(1975): Current firmware type: gate                                                                                way
18:16:32.032675 (  13216| 12160) processOT   (1701): Current firmware version: 6                                                                                .5
18:16:32.033456 (  13216| 12160) processOT   (1703): Current device id: pic16f18                                                                                47
18:16:32.034155 (  13216| 12160) processOT   (1705): Current firmware type: gate                                                                                way
18:16:32.146972 (  10976| 10296) processOT   (1676): Boiler            BC0193D00                                                                                (9)[MsgID= 25][READ_ACK        ]>Tboiler = 61.00 °C
18:16:32.306859 (  12968| 12160) processOT   (1676): Thermostat        T101815A3                                                                                (9)[MsgID= 24][WRITE_DATA      ]>Tr = 21.64 °C
18:16:33.146211 (  13664| 12808) processOT   (1676): Boiler            BD01815A3                                                                                (9)[MsgID= 24][WRITE_ACK       ] Tr = 21.64 °C
18:16:33.311065 (  12296| 11512) processOT   (1676): Thermostat        T80000200                                                                                (9)[MsgID=  0][READ_DATA       ]>Status = Master [-D---W--]
18:16:34.149338 (  12320| 11512) processOT   (1676): Boiler            B40000200                                                                                (9)[MsgID=  0][READ_ACK        ]>Status = Slave  [--------]
18:16:34.323290 (  12968| 12160) processOT   (1676): Thermostat        T10010600                                                                                (9)[MsgID=  1][WRITE_DATA      ]>TSet = 6.00 °C
18:16:35.182797 (  13640| 12808) processOT   (1676): Boiler            BD0010600                                                                                (9)[MsgID=  1][WRITE_ACK       ] TSet = 6.00 °C
18:16:35.318330 (  15848| 14104) processOT   (1676): Thermostat        T00110000                                                                                (9)[MsgID= 17][READ_DATA       ] RelModLevel = 0.00 %
18:16:36.153529 (  14304| 13456) processOT   (1676): Boiler            BC0110000 (9)[MsgID= 17][READ_ACK        ]>RelModLevel = 0.00 %
18:16:36.335057 (  13640| 12808) processOT   (1676): Thermostat        T80190000 (9)[MsgID= 25][READ_DATA       ] Tboiler = 0.00 °C
18:16:37.178881 (  12968| 11512) processOT   (1676): Boiler            B401933CC (9)[MsgID= 25][READ_ACK        ]>Tboiler = 51.80 °C
18:16:37.317545 (  15848| 14104) processOT   (1676): Thermostat        T00090000 (9)[MsgID=  9][READ_DATA       ] TrOverride = 0.00 °C
18:16:37.460332 (  15176| 14104) processOT   (1676): Boiler            BF0090000 (9)[MsgID=  9][UNKNOWN_DATA_ID ]-TrOverride = 0.00 °C
18:16:38.155406 (  12992| 12160) processOT   (1676): Answer Thermostat AC0090000 (9)[MsgID=  9][READ_ACK        ]>TrOverride = 0.00 °C
18:16:38.328709 (  12296| 11512) processOT   (1676): Thermostat        T80000200 (9)[MsgID=  0][READ_DATA       ]>Status = Master [-D---W--]

Good, that confirms that somehow the PIC needs a reboot. I can add that to the firmware.
When I have the time I will ping you to test it for me.
Robert

Now the question becomes why the PIC needs a reset. I have not heard from other people that they experience the PIC getting stuck.

Great question @hvxl i was wondering about that too. Any idea how we could find out what is going on in his case?

I see two possible ways to think about this:

As nobody else seems to have this problem, maybe the firmware in the PIC is somehow corrupt. This could be due to a hardware fault, or a bit has fallen over and the firmware simply needs to be reflashed. That last option is easy to do, so I would suggest to start with that. If possible, try with another PIC.
Of course there can also be a bug in the firmware that only shows up under very specific circumstances. To have a chance of locating that, it is crucial to understand what is going on at the moment the failure occurs. Having a log is a very important part of that.

@ArJay60 could you possibly run a long term log to find the situation that seems to cause this fault of the PIC. Another option is to replace the PIC, you can order one a nodoshop, that way the hardware issue can be ruled out.
Let me know if you are willing to find the underlying problem.

As I said, the easiest thing to try first is to reflash the PIC firmware. If the problem still occurs after that, you can try some more involved avenues.

Can I reflash the PIC while installed? By which instructions?

That's simple:

Goto the otgw.local (or whatever the IP of your otgw esp)
Click on Advanced button on the top right.

Click on the PIC firmware

You should get a webpage like this:

Now click on the "install this firmware" icon on the right of "gateway.hex" entry. So click this icon:

It takes a few seconds, and the firmware should be installed, the screen will refresh. And you should be back to the default webpage of OTGW and the PIC should be installed with new firmware.
If you want to observe the upgrade, just logon to port 23 and observe the firmware flash process in the log.

Seems to solved with a reflash of the PIC. Will close and keep fingers crossed that problem is gone.


No kind is registered for the type v1.EC2NodeClass in scheme even importing it in main.go

Description
Observed Behavior:
I'm creating an operator to manage Nodepools. In v1 the AddToScheme was removed to simplificate the schema registration. But it happens that I even import it into my main.go I got the error saying that the kind is not registered:  "error": "failed to apply *v1.EC2NodeClass: no kind is registered for the type v1.EC2NodeClass in scheme "pkg/runtime/scheme.go:100
Expected Behavior:
Reproduction Steps (Please include YAML):
It follows my main.go file:
package main

import (
   "crypto/tls"
   "flag"
   "os"

   // Import all Kubernetes client auth plugins (e.g. Azure, GCP, OIDC, etc.)
   // to ensure that exec-entrypoint and run can make use of them.
   _ "k8s.io/client-go/plugin/pkg/client/auth"

   _ "github.com/aws/karpenter-provider-aws/pkg/apis/v1"
   "k8s.io/apimachinery/pkg/runtime"
   utilruntime "k8s.io/apimachinery/pkg/util/runtime"
   clientgoscheme "k8s.io/client-go/kubernetes/scheme"
   ctrl "sigs.k8s.io/controller-runtime"
   "sigs.k8s.io/controller-runtime/pkg/healthz"
   "sigs.k8s.io/controller-runtime/pkg/log/zap"
   "sigs.k8s.io/controller-runtime/pkg/metrics/filters"
   metricsserver "sigs.k8s.io/controller-runtime/pkg/metrics/server"
   "sigs.k8s.io/controller-runtime/pkg/webhook"
   _ "sigs.k8s.io/karpenter/pkg/apis/v1"

   "github.com/nubank/nuks/karpenter-crd/api/v1alpha1"
   "github.com/nubank/nuks/karpenter-crd/internal/controller"
   // +kubebuilder:scaffold:imports
)

var (
   scheme   = runtime.NewScheme()
   setupLog = ctrl.Log.WithName("setup")
)

func init() {
   utilruntime.Must(clientgoscheme.AddToScheme(scheme))

   utilruntime.Must(v1alpha1.AddToScheme(scheme))
   // +kubebuilder:scaffold:scheme
}

func main() {
   var metricsAddr string
   var enableLeaderElection bool
   var probeAddr string
   var secureMetrics bool
   var enableHTTP2 bool
   var tlsOpts []func(*tls.Config)
   flag.StringVar(&metricsAddr, "metrics-bind-address", "0", "The address the metrics endpoint binds to. "+
   	"Use :8443 for HTTPS or :8080 for HTTP, or leave as 0 to disable the metrics service.")
   flag.StringVar(&probeAddr, "health-probe-bind-address", ":8081", "The address the probe endpoint binds to.")
   flag.BoolVar(&enableLeaderElection, "leader-elect", false,
   	"Enable leader election for controller manager. "+
   		"Enabling this will ensure there is only one active controller manager.")
   flag.BoolVar(&secureMetrics, "metrics-secure", true,
   	"If set, the metrics endpoint is served securely via HTTPS. Use --metrics-secure=false to use HTTP instead.")
   flag.BoolVar(&enableHTTP2, "enable-http2", false,
   	"If set, HTTP/2 will be enabled for the metrics and webhook servers")
   opts := zap.Options{
   	Development: true,
   }
   opts.BindFlags(flag.CommandLine)
   flag.Parse()

   ctrl.SetLogger(zap.New(zap.UseFlagOptions(&opts)))

   // if the enable-http2 flag is false (the default), http/2 should be disabled
   // due to its vulnerabilities. More specifically, disabling http/2 will
   // prevent from being vulnerable to the HTTP/2 Stream Cancellation and
   // Rapid Reset CVEs. For more information see:
   // - https://github.com/advisories/GHSA-qppj-fm5r-hxr3
   // - https://github.com/advisories/GHSA-4374-p667-p6c8
   disableHTTP2 := func(c *tls.Config) {
   	setupLog.Info("disabling http/2")
   	c.NextProtos = []string{"http/1.1"}
   }

   if !enableHTTP2 {
   	tlsOpts = append(tlsOpts, disableHTTP2)
   }

   webhookServer := webhook.NewServer(webhook.Options{
   	TLSOpts: tlsOpts,
   })

   // Metrics endpoint is enabled in 'config/default/kustomization.yaml'. The Metrics options configure the server.
   // More info:
   // -<EMAIL_ADDRESS>   // - https://book.kubebuilder.io/reference/metrics.html
   metricsServerOptions := metricsserver.Options{
   	BindAddress:   metricsAddr,
   	SecureServing: secureMetrics,
   	// TODO(user): TLSOpts is used to allow configuring the TLS config used for the server. If certificates are
   	// not provided, self-signed certificates will be generated by default. This option is not recommended for
   	// production environments as self-signed certificates do not offer the same level of trust and security
   	// as certificates issued by a trusted Certificate Authority (CA). The primary risk is potentially allowing
   	// unauthorized access to sensitive metrics data. Consider replacing with CertDir, CertName, and KeyName
   	// to provide certificates, ensuring the server communicates using trusted and secure certificates.
   	TLSOpts: tlsOpts,
   }

   if secureMetrics {
   	// FilterProvider is used to protect the metrics endpoint with authn/authz.
   	// These configurations ensure that only authorized users and service accounts
   	// can access the metrics endpoint. The RBAC are configured in 'config/rbac/kustomization.yaml'. More info:
   	//<EMAIL_ADDRESS>   	metricsServerOptions.FilterProvider = filters.WithAuthenticationAndAuthorization
   }

   mgr, err := ctrl.NewManager(ctrl.GetConfigOrDie(), ctrl.Options{
   	Scheme:                 scheme,
   	Metrics:                metricsServerOptions,
   	WebhookServer:          webhookServer,
   	HealthProbeBindAddress: probeAddr,
   	LeaderElection:         enableLeaderElection,
   	LeaderElectionID:       "a4fe8aa3.k8s.nu",
   	// LeaderElectionReleaseOnCancel defines if the leader should step down voluntarily
   	// when the Manager ends. This requires the binary to immediately end when the
   	// Manager is stopped, otherwise, this setting is unsafe. Setting this significantly
   	// speeds up voluntary leader transitions as the new leader don't have to wait
   	// LeaseDuration time first.
   	//
   	// In the default scaffold provided, the program ends immediately after
   	// the manager stops, so would be fine to enable this option. However,
   	// if you are doing or is intended to do any operation such as perform cleanups
   	// after the manager stops then its usage might be unsafe.
   	// LeaderElectionReleaseOnCancel: true,
   })
   if err != nil {
   	setupLog.Error(err, "unable to start manager")
   	os.Exit(1)
   }

   if err = (&controller.NodeGroupReconciler{
   	Client: mgr.GetClient(),
   	Scheme: mgr.GetScheme(),
   }).SetupWithManager(mgr); err != nil {
   	setupLog.Error(err, "unable to create controller", "controller", "NodeGroup")
   	os.Exit(1)
   }
   // +kubebuilder:scaffold:builder

   if err := mgr.AddHealthzCheck("healthz", healthz.Ping); err != nil {
   	setupLog.Error(err, "unable to set up health check")
   	os.Exit(1)
   }
   if err := mgr.AddReadyzCheck("readyz", healthz.Ping); err != nil {
   	setupLog.Error(err, "unable to set up ready check")
   	os.Exit(1)
   }

   setupLog.Info("starting manager")
   if err := mgr.Start(ctrl.SetupSignalHandler()); err != nil {
   	setupLog.Error(err, "problem running manager")
   	os.Exit(1)
   }
}

Versions:

Chart Version:
Kubernetes Version (kubectl version):

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Curious what the issue was - I'm running into the same problem

Curious what the issue was - I'm running into the same problem

I ended up here researching the same error as a user of the Karpenter tool.
It turned out that the requested pod had volume requirements that weren't being met (EFS in my case).
I'm not sure why that results in this error in the Karpenter controller and it may end up being entirely unrelated, but for posterity: after fixing pod dependencies (applying the EFS-CSI-Driver, EFS StorageClass and creating the dependent volume) this error seemed to go away.
EKS 1.31
Karpenter 1.0.7 via oci://public.ecr.aws/karpenter


Make an interactive ERP subplot for an ICA component

Describe the new feature or enhancement
Currently, when displaying the individual ICA component, the ERP subplot is not interactive. We want to make this subplot interactive .
Describe your proposed implementation
Implement a rectangle selector to zoom in and out for this plot.

@mdclarke

Sounds like this has been discussed with @drammock already, looking forward to a PR!


enhancement: add standard number validity checking

In the future, it would be nice to add some validity checking for standard numbers. Some examples:
bf:Lccn -- defined at https://www.loc.gov/marc/lccn_structure.html -- perhaps set a maximum length of the field?
bf:Issn -- perhaps include a check digit calculator? https://www.loc.gov/issn/basics/basics-checkdigit.html
bf:Isbn -- perhaps include a check digit calculator for 13-digit ISBNs?

transferred to Gitlab


Python 3.x support

Update niflib to use Python3.x

After having pip install modernize, try:
py -3.9 -m modernize -w FILENAME
py -3.9 -m pyupgrade --py3-plus --py36-plus --py37-plus --py38-plus FILENAME
with filename replaced with target files(and 3.9 replaced with current python version)(worked for upgrading docsys to 3.x)
Manually replace the .imports such as
from .nifxml import Member, Compound, Block
into
from nifxml import Member, Compound, Block
And possibly also delete the init.py files so python 3.x can autopackage without needing from future imports

Feel free to PR back in to the repos, I see that you have alot of working going on.
If you can drop by - discord.gg/9V2BSzR4

Discord link invalid

Sorry might have expired, updated there.
The last piece of work that jon did was to add some support within the nif.xml library itself to generate docs, with the intent that it should be self describing and not have to rely on external tooling.
I have a PR open for a minor bug, but haven't had time to look much further past it I am afraid.
All contributions are welcome as most project could do with much love to get them up to using latest versions.


Regr Test: Add multiple repetitions Feature

Proposed changes:

Parse num_repetitions from config, Add index_repetition to each matrix element

Add index_repetition to json, segment data, and datadog tags

Change gomplate input interface: Now accepts list-format for results (not yet for on-schedule results_main)
Adjust result comment (Example)
Adjust artifact names (include index_repetition now)
Had to change interface of result.json dict: Use list instead dict

Also changed interface (dict -> list) of single-experiment json files

BEFORE
{
  "Carbon Bot": {
    "BERT + DIET(bow) + ResponseSelector(bow)": {
      "accelerator_type": "GPU",
      ...

NEW
{
  "Carbon Bot": {
    "BERT + DIET(bow) + ResponseSelector(bow)": [{
    "accelerator_type": "GPU",
    ...

change the interface of on-schedule tests
Add legacy template for migration purposes so that the comment/analysis step doesn't fail until everybody is using the new interface

Refactor existing template model_regression_test_results.tmpl:

Refactor: introduce variable 'one_content_dict' to avoid duplication
Refactor tmpl: Rename dataset_main to results_for_dataset_main
Refactor tmpl: Rename config to results_for_dataset

Status (please check what you already did):

[x] added some tests for the functionality: Add unit test for gomplate template: model_regression_test_results.tmpl
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

/modeltest
dataset_branch: "main"
num_repetitions: 3
include:
 - dataset: ["financial-demo"]
   config: ["BERT + DIET(seq) + ResponseSelector(t2t)"]

FYI @tczekajlo


Remove unused imports.

Due to a bug in ghc, some unused imports do not yield warnings.
This commit will remove such unused imports in preparation for
the ghc bug fix (see https://ghc.haskell.org/trac/ghc/ticket/13064).

I've submitted this too early. Please consider this still a WIP PR. It may turn out unneeded in the end, but it depends on the changes for ghc issue 13064.


Message does not have permission to read or transmit content When I Use With Code With My Application

When I run Container App and Extension Shows At Safari Extension Preferences Its Shows me A Message does not have permission to read or transmit content from any webpages I don't find any Solution How to resolved this , Any Extension certificate required , now I am using developer certificate

Hi!
Could you attach some screenshots with the exact error messages?
The project needs to be updated to the latest Xcode 9 standards & Swift version. I do not have the time currently to do that but will try to update it in the near future. Manually using the .json files in the Safari Extension Builder should still work.


Web App support

Added support for Web Apps from Bot API v6
Read more here

@aero89 yes. E.g. python telebot has added support for web app.

Thank you! These changes will appear on V3.1 which I'm going to release soon. (Probably adjusted a little after a refactoring phase)


[gestures] Add possibility to enable only desired gestures

Sometimes the user can be interested in detecting only some specific gestures and ignore all the others.
Related functions [gestures.c]
void SetGesturesEnabled(unsigned int gestureFlags);

Function was declared to be completed, the idea was using mask-based flags system to enable/disable desired gestures. Enabled/Disabled gestures must be considered or not on UpdateGestures()

Implemented on commit https://github.com/raysan5/raylib/commit/d32feaa6685584e9856aa94f4d5bf80b7f5b861c


Replace deprecated NumPy aliases with builtin types

NumPy 1.20 deprecates some of the aliases of the builtin types: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
With version 1.24 the aliases were removed; the change is necessary to keep TrackEval working with newer versions of NumPy.
I replaced np.int, np.float and np.bool aliases with builtin types according to the table in the deprecation note.

The problem here is that pycocotools, which is used by this repo, also has this issue. While it isn't updated on both sides. I see no way of merging this.

I see. However the use of these aliases is not consistent throughout TrackEval and this PR addresses this issue, unifying the approach (there are multiple places in which Python types were already used). What is more, for those who use TrackEval without the functionalities of pycocotools (myself included), this allows to use newer versions of NumPy as well.
One way would be to create a fork of pycocotools, fix the issues and switch to the fork here. This seems to be a bit of a fuss though :/

One way would be to create a fork of pycocotools, fix the issues and switch to the fork here. This seems to be a bit of a fuss though :/

Yup :disappointed:

Came here looking to fix it myself because we need to update to Numpy 1.14, but then found this MR.
It's not preferable to stay tied to pycocotools if they are so far behind with Numpy. Perhaps creating a fork and updating it should be the way to go.

Also, pycocotools uses np.float in 2 lines only.
https://github.com/cocodataset/cocoapi/blob/master/PythonAPI/pycocotools/cocoeval.py#L378
I fixed it for me with this hack:
import numpy as np
from packaging import version

if version.parse(np.__version__) >= version.parse("1.24.0"):
    np.float = np.float32
    np.int = np.int32
    np.bool = bool

Added it just before the import to trackeval. But it would be awesome to see someone taking pycocotools over and updating it.

these commands to patch from CLI  worked for me
grep -rl np.int . | xargs sed -i 's/np.int/int/g'
grep -rl np.bool . | xargs sed -i 's/np.bool/bool/g'
grep -rl np.float . | xargs sed -i 's/np.float/float/g'

As the original Python API doesn't seem to be maintained anymore, would you consider using an alternative?
For example:
pycocotools
We could them merge this MR.


[Integration] It's impossible to edit (and Move to) prompt which was created as a duplicate from "Shared with me"

By user1 create a prompt -> copy the link to share the prompt
By user2 click on the link -> the prompt appears in "Shared with me"
By user2 create a duplicate of shared prompt
Select Edit item in context menu for duplicated prompt -> error in console appears, loader is shown instead of prompt body -> bug

reproduced on staging
Move to error:

Verified on staging successfully


Code generation improvements for better SIMD utilization

It is quite likely that LLVM's autovectorizer is not fully taking advantage of SIMD instructions due to issues with the LLVM IR that Numba emits.  We may also need to reverse engineer the IR that clang emits.

With the refcount improvement we are doing now, we are moving closer

Closing as this ticket has largely been addressed by https://github.com/numba/numba/pull/6266 and https://github.com/numba/numba/pull/3847. If new instances of specific missed SIMD optimisations are encountered please open new tickets with example code. Thanks.


Add support for Python 3.11

Is your feature request related to a problem? Please describe.
It's not possible to pip install on Python 3.11.
Describe the solution you'd like
Update package to support Python 3.11.

also for python3.9 it would be nice


solving s360 issues in MarketplaceOrdering swagger

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

The changes Im trying to do are in response for an S360 Alert that was triggered for the swagger – It says that some APIs that are defined in the swagger do not match the actual responses our service returns.
The APIs and the swagger are running in production from 2015, and are in use by many other services and customers, so theres no way for us to change the code so it matches the swagger. We have to change the swagger to match the code.
Ive requested approval for breaking changes for that reason

Hi @weidongxu-microsoft, The PR has been approved for breaking changes, and I have resolved all the validation error that could be resolved without changing the code.
Please finish your review of the PR and approve if there are no further issues
Thanks

@alkigel
Please fix LintDiff.

@weidongxu-microsoft As mentioned before, fixing the lintDiff error is not possible.
The error is:
Property named: 'Message', for definition: 'UnsupportedMediaTypeErrorResponse' must follow camelCase style. Example: 'message'
Meaning I need to change both the swagger and the code to have the field 'message' instead of 'Message'. But changing the code is impossible since its in production for several years now and will break clients in prod. so the field name must remain 'Message"

@alkigel
Then you can suppress it in readme.md


version 0.6.60 problem with "merge selected groups"

Hi Matt, I just started using the XASViewer from Larch and it worked great with the version 0.9.59. Today I did the update to version 0.6.60 and now unfortunately I cannot "merge selected groups" anymore. Thanks in advance.

@jo-schroe Ack, and thanks.   I can confirm this... I'll have a fix in the development version tomorrow.  This might need a fixed release before the end of the week.

Thanks Matt for taking care of it so fast!

@jo-schroe I believe this is fixed in 0.9.61


relic: 8.1.0 -> 8.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/sassoftware/relic/releases.
meta.description for relic is: Service and a tool for adding digital signatures to operating system packages for Linux and Windows
meta.homepage for relic is: https://github.com/sassoftware/relic
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 8.1.1 with grep in /nix/store/hvkmwmr2zkn76nbqmdkhz4bb47404g6s-relic-8.1.1
found 8.1.1 in filename of file in /nix/store/hvkmwmr2zkn76nbqmdkhz4bb47404g6s-relic-8.1.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

relic

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hvkmwmr2zkn76nbqmdkhz4bb47404g6s-relic-8.1.1 \
  --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 relic https://github.com/r-ryantm/nixpkgs/archive/4ef90206676e43c9c9378793591138be3dca3eea.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/4ef90206676e43c9c9378793591138be3dca3eea#relic

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hvkmwmr2zkn76nbqmdkhz4bb47404g6s-relic-8.1.1
ls -la /nix/store/hvkmwmr2zkn76nbqmdkhz4bb47404g6s-relic-8.1.1/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:

relic

Maintainer pings
cc @strager 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.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 362967

aarch64-darwin

:white_check_mark: 1 package built:

relic


ipptool: add a "$basename" variable

The $filename variable provides the entire path specified by the -f option. It would be nice if there was a way to trim that to its "basename" component (last element in the path) for when the filename is used in job naming, such as
ATTR name "job-name" "Some test $user $basename $job-id" etc. so that looking at the job log can be useful when testing.

Probably better to file this bug against the libcups project...

Moved to https://github.com/OpenPrinting/libcups/issues/44


CHEBI:2150, please CHECK entry

Hi Gareth and Steve,
Please CHECK this entry, 5beta-Dihydrotestosterone, that is used in Rhea.
Cheers,
Kristian

Hi Kristian,
Now done.
Cheers,
Gareth


Windows GUI: Change font for 'Text' view

This patch makes MediaInfo use Cascadia Mono font for 'Text' view if it is available on the system. Most updated Windows systems with Windows Terminal installed will have this font.
Reason for this change is that the current font does not scale properly. Notice that it does not scale as linearly as Cascadia Mono. Cascadia Mono also has smoother edges and is easier to read especially on high DPI scaling.
Comparison @ 100%

Comparison @ 150%

Comparison @ 200%

Let me know if it is desirable to change the font for other views as well.

Let me know if it is desirable to change the font for other views as well.

Yes, I prefer coherence so same font everywhere.


mv: make 'UpdateMode' public for nushell

Related to the work done on making some mv api public in pull #5335, there was UpdateMode missing from that as its still private and therefore cannot build Options {} for nushell.
The fix :
diff --git a/src/uu/mv/src/mv.rs b/src/uu/mv/src/mv.rs
index 9888389ae..02c856ce0 100644
--- a/src/uu/mv/src/mv.rs
+++ b/src/uu/mv/src/mv.rs
@@ -19,12 +19,12 @@ use std::os::unix;
 #[cfg(windows)]
 use std::os::windows;
 use std::path::{Path, PathBuf};
-pub use uucore::backup_control::BackupMode;
 use uucore::backup_control::{self, source_is_target_backup};
 use uucore::display::Quotable;
 use uucore::error::{set_exit_code, FromIo, UError, UResult, USimpleError, UUsageError};
 use uucore::fs::{are_hardlinks_or_one_way_symlink_to_same_file, are_hardlinks_to_same_file};
-use uucore::update_control::{self, UpdateMode};
+use uucore::update_control;
+pub use uucore::{backup_control::BackupMode, update_control::UpdateMode};
 use uucore::{format_usage, help_about, help_section, help_usage, prompt_yes, show};

 use fs_extra::dir::{

Right now I use that diff and it seems to work just fine from nushell, so the fix should be just fine I think :)
I could also make a PR with these tiny changes if its ok so that nushell can use them

Yes, make a PR, please


[AIRFLOW-XXX] Fix typos in faq.rst

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
Fix minor typos in faq.rst (https://airflow.apache.org/faq.html#what-are-all-the-airflow-run-commands-in-my-process-list).

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Only documentation .rst file is changed.

Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #3837 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3837   +/-   ##
=======================================
  Coverage   77.43%   77.43%
=======================================
  Files         203      203
  Lines       15846    15846
=======================================
  Hits        12271    12271
  Misses       3575     3575

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 a9878eb...2a536da. Read the comment docs.

Thanks @kaxil


Addresses empty stdClass case when doing a getdiff

Based on Pact-PHP test case to hit matches.json specification in 1.1

Thank you for your collaboration. Your help is very important to maintain the tool. I did some testing on "index.php" and in your case "TreeWalkerTest.php", and everything worked as expected with your fix.


Pl3xMap and MapTowny produce diagonal lines in plot renders

Describe the Bug
I just recently updated to the Alpha and noticed how in certain situations the lines don't line up as they should with Pl3xMap, producing diagonal lines instead of vertical ones.
Expected Behavior

The lines should go as shown in red but they actually connect diagonally which is obviously not correct.
Plugin Version
MapTowny version 3.0.0-ALPHA-1
Towny Version
Towny version <IP_ADDRESS>
Pl3xMap Version
Pl3xMap v3 1.20.4-SNAPSHOT (paper) git-3f104c4
I know this is a snapshot version but it should have nothing to do with this rendering bug.
Server Software Version
Paper version git-Paper-447 (MC: 1.20.4)
Additional Comments
None

Thanks for reporting this! Could you please post the results of towny map big ran in-game in the area shown by the map?

Should be fixed in v3.0.0-alpha-2, please try the second alpha version and let me know if it doesn't work. Thanks for reporting this!

I can confirm it's no longer happening, I just updated and checked.
Thanks for the update and take care 👋


tell rex to keep promoted headers in BakeOrderHeaders

fixes openstax/cnx-recipes#5447

Investigation:

built nursing-external bundle with latest tagged versions of submodules on enki
discovered that html for title links is present in the JSON served to rex
discovered that contents of <a> tag is being removed, likely in rex postprocessing

dug into rex content postprocessing, which is well documented. found an interaction between it & a recent bake-web change (removes h2 document-title elements --> turns some h3 document-title elements into h2s).
fix: add the data-rex-keep class to these h2s.


Expose some of the S3 client configuration for assets

This exposes some of the S3 client configuration for assets so we can change it.
This includes:

Max Connections
Connection Timeout
Max Retries

Additionally I improved the related documentation a bit.

Can we add these config bits to the distribution code as well?  I can see someone expecting in both places.

@gregorydlogan I was afraid you'd ask that...

@gregorydlogan Added the same options to distribution and couldn't resist cleaning up the code and the documentation a bit...


Derby Embedded DB stays open when using the Gradle wrapper

Which version and edition of Flyway are you using?
flyway 5.1.4, Derby <IP_ADDRESS>,
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Gradle plugin
Which database are you using (type & version)?
Derby Embedded Client
Which operating system are you using?
MacOS 10.11 but also confirmed happening on Windows using bash.
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
Running 'gradle flywayMigrate' twice causes derby database to not be connected due to the lock files still being valid. Running 'pkill java' fixes the issue for another run. 'gradle flywayMigrate --no-daemon' makes the issue go away.

Good point. This has now been fixed.


Sun Belly Foods

Business has no other contact info beyond Instagram link.

This is all we got for now, sorry.


update pvfree url

to https://pvfree.azurewebsites.net/

Yes, correct. I included it in this PR https://github.com/PVSC-Python-Tutorials/pyData-2021-Solar-PV-Modeling/pull/4 for including colab pip install commands in this commit https://github.com/PVSC-Python-Tutorials/pyData-2021-Solar-PV-Modeling/commit/982abca488e77bf39855fb84162a04bfb226f690 for PyData tutorial which was already merged and in this PR: https://github.com/PVSC-Python-Tutorials/PVSC48-Python-Tutorial/pull/13 for PVSC48.