add pyxelate – open source GUI script to partially pixelate images or short video clips.

https://github.com/blackstream-x/pyxelate is an open source GUI script written in Python to partially pixelate images or short video clips. Uses ffmpeg.

@Wikinaut: How is this project related to bikes?

@Wikinaut: How is this project related to bikes?

For documenting situations and aggressive car drivers like this:
https://twitter.com/Wikinaut/status/1443866702866010152?s=20

add to the fork https://github.com/Wikinaut/awesome-bikeprojects


Skip first cell for pathfinding passability

I noticed that A* pathfinding implementation calls its passability callback to determine if the sourceX,sourceY cell is passable. In my game this is a problem, since monsters block movement and the monster I'm pathfinding for therefore blocks its own movement! I work around this by creating the callback dynamically, and ignoring the source monster:
(typescript)
  /**
   * Build a function that checks if a point is passable, ignoring a given
   * entity. We need this so entities do not block themselves while pathfinding!
   * @param e Entity to ignore.
   */
  private passableCallbackFactory(e: Entity): (x: number, y: number) => boolean {
    return (x, y) => {
      if (!inRange(x, 0, this.MAX_X) || !inRange(y, 0, this.MAX_Y)) {
        return false;
      }
      const entities = entitiesAt(x, y);
      // Don't let entities block themselves
      if (entities === [e]) { return true; }
      // Otherwise, the tile is passable if there are no entities
      return entities.length === 0;
    };

Could the pathfinding algorithm be changed to assume the starting position is passable?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

This is more tricky than it looks. Partly because I would like to maintain consistency between the AStar and Dijkstra pathfinders.
The Dijkstra algorithm works by computing distances from every source cell to a particular target. That is why the [toX, toY] coords are fixed by passing them to ROT.Path.Dijkstra constructor, while [fromX, fromY] can be modified by calling .compute() with different arguments.
This means that the actual underlying computation is totally unrelated to the starting position. The topology used (i.e. what neighbors a particular cell has) is expected to by consistent and immutable for every single .compute() call. But your request (a very reasonable one!) implies that you want different topologies for different .compute() calls.
I am really not sure how to implement the requested behavior, given the current state of the API/implementation of the ROT.Path.Dijkstra pathfinder. On the other hand, I see no problem with your approach to the issue -- that is why the passableCallback exists; to provide enough flexibility for all situations.

Fair enough! While we're on the subject I have another feature request
which I don't think I can implement myself: different cell traversal costs.
Maybe mud tiles cost 2x to move through, or similar. Would this be
possible?!
On Thu., 13 Apr. 2017, 6:29 pm Ondřej Žára<EMAIL_ADDRESS>wrote:

This is more tricky than it looks. Partly because I would like to maintain
consistency between the AStar and Dijkstra pathfinders.
The Dijkstra algorithm works by computing distances from every source
cell to a particular target. That is why the [toX, toY] coords are fixed
by passing them to ROT.Path.Dijkstra constructor, while [fromX, fromY]
can be modified by calling .compute() with different arguments.
This means that the actual underlying computation is totally unrelated to
the starting position. The topology used (i.e. what neighbors a
particular cell has) is expected to by consistent and immutable for
every single .compute() call. But your request (a very reasonable one!)
implies that you want different topologies for different .compute() calls.
I am really not sure how to implement the requested behavior, given the
current state of the API/implementation of the ROT.Path.Dijkstra
pathfinder. On the other hand, I see no problem with your approach to the
issue -- that is why the passableCallback exists; to provide enough
flexibility for all situations.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ondras/rot.js/issues/115#issuecomment-293826366, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAXKda3IbuRoQn5byS6phi9cAswepUIWks5rvdzUgaJpZM4M8Qm3
.

I have another feature request which I don't think I can implement myself: different cell traversal costs. Maybe mud tiles cost 2x to move through, or similar. Would this be possible?!

Yes, and I think that we can even re-use the current API for that. The passableCallback can return a numeric value, representing a relative traversal cost. This behavior might be implemented for both AStar and Dijkstra pathfinders.
I am out of time to do this properly now, but feel free to open an Issue for this feature. Someone else might be interested in implementing it or I might find some time in the future.


bitrate 299Kps ever

Hello, I'm configuring or bitrate the cameras to have better quality, but I put or parameter 4096 in the configuration file, and it is not followed it always stays at 299Kbps. according to the log below,
"name": "KITCHEN",
                    "motion": true,
                    "videoConfig": {
                        "source": "-re -i rtsp: // syno<EMAIL_ADDRESS>554 / Sms = 9.unicast",
                        "stillImageSource": "-i rtsp: // syno<EMAIL_ADDRESS>554 / Sms = 9.unicast",
                        "maxStreams": 3,
                        "maxWidth": 1280,
                        "maxHeight": 720,
                        "maxFPS": 30,
                        "maxBitrate": 4096
[Camera-ffmpeg] Start streaming video from COZINHA with 1280:720@30fps (299kBit)
Does anyone know why?
Thank you.

I also see the bitrate always pegged at 299kbps

Same problem here.

It's not a problem. it's homekit feature. 300kbps via lan/wifi, 160kbps via external 3g/lte

It's not a problem. it's homekit feature. 300kbps via lan/wifi, 160kbps via external 3g/lte

Thank you. Now that you mention it, I have heard that before.


Clock Speed (GHz) is broken

Does not display CPU Clock speed, only displays "Yes"

See #281

Just merged #281, this should be fixed


Kubernetes yaml templates or Helm chart

Wondering if you have any K8s templates or Helm chart for standing up ELK  with SearchGaurd in a Kubernetes cluster

Hey @dkirrane I was about to suggest using kompose. But after testing it locally it fails since the  docker-compose.yml uses build and context and the Kompose maintainers still on it.
Check this issue

I think this is way beyond the scope of this project, but here is an excellent starting point for running ELK on Kubernetes:
https://github.com/pires/kubernetes-elasticsearch-cluster
You should be able to swap the images and get it running with Searchguard without problem.

@jemacom , issue  is fixed now :)

@surajnarwade I think am still facing some issues although am using the 1.6 release.
$kompose version
1.6.0 (e4adfef)

$kompose up
WARN Unsupported root level networks key - ignoring
WARN Unsupported depends_on key - ignoring
WARN Unsupported networks key - ignoring
FATA Error while deploying application: k.Transform failed: image key required within build parameters in order to build and push service 'elasticsearch'

Any thoughts on this ? Thanks.

@jemacom you need to mention image key in your services in docker compose file. then kompose will build your image with that name, push it to registry and then your cluster will pull it and deploy :)


Temporary rename and reset when the tab is closed

Temporary rename :
it can also use 🏃omnibox⌨ to trigger temporary rename,  It will also be very convenient!

❥ Expected behavior:
the 🏃omnibox-key⌨ of Tab Renamer is tr
　　　1. Alt+D to focus browser address bar.
　　　2. Typing tr + Space/Tab
　　　3. Typing  "xxxxxxxx"
　　　4. Enter
　　　5. The title of this tab page will temporarily become to "xxxxxxxx"

user UI

chrome://settings/searchEngines#:~:text=added by extensions
chrome://flags/#omnibox-ui-max-autocomplete-matches

If you have used omnibox, you will know the it very well!

📖 API documentation

https://developer.chrome.com/docs/extensions/reference/omnibox/
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/omnibox

Some extensions of only omnibox feature:

Omnibox Timer Again  　　🏃omnibox⌨ta
　　https://chrome.google.com/webstore/detail/nocmdcegkncmgdianofhdlhbaoinmonm
Bookmark Search  　　🏃omnibox⌨bm
　　https://chrome.google.com/webstore/detail/hhmokalkpaiacdofbcddkogifepbaijk
Instant Multi Search 　　🏃omnibox⌨m
　　https://chrome.google.com/webstore/detail/aamgapdgopfdmokckpkfciiddpahbbcg
ContextSearch web-ext 　　🏃omnibox⌨cs

(This extension is very powerful, and it also perfectly supports the omnibox)

https://chrome.google.com/webstore/detail/ddippghibegbgpjcaaijbacfhjjeafjh

Temporary rename :
it can also use 🏃omnibox⌨ to trigger temporary rename,  It will also be very convenient!

❥ Expected behavior:
the 🏃omnibox-key⌨ of Tab Renamer is tr
　　　1. Alt+D to focus browser address bar.
　　　2. Typing tr + Space/Tab
　　　3. Typing  "xxxxxxxx"
　　　4. Enter
　　　5. The title of this tab page will temporarily become to "xxxxxxxx"

user UI

chrome://settings/searchEngines#:~:text=added by extensions
chrome://flags/#omnibox-ui-max-autocomplete-matches

If you have used omnibox, you will know the it very well!

📖 API documentation

https://developer.chrome.com/docs/extensions/reference/omnibox/
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/omnibox

Some extensions of only omnibox feature:

Omnibox Timer Again  　　🏃omnibox⌨ta
　　https://chrome.google.com/webstore/detail/nocmdcegkncmgdianofhdlhbaoinmonm

This lightweight tool is also good, you can create reminders directly in the address bar, which is very convenient and direct.

Bookmark Search  　　🏃omnibox⌨bm
　　https://chrome.google.com/webstore/detail/hhmokalkpaiacdofbcddkogifepbaijk
Instant Multi Search 　　🏃omnibox⌨m
　　https://chrome.google.com/webstore/detail/aamgapdgopfdmokckpkfciiddpahbbcg
ContextSearch web-ext 　　🏃omnibox⌨cs

(This extension is very powerful, and it also perfectly supports the omnibox)

https://chrome.google.com/webstore/detail/ddippghibegbgpjcaaijbacfhjjeafjh
@imageslr

@dnknn It seemes that omnibox can only support one keyword for each extension. Which action do you think is better? To rename permanently or temporarily?

@dnknn It seemes that omnibox can only support one keyword for each extension. Which action do you think is better? To rename permanently or temporarily?

This is wrong. I have seen the issue of ContextSearch. We can use tr as the key. By default entering tr {title} means temporarily rename, and tr p {title} means permanently rename.

It seemes that omnibox can only support one keyword for each extension.

At the extension manifest.json file 👉   "omnibox": {  "keyword": "tr"    }
Corresponding to the  👉  chrome:settings/searchEngines#:~:text=added by extensions
Start the extension omnibox command/key, there can only be one, that's right!
But after startup, the extension itself can be programmed infinitely. Like you said:

We can use tr as the key. By default entering tr {title} means temporarily rename, and tr p {title} means permanently rename. How about that?

Permanently or temporarily, which should be set to the default action?

Obviously, it must be temporarily as the default action!

Congratulations! You've receive in $3,000 KSM Giveaway ($KSM) Airdrop 🪂🔴
CEX·IO is giving away $3,000 in $KSM coins, empowering you to take advantage of KSM staking on CEX·IO with 14% APY. Join the giveaway and earn a chance to win up to $500. Stake Kusama with CEX·IO, get high rewards and win prizes!
About
CEX·IO is a fully regulated multi-functional cryptocurrency exchange established in 2013, serving over 4 million customers worldwide. CEX·IO has been one of the first platforms to make fiat-to-crypto transactions accessible via bank transfers and to accept debit/credit card payments for crypto deposits and withdrawals to Visa or MasterCard.
→ How to join the $3,000 KSM Giveaway Airdrop?
Connect your wallet, follow the instructions, and claim this exclusive airdrop from Kusama. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

Step-by-Step Guide ''CEX·IO Kusama Giveaway''
Access the Kusama platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Use the connect method to interact with the contract
💰 Connect and receive your tokens
→ Claim Your $KSM Today


Adding Testing library as a library requiring jsdom

As the React Testing library requires a dom to execute their assertions, I'm adding it to the list of libraries requiring it on the documentation.
here's a screenshot of a test failing by using the node environment.

[ ]  Contributor License Agreement signed

Thanks!


Fix samples for personalizing grid tables and responsive tables

This will fix the samples Personalization for grid table and Personalization for responsive table when downloading and running locally.

sap/ui/core/util/reflection/JsControlTreeModifier is a private module which shouldn't be in the application code (e.g. Controller#onInit).
Maybe a new Issue could be opened that addresses the issue this PR is trying to resolve?

@boghyon why is it used here?https://github.com/SAP/openui5/blob/9029cba0953d767d607eaacc01536f73596c1a25/src/sap.ui.documentation/src/sap/ui/documentation/sdk/index.js#L98
I will open a issue and close PR


"Forgot password" tools

Send email to user with "reset" link

https://simpleisbetterthancomplex.com/tutorial/2016/09/19/how-to-create-password-reset-view.html


Add devbitcoinshow

German Bitcoin Show recommend for adding on twitter
Need to evaluate

Bitcoin only show in Dutch. Hosted by ; @AaronvanW @JWBurgers @GKBoris
Weekly new shows.

Added!


nu_scripts: unstable-2023-11-22 -> unstable-2023-12-29

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for nu_scripts is: A place to share Nushell scripts with each other
meta.homepage for nu_scripts is: https://github.com/nushell/nu_scripts
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-12-14 in filename of file in /nix/store/1micqnbbarrpy9j5iyqlzlsadyablyhs-nu_scripts-unstable-2023-12-14

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
nu_scripts

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1micqnbbarrpy9j5iyqlzlsadyablyhs-nu_scripts-unstable-2023-12-14 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/8b85113d7b8de0aa17b61228934ca4d509de00da#nu_scripts

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1micqnbbarrpy9j5iyqlzlsadyablyhs-nu_scripts-unstable-2023-12-14
ls -la /nix/store/1micqnbbarrpy9j5iyqlzlsadyablyhs-nu_scripts-unstable-2023-12-14/bin

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

1 package built:

nu_scripts

Maintainer pings
cc @CardboardTurkey for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for nu_scripts is: A place to share Nushell scripts with each other
meta.homepage for nu_scripts is: https://github.com/nushell/nu_scripts
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-12-29 in filename of file in /nix/store/ajyliz7hi5lz28wd6xkpia6zaqsv8dvy-nu_scripts-unstable-2023-12-29

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
nu_scripts

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ajyliz7hi5lz28wd6xkpia6zaqsv8dvy-nu_scripts-unstable-2023-12-29 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/0e13c454ef047f5027d2816bba9aefd58d032cae#nu_scripts

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ajyliz7hi5lz28wd6xkpia6zaqsv8dvy-nu_scripts-unstable-2023-12-29
ls -la /nix/store/ajyliz7hi5lz28wd6xkpia6zaqsv8dvy-nu_scripts-unstable-2023-12-29/bin

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

1 package built:

nu_scripts

Maintainer pings
cc @CardboardTurkey for testing.


Clarify hardware checks pre-rolling upgrade

In the last bullet of step 3 here, we say the following:

Make sure capacity and memory usage are reasonable for each node. Nodes must be able to tolerate some increase in case the new version uses more resources for your workload. Also go to Metrics > Dashboard: Hardware and make sure CPU percent is reasonable across the cluster. If there's not enough headroom on any of these metrics, consider adding nodes to your cluster before beginning your upgrade.

We need to clarify this guidance. There are two considerations: You want to make sure each node has enough CPU and memory to handle a possible increase in resource usage with the new version. And you want to make sure the cluster as a whole can handle a single node going down at a time, which can cause CPU usage to increase across the cluster.
More insight from @bdarnell:

so there are two things here: you need enough headroom to survive the largest loss that's a part of your fault tolerance model. this one is relatively easy to quantify. and then there's the "healthy margin" around upgrades, which is a hedge in case the new version is less efficient than the old version. it's hard to provide universal guidance here (we never expect the new version to be less efficient than the old, but sometimes it happens) because it comes down to the operator's personal level of caution for the upgrade margin, i'd personally use something like 10-15% (that is, if I'm within that distance of my cluster's red line, i'd add capacity before upgrading)

cc: @roncrdb.


AWS::Chatbot::SlackChannelConfiguration LoggingLevel validation

Hi!
I think there might be an error in the validation of the LoggingLevel property of the AWS::Chatbot::SlackChannelConfiguration. Currently the allowed values are ERROR, INFO, NODE - but that last one should be NONE according to https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-chatbot-slackchannelconfiguration.html

Thank you for the issue. Fixed.


[TASK] Operator and End User Instructions

Overview
Add a section in docs for Eigenlayer Tangle AVS. Most of the validator operation docs exist already. We will link to it from this section heavily. We will describe most importantly how to run the eigen-tangle-avs.

https://github.com/webb-tools/tangle-docs/pull/51


add SQL Resource Provider to post migration steps

Can we please add a post migration step to add the SQL Resource Provider for IaaS migrations ...
https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/sql-vm-resource-provider-register?tabs=azure-cli%2Cbash

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

ID: 5a310e70-bf4a-ebc2-4128-ee756e2de196
Version Independent ID: f0505dae-96b1-8a68-2140-641ee35db51a
Content: Azure Database Migration Service tools matrix
Content Source: articles/dms/dms-tools-matrix.md
Service: dms
GitHub Login: @pochiraju
Microsoft Alias: rajpo

@kiwibayer Thank you for your feedback . We will surely have this reviewed with the content authors and update further.

@kiwibayer This is being assigned to the content author to evaluate and update the documentation as appropriate.


Increment version for monitor releases

Increment package version after release of Azure.Monitor.Query

/check-enforcer override


Unexpected polyline drawing when map is rotated

Issue Type
[ ] Question
[x] Bug
[ ] Improvement
[ ] Build system related
[ ] Performance
[ ] Documentation
Description and/or steps/code to reproduce the problem
Hi,
I´ve identified a similar or other issue with polylines like #1527 . The following picture shows how it should be and if the map is rotated with the RotationGestureOverlay:

This one occurs if I use the following code to rotate the map:
mapController.animateTo(new GeoPoint(gpsLocation.getLatitude(), gpsLocation.getLongitude()), zoom, (long) 750, gpsLocation.getBearing());

If you need any further code sections, please let me know.
Environment
If it's a bug, version(s) of android this affects:
All
Version of osmdroid the issue relates to:
6.1.6

Cannot reproduce the issue.
Please provide the code for a simple case with a small Polyline.

Oh, I`m sorry - I have forgotten to tell that before the mapController.animateTo is called;
I call setMapCenterOffset(0, 450);
If I set the setMapCenterOffset(0, 0); everything is fine.
With different setMapCenterOffset(X, Y) values, also the position of the "visual polyline error" moves.
So it is probably related with the MapCenterOffset.
Can you reproduce it now?

Very interesting!
The fix should be easy then.
For the moment we pre-crop the Paths into the screen before we draw them, not only for performance reasons but also because "at some point" Android doesn't draw "too wide Paths".
If I remember well we crop from the screen center with a radius of the screen radius, which is relevant for a no map offset situation.
With just a double radius crop parameter, we should be able to handle any map offset.

I've just pushed #1529, which should fix the issue.
"Should"? Honestly for this one I'm in a "lazy bastard" mode, and I didn't find the will to build a test example from scratch.
@Ruediger34 Don't hesitate to test it, and tell us if it works!

@Ruediger34 According to @pasniak in #1527 the fix works. Do you want to test for your own case or can we close the issue?

@monsieurtanuki I have tested your PR #1529 and the bug is solved.
Thank you very much for your fast and successful response.


Add a test that exercises minimal input interaction of Flutter on Fuchsia.

See https://bugs.fuchsia.dev/p/fuchsia/issues/detail?id=35184#c8 for context. Discussion should occur there, please.

duplicate of https://github.com/flutter/flutter/issues/44826


Update version for using new authn-client

What does this PR do (include background context, if relevant)?
We released a new authn-client that adds the ability to authenticate hosts from anywhere in the policy branch. This PR updates the version of secretless so it uses the new client so that we can use this ability.
Tests for this feature are already implemented in kubernetes-conjur-demo.
What ticket does this PR close?
Connected to cyberark/conjur#1239

This is going to require updating the acknowledgements. If you feel up to it you can take a crack at it following the instructions in CONTRIBUTING, but if not I'm happy to do this when I am back online

Done. I updated the NOTICES.txt file and the spreadsheet. In the spreadsheet, I just duplicated the 1.4.0 tab and updated the license of conjur-authn-k8s-client.


Improve explanation of error handling for interrupting checkpoints

See https://github.com/iterative/dvc-checkpoints-mnist/pull/2 for background.
Here's the scenario:

My script includes a checkpoint (using make_checkpoint() or similar) but no error handling for keyboard interuptions.
I run an experiment and interrupt it with ctrl-c, which returns a non-0 exit code.
I resume the experiment.

If there were changes between the last time make_checkpoint() was called and when the experiment was interrupted, step 3 will create a new experiment because there was no final cleanup checkpoint applied at the end of step 2 (if the script exited cleanly with a 0 exit code, there would be a final cleanup checkpoint).
I couldn't figure this out until @pmrowla explained it, so IMO it's not going to be clear to users. Since we recommend this ctrl-c workflow in the docs and in our examples, I think we need to better document it. Thoughts?

Also should be noted that this is really only an issue for workspace runs, since in temp dir/queue runs the unsaved extra modifications at the end are just discarded entirely.

@dberenbaum do we know what part of the documentation it affects? (new User Guide section by @flippedcoder , command reference?)

It potentially impacts:

https://dvc.org/doc/command-reference/exp/run#checkpoints
https://dvc.org/doc/api-reference/make_checkpoint
maybe the doc @flippedcoder is working on

We will have to consider whether it need to be reflected in each of these sections. I think any examples should include error handling for keyboard interruption between checkpoints if ctrl-c is part of the expected workflow. Also, we should probably explain in detail somewhere. For example, https://dvc.org/doc/command-reference/exp/run#checkpoints states:

You can now use dvc exp run to begin the experiment. If the process gets interrupted (e.g. with [Ctrl] C or by an error), all the checkpoints so far will be preserved. When a run finishes normally, a final checkpoint will be added (if needed) to wrap up the experiment.

This could probably be more detailed about how interruptions should be handled and why.

should be noted that this is really only an issue for workspace runs

Good point but I'd rather skip that note as it complicates docs and handling errors is a good practice anyway 🙂

https://dvc.org/doc/command-reference/exp/run#checkpoints

Updated in b0fe6188 (part of #2417 which I started for other reasons but was already touching that text). It would now read:

All checkpoints registered at runtime will be preserved even if the process gets interrupted (e.g. with [Ctrl] C, or by an error*). A final checkpoint will be added (if needed) to wrap up the experiment.
* The stage command should return a non-error exit code (0) for the final checkpoint to be generated. Otherwise, it will not be possible to continue this experiment as described below (it will restart from scratch).
Following uses of dvc exp run will continue from this point...

https://dvc.org/doc/api-reference/make_checkpoint

It's funny because we had the interrupt exception in the example code but decided to remove it during review for simplicity 😆  So should I re-add it (and possibly make a short note about it)?

maybe the doc @flippedcoder is working on

As for #2373, maybe under Registering checkpoints in your code as a hidden <details> section? Something like "What happens if my loop gets interrupted?" perhaps. There's no mention of the final checkpoint either BTW. I suggest you open a review on that PR @dberenbaum and consider it solved here.
I looked and see no other existing docs where this should be mentioned.

see no other existing docs where this should be mentioned

Well... Maybe the examples in https://dvc.org/doc/dvclive/usage and https://dvc.org/doc/dvclive/dvclive-with-dvc should handle exceptions then? But it's not checkpoint-specific. Cc @pared

It's funny because we had exception handling in the example py code originally, but decided to remove it during review for simplicity 😆

Yup, my fault there! I vote to add it back, I didn't understand the implications at the time I suggested it.

As for #2373, maybe under Registering checkpoints in your code as a hidden <details> section? Something like "What happens if my loop gets interrupted?" perhaps. There's no mention of the final checkpoint either BTW. I suggest you open a review on that PR @dberenbaum and consider it solved here.

👍

Yup, my fault there! I vote to add it back

No worries, I think we all missed the implications and agreed to remove it. OK, reinstated in c54813b5.

@jorgeorpinel I think there should be some pointer in dvclive section to exception handling, though I am not sure it should be explained extensively there - main point there is to pass the knowledge on dvclive usage. So I would think about something like
What happens if I interrupt my code? Check here

Cool. I'll leave it up to you @pared. I personally don't think a change is needed in that case, but it wouldn't hurt either.

Not sure this is closed actually, would you mind re-assessing @dberenbaum ?

I think #2417 is good, at least for now.


Integrate asn2rflx tool

The tool is harder to integrate that anticipated. E.g. it uses the asn1tools library which has no type information. I also have the feeling that we don't understand the code well enough to be able to maintain it in the future. Let's reconsider ASN.1 support at a later time.


Optional Float argument becomes NaN

The bug should come from somewhere near here.
https://github.com/ufront/ufront-mvc/blob/c41e235a6c5961b4b088376bdac2f86e3384d509/src/ufront/web/ControllerMacros.hx#L651

Ok, when the argument is optional (? prefixed) the check expression is not generated. I think even if the argument is optional, it should be still validated if it is present?

Cleaning up my old issues and I think this is no longer needed.


error: mutable capture of 'inout' parameter 'buffer' is not allowed in concurrently-executing code

Description
Running Sourcery with Xcode 16 throws out the error:
error: mutable capture of 'inout' parameter 'buffer' is not allowed in concurrently-executing code

with regards to this line

Closing as it's fixed with the above referenced PR


How to compile using Eclips/spring boot.we are getting errors in pom.xml

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?

Bug

Which version of SkyWalking, OS and JRE?

Which company or project?

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.

Requirement or improvement

Please describe about your requirements or improvement suggestions.

I don't know. AFAIK, all committer team is using IntelliJ if they are developing the Java part. Any help from the Eclipse user is welcome, but we don't have experience with this. Sorry.


[Release 1.3.5] Version increment

Description
Incremented version to 1.3.5.
Issues Resolved
Part of: https://github.com/opensearch-project/opensearch-build/issues/2348
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

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

Hey @ylwu-amzn can you please review this PR?
Thank you

Hey @Zhangxunmt  waiting this to me merged, can you please merge the PR?
Thank you


Authentication misconfiguration causes integration test failure

Need help resolving the issue which is not covered anywhere in docs/SO as far as I can tell.
I'm using Auth0 (https://auth0.com/) to authenticate WebApi calls. If I disable JwtBearerAuthentication, integration tests work, otherwise I get the following exception when make a call via an HttpClient:
Result StackTrace:
at Microsoft.IdentityModel.Protocols.ConfigurationManager`1.<GetConfigurationAsync>d__24.MoveNext()
...
IDX10803: Unable to obtain configuration from: 'https:///.well-known/openid-configuration'.
IDX10108: The address specified is not valid as per HTTPS scheme. Please specify an https address for security reasons. If you want to test with http address, set the RequireHttps property  on IDocumentRetriever to false.

Detailed info is available here: https://gist.github.com/another-guy/6f4c66cea405b395a265ad53cfcfca1d
project.json of the service
{
  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.0.0",
      "type": "platform"
    },
    "Microsoft.AspNetCore.Mvc": "1.0.0",
    "Microsoft.AspNetCore.Server.IISIntegration": "1.0.0",
    "Microsoft.AspNetCore.Server.Kestrel": "1.0.0",
    "Microsoft.AspNetCore.Cors": "1.0.0",
    "Microsoft.Extensions.Configuration.EnvironmentVariables": "1.0.0",
    "Microsoft.Extensions.Configuration.FileExtensions": "1.0.0",
    "Microsoft.Extensions.Configuration.Json": "1.0.0",
    "Microsoft.Extensions.Logging": "1.0.0",
    "Microsoft.Extensions.Logging.Console": "1.0.0",
    "Microsoft.Extensions.Logging.Debug": "1.0.0",
    "ServiceCommon": "1.0.0-*",
    "ShortGuid": "1.0.2",
    "Swashbuckle.SwaggerGen": "6.0.0-beta901",
    "Swashbuckle.SwaggerUi": "6.0.0-beta901",
    "System.Data.SqlClient": "4.1.0",
    "Microsoft.AspNetCore.Authentication.JwtBearer": "1.0.0",
    "Microsoft.AspNetCore.Identity": "1.0.0",
    "Microsoft.AspNetCore.Identity.EntityFrameworkCore": "1.0.0",
    "System.IdentityModel.Tokens.Jwt": "5.0.0",
    "Peppermint": "1.0.0-*"
  },

  "tools": {
    "Microsoft.AspNetCore.Server.IISIntegration.Tools": {
      "version": "1.0.0-preview1-final",
      "imports": "portable-net45+win8+dnxcore50"
    }
  },

  "frameworks": {
    "netcoreapp1.0": {
      "imports": [
        "dotnet5.6",
        "dnxcore50",
        "portable-net45+win8"
      ]
    }
  },

  "buildOptions": {
    "emitEntryPoint": true,
    "preserveCompilationContext": true
  },

  "runtimeOptions": {
    "gcServer": true
  },

  "publishOptions": {
    "include": [
      "wwwroot",
      "Views",
      "appsettings.json",
      "web.config"
    ]
  },

  "scripts": {
    "postpublish": [ "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%" ]
  }
}

project.json of the tests
{
  "version": "1.0.0-*",
  "testRunner": "xunit",
  "dependencies": {
    "xunit": "2.1.0",
    "TheNextOne2Service": "1.0.0-*",
    "NSubstitute": "2.0.0-alpha003",
    "dotnet-test-xunit": "1.0.0-rc2-build10025",
    "Microsoft.AspNetCore.TestHost": "1.0.0",
    "System.Diagnostics.TraceSource": "4.0.0-rc2-24027",
    "ShortGuid": "1.0.2"
  },
    "frameworks": {
        "netcoreapp1.0": {
          "dependencies": {
            "Microsoft.NETCore.App": {
              "type": "platform",
              "version": "1.0.0"
            }
          },
            "imports": [
                "dnxcore50",
                "portable-net45+win8"
            ]
        }
    }
}

Startup.cs configuration for Jwt based auth
        public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
        {
            //...

            var options = new JwtBearerOptions
            {
                Audience = Configuration["auth0:clientId"],
                Authority = $"https://{Configuration["auth0:domain"]}/",

            };
            app.UseJwtBearerAuthentication(options);

            app.UseCors(builder =>
            {
                builder
                    .AllowAnyOrigin()
                    .AllowAnyHeader()
                    .AllowAnyMethod()
                    .AllowCredentials();
            });

            app.UseMvc();

            //...
        }

Thanks!

Configuration["auth0:domain"] is returning null. Your config sources may not be set up correctly.

@Tratcher  Thanks a ton! After adding application settings files to my unit test project and the following section in project.json my tests work fine!
"buildOptions": {
  "copyToOutput": [ "appsettings*.json" ]
}


Update status on campaign save

What's this PR do?
Updates the campaign status when someone changes the campaign run on campaign nodes.
Also, updated the hooks I was using to update the campaign status on campaign run node save to use hook_node_submit so we can more reliably get the values that had just been submitted by the user.
Where should the reviewer start?
Start at dosomething_campaign.module where I use hook_node_validate() to get the form state of the campaign node that is submitted and allows me to update the value of fields before the form actually gets submitted. This is where we update the status.
What are the relevant tickets?
Fixes #6052

@angaither updated the campaign status function to check for null dates.

:+1:


Add more embedding models

In addition to potentially interesting open source models, we should add deprecated models like OpenAI ada-002 and each specific preview version. In supporting  #13 we would want to let people import embeddings they already made, and there are likely tons of embeddings made with the older models.

Thanks to @dhruv-anand-aintech for pointing out LiteLLM as a possible way of adding support for many more providers/models:
https://litellm.vercel.app/docs/embedding/supported_embedding
https://litellm.vercel.app/docs/providers

We should also look into allowing the user to freeform add a huggingface transfomer model.
I'm imagining the model dropdown would have a "Custom" option, which would then display a text input for the huggingface model address, i.e. Snowflake/snowflake-arctic-embed-m-long and then have some inputs to choose max-tokens (context length) and the pooling method (essentially whats currently input via the json config https://github.com/enjalot/latent-scope/blob/main/latentscope/models/embedding_models.json

Hi - a vote for custom. I also have to admit I sometimes want glove/word2vec models too, for some kinds of text grouping problems. seems like it would be easy to do?

@arnicas would implementing something like this with pre trained glove models?
https://www.geeksforgeeks.org/pre-trained-word-embedding-using-glove-in-nlp-models/
I'm now considering using sentence-transformers and powering the embedding choice via a HuggingFace hub API search

I've made some progress switching to sentence_transformers and enabling backend support for passing in any huggingface model id. Next I'll work on an advanced dropdown that lets you search the HF api or pick from available 3rd party (and even recently used models)

I just pushed support for searching the HuggingFace hub for any sentence transformer model (defaulting to showing 5 most downloaded) instead of needing to preconfigure each available model. closing this issue as its mostly supported via the new 0.4.0 release
I will open a new one with your request @arnicas


Fix Babel Example

examples/babel/app.py still imports TextField from wtforms which has been removed. This PR changes it to StringField.
Checklist:

[ ] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[ ] Add or update relevant docs, in the docs folder and in code.
[ ] Add an entry in docs/changes.rst summarizing the change and linking to the issue. Add .. versionchanged:: entries in any relevant code docs.

Thank you!


Filters not generated for owner field in model

Everything is in the title.
I tried to add the owner field explicitly but then the onCreate and onUpdate subcriptions fails.
Is this normal?
    filter: {
          owner: { eq: this.stateUser.id }
        }

Error:
"The variables input contains a field name 'owner' that is not defined for input object type"

How did you define your schema?
Please also provide the following information:
CLI version
OS

How did you define your schema?
Please also provide the following information:

CLI version
OS

CLI version:
➜  ~ amplify --version
4.24.0

OS:
➜  ~ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.15.5
BuildVersion:	19F101

Schema:
I made a minimal example based on the doc that reproduces the error and uses the same authentication rules as in my schema.
type Blog
  @model
  @auth(
    rules: [
      # Admin users can access any operation.
      { allow: groups, groups: ["Admin"] }
      # Authorize create, update, read.
      { allow: owner, operations: [create, update, read] }
      # Authorize access via API key.
      { allow: public, provider: apiKey }
    ]
  ) {
  id: ID!
  name: String!
  posts: [Post] @connection(name: "BlogPosts")
}

type Post
  @model
  @auth(
    rules: [
      # Admin users can access any operation.
      { allow: groups, groups: ["Admin"] }
      # Authorize create, update, read.
      { allow: owner, operations: [create, update, read] }
      # Authorize access via API key.
      { allow: public, provider: apiKey }
    ]
  ) {
  id: ID!
  title: String!
  blog: Blog @connection(name: "BlogPosts")
  comments: [Comment] @connection(name: "PostComments")
}

type Comment
  @model
  @auth(
    rules: [
      # Admin users can access any operation.
      { allow: groups, groups: ["Admin"] }
      # Authorize create, update, read.
      { allow: owner, operations: [create, update, read] }
      # Authorize access via API key.
      { allow: public, provider: apiKey }
    ]
  ) {
  id: ID!
  content: String
  post: Post @connection(name: "PostComments")
}

It really annoys me in my use case because I have a user group that has the admin group and that has access to everything and it screws up my queries as I can't filter by owner.
It's really something basic I didn't expect to have this problem at all.
It looks like it has something to do with #300
I hope we can solve this problem quickly.

ping @UnleashedMind

@UnleashedMind ?

I tested with the latest version 4.29.x, and the issue seems to be resolved already.
With the annotated schema that you provided, the owner field is added into to the compiled schema by the Amplify CLI.
Please test and confirm.


Implement subqueries in the transpiler

Subqueries need to be implemented in the transpiler. The first step is to define the method for how we evaluate and construct queries with subqueries in the transpiler README and then actually implement it.

This will likely require a refactor of the transpiler to use the existing query compiler from the query package.
I'm going to put this back in the backlog at the moment since we are not addressing it immediately.


proxy: add more error cases to retry connect

Problem
In the logs, I noticed we still weren't retrying in some cases. Seemed to be timeouts but we explicitly wanted to handle those
Summary of changes
Retry on io::ErrorKind::TimedOut errors.
Handle IO errors in tokio_postgres::Error.
Checklist before requesting a review

[X] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

I was also thinking this. set the timeout to 2s each connection rather than 10 seconds and 10 retries

I'm going to open a separate PR for this so it can be discussed more without blocking this


Error while using it with Next.Js 13

Hi there,
Don't know if it's due to Next.Js or not.
But when impletementing the lib it actually works but I am getting an error in my console.

Any idea about it ?
Thanks for helping.

Me too!

I've ran into this as well.

I've ran into this as well.

Also with Next.js ?
If this can help the maintainer, what config are you using ? Here I am in full static.

Interesting because the website itself is using Next 13

Comparing them, it appears to be all the minified variable names that differ.

Fixed with #12, please try https://github.com/shuding/react-wrap-balancer/releases/tag/0.2.4


increase codacy grade

We want to have an A from the automated code review. Some of the raised issues (for example security) are not relevant for us but these can then be removed from inspection through proper codacy configuration.

This has solved itself, as I turned of the security warnings that do not apply to our program.


ESpec helpers

Is there any interest in this? If so, I'll contribute a module (Bamboo.Spec, perhaps).

@facto I hadn't heard of ESpec before. I think this is a great idea, but since I don't use it and no one else at thoughtbot uses it, I don't think we would be the best maintainers for this.
What do you think about making a bamboo_espec library? I'd be happy to put a link in the README. That way people can find it, and it will be better maintained by people that actually use ESpec. Thoughts?

Definitely! I'll send a PR with a link in the README when it's ready. Cheers.


If progress is cancelled but does not manually emit an end event, the debug view remains 'busy'

Refs: https://github.com/microsoft/vscode/issues/92914

Have a progress event
Cancel it, and don't manually send a progressEnd after cancellation from the debug adapter
The debug view gets stuck as being "busy"

https://memes.peet.io/img/20-03-659125af-4489-4877-83c7-874ed6036e4e.webm

This is designed behavior, since we can not assume that the debug adapter trully canceled the progress.
I am open to suggestions here
Currently we will complete the progress if the session goes down, which is fair.
fyi @weinand

I think a successful reply to the cancel method call from the debug adapter is probably enough of an acknowledgement. If the adapter says the 'cancel' call succeeded and didn't actually cancel the progress event, that's a bug on their side.


Moved infractions off the user and onto the guild with a key to the user

It is easier to track guild-level cases without having to traverse the entire database to pull up what infractions occurred on a given guild, and thus it was moved.
Along with that, IDatabaseService, and it's concrete implementation have been removed. Some slight improvements have been made to the InfractionService, and multiple UserFlags have been removed, causing their values to differ.
This will be pushed as part of 1.4, and with further testing, cleanup, and hopefully more Unit Tests, we will precede to push to master/prod. cc @NatsumiHB and @CalebABG, let me know if any changes need to be made.

Done


Sync websocket action with the one from openwhisk

see https://github.com/openwhisk/openwhisk/pull/1054 for change to this action.

This one looks good to me.
We can merge it as long as the travis ci passes. Thank you. @jasonpet


Updated personalized install code to use github.io

@plusjade, this is a tweak to gh-pages. Isn't the generator on Ruhoh? If so, it's as simple as tweaking "github.com" to be "github.io". If not, I'll merge this PR. Assuming edits won't take effect from the gh-pages branch, though.

@groundh0g is this project dead?

@ilivewithian Nope. Sorry for inactivity recently. Started new job in another state and have been travelling 100%. We close on our new house in GA on the 16th, so I'm hoping things will settle down shortly thereafter.

I'm merging now. Don't think it will have any effect, though. Pretty sure the jekyll-bootstrap site is powered by @plusjade's static blog engine, Ruhoh.


Launch process with busy loop at entry point

"BusyLoopLauncher" is a utility to launch a process and install a busy
loop at entry point. It uses functions defined in "BusyLoopUtils.h", which
also contains functions to resume execution of the original code.
Tests are found in "BusyLoopLauncherTest".
Note that resuming the execution of the launched process has not been
implemented yet. We test that functionality in the current process for now.
Tests: ran tests.

@danielfenner , @florian-kuebler , thanks for the comments. The PR is in a better state now, the end-to-end loop is working. We can launch a process that spins at entry point, inject a dll very early during process creation, before main is called, replace the busy loop by the original code and suspend the main thread until we decide to resume it for normal process execution. Please take another look, thanks!


Workspace backup CLI tool

A little tool to back up workspaces.
python -m capellacollab.cli ws volumes --namespace collab-sessions

python -m capellacollab.cli ws ls  persistent-session-admin --namespace collab-sessions

python -m capellacollab.cli ws backup persistent-session-admin --namespace collab-sessions

python -m capellacollab.cli ws restore persistent-session-admin persistent-session-admin-backup.tar.gz --namespace collab-sessions

Thanks for the useful CLI, it works very well for most workspaces.
There is just one small issue with too long PVCs:

Also, it would be good to have a --all flag to download all workspaces at once. We solved it by a simple bash script:
for workspace in  $(python -m capellacollab.cli ws volumes --namespace t4c-sessions)
do
    echo "Downloading workspace $workspace..."
    python -m capellacollab.cli ws backup $workspace --namespace t4c-sessions
    echo "Finished downloading workspace $workspace..."
done;

Also, we need a bit of documentation:

A documentation for the CLI itself
A documentation mentioning the complete backend & restore procedure for the Collaboration Manager data.


Remove unlawful alternative

This PR replaces Alternative instance with Plus instance because Observable does not always satisfy distributivity law. See test for more info.

This is weird, all the following libraries define an Alternative instance:

https://github.com/bodil/purescript-observable
https://github.com/jasonzoladz/purescript-rxjs
https://github.com/LukaJCB/purescript-rxps

Neither of them tests Alternative laws.
The test in this PR shows that distributivity of alt doesn't hold - is it correct or am I missing something?

@raveclassic does the actual problem stem from the ap implementation which uses combineLatest? I guess should use zip instead
ap: (fab, fa) => zip(fab, fa).pipe(rxMap(([f, a]) => f(a)))

@mlegenhausen what do you think

@gcanti Exactly. But I'm not sure what will be the impact of this...

If combineLatest is changed to zip, ap test fails

Also the following fails:
it('array.sequence', () => {
    const timeline = {
      a: '--a--------|',
      b: '----b------|',
      c: 'c-----d----|',
      r: '----x-y----|'
    }
    new TestScheduler(assert.deepStrictEqual).run(({ cold, expectObservable }) => {
      const fa = cold(timeline.a)
      const fb = cold(timeline.b)
      const fc = cold(timeline.c)
      const fr = array.sequence(R.observable)([fa, fb, fc])
      expectObservable(fr).toBe(timeline.r, { x: ['a', 'b', 'c'], y: ['a', 'b', 'd'] })
    })
  })

And this is how sequence is mostly used for Observables, that's a massive break.

@raveclassic never mind, zip doesn't behave like I thought

Definitly a massive break just from a practical standpoint in all the years I have used rxjs I have "almost" never used zip at all. combineLatest is the de facto default combinator in this case and it seems not to be trivial to change from combineLatest to zip.

So what is the decision, @gcanti?
This is not a breaking change because we still have zero from Plus typeclass, we just relax constraint on alt to not be distributive. Something similar was done for Semigroup/Magma.

@raveclassic this is a theoretical problem: what's the meaning of = in the Distributivity law?
A.ap(A.alt(fab, gab), fa) = A.alt(A.ap(fab, fa), A.ap(gab, fa))

or, in other words, given two Observables when we can say that they are equal?
or, in other words, is it possible to define Eq<Observable>?

given two Observables when we can say that they are equal?

IMHO from a practical point of view it seems only to be relevant that two Oberservables are equal when the values A are equal at a certain point in time t. Looking at the whole sequence of As from t0 till tcomplete or any other partial sequence is uncommon (Sorry for my missing mathematical precision).

is it possible to define Eq<Observable>

Seems misleading as we can't define it for Task either 😉 but I know what you mend.

we can't define it for Task

@mlegenhausen well, actually we can, the trivial one
import { Eq } from 'fp-ts/lib/Eq'
import { constTrue } from 'fp-ts/lib/function'
import { Task } from 'fp-ts/lib/Task'

export function getEq(): Eq<Task> {
  return { equals: constTrue }
}

I'd say that two observables are equal if values, time (discrete according to some virtual scheduler, like marbles) and order of their events are equal in a certain fixed time period of observation. The same applies for Task although we don't test the time of its value because we have no virtual scheduler.

@raveclassic so cold('-a--') != cold('--a-')?

If both are subscribed in a single moment (the first -), then yes, they are different in a way they produce values (being cold). The period of observation should be the same (no shifts) for all observables.

The same applies for Task although we don't test the time of its value because we have no virtual scheduler

This doesn't seem right as equality, Task is useful precisely because may yield different values.
Let's say you define a Task<Weather> which fetches weather infos, and then you run it two times, today and tomorrow
const fetchWeather: Task<Weather> = ...

const today = fetchWeather
...
today()

// later...
const tomorrow = fetchWeather
...
tomorrow()

You likely get different data but how is it possible that tomorrow != today when tomorrow === today (i.e. they even relate to the same value in memory)?
All Task<Weather> must be equal.
I'm not saying that is not useful to reason about what happens after you run a task (or subscribe to an observable), but that's a slippery slope. Is what actually happens at runtime related to the meaning of = and/or to the laws? This does seem arguable.
TLDR: IMO you can't define an Eq based on the runtime behavior

I'm not a pro in the field of FRP, but Task (and Observable) are time-dependent computations which means they may produce different values if run in different time. This explains why today === tomorrow but today() !== tomorrow(). The time is an implicit dependency. If it was explicit then we would define Task as type Task = (t: number) => Promise. Then it would totally make sense that
const today = Date.now();
const tomorrow = today + 1000 * 60 * 60 * 24;
fetchWeather(today) !== fetchWeather(tomorrow);

Related (but out of scope): I'm studying this paper and it introduces a so called "Now"-computation being essentially an explicit way to define dependency on time. There's also a library implementing that concept: https://github.com/funkia/hareactive#now

type Task = (t: number) => Promise

Thats not the signature of Task what you mean is type Forecast = (t: number) => () => Promise<Weather>.
I think this is important, cause the computation behind it is the same Task<Weather>. So I currently don't know if we could decide if these computations are equal by just looking on its outcome, cause my naive approach would be to use eqStrict but this will fail cause we create new references which could do logically the same?

Thats not the signature of Task

It doesn't really matter. We can describe type Task = IO<Promise> which tracks that the computation should be "invoked" (that () call). We can however say that the computation is "invokable" in a specific moment of time so that it produces a type Behavior = (t: Time) => A: type Task = Behavior<Promise>. This reflects that starting in different moments in time the task produces different promises (different values). Finally we would declare type Forcast = Task<Weather>. But to run such computation we would need to find the current moment in time:
declare const forecast: Forecast<Weather>;
const nowForecast = forecast(performance.now());

The same as we would do for usual Task:
declare const forecast: IO<Promise<Weather>>;
const nowForecast = forecast(); // <-- time is implicit here

I do not insist on introducing these concepts but IMO they describe what happens in the most accurate way.

To be honest, eqStrict often fails. But I see what you mean, we cannot define an Eq for Promise. Specifically because it has implicit time dependency :) If it was smth like type Promise = (t: Time) => Option we would just memoize it with t argument. Then we would produce the same reference for equal time arguments (omitting memory). Going further if we had a scheduler virtualising time we would just instantly run the timeline of our observation period (subscribe/unsubscribe) with some discrete notion of time and check if occurrences of two promise results are equal.

Summing up, Task and Observable conceptually are the same. Even more, if underlying Promise (implementation detail actually) was lazy, they would even have the same signatures: Promise#then is Observable#subscribe.

Take a look at the Eq<Observable> in the PR:
const liftE = (E: Eq): Eq<Observable> => {
  const arrayE = getEq(E)
  return {
    equals: (x, y) => {
      const scheduler = new TestScheduler(assert.deepStrictEqual)
      const xas: Array = []
      x.pipe(subscribeOn(scheduler)).subscribe(a => xas.push(a))
      const yas: Array = []
      y.pipe(subscribeOn(scheduler)).subscribe(a => yas.push(a))
      scheduler.flush() // <-------- run the timeline
      assert.deepStrictEqual(xas, yas)
      return arrayE.equals(xas, yas)
    }
  }
}

The same could be done for Promise if we could change the underlying scheduling.

Ah ok the n was the time passed. Sorry haven't come to read the paper yet.

Summing up, Task and Observable conceptually are the same.

I would say the same. So coming back to the original question

Sorry my fault.

@raveclassic you can't define an Eq instance based on side effect execution.
IO, Task, Observable... they are all just values, you can think of them as recipes for the runtime. And the runtime is something you must consider out of reach.
import { IO } from 'fp-ts/lib/IO'

let counter = 0

const increment: IO<number> = () => counter++

How can you define an Eq instance for IO<number>?
This is not possible:
import { Eq } from 'fp-ts/lib/Eq'

const eq: Eq<IO<number>> = {
  equals: (x, y) => x() === y() // <= you can't run the side effects here
}

Here's another possible implementation of increment as a simple value, a recipe for the runtime (i.e. The Great Interpreter Of All Side Effects)
class IO {
  readonly A: A
  readonly type: 'IO'
}

class Increment extends IO<number> {
  readonly what_to_do = 'please increment the counter'
}

class Decrement extends IO<number> {
  readonly what_to_do = 'please decrement the counter'
}

// other IO recipes...

const increment: IO<number> = new Increment()

let counter = 0

function interpreter(recipe: IO) {
  if (recipe instanceof Increment) {
    counter++
  } else if ( ... ) {

  }
}

All Increment instances are equal.
You can consider fp-ts's IO
type IO = () => A

as a recipe with its own little, specific interpreter packed together.
However only the runtime is allowed to execute these recipes.

@gcanti Well... Makes sense :/
Ok. How can we check the laws safely and correctly for #27 ?

We cannot prove laws of observables (the way proofs work in category theory) if we don't lawfully implement the observables ourselves. We are choosing to not implement observables ourselves so we must assume that observables is a black box.
So because we cannot prove the laws, we can brute force it by using runtime equality and running it for infinite cases.
Or we can use a heuristic to predict correctness of laws by using runtime equality for a few edge cases (that we think are edgy).
When runtime equality is not an option, there isn't much to do but predict based on gut feelings?


Issue with creating customer portal

Bug report

Extension name: [e.g. firestore-stripe-subscriptions]

Describe the bug
I am having some issues with creating a customer portal.
The customer portal link only works if the user is authenticated and has just paid (the session where they go to checkout), and in session.
As soon as the user signs out and signs back in the link to the customer portal does not work anymore, and I get "Unhandled Runtime Error
Error: Missing required param: customer."
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
This is how I am creating a checkout session and creating link to customer portal:
`import firebase from '../src/firebase/config';
import getStripe from './initializeStripe';
import NProgress from 'nprogress';
// import firebase from '@firebase/app';
require('firebase/functions');
export async function createCheckoutSession(uid: string) {
NProgress.start();
const firestore = firebase.firestore();
const checkoutSessionRef = await firestore
    .collection('users')
    .doc(uid)
    .collection('checkout_sessions')
    .add({
        price: process.env.NEXT_PUBLIC_STRIPE_PRODUCT_PRICE,
        success_url: 'https://mantrahub.co/mantras',
        cancel_url: 'https://mantrahub.co/auth',
    });

checkoutSessionRef.onSnapshot(async snap => {
    const { error, sessionId } = snap.data();
    if (error) {
        // Show an error to your customer and
        // inspect your Cloud Function logs in the Firebase console.
        alert(`An error occured: ${error.message}`);
    }
    if (sessionId) {
        const stripe = await getStripe();
        stripe.redirectToCheckout({ sessionId });
    }
});

}
const app = firebase.app();
export async function goToBillingPortal() {
const functionRef = app
.functions('us-central1')
.httpsCallable('ext-firestore-stripe-subscriptions-createPortalLink');
const { data } = await functionRef({
returnUrl: ${window.location.origin}/profile,
});
window.location.assign(data.url);
}`
This is the page that has the button to go to customer portal:
`import React, { useState } from 'react';
import firebase from 'firebase/app';
import 'firebase/firestore';
import 'firebase/auth';
import { useAuth } from '../contexts/AuthUserContext';
import { goToBillingPortal } from '../../stripe/createCheckoutSession';
console.log(goToBillingPortal);
const Profile = () => {
const { user, signout } = useAuth();
const [isBillingLoading, setBillingLoading] = useState(false);
return (
<button
onClick={() => {
setBillingLoading(true);
goToBillingPortal();
}}
>
Manage Billing

);
};
Here is the Firestore rules:
`rules_version = '2';
service cloud.firestore {
match /databases/{database}/documents {
match /users/{uid} {
allow read, write: if request.auth.uid == uid;
  match /checkout_sessions/{id} {
    allow read, write: if request.auth.uid == uid;
  }
  match /subscriptions/{id} {
    allow read, write: if request.auth.uid == uid;
  }
}

match /products/{id} {
  allow read: if true;
  allow write: if false;

  match /prices/{id} {
    allow read: if true;
    allow write: if false;
  }

  match /tax_rates/{id} {
    allow read: if true;
  }
}

}
} export default Profile;
Expected behavior
For users to be able to go to customer portal after their customer checkout session
Screenshots

System information

OS: [e.g. macOS, Windows]
Browser (if applies) [e.g. Chrome, Safari]

Additional context
Add any other context about the problem here.

Sorry for the delay here. Do you see any logs in the createPortalLink function in your Firebase console?

Same error occurred for me. following logs were reported in the firebase console. It's very helpful if you fix it.
12:09:21.356
ext-firestore-stripe-subscriptions-createPortalLink
Function execution started
12:09:21.360
ext-firestore-stripe-subscriptions-createPortalLink
Function execution took 5 ms, finished with status code: 204
12:09:21.373
ext-firestore-stripe-subscriptions-createPortalLink
Function execution started
12:09:21.376
ext-firestore-stripe-subscriptions-createPortalLink
Callable request verification passed
12:09:21.662
ext-firestore-stripe-subscriptions-createPortalLink
❗[Error]: Customer portal link creation failed for user [xwYCKQYhObcd9M3BOaMfcsdNxzA3]: Missing required param: customer.
12:09:21.663
ext-firestore-stripe-subscriptions-createPortalLink
Function execution took 291 ms, finished with status code: 500

I found that reason of this problem is that I set firestore document "customers" when user login.
It was solved I changed my code as follows.
  firebaseApp.firestore().collection("customers").doc(authResult.user.uid).set(
    {
      uid: authResult.user.uid,
      email: authResult.user.email,
      name: authResult.user.displayName,
      provider: authResult.user.providerData[0].providerId,
      photoUrl: authResult.user.photoURL,
    },
+    { merge: true }
  );

I am not sure hesamalavi is at same situation or not.

Thanks for the update @tanosugi.
I'll close this issue as a solution has been found.
Happy to re-open if another resolution is required or if this can be considered a potential documentation update (for example).


inconsistency in migration: removal of isAncestor and getParent in GraphModel

In the old version, mxGraphModel contains the isAncestor function. In the new version, the isAncestor function is replaced by the isAncestor method in Cell.js. However, the input parameters are changed, causing inconsistency in migration.
mxGraph4.2.2

maxGraph0.8.0: The GraphDataModel does not contain the isAncestor function. Instead, the isAncestor function in the Cell.js is invoked.

And the getParent method has exactly the same problem.
mxGraph4.2.2

maxGraph0.8.0

They are not serious problem. I can modify my code accordingly.

Hello @Duoladuola
The change was made voluntarily during the migration of the mxGraph code.
For now, I'm creating a PR to try to improve the migration documentation about the removal of the 2 methods.  The getParent method has already been mentioned.
As stated in https://github.com/maxGraph/maxGraph/discussions/179#discussioncomment-5388614, the removal of these GraphDataModel methods was done to simplify the code base, but it could limit extension capabilities.
If this is the case, create a dedicated question explaining the specific limitations that the current maxGraph code introduces.


Pet cat plugin

A complete plugin for your pet cat.

Notify whenever your kitten is hungry or needs attention
Infoboxes with timers till next actions
Pet kitten growth timer infobox to Cat
Cat growth timer infobox to Overgrown Cat
Wily cat reversal timer infobox to Lazy Cat
Cat hitpoints threshold notification while fighting Hell-rat behemoth/King rat
Cat training NPCs highlight/indicator
Configurable Hell-rat behemoth indicator or colored highlight according to the appropriate spice color

Duplicate of #3815


The help pop up does not show up for method chains

I was adviced to migrate this issue here from https://github.com/microsoft/vscode-jupyter/issues/10004
Environment data

VS Code version: 1.67
Jupyter Extension version (available under the Extensions sidebar): v2022.4.1011282140
Python Extension version (available under the Extensions sidebar): v2022.6.0
OS (Windows | Mac | Linux distro) and version: PopOS 21.10
Python and/or Anaconda version: 3.9
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Jupyter server running: Local | Remote | local

Expected behaviour
The help for the method would show up correctly
Actual behaviour and step to reproduce
If I type the name of a top level object, the help bubble shows up fine:

If I chain a function to this object I get either just a single line in the help bubble, or the same message as for the parent object

Logs
The output pane is empty

I'm not seeing this behavior. I'm using:

VS Code: 1.88.0-insider
Python extension: v2023.8.0
Jupyter extension: v2024.3.2024030101
Pylance extension: v2024.2.105

The VS Code and extension versions that you mentioned above are very old. Please upgrade to latest and we can reactivate this issue if it's still not fixed for you.

Thanks @debonte , I just tried again with v1.86 and I see the popup like in your screenshot so that is great! I noticed that I no longer see a comprehensive popup for the first part of the chain, e.g. pd.DataFrame( just shows () -> None instead of the full dosctring that shows when I hover with the mouse over that class. Do you see the same thing?

Do you see the same thing?

Yes. Looks like this regressed in Pyright 1.1.335. Could you file an issue at https://github.com/microsoft/pyright/issues?

Thanks for confirming, I filed https://github.com/microsoft/pyright/issues/7405


latest version requires cuda >= 12.1?

I have a problem getting the garbage outputs with version >= 0.2.2, but works fine with lower version e.g. 0.2.1.post1.
Could it be related to cuda version? mine is 11.8.
I also have a try with cu118 version, or build from source, but didn't work.

same issue #1929

Install the CUDA 11.8 version as per instructions here: https://docs.vllm.ai/en/latest/getting_started/installation.html
For VLLM_VERSION use 0.2.5
# Install vLLM with CUDA 11.8.
export VLLM_VERSION=0.2.4
export PYTHON_VERSION=39
pip install https://github.com/vllm-project/vllm/releases/download/v${VLLM_VERSION}/vllm-${VLLM_VERSION}+cu118-cp${PYTHON_VERSION}-cp${PYTHON_VERSION}-manylinux1_x86_64.whl

# Re-install PyTorch with CUDA 11.8.
pip uninstall torch -y
pip install torch --upgrade --index-url https://download.pytorch.org/whl/cu118

@miko7879 thanks, very helpful.


Jax Cliffwalking Env

Description
This adds a CliffWalkingJaxEnv to the tabular environment suite, as well as the underlying FuncEnv subclass CliffWalkingFunctional.
CliffWalkingJaxEnv is registered with the name "Jax-CliffWalking-v0" This PR still needs a bit of polish work, but you can try it out for yourself in GUI mode with
python3 ./gymnasium/envs/tabular/cliffwalking.py

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist:

[ ] I have run the pre-commit checks with pre-commit run --all-files (see CONTRIBUTING.md instructions to set it up)
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

added that typing fix


Update popular contracts on explore

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
The focus of this PR is to refactor the ExploreCategory interface and introduce ModularContractInfo for better contract organization.
Detailed summary

Introduced ModularContractInfo type to store contract information with title and description
Reorganized contracts in ExploreCategory to use ModularContractInfo or PublishedContractID
Added modularOpenEdition, modularNFTDrop, and modularNFTCollection with detailed information

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#4673  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MananTank and the rest of your teammates on  Graphite


[Vcpkg] Fix macOS applocal.py dependency bundling error

This is the same issue and fix applied here https://github.com/OpenZWave/ozw-admin/issues/4.
This issue occurs when building a .app bundle (when MACOSX_BUNDLE is ON). I believe it's related to Python version or macOS Catalina. Vcpkg is using Python 3.8.1 (validated by print statement within applocal.py itself).
Let me know if I can validate anything else. I was hoping to add an automated test for running macOS app package builds, but it looks to me like we don't have automated testing of Vcpkg itself for macOS ☹.
Describe the pull request

What does your PR fix? Fixes issue #
Currently no open issue, though this is a problem.

Which triplets are supported/not supported? Have you updated the CI baseline?
This is relevant only for macOS. Problem was observed on Catalina (so, 64-bit only).

/azp run

/azp run

This is correct, as far as I can tell. I don't know why we weren't decoding before... I wonder if it was getting run in python2? Thanks @kevinhartman :)


Expand the default decorator markers

Looks like this is the range of default decorator markers we can expect.
Source: https://github.com/sanity-io/block-content-to-hyperscript/blob/master/src/buildMarksTree.js#L1

Better to merge #4 and redo


Clarify confusion

This rewords a sentence to clarify a little better.

Going to just merge this, since it's a simple change to a text doc.


shared: remove is prefix from JavaScript class properties

Closes #182

Hey, have you checked v1 typings and */js/compatiblity stuff? You might break v1 compat with the changes you made.

@carlos-menezes remove "Draft" tag once it's ready for review 👍

Sorry for the delay, @Yiin . Will look into the rest of this PR this weekend.

Hey there, any progress on this?

Really sorry for the delay, these last few weeks have been crazy. Anyway, I'm marking this a ready for review after the last commit. Let me know about any wrong-doings.


elasticsearch is unavailable

When creating a view for elasticsearch data source, a null pointer error will be reported when elasticsearch data source is selected. Tracking the source code found that the code is always using empty objects.

you can try some other es jdbc driver

When creating a view for elasticsearch data source, a null pointer error will be reported when elasticsearch data source is selected. Tracking the source code found that the code is always using empty objects.

大佬，你用的哪些连接ES的依赖包的，求指导。感谢

When creating a view for elasticsearch data source, a null pointer error will be reported when elasticsearch data source is selected. Tracking the source code found that the code is always using empty objects.

大佬，同问，依赖包是啥，链接那该怎么写

额，同问demo走通了，jdbcTemplate这个走不通


Port the tests in test/ansible for the new layout

The tests in https://github.com/operator-framework/operator-sdk/tree/master/test/ansible still using the legacy layout. This task is for we port them for the new one.

c/c @asmacdo @fabianvf @estroz

Shows that it has been done in #3433,

We are closing this one in favor of: https://github.com/operator-framework/operator-sdk/issues/4025


GRANDPA assumes that light clients only need to know authorities list and slot number

GRANDPA assumes that light clients only need to know authorities list and slot number.  This blocks BABE epochs from working on light clients.

Why should GRANDPA consensus influence anything about BABE?
As long as light clients know the next authorities 1 epoch ahead, it should be fine under a synchrony assumption (which BABE has).


Player Data Not Saving

I was testing out the mod using Wurst Client, and I flew upward and got disconnected. After reconnecting I tried using a elytra with the "jetpack" hack to fly around, afterword I went to shut down the server and I noticed in the console:
"[15:28:01] [Server thread/WARN]: Failed to save player data for Blue_Dye"
After reconnecting and disconnecting a couple of times I found that I always respawned up in the air where I got disconnected. I have verified that player data is saved successfully without GolfIV. I have no other mods than GolfIV and fabric api. Log attached. Build is https://github.com/samolego/GolfIV/actions/runs/438107637.
2020-12-26-3.log.gz

Hi, thanks for reporting! I'll look into it when I have time 😉 .

Did you die during the test proccess? I think this might be one of the reasons ...

Did you die during the test proccess? I think this might be one of the reasons ...

Forgot to close this on push :)

Forgot to close this on push :)


Structure paperclip_<fn_name> should have CamelCase name

Every time I apply #[api_v2_operation] to a function, I get an info-level warning from rust-analyzer telling me that I should be naming a struct generated by the derive using CamelCase.
When I do this:
/// Gets all users
#[api_v2_operation(tags("Users"))]
#[get("/users")]
async fn get_all(pool: web::Data<PgPool>) -> Result<Json<Vec<User>>, Error> {
    match User::get_all(&pool).await {
        Ok(u) => Ok(Json(u)),
        Err(e) => Err(ErrorInternalServerError(e)),
    }
}

I get this warning:
Structure `paperclip_get_all` should have CamelCase name, e.g. `PaperclipGetAll`

I'm not seeing anyone else with this error in the issues so I'm thinking I may not have configured something correctly.
I am using Neovim v8.0.0 with rust-tools which uses rust-analyzer.

hmm Interesting, that should not be highlighted as an error AFAICT: https://github.com/paperclip-rs/paperclip/blob/aac5bc734a470f46c31b727b859cf9089f22c0be/macros/src/actix.rs#L1902
Unless I'm looking in the wrong place.. would you be able to show me the generated code, eg with cargo-expand?

Here's a snippet from the output from cargo expand
        struct paperclip_create;
        #[allow(non_camel_case_types, missing_docs)]
        pub struct create;
        impl create {
            fn resource() -> paperclip::actix::web::Resource {
                /// Creates a new event
                fn create(

If I'm not mistaken, doesn't the #[allow(...)] meta need to come before the type name?
Actually, I think the error stems from the difference between:
#[api_v2_operation(tags("Users"))]
#[post("/users")]
async fn create(

And:
#[post("/users")]
#[api_v2_operation(tags("Users"))]
async fn create(

In the latter case, the error seems to go away.

Ah right, I suspect that's because in the first case the "paperclip" struct actually defined within the struct created by the other macro.
Would you be able to try this branch (https://github.com/paperclip-rs/paperclip/tree/clippy-fix) to see if it fixes the issue?


Checkbox support

What a great editor! Congratulation to for this great software.
Is checkbox support planed? Something that:

[ ] test
[x] test2

Thank you!
Up to your question what kind of backend would you use for the checkbox toggling, once the checkbox is rendered? Or maybe I am missing something

Thank you for the fast answer.
I would respond to changes from markdown.

I think there is checkbox support in lexical:

https://lexical.dev/docs/api/modules/lexical_list
https://codesandbox.io/embed/lexical-list-plugin-example-00d642?fontsize=14&hidenavigation=1&module=/src/Editor.js,/src/plugins/ListToolbar.tsx&theme=dark&view=split

Yes, there is - it's fairly easy to implement it in the editor. I was more interested in how you're going to deal with the checkboxes "outside" of the editor. For example, when you put checkboxes in the GitHub issue, they are interactive (and modify the actual markup) when rendered in read-only mode.

hi, I try to implement task list by extend lists plugin. But I encounter some difficulties.
lexical determine a list is checkbox by ListNode.__listType
export declare class ListNode extends ElementNode {
    /** @internal */
    __tag: ListNodeTagType;
    /** @internal */
    __start: number;
    /** @internal */
    __listType: ListType;

but mdast(with mdast-util-gfm-task-list-item) determine a list is checkbox by property list.children.checked
{
     type: 'list',
     ordered: false,
     start: null,
     spread: false,
     children: [
       {
         type: 'listItem',
         spread: false,
         checked: true,
         children: [
           {type: 'paragraph', children: [{type: 'text', value: 'Done'}]}
         ]
       }
     ]
   },

so in the file mdastListVisitor I must do the thing like this
const isCheck = mdastNode.children?.[0]?.checked !== null && mdastNode.children?.[0]?.checked !== undefined
const lexicalNode = $createListNode(isCheck ? 'check' : mdastNode.ordered ? 'number' : 'bullet')

Is my implementation correctly, do you have better suggestions?

I guess that's the way to go. Technically, the user can mix and match different list items, not sure how it would work then, though.

Hi, checkbox support would be great. In fact, it's just a display issue.
If the raw markdown looks like this
* [ ] foo
* [x] bar

then display like this in the rich text editor

[ ] foo
[x] bar

About storing the state of the boxes, I store the entire raw markdown in my database, so changing the state of the checkbox in rich text would be reflected in raw and vice versa.
I think this would be a basic use case similar to the lists. I would implement it myself but find the Lexical system a little bit overwhelming and it will take me some time to make it. It's probably a lot easier for @petyosi :)

@ValiDraganescu I appreciate your faith in my capabilities. What I do appreciate more though is some help and contributions - the project is fairly large, so the backlog is much larger than what I can handle.

Thank you very  much.


Bump to dbt <2.0.0 (1.0.3)

@ssassi any plan to review/merge/release this?  seems like this repo is way behind current dbt versions so I probably won't use it until it's more up to date

@bbrewington I think we should actually just archive this project as we are not maintaining it. Have you seen that dbt-coves has a setup method?
What is your use case, we are going to be adding some other things to dbt-coves, so feedback might help us.

@noel was just exploring tooling for analyst developer productivity, so will definitely get back on trying out dbt-coves!  (yeah, if this one isn't maintained, might be good idea to archive...I'll assume to use the functionality in dbt-coves)
This was my blocker today and got it figured out thanks to my new friend Jared, so will do some more testing with it soon: https://github.com/datacoves/dbt-coves/issues/340


target blank in link

Hello,
How to add the target on the link?

To achieve this - create instance of HtmlHighlighter and provide target in second argument. See this code sample for an example:
<?php
require __DIR__ . '/vendor/autoload.php';

use VStelmakh\UrlHighlight\Highlighter\HtmlHighlighter;
use VStelmakh\UrlHighlight\UrlHighlight;

$highlighter = new HtmlHighlighter('http', ['target' => '_blank']);
$urlHighlight = new UrlHighlight(null, $highlighter);

$urlHighlight->highlightUrls('Hello, http://example.com.');
// return: Hello, http://example.com.

⚠ This is a new feature released today.  You need to update to v2.1

thanks man

Happy to help 😉


[AppService] az functionapp: Use the sku from the function app to validate if on a flex plan

Related command
az functionapp deployment source config-zip
Description
Resolves #28741 by not making calls to the Microsoft.Web/serverfarms API to determine if a function app is on a flex plan
History Notes

[AppService] az functionapp deployment source config-zip: Users with no Microsoft.Web/serverFarm read privileges should still be able to deploy function apps

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

AppService

Is there any other change in custom.py file apart from moving of the code into the try/catch block? Just want to make sure that I am not missing anything?

Is there any other change in custom.py file apart from moving of the code into the try/catch block? Just want to make sure that I am not missing anything? Please point to the specific change in the file .

Yes. Please see commit https://github.com/Azure/azure-cli/pull/28845/commits/aa99a118f62bffaf969f8b2a969ecbaebf96b778 That resolves https://github.com/Azure/azure-cli/issues/28741

Closing this PR. Created a new one without merge conflicts.
https://github.com/Azure/azure-cli/pull/28899


fix formatting issues

While reviewing the issue #3623, I've noticed that the topic (https://docs.microsoft.com/en-us/dotnet/framework/wpf/advanced/how-to-localize-an-application) has some other issues:

A broken table:

Broken snippet references

While we wait for the team to confirm the new location of the samples, I thought I'd fix these other issues.
Internal Review URL

Thanks for checking @JRAlexander and adding the preview URL. Let's see if this change fixes the issue. It did on the Gauntlet preview at least.

@JRAlexander it seems that my last commit fixed the issue. Can you give me your seal of approval? 😄

Looks wonderful @mairaw!!!

Looks wonderful @mairaw!!!


Change popup tool tip from "Disable" to "Pause"

There are currently two ways to "disable." Via our extension as shown below and in the Firefox settings via about:addons. The former just pauses. So, let's rename accordingly to avoid confusion.

Not sure where else in the codebase this occurs. Let's check and change everywhere. Also in comments, variable names, etc. wherever there is disabling language used, it should be "pause" and disabling refers to the Firefox browser functionality.

I am closing this issue as there is actually some interaction between the popup and settings page when a user disables. And so these are not just linguistic changes but we also would need to think about a restructuring of the disabling/enabling logic, which is generally good as is.


[FEATURE] Add eye button in password section

I want to create a show hide password, eye button for both Login & Sign Up page
@iamparas0  please assign me this task.

@iamparas0 assign me with level 2


Add a macro-recordable plugin

... for applying labkit-classifiers to images....
closes #46

Hey @maarzt ,
here you go: A macro-recordable plugin with example macro and example model.
Hint: We cannot use BDVFunctions.show because BDV is not macro-recordable. Macro users need to read from ImagePlus windows and output to ImagePlus windows in order to integrate LabKit into their workflows.
🥳 With that, we can integrate LabKit into any kind of workflow! Awesome. Thanks for your great work!
Cheers,
Robert

While testing this, I noticed that the macro-recordable plugin produces inconsistent segmentations on RGB images.

When segmenting the image using the UI the intensities get scaled by a factor of 1/255.
There is no such scaling when the macro-recordable plugin is used.

I would like to remove this intensity scaling in the UI, but that also means that models trained on RGB images will break.

While testing this, I noticed that the macro-recordable plugin produces inconsistent segmentations on RGB images.

When segmenting the image using the UI the intensities get scaled by a factor of 1/255.
There is no such scaling when the macro-recordable plugin is used.

I would like to remove this intensity scaling in the UI, but that also means that models trained on RGB images will break.

Ok, I fixed the issue that I mentioned above and added the macro-recordable  Labkit command. (see b5999a47ecdfb304d3e42d63c13c86f8411825bf)
Thank you for the input!

Ok, I fixed the issue that I mentioned above and added the macro-recordable  Labkit command. (see b5999a47ecdfb304d3e42d63c13c86f8411825bf)
Thank you for the input!


started deepinframodels

wrote test and components for deepinframodel

we'll have to add ENV keys to workflows as well


Second and next images pixelated in Firefox (35.0.1)

Hi guys in the browers IE and Chrome backstretch works great, but it seems Firefox backstretch is showing the second and next images pixelated. Two months ago this wasn't the case.
The code I use loads different imagesizes for different screen widths.
Anyone have an idea what could be the issue and hopefully the solution?
var smartresize = smartresize(); // returns a preset width like 1920 for usage in image names

var location = "/path/to/";
var images = [
    location + "image1" + smartresize + ".jpg",
    location + "image2" + smartresize + ".jpg",
    location + "image3" + smartresize + ".jpg",
    location + "image4" + smartresize + ".jpg"
];

$.backstretch(images, {duration: 6000, fade: 1500});

P.s. If I inspect the site I can see however that the correct files are being pulled from the server.

I can confirm this problem exactly. Chrome and IE work perfectly, but FF shows pixelated images for the second and third (I currently don't have a fourth on the page). I was using files exactly the same dimensions.

Same here guys with Firefox 35.0.1. I think it might have started with Firefox 35 as I noticed it a few weeks ago and dropped it as a connection issue; but then it persisted and when you refresh the page you get different results. Sometimes you have major pixelation and sometimes a little.

I found this related thread: https://github.com/srobbin/jquery-backstretch/issues/399
Looks like there's nothing we can do on our end and will have to wait a little for the next Firefox update as there's a bug report issued for Firefox.
Cheers.

@marioawad Yeah I noticed that topic too. I added this anomaly at the FF bug tracker. Hopefully it helps in figuring out a fix.


Psych has some issue with some inline objects.

This was discovered while I was playing around with roodi:
This YAML fragment parses fine under both Syck and Psych:
ClassNameCheck:
  pattern: !ruby/regexp /^[A-Z][a-zA-Z0-9]*$/

However, if you turn this into a single line object
ClassNameCheck:                  { pattern: !ruby/regexp /^[A-Z][a-zA-Z0-9]*$/ }

Psych blows up on it, although Syck handles it fine.
Psych::SyntaxError: couldn't parse YAML at line 4 column 60
from /Users/andrew/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:148:in `parse'
from /Users/andrew/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:148:in `parse_stream'
from /Users/andrew/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:119:in `parse'
from /Users/andrew/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:106:in `load'
from /Users/andrew/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:205:in `load_file'
from (irb):8
from /Users/andrew/.rvm/rubies/ruby-1.9.2-p290/bin/irb:16:in `<main>'

The problem is that when you put the regular expression inside a flow map node, the [] become ambiguous.  In that context they could possibly be parsed as inline "flow arrays".
Hopefully this page will explain.


Docker

The app is Dockerized!
Docker allows for a consistent, easily reproducible that can be run on pretty much any platform. There is a bit of a learning curve, but I tried to make it as simple and easy-to-use as possible. Any feedback is appreciated.
I expect hope that this might provide a better way for us to reliably deploy and update, and maybe become our default method of building/shipping the app. This is still new and I don't know all the ins and outs, so I'm definitely looking for feedback. Even if it's not our primary method, it would be very nice if the app supported containerization.
Instructions to build and run are in the README.md

Added docker-machine instructions, should be ready to merge now.

Okay, so this looks good to me. I'm all set to merge it. The only comment I have is that we should ideally have a way to persist database changes. We don't want to have something happen where we lose data because the container goes down or because someone accidentally writes the wrong command.
For now, my recommendation is to use this only for development, but as we become more comfortable using it, we can migrate to using it on the server.


Switched IV vector to openssl and added a test to verify it works as before

Added a quick unit test to verify that everything works and updated it to only use openssl.

Great PR! Thanks. I hope this gets merged into master, otherwise I'll keep using NoMan2000's fork.

This is a great PR!
I can use this PR on my php7.1 because mcrypt has been deprecated on php7.1
@nickion could you please suggest how the messages need to look like?
Is a shame that this super awesome PR can not be accepted for a simple message style

Thanks for the pull request, sorry it took us a while to merge it


Validate Principal

Describe the bug
First of all, now I'm using 'custom consent example' to build my oauth2.0 server. I really appreciate your awesome project.
The problem has occurred when authenticated principal has been expired or the user account has been deleted. When the SecurityContextHolder is still alive, authorization end point still throw me to consent page. But I think end point should throw me back to login page if principal is not actually valid. I've cleared up the SecurityContextHolder and could solve problem.
Expected behavior
How do you think about double check the principal on OAuth2AuthorizationCodeRequestAuthenticationConverter? I could solve the problem with under code.
Well I'm not quite good at 'Spring Security' so it can be a bad idea though...
Sample
        Authentication principal = SecurityContextHolder.getContext().getAuthentication();
        if (principal == null) {
            principal = ANONYMOUS_AUTHENTICATION;
        } else {
            boolean exist = userService.fetchUserExistence(principal.getName());
            if(!exist) {
                SecurityContextHolder.getContext().setAuthentication(ANONYMOUS_AUTHENTICATION);
                principal = ANONYMOUS_AUTHENTICATION;
            }
        }

@kwanik-kor Regarding your comment:

The problem has occurred when authenticated principal has been expired or the user account has been deleted. When the SecurityContextHolder is still alive...

Session management (expired) and User management (deleted) is not a responsibility of the framework and should instead be implemented/configured in Spring Security instead. Session management can be configured using httpSecurity.sessionManagement() and user management is dependent on where your user's are stored and the underlying identity provider being used, e.g. LDAP, SAML, custom user database, etc.
The only requirement for Spring Authorization Server to continue the Authorization flow is to ensure the current Authentication.isAuthenticated and not anonymous. The underlying authentication mechanism being used is responsible for clearing the session if the user has been deleted or if the session has expired.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


fix : unexpected error when fees are at 0

Codecov Report
Patch and project coverage have no change.

Comparison is base (70596ef) 41.63% compared to head (de8b168) 41.63%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #480   +/-   ##
=======================================
  Coverage   41.63%   41.63%
=======================================
  Files          15       15
  Lines        1064     1064
=======================================
  Hits          443      443
  Misses        575      575
  Partials       46       46

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Adding logprobs in Chat Completions response

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

Project coverage is 90.13%. Comparing base (64cabcb) to head (d8ba9db).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main     #107      +/-   ##
============================================
+ Coverage     90.00%   90.13%   +0.13%
- Complexity      711      715       +4
============================================
  Files           124      125       +1
  Lines          1131     1146      +15
  Branches         19       19
============================================
+ Hits           1018     1033      +15
  Misses           84       84
  Partials         29       29

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


getrow / getcol of dok_matrix do not return 'real sparse' dok matrices

getrow or getcol of dok_matrix return as expected a row or a vector matrix of dok_matrix type. However, the zero coefficients are created in the dictionary . I would expect to get a row or column with dictionaries "just extracted" from the original dok_matrix.
Reproducing code example:
from scipy.sparse import dok_matrix

sparse_matrix = dok_matrix((6, 5))
sparse_matrix[1,0] = sparse_matrix[1, 3] = 1.
row = sparse_matrix.getrow(1)
print row

Current output:
  (0, 1)	0.0
  (0, 3)	1.0
  (0, 0)	1.0
  (0, 2)	0.0
  (0, 4)	0.0

Expected output:
  (0, 3)	1.0
  (0, 0)	1.0

Scipy/Numpy/Python version information:
(scypy, numpy, sys) = ('1.0.0', '1.14.0', sys.version_info(major=2, minor=7, micro=14, releaselevel='final', serial=0))

Comments:
I don't know if current returned dok_matrix are done on purpose or not. If yes, I imagine that the main intent is performance. However, this is inducing some complexity in my scripts. If not, I'll be happy to volunteer to fix the issue.

You can write sparse_matrix[1,:] instead of getrow(1).

In principle, getrow and getcel could be replaced with
return self[j,:] and return self[:,j], or equivalent refactoring
for the slice case.

I'm a bit surprised this wasn't already addressed in my indexing overhaul PR (gh-7827). I'll fix it there.

Code passes at head, seems PR #7827 fixed this.