ADAL to MSAL migration - update apache-spark-sql-connector.md

Context: As a way of ensuring that third-party apps / services migrate to MSAL and no new ADAL apps are created, we are looking to work on all our content that endorses / mentions ADAL or endorse products that use the same.
We have identified the following doc(s) that need immediate attention.
Changes:

get SP credentials via mssparkutils.credentials.getSecret
remove adal library
use msal to get the token

Learn Build status updates of commit b153081:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/synapse-analytics/spark/data-sources/apache-spark-sql-connector.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@midesa

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

#sign-off

#sign-off

@midesa

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

@Jak-MS - could you please help with the merge? Misha has already approved it.


How to debug the server bundle?

I'm playing with the demo for past three days and get a rough understanding of how the whole system run. I would say vue 2.0 is amazing. I want to upgrade my 1.x to 2.x ASAP.
The only issue that block me is for server bundle debugging.
I basically fail to debug the server bundle and have no idea how to setup breakpoint for the Vue app. I can break in the server.js anyway, but it's not that useful because I would like to debug my Vue app.
And debugger statement doesn't work either.
Please suggest. Currently I have to fallback to use console.log.

This is something that still needs to be improved in bundleRenderer.

I think that one cool and missing functionality in Vuex shall be the ability to replay all your actions and mutations inside your SPA from a single log file.
There is a React example i can show you as reference: https://github.com/dtschust/redux-bug-reporter


FTC Objective Brainstorm

Build an arm to reach the lower basket & score samples
Build a claw to hold specimens/samples efficiently
Place Specimens on high chambers
Hang the robot on the low-rung
Create a team name/logo

Examples of team names so far:

The Forseen Fiasco
Mischief Unmanaged
Catastrophe Crew


Enhance Docker Image Tagging

This PR introduces an improved tagging strategy for Docker images, aiming to streamline image versioning and identification.
Changes Introduced:

Dynamic Tagging: Implemented dynamic generation of Docker image tags based on the git commit SHA (prefixed with git-), branch names, tags (including semantic versioning), and the special latest tag for the most recent build from the main branch.

Benefits:

Improved Traceability: Easily identify and pull images based on specific commits, branches, or release versions.
Simplified Deployment: Use the latest tag for deploying the most recent version without specifying a specific tag.

These updates enhance the Docker workflow's flexibility and usability, supporting more efficient development and deployment processes.

Amazing stuff! LGTM, Thanks!


draft of user tutorial in docs

docs should have a brief "tutorial" page with a minimal end-to-end example
Acceptance Criteria
At the upcoming June 7 garden all-hands meeting, we can point to this page of our docs so people can follow along with our end-to-end demo

part of #98


Why is the ESP WebTools page ow-breaker not recommended atm? worked for me

Why is the ESP WebTools page ow-breaker not recommended atm?
worked for me
thou v0.0.1
is it recommended to use 1.1.0
?

The only issue is that ow-breaker's page isn't automatically updated with the new releases. It's a third-party page that I'm not in control of.
My recommendation is to always use the latest official release on Owie's page so yes, in this situation you'd have to download it manually and perform the first install using esptool or other ESP8266 flashing method.


Forbid whitespaces in DatasetV2.zarr_dir

closes #2127
Checklist before merging

[x] I added an appropriate entry to CHANGELOG.md
[ ] I added logging to new code - if appropriate.
[x] I merged main into the current branch.

For my understanding: Do we strip leading & trailing whitespace? Or forbid whitespace overall in zarr_dir?
Requiring all paths to never require spaces could be tricky


How can i skip the video download from the playlist?

Is there any method to skip one or two files from the playlist?

unfortunately not directly but you could download the playlist in a json array format from youtube using their api and then edit it and pass it into the youtube-dl.exe using the exec command mentioned at the last of the post.


Add .Dockerignore file

This will avoid sending unnecessary files to docker:
https://docs.docker.com/engine/reference/builder/#dockerignore-file
https://www.tutorialspoint.com/using-dockerignore-file

Also move the COPY . /code/ line to the bottom of the dockerfile, after the requirements have been installed. This will prevent unwanted cache invalidations

https://testdriven.io/blog/docker-best-practices/


Fix compiler errors in tests and samples

After moving to ESM/tshy, we no longer build tests/samples. This PR enables running "typecheck" as an optional rush bulk command, and fixes some of the errors found.
The known errors reported on files from vite/vitest/chai are ignored.
The update-snippets dev-tool command throws error of reading undefined in some cases, adding a null check fixes it.
Snippets are updated as well after snippets.spec.ts files are fixed.

API change check
API changes are not detected in this pull request.


s3 bucket upload not triggering step functions and AttributeError: NoneType

Describe the bug
Hi! I was able to create the stack without any errors, but when a modified version of the csv file is uploaded to the s3 bucket, the step functions are not automatically triggered and the aws forecast autopredictor is not trained. I get the following error when I manually click start execution in the step functions.
[ERROR] AttributeError: 'NoneType' object has no attribute 'endswith'
Traceback (most recent call last):
File "/opt/python/shared/helpers.py", line 68, in wrapper
(status, output) = f(event, context)
File "/var/task/handler.py", line 29, in createdatasetgroup
dataset_file = DatasetFile(event.get("dataset_file"), event.get("bucket"))
File "/opt/python/shared/Dataset/dataset_file.py", line 36, in init
if key.endswith(".related.csv")
It seems to say there is no related time series csv file, but that's optional according to the documentation. Thus, I included the related time series dataset csv file, but it still gives the error. I provided both target and related time series datasets in the Cloud Formation stack, but it still has the value 'None'.
I believe this error is occurring because there was no event that triggered the steps function (I click start execution button instead). AWS instructions regarding deploying AWS forecast models with AWS cloud formation stacks say that I should just upload a file to s3 and it will automatically trigger the step functions that deploy the AWS forecast model we created. When I upload a modified version of the csv file to s3, nothing happens and I am not given any error. Could you please help me figure out why the stack is not deploying automatically? Thx
To Reproduce
https://docs.aws.amazon.com/solutions/latest/improving-forecast-accuracy-with-machine-learning/automated-deployment.html
Using the improving-forecast-accuracy-with-machine-learning.template and the following yaml configuration file:
Default:
DatasetGroup:
Domain: METRICS
Datasets:
- Domain: METRICS
DatasetType: TARGET_TIME_SERIES
DataFrequency: 15min
TimestampFormat: yyyy-MM-dd HH:mm:ss
Schema:
Attributes:
- AttributeName: timestamp
AttributeType: timestamp
- AttributeName: metric_name
AttributeType: string
- AttributeName: metric_value
AttributeType: float
AutoPredictor:
PredictorName: predictor_v1
MaxAge: 100
ForecastHorizon: 3
ForecastFrequency: 15min
Forecast:
ForecastTypes:
- "0.10"
- "0.50"
- "0.90"
No additional advanced settings added when creating the stack.
Please complete the following information about the solution:

[ ] Version: [e.g. v1.4.0]

Hi @nivedha75, thank you for creating this issue.
Could you please share your modified version of the csv file to try reproduce the issue.
Thanks

Closing stale issue. Please re-open if issue still exists.


Error Task Segfaults instead of waiting for PS

If the Error Task requests a model after the parameter server has started but before the PS has initialized the model, the error task will segfault.

#58

It seems the error results from the connect in the constructor of PSSparseServerInterface.cpp failing and throwing an error. However this error is then caught by the ErrorTask, but it doesn't quit the program or try to reconnect. When the socket is then used, the Error Task segfaults.

Should be fixed.


Environmental qualities

Greetings PATO Team,
Over at the Environment Ontology, we (myself and @cmungall) were considering the creation of some experimental quality-like classes that seem within the PATO domain:
e.g. "aquatic", "marine", "littoral", "deciduous", etc
Draft example definition...

"marine": A quality that inheres in an environmental system (the bearer) by virtue of that bearer being determined by an ocean or sea.

Where "determined by" is an ENVO relation expressing strong causal influence
The qualities of interest are generally used in the context of describing environments and ecosystems, thus we would be happy to develop them in ENVO as "environmental qualities"; however, we think that these should eventually merge into PATO once the experimental phase is over. Would we have a green light on this?

We have an analogous situation with anatomy. We're defining qualities like 'collagenous' as equivalentTo
'inheres in' some ('composed primarily of' some collagen)

This effectively makes them syntactic sugar. You could write the same thing without PATO. But it's useful as various apps 'expect' to have a Q to place in certain fields so it's continuous.
The modularization is slightly odd as we have some stuff over here in PATO in an odd bridge file, other stuff in uberon. In some ways it would easiest to organize this all over here in uberon or caro, minimize inter-module dependencies. But there is a certain historic attachment to having any kind of anatomical quality in PATO.
There isn't really any such expectation for qualities that are purely environmental (of course there are qualities like 'liquid' that are being used for multiple domains). For a purely environmental quality it may be simpler to minimize inter-module crossings and keep these in ENVO. Hard to say what is purely environmental. With my planteome hat on I can see wanting to use deciduous as a trait descriptor.

Yes, the 'problem' with environments is that pretty much any material entity can be 'hubs'  of some environmental system (and thus realise the environmental feature 'role'). I don't think we can really avoid modularity and importing a bunch of ontologies (plants, qualities, etc). Things like 'arid' and 'oceanic' can be considered closer to 'pure' environmental, but that's probably because there's no physical geography ontology interacting with ENVO.
Perhaps the model whereby 1) a set of potentially-out-of-domain classes are drafted in the ontology that's working with them given that 2) the respective domain ontology (here, PATO) is made aware of these and contributes to their definition so that 3) the classes will be surrendered en masse to the appropriate domain ontology (and given alternate IDs?). Is this feasible?


Hard code version number in Cog

Reopening this because if you fork and do a build, then you don't have any tags locally and the version doesn't get set.  https://canary.discord.com/channels/775512803439280149/994294965574303826/1002257687356125295
At Replicate, we rely on the version number to determine what API the Cog container speaks, so perhaps we need a more reliable way of determining version number.
(thanks @palp for uncovering!)


Abandoned php-http/message-factory package is used

Guzzle version(s) affected: 7.7.0
PHP version: 8.2 (hint: php --version)
Description
When using "composer install" a "Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead" warning appears. It seems that since 7.7.0 uses php-http/message-factory package which is abandoned.
How to reproduce
Composer Install
Possible Solution
Use psr/http-factory
Additional context
Package was added in Fixed tests commit and released in 7.7.0.

This only in require-dev. When you use guzzle in your own code, this package is not pulled in.

This still isn't proper package and shouldn't be used there.

The warnings are totally fine, and don't affect you in any way.

We should still plan to migrate to psr/http-factory at some point. It will otherwise show this warning in lots of projects.

Can you show me where installing guzzle in your app or library shows the warning please?

During a composer install (including require-dev)
The warning is
Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead.
Tested with Composer 2.1.8

My project does not require guzzle at all directly. It requires "league/oauth2-client", which requires guzzle and I sill get the warning.
composer install
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Nothing to install, update or remove
Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead.
Generating optimized autoload files
64 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

That's probably not from us. Can you run composer why php-http/message-factory please?

A thanks, you are right.


[2pt]  Display joined missions in My profile - Filters

Render a list of all joined missions (use filter()) on the "My profile" page.

This task is complete. Great work buddy


TypeError for non-base64 encoded images

Hi,
jupyter can store images as raw text, e.g.:
  "outputs": [
    "data": {
      "image/svg+xml": [
       "<?xml version=\"1.0\" encoding=\"utf-8\" standalone=\"no\"?>\r\n",
       "<!DOCTYPE svg PUBLIC \"-//W3C//DTD SVG 1.1//EN\"\r\n",
       "  \"http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd\">\r\n",
       "<!-- Created with matplotlib (https://matplotlib.org/) -->\r\n",
       "<svg ...>...</svg>\r\n"
      ]
    }
  ]

In that case junix throws the following exception:
  File "[...]/junix/exporter.py", line 96, in save_images
    img_data = base64.b64decode(image["content"])
  File "/usr/lib/python3.9/base64.py", line 80, in b64decode
    s = _bytes_from_decode_data(s)
  File "/usr/lib/python3.9/base64.py", line 45, in _bytes_from_decode_data
    raise TypeError("argument should be a bytes-like object or ASCII "
TypeError: argument should be a bytes-like object or ASCII string, not 'list'

This can be fixed by replacing:
-            img_data = base64.b64decode(image["content"])
+            content = image["content"]
+            if isinstance(content, list):
+                img_data = ''.join(content).encode('utf-8')
+            else:
+                img_data = base64.b64decode(content)

When looking at the code, I noticed some stuff that can be simplified to make the code easier to understand and modify (at least for me). For example, it's hard to see that your version doesn't export all available formats if an output image is available in multiple formats. I would suggest a rewrite of the entire exporter akin to this:
import base64
import json
import os

def export_images(filename, prefix=None):
    with open(filename, "r") as f:
        notebook = json.load(f)

    if prefix is None:
        basename, ext = os.path.splitext(filename)
        prefix = prefix or os.path.join(basename, '')

    images = list(get_images(notebook))
    if images:
        os.makedirs(os.path.dirname(prefix), exist_ok=True)

    for c, o, content_type, image_data in images:
        file_ext = content_type.split('/', 1)[1].split('+', 1)[0]
        filename = "{}{}_{}.{}".format(prefix, c, o, file_ext)
        with open(filename, "wb") as f:
            f.write(image_data)

    return images

def get_images(notebook):
    return (
        (idx_cell, idx_output, content_type, decode_image_data(content))
        for idx_cell, cell in enumerate(notebook.get("cells", ()))
        for idx_output, output in enumerate(cell.get("outputs", ()))
        for content_type, content in output.get("data", {}).items()
        if content_type.startswith('image/')
    )

def decode_image_data(content):
    if isinstance(content, list):
        return ''.join(content).encode('utf-8')
    else:
        return base64.b64decode(content)

Feel free to use this code, or let me know if I should submit a PR.
Best, Thomas

Thanks @coldfix! I will try to add your code in. I will tag you in the PR!

Thanks @coldfix for the suggestions! I did some refactoring and I will try to add your code in. I will tag you in the PR!

great, thanks!

Would you have an example on how to generate such format? I will try creating a unit test that checks the format is properly handled.

I see you got an example already. If you want more, here is how SVG output would be generated by matplotlib:
# Either this way:
%config InlineBackend.figure_formats = ['svg']

# Or this (some libraries seem to execute this automatically):
import matplotlib_inline
matplotlib_inline.backend_inline.set_matplotlib_formats('svg')

# And display a figure:
import matplotlib.pyplot as plt
plt.plot()

Thanks @coldfix.
Ya, i used a free svg I found online.
I added your code to loop more efficiently through the notebook as well as the part to handle the SVG part + the possibility to pick the prefix.
It was smooth to make the changes. Thanks for your code snippets!
This was done in this PR if you are interested in having a look
https://github.com/damienmarlier51/JupyterNotebookImageExporter/pull/9/files
Cheers
Damien


Add uefi capsule update for AGX Orin

We need to merge and test this with a modified upgrade-ssh-2x in balenaHUP that bindmounts /sys

@balena-ci I self-certify!

Testing upgrade-2.x showed that balenaHUP runs hostapp-update in a container only for a non-hostapp to hostapp migration.


Create Two Sum.cpp

Related Issue
issue number #1
Added Two Sums Leetcode problem.
Proposed Changes

Added Two Sum problem Based on Sorting Algorithm

Additional Info

Was not present in the Algo section so I thought put it.

Checklist

[ x] My code follows the code style of this project.
[x ] My change requires a change to the documentation.
[x ] I have updated the documentation accordingly.
[ x] I have read the CONTRIBUTING document.
[x ] I have added tests to cover my changes.
[ x] All new and existing tests passed.

Added Two Sum Problem
Uses Quick Sort Algorithm
Quick Sort Algo was missing in this Repo
Added one test case and tested for input and verified the output.

[ ] Bug fix (non-breaking change which fixes an issue)
[x ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Output Screenshots
| ----------- | ----------- |
Two sum

please let me know if there could be some improvement .
Thanks

Please read the following steps here for problem statement
Your code is fine output is fine , just one more step and it will be merged
Thanks for your interest
Happy Coding !!


Add Github Action to publish readthedocs

https://github.com/readthedocs/actions

https://rtds-action.readthedocs.io/en/latest/


Players frequently losing connection on new ViaVersion (when 1.13 support was added)

What is the output link of /viaversion dump?
https://dump.viaversion.com/4a5a170c4dbc46c857295d323134f3e3657cb1a9ad17ec168c73abc294922382
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
Error does not happen on ViaVersion 1.3.0 or lower, but happens on any more recent version, it's happening on the latest build of ViaVersion and ViaVersion-DEV, the server is also using the latest ViaBackwards-DEV and it was happening on the non dev version too. Its happened on Spigot 1.12, Spigot 1.12.2, and PaperSpigot 1.12.2, This also happens when only ViaVersion is used without ViaBackwards. Plugins: https://pastebin.com/uBS7UvQ2
(Note: This is happening to all players on all versions 1.10-1.13, not just on 1.13)
How does this error happen? login? Using an item?
Happens a lot Login or randomly
Is there an error in the console? Use pastebin.com. Is there a kick message?
https://pastebin.com/dvJWHnjj
https://pastebin.com/H85AbJck
https://pastebin.com/tRhE0AQA

What is the ping of players to your server?
Are you able to replicate this by yourself? (You say all players? Does everyone experience this or could it be based on latency?)

Most players have a 5-10ms ping, however when I use the newer ViaVersion with 1.13 support a lot of people have been getting poor connections and only get 1 bar in tab. And Yes I'm able to replicate it myself, I've timed out a fair amount of times aswell (Usually when my game is minimized, not sure if that has anything to do with it)

Same problem here, rare but apparently random disconnects on executing (vanilla and other) commands, doesn't seem to matter which (gamemode, ..., any other command from another plugin). I haven't realy looked at the circumstances, but it seems random

We've never been able to replicate this, I've fixed a possible deadlock in latest build. Otherwise it's case of if you can build a .zip which can replicate this i'll happily look into it further (ensure it works on other machines). Otherwise i'm convinced this might be down to something else.


PARTICIPANT Error when using XRCE Agent

Hi,
I am using an XRCE Client over an STM controller, which communicates with and XRCE Agent running on a linux machine. The controller is connected to the linux machine over a serial connection using an FTDI.
For some reason, on occasion, when I restart the Client while the Agent is still up and running, I get the following error:
[MicroXRCEAgent-6] 2021-03-01 15:33:01.988 [PARTICIPANT Error] Type : std_msgs::msg::dds_::Float32MultiArray_ Not Registered -> Function createSubscriber
Do you have any idea what am I doing wrong?

Could you share your client code?

It is based upon https://github.com/ROBOTIS-GIT/ros2arduino/blob/master/README.md

For solving this issue I need:

Exact version or commit of the Micro XRCE-DDS Client and Agent
Micro XRCE-DDS Client build options
Micro XRCE-DDS Client code and reference files for replicating the problem

Closing due to inactivity


[CLOSED] Add history window to training CSV

 Issue by mareklinka
Sat Aug 25 15:29:15 2018
Originally opened as https://github.com/ERNICommunity/dust-measurement-network/issues/30

In addition to the current values, we want to include also the values from previous four hours in the training examples. After joining the weather data with the sensor data, also add these history windows to each example so that we don't have to do it in a different tool.

 Comment by mareklinka
Thu Aug 30 12:35:47 2018

This is now pretty much done. Closing the issue.


Basic NFT / Collection / Marketplace helpers

Add Basic NFT / Collection / Marketplace helpers to the E2E-test-dApp.

This task was completed here: https://github.com/capsule-corp-ternoa/ternoa-js-test-dapp/commit/cb19e938671a550d4e02e2eedd72ab0e939986b8


Make it possible to use it as a log-logger?

So we can simply add it as the logger for  https://crates.io/crates/log ?

At the moment there is support for slog
https://github.com/Ralvke/logram#use-logram-as-slog-drain
But i have plans for fully rewrite logram, and i add support for log
I plan to do this in a week.

Cool! Thanks!

No worries, I'm aware of being a maintainer with limited resources in terms of time. :)

Works perfectly fine, thank you! :)

Update: log records with target starts with tokio_reactor, hyper, mio, want or reqwest will be skipped, because limitations in log #https://github.com/rust-lang-nursery/log/issues/312


Dilithium implementation variant dropped

I see that the details of PQC algorithms are a moving target.
And it is appreciated that the ML-DSA-87 is implemented. But it is upsetting that the support for OID <IP_ADDRESS>.<IP_ADDRESS><IP_ADDRESS> was dropped from BC while the ejbca is happily signing certificates with exactly this OID.
Please amntion a dropped OID in the release notes or even better, mark it as deprecated and support it some a few releases.

Sorry, but it's not just the OID that changed - the OQS OIDs change as the algorithm is tweaked, we just don't have the resources to support multiple variants. Understand the frustration though and we should mention it, hopefully this whole thing will be resolved soon - initial testing is now possible on the ACVP demo system so it looks like everything is going into place for the final standard.

OK, I see!
Thank you for the quick reply. Thomas also promised that ejbca will be using the most recent BC version, soon.
We'll test as soon as possible!


DevTools: Improved the general tab layout

Description

This also includes an update to the design system to get the Chip component.
Made the layout more responsive so it actually uses the horizontal space, and added scrolling. Also added a warning message above the preview PDF button if not using google chrome. To make the navigation more responsive I used the new Chip component from the design system.

https://github.com/Altinn/app-frontend-react/assets/47412359/41a362e2-b87d-4970-94bb-fe8b1cfef0dd

Waiting a bit for clarification on design system button updates.


fix to typo in '+build'

What does this pull request do?
fix typo in wrap.go
Where should the reviewer start?
look at wrap.go
How should this be manually tested?
run go install or go build

Codecov Report

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

@@           Coverage Diff           @@
##           master      #27   +/-   ##
=======================================
  Coverage   43.03%   43.03%
=======================================
  Files           2        2
  Lines         165      165
=======================================
  Hits           71       71
  Misses         84       84
  Partials       10       10

Impacted Files
Coverage Δ

wrap.go
42.51% <ø> (ø)
: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 babee2a...a8014f2. Read the comment docs.

@alessandrozucca have you signed the Google CLA?

I've signed it now


changes to readme for local setup

@kliu28 Could you please move the "install Postgres" item down into the "no containers" section? If you are running docker, the database will be a container managed with docker-compose rather than being on your machine.

updated. also edited numbering just for editing's sake; markdown technically doesn't care about the actual numbers in a numbered list


Improve performance of operations with an expiration.

See issue #118
This PR improves the performance of the of operations with expiration. The performance issue is due to the expire_times data structure in the Database class. The PR improves the performance by inserting the key-time pair in the expire_times Array at the correct position instead of inserting it at the end and re-sorting.
These are the results on my machine for the script mentioned in #118 with 10,000 keys.
# before
[mdalton@mdalton-MacBook-Pro-7 mock_redis (master)]$ bundle exec ruby performance.rb
setex
25.877892246004194
set
0.16075976501451805

# after
[mdalton@mdalton-MacBook-Pro-7 mock_redis (master)]$ bundle exec ruby performance.rb
setex
6.0611226839828305
set
0.13644369100802578

My first attempt to fix this issue was to change the data structure for expire_times from an Array to a Hash. I thought this would speed things up since most operations on this data structure in the Database class would be performed in constant time with a Hash but are linear time with an Array. However, when I made this change, the time actually increased. I realized that the reason it was a sorted Array to begin with was because it is optimized for the expire_keys method.
Even though this PR does not prevent the exponential degradation, it does improve it.
Let me know your thoughts.

It's a great improvement, thank you!
I think that the best solution would be to use a priority queue but it will require bigger changes.

Hey @kcdragon, thanks for this pull request!
This is great, but unfortunately Array#bsearch_index is available only in Ruby 2.3+. We'd like to have something that is at least supported by Ruby 2.0+ (though I would accept Ruby 2.1+ as Ruby 2.0 has been end-of-lifed).

@sds Ah, I always forget about needing to support older versions of Ruby. I could write my own implementation of that method but at a certain point the complexity of that outweighs the small benefit of performance.

I'm going to close this for now as it seems neither of us has time to work on getting this working with Ruby 2.1+
Perhaps we can revisit once 2.1 and 2.2 are EOLed, at which point it makes sense for MockRedis to consider supporting only Ruby 2.3+.
Thanks again! Feel free to open a new pull request with support for Ruby 2.0.


1.2.0-rc4-nested

Making DCS optional to support nested edge scenario

Hi @veyalla could you please have a look at this PR? It makes the DCS optional on RC4 so that we can use the new nested edge config tool (that takes care of the device connection string). Thanks!

@veyalla , can you please merge this PR if you re ok with it? I dont have merge permissions. Thanks!


Crash when exporting in headless mode on Linux with Godot 4.2.2.rc2.mono

Tested versions

Reproducible in: v4.2.2.rc2.mono.official (c61a68614e5b030a4a1e11abaa5a893b8017f78d) and I think also 4.2.1.stable and 4.2.2.rc1 (I was testing various things inside podman before finding the root cause but I didn't keep the various containers).
Not reproducible: Godot 3.5 (I can't say anything more specifically as I'm porting my project to Godot 4 and haven't gotten a working version yet).

System information
Fedora 39, also happens inside a podman container with Fedora 39 base with minimal packages
Issue description
When exporting in headless mode I get a crash:
$ godot --export-release Linux/X11 build/BlankProject --headless
Godot Engine v4.2.2.rc2.mono.official.c61a68614 - https://godotengine.org

WARNING: Custom cursor shape not supported by this display server.
     at: cursor_set_custom_image (servers/display_server.cpp:505)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.2.2.rc2.mono.official (c61a68614e5b030a4a1e11abaa5a893b8017f78d)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /usr/lib64/dotnet/shared/Microsoft.NETCore.App/8.0.2/libcoreclr.so(+0x606a85) [0x7f866da06a85] (??:0)
[2] /usr/lib64/dotnet/shared/Microsoft.NETCore.App/8.0.2/libcoreclr.so(+0x6060b5) [0x7f866da060b5] (??:0)
[3] /lib64/libc.so.6(+0x3e9a0) [0x7f86931d39a0] (??:0)
[4] godot() [0x314a2a9] (??:0)
[5] godot() [0x31bab24] (??:0)
[6] godot() [0x31b5db7] (??:0)
[7] godot() [0x31b571f] (??:0)
[8] godot() [0x31bbdd4] (??:0)
[9] godot() [0x31bcff4] (??:0)
[10] godot() [0x31e852e] (??:0)
[11] godot() [0x2bef894] (??:0)
[12] godot() [0x172a448] (??:0)
[13] godot() [0x12edc3c] (??:0)
[14] godot() [0x4a70b7] (??:0)
[15] godot() [0x41e7f9] (??:0)
[16] /lib64/libc.so.6(+0x2814a) [0x7f86931bd14a] (??:0)
[17] /lib64/libc.so.6(__libc_start_main+0x8b) [0x7f86931bd20b] (??:0)
[18] godot() [0x42b24a] (??:0)
-- END OF BACKTRACE --
================================================================
Keskeytetty (luotiin core-tiedosto)

Running without the headless flag works:
$ godot --export-release Linux/X11 build/BlankProject
Godot Engine v4.2.2.rc2.mono.official.c61a68614 - https://godotengine.org
Vulkan API 1.3.267 - Forward+ - Using Vulkan Device #0: AMD - AMD Radeon RX 7900 XTX (RADV NAVI31)

savepack: begin: Pakataan steps: 102
	savepack: step 2: Varastoidaan Tiedostoa: res://.godot/imported/icon.svg-218a8f2b3041327d8a5756f3a245f83b.ctex
	savepack: step 2: Varastoidaan Tiedostoa: res://icon.svg.import
	savepack: step 52: Varastoidaan Tiedostoa: res://.godot/exported/133200997/export-3070c538c03ee49b7677ff960a3f5195-main.scn
	savepack: step 102: Varastoidaan Tiedostoa: res://main.tscn.remap
	savepack: step 102: Varastoidaan Tiedostoa: res://.godot/global_script_class_cache.cfg
	savepack: step 102: Varastoidaan Tiedostoa: res://icon.svg
	savepack: step 102: Varastoidaan Tiedostoa: res://.godot/uid_cache.bin
	savepack: step 102: Varastoidaan Tiedostoa: res://project.binary
savepack: end
ERROR: Condition "!EditorSettings::get_singleton() || !EditorSettings::get_singleton()->has_setting(p_setting)" is true. Returning: Variant()
   at: _EDITOR_GET (editor/editor_settings.cpp:1144)

(though it prints this error: https://github.com/godotengine/godot/issues/84839)
When I export my full project, I get slightly different results, instead of SIGSEGV I get SIGILL:
Core was generated by `godot --editor --headless .'.
Program terminated with signal SIGILL, Illegal instruction.
#0  0x0000000000472607 in ?? ()
[Current thread is 1 (LWP 1563)]
(gdb) bt
#0  0x0000000000472607 in ?? ()
#1  0x0000000000000000 in ?? ()

Exporting to folder: builds/Thrive_<IP_ADDRESS>-alpha_linux_x11
libfontconfig.so.1: cannot open shared object file: No such file or directory
Godot Engine v4.2.2.rc2.mono.official.c61a68614 - https://godotengine.org

WARNING: Custom cursor shape not supported by this display server.
     at: cursor_set_custom_image (servers/display_server.cpp:505)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.2.2.rc2.mono.official (c61a68614e5b030a4a1e11abaa5a893b8017f78d)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
ERROR: FATAL: Index p_index = 1 is out of bounds (size() = 0).
   at: get (./core/templates/cowdata.h:158)

Steps to reproduce

Open a basically new project (I just added one scene with a label and the default icon file in it to check that the exported project launches fine) in Godot
Try to export it with the --headless flag from terminal, observe it crashes
Export without the headless flag, this time it works (godot --export-release Linux/X11 build/BlankProject)

Minimal reproduction project (MRP)
BlankProject.zip

I can confirm that trying to export that project still crashes for me (well I'm still using the 4.2.2 RC2 version, sorry if I missed a newer RC being available). So it does not require a C# project. I also just confirmed that v4.2.2.rc2.official.c61a68614 also crashes so it is not required to have the mono version of Godot to get this crash.
Here is a Dockerfile which reproduces the issue for me (and hopefully for everyone else as well):
FROM fedora:39

RUN dnf install -y --setopt=deltarpm=false unzip wget dotnet-sdk-8.0 fontconfig

ENV GODOT_VERSION "4.2.2-rc2"

RUN wget https://downloads.tuxfamily.org/godotengine/4.2.2/rc2/mono/Godot_v4.2.2-rc2_mono_linux_x86_64.zip \
    && wget https://downloads.tuxfamily.org/godotengine/4.2.2/rc2/mono/Godot_v4.2.2-rc2_mono_export_templates.tpz \
    && mkdir .p ~/.cache \
    && mkdir -p ~/.config/godot \
    && mkdir -p ~/.local/share/godot/export_templates/${GODOT_VERSION}.rc2.mono \
    && unzip Godot_v${GODOT_VERSION}_mono_linux_x86_64.zip \
    && mv Godot_v${GODOT_VERSION}_mono_linux_x86_64 godot_dir \
    && mv godot_dir/* /usr/local/bin/ \
    && ln -s /usr/local/bin/Godot_v${GODOT_VERSION}_mono_linux.x86_64 /usr/local/bin/godot \
    && unzip Godot_v${GODOT_VERSION}_mono_export_templates.tpz \
    && mkdir -p ~/.local/share/godot/export_templates/${GODOT_VERSION}.rc2.mono \
    && mv templates/* ~/.local/share/godot/export_templates/${GODOT_VERSION}.rc2.mono/ \
    && rm -f Godot_v${GODOT_VERSION}_mono_export_templates.tpz Godot_v${GODOT_VERSION}_mono_linux_x86_64.zip \
    && rm -rf templates godot_dir

RUN mkdir /project

ADD export_presets.cfg icon.svg icon.svg.import main.tscn project.godot /project

RUN mkdir /project/build

# This is the export step which ends with a segfault
RUN cd /project && godot --export-release Linux/X11 build/BlankProject --headless

Putting that docker file in the sample project folder and running with podman ends with the following:
$ podman build BlankProject
# I cut out the long output from wget downloading stuff here
--> dcfa293def38
STEP 5/8: RUN mkdir /project
--> a0635cb09844
STEP 6/8: ADD export_presets.cfg icon.svg icon.svg.import main.tscn project.godot /project
--> f89e490cdf13
STEP 7/8: RUN mkdir /project/build
--> 7b3392ecbfa6
STEP 8/8: RUN cd /project && godot --export-release Linux/X11 build/BlankProject --headless
Godot Engine v4.2.2.rc2.mono.official.c61a68614 - https://godotengine.org

WARNING: Custom cursor shape not supported by this display server.
     at: cursor_set_custom_image (servers/display_server.cpp:505)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.2.2.rc2.mono.official (c61a68614e5b030a4a1e11abaa5a893b8017f78d)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
ERROR: FATAL: Index p_index = 1 is out of bounds (size() = 0).
   at: get (./core/templates/cowdata.h:158)
container exited on illegal instruction
Error: building at STEP "RUN cd /project && godot --export-release Linux/X11 build/BlankProject --headless": while running runtime: exit status 1

Here's the updated sample project with the included Dockerfile: BlankProject2.zip

See #90431

Tested using the dockerfile above and podman on Fedora 39.
The dockerfile had some typos and installed the templates in the wrong folder, here's a fixed version with fully dehardcoded version numbers:
FROM fedora:39

RUN dnf install -y --setopt=deltarpm=false unzip wget dotnet-sdk-8.0 fontconfig

ENV GODOT_VERSION "4.2.2-rc2"

RUN wget https://github.com/godotengine/godot-builds/releases/download/${GODOT_VERSION}/Godot_v${GODOT_VERSION}_mono_linux_x86_64.zip \
    && wget https://github.com/godotengine/godot-builds/releases/download/${GODOT_VERSION}/Godot_v${GODOT_VERSION}_mono_export_templates.tpz \
    && mkdir .p ~/.cache \
    && mkdir -p ~/.config/godot \
    && mkdir -p ~/.local/share/godot/export_templates/${TEMPLATE_VERSION}.mono \
    && unzip Godot_v${GODOT_VERSION}_mono_linux_x86_64.zip \
    && mv Godot_v${GODOT_VERSION}_mono_linux_x86_64 godot_dir \
    && mv godot_dir/* /usr/local/bin/ \
    && ln -s /usr/local/bin/Godot_v${GODOT_VERSION}_mono_linux.x86_64 /usr/local/bin/godot \
    && unzip Godot_v${GODOT_VERSION}_mono_export_templates.tpz \
    && export TEMPLATE_VERSION=$(echo ${GODOT_VERSION} | sed -e "s/-/./") \
    && mkdir -p ~/.local/share/godot/export_templates/${TEMPLATE_VERSION}.mono \
    && mv templates/* ~/.local/share/godot/export_templates/${TEMPLATE_VERSION}.mono/ \
    && rm -f Godot_v${GODOT_VERSION}_mono_export_templates.tpz Godot_v${GODOT_VERSION}_mono_linux_x86_64.zip \
    && rm -rf templates godot_dir

RUN mkdir /project

ADD export_presets.cfg icon.svg icon.svg.import main.tscn project.godot /project

RUN mkdir /project/build

# This is the export step which ends with a segfault
RUN cd /project && godot --export-release Linux/X11 build/BlankProject --headless

I can reproduce the crash with 4.2.2-rc2 and 4.2.2-rc3.
It seems fixed in 4.3-dev5.
Would be good to figure out which commit fixed it in 4.3 so it could be cherry-picked for a future 4.2.x release. But otherwise the bug appears to be fixed.

Would be good to figure out which commit fixed it in 4.3 so it could be cherry-picked for a future 4.2.x release. But otherwise the bug appears to be fixed.

Well I'll keep it open for now as reminder to try to find that commit.

So I did some more testing, the bug is not reproducible in any 4.3 dev snapshot, nor 4.2-stable, 4.2.1-stable, or 4.2.2-rc1... but it's indeed present in 4.2.2-rc2, so it was a regression all along.
It's also still reproducible in 4.2.2-rc3, so that's a release blocker for 4.2.2-stable.

Here's a backtrace:
Thread 1 "godot" received signal SIGBUS, Bus error.
0x00000000064429dd in ShaderCompiler::_get_sampler_name (this=0xb14b810, p_filter=185666464, p_repeat=ShaderLanguage::REPEAT_DISABLE) at ./servers/rendering/shader_compiler.cpp:300
300             return String(name_mapping[p_filter + (p_repeat == ShaderLanguage::REPEAT_ENABLE ? ShaderLanguage::FILTER_DEFAULT : 0)]);
Missing separate debuginfos, use: dnf debuginfo-install bzip2-libs-1.0.8-16.fc39.x86_64 fontconfig-2.14.2-6.fc39.x86_64 freetype-2.13.1-2.fc39.x86_64 glib2-2.78.3-1.fc39.x86_64 glibc-2.38-17.fc39.x86_64 graphite2-1.3.14-12.fc39.x86_64 harfbuzz-8.2.1-2.fc39.x86_64 libbrotli-1.1.0-1.fc39.x86_64 libcap-2.48-9.fc39.x86_64 libgcc-13.2.1-7.fc39.x86_64 libpng-1.6.37-15.fc39.x86_64 libxml2-2.10.4-3.fc39.x86_64 pcre2-10.42-1.fc39.2.x86_64 systemd-libs-254.10-1.fc39.x86_64 xz-libs-5.4.4-1.fc39.x86_64 zlib-1.2.13-4.fc39.x86_64
(gdb) bt
#0  0x00000000064429dd in ShaderCompiler::_get_sampler_name (this=0xb14b810, p_filter=185666464, p_repeat=ShaderLanguage::REPEAT_DISABLE) at ./servers/rendering/shader_compiler.cpp:300
#1  0x000000000644a9f5 in ShaderCompiler::_dump_node_code (this=0xb14b810, p_node=0xb914e80, p_level=2, r_gen_code=..., p_actions=..., p_default_actions=..., p_assigning=false, p_use_scope=true)
    at ./servers/rendering/shader_compiler.cpp:1297
#2  0x0000000006447a50 in ShaderCompiler::_dump_node_code (this=0xb14b810, p_node=0xb9ba970, p_level=2, r_gen_code=..., p_actions=..., p_default_actions=..., p_assigning=false, p_use_scope=true)
    at ./servers/rendering/shader_compiler.cpp:857
#3  0x0000000006447387 in ShaderCompiler::_dump_node_code (this=0xb14b810, p_node=0xb9b51d0, p_level=2, r_gen_code=..., p_actions=..., p_default_actions=..., p_assigning=false, p_use_scope=true)
    at ./servers/rendering/shader_compiler.cpp:811
#4  0x0000000006446f5a in ShaderCompiler::_dump_node_code (this=0xb14b810, p_node=0x123fd250, p_level=1, r_gen_code=..., p_actions=..., p_default_actions=..., p_assigning=false, p_use_scope=true)
    at ./servers/rendering/shader_compiler.cpp:772
#5  0x000000000644dbbb in ShaderCompiler::compile (this=0xb14b810, p_mode=RenderingServer::SHADER_CANVAS_ITEM, p_code=..., p_actions=0x7fffffff7f00, p_path=..., r_gen_code=...)
    at ./servers/rendering/shader_compiler.cpp:1558
#6  0x0000000006578a72 in RendererDummy::MaterialStorage::shader_set_code (this=0xb14b7c8, p_shader=..., p_code=...) at servers/rendering/dummy/storage/material_storage.cpp:89
#7  0x00000000064a1af4 in RenderingServerDefault::shader_set_code (this=0xb101570, p1=..., p2=...) at ./servers/rendering/rendering_server_default.h:235
#8  0x0000000005b91d99 in Shader::set_code (this=0x1440a600, p_code=...) at ./scene/resources/shader.cpp:108
#9  0x00000000048e4fa7 in AnimationPlayerEditor::AnimationPlayerEditor (this=0x13b8df30, p_plugin=0x13b8d830) at ./editor/plugins/animation_player_editor_plugin.cpp:2026
#10 0x00000000048e67a7 in AnimationPlayerEditorPlugin::AnimationPlayerEditorPlugin (this=0x13b8d830) at ./editor/plugins/animation_player_editor_plugin.cpp:2196
#11 0x000000000431e79b in EditorNode::EditorNode (this=0xbc8e400) at ./editor/editor_node.cpp:7854
#12 0x00000000029f348e in Main::start () at main/main.cpp:3309
#13 0x0000000002964a79 in main (argc=5, argv=0x7fffffffd6a8) at platform/linuxbsd/godot_linuxbsd.cpp:72

This points at #87392 likely causing the regression. It works in 4.3, but evidently this wasn't applicable as is to 4.2.x.
CC @clayjohn

Fixed by #90738.


Manual approval required for workflow run<PHONE_NUMBER>: Approve production deployment, high risk: true

Workflow is pending manual review.
URL: https://github.com/anbl-jyskebank-dk/approval-test/actions/runs/3648485414
Required approvers: [anbl-jyskebank-dk]
Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel.

lgtm

All approvers have approved, continuing workflow and closing this issue.


Add utility methods to Theme, improve error messages and documentation

This adds several utility methods that can be used to replace a lot of boilerplate code mentioned in https://github.com/godotengine/godot/pull/46593#issuecomment-792306683. While mostly useful internally, users can find them handy as well, especially plugin developers. So I've exposed them.
This PR also includes all theme additions from #46593 and #46808, so that they can be tested and merged separately (and those PRs can then be rebased).
This should be portable to 3.x, likely even cherrypickable.

Added missing get_font_size_type_list() method.
Added rename_X() methods for renaming theme items.
Added add_X_type() method for creating empty theme item types; these methods are not exposed to the API to prevent confusion from users thinking calling them is necessary, when in fact all set_X methods implicitly create types.
Added DataType enum and VERB_theme_item_X() methods to perform all the same tasks as are available for individual item types but without hardcoding all the function names.

Thanks!


OneOf WorldQuery via a Xor filter, alternative to Enum filtering

What problem does this solve or what need does it fill?
A somewhat common question in the Bevy Discord involves being able to filter by a component's enum variant:
enum MyComponent {
    Foo,
    Bar,
}

fn my_system(query: Query<Entity, With<MyComponent::Foo>>) {
    // ...
}

This doesn't work because Rust doesn't represent enum variants as full types. A common alternative is to use marker components instead, but currently you lose out on the mutual exclusivity that standard enums provide.
I propose to add a new OneOf<(A, B, C, ...)> WorldQuery similar to AnyOf, but backed by a Xor filter rather than Or.
What solution would you like?
Similar to how AnyOf works:
// equivalent to `Query<(Option<&A>, Option<&B>, Option<&mut C>), Or<(With<A>, With<B>, With<C>)>>
fn my_system(query: Query<AnyOf<(&A, &B, &mut C)>>) {}

This new OneOf should work like:
// equivalent to `Query<(Option<&A>, Option<&B>, Option<&mut C>), Xor<(With<A>, With<B>, With<C>)>>
fn my_system(query: Query<OneOf<(&A, &B, &mut C)>>) {}

Could also look at having an enum return type per arity, like
enum OneOf2<A, B> {
    A(A),
    B(B),
}

enum OneOf3<A, B, C> {
    A(A),
    B(B),
    C(C),
}

// etc ...

This might be best paired with Archetype Invariants.
What alternative(s) have you considered?
Use enums and deal with its inherent issues manually.

This is not ergonomic. Bevy could generate marker types for each variant of the enum and they can then be used in the query.


NIFI-5346 Introduces new PGP controller service and PGP processors.

Introduces new PGP Controller Service and PGP Processors
Enables PGP encryption, decryption, digital signing and verification functionality; fixes bug NIFI-5346.
Also addresses or resolves NIFI-5335, NIFI-6708.
This PR replaces #4032.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

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

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

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

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

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

For documentation related changes:

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

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

I also don't see any changes to the existing EncryptContent processor. We should clearly indicate that the PGP operations in the new processors will be faster and easier to use and configure, update the documentation for both, and explain to the users and developers why this decision was made. We don't want to break BC on a minor release, but users should be encouraged to change now so we can drop the PGP operations from the legacy processor in a major release.

Thanks for the additional comments @sasqnz . I believe the original author is not continuing with this effort, so I will be making a new PR for this ticket and will be sure to test the cases you raised.


[remove-resource] Delete OER Content Space Skeleton

With the release of my new Open Publishing Space skeleton and revised documentation, I'd like to have my (very similar) Gantry-based skeleton OER Content Space removed from the getgrav.org site:
https://github.com/hibbitts-design/grav-skeleton-oer-content-space
I will continue to offer direct downloads of this skeleton for a period of time, and as well all the Gantry Particles I created for it.
Thanks very much,
Paul

will remove this soon.

Update please?

its done.

Thanks Andy!

Hi @rhuk , the OER Content Space Site skeleton seems to still be listed on https://getgrav.org/downloads/skeletons, is that intentional? I'd like to remove it from the getgrav.org site altogether. Thanks!

Uggg.. i committed it but didn't push.. Done so now.

There's some problems going on with Travis and they responded to me with this message "During the week of September 25th-29th, we’re at a company-wide offsite, working on new features and improving Travis CI. While we’ll be checking email daily, our response times may be delayed." my particular problem is builds running for 6+ hours and never ending as per their 50 minute build timeout


remove "protected" managed threads

Plus: simpler mechanism and better logging for worker vs managed threads

@davidszotten this is ready for another round of review.
Apologies for all the commits. I have been back and forth a lot with various versions of pytest, eventlet, coverage and pytest-cov.
The root cause of all the failures above was upgrading to a recent pytest, which has issues with eventlet on python3. I've summarised these in a separate repo (https://github.com/mattbennett/eventlet-pytest-bug) but the short answer is that pytest > 2.7.3 is incompatible with eventlet > 0.17.4.
Along the way I also learned that (irrespective of python version) we can't use coverage on its own (i.e. without pytest-cov) because coverage from tests executed by the testdir subprocess aren’t stored unless they return with 0 status code, and nor can we use pytest-cov > 2.1.0 because it doesn't honour the coveragerc file when used with the testdir pytest plugin. For posterity, I created and then reverted a couple of commits to demonstrate these failures.
There is at least one bug to raise against eventlet/pytest. It may also be considered a bug that coverage isn’t collected in all cases when using testdir, and that the behaviour in pytest-cov changed since 2.1.0. I’ll try to raise these too.
In the mean time I don’t think there’s anything blocking this PR from landing, if you’re happy.

@davidszotten I think this can land now, if you're happy

yep. this is fine. (changelog entry?) 👍


"az acr check-health" with containerd support

Related command

az acr check-health
Is your feature request related to a problem? Please describe.

Yes - sometimes when troubleshooting image pull failures from an AKS worker node, it would be useful to be able to use "az acr check-health" but Docker is no longer present and is a requirement of that command
Describe the solution you'd like

Allow the "check-health" command to operate with either Docker or container
Describe alternatives you've considered

N/A
Additional context

N/A

route to CXP team

@AdamSharif-MSFT Thanks for reaching out to us and sharing this feedback. Could you check if you could use the
https://github.com/Azure/aks-canipull instead ?

@AdamSharif-MSFT Thanks for your time and sharing the details offline. I am pasting the requirement here for the documentation purpose:
Your Ask:

On an AKS worker node you might want to use check-health to try an actual connection to and operation against the ACR, however worker node no longer have Docker and only Containerd – it was just a suggestion really as a “nice to have” for future cases where we troubleshoot AKS worker node ___> ACR connectivity issues.

My Suggestion:
Please try the “az aks check-acr” command. This helps to Validate an ACR is accessible from an AKS cluster. This and aks-canipull tool should be the same.
This “az aks check-acr” command should also work on containerd since it would create a pod with mcr.microsoft.com/aks/canipull:0.0.4-alpha image, and then exchange token with ACR repo. See below:

az aks check-acr --resource-group MyAKSRG --name MYAKS --acr MyACR.azurecr.io
[2022-05-09T08:29:11Z] Checking host name resolution (XXXXXXX): SUCCEEDED
[2022-05-09T08:29:11Z] Canonical name for ACR (XXXXXXX): XXXXX.westus2.cloudapp.azure.com.
[2022-05-09T08:29:11Z] ACR location: westus2
[2022-05-09T08:29:11Z] Loading azure.json file from /etc/kubernetes/azure.json
[2022-05-09T08:29:11Z] Checking ACR location matches cluster location: FAILED
[2022-05-09T08:29:11Z] ACR location 'westus2' does not match your cluster location 'centraluseuap'. This may result in slow image pulls and extra cost.
[2022-05-09T08:29:11Z] Checking managed identity...
[2022-05-09T08:29:11Z] Cluster cloud name: AzurePublicCloud
[2022-05-09T08:29:11Z] Kubelet managed identity client ID: f73b8ef7-XXXXXXX-XXXXXXX
[2022-05-09T08:29:11Z] Validating managed identity existance: SUCCEEDED

Hope this helps.

Hello @navba-MSFT,
Thank you very much, this is really helpful and a great alternative - much appreciated
Kind regards,
Adam


evaluation

hello，how to evaluate the model obtained from DTU dataset? Is there any code for calculating chamfer distance?

Hello，I got the same problem, do you solve this issue?


Update Settings “general”

Automatically generated by Netlify CMS

👷 Deploy Preview for ania-strona processing.

Name
Link

🔨 Latest commit
46f42e557035bd54a183967d276f1c9284c22089

🔍 Latest deploy log
https://app.netlify.com/sites/ania-strona/deploys/625074c85af2690008b822de


Null bytes in protobuf messages sent via unix datagram socket

Hi,
I just noticed that when the service sends a StreamQosResponse with ok = False, an empty packet is received on receiver side.
The reason for that is that protobuf messages are allowed to contain null bytes (and a False boolean is encoded as null byte \0).
Unfortunately, that is also the terminator of a datagram. In the current implementation that probably got unnoticed, because if ok = False the subsequent fields are ignored anyway. However, I still think we should avoid sending raw protobuf messages via unix datagram sockets.
I am happy to provide a fix, but since there are many different options to solve this, I would appreciate your opinion on this topic:

We could further encode the protobuf message to prevent null bytes (e.g. as Base64).
We could avoid using datagram sockets and use stream sockets instead. We would then need a method for separating the messages in the stream again.
We completely avoid protobuf and use another IPC method. One option that you already mentioned in the README would be to replace it by DBus.

What do you think?

Hi!
Ey, good catch! Thanks a lot for your brilliant assessment and proposals to improve the IPC interface!
I would +1 the D-BUS choice. Some comments below.

Linux integration

@vcgomes and @shifty91 also suggested the usage of D-BUS in the past. That would clearly improve the Linux integration, add robustness, and probably benefit from better CVE fix backports in the upstream distributions.
For x86 controllers, we could easily live up with any runtime overhead. But we should definitely keep an eye on the impact for more constrained Linux-based devices. We could always introduce a more modular IPC interface if users require it.

Built-in SCM_RIGHTS

Another plus -if I am not mistaken- would be the built-in D-BUS support to pass fds. The current interface performs the resource management and system configuration, and provides the caller with the necessary information to perform the AF_PACKET socket initialization.
But there is already demo code performing the initialization in the privileged entity, and returning the fd via SCM_RIGHTS. See test_service_add_talker_socket in test_service.py      https://github.com/Avnu/detd/blob/dc8c1e7956c31057bca77901bfee15d43bb705e8/tests/test_service.py#L134
The intention would be to aim for something similar in the AF_XDP case, so we can introduce some privilege separation between resource management and user applications. @magnus-karlsson @garyloug is there any pointer to existing code that we could check in order to define the right API between the privileged entity and the user application when using AF_XDP?
I am not suggesting to address this with the initial port, of course :) First we should move to D-BUS, and then let us look into the new improvements possible.

Developer documentation

IMHO D-BUS XML interface definition is busier and more intrincate than protobuf's IDL. So it would be great to provide developer documentation generation, for human-readable IPC API docs.
Later we may easily add support to generate internal API and even a couple of diagrams built from the code. I have experimented with pandoc, pyreverse and plantuml and the result is ok.

ok vs status

The intention of the "ok" field was just a quick and dirty way to handle errors between privileged and user entities. So we can catch the error on the client side, and then look into the log for details.
For the programmatic interface, it may make sense to provide additional details about the failure to the client, e.g. with a numeric "status" field.
After the initial port, we may also look into this change.

Dependencies

I have a few docker-based build environments ready, and hope to get through the release process ASAP. By calling a bash function per distribution, they copy the code in your local repo to a container with the build deps, generate the deb, and then copy it to the host filesystem.
As they install the build-deps, it may make sense that we merge the build envs first, and then the D-BUS port, including the required changes to the docker-based build and deb packaging script.

Schönes Wochenende!

There was a C-based example in samples/bpf/xdpsock_ctrl_proc.c and xdpsock_user.c in kernels prior to 6.0 (I removed it in that release). Do not know if that will help you. If you are looking for a higher level example, maybe  @garylough has something?

Thanks a lot for providing these details!
Sounds very reasonable to wait until your upcoming release before implementing it. I am looking forward to the release and will have a look again after that.


Remove unreachable bad return statement

The first return statement seems to match the expected outcome; removing the second one which causes warning in browser console about unreachable code.

Thanks for fixing this!

I will publish a new version later in the evening.

New version (1.3.3) published to npm

Thanks!


add README.md for empathy

The foundation of design thinking is determining the customers needs and creating an MVP that can create a solution.


Products with baseline 02.09

Using Jupyter Notebook "AWS Request.ipynb", I have received the following warning message.
"SHUserWarning: Products with baseline 02.09 are not officially supported in sentinelhub-py. If you notice any errors in naming structure of downloaded data please report an issue at https://github.com/sentinel-hub/sentinelhub-py/issues. Pull requests are also very appreciated"
Please help me to resolve.

Hi @enzopolo
ESA processing pipelines for producing L1C/L2A/... data are changing through time, and unfortunately, some of the presumptions about the structure of .SAFE files change with them. Baseline 2.09 is one such version of .SAFE formats. The warning you received in the notebook is telling you that the product the code is trying to unpack is not supported.
In order to understand the problem, we (or anybody willing to work on this issue) would need at least some more information (e.g. which product did you try to read). As we cannot commit to support all all of the baselines, we are also asking users (in the warning itself) to contribute back to code with pull requests solving the issue at hand.

@batic Trying to reconstruct .SAFE folders from requested product ids in France, also produces the same warning (2.08) for some of them.
Can you please enlighten us, what does this mean?
Is the inner folder structure not properly re-constructed?
Will files be missing?
I heavily rely on folder structure and band metadata for later processing. So knowing what might be off, could help a lot.
Thanks!

As written in the comment above, this is due to changes/differences in ESA processing pipelines.
We (Sentinel-Hub) unpack the .SAFE files when copying them to AWS, and rename them to be consistent throughout the whole S-2 archive. The function implemented in the sentinelhub-py tries to reconstruct the unpacked/renamed files from AWS into the .SAFE format, but not all baselines are supported.
The "Pull requests are appreciated" means that the user would try to understand what doesn't get correctly reconstructed into .SAFE format for that particular baseline. That would generally mean one would have to:

download that particular .SAFE file directly from ESA
compare it to the result from sentinelhub-py
fix the issues

Note that nothing should be missing on AWS, it is just the reconstruction algorithm that needs tweaking.
Hope this helps and looking forward to your contributions ;)

Solved in the newly released version 3.5.0.


Log layer design

My idea is to build a minimalistic logging layer build on top of logrus, having the ability to use a default logger (used by core vinxi package) or alternatively use custom loggers.
In order to make it very simple to use, I think the package should expose a singleton style logger interface, such as (log package consumer side):
import "gopkg.in/vinxi/log.v0"

func main() {
  log.Printf("Write something: %s", "foo")
  log.Debug("Debug message")
  ...
}

From the other side, developers should be able to build and reuse custom loggers with custom formatters and listeners. Possible example:
import "gopkg.in/vinxi/log.v0"

var logConfig := log.NewConfig(...)
var myLog := log.New("myLog", logConfig) // implicitly registered

func main() {
  myLog.Printf("Write something: %s", "foo")
  myLog.Debug("Debug message")
  ...
  // Or you can also retrieve the previously created logger
  log.Logger("myLog").Warm("Got it")
}

@groyoh What do you think?

var myLog := log.New("myLog", logConfig)
Would you have to do that for every file or just once the main file?
Also, can you only pass the config for the logger or can you pass a custom logger itself?

If using the generic built-in logger, you won't have to do never, just import tha package.
If using a custom logger, only have to do once time.

Generic logging layer is done. We could consider implementing a logger global store as I described above in order to easily register and fetch logger instances from other packages without the instantiation boilerplate.
My opinion is that we could support that in the future when we actually need it more. Should be trivial to support anyway.


SI-4694 bugfix: correctly detect endianness at compile time if possible

..., #error if endianness cannot be detected at compile time, delegating the detection to configuring the build system to indicate the endianness through #defines

That it a much better, and more correct way of doing this. But perhaps we also need to detect if the __ORDER_LITTLE_ENDIAN__ and the __ORDER_BIG_ENDIAN__ are defined?

I thought about it.... Maybe I should update the PR with this and allow specifying the endianess with a pre-processor macro so that if (when) we encounter a compiler that fails on these tests, we can simply update the build system instead of revisiting this to include this new compiler corner-case.
Thoughts ?


The extension is incompatible with the current GNOME version

when I update to GNOME 43.1, the extension is show "The extension is incompatible with the current GNOME version", and app.conf is not work.

The text "The extension is incompatible..." sounds like you have installed some GNOME extension? Where do you see that text?

Try editing ~/.local/share/gnome-shell/extensions/keyd/metadata.json and add to the shell-version list. I'm unsure if you should add "43", "43.1" or both. Log out and in and see if things are OK.

think you.

Can someone confirm that the latest commit works without modification? (preferably by running rm -rf ~/.local/share/gnome-shell/extensions/keyd first)


📝 docs: add read* functions with cleanup

The following actions have been added to the docs:

getSecondsToFinalizable
readFinalizedWithdrawals
readProvenWithdrawals

Along with some other minor cleanup.
Resolves #82

@Sabnock01 I think there's a conflict with your other PR that went in


Unable to access a collection: Unexpected end of JSON input

Hello, we are currently maintaining a site using Gatsby.js and Netlify CMS. Last week the CMS started failing to load a collection(file collection) of pages returning the error: Unexpected end of JSON input. We are getting the error on mediaLibrary.js and entrie.js resulting in the CMs not loading that collection. This issue only happens when we run the project locally, on production the CMS is working as expected.
Describe the bug

we have a site with a collection named pages
we have a site with over 1000 images
we are using bitbucket as the backend
mediaLibrary.js and entries.js fails with the Unexpected end of JSON input error, hence those collections are inaccessible

Applicable Versions:

Netlify CMS version: 2.14.3
Git provider: Bitbucket
OS: Mac OS Catalina

Node.JS version: 12+

CMS configuration
init({
    config: {
        slug: {
            clean_accents: true,
        },
        backend: {
            name: 'bitbucket',
            repo: [our-repo-name],
            branch,
            cmsLabelPrefix: branch,
            auth_type: 'implicit',
            app_id: process.env.NETLIFY_APP_ID,
        },
        media_folder: 'static/uploads',
        public_folder: '/uploads',
        publish_mode: 'editorial_workflow',
        local_backend: env === 'local',
        collections: CMS_COLLECTIONS,
    },
});

I appreciate it if you guys could help us figure out this error, we have been trying to debug it ourselves but we haven't found what is causing those errors to throw. If you need more information I'll happily add it.
Regards

Yes, more information is definitely needed. There was this section in the issue template, that you skipped
**To Reproduce**
<!--
Steps to reproduce the behavior. For example:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
-->

please provide runnable example where this issue can be reliably reproduced.

Hello guys, we will work on creating a repo with the error so you guys can run it. Thanks!

Hello guys and sorry for the delay:
Here https://github.com/jfgamez/error-netlify-CMS you can find a repo with a reproducible error. We created a repo with over 600 images resulting in a size of more than 400mb, whenever this happens, the CMS fails to get the media.
We created a script that generated different sizes and numbers of images and identified that the issue was not given by the number of images but rather the size of the folder.
To Reproduce

Download repo and install dependencies
Run yarn develop:local-cms
Access the CMS admin
Open the console
Navigate to the collection of the pages and select Home
Check the API errors in the console

I expect this is useful for you guys, please let me know if there is anything else we can do to help solve this issue.

Well, this is happening because node can't handle large json objects
https://github.com/nodejs/node/issues/35973
https://github.com/nodejs/node/issues/9489
@erezrokah why do we need to base64-encode all the images? Why can't they be just loaded from their URLs?

@erezrokah why do we need to base64-encode all the images?

We do that in several places. Which one are you referring too? We don't keep image URLs since that doesn't play nice with private repos (some contain a token that expires after a few minuets hence the usage of URL.createObjectURL() to get an object URL).

I'm talking about getMedia endpoint. Do you have any idea how this issue can be solved? When there are many images or images are big enough, the resulting JSON is huge and it exceeds node's maximum string length.

For the local proxy backend we might be able to drop the base64 encoding/decoding. Not sure for other backends if they support reading raw bytes.
As a general approach maybe something like https://github.com/discoveryjs/json-ext? That would require some more research

Hello guys,
Just to follow up, is there something we c ould help to keep this conversation going and help to fix the issue?

Hi @xtatanx, I think we have all the info we need, it's just the solution requires some effort.
Another possible approach would be to implement pagination for our local backend (this is what we have for the other backends - that is mostly dictated by the git service providers).

Just stumbled upon this myself. This issue makes it impossible to use netlify-cms with big images. @erezrokah have you thought about how to fix it?

Just stumbled upon this myself. This issue makes it impossible to use netlify-cms with big images. @erezrokah have you thought about how to fix it?

This requires more research and I don't think there's an easy fix for it.
If you're will to use an external service, Cloudinary should work well.

Well, I think it's only relevant for a proxy backend. So, maybe it's not that big of a change and research?

Well, I think it's only relevant for a proxy backend. So, maybe it's not that big of a change and research?

Oh right, so I think implementing pagination here https://github.com/netlify/netlify-cms/blob/6d801ae092a6763bd751cb82bd238c7c12b31884/packages/netlify-cms-proxy-server/src/middlewares/localFs/index.ts#L92 would be a good start.

You said before that it might be possible to drop the base64 encoding/decoding completely

You said before that it might be possible to drop the base64 encoding/decoding completely

Yes, but I think that without pagination it will only defer the problem.


Replace cumsum broadcast with accumulate

Tests a single change from #470

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.02%. Comparing base (21fb991) to head (86af1a7).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #472   +/-   ##
=======================================
  Coverage   90.02%   90.02%
=======================================
  Files          57       57
  Lines         742      742
=======================================
  Hits          668      668
  Misses         74       74

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

So this has a different pattern of impact vs #470.
Here I see slower evaluation and forward diff, no real impact on reversediff with compilation and much faster reverse diff.
Is this due to a specialisation that exists for accumulate do we think or other?
I think this one is worth changing given these results (this makes me want to get Enzyme and Tapir into the benchmarks asap)

Is this due to a specialisation that exists for accumulate do we think or other?

This is possible, but cumsum calls down to accumulate! which I'd imagine has similar things happening.
My mental model was that accumulate saves either a broadcast sum or a vcat by using the init keyword arg... but I'm not sure thats the win I thought it would be now.

I've refreshed this test with the xexpy based function committed on main by #473

This is still ambiguous: some cases worse, some better.
As per f2f discussion with @seabbs I think that mean not going forward with this unless we get extra evidence. For example, if in a realistic inference exercise some kind of extra sampling stability improves sampling overall even if individual primal+grad calls are slower.


[BEAM-8575] Add a trigger test to test Discarding accumulation mode w…

…ith early data
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---

---
---

Java

Python

---

---
---

XLang
---
---
---

---
---
---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website

Non-portable

Portable
---

---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

@robertwb Hi Robert, this PR is a test case to cover early data with Discarding accumulation mode using the test suite you added:) May I get your review? Thanks!

Run Python PreCommit


Setup Laravel Sail

I wanted to get the project running locally, but didn't want to install everything manually on my machine, therefore I started to work on adding some docker for local development.
Initially I went with a custom docker solution (which I used on a different project), but then I realized that we have Laravel Sail which solves the problem I was having, and it has great docs.
I wanted to keep it clean and simple, but unfortunately I was forced to publish sail's docker files so that I can add chrome which is required for puppeteer.
I'm up for working more on this if needed, like cleaning up the code or writing up some docs.
Thanks

This is great! One remark though: could you remove the 8.0 and 8.1 configs, as this project only runs on 8.2?

Sure, removed those configs and docker files.

Awesome! Thanks :)


MacOS Javascript Error

I get the following error after opening the app.

Also seeing this on 2.0.0 and 10.14.5

I fixed this by recursively changing the permissions on /Applications/Android Messages.app to [my_user]:staff instead of root:wheel
MBP:~ bgreen$ sudo chown -R bgreen:staff /Applications/Android\ Messages.app/

A similar error on my end:
Uncaught Exception:
Error: EROFS: read-only file system, open '/private/var/folders/48/7zsx1c294zv9m42pc1lz8_m40000gn/T/AppTranslocation/E1322FF5-361E-4DC0-B60D-843D9D8FCB2F/d/Android Messages.app/Contents/Resources/resources/dictionaries/supported-languages.json'
    at Object.openSync (fs.js:436:3)
    at Object.module.(anonymous function) [as openSync] (ELECTRON_ASAR.js:160:31)
    at Object.writeFileSync (fs.js:1168:35)
    at WriteStream.Array (/private/var/folders/48/7zsx1c294zv9m42pc1lz8_m40000gn/T/AppTranslocation/E1322FF5-361E-4DC0-B60D-843D9D8FCB2F/d/Android Messages.app/Contents/Resources/app.asar/app/webpack:/src/helpers/dictionary_manager.js:69:71)
    at WriteStream.emit (events.js:187:15)
    at lazyFs.open (internal/fs/streams.js:273:12)
    at FSReqWrap.oncomplete (fs.js:141:20)

I fixed this by recursively changing the permissions on /Applications/Android Messages.app to [my_user]:staff instead of root:wheel
MBP:~ bgreen$ sudo chown -R bgreen:staff /Applications/Android\ Messages.app/

That fixed it!
Hopefully, this fix can be incorporated into the next update.

@purevertigo @greenbp @EXYZED @timcappalli
Hey all, this should now be fixed in v3.0.0 which I just released. This bug was a side effect of me not storing certain files in the right directory.
For some background, when the app opens, it asks your OS what language it should use and then downloads the spelling dictionaries for that language (if available) as well as a JSON file which lists the languages available to download. It is done this way because if I were to include these files in the app, it would about double the size of the output files (.exe/.dmg/.deb etc).
The problem was I had programmed the downloads to go into the Electron resources directory (where things like the icons are), but Electron intends this directory to be read-only. The correct solution is to use the userData directory provided by Electron which is safe to write to.
Please download v3.0.0 and file a new issue if you encounter something wrong. Apologies that this took so long and thanks for using the app!


MobileBERT tflite int8 model seems not follow quantization spec

The model downloaded from https://github.com/fatihcakirs/mobile_models/blob/main/v0_7/tflite/mobilebert_int8_384_20200602.tflite
Some Fully-connected weights has none-zero zero point (ex. weight bert/encoder/layer_0/attention/self/MatMul19 has zero-point = 6) , which violate the TFLite quantization spec.
I am afraid this might cause issues on some implementation which bypass the FC weight zero-point calculation.

@rednoah91 Why are you using https://github.com/fatihcakirs/mobile_models vs https://github.com/mlcommons/mobile_models?

@mcharleb The mobileBERT model in  https://github.com/mlcommons/mobile_models points to https://github.com/fatihcakirs/mobile_models. They are the same.

The model downloaded from https://github.com/fatihcakirs/mobile_models/blob/main/v0_7/tflite/mobilebert_int8_384_20200602.tflite
Some Fully-connected weights has none-zero zero point (ex. weight bert/encoder/layer_0/attention/self/MatMul19 has zero-point = 6) , which violate the TFLite quantization spec.
I am afraid this might cause issues on some implementation which bypass the FC weight zero-point calculation.

This model was provided by Google as QAT model, approved for use by the mobile working group


Kotlin/Android counterpart

Hello,
Wondering if you guys could help out with a question:

Are aware of any implementation or
Any reason/blocker why there isn't

a Kotlin/Android version of this awesome tool
For reference, we did ask on SO but got no answer:
https://stackoverflow.com/questions/49031599/rxswift-like-actions-for-android

Hi there 👋 I'm not aware of any ports, but I have nearly zero visibility into the Android ecosystem. If you've looked wherever Android dependencies are collected and can't find one, there probably isn't one yet. Maybe open an issue on https://github.com/ReactiveX/RxKotlin or https://github.com/ReactiveX/RxJava to ask?
I don't think there's any technical reason why a port wouldn't work but again, I'm not familiar with those languages. This library is itself a port of a class from ReactiveCocoa, which is an Objective-C library. So porting the "Action" abstraction across languages has precedent. I would imagine no one has done it yet simply because no one has thought of it. I'm sure you'd be able to write out a successful port with some time and patience.
Good luck, if you do manage to find something or write something, please drop us a line to let us and others know. Good luck!

Hey @ashfurrow 👋,
Thanks for your feedback and tips, I guess the solution is to write it out, I will write back if I get any update(s)
Thanks 💪

Hello again @ashfurrow 👋
Just published v0.0.1 🎉. Decided to call it KAction since is written in Kotlin ❤.
Check it out when you have a moment:

https://github.com/tonsser/kaction

That's so cool, congratulations! One note: in the readme, you say SwiftCommunity instead of RxSwiftCommunity. But yeah, excellent work!
Are you comfortable closing this issue?

Terribly sorry or that!
I've fixed it: https://github.com/tonsser/kaction/commit/91b001250a5a55aec4f071ef96381970d7d45f68
Once again thank your time and this awesome tool, we rely on it @tonsser!
💪


Posts from external timeline don't open in sidebar

Describe the bug
I added a shortcut to a local timeline from an external instance (https://mastodon.la/). It works great (thanks, it's great feature!) but when I click on posts in that column they don't open up in the sidebar.
On the dev version I get an "Unable to process URL" error.
Example post:
https://phanpy.social/#/https://mastodon.la//s/110216039553116745
https://dev.phanpy.social/#/https://mastodon.la/s/110216039553116745
(Post on the instance: https://mastodon.la/@giorgiograppa/110216039553116745)
To Reproduce
Steps to reproduce the behavior:

Create a shortcut of a local instance (might be specific to https://mastodon.la/)
Click on any post.
In the production site, nothing happens. In the dev site, get an "Unable to process URL" error.

Expected behavior
The post should open in the sidebar.
Desktop (please complete the following information):

OS: elementary OS 6.1 Jólnir uilt on Ubuntu 20.04.6 LTS
Browser: Tested on Firefox
Version: Firefox 112

Awesome. The workaround worked :) THanks!

Field validation added now on production site. Closing this for now.


conserver-server: add more missing high baud rates

For as long as we support fixed baud rates fill in more gaps left
after e7ca230c2239735d1b4c05747da8efbbae2fb547 supported by various
operating systems.

These baud rates are already listed in the master branch.


Apparent Bug

greetings kind regards
please see attached image . it is the result of testing bits::shift_left . there seems to be an error w/said routine . std::bitset is utilized as a reference . i am uncertain as to meaning of "offset_bits" argument . from brief study of code it seems to be the number of lower bits to not shift , the tests utilize a value of 0 . also attached is the test code for purpose of reproduction .
thank you kindly
main.cpp.txt

Thanks for that. I'll look into this. I didn't test it directly I'm ashamed to say. I tested via my bitmap code in my graphics library, which it seems to work for, so I'm thankful for your repro. I'll get to it when it cools off some here and I can think. Thanks again!

greetings kind regards
i seem to have finally gotten my own left shift code to work w/o error . it is attached if you would like to have a look at it . also the attached code rather thoroughly tests mine and htcw code . i am surprised it reports no errors of mine but am even more surprised and am sorry to say reports quite a large number of htcw errors . perhaps i am in error as to how to utilize htcw code .
kind regards
main.cpp.txt

Thanks for all that. bits requires C++14 or C++17 to compile, and should work with MSVC2022 or later. If you're getting errors after that, it must be something with your compiler settings?

Greetings & Kind Regards
I am sorry but I must find great fault w/ the bits::shift_left code.
Please permit me to elaborate.
re/ line 498 *pdst = (src << shift_bits) | (src2 >> (8 - shift_bits));
I can not comprehend why it is affecting the lower order byte w/ the value in the next higher byte whilst performing a left shift.
re/ all the code from line 492 to end of routine
It seems to be unconcerned w/ the intermediate bytes other than the lowest order and highest order w/ the presumed possible result the transfer of bits from a lower order byte to the next higher byte does not occur.
re/ line 504 --pend;
is pend to be utilized? it does not appear further.
By the way the previous file I provided contained an error. I provide it again w/ the correction.
As for compiler settings I never fiddle w/ those as I know little re/ same. However it is C++20.
main.cpp.txt
Kind Regards

Hello again. Sorry to trouble your kind self. May I please inquire does bits assume large endian. I tested assuming little.
Thank You Kindly

Greetings & Kind Regards
May I suggest a simple test of bits::shift_left as I am now convinced it is not correct. Attached please find my own result of such a test and the test values. On the face of it it seems to shift in 1s instead of 0, which I believe is not the correct procedure. However that is not how that extra 1 got into the lower byte. It got there because it is being or'd via the upper byte in line 498 for reasons I can not comprehend.
Kind Regards

I'm just going to have to rewrite the whole thing, and then regression test my graphics library that uses it. I haven't gotten to it yet part because I was visiting my family yesterday. Thanks for all this.

Greetings & Kind Regards
May I suggest utilizing my own version also my test code. I would be honored if your kind self would even consider such.

I'd have to modify it first, as I need the offset bits parameter - it needs to be able to shift on non-byte boundaries. But I'll take a look at it, thanks.

Greetings & Kind Regards
May I inquire have you investigated further the behavior of your bit shift code. Is it in fact in error. If in error and not yet repaired I humbly offer my paltry services to re-write my own code so as to operate on non-byte boundaries.
Kind Regards

I haven't yet, sorry


"Webview: Cannot load resource outside of protocol root", if .md source is an network share

if a markdown file is located on a network share, images ![test](./2019-10-30-10-04-55.png) can not be loaded in preview.
Same folder on the local filesystem work fine.

Console display the error
webviewProtocols.ts:27 Webview: Cannot load resource outside of protocol root

e.session.protocol.registerBufferProtocol
@
webviewProtocols.ts:27

async function (async)

e.session.protocol.registerBufferProtocol
@
webviewProtocols.ts:19

apply
@
C:\Users\adbase2\App…acks-registry.js:47

handleMessage
@
C:\Users\adbase2\App…r\api\remote.js:285

ipcRenderer.on.args
@
C:\Users\adbase2\App…r\api\remote.js:275

emit
@
events.js:182

Version: 1.39.2 (user setup)
Commit: 6ab598523be7a800d7f3eb4d92d7ab9a66069390
Date: 2019-10-15T15:35:18.241Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17134
Steps to Reproduce:

create a markdown file with images on a network share.
markdown file and image are in the same notwork folder.
open preview

Does this issue occur when all extensions are disabled?: Yes

I am starting working on this one


Rate limited when attempting to upgrade Amplify CLI

How did you install the Amplify CLI?
npm -g i @aws-amplify/cli
If applicable, what version of Node.js are you using?
v16.13.0
Amplify CLI Version
10.6.0
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug

Expected behavior
Amplify package upgrades to the latest version
Reproduction steps

Have 10.6.0 installed
run amplify upgrade
profit?

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Marking as a bug to reevaluate this strategy for checking updates when working behind a corporate VPN (or in an AWS EC2 instance, for example) blocks our ability to upgrade the CLI with amplify upgrade
As a workaround, please use the Node.js package manager of choice to update the CLI.

Marking as a p3 bug to improve error messaging when running into 403's from GitHub's API


Added Codecov.io coverage reporting

Hey Friends! I'm from Codecov.io and I wanted to personally add our free coverage reporting tools to PhotoView.
When travis-ci passes you can see the live reports here: codecov.io/github/chrisbanes/PhotoView

Make sure to signup to enable these free features
I'm excited to hear your feedback!
Thank you for your time.

We are not interested, than you.

Thanks for reviewing :) Have a nice 2015!


Pass parameter in Route

Passing a path parameter doesn't seem to work.
For ex: Based on id it needs to fetch different kind of data so in that case passing as path parameter would be easy.
Lmk if there is some other way to achieve it.
Sample Code
const DefaultApp = () => (
  <Container>

Report App

    67 Test
  </Container>
);

const App = () => (
  <BrowserRouter>
    <Route path="invoice/:id" component={Invoice} />
    <Route path="" component={DefaultApp} isDefault />
  </BrowserRouter>
);

https://github.com/PejmanNik/jikji/assets/17666778/eac4c5fe-482f-4109-b676-0ce2d2e871ff

The router component is very simple and just exists to cover the basic usage without a third-party library, as this library attempt to handle reports I don't want to focus on routing, there are several advanced router components for React you can use. for instance react-router

The router component is very simple and just exists to cover the basic usage without a third-party library, as this library attempt to handle reports I don't want to focus on routing, there are several advanced router components for React you can use. for instance react-router

Thanks

No problem 👍


Downloading data

The current wget command doesn't work. The site where the data is needs to be changed.
Error message in lambda:
--2024-01-11 09:05:32--  ftp://ftp.mcs.anl.gov/pub/candle/public/improve/benchmarks/single_drug_drp/benchmark-data-pilot1/csa_data
  (try:11) => ‘./.listing’
Connecting to ftp.mcs.anl.gov (ftp.mcs.anl.gov)|<IP_ADDRESS>|:21... connected.
Error in server response. Closing.
Retrying.

Updated the README to:
wget --cut-dirs=8 -P ./ -nH -np -m https://web.cels.anl.gov/projects/IMPROVE_FTP/candle/public/improve/benchmarks/single_drug_drp/benchmark-data-pilot1/csa_data/


MAINT: Performance optimization

This PR reduces the number of SQL request issued in particular when loading analyses. The goal is to reduce load times for large surface twins that can be around 30 seconds.
The strategy is to avoid nested serialization, i.e. return ids of nested datasets and have the frontend load if required. In particular for datasets with many measurements this can be a bottleneck, as each measurement incurs an SQL request to load the complete measurement model, but most of that data is actually not needed by the frontend.

We should also try to avoid generic relation, I've opened an issue here #1014


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit 486360c:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-11-21-08-59-37 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Archive_master_2019-11-21-08-59-37

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


Log format shouldn't be read from environment variable

Log format should be basses as helm parameter or be read from config map.
https://github.com/dell/csi-baremetal/blob/2aff329efef43e13c4cd90f3a0377dba2c6ca733/pkg/base/linuxutils/lsblk/lsblk.go#L91-L95

Currently we have different approaches in different components. Need to do unification.


Text bounds fix and additional options for Baseline

Thank you a lot for your work! It would be better to split pull requests by task. There are three different tasks in this request:

Fix of #241. This one is good, with a pull request I can quickly check and apply it.
Documentation. It's a good start, but it will require some iteration to describe all necessary parts, so it will be good to keep progress in one independent pull request.
Model changes, i.e. perfectTop/perfectMid/... This one is tricky, I'll provide you more details in the corresponding ticket #242.

Ok. I will create two new pull requests, one for fix #241 and for the Documentation I will create a new branch and there I can add my DocStrings step by step (but this needs time, I still do not understand everything in Macaw, luckily the code is very vell readable!)


fixed incorrect command option

removed extra  -- from the command to work properly

Npm requires these dashes, so I'm afraid your PR is not valid.

@cpojer In my case, it didn't work with dashes, in-fact it worked without them

@scazzy -- is a bash convention signifying the end of options. In npm's case arguments before the -- are options passed to npm itself, just as if you'd written them into .npmrc (and note npm silently ignores options it doesn't recognise).
Options after the -- are passed through to the command you've requested, so npm invokes the start script with the --reset-cache argument appended (in this case node [...]cli.js start --reset-cache).
You can see the difference between the two if you look at the second/third line of npm's output, where npm shows the node command it's about to execute.


set debit/credit via magic methods

Added three examples (for money creation)
One bugfix: using asset or liability accounts was checking whether the balance was on the correct side (debit/credit, respectively), which failed when the balance went to 0 (account side balanced). Instead I am now checking whether the balance doesn't go to the wrong side.


Unable to get key and credentail for swish certificate

Everything works fine on testing data.
I have created a certificate from swish portal but how do i get key and password of it.
I couldnt find anything in documentation.

@zeeshan0080 For the Merchant Swish Simulator (MMS) the key will be provided in the downloadable and the password is "swish" for all files (read more here: Swish Certificates).
Unfortunately if you want to try this on production data and have generated your own certificates from the Swish portal, you must contact Swish support for help on how to find your personal key and password (this can be done here: Swish Support).
If you believe this is a bug or missing feature you are more then welcomed to try and solve it with a pull request 🚀

@zeeshan0080 For the Merchant Swish Simulator (MMS) the key will be provided in the downloadable and the password is "swish" for all files (read more here: Swish Certificates).
Unfortunately if you want to try this on production data and have generated your own certificates from the Swish portal, you must contact Swish support for help on how to find your personal key and password (this can be done here: Swish Support).
If you believe this is a bug or missing feature you are more then welcomed to try and solve it with a pull request 🚀

Got my key and password and now it gives this error on createpaymentRequest method:
[ERROR:flutter/lib/ui/ui_dart_state.cc(198)] Unhandled Exception:
E/flutter ( 6937): 	BAD_DECRYPT(e_aes.c:1090)
E/flutter ( 6937): 	DECRYPTION_FAILED_OR_BAD_RECORD_MAC(tls_record.cc:298) error 503316581
E/flutter ( 6937): #0      IOClient.send (package:http/src/io_client.dart:66:7)
E/flutter ( 6937):
E/flutter ( 6937): #1      BaseClient._sendUnstreamed (package:http/src/base_client.dart:93:32)
E/flutter ( 6937):
E/flutter ( 6937): #2      SwishClient.createPaymentRequest (package:flutter_swish_payment/flutter_swish_payment.dart:576:30)

@zeeshan0080 Amazing 🔥
In order to actually make a transaction the api url must indeed be updated to production mode.
This is not a feature yet in this package, but fear not since the change is quite simple. I suggest you open a pull request for it and become a contributor too!
In order to make it work i suggest the following changes:

Add a optional flag in SwishAgent indicating that this agent should use the dev api (and default the client to prod if no flag is provided). Final initialization for dev should look something like this (and for prod no flag):

SwishAgent swishAgent = SwishAgent.initializeAgent(
    key: key,
    cert: cert,
    credential: credential,
    environment: 'dev',
  );

Change createPaymentRequest to depend on the environment flag provided from the SwishAgent so that this hardcoded dev api url becomes dynamic in the function:

      ...
     // TODO: Change this string depending on environment
      Uri.parse(
        'https://mss.cpc.getswish.net/swish-cpcapi/api/v2/paymentrequests/' +
            swishAgent.instructionUUID,
      ),
     ...
);

Production api urls can be found here: Swish Environments
Flutter Swish Payment is under constant development, only through the collective efforts of the Swish community can this project be taken from a proof of concept to a final open source package ❤

Will do if i get it to working. Right now i'm having parsing errors on api response.