Increment version for core releases

Increment package version after release of azure-core

Don't merge this yet, the pipeline failed (no release tag/no docs/no vcpkg).


[FLINK-14362][runtime] Change DefaultSchedulingResultPartition to return correct partition state

What is the purpose of the change
This PR makes a clearer definition of ResultPartitionState as:

CREATED // partition is just created or is just reset
CONSUMABLE // pipelined partition has data produced or blocking partition's parent result finishes. Corresponds to IntermediateResultPartition#isConsumable.

The DefaultResultPartition is also fixed to return ResultPartitionState based the true partition state, rather than the vertex state.
Brief change log

Refactored ResultPartitionState
Fixed DefaultResultPartition

Verifying this change
This change added tests and can be verified as follows:

Adjusted unit tests for DefaultResultPartition and  DefaultExecutonTopology

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Rebased onto latest master for the hotfix for docs.

Rebased onto latest master.

Merging.


translate didn't work

So I type “tr work" and it shows nothing.

same here!

same as others

same!

Google translate changes it's service and only send back a single word.
One way to fix is remove everything after get_page = json.loads(get_page) and add
    print '[' + get_page + ']'
    print 'command=copy'
    print 'icon='
    print 'subtext='

thx!
2016年6月2日 下午3:40于 Chao Xu<EMAIL_ADDRESS>
Google translate changes it's service and only send back a single word.
One way to fix is remove everything after get_page = json.loads(get_page) and add
print '[' + get_page + ']'

print 'command=copy'

print 'icon='

print 'subtext='

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@chaoxu thanks for your reply, just which file should be edited?

config/scripts/googletranslate/google_translate.py

For those who are looking for final script, you may find the final script here. https://gist.github.com/samundra/d07bd2e312f7c3d0b65de4b68c91b22d
Don't forget to change the target language to your own liking.

