Plugin disabled by Grafana

Just installed Grafana 7.4.0. Installed plugin. Shows disabled because of "Modified signature":
We have encountered data source backend plugins that are unsigned. Grafana Labs cannot guarantee the integrity of unsigned plugins and recommends using signed plugins only.
The following plugins are disabled and not shown in the list below:
marcusolsson-csv-datasource

Modified signature - Valid signature but content has been modified

Note that unsigned front-end datasource plugins are still usable, but this is subject to change in the upcoming releases of Grafana

Thank you for noticing. I'll look into this right away.

I've just tested version 0.3.3 in both 7.3.7 and 7.4.0 and it shows a valid signature.
What OS are you running, and how did you install the plugin?

I am using Windows 10 with all the latest updates:
Edition: Windows 10 Pro
Version: 20H2
OS Build: 19042.746
Installation:
C:\Users\drano>grafana-cli plugins install marcusolsson-csv-datasource
installing marcusolsson-csv-datasource @ 0.3.3
from:
https://grafana.com/api/plugins/marcusolsson-csv-datasource/versions/0.3.3/download
into: ../data/plugins
←[32m✔←[0m Installed marcusolsson-csv-datasource successfully
Failed to remove temporary
filefileC:\Users\drano\AppData\Local\Temp\954340319.ziperrremove
C:\Users\drano\AppData\Local\Temp\954340319.zip: The process cannot access
the file because it is being used by another process.
Restart grafana after installing plugins .
C:\Users\drano>
On Sun, Feb 7, 2021 at 11:31 PM Marcus Olsson<EMAIL_ADDRESS>wrote:

I've just tested version 0.3.3 in both 7.3.7 and 7.4.0 and it shows a
valid signature.
What OS are you running, and how did you install the plugin?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/marcusolsson/grafana-csv-datasource/issues/32#issuecomment-774878259,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVN7CKPI6EDWMUX5DQFI5TS55ZKFANCNFSM4XIEN6TA
.

Thank you for the details, I'll see if I can get my hands on a Windows machine to try and reproduce this.

Just to confirm, are you able to install the plugin on 7.3?

I've verified that the plugin works on 7.3.7, but fails in 7.4 on Windows 10. This feels like a bug in Grafana. I'll do some more research and get back to you.

Yes, I actually did install it on Grafana 7.3 but did not try it. I got a
message saying Grafana could be upgraded, which I did. Then, I noticed the
problem.
On Mon, Feb 8, 2021 at 8:20 AM Marcus Olsson<EMAIL_ADDRESS>wrote:

I've verified that the plugin works on 7.3.7, but fails in 7.4 on Windows
10. This feels like a bug in Grafana. I'll do some more research and get
back to you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/marcusolsson/grafana-csv-datasource/issues/32#issuecomment-775182294,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVN7COAF4GTNI7GSAZGRDTS57XJVANCNFSM4XIEN6TA
.

FYI. I went back to Grafana 7.37 and reinstalled your plugin okay. I wanted
to use it with a local CSV file which works if I enter file name, rather
than full path in the Path item of the UI. Then, the CSV file must be
placed in the "Grafana Home" folder. That will certainly take care of me
for now.
Thanks for your help!
Norm
On Mon, Feb 8, 2021 at 11:40 AM Norm Draper<EMAIL_ADDRESS>wrote:

Yes, I actually did install it on Grafana 7.3 but did not try it. I got a
message saying Grafana could be upgraded, which I did. Then, I noticed the
problem.
On Mon, Feb 8, 2021 at 8:20 AM Marcus Olsson<EMAIL_ADDRESS>wrote:

I've verified that the plugin works on 7.3.7, but fails in 7.4 on Windows
10. This feels like a bug in Grafana. I'll do some more research and get
back to you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/marcusolsson/grafana-csv-datasource/issues/32#issuecomment-775182294,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVN7COAF4GTNI7GSAZGRDTS57XJVANCNFSM4XIEN6TA
.

There's bug related to paths on Windows. If you use forward-slashes instead, you can use a full path. But I'm glad you got it to work.
https://github.com/marcusolsson/grafana-csv-datasource/issues/26
The Grafana team is working on a fix, so try again when the next release is out :)

level=error msg="Plugin validation failed" pluginId=larona-epict-panel error="plugin 'larona-epict-panel' has an modified signature"
I have built a docker image using my plugins and i ftecjed plugins from docker image it worked fine for grafana version 8 but for grafana 11 i am facing the above error.
Any suggestions


Read The Docs flyout menu is now in the bottom-right corner

Read The Docs changed how they do various things including the flyout menu [1]. In our Insipid-themed, Read The Docs-managed documentation projects [2][3], this has caused the flyout menu to appear in the bottom-right corner (leaving a blank area in the bottom-left corner where it used to be).
[1] https://about.readthedocs.com/blog/2024/07/addons-by-default/
[2] https://docs.lockss.org/
[3] https://docs.lockss.org/projects/manual/

Thanks for reporting this!
I'm aware of this new behavior, and I don't like it.
There are some discussions going on, e.g. here: https://github.com/readthedocs/readthedocs.org/issues/11688
Other themes are affected by this as well, but I haven't yet seen a real good solution how to work around this new situation.
If you have any ideas, please let me know!
I'm thinking about moving my own projects off of RTD eventually, but I still have to find a way how to handle a multi-version site. I have done some experiments there: https://github.com/mgeier/version-injector-nursery/


Coq installer makes binaries available?

Description of the problem

We teach using Coq at an introductory level (second course for CS majors), where many of the students aren't particularly familiar with the terminal. The startup cost---whether we use CoqIDE or Proof General---is fairly high; in both setups, we've had to use coqc on the terminal to manually compile things.
It would be helpful to us if CoqIDE, on installation, either:
(a) symlinked /usr/local/bin/coq* to the installation location (e.g., /Applications/CoqIDE\ 8.10.2.app/Contents, or
(b) added the installation location to the user's PATH
The precise way to do this (and possibly, best course of action) may be platform dependent.
Coq Version
8.10.2 on macOS and Windows.

@SkySkimmer : On Mac it is tricky, because the contents of an application package is not (usually) visible, so one can't put anything in there a non expert user can be expected to find. What one could do is to include a shell script at the top level of the .dmg file one can move e.g. to the desktop.
But in general I would say there is no bullet proof way to supply a working shell environment for people who don't know what a shell is.
It might be easiest to explain what path command you have to issue on macOS or Windows.


Suggestion: function that split iterable into two at a given position

Split by Index
function splitAt (position, iter) {
  const [first, second] = tee(iter)
  return [
    slice({ end: position }, first),
    slice({ begin: position }, second)
  ]
}

Split by Condition
...

fork is now on master @KSXGitHub
I like both splitAt and splitBy ideas ;-)


upsert has wrong 'nModified' when document has no change

import mongomock
collection = mongomock.MongoClient().test.test
r = collection.update({'a': 1}, {'$set': {'b': 2}}, upsert=True)
r = collection.update({'a': 1}, {'$set': {'b': 2}}, upsert=True)
assert r['nModified'] == 0

AssertionError                            Traceback (most recent call last)

<ipython-input-70-50d7132d83ce> in <module>()
      3 r = collection.update({'a': 1}, {'$set': {'b': 2}}, upsert=True)
      4 r = collection.update({'a': 1}, {'$set': {'b': 2}}, upsert=True)
----> 5 assert r['nModified'] == 0
      6

AssertionError:

Thanks for reporting. Sorry for the delay in triaging.

This was reported again in #355, and #423 is a PR that will fix it. In the meantime I'll close this one as duplicate.


Use "set par()" instead of "show par: set block()"

show par: set block(spacing: ..) has no effect anymore, as paragraphs are not considered blocks anymore.
Use set par(spacing: ..) instead.

Can this be merged :)

You got it. Thanks!

Thank you for the quick response :)


Bumping 2.x to 2.4.0

Signed-off-by: Suraj Singh<EMAIL_ADDRESS>Description
Preparing for 2.3.0 release. Bumping 2.x current version to 2.4.0
2.3 branch  - https://github.com/opensearch-project/OpenSearch/tree/2.3
Issues Resolved
https://github.com/opensearch-project/OpenSearch/issues/4357
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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

Codecov Report

Merging #4454 (552e704) into 2.x (ceb0e17) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##                2.x    #4454      +/-   ##
============================================
+ Coverage     70.67%   70.70%   +0.03%
- Complexity    57179    57189      +10
============================================
  Files          4585     4585
  Lines        274506   274507       +1
  Branches      40227    40227
============================================
+ Hits         193996   194081      +85
+ Misses        64278    64171     -107
- Partials      16232    16255      +23

Impacted Files
Coverage Δ

server/src/main/java/org/opensearch/Version.java
82.40% <100.00%> (-0.85%)
:arrow_down:

...adcast/BroadcastShardOperationFailedException.java
33.33% <0.00%> (-66.67%)
:arrow_down:

...h/action/ingest/SimulateDocumentVerboseResult.java
60.71% <0.00%> (-39.29%)
:arrow_down:

...ion/admin/cluster/node/info/PluginsAndModules.java
53.12% <0.00%> (-34.38%)
:arrow_down:

...r/src/main/java/org/opensearch/http/HttpUtils.java
33.33% <0.00%> (-33.34%)
:arrow_down:

...opensearch/index/reindex/BulkByScrollResponse.java
48.38% <0.00%> (-28.23%)
:arrow_down:

...va/org/opensearch/client/sniff/SnifferBuilder.java
72.72% <0.00%> (-27.28%)
:arrow_down:

...main/java/org/opensearch/ingest/ProcessorInfo.java
47.36% <0.00%> (-21.06%)
:arrow_down:

...pensearch/test/rest/yaml/section/SetupSection.java
74.07% <0.00%> (-18.52%)
:arrow_down:

...ch/persistent/decider/EnableAssignmentDecider.java
59.09% <0.00%> (-18.19%)
:arrow_down:

... and 464 more

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


straight.el vs package.el - Which should we stick with?

Discuss!

Hm. That does depend on what Rational Emacs is supposed to be, isn't it? We might need to discuss that one too. If RE is supposed to be closer to the original Emacs and mostly provide reasonable defaults, then I'd strongly suggest package.el. But if it's an opinionated piece, then straight.el might be fine.

Going by the current README and the principles stated there, I'd definitely go with the built-in package.el:

Principles
This configuration and all associated modules intend to follow the below priniciples. [...]
Minimal, modular configuration [...]
Prioritize built-in Emacs functionality [...]

But I'm not a straight.el user and thus don't quite know its possible advantages.

I liked @daviwil's thoughts on being able to pin to other git repos to support a time when modules may themselves become their own projects. However, we are no where close to that.
I feel it would be best to go with package.el for now. If we run into an issue which that cannot solve, we can address it at that time.

Any additional thoughts? We seem to be trending toward using package.el instead of straight as the default package manager here.
cc: @daviwil

NOTICE!!!!
There seems to be no further discussion here, and the consensus seems to be to prefer package.el as it is built-in. I'll begin the work to make that change on Monday, 5 April 2022 unless there is further discussion here.

After looking at #120, I'm a bit confused on the plan.
Is the idea to allow the user to use straight if they decide to configure it? I think that might get us into some mixed up scenarios. If we allow the user to choose, we will need to make sure only one of them is ever active.

So, I was of two minds on that. I left it in the macro because we had used it and maybe someone who preferred straight wouldn't have to do anything other than add the bootstrap to their early-config.el file. I'd rather take it out now that I've been tinkering with it, especially since the bootstrap stuff is gone for straight.

@jeastman I've updated the PR, if you could review one more time please.

Unfortunately I missed this thread. It is disappointing straight support has gone as I find it much more reliable than package.el. As an example, I just did a completely fresh install of rational-emacs on a VM and it now fails to start correctly with errors relating to problems in the package.el version of evil-ex.  Having been a package.el user for a long time, I know how to resolve these problems, but their resolution is more work/effort than with straight.el. My original hope was that this project would provide a modular repository which would allow users to easily select the 'modules' they want, including preferred package management.
I understand this is the direction the community has decided upon and that is fine. I'm very thankful for the good ideas and exmaples this has provided, but I think for now, I'll go my own way. I'm particularly thankful for this project introducing me to embark, vertico et. al.  Keep up the good work!

@theophilusx  You can probably still use straight if you with rational, I tried to keep it at least "friendly" to the concept. In your early-config.el you'll need to turn off package-enable-at-startup and provide the bootstrap code for straight. You can then either advise or redefine the rational-package-install-package macro to use straight-use-package.
That being said, thanks for your kind words! The best thing about Emacs is you can choose your own way to make things work best for you! Thanks for participating with us here, we hope to see you back from time to time... until then - all the best!

For those who are interested, please see the recent additional of an example configuration to use straight.el instead of package.el. It is in the examples/straight/ folder.
cc: @theophilusx


Cancel tooltip when mouse leaves viewport

Fixes #48634
Supersedes #49015
The issue is not so much about focus, but the fact that the tooltip will still appear when cursor moves out of viewport or even when another window appears on top. Example:
https://github.com/godotengine/godot/assets/2223172/f44b7448-f12d-4565-bca6-01dcfef12bc6
This PR fixes it.

Thanks!

Cherry-picked for 4.0.4.


Update wiringMotors.md file in docs directory

This file contains outdated material and a picture of the old Hexbot robot rather than the new HexaFloorRide robot. All of this needs re-working but we must wait on the circuit design to proceed here.

Just realized that this task is NOT blocked by the PCB design because the wires go to the motor controllers. The purpose of this diagram is to ensure all robots use the same ports to control the same joints on the same leg. An old design exists but a new one is needed to reflect the updated robot.


[21pt] Change hand output files CRS before handing to HydroVIS

There are a number of potental  things we can do to make HydroVIS processes easier, quicker, less memory intensitive and cheaper.

HydroVIS has a significant inefficiency that they can not easily compensate for and would be easier for FIM dev to do it.

Currently, HydroVIS has to load the REMs directly from S3 as they can not be stored into the PostGres database.  They load the catchments at the same time from S3, and use both files against incoming forecast data to inundate and create the vectors. In that process they have to reproject everything to EPSG:3857 to match NWM forecast data.
On the hand side, we certainly want to keep processing as 5070 for CONUS AND 3338 for Alaska, but before we turn it over to HV, reproject it all to 3857. That way they can pull from S3 and not need all of that reproject how many times per day.  It is far easier for Fim Dev to do this as a script for Prod runs as part of handing over a new HAND dataset.

There are a number of columns in various places that they drop or rename. We can help take care of that ahead of time. More details coming

Other efficiencies have been detected and details to come.

This is stuff we can look at implementing for the spring release of HydroVIS 2.1.9 (ish)

Moved to different documentation system on where enhancements for 2.1.9 that FIM can make to make HV's part easier.

closed in error


kandra: Enable per-object metrics from rabbitmq.

These default to off, because in situations with thousands of queues, consumers, and producers, they cause unreasonable overhead.  Our use case has few enough queues that we do want to be able to inspect them individually.
Enable per-object Prometheus metrics, per 1.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Great, merged, thanks @alexmv!


White bar on iPhone X with WKWebView

I'm submitting a ...  (check one with "x")
[ ] question
[x] any problem or bug report
[ ] feature request
If you choose 'problem or bug report', please select OS:  (check one with "x")
[ ] Android
[x] iOS
cordova information:  (run $> cordova plugin list)
com.googlemaps.ios 2.5.0 "Google Maps SDK for iOS"
com.napolitano.cordova.plugin.intent 0.1.3 "IntentPlugin"
com.phonegap.plugins.nativesettingsopener 1.2 "Native settings"
cordova-background-geolocation 2.8.5 "BackgroundGeolocation"
cordova-custom-config 4.0.2 "cordova-custom-config"
cordova-fabric-plugin 1.1.10 "cordova-fabric-plugin"
cordova-plugin-actionsheet 2.3.3 "ActionSheet"
cordova-plugin-app-version 0.1.9 "AppVersion"
cordova-plugin-background-fetch 5.1.1 "CDVBackgroundFetch"
cordova-plugin-camera 2.4.1 "Camera"
cordova-plugin-cocoalumberjack 0.0.4 "CocoaLumberjack"
cordova-plugin-compat 1.2.0 "Compat"
cordova-plugin-device 1.1.7 "Device"
cordova-plugin-device-orientation 1.0.7 "Device Orientation"
cordova-plugin-dialogs 1.3.4 "Notification"
cordova-plugin-disable-bitcode 1.3.2 "DisableBitcode"
cordova-plugin-email 1.1.1 "EmailComposer"
cordova-plugin-facebook4 1.9.1 "Facebook Connect"
cordova-plugin-fastrde-checkgps 0.9.9 "checkGPS"
cordova-plugin-file 4.3.3 "File"
cordova-plugin-file-transfer 1.6.3 "File Transfer"
cordova-plugin-globalization 1.0.8 "Globalization"
cordova-plugin-google-analytics 1.8.2 "Google Universal Analytics Plugin"
cordova-plugin-googlemaps 1.4.0-beta "cordova-plugin-googlemaps"
cordova-plugin-image-picker 1.1.1 "ImagePicker"
cordova-plugin-inappbrowser 1.7.1 "InAppBrowser"
cordova-plugin-insomnia 4.3.0 "Insomnia (prevent screen sleep)"
cordova-plugin-ionic-webview 1.1.16 "cordova-plugin-ionic-webview"
cordova-plugin-ios-disableshaketoedit 1.0.0 "iOS Disable Shake to Edit"
cordova-plugin-network-information 1.3.4 "Network Information"
cordova-plugin-safariviewcontroller 1.4.7 "SafariViewController"
cordova-plugin-screen-orientation 2.0.2 "Screen Orientation"
cordova-plugin-splashscreen 4.0.3 "Splashscreen"
cordova-plugin-statusbar 2.3.0 "StatusBar"
cordova-plugin-whitelist 1.3.3 "Whitelist"
cordova-plugin-x-socialsharing 5.1.8 "SocialSharing"
cordova-sqlite-ext 0.10.4 "Cordova sqlite storage plugin with extras"
cordova-universal-links-plugin 1.2.1 "Universal Links Plugin"
es6-promise-plugin 4.1.0 "Promise"
ionic-plugin-keyboard 2.2.1 "Keyboard"
sqli-cordova-disk-space-plugin 1.0.0 "DiskSpacePlugin"
uk.co.workingedge.phonegap.plugin.launchnavigator 3.2.2 "Launch Navigator"

If you use @ionic-native/google-maps, please tell the package.json (only @ionic-native/core and @ionic-native/google-maps are fine mostly)
Current behavior:
White, 44px bar at top of map on iPhone X.
Expected behavior:
No white bar.
Screen capture or video record:

Forgot to mention that this is with a much older version of the plugin.

Wow, cordova-plugin-googlemaps 1.4.0-beta is too old for me. No more support that version.

If you will update to the current version, I will help you.

By the way, thank you for your donation!

I guess the reason of staying on v1.4 is the kmlOverlay?

We've made our own changes in a fork to allow encrypted polylines, so we cannot update at this time.  Any suggestions for how I can go about debugging this?

Could you tell me the link of the folk repo?

The plugin shift down 20px (or 40px... etc, I forgot) when your app has the status bar.
I removed the code from the multiple_maps branch version(next release), because the plugin tests other plugins before handing the touch event for this plugin, so (I guess) you don't face this issue anymore.
But you stay on the v1.4, you need to handle it by yourself.
I will find the code in your forked repo if you tell me the link.

Thanks.

It seems the v1.4 does not shift down.
But I found a PR to fix this issue.
Try this PR.
https://github.com/mapsplugin/cordova-plugin-googlemaps/pull/1630/files

Did you solve your issue?

That didn't work, I'm still looking into it.  I'll post back here if I figure something out.  Thanks for the help.

How about this?
https://github.com/mapsplugin/cordova-plugin-googlemaps/blob/c5b156ab00bde96d7da3a3b740fece70c91341e1/src/ios/GoogleMaps/MyPluginLayer.m#L327-L332

I was wondering about that, but it seems like clicks are working fine.
Some more information...
It isn't limited to just iPhone X.  It seems to be effecting all sizes of phones.  But the height of the white bar is maybe about the height of the status bar?

It appears the map is just too low.  If you look at this screen shot above, you can just barely see the Google logo in the bottom left for the licensing stuff.  And then the first screenshot of the iPhone X above, you can't even see the Google logo.  So I think it is just drawing too low.  I don't know enough objective C to figure out where that happens, but I'm working through the code now.  Maybe the container view is in the wrong place or something.

I guess the reason is the status bar shift down the wkwebview itself.
https://github.com/apache/cordova-plugin-statusbar/blob/e41c06334e3b2fe5bd7b780f1d03a47bdd242147/src/ios/CDVStatusBar.m#L481-L498

Some how the bounds for PluginScrollView is getting an origin of 0,20 (for most iPhones), and 0,40 (for iPhone X).  Resetting the bounds origin seems to solve the problem.  Going to test more to make sure it doesn't reset itself while using the app.
Any idea why it might be getting set to the height of the scrollbar?
Going to close this because it doesn't apply to the current version and I found the problem.

Hey Bentomas,
How do you reset the bounds origin?
https://bitbucket.org/piyashrija/googlemapcordova
Thanks
Shrijan


feat: Add binaries to release build

This builds Linux static binary and Mac OS binary for x86_64 architectures.

Why is ic-ref worklow failing? This PR didn't touch it


wave fetch server downloads linux rather darwin in Mac M1

Here is my M1 Mac log
sai@mbp21 doc-checker % ./venv/bin/wave fetch
Fetching examples and related files. Please wait...
Downloading https://github.com/h2oai/wave/releases/download/v0.20.0/wave-0.20.0-linux-amd64.tar.gz
Extracting...

All additional files downloaded and extracted successfully!
Examples and tour............. /Users/sai/projects/doc-checker/wave/examples
Demos and layout samples...... /Users/sai/projects/doc-checker/wave/demo
Automated test harness........ /Users/sai/projects/doc-checker/wave/test
Wave daemon for deployments... /Users/sai/projects/doc-checker/wave

Please let me know if you need any other log.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8000 (Press CTRL+C to quit)
INFO:     Started reloader process [79290] using statreload
INFO:     Started server process [79307]
INFO:     Waiting for application startup.
ERROR:    Traceback (most recent call last):
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpx/_exceptions.py", line 326, in map_exceptions
    yield
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1502, in _send_single_request
    (status_code, headers, stream, ext,) = await transport.arequest(
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpcore/_async/connection_pool.py", line 218, in arequest
    response = await connection.arequest(
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpcore/_async/connection.py", line 93, in arequest
    self.socket = await self._open_socket(timeout)
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpcore/_async/connection.py", line 119, in _open_socket
    return await self.backend.open_tcp_stream(
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpcore/_backends/auto.py", line 44, in open_tcp_stream
    return await self.backend.open_tcp_stream(
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpcore/_backends/asyncio.py", line 270, in open_tcp_stream
    return SocketStream(
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/contextlib.py", line 137, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpcore/_exceptions.py", line 12, in map_exceptions
    raise to_exc(exc) from None
httpcore.ConnectError: [Errno 61] Connect call failed ('<IP_ADDRESS>', 10101)

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

Traceback (most recent call last):
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/starlette/routing.py", line 526, in lifespan
    async for item in self.lifespan_context(app):
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/starlette/routing.py", line 467, in default_lifespan
    await self.startup()
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/starlette/routing.py", line 502, in startup
    await handler()
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/h2o_wave/server.py", line 242, in _register
    await self._wave.call(
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/h2o_wave/server.py", line 199, in call
    return await self._http.post(
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1633, in post
    return await self.request(
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1371, in request
    response = await self.send(
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1406, in send
    response = await self._send_handling_auth(
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1444, in _send_handling_auth
    response = await self._send_handling_redirects(
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1476, in _send_handling_redirects
    response = await self._send_single_request(request, timeout)
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpx/_client.py", line 1502, in _send_single_request
    (status_code, headers, stream, ext,) = await transport.arequest(
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/contextlib.py", line 137, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/Users/sai/.pyenv/versions/3.9.10/lib/python3.9/site-packages/httpx/_exceptions.py", line 343, in map_exceptions
    raise mapped_exc(message, **kwargs) from exc  # type: ignore
httpx.ConnectError: [Errno 61] Connect call failed ('<IP_ADDRESS>', 10101)

ERROR:    Application startup failed. Exiting.

Hi @lo5 , Yes I did holler without deep-diving into wave fetch 🙏🏽  - my bad.
v0.20 is awesome and with some quick dabble, I do like the ui.header_card and wave-cli 💯


Remove sh from shell code blocks.

See #273.  This makes these code blocks copy-pasteable.

I think you should add a $ prompt at the beginning of each command, and leave it using the sh language hint: https://developers.cloudflare.com/workers/docs-engine/docs-flavored-markdown#terminals .

Ahh, that makes more sense, done!

@greg-mckeon — we've migrated repos, would you mind reopning your PR here https://github.com/cloudflare/cloudflare-docs/pulls? 🙏


NodeJS/Vite usage issues

It seems like trying to import the package in nodejs when building with vite is currently not possible / has issues
Running the project in node results in a throw on import in the SDK
file:///C:/dev/project/node_modules/@sundaeswap/core/dist/esm/DatumBuilders/DatumBuilder.Lucid.V3.class.js:1
import { sqrt } from "@sundaeswap/bigint-math";
         ^^^^
SyntaxError: Named export 'sqrt' not found. The requested module '@sundaeswap/bigint-math' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from '@sundaeswap/bigint-math';
const { sqrt } = pkg;

removing
  "exports": {
    ".": {
      "import": "./dist/esm/index.js",
      "require": "./dist/cjs/index.js",
      "types": "./dist/types/index.d.ts"
    }
  },

from all the sub-dependencies, so bigint-math, asset, cpp, and fraction seemed to fix the issue
It also seems like there's no way to use the SDK since on init, it tries to use a wallet through window[walletName], which is not present on nodeJS.

This SDK is meant to be used in browser clients, since it builds the transaction using a user's wallet. Though NodeJS support wasn't on the roadmap, I think there is a solid case for doing so. Closing this for now, but will make a note to add support for backend environments later.


Add unit test for WebAssets class

Follow up to #404.
Add missing unit test for WebAssets class

Communicating with text can be challenging, but thank you for your patience in adding this!

No problem. Thanks for the merge 🙏🏿


[AVM Module Issue]: hibernation_enabled in additional_capabilities missing

Check for previous/existing GitHub issues

[x] I have checked for previous/existing GitHub issues

Issue Type?
I'm not sure
(Optional) Module Version
No response
(Optional) Correlation Id
No response
Description
Since the azurerm provider (since version v3.103.0) hibernation_enabled supports, I think this should also be integrated here, as we should stay as close as possible to the functions of the original azurerm provider.

If you want, I can create a pull request for this, but I think the change is trivial.

Adding this to release 0.17


Update the README in YarpRobotLoggerDevice

Since this logging device is widely used in the lab, I think we should keep the readme up to date. This PR updates the readme and explains how to log exogenous signal data.
Moreover, it closes https://github.com/ami-iit/bipedal-locomotion-framework/issues/527
cc @G-Cervettini @traversaro @nicktrem @davidegorbani

Failure of the CI tracked in https://github.com/ami-iit/bipedal-locomotion-framework/issues/780


get_exename() for OpenBSD.

Issue
get_exename() gets the pathname of the current process.  In femtolisp, this is used to set the top-level *install-dir* which in turn is used as the location of the system image, flisp.boot.
There is only a trivial implementation of get_exename() for OpenBSD that simply returns NULL.  A minor consequence is that the unit test will fail for the default build (make) because the system image cannot be found.
Fix
This commit provides an implementation of get_exename() for OpenBSD, so that the system image can be found.
Unlike, say, Linux or FreeBSD, OpenBSD doesn't have a system call to get the path of the current (or any, for that matter) process.  The present code contains some logic that was put together to emulate the behavior of the Linux and FreeBSD variants of get_exename() as best as possible.  It works as described by the following.
(1) Call sysctl(3) (with CTL_KERN -> KERN_PROC_ARGS -> KERN_PROC_ARGV) to get the "argv[0]" of the current process.  If the program (flisp) was called in "basename form" (i.e. as "flisp"), then go to (2).  Otherwise, return the value from sysctl(3) which will be an absolute or relative pathname, e.g. "/usr/local/bin/flisp" or  "../flisp".
The code for (1) was adapted from old OpenBSD-specific tmux code that has since been abandoned by the author only because he deemed it "too expensive".  For that code, see
http://sourceforge.net/p/tmux/tmux-code/ci/8c259f562be24570a19fd94b223034ae8c6e4277/tree/osdep-openbsd.c
(2) Since we now only have "flisp", we need to find out where it is located on the system.  We assume that a program like the shell had to crawl PATH to find "flisp"; hence we do the same.
The code for (2) was adapted from the which utility in OpenBSD.  See
http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/usr.bin/which/which.c?rev=1.20&content-type=text/plain
Finally, any error condition returns NULL, which is the same behavior of the other get_exename() variants.

I thought of another thing.  The whole idea for this commit is to make the behavior of get_exename() in OpenBSD be like that of Linux or of FreeBSD.  But here is a difference between, say, FreeBSD and OpenBSD with this commit implemented. (I elided the banners).
$ uname -rsm
FreeBSD 9.3-RELEASE-p2 amd64
$ ./flisp
> *install-dir*
"/home/rick/dev/femtolisp"

$ uname -rsm
OpenBSD 5.6 amd64
$ ./flisp
> *install-dir*
"."

This works for finding flisp.boot in the build case, but I'm now wondering if on OpenBSD the value of *install-dir* shouldn't be "/home/rick/dev/femtolisp" instead. (That's in fact the absolute pathname of "." on my OpenBSD box too.)
Whether this should be the case (i.e. *install-dir* should always be an absolute (full) pathname) is probably dependent on what other purpose you would use the value of get_exename() for.  One thing that comes to mind is that the absolute pathname might be needed if we were to install femtolisp under, say, /usr/local.  Just a thought.
What do you think?  Am I over-thinking this?  Thanks!

Thanks, this is much appreciated!
I think install-dir should be an absolute path; it should still be possible to use it to find flisp's files if the current directory changes at run time.

Oh, yes, you are right.  So, I should put in more logic to resolve the relative pathnames to absolute.
Now, comes my lack of github etiquette/protocol: should I add another commit (the new change) on top of this one, or ditch this commit and resubmit a new commit/issue, being the combination of what I have now plus the new stuff coming (as if I'd known all along what I was doing :)?  I suppose, in the end, it's not a big deal, but I thought I'd ask.  Thanks, Jeff!

Typically I'd force push to the same branch (then github will update the PR automatically), and squash commits if there are lots of them. With just 2 commits I'd say squashing is optional.

OK, Jeff, you should see the second commit now.  I added a call to realpath() to resolve the relative pathnames.  Also, I rearranged the conditional logic slightly to catch a corner case I missed before.  I originally assumed that looking down $PATH we'd only be encountering absolute directory pathnames -- I forgot you could put things like . in PATH (mostly because I don't :) -- so now when it searches down $PATH, after it finds the directory (location), it will still check for a relative pathname to resolve.
Sorry for the delay finishing this.

Here are some tests (some of which may be overkill, but hey, Overkill's my middle name).  I start the whole thing with a clone from scratch.  (I omit some output for brevity's sake.)
~/dev $ uname -rsm
OpenBSD 5.6 amd64
~/dev $ git clone https://github.com/cryptorick/femtolisp.git flisp-test
~/dev $ cd flisp-test
~/dev/flisp-test $ git checkout openbsd-get-exename
~/dev/flisp-test $ gmake
gcc -O2 -DNDEBUG -falign-functions -Wall -Wno-strict-aliasing -Illt  -DUSE_COMPUTED_GOTO -c flisp.c -o flisp.o
gcc -O2 -DNDEBUG -falign-functions -Wall -Wno-strict-aliasing -Illt  -DUSE_COMPUTED_GOTO -c builtins.c -o builtins.o
gcc -O2 -DNDEBUG -falign-functions -Wall -Wno-strict-aliasing -Illt  -DUSE_COMPUTED_GOTO -c string.c -o string.o
    .
    .
    .
cd tests && ../flisp unittest.lsp
all tests pass
~/dev/flisp-test $ # ^^ Note "all tests pass"; before: "fatal error:"
~/dev/flisp-test $ #
~/dev/flisp-test $ # Test 1: Call flisp here
~/dev/flisp-test $ #
~/dev/flisp-test $ ./flisp
> *install-dir*
"/home/rick/dev/flisp-test"
> ^D
~/dev/flisp-test $ #
~/dev/flisp-test $ # Test 2: Call flisp via PATH with `.` on PATH
~/dev/flisp-test $ #
~/dev/flisp-test $ echo $PATH
/home/rick/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/games:.
~/dev/flisp-test $ flisp
> *install-dir*
"/home/rick/dev/flisp-test"
> ^D
~/dev/flisp-test $ #
~/dev/flisp-test $ # Test 3: Call flisp via PATH with absolute directory pathname
~/dev/flisp-test $ #
~/dev/flisp-test $ PATH=$PATH:~/dev/flisp-test
~/dev/flisp-test $ echo $PATH
/home/rick/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/games:.:/home/rick/dev/flisp-test
~/dev/flisp-test $ cd
~ $ flisp
> *install-dir*
"/home/rick/dev/flisp-test"
> ^D
~ $ #
~ $ # Test 4: Call flisp with (other) relative pathname
~ $ #
~ $ dev/flisp-test/flisp
> *install-dir*
"/home/rick/dev/flisp-test"
> ^D
~ $ #
~ $ # Test 5: Call flisp with absolute pathname
~ $ #
~ $ /home/rick/dev/flisp-test/flisp
> *install-dir*
"/home/rick/dev/flisp-test"
> ^D


Function calling (using food-search.ts)

I'm submitting a ...
[ x] bug report
Summary
I'm getting errors with:
Anthropic
@ax-llm/ax/build/module/src/util/apicall.js:39
        throw new Error(`API Error: ${apiUrl.href}, ${e}`);
              ^

Error: API Error: https://api.anthropic.com/v1/messages, Error: API Error: https://api.anthropic.com/v1/messages, 400, Bad Request
{
  "type": "error",
  "error": {
    "type": "invalid_request_error",
    "message": "Your API request included an `assistant` message in the final position, which would pre-fill the `assistant` response. When using tools, pre-filling the `assistant` response is not supported."
  }
}

Also:

Anthropic just released "claude-3-5-sonnet-20240620" 🎉

Groq
@ax-llm/ax/build/module/src/ai/openai/api.js:166
        ({ delta: { content, role, tool_calls }, finish_reason }) => {
                    ^

TypeError: Cannot read properties of undefined (reading 'content')

Also:

ai/groq/index.ts is missing "export * from './types.js';"
is 'AxAxGroqArgs' a typo?

Cohere

@ax-llm/ax/build/module/src/util/apicall.js:39
        throw new Error(`API Error: ${apiUrl.href}, ${e}`);
              ^

Error: API Error: https://api.cohere.ai/v1/generate, Error: API Error: https://api.cohere.ai/v1/generate, 400, Bad Request
{
  "message": "invalid request: prompt must be at least 1 token long."
}

Google

@ax-llm/ax/build/module/src/util/apicall.js:39
        throw new Error(`API Error: ${apiUrl.href}, ${e}`);
              ^

Error: API Error: https://generativelanguage.googleapis.com/v1beta/models/gemini-1.5-pro:streamGenerateContent?alt=sse&key=, Error: API Error: https://generativelanguage.googleapis.com/v1beta/models/gemini-1.5-pro:streamGenerateContent?alt=sse&key=, 400, Bad Request
{
  "error": {
    "code": 400,
    "message": "Invalid JSON payload received. Unknown name \"default\" at 'tools[0].function_declarations[0].parameters.properties[1].value': Cannot find field.\nInvalid JSON payload received. Unknown name \"default\" at 'tools[0].function_declarations[1].parameters.properties[1].value': Cannot find field.",
    "status": "INVALID_ARGUMENT",
    "details": [
      {
        "@type": "type.googleapis.com/google.rpc.BadRequest",
        "fieldViolations": [
          {
            "field": "tools[0].function_declarations[0].parameters.properties[1].value",
            "description": "Invalid JSON payload received. Unknown name \"default\" at 'tools[0].function_declarations[0].parameters.properties[1].value': Cannot find field."
          },
          {
            "field": "tools[0].function_declarations[1].parameters.properties[1].value",
            "description": "Invalid JSON payload received. Unknown name \"default\" at 'tools[0].function_declarations[1].parameters.properties[1].value': Cannot find field."
          }
        ]
      }
    ]
  }
}

Other observations:

DeepSeek worked quite well, except when I changed "sushi" to "sashimi", then it failed... But it's a coding model, not a foodie.
None of the Together function calling models worked (they're either confused or hallucinating):
mistralai/Mixtral-8x7B-Instruct-v0.1
mistralai/Mistral-7B-Instruct-v0.1
togethercomputer/CodeLlama-34b-Instruct

will take a look

can you confirm you're testing with the latest version we fixed a bunch of stuff today and also added the new 3.5 sonnet model.

@dosco Anthropic and Groq still throwing the same errors. I'm having different issues with Cohere and Google, but I need to double check that I'm not missing something.
I like the new AxAI syntax, easier to follow!

great will take a look and fix this today. thanks as the api was growing the proper prefix helps with autocomplete etc

latest release https://github.com/ax-llm/ax/releases/tag/9.0.9 has fixes for anthropic, cohere, gemini, i'm looking into groq but i suspect its more a model issue there i might bump up the default model choice to a bigger model

@dosco Cool, I'll check it out! Regarding Groq, one thing to keep in mind - they limit llama3-70b to 6k tokens/min and llama3-8b to 30k t/m. I found myself hitting the limit with the larger model quite often, within one run.

probably need to add a rate limiter we support those in the library maybe groq needs one by default

in the latest release i added a default token bucket bases rate limiter to groq by default to slow it down when needed.


Add the ability to set the build directory

The "findLatesBuild" function does currently only account for projects with a build folder named "out". It would be nice to have a parameter to change this directory (e.g. "build")

#3

@as71xoho Thanks for your help with the PR seems like @jjeff  is going to help here.

closed with #3


Update visualisation

Looks great! the graphs in the docs an manual do seem quite large on my end? If that's quick to fix then that could be nice, but if not then I think it's good to go as it is.

I spent a while flitting around with sizes and they seemed to compress badly for smaller sizes and look worse, I think partially because they're vertical now.
It's not a quick change as I'd have to manually resize everything (though I have a branch with them all stored) so I'm going to suggest we leave them for now, prioritise the release and then attempt a more aesthetic redo later.


Add new rebus

Associated Issue: #121
Summary of Changes

Add a new rebus

Pull Request Test Coverage Report for Build 614

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

Totals

Change from base Build 514:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls


wishlist: add search option to the "global settings" screen

The subject says pretty much everything: since there are so many global options it would be nice to have

a smaller font size used for showing such options, so that we don't need to scroll continuosly
have a search box that shows you only options relevant with your search

Closing since this now exists in the current version.


Add expungement clinic info to our website

From Noella:

I think we should definitely include some information about the U of U’s monthly expungement clinic:
Expungement Free Legal Clinic
Area of Law: Impediments to employment, such as expungements and addressing issues regarding outstanding warrants.
When: 1st Thursday of every month. Closed July 5.
Time: 5 pm – 6:00 pm (Please plan to arrive no later than 6 pm otherwise you will have to wait until the following month).
Location: LDS Employment Center. 780 West 800 South in Salt Lake City.
Sponsored by: S.J. Quinney College of Law and Utah Legal Services.

I created another overview landing 7 in en.js and rendered it in landing.component.js. I was wondering though do we want to include a link to the event? If so this is the only url I could find that references the event, the problem being it also references other free legal clinics.  I didn't know if it would be to confusing for a user.
I was just wondering if I could get your opinion on the url, ie if I should include the link or not.
url:
https://law.utah.edu/pro-bono-initiative/free-legal-clinics/
Thanks!

Resolved in https://github.com/JustUtahCoders/utahexpungements.org/pull/91


Improve masking

Codecov Report

Merging #42 (11cd36a) into master (f6fbab3) will decrease coverage by 0.15%.
The diff coverage is 80.85%.

@@            Coverage Diff             @@
##           master      #42      +/-   ##
==========================================
- Coverage   92.83%   92.68%   -0.16%
==========================================
  Files          94       94
  Lines        2988     3021      +33
==========================================
+ Hits         2774     2800      +26
- Misses        214      221       +7

Flag
Coverage Δ

unittests
92.68% <80.85%> (-0.16%)
:arrow_down:

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

Impacted Files
Coverage Δ

xfuse/convert/st.py
72.54% <60.00%> (-1.92%)
:arrow_down:

xfuse/__main__.py
92.76% <73.33%> (-1.44%)
:arrow_down:

xfuse/convert/visium.py
92.85% <80.00%> (-7.15%)
:arrow_down:

xfuse/convert/utility.py
89.81% <100.00%> (+0.92%)
:arrow_up:

xfuse/utility/mask.py
92.15% <100.00%> (+0.66%)
:arrow_up:

xfuse/messengers/stats/writer/tensorboard.py
100.00% <0.00%> (+3.70%)
:arrow_up:

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 f6fbab3...11cd36a. Read the comment docs.


[Hub Generated] Review request for Microsoft.Security to add version preview/2021-08-01-preview

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

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

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the 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
[x] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] 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

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[x] 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 any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a 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.

Please let me know any remaining items needed to merge in this documentation change.

Dealt with merge conflict.

@ruowan I noticed this PR has label 'WaitForARMFeedback' but got merged without ARM sign off. Is this intentional? I am wondering if any of the merge checks break.
I reviewed the PR just now and it looks good to me.


Modified for the feedback

…'cp-starter-ibpm-employeeonboarding-2-businessrules', 'cp-starter-ibpm-employeeonboarding-3-workflow', 'cp-starter-ibpm-employeeonboarding-4-visibility', 'cp-starter-ibpm-employeeonboarding-5-run' from QA to Production

I have significantly updated the setup guide and other tutorials to make it shorter and easier and I will bring the needed changes of description with those commits. Else I have to revert the changes done and bring this one change. If you could accept these changes for now, and very soon next week I will send new set of changes.


Add Pydantic smart union test for Hera runner output serialization

Pull Request Checklist

[ ] Fixes #
[x] Tests added
[ ] Documentation/examples added
[x] Good commit messages and/or PR title

Description of PR
@lancour discovered that typing a field as a union such as str | int | float + using the Hera runner results in int + float being serialized as str. This is likely caused by the way serialization occurs during runner validation here. My guess is that it happens somewhere around https://github.com/argoproj-labs/hera/blob/main/src/hera/workflows/runner.py#L234
This PR only adds a failing test to illustrate how an expected integer is actually a string, hence it fails. Still working through the code

I would say this is WAD/the issue stems from Pydantic - the order of the Union types dictates how the class is serialised. The basic idea is that the stricter types should come first, as it will be the first type can coerce the value that is used. Or, you can set the config to use smart_union - this is  explained here in pydantic 1.10. Not sure about 2.0+
Therefore it's a user issue to set their types correctly - I'm happy to add the test as an example and use the smart_union config to get it to pass?

@elliotgunton if you have a chance and want to approve I think this is ready to ship


target avalonia 0.9.5

not sure I understand why the PR was closed?

not sure I understand why the PR was closed?

It's targeting master and master is not mergable for service releases of Avalonia. I have to create release branch based on latest release branch.
https://github.com/wieslawsoltes/AvaloniaBehaviors/tree/release/0.9.5

@FoggyFinder @danwalmsley
So in order to update from Avalonia 0.9.4 to 0.9.5 you need to create branch release/0.9.5 from release/0.9.4 and than push necessary changes to release/0.9.5 branch. The master is tracking nightly build and those build have breaking changes so we have to base the service releases on release/* branches.

Also master is tracking 0.9.999-cibuild* nightly builds.


chore: pivot mermaid classDiagram to flowchart

This PR brings changes to generate mermaid flowchart syntax rather than mermaid class Diagrams syntax.
Reference: https://github.com/asyncapi/app-relations-discovery/pull/10#issuecomment-861259951
Have a look at mermaid flowchart here.

@alnacle look what we are using your Flight Status example for 😄
@arjungarg07 all good, ready to accept, but just one question. I think you made some changes to flight status example and it is hard for to check if the chart is correct or not. I look at https://github.com/amadeus4dev/amadeus-async-flight-status/blob/main/notifier/asyncapi.yaml that has just one channel flight/update of publish operation. This means the Notifier service is subscribed to flight/update and the arrow should point to the service and not the server. It should be server1 -- flight/update --> FlightNotifierService. I'm also not sure where flight/queue on the same service is coming from

@derberg Yeah! For testing how it would look for multiple servers I made some changes, sorry for that confusion.
This is the relations diagram of the original service: FlightService Flowchart

no worries.
so the arrow that now points from Flight Notifier Service to the server, should point the other way around, from server to service. This means that the service is actually subscribed to the channel on the broker, so it is consuming, not producing messages.
Have a look at this article for more details

This means that the service is actually subscribed to the channel on the broker, so it is consuming, not producing messages.

Ooh! I see, then that would also change meaning under subscribe: and the correct relations would be like this.
Thanks for sharing the article.

yup, subscribe means that service is actually publishing to a given channel, so arrow goes to the server

Pushed the changes. Ready to merge 🚀

and yes, now your diagram is perfect and match the diagram from the article https://www.asyncapi.com/blog/building-async-flight-notification-service

@magicmatatjahu I know that in one of the PRs you had different opinions, but the thing is we are not on a major release and we do not need to be strict and I think it would be great to publish these as feat and fix to release and as a result notify on slack and twitter so others can see progress, how quickly it happens and jump in to comment and give feedback.
Thoughts?

@arjungarg07 @derberg No worries 😅 I had different opinion, because we hadn't anything to publish, now we have. But if we want to publish package we should write at least some little documentation in the Readme.md like

what is it - we had it, but we can make the introduction like in other repos -> https://raw.githubusercontent.com/asyncapi/asyncapi-react/master/README.md I mean only logo and centered package name
how to install it
how to use it

And for the third point, we should change this line
https://github.com/asyncapi/app-relations-discovery/blob/master/lib/index.js#L3
to:
module.exports = {
  getRelations: appRelationsDiscovery,
};

And also sorry for confusing about connections/arrows for subscriptions. Probably I still understand it wrong 😅

@arjungarg07 can you add these simple docs to readme in this PR please? simple npm install and how to use API atm

And for the third point, we should change this line
https://github.com/asyncapi/app-relations-discovery/blob/master/lib/index.js#L3

@magicmatatjahu I don't get it, why do we have to change it to this 🤔
Since API use(currently) is like this:
const output = appRelationsDiscovery.getRelations(...docs);  // for default syntax
const output = appRelationsDiscovery.getRelations(...docs,{syntax:'mermaid'}); // for mermaid flowchart

After your suggestion APIs would be like:
const output = getRelations.getRelations(...docs);  // for default syntax
const output = getRelations.getRelations(...docs,{syntax:'mermaid'}); // for mermaid flowchart

So why to export appRelationsDiscovery as getRelations?

Sorry :P I didn't check that appRelationsDiscovery returns the object with function. It can stay as it is :)

@derberg Shall we change the title now? Also I don't have the merge permission 😅


Advice on how to properly construct a workflow that is inherently recursive

I am responsible for running and maintaining the Conductor instances in my organization. I have had a few teams in my organization that have created 'recursive' workflows that have caused major issues for Conductor. They have workflows that do things like check a status in their database and if the status is not what they want then their workflow calls itself as a subworkflow and so on and so on until the status is what they want.
This causes StackOverflow errors when Conductor is 'deciding' the lowest level subworkflow because it has to walk the parent chain and there could be over a hundred levels of parent/child from bottom to top. It also adds a workflow to the _deciderQueue of Postgres every time so Conductor has to 'decide' on every one of the subworkflows as well as the original workflow itself. Eventually this _deciderQueue gets really large if they have a lot of workflows because each workflow could live for months.
Given this problem domain, one of the solutions we have come up with is to spawn a fresh workflow with the same correlation id and look up all the workflows with the same correlation id to diagnose what is going on with the one logical workflow. This is not palatable to one of the teams as they want a tree of workflows to traverse from top to bottom to see the history. It also does not solve the problem of the _deciderQueue growing to an unmanageable size.
In some business problems, we can use a workflow that uses a WAIT task and have an external service that checks the database status and COMPLETEs the WAIT task when the status is right. Unfortunately that doesn't solve other similar but not so simple situations.
Has anyone tackled a similar problem and come up with a good template solution?
BTW, one of the teams mentioned used a DO_WHILE task for this purpose about a year ago and had so many problems with it that they don't want to go down that path...

I see two separate problems listed here. We are aware of the bottlenecks that a large _deciderQueue could cause. We are exploring ways to split the queue and also options to scale up processing corresponding to _deciderQueue depth. These improvements are expected in Q3.2021.
Lately, we have seen problems with Subworkflows inside a FORK_JOIN, which led us to reevaluate how child workflows interact with the parent workflow. We are looking to move away from subworkflows traveling up the graph and deciding the parent.  We are planning to make the 'decide' process asynchronous where the sub workflow only updates the subworkflow task in the parent, but does NOT call decide on it. The parent workflow will be decided when the sweeper picks it up. This should avoid the Stackoverflow errors that can happen with recursion. This is in active development and will be released in Q1.2021.
Also, we are curious to know what problems that your team ran into with DO_WHILE task?

I have had a few teams in my organization that have created 'recursive' workflows that have caused major issues for Conductor. They have workflows that do things like check a status in their database and if the status is not what they want then their workflow calls itself as a subworkflow and so on and so on until the status is what they want

This is a rather strange implementation.  Have you considered using the callbackAfterSeconds mechanism instead? In this case, the worker would return the task as IN_PROGRESS with a desirable value for callbackAfterSeconds in the TaskResult object till the status in the db is not as expected for the task to be COMPLETED. This would mean that the same task instance is reused by the worker. The callbackAfterSeconds duration means that this particular task instance will be made invisible by the conductor server for this duration and be made available to be polled and executed after. This is quite a common use-case in our system and has been employed in a large number of long-running workflows by our users. This section in the documentation expands on this to some extent.

tree of workflows to traverse from top to bottom to see the history

As part of the above mechanism, the worker could choose to add a TaskExecutionLog to the TaskResult upon every poll/process, thereby maintaining a history of executions.

Thanks for the additional context, for this use-case a DO_WHILE does look to be a better fit. Alternatively depending on the nature of the logical decision (whether it could be modeled as an independent subworkflow), you could use trigger a new workflow in every iteration which operates independently in a fire-and-forget manner.

Hi,
Below is my understanding of the usecase.
Trigger Workflow 'Perform HC'

Start
Check Status
2.1) If Status is Green --> Terminate with Status COMPLETED or just Stop (as in let the workflow end)
2.2) If Status is Amber (as in not Green) --> Repeat

Instead of using a SUB_WORKFLOW, it can be replaced with a HTTP Task that would POST a request to run 'Perform HC'.
Something like below
Trigger Workflow 'Perform HC'

Start
Check Status
2.1) If Status is Green --> Terminate with status COMPLETED or just Stop (as in let the workflow end)
2.2) If Status is Amber (as in not Green) --> HTTP Task (call Trigger Workflow 'Perform HC') --> Terminate (With status FAILED)

And while checking if the HC was successful, a GET request to the API with a correlationId as search parameter can give the latest status.
This way a workflow's latest run always has the current status which can simply be determined by the workflow latest execution instance status itself.
--> COMPLETED would mean the HC was successful
--> FAILED would mean the latest check was unsuccessful
--> IN_PROGRESS would mean , the check is in progress as the previous run FAILED.
Though it might increase the number of workflow executions, I think this would avoid the StackOverFlow error or anything similar.
Thanks and Regards,
Mahesh Yaddanapudi.

Thanks. This is a good solution, very similar to using EVENT tasks to start the secondary workflow. We will look into this.


Can't open another pages in kitchen sink when framework7-vue is updated to version 0.9.0

Excuse me, @bencompton . Finally I can know what's actually changed between framework7-vue v0.8.5 and v0.9.0. You can view it in this link. Variable names for handling router has been changed in pages.vue and also in framework7-vue.js, so I can just view the main page, can't open others page like chips, data table, dynamic routing, etc, when open kitchen sink. I hope that link can help you to update framework7-react package to newer version.

Thanks for all of the investigation you have done. I am hoping to have more time to get the v0.9 release  out soon.

Should be fixed now in v0.9.1.


fix: cursor should not jump when toggling remotes

Perhaps util.save_cursor_position(view), util.restore_cursor_position(view) helpers?

Ping.

Please see the comment and explanation for 6eda35a.


Update to MP 3.3 Jakarta dependencies

Fixes #137

CC @starksm64

+1

@radcortez thanks
@rdebusscher Hi, can you please check on your own end if getting it into JWT 1.2 works OK for you ? Looks like it can easily go into the next release.
CC @ederks85

Is MP-JWT 1.2 for MP 3.3 or MP 4.0? what is target date for MP 3.3 and 4.0?

@chunlongliang-ibm
MP 3.3 is already released on March 18th.

@rdebusscher I have a PR on my branch already to have el-api excluded. Thanks for the approval.
Actually I forgot to ask David, @dblevins double check please, I'll merge soon, but we can deal with any issues if any before the release

@chunlongliang-ibm yes, originally I created this PR for MP 3.3 but since MP JWT has missed it anyway, and, as I was explained by my colleagues these dependencies are backward compatible, we may just go ahead and have them done now

Going ahead with this merge now, lots of time to fix something if needed

Just updated the subject of the PR to correctly refer to MP 4.0 as I'm about to link to it from the release notes


Allow etcd hosts in some playbooks

What type of PR is this?
/kind enhancement

What this PR does / why we need it:
Allow etcd hosts in some playbooks
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

/lgtm


using random_create instead of timestamp_create

I'd prefer to use the type 4 UUID (random). Any thoughts about supporting this? I should have mentioned in the other issue that I'm happy to code up a solution for either of these if they don't fit in your roadmap.

Have you tried SecureRandom.uuid?


fix fix jni_reader function name get_nex_block to get_next_block

Proposed changes
Issue Number: close #xxx
fix jni_reader function name get_nex_block to get_next_block
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildadd

run buildall

run buildall

run buildall

run buildall


Crash on Startup "Error: java.lang.NoSuchMethodError: "

Mod Version: <IP_ADDRESS>.
Forge Version: <IP_ADDRESS>54
https://hastebin.com/riqofocame.md Client Log
https://hastebin.com/wonuvekiqa.bash Crash Log
Description:
I tried Installing dynamic surroundings the other day, with no success, I am not using a modpack but rather made one myself, or better said just downloaded a bunch of mods, and in the loading phase of minecraft after the crash the following message appears
"The game crashed whilst initializing game
Error: java.lang.NoSuchMethodError: net.minecraftforge.common.capabilities.Capability$IStorage.writeNBT(Lnet/minecraftforge/
common/capabilities/Capability;Ljava/lang/Object;Lnet/minecraft/util/EnumFacing;)Lnet/minecraft/
nbt/NBTBase;"
Description of the problem.
I recently added the mod to my collection
I experienced no prior crashes
No mods have been updated
yes sadly this is a home kitchen sink with lots of mods, and no official modpack

Try DS <IP_ADDRESS> and let me know if it works.

Try DS <IP_ADDRESS> and let me know if it works.

yes it did work, thank you :D

OK.  I suspect there is a mod in your pack that is using Mixin 0.7.11.  The <IP_ADDRESS> version of DS uses version 0.8 - the stable build for 1.12.2.


Lane2Seq Code

Thanks for sharing your new work Lane2Seq. Could you please share the expected release date for the code of this new work? Thank you!

Hi@Mollylulu, sorry for the late reply. Thanks for your interest in our work. I was busy with my ECCV paper.  The release date may be after the ECCV deadline.

Noted. Thanks for your reply and looking forward to your code :)

The implementation is similar to Pix2seq and you can refer to it.


Command 'CRS: Rename - Current File' resulted in an error (command 'crs.RenameCurrentFile' not found)

Hello,
Today some of my VS Code projects have been failing with the error mentioned in the title ("...command ... not found").  When I look at the console in VS Code, I see the following:
mainThreadExtensionService.ts:111 Activating extension 'waldo.crs-al-language-extension' failed: Cannot find module 'opn'
Require stack:

c:\Users\matt_.vscode\extensions\waldo.crs-al-language-extension-1.5.9\out\DynamicsNAV.js
c:\Users\matt_.vscode\extensions\waldo.crs-al-language-extension-1.5.9\out\CRSFunctions.js
c:\Users\matt_.vscode\extensions\waldo.crs-al-language-extension-1.5.9\out\extension.js
c:\Users\matt_\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js
c:\Users\matt_\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-amd.js
c:\Users\matt_\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-fork.js.

Is there an "opn" extension I need to install from somewhere?

I installed the previous version (I had a new one that installed 6 hours ago), and it is working again.  Perhaps an issue in the latest version?

Thanks @MBK75 for reporting this bug and sorry about the mess. What is interesting for me is the fact that there is no compilation error.
Hint for the future: the opn dependency is deprecated (https://www.npmjs.com/package/opn) and has been replaced by open (https://www.npmjs.com/package/open).

thanks for reporting indeed!
Just upgraded opn to open .. and implemented your fix as well.
All seems well again.  Can you confirm, @MBK75 ?

Thank you! I have not tried yet but will


⚠ Bofrost.be has degraded performance

In 6566e0f, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1525 ms

Resolved: Bofrost.be performance has improved in f9b4ce9 after 7 minutes.


Tuya Light without brightness throws error in the logs

Breaking Change:

Description:
Return none if there is no brightness data from tuya
Related issue (if applicable): fixes #
https://github.com/home-assistant/home-assistant/issues/25896
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

@PaulAnnekov do you have time to review?

@MartinHjelmare LGTM.
@tyjtyj so what does data dictionary contains when no brightness present?

unfortunately nothing. I just prevent it dumping error logs
{
	'data': {
		'online': True,
		'state': 'true'
	},
	'name': 'Mood Lamp',
	'icon': 'https://images.tuyaeu.com/smart/icon/xxxxxxxxxxxxxxxxxxxxxxxxxxx.png',
	'id': 'xxxxxxxxxxxxxxxxxxxxxxxxxxxx',
	'dev_type': 'light',
	'ha_type': 'light'
}

Let me know, and I'll merge.

@MartinHjelmare yep, merge it.


Clicks within iscroll on a touch laptop with the mouse

I've got a client working on a Microsoft Surface (which is detected as a touch device so I guess treated like a mobile phone or tablet).
Tapping (touch event) on the screen causes links to go to the next page, but using the trackpad or a mouse (click event) doesn't do anything.
I've tried different settings, but I can't get it to work.

Can you provide a repro?

I've made an example here:
http://prototype.dpdk.com/iscroll-test/
I've figured out the "click:true" is causing it. But without it the clicks don't work at all on any touch device.
Is there another way to get clicks (taps) te work on mobile devices?

We've implemented the tap event instead of click:true and that seems to fix the issue.
I do think it's a shame tapping isn't supported by default and needs custom implementing.

I do think it's a shame tapping isn't supported by default and needs custom implementing.

Yeah, that's quite a big bug in iScroll.js related with this issue: https://github.com/cubiq/iscroll/issues/783


Add Zitadel community package

@susanev Could you please remind me where do I need to upload an icon for my package? I did it for another package but do not remember the place where I need to put it 🤨

I mean this missing icon


optimize rendering

Put BlockGrid inside of a drawingGroup for better performance.
The same method was applied in:
WWDC 2019 Session 237 - Building Custom Views with SwiftUI

I've done that in my latest commit: https://github.com/unixzii/SwiftUI-2048/commit/11e961b7913da92d0d5acb22107dcf5e256b7ba6
Anyway, thanks for your PR!


[core] GetMouseDelta() does not work on PLATFORM_WEB running on mobile browser

GetMouseDelta() does not work with smartphone touch using PLATFORM=PLATFORM_WEB
I replaced it with a difference between the current and previous position returned by GetMousePosition()

@trikko Just reviewed the code and I can't find the issue, all looks correct to me...

I'm closing this issue as out-of-scope, too many systems involved for proper review.


Remove TheDocumentFoundation.LibreOffice.LTS

Description of the new feature/enhancement
I'm thinking about removing the TheDocumentFoundation.LibreOffice.LTS package and only keeping the non-LTS one, as the LTS one no longer makes sense:

The 7.x series got removed from the download page some hours before this post today.
The LibreOffice auto updater is now suggesting 7.x series users to update to 24.2.4, which is the current non-LTS version.

The 7.x has been EOL'd.

Also see: https://github.com/chocolatey-community/chocolatey-packages/issues/2496
Proposed technical implementation details (optional)
No response

Starting removal

https://github.com/microsoft/winget-pkgs/pull/162302
https://github.com/microsoft/winget-pkgs/pull/162301
https://github.com/microsoft/winget-pkgs/pull/162300
https://github.com/microsoft/winget-pkgs/pull/162299
https://github.com/microsoft/winget-pkgs/pull/162298
https://github.com/microsoft/winget-pkgs/pull/162297
https://github.com/microsoft/winget-pkgs/pull/162296
https://github.com/microsoft/winget-pkgs/pull/162295
https://github.com/microsoft/winget-pkgs/pull/162294
https://github.com/microsoft/winget-pkgs/pull/162293
https://github.com/microsoft/winget-pkgs/pull/162292
https://github.com/microsoft/winget-pkgs/pull/162291
https://github.com/microsoft/winget-pkgs/pull/162290
https://github.com/microsoft/winget-pkgs/pull/162289
https://github.com/microsoft/winget-pkgs/pull/162288
https://github.com/microsoft/winget-pkgs/pull/162287
https://github.com/microsoft/winget-pkgs/pull/162286
https://github.com/microsoft/winget-pkgs/pull/162285
https://github.com/microsoft/winget-pkgs/pull/162284
https://github.com/microsoft/winget-pkgs/pull/162283
https://github.com/microsoft/winget-pkgs/pull/162282
https://github.com/microsoft/winget-pkgs/pull/162281
https://github.com/microsoft/winget-pkgs/pull/162280
https://github.com/microsoft/winget-pkgs/pull/162279
https://github.com/microsoft/winget-pkgs/pull/162278
https://github.com/microsoft/winget-pkgs/pull/162277
https://github.com/microsoft/winget-pkgs/pull/162276
https://github.com/microsoft/winget-pkgs/pull/162275
https://github.com/microsoft/winget-pkgs/pull/162274

#162282

@vikingnope I think you've mentioned the wrong PR here :D

oh yep sorry

@SpecterShell, should I remove the SDK LTS as well? TheDocumentFoundation.LibreOffice.SDK.LTS

By deleting the ID "TheDocumentFoundation.LibreOffice.LTS" systems of users who use
winget upgrade TheDocumentFoundation.LibreOffice.LTS
are affected in a not expectable way, because winget is suggesting to upgrade to TheDocumentFoundation.LibreOffice (without .LTS) now.
The currently used download link for <IP_ADDRESS> is wrong.

By deleting the ID "TheDocumentFoundation.LibreOffice.LTS" systems of users who use winget upgrade TheDocumentFoundation.LibreOffice.LTS are affected in a not expectable way, because winget is suggesting to upgrade to TheDocumentFoundation.LibreOffice (without .LTS) now.
The currently used download link for <IP_ADDRESS> is wrong.

LTS is no longer supported by LibeOffice and this is why it has been removed. I will check out ythe current download link for <IP_ADDRESS>.

I think there might be an outage with their CDN

Dear all,
Until now LibreOffice was calling the versions Stable and Fresh on their website. I think to have a stable (or LTS) ID would nevertheless make sense. At times like now the latest (fresh) and stable (LTS) would be the same version. In one month when 24.8 will be released the LTS will stay on 24.2 and 24.8 would be there additionally.
What do you think?

I think there might be an outage with their CDN, there is also a new update <IP_ADDRESS> so I will add that
EDIT: It seems to be going online and offline currently

That version is actually <IP_ADDRESS> not <IP_ADDRESS>. I'm fixing it.

Dear all,
Until now LibreOffice was calling the versions Stable and Fresh on their website. I think to have a stable (or LTS) ID would nevertheless make sense. At times like now the latest (fresh) and stable (LTS) would be the same version. In one month when 24.8 will be released the LTS will stay on 24.2 and 24.8 would be there additionally.
What do you think?

It is somehow similar to NodeJS, which has a current (non-LTS) channel and active (LTS) channel, and a major version (e.g., 22.x) in the current channel may go to the active channel when the current channel is moving to the next major version (e.g., 23.x).


add OneWire into DTS

As requested, here is the W1 DTS that allows to connect devices such DS18B20 if EndUser enable it in DTS by changing "disabled" with "okay".

I keep this as PR for now as the Kernel does not have the w1 driver enabled. I might change this in the future and then merge.
If anyone wants to use W1, use the DTS changes from this PR and enable CONFIG_W1 in your Kernel build.

Hi Simon,
Do you wish that I had the config changes in this PR too ?

Thanks Martin but that's not necessary - i think everyone who needs it can figure it out.

Hi Simon,
You can see that I've done new fix unrelated with the previous, but unfortunately, when a PR is already opened, new commits are coming into the same PR since previous wasn't merged.
The description of the new fix is explain here :
http://forum.pine64.org/showthread.php?tid=1297&pid=15958#pid15958

Thanks - I cherry picked 8a0440a and you can rebase and force push to get this PR clean again. Also you can always also create another branch on top of master and submit a new PR for this branch to avoid getting things mixed up.

Rebase done !


Remove most PRM HTTP calls from declaration requests

Changes Unknown when pulling d677a1e75b8508e3b7ea1d3fc7be2b25659c0ae8 on gmile:prm-refactoring-5 into ** on edenlabllc:master**.

Changes Unknown when pulling 897e9c13c618c6ae66ce4a16f9c8fe31be386f7d on gmile:prm-refactoring-5 into ** on edenlabllc:master**.


represent lack of information similarly across schema

Currently, we are inconsistent because we capture unknown information a few different ways across the obs schema...

string unknown

development_stage
sex
self_reported_ethnicity

non-specific term from the required ontology

assay - not allowed in practice (but technically could be as broad as assay by molecule or single cell library construction)
organism - not allowed in practice (but technically could be as broad as unclassified Metazoa)
tissue - not allowed in practice (but technically could be as broad as anatomical structure)
cell_type - non-specific term from CL native cell or animal cell or eukaryotic cell

term from a different ontology than known information

disease - PATO:0000461 [normal]

Issues caused

The variability can make understanding the schema more difficult
When extending the schema, we have no single principle to align new fields with
The mix of free text strings & ontology term IDs in the *_ontology_term_id fields can make coding inconvenient (the level of inconvenience will increase as the schema expands)
The non-specific terms are confusing to users & contributors
Using non-specific terms results in inconsistent annotations across the corpus (un-annotated cells could be native or animal or eukaryotic cells) - overlaps with #380

~To be consistent, we could choose to use a non-specific term from the appropriate ontology but these labels are likely to lead to general confusion for data consumers...~ Bad idea as noted in the Issues
One option would be to conform to the disease approach of "borrowing" a term from another resource so that every value in *_ontology_term_id field is an ID in the format :

NCIT:C17998 [unknown]
NCIT:C48660 [not applicable] (suspension_type & self_reported_ethnicity currently use string na)
There is also NCIT:C14165 [normal] if that's preferable to align on NCIT

National Cancer Institute Thesaurus downloads and README.

Are there concrete cases where this has caused specific problems? I noticed some use non-ontology ID strings so could trip up computational folks.

I have run into issues writing code for Ontology UI, in particular trying to classify cells by their labels and relationships.  I ended up writing special filters to ignore the ad hoc terms.  It would have been cleaner if I could have just used standard OBO or RDF tools without these modifications.
IMHO, this isn't a huge deal, but does speak to data hygiene and setting precedents for future extensions

Per triage, @brianraymor to review further because who doesn't like "data hygiene", but my perception is that this adds little value for data consumers and requires  unwinding to re-handle cases like "unknown" vs NCIT:C17998 [unknown].

@ebezzi @nayib-jose-gloria - I'd be interested in your impressions as you become more familiar with the code base. Would any changes make it easier to validate?

@nayib-jose-gloria privately responded:

I think using 'unknown' or 'na' across the board is the most clear on our end for an engineer reading+contributing the code, but I don't think it would introduce any technical challenge to do either of the other two proposed solutions

Closing in favor of addressing the specific case #380


add a serial (Oxford) comma

On a vaguely related note, I can't figure out how/where to submit changes to these pages:

https://www.erlang.org/doc/man/xref.html
https://www.erlang.org/doc/apps/tools/xref_chapter.html

Help?

Thanks! The documentation for xref is located here. You can read about how to write and build documentation here.


Change default color

Fixes #210 by moving red down to a lower position in our default selections and moving magenta up.

Looks good. Glad we have this for better accessibility on the demo. Probably should think about something similar in vitessce, or having different color palletes.
https://github.com/hubmapconsortium/vitessce/issues/592


Rebase spark3.3 onto master

Related Issues/PRs

#xxx
What changes are proposed in this pull request?
Rebase the spark3.3 branch onto master
How is this patch tested?

[ ] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[ ] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[ ] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

Did this already!


Question: What is the release schedule of the project?

The title pretty much says it all. What is the release schedule or logic for when to release a new version for this project?

There isn't a hard release schedule. After #80 is merged, I plan on publishing v1.9.0.

v1.9.0 is live on PyPI!

Thank you! By the way, if you're ever interested in automating your versioning, I would suggest using bumpr (https://github.com/haya14busa/action-bumpr) to automate version tagging with simple labels on PRs. In my experience, it is one line in the CI files to implement it. The hard part would be getting your PyPI publishing action to also trigger automatically after the new version is tagged. I don't have experience with that part, but I have seen it done before!


[NRCE] 4-Rocker Node API

the 4-Rocker Node is just a convenient node to send button press command.

without the 4-rocker node, you can achieve the same effect by sending an array of JSON objects accepted by the output node, through a split node

switch on a light would the look like this:
[
    {
        "meta": {
            "eep": "f6-03-01",
            "channel": 1,
            "type": "data",
            "status": 16
        },
        "data": {
            "R1": 0,
            "EB": 1
        }
    },
    {
        "meta": {
            "eep": "f6-03-01",
            "channel": 1,
            "type": "data",
            "status": 0
        },
        "data": {
            "R1": 0,
            "EB": 0
        }
    }
]

and switching it off, like this:
[
    {
        "meta": {
            "eep": "f6-03-01",
            "channel": 1,
            "type": "data",
            "status": 16
        },
        "data": {
            "R1": 1,
            "EB": 1
        }
    },
    {
        "meta": {
            "eep": "f6-03-01",
            "channel": 1,
            "type": "data",
            "status": 0
        },
        "data": {
            "R1": 0,
            "EB": 0
        }
    }
]

using a 4-rocker node, you can inject:
ON:
{
    "button": 0,
    "channel": 1,
    "event": "click"
}

or
OFF:
{
    "button": 1,
    "channel": 1,
    "event": "click"
}

I'm thinking of getting rid of this node entirely because it's really not needed. You can write a function node to achieve the same effect, and be more flexible in doing so...
On the other hand, sending button clicks is the most common task and should be easy.

keeping it...


How to get  2D and 3d box with FCOS3D?

How to get  2D and 3d box with FCOS3D? THX！！！！！！！！！

What do you mean by "get 2D and 3D box"? Please describe your problems more clearly.


Change mode name to file-browser-extended to avoid name clash

Solution for https://github.com/marvinkreis/rofi-file-browser-extended/issues/31

Thank you for the PR! Looks good.


User config file could not be loaded. Exiting Application.

Expected Behavior
App should be running with no errors
Current Behavior
I get an error for some odd reason
Possible Solution
Not sure i compared my config.yaml with the one in github and its the same exact thing 1:1
Steps to Reproduce
Follow the instructions in the github readme and run it
Context (Environment)

In the yasb.log file it writes this
2024-08-25 03:48:42 INFO log.py: Yasb - Yet Another Status Bar
2024-08-25 03:48:42 ERROR config.py: The config file 'C:\Users\slime\.yasb\config.yaml' contains validation errors. Please fix:
widgets:
- traffic:
  - null value not allowed

2024-08-25 03:48:42 ERROR config.py: User config file could not be loaded. Exiting Application.

All you need is tab all parameters under "traffic: "


handleBackspace causes blockembed attributes to be passed into next blot

This behaviour occurs when there are two consecutive videos. If the selection (cursor) is placed between the 2 videos and backspace is pressed to delete the first video, the height and width of the deleted video are transferred to the second video.
This does not occur if the cursor is before the first video and deleted with the delete key. It does not occur if there is a blank line (or other content) separating the two videos.
There are two default Backspace bindings pointing to the handler:
https://github.com/slab/quill/blob/b213e1073bac1478649f26e3c0dad50ad0eb2a49/packages/quill/src/modules/keyboard.ts#L105-L109
https://github.com/slab/quill/blob/b213e1073bac1478649f26e3c0dad50ad0eb2a49/packages/quill/src/modules/keyboard.ts#L126-L136
And, for firefox:
https://github.com/slab/quill/blob/b213e1073bac1478649f26e3c0dad50ad0eb2a49/packages/quill/src/modules/keyboard.ts#L94-L98
Removing these from quill.keyboard.bindings.Backspace removes the bug.
Demonstration:
The cursor is placed at the end of the first video and backspace pressed to delete the video. After deletion, the second video now has the width & height attributes of the first.
The delete is undone, the two loaded keyboard bindings for Backspace that point to handleBackspace are both deleted.
The delete action is repeated (cursor between videos, backspace pressed), this time the second video retains its width/height attributes.
https://github.com/user-attachments/assets/c757b415-3190-4c23-8de0-c08e1fbde472
Steps for Reproduction

Standard quill instance
Insert two adjacent videos
Format first with custom height/width
Format second with different height/width
Set cursor between videos, press backspace to delete the first video
See the remaining video size attributes have been replaced with those from the first
Undo delete
Delete Backspace keyboard bindings from quill instance (quill.keyboard.bindings.Backspace)
Set cursor between videos, press backspace to delete the first video
See the remaining video size attributes have not been altered

Version: 2.0.2

This is my workaround for now:
      this.quill.keyboard.bindings.Backspace.unshift({
        key: 'Backspace',
        empty: true,
        line: {
          domNode: {
            tagName: "IFRAME"
          }
        },
        handler: (range: any) => {
          this.quill.deleteText(range.index - 1, 1, "user");
        }
      });


Downgrade Moment to 2.8.3

2.8.4 has a bug that messes with the date pickers in basic dashboard.
For now, until we can properly investigate and fix, downgrading to the
version of moment that doesn't have the bug.

Got a +1 from @harrison in person


net45 support for Signalr C# client

Hello,
Thanks for this wonderful library.
Any plan to support old .net versions for the Microsoft.AspNetCore.SignalR.Client ? (in my case: net452)
Its a bit early to publish desktop apps using newer versions (not everybody has the newest framework versions installed)...
For what its worth, I only see two dependencies of SignalR.Client that would not support netstandard 1.2:

Microsoft.Extensions.Options  (referenced by Microsoft.AspNetCore.SignalR.Common.csproj)
Microsoft.AspNetCore.Protocols.Abstractions  (referenced by Microsoft.AspNetCore.Sockets.Abstractions.csproj)

Thanks

We have no plans to support anything below .NET Standard 2.0 (which is .NET 4.6.1). The dependencies you reference that require .NET Standard 2.0 also happen to be extremely core dependencies :). In general, ASP.NET Core (including the SignalR Client library) requires a minimum of .NET Standard 2.0.

Feel free to fork and port it down level but we have no plans to support it.


Task/add additional testing for team page

Codecov Report

Merging #153 (86d4a78) into development (210a282) will decrease coverage by 0.14%.
The diff coverage is 30.00%.

@@               Coverage Diff               @@
##           development     #153      +/-   ##
===============================================
- Coverage        88.59%   88.44%   -0.15%
===============================================
  Files               52       52
  Lines             3998     4008      +10
===============================================
+ Hits              3542     3545       +3
- Misses             456      463       +7

Flag
Coverage Δ

unittests
88.44% <30.00%> (-0.15%)
:arrow_down:

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

Impacted Files
Coverage Δ

api/authentication.py
61.93% <ø> (ø)

api/website/testing_routes.py
41.17% <30.00%> (-1.50%)
:arrow_down:

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 210a282...86d4a78. Read the comment docs.


Add assert_cmd test

Codecov Report

Merging #158 into master will increase coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #158      +/-   ##
==========================================
+ Coverage   81.34%   81.44%   +0.09%
==========================================
  Files          11       12       +1
  Lines         386      388       +2
==========================================
+ Hits          314      316       +2
  Misses         72       72

Impacted Files
Coverage Δ

tests/cli.rs
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


fix contributor workflow

Description
Fix contributor workflow (for #2355)

Summary by CodeRabbit

Chores

Updated the GitHub Actions workflows to improve the usage of secrets for authentication.
Modified the conditions for running SonarCloud Scan to only execute for the repository owner.

replaced by #2358


ERR Profile save() exception: Error: EACCES: permission denied, open '/bot/demo.wechaty.json'

Provide Your Network Information

Where is the location of your server? (i.e. City, or In/Out China)
Which cloud platform(AliYun/Qcloud/DigitalOcean/etc) are you using?

Run npm run doctor or wechaty run doctor(for docker user), paste output here
wechaty run doctor
Expected behavior
success
Actual behavior
13:45:16 ERR Profile save() exception: Error: EACCES: permission denied, open '/bot/demo.wechaty.json'
(node:30) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: EACCES: permission denied, open '/bot/demo.wechaty.json'
(node:30) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
^C13:45:19 INFO Bot finis(130, SIGINT)
Steps to reproduce the behavior (and fixes, if any)
Full Output Logs
$ WECHATY_LOG=silly npm run ts-node mybot.ts

# or

$ WECHATY_LOG=silly node dist/mybot.js

Show Logs

### Paste the full output logs here with `WECHATY_LOG=silly` set
# PASTE FULL LOG OUTPUT AT HERE:

The error message is clear enough:  Error: EACCES: permission denied, which means you have not right to right to directory /bot

sudo chown 999.999 pwd

Thanks @Gcaufy
Confirmed, will look into it to see if we should go back to use root user as before.

@zixia did you fixed this exception? when i try to save the user's avatar, the docker will exit.  thanks a lot

Not fix yet, because I'm still thinking about why I change to non-root user before...
It seems we should restore the docker to use the root user to make the life easier.

I agree, docker container they are independent, root should be safe for your host machine.

@Gcaufy Ok, let's change it back to use root user.
Is there anyone who wants to make this PR? :)

Will close this issue because I believe we had already switch back to use root inside our docker containers.


non-lowercase types get ignored

A commit message of Fix: The thing gets identified as type "Fix" but then discarded:
Using input tag: v1.2.3
Using latest tag: v1.2.3
Using previous tag: v1.2.2
[OK] Commit <hash> of type Fix - The thing
Warning: Nothing to add to changelog because of excluded types.

(In my cases, excluded types here is set to: excludedtypes: '' to include everything)
Looking at the FAQ on https://www.conventionalcommits.org/en/v1.0.0/ these should not be case-sensitive:

Are the types in the commit title uppercase or lowercase?
Any casing may be used, but it’s best to be consistent.

Fixed in v1.7.0


Next Team: Change Repository for Tests

Currently the tests create issues on my IssueTest repository, this should be changed

This has been fixed :-)


⚠ Bofrost.at has degraded performance

In 38fca11, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2285 ms

Resolved: Bofrost.at performance has improved in f42e9ae.


Convert to .netstandard 2.0 nuget package

Any updates on this? I would love to use this repo but need it to be in .Net Core instead of full framework. Thanks!

No - but feel free to do it, I will republish package
On Mon, Feb 3, 2020 at 6:27 PM Jeremy Kruer<EMAIL_ADDRESS>wrote:

Any updates on this? I would love to use this repo but need it to be in
.Net Core instead of full framework. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/voloda/AsyncDataAdapter/pull/4?email_source=notifications&email_token=AB5M4SGU4SNSJ7DANSD5ERLRBBHZFA5CNFSM4FWAXS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKUWAEQ#issuecomment-581525522,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5M4SGVLL5HY2QN6H45YALRBBHZFANCNFSM4FWAXS3A
.

PR Submitted.  Struggling with the appveyor build a little bit

It seems to be an issue with the MSBuildTasks.  Everything builds fine when running dotnet build but the build tasks fail.  I'm no very familiar with those tasks.  Is this something you would be able to look at?

I will try to have a look over weekend

@voloda any luck on this?


alternate to https://github.com/GarageGames/Torque3D/pull/1602

This fixes the animation while maintaining the brightness adjustment.