I've already change the code as @samundra  said above. It still doesn't work.
I type in the terminal
$ mutate
and try "tr work"
and I see the errors as below
  File "/home/yb/.config/Mutate/scripts/googletranslate/google_translate.py", line 51, in <module>
    response = urllib2.urlopen(response)
  File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
    return opener.open(url, data, timeout)
  File "/usr/lib/python2.7/urllib2.py", line 435, in open
    response = meth(req, response)
  File "/usr/lib/python2.7/urllib2.py", line 548, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python2.7/urllib2.py", line 473, in error
    return self._call_chain(*args)
  File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
    result = func(*args)
  File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 403: Forbidden```
thx a lot

@YanB25 The response has 403 Forbidden error.
This could possibly be due to various reasons. Finding the root cause needs more debugging. However you can start to debug from there. For reference see https://stackoverflow.com/questions/5871710/translate-url-with-google-translate-from-python-script


Can't ssh to any deployment on qanet

Description
Qanet, 2.2.0-rc2.
I can't ssh into any of my deployments. I have tried many deployments with different solutions, different nodes, and different accounts, but I have not been able to ssh into any of them.
In the image below, I tried deployment on nodes 2 and 3.

and on public ips?

Both public and ygg ips

and on public ips?

Both public and ygg ips

@xmonader can not make any deployment now with or without public ip

and on public ips?

Closing issue as it wasn't the network problem but it was a Ygg version problem.
and the solution was https://forum.threefold.io/t/yggdrasil-upgrade-action-required/4124.


[Question] How do you correct disk warnings on hosts?

Warning Message
"the disk xxx has xxx available, but requires reserved xxx, minimal 25% to schedule more replicas. "

Just not sure exactly what to do with this warning message.
What causes this warning?  Is it just to much allocated?  If so,  can I tell the system to reduce what that drive can take?

Follow up,  the message is now gone.   Which is good.  I did not do anything to remove it.
My concern is still there though.
What happens if it comes back and do I have something miss configured.

Hi @BringerOD,
Sorry for the late update. For your questions.
I thought the original warning message tips users to know that the disk is on low capability.
(we need to keep some space for replication due to thin-provision design)
For the second picture, Longhorn (Harvester volume backend) has some mechanism to release the disk space by cleaning up the system snapshot, orphaned data, or backing image  I am not sure how your system status (like pods, nodes status) but release some disk space is respectable.
Hope the above information would be helpful for you :)

Thanks for the response!
One of the issues I have is I have 4x900GB drives each separately provisioned.  I am not sure how longhorm\harvester decides where data goes,  and why it would chose one drive over the other.
Reading through some of the docs,  I think it suggested I combine all the drives.  Is that true?
Do you have any suggestions on how to configure the drives in this scenario?  Are there any docs on what the best practices are?

The logic how do distribute the data between drives is based on the logic Longhorn has implemented.
In case I understand this right - the data distribution should be more or less „automatic“ and Longhorn could even be configured to re-distribute data automatically.
Combining the disks would be possible in case you have a raid controller in the server - then you could i.e. build a RAID 5 out of the disks and present only one drive.. but yes - this would reduce capacity.. an other option (maybe complex to be done with Harvester) would be to combine the drives in a LVM VG - but that would also have a potential single point of failure in case one of the disk fails.
So - for the time being - do you still see a problem with one disk running out of available disk space?
P.S. Longhorn does not support sharding - so having very large volumes also can cause a challenge in case a single disk does not have enough capacity left and that might also cause not all disks having the same usage - see also https://github.com/longhorn/longhorn/issues/1061

@Martin-Weiss thanks for your help here.  Is there a guide on how to combine the disks.  It makes sense to combine the drives,  especially if it has a replica.
Do you combine the drives before you install harvester?  Or can you combine them after it is installed.  I am not that great at disk management on linux.  Conceptually I get it,  but do it is anther thing.
The problem I had today was I had a 500gb volume and it failed.  It was 800gb + on disk,  and there was not space left.  The replicas failed.  Lost the whole volumne.  I have to find a solution to it.
My plan was to restore,  but restore is not working either.

@Martin-Weiss thanks for your help here. Is there a guide on how to combine the disks. It makes sense to combine the drives, especially if it has a replica.

I prefer "combining" disks with a hardware based RAID controller.

Do you combine the drives before you install harvester?

Yes

Or can you combine them after it is installed. I am not that great at disk management on linux. Conceptually I get it, but do it is anther thing.

I am pretty sure we do not support "combining" disks i.e. via LVM or MDRAID on Harvester.

The problem I had today was I had a 500gb volume and it failed. It was 800gb + on disk, and there was not space left. The replicas failed. Lost the whole volumne. I have to find a solution to it.

It is possible to reduce the "reserved" space and to allow overprovisioning as a workaround but for production usage I would not want to do that..

My plan was to restore, but restore is not working either.

In case there is not sufficient disk space - the only chance I see is to add more / bigger disks.


Update module github.com/charmbracelet/bubbletea to v1.2.4

This PR contains the following updates:

Package
Type
Update
Change

github.com/charmbracelet/bubbletea
require
patch
v1.2.3 -> v1.2.4

Release Notes

charmbracelet/bubbletea (github.com/charmbracelet/bubbletea)
v1.2.4
Compare Source
Changelog
Bug fixes

4ad0792: fix: cursor position adjustment after exiting alt screen (#1241) (@semihbkgr)
ede8caa: fix: renderer: keep a separate count of lines rendered in the alt screen (@aymanbagabas)

Other work

76b0f81: ci: fix goreleaser config (#1238) (@caarlos0)

Thoughts? Questions? We love hearing from you. Feel free to reach out on Twitter, The Fediverse, or on Discord.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

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

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
438

Relevant Lines:
991

💛  - Coveralls


Fix #9034 - middleware icons not displayed in tile and summary views

@miq-bot add_label bug, providers/hawkular, ui

@himdel @mzazrivec @ammendonca please review
@pilhuhn fyi - decorators change

@miq-bot add_label wip

@miq-bot rm_label wip

Fixes it for Grid and Tile views:

But breaks it for List view:

@ammendonca you are correct regarding list view. I think that this is currently broken for everyone because it was not updated as part of #8734 following the rest of the path changes.
IMO the relevant code is here
I'll open a separate issue.

unrelated test failures - something with Foreman controller

@abonas @chessbyte I'd need this PR to be backported to Darga, to be able to backport #9351.


random: generate large sequences via vmap rather than Python loops

Fixes #7011
Testing that this does not change random results requires generating >4GB of random bits. Instead, I confirmed this is correct by temporarily setting the maximum to a small number to generate multiple small blocks, and compared the output of the old version to the output of the new version.
With the new version, the size of the jaxpr no longer scales with the size of the requested random bits.

Nice use of vmap!


Update office-365-network-mac-perf-score.md

Added final Teams network assessment calculation, aligned some terms with what we use elsewhere in the feature such as Exchange service front door, corrected some technical errors. @kelleyvice-msft

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks


Implement OAuth 2.0 Dynamic Client Registration Protocol

This feature will deliver OAuth 2.0 Dynamic Client Registration Protocol.

@jgrandja Can I pick this one?

Thanks for your interest @pkostrzewa.
This feature is currently on-hold (as indicated in the labels) and will likely not get implemented for a couple months at least.
OpenID Connect 1.0 Client Registration Endpoint gh-57 is the priority at the moment and the work has started in gh-189.

@jgrandja Do I understand the status of this issue correctly?

Create a registration: OIDC spec RFC Spring Authorization Server issue (done)
Get a registration: OIDC spec RFC Spring Authorization Server issue (done)
Update a registration: RFC Unable to find Spring Authorization Server issue
Delete a registration: RFC Unable to find Spring Authorization Server issue

@uhhhh2 Yes, the first 2 items are completed.
The last 2 items refer to RFC 7592 OAuth 2.0 Dynamic Client Registration Management Protocol, which does not have any tickets open at the moment. And would be a low priority item anyway, as we have many more features that still need to be built that are high priority.
This specific ticket addresses RFC 7591 OAuth 2.0 Dynamic Client Registration Protocol, which is on-hold and is a low priority item as well.

@jgrandja can you please let us know tentative release when  we will get this? And what would be the alternative way as of now to register the client dynamically?
Thanks in advance,
Atul.

@aphalke OpenID Connect 1.0 Client Registration Endpoint has been implemented for a while now.

@jgrandja Do I understand the status of this issue correctly?

Create a registration: OIDC spec RFC Spring Authorization Server issue (done)
Get a registration: OIDC spec RFC Spring Authorization Server issue (done)
Update a registration: RFC Unable to find Spring Authorization Server issue (probably not started yet?)
Delete a registration: RFC Unable to find Spring Authorization Server issue (probably not started yet?)

@jgrandja Do you guys have any update regarding the "client registration update" feature? We're looking on possibly creating our own converter to achieve this, but wanted to know first if the feature was on your short-time roadmap.
Thanks.

@proyupgrade The "Update a registration" feature is not on the roadmap. I'm not sure when it will be implemented as there are a few higher priority items ahead.

I know why it's a low priority item - anybody can implement a CRUD.
But is this (DCR and DCR-M) implemented? @jgrandja  LOL

@oracle-fusion-middleware-team No it's not implemented. FYI, you can see the current feature list here.

Thanks for the info Joe,  I'll go ahead implement my own.

@oracle-fusion-middleware-team were you able to implement a workaround for update registrations?

@Suvink Nope, we eventually decided not to use dynamic registrations...

I've added my vote to this but not for the basic dynamic registration but for the dynamic client registration management (RFC 7592).


[ST] ezETH bridge choosing BNB destination by itself

Describe the bug
A user tried to bridge ezETH from Ethereum mainnet to Mode. They instead started a transaction with BNB Chain destination. They used our bridge UI and are positive that Mode network was chosen correctly.
I know there were some issues with the asset/chain selector in the UI so I'm filing this in case it's something we can reproduce and debug.
https://connextscan.io/tx/0x7fae9a09df637536af9abae68cbbaf85c8b6ebb77dfbe4fca42cb3029a998bf9
Link to ticket in discord
https://discord.com/channels/454734546869551114/1215863856719462420/1215863946851123210

Leaving only #5842 open


Add University of Information Technology, VietNam

Add University of Information Technology, VietNam.
Website: https://en.uit.edu.vn/.
Email address sample<EMAIL_ADDRESS>

@hungdluit90 I am sorry, the domain uit.edu.vn is removed from our trusted domains list because the school allows to register an email address there even if you are not a student of the school. If you are the student of this school, please apply with official document (OFFICIAL DOCUMENT tab at https://www.jetbrains.com/shop/eform/students).


SO2 to R1 conversion for postprocessing

The timers assume that the path representation is in R1. When the joints in the skeleton are SO2, we would like them to move along the geodesic and not the other way around. To ensure this happens, we need to appropriately convert the path representation to R1 along the geodesic. THis PR handles this conversion.

Before creating a pull request

[x] Document new methods and classes
[x] Format code with make format

Before merging a pull request

[x] Set version target by selecting a milestone on the right side
[ ] Summarize this change in CHANGELOG.md
[x] Add unit test(s) for this change

@brianhou I do not think dealing with multiple DOF joint spaces needs to be a part of this PR given that the rest of the stack, especially trajectory execution does not support it. Other comments have been addressed.

After discussing with @aditya-vk, it seems that somewhere lower down in the stack would be a better place to convert to R1 trajectories (when necessary). I think this would make for a cleaner abstraction, since we'd be able to reason with the SO(2) joints all the way from planning until we send it off to the controller.
I've created https://github.com/personalrobotics/rewd_controllers/issues/30 to track this, let's clean up this PR to remove the conversion here.


feat: ai sensing wedge

the standard enemy now has a flag if it can "see" the player.
this works in 4 steps:

calculate the distance from the player and check if it's less than the range
calculate the angle between the forward vector and the direction vector the player currently is and checking if it's less then the max
checking if the player is on the same z coordinate as the enemy -> this could be made a little smarter by using the players height as well.
[not done yet] checking if the player is obstructed by world geometry by casting a ray from the entity to the player and testing if it hits something else first. this is not implemented due to the performance constraints as of now. could easily be done when we have some acceleration structues in place

it also adds a debug view for the "wedge" the entity can see. you can toggle it via the console dbg_show_enemy_vision = 1

I notice that the enemy's animation changes to run seemingly randomly but doesn't change it's velocity?

Does something speak against having it binary like in eg. half-life? The animation system has no animation blending and doesn't scale to continuous velocities.

making it binary would mean that all the velocity and force calculation would be pretty meaningless. we could map the continuous space to discrete afterwards, but this is a hacky fix because the system currently build is not meant to do that. i think i would rather work on making the animation depend on the velocity

making it binary would mean that all the velocity and force calculation would be pretty meaningless. we could map the continuous space to discrete afterwards, but this is a hacky fix because the system currently build is not meant to do that. i think i would rather work on making the animation depend on the velocity

Yes, the animation should depend on the velocity but if the velocity's magnitude increases cintinuously but the animation plays the same speed it might look weird. Do you understand what I mean?

i think we are thinking the same but are talking against each other. we can have a talk in person :) that should fix this issue up


Move error util to a new directory

	go run github.com/layer5io/meshkit/cmd/errorutil -d . update -i ./helpers -o ./helpers

Also move the errorutil files to the new directory
Originally posted by @DelusionalOptimist in https://github.com/meshery/meshery-operator/pull/176#discussion_r661831801

@DelusionalOptimist Will you be able to pick this item?

Sure @kumarabd :slightly_smiling_face:


Tiles disappearing on pan when zoom level change is big

Found this out in a screenshare with @ahocevar just now, to reproduce go to:
http://openlayers.org/en/v3.12.0/examples/xyz-esri.html
Zoom in with a very small bbox, and then pan the map. The tiles will blur completely sometimes. In 3.11.2 you will see a small section blurred only, where no tiles are present as yet.

Caused by #4536 ?

No that doesn't seem to be the cause @fredj I'll investigate what caused it.

seems to be caused by https://github.com/openlayers/ol3/commit/0259977fa95da120b38d56eac0b020190e4cfb22

maybe because we got rid of goog.array.defaultCompare ?

Can the regression be fixed by always passing a compareFn in cases where we currently don't pass one)?
function(a, b) {
  return a > b ? 1 : a < b ? -1 : 0;
}

https://github.com/google/closure-library/blob/master/closure/goog/array/array.js#L1298

yes that's actually the PR I'm preparing now

:+1:


Add generated paginators for autoscaling

Codecov Report

Merging #1642 into develop will decrease coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #1642      +/-   ##
===========================================
- Coverage    92.39%   92.36%   -0.04%
===========================================
  Files           53       53
  Lines         9797     9797
===========================================
- Hits          9052     9049       -3
- Misses         745      748       +3

Impacted Files
Coverage Δ

botocore/credentials.py
98.43% <0%> (-0.4%)
:arrow_down:

Continue to review full report at Codecov.

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


BYC-1304 Handle focus trap on the Modal component

Description
Manage the trap of focusing on the modal component.
The added logic is quite simple, and solves simple scenarios. I'll add complexity later if more complex situations come up.
To avoid introducing regression, this new behavior is only activated by a new focusTrapEnabled property.
Later, when we create a major new version of UI-Toolkit (v5), we'll set this behavior as default.
JIRA ticket
JIRA_Ticket
Demo
https://github.com/user-attachments/assets/a534b614-9bc6-4f53-990c-505441f273d2

Do you think we could have cases where we prefer the previous accessibility behaviour ?
If not, we can directly set it as default behaviour 🤔


Switch license to Apache v2.0

I'd like to switch the license of this project to Apache v2.0 license.
Do I have your permission for doing that @foobarto, @mhor, @Flipez? (the project includes your contributions so I need your permission to re-license them)

Yes. No objections here.
I would think you as the main author could make that decision yourself.
On Sat 3 Jun 2017, 16:59 Marcin Kulik<EMAIL_ADDRESS>wrote:

I'd like to switch the license of this project to Apache v2.0 license.
Do I have your permission for doing that @foobarto
https://github.com/foobarto, @mhor https://github.com/mhor, @Flipez
https://github.com/flipez? (the project includes your contributions so
I need your permission to re-license them)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/asciinema/asciinema.org/issues/264, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAQivP0F0wpBN3OvjWsc5hCQh2QtxbE4ks5sAYLrgaJpZM4NvH61
.

@foobarto thanks :) (I think so but asking wouldn't hurt)

Yes no problem

@Flipez ping ;)

@mhor 👍

@sickill Sure, no problem for me ;)


Speed up the redirect process

Is your feature request related to a problem? Please describe.
The current redirect happens after the entire app is loaded, which is slow.
Describe the solution you'd like
The redirect should happen almost instantly.
Describe alternatives you've considered
It might be possible to split the app and have a specific page for the redirect.

Can You Please Explain this more? this looks intresting

I want to try this Code-Splitting work.
Can you please assign me this issue?

@ashuvssut sounds good, please go ahead!


Feature Suggestion:  Set default path for saving token images

In order to help keep the Foundry Data folder structured, I have a specific folder for tokens.  It would be helpful if there were module settings that allowed you to chose the path where this module saves token images.

Yeah, good idea!

This is now added in the module settings menu


v177 release incomplete

Release 177 is missing from the releases page, I guess a tag needs to be added since this was a PR merge.
While at it, lots of tags are missing from the Docker Hub page -- the last one is 147. Is it possible to tag at least a recent build (say 177)?

@Starefossen PTAL

@Starefossen thank you so much, appreciated!


Add support for nested lists/dicts in ContentMessage list fields

Content variation template uses a list of dictionaries for rendering framework agreement changes so we need to support arbitrary nesting of structures in ContentMessage.
The logic remains mostly the same:

render simple fields right away
wrap dictionaries with ContentMessage
render/wrap all items inside a list individually

👍


Empty release - http://pyyaml.org/download/libyaml/yaml-0.2.2.tar.gz

If you download:
http://pyyaml.org/download/libyaml/yaml-0.2.2.tar.gz
And e. g. try to repackage it, you get this:
tar -zxvf /Users/x/SRC/yaml/yaml-0.2.2.tar.gz -C /Depot/Temp/
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
If you then use file on it:
file yaml-0.2.2.tar.gz

You get:
yaml-0.2.2.tar.gz: HTML document, ASCII text, with no line terminators
Not sure what/where the problem is but previous releases worked fine; perhaps
something was automated but did not properly work. The .tar.gz but also the
.zip files do not appear to contain the code to yaml 0.2.2. The older releases
e. g. yaml-0.2.1.* still work fine. Just reporting this, feel free to close this at
any moment in time. :)

Oops, thanks. Downloading with curl apparently wasn't enough. Fixed!

I think I need to do a make dist to actually create a correct dist tarball. Will try...

correct tarball and zip are now uploaded, thanks


add date input

@mnibecker

Where are we going to document inputs - here? That's docs/concepts/inputs.md in juttle repo. Not sure if the right place.

I spose this is fine +1

@dmehra, not sure yet where the docs should go. I think it depends on whether these inputs are going to be outrigger-specific or "more core" and supported by the CLI itself.


Cache Feature Request

The current implementation of caching is wonderful, its been a great help speeding up conversations.
I do notice this trips up when a secondary user starts a conversation, would it be possible to allow for multi-conversation caching?
The main issue currently is the fact that the cache grows large over time and if the second user submits a question and then the first user submits another their entire chat history is being reran all over.

I agree the "dummy" caching feature is already really useful. Makes all the difference between me wanting to use it or rather going to openai ;)
Regarding a real caching feature we are waiting for upstream to persist the state correctly, right?
Hypothetically, how large would a single state be?
llama_model_load_internal: mem required  = 9807.47 MB (+ 1608.00 MB per state)
Is that the relevant state size?

@snxraven @jmtatsch definitely high on my list, unfortunately at the moment I'm blocked because I can't restore the model state. I've tried the kv_state api in both the python bindings and regular c++ but have been unable to actually use this to cut down any processing times or checkpoint the model.
If anyone get even a basic example to work using that API I'd be happy to implement this.

Relevant issue has been opened by another dev over at llama.cpp: https://github.com/ggerganov/llama.cpp/issues/1054

Furthermore, this issue has been reopened so it may be fixed within llama.cpp:
https://github.com/ggerganov/llama.cpp/issues/730
If you would like we can close this issue since there obviously is a solution coming.

I did once do this by simply having multiple instances of llama running.
This works because mmap uses the cache to load the model, so you‘re effectively only penalized by the state size.
But this could be undesireable because of cpu usage

Closing this in favor of #44


Mangaschan

Source name
Mangaschan
Source link
https://mangaschan.com/
Language
Portuguese
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

I can't find any novels under this website, I can only seem to find manga.


DocumentDB .NET SDK ETW trace doesn’t support TCP protocol.

DocumentDB .NET SDK (version 1.13.2) is only traced if ConnectionPolicy.ConnectionProtocol is HTTPS.
Usually, I use TCP. This is inconvenient.
The following documents do not mention protocol limitations.
https://github.com/Azure/azure-documentdb-dotnet/blob/master/docs/documentdb-sdk_capture_etl.md

@takekazuomi I'm not aware of any such limitation. Does it traces nothing for the same app when using TCP protocol as compared to HTTPS protocol? Were you using Gateway mode or Direct mode for HTTPS. Can you send us a trace files on what is being traced and what not just by switching the protocol?

@rnagpal  I'm sorry. I confused TraceSource and EventSource. The problem is the EventSource. (Name: DocumentDBClient, Guid: f832a342-0a53-5bab-b57b-d5bc65319768)
Reproduction

create database (db01) and collection (data), store document ({"id": "1", "partitionKey": "1"})

code used for reproduction. Compile to Console2.exe

using System;
using Microsoft.Azure.Documents;
using Microsoft.Azure.Documents.Client;

class Program
{
    static void Main(string[] args)
    {
        var endpointUrl = "https://localhost:8081";
        var authorizationKey = "*****";
        var connectionPolicy = new ConnectionPolicy {
            ConnectionMode = ConnectionMode.Direct,
            ConnectionProtocol = Protocol.Tcp
//                ConnectionProtocol = Protocol.Https
        };

        using (var client = new DocumentClient(new Uri(endpointUrl), authorizationKey, connectionPolicy))
        {
            var uri = UriFactory.CreateDocumentUri("db01", "data", "1");
            var response = client.ReadDocumentAsync(uri,
                new RequestOptions {PartitionKey = new PartitionKey("1")}).Result;
            Console.WriteLine(response.Resource);
        }
    }
}

In the case of tcp.

$ Perfview.exe / onlyproviders = f832a342-0a53-5bab-b57b-d5bc65319768: *: 0 collect tcp.etl
$ Console2.exe

Change ConnectionProtocol tcp to  https

In the case of https.

$ Perfview.exe / onlyproviders = f832a342-0a53-5bab-b57b-d5bc65319768: *: 0 collect tcp.etl
$ Console2.exe

Result
For https three requests are recorded. In the case of tcp, only two requests are recorded.  In case of tcp is no event trace of document query request and response. Also, Create Document is not traced.
https.etl.zip
tcp.etl.zip

@rnagpal ping


"Bail out! Gsk:ERROR" when running through gdb

Describe the bug
When trying to run spot through gdb to debug https://github.com/xou816/spot/issues/118, spot crashes while selecting a playlist.
To Reproduce
Steps to reproduce the behavior:

Run using gdb spot then r.
Click on All Playlists.
See error:

Gsk:ERROR:../../../gsk/gl/gskglcommandqueue.c:1276:gsk_gl_command_queue_create_render_target: assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x00008cd6 == 0x00008cd5)
Bail out! Gsk:ERROR:../../../gsk/gl/gskglcommandqueue.c:1276:gsk_gl_command_queue_create_render_target: assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x00008cd6 == 0x00008cd5)

Thread 1 "spot" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
49      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.

Expected behavior
I expect the list of all playlists to be displayed, so I can pick some music and hopefully reproduce the "muting" issue.
Amusingly, if I run the app directly, rather than through a debugger, it doesn't display this behaviour, and I can reproduce #118.
General information:

Distribution: Mobian GNU/Linux
Installation method [e. g. built from source, installed from Flathub...]: built from source
Version [e.g. 0.1.0]:  0.3.3-dev
Device used [e. g. desktop, phone...]: PinePhone

thanks for the report! yeah I'm really not skilled enough to tackle this kind of issue. it most likely has to do with gtk/gsomething rather than spot anyway :/ I'll close that for now if you don't mind


{AKS} Fix Section Released version and adopted API version in readme

This checklist is used to make sure that common guidelines for a pull request are followed.
{AKS} Fix Section Released version and adopted API version in readme
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

AKS


Allow CTRL+click on \input{} files

Allow to navigate to included file by CTRL+Click on \include{} directive

@thePanz Thanks for reporting !
This feature will be available in the next release.
The file reference is handled for \input, \include and \includeonly instructions.

How about also navigating to command definitions? And will Ctrl-B work?


Show the tenant name in the header on all pages

Currently the actual tenant is only visible in the user-submenu.
It would be helpful if the tenant name would be present e.g. somewhere in the header or as a badge in a corner

+1.
This could be a dropdown list with all authorized tenants, so we could switch easily too

Tenants's new incarnation is being discussed as part of the Workspaces RFC. Closing this one to make sure we capture all the feedback in one place.


add docker file

Fixes https://github.com/TechnicPack/TechnicSolder/issues/695

[x] Tested Changes using phpunit
[x] Have read and followed the Contribution Guidelines

this is still WIP add a basic dockerfile will add a docker compose too

This PR was replaced by https://github.com/TechnicPack/TechnicSolder/pull/715. Appreciate the PR anyway!


timeBetweenSendingQueuedPackages

timeBetweenSendingQueuedPackages is unused and should probably be removed from docs and default-config. I think it's been superseded by broadcastTimeout.

Good point


[FLINK-17307] Add collector to deserialize in KafkaDeserializationSchema

What is the purpose of the change
This PR adds a way to emit multiple records from
KafkaDeserializationSchema. This is possible through a collector, which
will buffer deserialized records in a queue and then emit all records
atomically. The queue is reused for all incoming Kafka records to
minimize creating new objects on the hot path.
Verifying this change
All existing kafka tests should pass.
Added:

org.apache.flink.streaming.connectors.kafka.KafkaConsumerTestBase#runCollectingSchemaTest

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @aljoscha

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure


Demo is HS

Same as your other theme's demo ;-)
The Free Trial is Over
Log into ghost.org to upgrade your account and restore your blog!

                                                                                the theme still works though                                                                                qL.b                                                                                From: Rémy G.Sent: niedziela, 31 stycznia 2016 20:08To: GavickPro/Portfolio-Free-Ghost-ThemeReply To: GavickPro/Portfolio-Free-Ghost-ThemeSubject: [Portfolio-Free-Ghost-Theme] Demo is HS (#20)Same as your other theme's demo ;-)

The Free Trial is Over
Log into ghostorg to upgrade your account and restore your blog!
—Reply to this email directly or view it on GitHub.


Button donation github for django cookie cutter ?

Hello, I recently finished a project, and I count a small amount to my customers to redistribute to the libraries I use. I wanted to make a donation to you but I don't see a git button or a link to make it. Can you inform me if this is available? Thank you in advance

I believe only the repo admin can enable it from the settings:

Update: this is now available (added about 2 months ago) 🎉

@browniebroke  thanks in the meantime I had subscribed to the site "patreon" of "django cookie cutter" but here I just changed today :)


Correct regex match field according to docs

Changes made since last time:

Target the "regex" manager in the packageRules rule.
Put fileMatch at the top level, where it should be.
Put regexManagers at the top level, where it should be.
Adjust the regex to handle both deps with submodules (//) and without.

The regex was tested against these files via regex101:

https://github.com/GoogleCloudPlatform/healthcare-data-protection-suite/blob/master/examples/tfengine/generated/team/example-prod-apps/main.tf
https://github.com/GoogleCloudPlatform/healthcare-data-protection-suite/blob/master/templates/tfengine/components/resources/gke_clusters/main.tf

The way I tested:

Commit the renovate.json config in my fork on the master branch

Install renovate: npm i -g renovate

Write a config.js:
module.exports = {
  endpoint: 'https://api.github.com',
  token: '<redacted>',
  platform: 'github',
  logFileLevel: 'warn',
  logLevel: 'debug',
  logFile: './renovate.log',
  onboarding: true,
  dryRun: true,
  onboardingConfig: {
    extends: ['config:base'],
  }
  repositories: ['MartinPetkov/healthcare-data-protection-suite'],
};

Run renovate locally: renovate --dry-run --include-forks

Look for warnings (there shouldn't be any) and for the results under packageFiles with updates under the "terraform" manager. There should be results for files under templates/ as well as under examples/.


Jupyter canvas

Closes #176
I'm going to leave this open until I've updated pygfx, so I can make sure that it works well for pygfx too.

Can you tell me a little bit about how this works if someone has multiple cells with rendered scenes in each cell?

Can you tell me a little bit about how this works if someone has multiple cells with rendered scenes in each cell?

Good question. Each cell would probably create a new canvas with a new renderer. So the device would be shared (we should probably make that so), but each canvas comes with its own pipeline(s). I should make a notebook with multiple cells to get a better feel. Will do when we can use pygfx.

BTW: you may see in the screenshots that the colors are a bit off. This has been fixed too by using the appopriate texture format.

 Does that work?

Yes. Then a redraw is only requested when the canvas is resized (in the browser) like with normal windows.

Examples:  https://jupyter-rfb.readthedocs.io/en/latest/examples/


Support reading schedule details

Hu guys, right now, there is no ability to create a proper report with info about entries since we cannot fetch schedule information

I assume that we can extend https://github.com/contentful/contentful-management.java/blob/master/src/main/java/com/contentful/java/cma/model/CMAEntry.java like we already did with tags

@rafalniski 🙏🏻

Hey @meldmy,
I created PR with the initial implementation, please let me know if anything is missing!


Create a User model 0.5pt

You should create a User model according to the design  requirements.
Requirements

A user should have a Model according to the design
A User can have many recipes


[Question] How to use event system with logging library

I currently use winston for all my logging needs and I would like to print a progress bar as well. I would like to just add a new ProgressBarConsoleTransport to winston, but I can't find a nice way to make this work. I read through some issues and pull requests, like #57.
The progress bar doesn't have an easy-to-use interrupt feature like node-progress, but provides more options and custom features.
From my understanding, the event system is implemented in the opposite direction. I would like to send an event to the progress bar every time there is a need to log something to the console, but instead, I get an event every time I can write something to the console. This means I would have to buffer all the logs somehow and write them all at once as soon as I am able to.
So my question really is, what would be the best way to make this library compatible with a logger like winston?

cli-progress is a gui-component and has nothing to to with logging itself. it's just a display for users.
for application "logging" in container/ci context there are the noTTY options noTTYOutput and notTTYSchedule available - this one can be used in conjunction with the events (or pass a custom output stream, or even better a custom terminal)

My question is more related to #57, #85 and #99. Winston has multiple transports that can l log the messages to all kinds of outputs as well as the console.
A typical config would look something like this:

export const logger = winston.createLogger({
  transports: [
    // Normal log file
    new winston.transports.File({
      filename: logfilepath,
      level: 'warn',
      handleExceptions: true,
      format: winston.format.combine(
        winston.format.splat(),
        winston.format.timestamp(),
        logformat
      )
    }),

    // Console logging
    new winston.transports.Console({
      format: winston.format.combine(
        winston.format.splat(),
        winston.format.colorize(),
        winston.format.simple()
      ),
      colorize: true,
      level: 'info'
    })
  ]
});

And all events from logger.error and logger.warn would be written to the console and the file, where logger.info is only written to the console. Currently, this is messing with every progress bar, because in the end this prints to the console just like console.log does.
It would be great to have an example of a log(msg) function that uses watson.Logger or Console.log that works while a progress bar is running without messing everything up. I think @dlvoy in #57 hinted something like that, but I'm not sure how he solved it in the end.

I made some progress, by wrapping the logger for the object that uses the progress bar like this:
class LoggerWrap {
  /**
   * A wrapper for the winston logger to work with cli-progress
   * @param {watson.Logger} logger the logger instance
   */
  constructor(logger) {
    this.logger = logger;

    this.logArgs = new Array();
  }

  getCallback() {
    return () => {
      while (this.logArgs.length > 0) {
        const msg = this.logArgs.shift();
        this.logger.log(...msg);
      }
    };
  }

  log(...args) {
    this.logArgs.push(args);
  }

  error(msg, ...meta) { this.log('error', msg, ...meta); }
  warn(msg, ...meta) { this.log('warn', msg, ...meta); }
  info(msg, ...meta) { this.log('info', msg, ...meta); }
  http(msg, ...meta) { this.log('http', msg, ...meta); }
  verbose(msg, ...meta) { this.log('verbose', msg, ...meta); }
  debug(msg, ...meta) { this.log('debug', msg, ...meta); }
  silly(msg, ...meta) { this.log('silly', msg, ...meta); }
}

But there are still some open problems (probably not related to this):

There is nothing printed to the console (not even the progress bar) until the end where everything is printed at once
The progress bar seems to stop the script from terminating. The duration ticks up every second, but the script should be finished. Not sure what's going on there.

I'll post my final solution, when I got everything working.

redraw-pre should be used (relative cursor reset applied - https://github.com/npkgz/cli-progress/blob/master/lib/multi-bar.js#L114).
you have to stop the bar after your task has been finished (or use stopOnComplete) otherwise the timers will keep the application active

I just found this: https://answers.ros.org/question/368802/ros2-set-parameters-from-file-and-directly/?answer=369015#post-id-369015

For example, to set the ROS parameter use_sim_time for all nodes in a launch file, you can something like

import launch
import launch_ros.actions

def generate_launch_description():
    return launch.LaunchDescription([
        launch_ros.actions.SetParameter(name='use_sim_time', value=True),
        # 'use_sim_time' will be set on all nodes following the line above
    ])

Havn't tested this yet.

I can't really solve this. I created an MWE, so anyone can reproduce this:
The only dependencies are winston and cli-progress.

import winston from 'winston';
import cliProgress from 'cli-progress';

/**
 * Create logger instance
 */
const logger = winston.createLogger({
  transports: [
    // Console logging
    new winston.transports.Console({
      format: winston.format.combine(
        winston.format.splat(),
        winston.format.colorize(),
        winston.format.simple()
      ),
      colorize: true,
      level: 'silly'
    })
  ]
});

class LoggerWrap {
  /**
   * A wrapper for any logger with a `log` method to work with cli-progress
   *
   * Compatible to:
   *  - `console`
   *  - `watson.Logger`
   *
   * @param {watson.Logger|console} logger the logger instance
   */
  constructor(logger) {
    this.logger = logger;

    this.logArgs = new Array();
  }

  getCallback() {
    return () => {
      while (this.logArgs.length > 0) {
        const msg = this.logArgs.shift();
        this.logger.log(...msg);
      }
    };
  }

  // logger overrides
  log(...args) {
    // copy all values, to log them later and still log the current state
    this.logArgs.push(JSON.parse(JSON.stringify(args)));
  }

  // winston overrides
  error(msg, ...meta) { this.log('error', msg, ...meta); }
  warn(msg, ...meta) { this.log('warn', msg, ...meta); }
  info(msg, ...meta) { this.log('info', msg, ...meta); }
  http(msg, ...meta) { this.log('http', msg, ...meta); }
  verbose(msg, ...meta) { this.log('verbose', msg, ...meta); }
  debug(msg, ...meta) { this.log('debug', msg, ...meta); }
  silly(msg, ...meta) { this.log('silly', msg, ...meta); }
}

// First Test
logger.info('Start')

// Create wlogger and bar
const wlogger = new LoggerWrap(logger);
const bar = new cliProgress.SingleBar({
  clearOnComplete: false, // this would be true in production
  hideCursor: false,
});
bar.on('redraw-pre', wlogger.getCallback());

// create concurrent que
const request = (file) => new Promise((res, rej) => {
  wlogger.info('requesting', file);
  setTimeout(() => {
    if (Math.random() < 0.5) {
      wlogger.info('resolving', file);
      res(file);
    } else {
      wlogger.warn('rejecting', file);
      rej(file);
    }
  }, 1000 + Math.random() * 1000);
});
const files = [1, 2, 3, 4, 5, 6];

const makeRequests = files.map(file => () => request(file));
const results = [];
let started = 0;
const recurse = () => {
  const i = started++;
  const makeRequest = makeRequests.shift();
  return !makeRequest ? null : Promise.allSettled([makeRequest()])
    .then(result => {
      results[i] = result[0];
      bar.increment();
      return recurse();
    })
};

bar.start(7);
const limit = 2;
await Promise.all(Array.from({ length: limit }, recurse))
  .then(() => {
    // The bar has to be stopped manually if not all of them finish
    bar.stop();

    // Handle logging que
    logger.debug('Print backlog:');
    wlogger.getCallback()();

    logger.info("Finished");
  });

// End Test
logger.info('End')

Ok, I found the issue. redraw-pre is emitted before the cursor is reset.
https://github.com/npkgz/cli-progress/blob/0457e845ff33c59635aa3effa1e1e1b41fff2dca/lib/generic-bar.js#L86-L107
For better performance the line is never deleted es well, so moving the event down, wouldn't do much. I can fix my problems by adding: process.stderr.clearLine(-1); process.stderr.cursorTo(0, null); to the LoggerWrap.callback but I think that wouldn't be a nice solution. There should only be one process using terminal commands at a time and that's cli-progress in this case.
My preferred solution would be a callback method, that if set, is called after resetting the curser and deleting the current line. Then the line would still only be deleted if this feature is needed.

the events of the generic bar are not exposed to the multibar instance and won't be populated outside
there are two different event implementations used for the single and multibar use-case. the logging functionality mentioned within other issues are only valid for multibar instances.

Ok, then I would suggest making a uniform system, so there is no need for a second documentation. Or name the events differently.
I changed my test code to:

import winston from 'winston';
import cliProgress from 'cli-progress';

/**
 * Create logger instance
 */
const logger = winston.createLogger({
  transports: [
    // Console logging
    new winston.transports.Console({
      format: winston.format.combine(
        winston.format.splat(),
        winston.format.colorize(),
        winston.format.simple()
      ),
      colorize: true,
      level: 'silly'
    })
  ]
});

class LoggerWrap {
  /**
   * A wrapper for any logger with a `log` method to work with cli-progress
   *
   * Compatible to:
   *  - `console`
   *  - `watson.Logger`
   *
   * @param {watson.Logger|console} logger the logger instance
   */
  constructor(logger) {
    this.logger = logger;

    this.logArgs = new Array();
  }

  getCallback() {
    return () => {
      process.stderr.clearLine(-1);
      process.stderr.cursorTo(0, null);
      while (this.logArgs.length > 0) {
        const msg = this.logArgs.shift();
        this.logger.log(...msg);
      }
    };
  }

  // logger overrides
  log(...args) {
    // copy all values, to log them later and still log the current state
    this.logArgs.push(JSON.parse(JSON.stringify(args)));
  }

  // winston overrides
  error(msg, ...meta) { this.log('error', msg, ...meta); }
  warn(msg, ...meta) { this.log('warn', msg, ...meta); }
  info(msg, ...meta) { this.log('info', msg, ...meta); }
  http(msg, ...meta) { this.log('http', msg, ...meta); }
  verbose(msg, ...meta) { this.log('verbose', msg, ...meta); }
  debug(msg, ...meta) { this.log('debug', msg, ...meta); }
  silly(msg, ...meta) { this.log('silly', msg, ...meta); }
}

// First Test
logger.info('Start')

// Create wlogger and bar
const wlogger = new LoggerWrap(logger);

// Single Bar
// const bar = new cliProgress.SingleBar({
//   clearOnComplete: true, // this would be true in production
//   hideCursor: false,
// });
// bar.on('redraw-pre', wlogger.getCallback());
// bar.start(6);

// Multi Bar
const mbar = new cliProgress.MultiBar({
  clearOnComplete: true, // this would be true in production
  hideCursor: false,
});
mbar.on('redraw-pre', wlogger.getCallback());
const bar = mbar.create(6, 0);

// create concurrent que
const request = (task) => new Promise((res, rej) => {
  wlogger.info('requesting %s', task);
  setTimeout(() => {
    if (Math.random() < 0.5) {
      wlogger.info('resolving %s', task);
      res(task);
    } else {
      wlogger.warn('rejecting %s', task);
      rej(task);
    }
  }, 1000 + Math.random() * 1000);
});

// Task list
const tasks = [1, 2, 3, 4, 5, 6];

// List of callables
const makeRequests = tasks.map(task => () => request(task));

const recurse = () => {
  const makeRequest = makeRequests.shift();
  return !makeRequest ? null : Promise.allSettled([makeRequest()])
    .then(() => {
      bar.increment();
      return recurse();
    })
};

const limit = 2;
await Promise.all(Array.from({ length: limit }, recurse))
  .then(() => {
    // The bar has to be stopped manually if not all of them finish
    if (bar) bar.stop();
    if (mbar) mbar.stop();

    // Handle logging que
    logger.debug('Print backlog:');
    wlogger.getCallback()();

    logger.info("Finished");
  });

// End Test
logger.info('End')

And I get the following result:
$ node test.js
info: Start
info: requesting 1
info: requesting 2
info: resolving 1---------------------------------] 0% | ETA: 0s | 0/6
info: requesting 3
warn: rejecting 2---------------------------------] 16% | ETA: 7s | 1/6
info: requesting 4
warn: rejecting 4======---------------------------] 33% | ETA: 3s | 2/6
info: requesting 5
info: resolving 3=============--------------------] 50% | ETA: 3s | 3/6
info: requesting 6
info: resolving 5====================-------------] 66% | ETA: 2s | 4/6
debug: Print backlog:
warn: rejecting 6
info: Finished
info: End

It still looks like, that the line is not cleared before the event is fired. And that's the case:
https://github.com/npkgz/cli-progress/blob/0457e845ff33c59635aa3effa1e1e1b41fff2dca/lib/multi-bar.js#L99-L114
https://github.com/npkgz/cli-progress/blob/0457e845ff33c59635aa3effa1e1e1b41fff2dca/lib/terminal.js#L72-L86

you have to clear it on your own..for performance reason only the end-of-line is cleared after the content have been updated.
atm i've absolutely no time for a refactoring of the codebase to allow logging functionality, sry

Ok, that's fine.
Then here is my workaround code:

import winston from 'winston';
import cliProgress from 'cli-progress';

/**
 * Create logger instance
 */
const logger = winston.createLogger({
  transports: [
    // Console logging
    new winston.transports.Console({
      format: winston.format.combine(
        winston.format.splat(),
        winston.format.colorize(),
        winston.format.simple()
      ),
      colorize: true,
      level: 'silly'
    })
  ]
});

class LoggerWrap {
  /**
   * A wrapper for any logger with a `log` method to work with cli-progress
   *
   * Compatible to:
   *  - `console`
   *  - `watson.Logger`
   *
   * @param {watson.Logger|console} logger the logger instance
   */
  constructor(logger) {
    this.logger = logger;

    this.logArgs = new Array();
  }

  getCallback() {
    return () => {
      process.stderr.clearLine(1);
      // process.stderr.cursorTo(0, null);
      while (this.logArgs.length > 0) {
        const msg = this.logArgs.shift();
        this.logger.log(...msg);
      }
    };
  }

  // logger overrides
  log(...args) {
    // copy all values, to log them later and still log the current state
    this.logArgs.push(JSON.parse(JSON.stringify(args)));
  }

  // winston overrides
  error(msg, ...meta) { this.log('error', msg, ...meta); }
  warn(msg, ...meta) { this.log('warn', msg, ...meta); }
  info(msg, ...meta) { this.log('info', msg, ...meta); }
  http(msg, ...meta) { this.log('http', msg, ...meta); }
  verbose(msg, ...meta) { this.log('verbose', msg, ...meta); }
  debug(msg, ...meta) { this.log('debug', msg, ...meta); }
  silly(msg, ...meta) { this.log('silly', msg, ...meta); }
}

// First Test
logger.info('Start')

// Create wlogger and bar
const wlogger = new LoggerWrap(logger);

// Single Bar
// const bar = new cliProgress.SingleBar({
//   clearOnComplete: true, // this would be true in production
//   hideCursor: false,
// });
// bar.on('redraw-pre', wlogger.getCallback());
// bar.start(6);

// Multi Bar
const mbar = new cliProgress.MultiBar({
  clearOnComplete: true, // this would be true in production
  forceRedraw: true, // without this the bar is flickering
  hideCursor: false,
});
mbar.on('redraw-pre', wlogger.getCallback());
const bar = mbar.create(6, 0);

// create concurrent que
const request = (task) => new Promise((res, rej) => {
  wlogger.info('requesting %s', task);
  setTimeout(() => {
    if (Math.random() < 0.5) {
      wlogger.info('resolving %s', task);
      res(task);
    } else {
      wlogger.warn('rejecting %s', task);
      rej(task);
    }
  }, 1000 + Math.random() * 1000);
});

// Task list
const tasks = [1, 2, 3, 4, 5, 6];

// List of callables
const makeRequests = tasks.map(task => () => request(task));

const recurse = () => {
  const makeRequest = makeRequests.shift();
  return !makeRequest ? null : Promise.allSettled([makeRequest()])
    .then(() => {
      bar.increment();
      return recurse();
    })
};

const limit = 2;
await Promise.all(Array.from({ length: limit }, recurse))
  .then(() => {
    // The bar has to be stopped manually if not all of them finish
    if (bar) bar.stop();
    if (mbar) mbar.stop();

    // Handle logging que
    logger.debug('Print backlog:');
    wlogger.getCallback()();

    logger.info("Finished");
  });

// End Test
logger.info('End')

Unfortunately, I had to set forceRedraw: true, because without this the bar was flickering too much because it is then only drawn when updated. It would be simple to fix if it is possible to check if an event listener is connected. Because then the line should be cleared beforehand and the bar redrawn afterwards.

https://nodejs.org/api/events.html#emitterlistenercounteventname
Should be suitable. Should I submit a quick PR?

keep it as it is... i didn't have the time to check all possible implications - there are also other use-cases for the listener and such behaviour might break other users code..
maybe there will a a dedicated logging option in the future

been using cli-progress for a few days now and at some point, i really need to log while the progress are running.
somehow this worked on my end. using redraw-pre and multiBar.terminal.clearLine():
import { MultiBar } from 'cli-progress'

const multiBar = new MultiBar({
  hideCursor: true,
  format: '{name} {bar} {percentage}%',
  barCompleteChar: '\u2588',
  barIncompleteChar: '\u2591',
  stopOnComplete: true,
  clearOnComplete: true
})

// create / update
![...Array(10)].forEach((_, i) => {
  let timer, progress = 0

  const bar = multiBar.create(1000, 0, {
    name: 'Bar #' + i
  }).on('stop', () => {
    clearInterval(timer)
    multiBar.remove(bar)            // fixes invisible bars
  })

  timer = setInterval(() => {
    bar.update(progress += 2 * (1 + i))
  }, 40)
})

// logging
!(function log(message = 'Logs below:') {
  if (!multiBar.isActive) return

  multiBar.once('redraw-pre', () => {
    multiBar.terminal.clearLine()   // <--
    console.log(message)            // log anything
  })

  setTimeout(() => log(new Date()), 1000)
})()


BufferGeometry support

as they say they are going to eventually drop Geometry. there is still quite some time before they do, but...

I think it makes more sense to make this tool library agnostic, with helpers for Three's geometry types. For now the manual BufferGeometry -> Geometry and back again workflow isn't awful.

Closing then.

BufferGeometry -> Geometry and back again

Just left the code in #7

Thank you.


NIFI-12752 Update GitHub Workflows to use macos-14

Summary
NIFI-12752 Updates GitHub ci-workflow and system-tests automated builds to use macos-14 for the macOS Runner.
The macos-14 version provides Apple Silicon M1 processing with the AArch64 architecture. This provides additional differentiation from the Ubuntu Linux and Windows builds, and also exhibits performance improvements over the current macOS runners.
Additional changes include updating the setup-java action to version 4 and updating the setup-python action to version 5, with Python 3.10 for compatibility with macOS AArch64.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

@exceptionfactory wonderful find - +1 if the checks are green.  please self merge!


Update requirements, setting new pyroma minimum

https://github.com/sphinx-doc/sphinx/issues/5322 - we can't update Sphinx just yet because of this.

Codecov Report

Merging #1288 into master will increase coverage by 1.98%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #1288      +/-   ##
=========================================
+ Coverage   98.01%    100%   +1.98%
=========================================
  Files          33      33
  Lines        2469    2469
  Branches      100     100
=========================================
+ Hits         2420    2469      +49
+ Misses         48       0      -48
+ Partials        1       0       -1

Impacted Files
Coverage Δ

src/dcos_e2e/cluster.py
100% <0%> (+1.81%)
:arrow_up:

tests/test_dcos_e2e/test_legacy.py
100% <0%> (+14.63%)
:arrow_up:

tests/test_dcos_e2e/test_node_install.py
100% <0%> (+18.18%)
:arrow_up:

tests/test_dcos_e2e/test_cluster.py
100% <0%> (+23.64%)
: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 4388b4c...8472530. Read the comment docs.


Do not switch TLS version on 1.6 -> 1.7 upgrade

See https://github.com/istio/istio/issues/28120
See https://github.com/envoyproxy/envoy/issues/13864
This resolves a downtime event on in place upgrade from 1.6 to 1.7. This
is a couple seconds of 503s.
This is intentionally sent only to 1.7 as it is only relevant for this
branch.
Please note this feature flag is shipped by on by default. We have two
choices:

Off by default. Anyone upgrading from 1.6 to 1.7 will continue to get
downtime unless they read the release notes and add the flag.
On by default. Anyone with 1.7 already deployed, but that still has
1.6 proxies will encur a downtime unless they read the release notes and
remove the flag.

I have chosen on by default, as the set of people with 1.6 proxies with
1.7.x Istiod upgrading to 1.7.5 seems far smaller than the impacted set
of "off by default", and the mitigation is the same. Additionally, for
those that are impacted, the impact will be exclusively the proxies on
1.6, which is presumably not 100% of proxies, whereas in the other case
ALL proxies are 1.6 and thus impacted.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
c9b7e693a92e2bc0baef67c3b7c184024112faab
link
/test unit-tests_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Looks like a v2 cluster/listener config is probably not compatible with v3 Secret_ValidationContext or Secret_TlsCertificate. But I will leave it to @howardjohn to confirm.

Looks like a v2 cluster/listener config is probably not compatible with v3 Secret_ValidationContext or Secret_TlsCertificate. But I will leave it to @howardjohn to confirm.

It is compatible, but switch it causes a temporary downtime

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.7
9a91a90578f0f332e29aa8d8bdd070d9c313c8d8
link
/test unit-tests_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn can you add an integration test for this migration config knob? This looks like something which can be unstable from release to next.

This looks like something which can be unstable from release to next.

This is not going to be around in any other release. We do not have the capability to test cross version communication currently

/retest

This looks like something which can be unstable from release to next.

This is not going to be around in any other release. We do not have the capability to test cross version communication currently

Interesting, so when we advertise that control plane version N supports proxy versions N & N-1 it's based on code reviews and not any manual or automated tests.


bug: failures when creating a workspace via deck sync

In a PostgreSQL-backed hybrid deployment of Kong Gateway <IP_ADDRESS>, the deck sync command fails when the target workspace (either via _workspace in the deck file or the --workspace flag) does not yet exist.
When a deck file has a workspace that does not exist, it successfully creates the workspace and then fails any subsequent actions.
$ deck version
decK v1.15.1 (bb70f8f)
$ deck sync -s kong/small_workspace.yaml
creating workspace small-workspace
Error: building state: add defaults to plugin 'kafka-log': retrieve schema for kafka-log from Kong: HTTP status 404 (message: "Workspace 'small-workspace' not found")

Re-running the exact same command a moment later successfully syncs the state file.

small_workspace.yaml
_workspace: small-workspace
_format_version: '1.1'
plugins:
  - name: kafka-log
    config:
      producer_async: false
      topic: kongRequestLogRaw
      bootstrap_servers:
        - host: kafka-broker.service.company.com
          port: 9092
  - name: prometheus
    config:
      per_consumer: false

It seems a reasonable solution would be for deck sync to consider the --db-update-propagation-delay flag after creating a workspace here. Based on the description of that flag ("artificial delay (in seconds) that is injected between insert operations for related entities"), it seems like an oversight that it's ignored at all (if not the root of this bug).
(NB: simultaneously reported in support ticket #00030766 but posted here for posterity and for the specific fix suggestion)

Hello,
We are getting hits by this bug too any news / progress in this ?
Best Regards.


Consider removing RouteString

RouteString, currently residing at https://github.com/yewstack/yew_router/blob/master/src/route_info.rs#L21, is a compatibility enum used to provide access to individual parts of a route (path/query/fragment). The library currently doesn't make use of having access to individual sections of a route string, and sometimes having the ability to do so is confusing and possibly misleading.
It should be removed and instead, if needed, be replaced with a parser that can extract the path, query and fragment from a plain string. The only downside to this would be including another library to do the parsing or a general parsing library would be required to always be included in order to hand-roll a parser to do this.

removed in https://github.com/yewstack/yew_router/pull/89


The galaxy brain badge

It is the solution

this is not supposed to be difficult

i think they closed it

i think they closed it

no u cant achieve brain galaxy badge easily

i think they closed it

no u cant achieve brain galaxy badge easily

Yes u can


Case label inside version block gets indented wrong

unittest
{
    switch(x)
    {
    case 0:
        version (none)
        {
            // Comment
-            case '\n':
+        case '\n':
                 break;
        }
    }
}

The output that I get when formatting this is as follows:
unittest
{
	switch (x)
	{
	case 0:
		version (none)
		{
			// Comment
	case '\n':
			break;
		}
	}
}

Aligning the "case" with the "switch" is intentional.

Ok well I guess this is an enhancement request then.

Normal labels appear to be aligned with the switch statement too, is that also intentional?

It looks pretty bad when combined with #76

unittest
{
    switch(x)
    {
    case 0:
        {
-        Label:
-            while(1) {}
+    Label: while(1)
+            {
+            }
            break;
        }
    }
}

Normal labels appear to be aligned with the switch statement too, is that also intentional?

Yes.

The 0.3.0 release will add configuration options, and I think that this should be one of them.

That sounds great.  How are you planning to expose the configuration options?

Not sure yet.


Duration to delete directory increases exponentially based on # of files

@pkdash and I noticed that irods irm on dir with 30 tiny files takes up to 1min
@cbcunc and I isolated the issue to the current microservices
Likely resolved by:
https://github.com/hydroshare/hydroshare/issues/5195
(but creating this issue in case there are interim patches that can be made)

related to https://github.com/hydroshare/hydroshare-quota/issues/5

Attempt at fix in https://github.com/hydroshare/hydroshare-quota/pull/9

resolved by Quota updates released as 2.14 move the HS datazone away from microservices.


Point Set

A point set represents an array of points, not necessarily associated with a Path.
@paulmach

BOOM!  committed as d0e729f16812e8843bce5c7d235be38a6945d79d


  This should mean the move to modules should have very little effect on CI or anything that already expects vendor.
containerd/cri and containerd has a weird circular relationship so this PoC is based on also updating containerd/cri to go 1.14 and go.mod.  If you look at the go.mod file its very clean now except all the replaces for k8s.io/* packages.  That is because containerd/cri depends on k8s.io/kubernetes for the streaming package.  Depending on k/k is a big no-no and I guess made very difficult on purpose. There is a path forward in that I believe the streaming package can be moved to k8s.io/streaming-server which would then make the go.mod very clean.
This PR can't be merged because it's based on a local fork containerd/cri as I explained before.

The go.mod file didn't get included yet

@dmcgowan Minor details :)  Just added

Note that we aren't using Travis for CI on master at this point. The Go version for CI is set in the .github/workflows/ci.yml file

The circular dependency between containerd/cri and containerd is making this barf at the moment.  I'll keep fooling around to figure out how I can test this works in CI with having to update both projects.

Figured out switch to go 1.14 really doesn't matter as all the leg work has already been done to support modules in CI it seems. The only odd thing is https://github.com/containerd/project/blob/master/script/validate/vendor is going to be fragile based on what go version the developer used to run "go mod tidy".  go 1.13 and go 1.14 will produce slightly different output.  I'm wondering if "go mod verify" is better.

Ah crap..... There's no point to this. Basically containerd can't switch to go modules until the dependency on k8s.io/kubernetes is removed from containerd/cri.  The problem is that if anybody need to use the containerd client in a go.mod project as soon as we switch to modules and we depend on k/k the consumers will have to include the crap ton of replace statements k/k requires.
I'm going to go cry now.
@Random-Liu It would be super swell if streaming server can move to a k8s.io top level project.  Until then no go.mod for us :cry:

@ibuildthecloud @Random-Liu it's not great but it seems manageable. Or is the problem the implied vendoring of k/k?
My working example: https://github.com/dweomer/cri/blob/release/1.3-go-mod/go.mod#L9-L30
replace (
	github.com/docker/distribution => github.com/docker/distribution v2.7.1-0.20190205005809-0d3efadf0154+incompatible
	github.com/opencontainers/runc => github.com/opencontainers/runc v1.0.0-rc10
	k8s.io/api => k8s.io/api v0.16.6 // v0.16.6
	k8s.io/apiextensions-apiserver => k8s.io/apiextensions-apiserver v0.16.6 // v1.16.6
	k8s.io/apimachinery => k8s.io/apimachinery v0.16.6 // v1.16.6
	k8s.io/apiserver => k8s.io/apiserver v0.16.6 // v1.16.6
	k8s.io/cli-runtime => k8s.io/cli-runtime v0.16.6 // v1.16.6
	k8s.io/client-go => k8s.io/client-go v0.16.6 // v1.16.6
	k8s.io/cloud-provider => k8s.io/cloud-provider v0.16.6 // v1.16.6
	k8s.io/cluster-bootstrap => k8s.io/cluster-bootstrap v0.16.6 // v1.16.6
	k8s.io/code-generator => k8s.io/code-generator v0.16.6 // v1.16.6
	k8s.io/component-base => k8s.io/component-base v0.16.6 // v1.16.6
	k8s.io/cri-api => k8s.io/cri-api v0.16.6 // v1.16.6
	k8s.io/csi-translation-lib => k8s.io/csi-translation-lib v0.16.6 // v1.16.6
	k8s.io/kube-aggregator => k8s.io/kube-aggregator v0.16.6 // v1.16.6
	k8s.io/kube-controller-manager => k8s.io/kube-controller-manager v0.16.6 // v1.16.6
	k8s.io/kube-proxy => k8s.io/kube-proxy v0.16.6 // v1.16.6
	k8s.io/kube-scheduler => k8s.io/kube-scheduler v0.16.6 // v1.16.6
	k8s.io/kubectl => k8s.io/kubectl v0.16.6 // v1.16.6
	k8s.io/kubelet => k8s.io/kubelet v0.16.6 // v1.16.6
	k8s.io/kubernetes => k8s.io/kubernetes v1.16.6 // v1.16.6
	k8s.io/legacy-cloud-providers => k8s.io/legacy-cloud-providers v0.16.6 // v1.16.6
	k8s.io/metrics => k8s.io/metrics v0.16.6 // v1.16.6
	k8s.io/sample-apiserver => k8s.io/sample-apiserver v0.16.6 // v1.16.6
)

@ibuildthecloud @Random-Liu it's not great but it seems manageable. Or is the problem the implied vendoring of k/k?
My working example: https://github.com/dweomer/cri/blob/release/1.3-go-mod/go.mod#L9-L30
replace (
	github.com/docker/distribution => github.com/docker/distribution v2.7.1-0.20190205005809-0d3efadf0154+incompatible
	github.com/opencontainers/runc => github.com/opencontainers/runc v1.0.0-rc10
	k8s.io/api => k8s.io/api v0.16.6 // v0.16.6
	k8s.io/apiextensions-apiserver => k8s.io/apiextensions-apiserver v0.16.6 // v1.16.6
	k8s.io/apimachinery => k8s.io/apimachinery v0.16.6 // v1.16.6
	k8s.io/apiserver => k8s.io/apiserver v0.16.6 // v1.16.6
	k8s.io/cli-runtime => k8s.io/cli-runtime v0.16.6 // v1.16.6
	k8s.io/client-go => k8s.io/client-go v0.16.6 // v1.16.6
	k8s.io/cloud-provider => k8s.io/cloud-provider v0.16.6 // v1.16.6
	k8s.io/cluster-bootstrap => k8s.io/cluster-bootstrap v0.16.6 // v1.16.6
	k8s.io/code-generator => k8s.io/code-generator v0.16.6 // v1.16.6
	k8s.io/component-base => k8s.io/component-base v0.16.6 // v1.16.6
	k8s.io/cri-api => k8s.io/cri-api v0.16.6 // v1.16.6
	k8s.io/csi-translation-lib => k8s.io/csi-translation-lib v0.16.6 // v1.16.6
	k8s.io/kube-aggregator => k8s.io/kube-aggregator v0.16.6 // v1.16.6
	k8s.io/kube-controller-manager => k8s.io/kube-controller-manager v0.16.6 // v1.16.6
	k8s.io/kube-proxy => k8s.io/kube-proxy v0.16.6 // v1.16.6
	k8s.io/kube-scheduler => k8s.io/kube-scheduler v0.16.6 // v1.16.6
	k8s.io/kubectl => k8s.io/kubectl v0.16.6 // v1.16.6
	k8s.io/kubelet => k8s.io/kubelet v0.16.6 // v1.16.6
	k8s.io/kubernetes => k8s.io/kubernetes v1.16.6 // v1.16.6
	k8s.io/legacy-cloud-providers => k8s.io/legacy-cloud-providers v0.16.6 // v1.16.6
	k8s.io/metrics => k8s.io/metrics v0.16.6 // v1.16.6
	k8s.io/sample-apiserver => k8s.io/sample-apiserver v0.16.6 // v1.16.6
)

@ibuildthecloud do you remember Maven BOMs? :rofl:


Executor not handling 1 exit code from Playwright

Plugin version: "@mands/nx-playwright": "0.1.26"
Playwright version: "playwright": "1.26.0"
When a playwright test fails using the nx e2e <app-name>-e2e command I would expect the playwright output to be logged to the console in a normal fashion, below is an example of "normal" output from playwright
Running X tests using X workers

  ✓  3 [chromium] › src\example.spec.ts:23:3 › Playwright example tests @example-playwright › Console output should be retained (7s)

  X skipped
  X passed (55s)
Done in 56.75s.

However, I am noticing that whenever a single test fails that this is not the case, instead we see that all playwright output is logged in the following format as the playwright test command is returning a 1 exit code for failure:

Looking at the executor, I can see that the code is not running past the following line:
const { stdout, stderr } = yield (0, util_1.promisify)(child_process_1.exec)(command);
Instead, as a 1 exit code is being returned from playwright, I'm assuming the promisify call is being rejected, therefore meaning we go straight to the catch block where console.error('Unexpected error', error); is ran, resulting in the errors being logged into the console as seen above.
To reproduce
Steps to reproduce the behavior:

Use the @mands/nx-playwright generator to add playwright to your project
Run a single test through the @mands/nx-playwright executor where you would expect that test to fail

Expected behaviour

For a failed test, the code should not fall into the 'catch' block, only going into that block for errors unrelated to test failure
Formatting of any playwright output should be retained and logged to the console in a normal fashion.

If anyone could take a look at this please, that would be great. I suggest the following change to the executor which should allow the playwright output to be captured/reported correctly
`import { ExecutorContext } from '@nrwl/devkit';
import { exec } from 'child_process';
import { startDevServer } from './lib/start-dev-server';
import executorSchema from './schema.json';
import { PlaywrightExecutorSchema } from './schema-types';
const PASS_MARKER = 'PLAYWRIGHT_PASS';
function getFlags(options: PlaywrightExecutorSchema): string {
const headedOption = options.headed === true ? '--headed' : '';
const passWithNoTestsOption = options.passWithNoTests === true ? '--pass-with-no-tests' : '';
const browserOption = options.browser?.length ? --browser=${options.browser} : '';
const reporterOption = options.reporter?.length ? --reporter=${options.reporter} : '';
const timeoutOption = options.timeout !== undefined ? --timeout=${options.timeout} : '';
const grepOption = options.grep !== undefined ? --grep=${options.grep} : '';
const grepInvertOption =
options.grepInvert !== undefined ? --grep-invert=${options.grepInvert} : '';
const flagStrings = [
headedOption,
browserOption,
reporterOption,
timeoutOption,
grepOption,
grepInvertOption,
passWithNoTestsOption,
].filter(Boolean);
return flagStrings.join(' ');
}
export default async function executor(
options: PlaywrightExecutorSchema,
context: ExecutorContext,
) {
await startDevServer(options, context);
const flags = getFlags(options);
const runnerCommand = options.packageRunner ?? executorSchema.properties.packageRunner.default;
const path = options.path ?? executorSchema.properties.path.default;
const command =
${runnerCommand} playwright test ${path} --config ${options.e2eFolder}/playwright.config.ts ${flags} && echo ${PASS_MARKER}.trim();
console.debug(Running ${command});
const success = await new Promise((resolve, reject) => {
exec(command, (error, stdout) => {
console.info(Playwright output ${stdout});
if (error) {
reject(error);
}
resolve(stdout.trim().includes(PASS_MARKER));
});
});
return { success };
}
`

Thanks for submitting this @Danphillipz. This is something that has been on our radar too but haven't got around doing yet. Do you mind creating a PR for this please?

Hello there, I've got a similar issue in my project, but how I "solved" was running the application in parallel with the execution of Playwright. Doing this, I got a success message like this:
> nx run host-e2e:e2e

Running npx playwright test src --config apps/host-e2e/playwright.config.ts  && echo PLAYWRIGHT_PASS
Playwright output
Running 1 test using 1 worker

  ✓  1 src/app.spec.ts:3:5 › should start page (999ms)

  1 passed (1.9s)
PLAYWRIGHT_PASS

 ————————————————

 >  NX   Successfully ran target e2e for project host-e2e (4s)

So I wonder if this issue is related to the triggering of the application, I didn't have enough time to review more in the deep the plugin, but if this would help someone, I hope so...

@andreacaldera Will look at getting a PR raised, may need to do something different to my suggestion as the unit tests are failing.
@jrltt Yes I am running the tests in the same way as yourself, what you have seen it correct for a positive journey (no test failures), it's upon test failure where you run into the bug


Update URL's to point to new location

As discussed on Gitter.

https://github.com/cake-build/bitrise-cake-step/commit/9f83c661ae9fadb56bd3a58ad7e24cdc48873dea

PR https://github.com/bitrise-io/bitrise-steplib/pull/973 is submitted


Create an OpenRefine endpoint & add to user documentation

Latest specs: https://reconciliation-api.github.io/specs/latest/
User request: https://twitter.com/AWhitTwit/status/1570163562638876672

OpenRefine reconciliation works now when using https://verifier.globalnames.org/api/v1/reconcile as a reconciliation URL.

However, I do not think I am out of the woods yet. @amandawhitmire can we make a screen-sharing call? It would be helpful to get your feedback about this functionality.
I do not have documentation yet, in case if something will have to be changed significantly. Also I would like to add some more useful features to the service.

@dimus this is fantastic! Very happy to have a screen-sharing call with you. When works? What time zone are you in? I'm GMT-7 (Pacific Daylight Time).

Great @amandawhitmire! I am CDT (GMT -5), I am free after lunch on Monday, all day Tuesday. You can write me at<EMAIL_ADDRESS>to choose a time that is good for you.

@amandawhitmire, thank you for starting documentation at https://github.com/gnames/gnverifier/wiki/OpenRefine-readme


NewResourceName: AdcsOcspExtension.  A feature to add/remove OCSP URI extensions - New Resource Issue #70.

Pull Request (PR) description
This PR adds a new resource named AdcsOcspExtension.  This resource can be used to add/remove
OCSP URI extensions on a Certificate Authority.
This Pull Request (PR) fixes the following issues
- Fixes #70

Task list

[x] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[x] Resource documentation added/updated in README.md in the resource folder.
[x] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[x] Comment-based help added/updated.
[x] Localization strings added/updated in all localization files as appropriate.
[x] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

It looks like there are some merge conflicts (sorry, caused by the PR that just got merged). Can you resolve these and I'll review. Thanks again for contributing this - very cool. Thanks @rchristman89 for reviewing too - much appreciated (more eyes make light work).

@PlagueHO  Thanks for the detailed review.  Will get this wrapped up by the end of the week.

Cool. A pleasure to help and this resource will make a great addition!

@PlagueHO  Daniel, I made all the changes requested but have one outstanding item that I had a question on.  Thanks again for the awesome review and looking forward to contributing more to this resource.

@PlagueHO Daniel, all done.  Let me know if we need to do anything else.  Really appreciate the opportunity to contribute.


sceneReadyCallback returns null error when there is an error

TO REPRODUCE THE ISSUE, FOLLOW THESE STEPS:
load a scene with a URL gives 404
RESULT:
On console, exception is printed
D/OkHttp: java.io.IOException: Unexpected response code: Response{protocol=http/1.1, code=404, message=Not Found...
sceneReadyCallback returns a null Error object with an integer sceneId
EXPECTED RESULT:
since the URL gives 404, I would expect an error of MapController.Error with sceneReadyCallback
ENVIRONMENT:
Android

I can confirm this issue.

Yep this error reporting facility is currently a little bit .. inadequate haha
I believe this error parameter was added specifically for scene updates - which reload the scene and invoke the scene ready callback. The current interface isn't well-suited for capturing all the things that could go wrong when loading a scene. To make things trickier, scene loading happens in native code so we can't just use exceptions. Our strategy so far has been to just write those kinds of errors to the log.


modulesync 6.0.0

modulesync 6.0.0

also contains https://github.com/voxpupuli/puppet-catalog_diff/pull/98


Why react app keep calling ws/info and ws/iframe.html ?

I have setup new project using create-react-app, and saw my scripts inside index.html are called multiple time

Do you have any chrome plugins that might be the culprit here?

There are a couple of reasons why your React app might be calling ws/info and ws/iframe.html multiple times and causing your scripts in index.html to be loaded repeatedly. Here's how to diagnose and fix the issue:

Webpack Code Splitting (Less Likely):

Create React App uses Webpack for bundling your code. In rare cases, Webpack's code splitting might be causing these additional calls.
This is less likely for a new project, but it's worth checking.
Solution:
Look for any code in your components that might be dynamically importing these resources using import() statements.
If you find dynamic imports, consider refactoring your code to load them only when needed.

External Dependency Behavior (More Likely):

It's more probable that an external dependency you've installed is making these calls. Some libraries might use WebSockets or iframes for internal functionality and might be fetching information from these URLs.
Solution:
Review the documentation of any third-party libraries you've included in your project. Look for known behavior related to WebSockets or iframes.
If a specific library is causing the issue, you might be able to configure it to avoid these calls or consider using a different library.

Debugging Network Calls:

Use your browser's developer tools to inspect network requests. This will help you identify which part of your code is making the calls.
Open the developer tools (usually F12 key).
Go to the "Network" tab.
Refresh your page and look for requests to ws/info and ws/iframe.html.
Expand the request to see which script or component is making the call.


Crash: Faulting application name: SystemInformer.exe, version: 3.0.11566.7039, time stamp: 0xb6b0d234

Brief description of your issue
Random crash since updated to 3.0.11566.7039
Windows Event log
Faulting application name: SystemInformer.exe, version: 3.0.11566.7039, time stamp: 0xb6b0d234
Faulting module name: USER32.dll, version: 10.0.22621.1928, time stamp: 0xf615ee3f
Exception code: 0xc0000409
Fault offset: 0x0000000000017f15
Faulting process id: 0x0x1FE0
Faulting application start time: 0x0x1D9D831BF948246
Faulting application path: C:\Program Files\SystemInformer\SystemInformer.exe
Faulting module path: C:\Windows\System32\USER32.dll
Report Id: b3be3ca7-1269-45b5-839a-81b4d4cfb2a9
Faulting package full name:
Faulting package-relative application ID:
Steps to reproduce (optional)
Random can happen when minimized even
Expected behavior (optional)
No response
Actual behavior (optional)
No response
Environment (optional)
SystemInformer.exe, version: 3.0.11566.7039

Windows 11 22h2 22621.2134 (latest update at the time of this report)

Duplicate of #1787


Speech recognition works in 1.1.1 but not text to speech

Hi! I really love the new voice option in 1.1.1! Thanks for writing it.
The speech recognition works very well, it recognises my prompts quickly. But the responses are not played back. Perhaps it's because you expect google TTS? I have the Samsung one selected on my phone.
Also, I noticed that in voice mode when the response is larger than the screen, I can't scroll down to see the rest. But perhaps that would happen automatically when the speech would get there?

Hi there, thanks for enjoying my app.
Are you certain that your volume is high enough for TTS to be audible? Could you switch to Google TTS engine and test if the issue persists?

Thanks for the quick reply!
Yes the volume is set to max, I do hear the ploing sounds when it start/stops recording voice.
I tried also by setting the google TTS under accessibility settings but that didn't help, it's still not playing it on my phone, sorry.  It's a Samsung S23, Android 14.

Ok thank you, I'll investigate

Hi there, it took a while, I'm sorry.
I suspect that there's some issue with my structure. Could you download and install ollama.zip? When installed, say something in Voice Mode to the AI and wait for the answer. Before TTS is triggered, a dialog will pop up. Could you send a screenshot of it (from start to end)?

Ok thanks! I'll do it tomorrow, I'm on a business trip and only have my work phone with me on which I can't sideload.

From: JHubi1 @.>
Sent: Tuesday, June 18, 2024 6:57:09 PM
To: JHubi1/ollama-app @.>
Cc: Tycho Schenkeveld @.>; Author @.>
Subject: Re: [JHubi1/ollama-app] Speech recognition works in 1.1.1 but not text to speech (Issue #22)
Hi there, it took a while, I'm sorry.
I suspect that there's some issue with my structure. Could you download and install ollama.ziphttps://github.com/user-attachments/files/15889991/ollama.zip? When installed, say something in Voice Mode to the AI and wait for the answer. Before TTS is triggered, a dialog will pop up. Could you send a screenshot of it (from start to end)?
—
Reply to this email directly, view it on GitHubhttps://github.com/JHubi1/ollama-app/issues/22#issuecomment-2176564250, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACUMU6CEYF2GBNT3RLPY66TZIBRGLAVCNFSM6AAAAABJJSZD4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZWGU3DIMRVGA.
You are receiving this because you authored the thread.Message ID: @.***>

Did you have time to try it yet?

Yes sorry I didn't have a chance to do it before i left on holidays. But I got a chance to test it now!
No dialog popped up however. Here's an example attached. I said hello and the response was displayed but not spoken. The version you sent me is still 1.1.1 right?

From: JHubi1 @.>
Sent: Tuesday, June 18, 2024 6:57:09 PM
To: JHubi1/ollama-app @.>
Cc: Tycho Schenkeveld @.>; Author @.>
Subject: Re: [JHubi1/ollama-app] Speech recognition works in 1.1.1 but not text to speech (Issue #22)
Hi there, it took a while, I'm sorry.
I suspect that there's some issue with my structure. Could you download and install ollama.ziphttps://github.com/user-attachments/files/15889991/ollama.zip? When installed, say something in Voice Mode to the AI and wait for the answer. Before TTS is triggered, a dialog will pop up. Could you send a screenshot of it (from start to end)?
—
Reply to this email directly, view it on GitHubhttps://github.com/JHubi1/ollama-app/issues/22#issuecomment-2176564250, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACUMU6CEYF2GBNT3RLPY66TZIBRGLAVCNFSM6AAAAABJJSZD4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZWGU3DIMRVGA.
You are receiving this because you authored the thread.Message ID: @.***>

Did you use the API from the ZIP in the message? Are you able to send a second message afterwards by once tapping the button? I'll investigate

Yes I used the one from the zip of course.
And no the second time it wrote something like "here's a clear and concise summary of "hello",, it didn't state what I actually said

From: JHubi1 @.>
Sent: Tuesday, June 25, 2024 6:52:00 AM
To: JHubi1/ollama-app @.>
Cc: Tycho Schenkeveld @.>; Author @.>
Subject: Re: [JHubi1/ollama-app] Speech recognition works in 1.1.1 but not text to speech (Issue #22)
Did you use the APK from the ZIP in the message? Are you able to send a second message afterwards by once tapping the button? I'll investigate
—
Reply to this email directly, view it on GitHubhttps://github.com/JHubi1/ollama-app/issues/22#issuecomment-2187973225, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACUMU6BCJ6ENFBNQNLRM4OLZJDZPBAVCNFSM6AAAAABJJSZD4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBXHE3TGMRSGU.
You are receiving this because you authored the thread.Message ID: @.***>

Hi there again,
could you try this build ollama.zip? Is a warning shown in Voice settings? If so, does switching the language to one with a speech symbol next to it solve the issue?

Ok thank you! But is it ok if I do this next week? It's a bit difficult now on holidays :(

Hi there, did you have time to test it yet?

Had you had time to test the build yet? It should show an icon next to languages that support TTS. Could you test if yours has?

I know I'm a bit pushy, but I'd really need to know whether the solution makes it clearer for you if the language you selected supports TTS, or if this really is an issue with the app and its implementation of various systems. Please test the build and tell me.


Connect FE an BE for recent bookings on overview page and booking overview

User story

As a user
I want / need to see the correct recent and future bookings for myself stored in the database
So that I am reminded which desks I booked

Acceptance criteria

Mock data in FE gets replaced with real data queried from the backend
For the overview front page the bookings for the current week (Mon-Sun) should be shown (possibly future and past bookings)
For the bookings overview page all future bookings should be shown

Definition of done (DoD)

The code has been peer-reviewed by at least one team member
The documentation was updated if necessary
The bill of materials was updated if necessary
Working dev setup was created

DoD general criteria

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Developers agreed to release

@woerndle Can we have another information when getting a list of bookings in the bookings route?
Like:
{
  "total": 20,
  "bookings": [...normal Bookings return]
}


Add support for @direction.

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

Project coverage is 76.01%. Comparing base (d9d7dd2) to head (2d592ec).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #19      +/-   ##
==========================================
+ Coverage   75.93%   76.01%   +0.08%
==========================================
  Files          10       10
  Lines         590      592       +2
==========================================
+ Hits          448      450       +2
  Misses        142      142

Files with missing lines
Coverage Δ

lib/canonicalize.js
88.53% <100.00%> (+0.14%)
:arrow_up:

Continue to review full report in Codecov by Sentry.

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

----
🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles