feature: dynamic topic filtering routing with wildcards

I'm thinking about a scenario I'm going to need in the near future.
newsfeed scenario is:
I have multiple clients interested on some general news topic such as
1 client subscribe to following
newsagency.politics.asia.thailand
another client subscribe
newsagency.politics.asia.cambodia
where another would like, let's say subscribe to all
newsagency.politics.asia.*
or
newsagency.*.asia.singapore
NB: separator is ".", but could be "/" or else except ":" used by prefix curie
This a classic in EAI patterns
http://www.eaipatterns.com/MessageRouter.html
http://www.eaipatterns.com/Filter.html
I exclude content routing, it is out of scope in this library, better use Spring Integration.
What I foresee is more destination topic routing.
First served would be the full topic subscriber, where after wildcard subscribers would be processed
I guess @WampPublishListener, @WampSubscribeListener, @WampCallListener should include a regex, or wildcard switch to activate destination pattern.
separator could be a general configuration or a case by case setup.
To avoid a performance drop for current simple destination,
PubSubHandler should have an additional method like sendToMatchingTopic which will search for matching destinations/topics
example:
eventMessenger.sendToMatchingTopic("newsagency.politics.asia.*", list);
I wonder if SpEL expression evaluation could be of any use.
SpEL can use regex, or build a graph of destinations will be better (http://introcs.cs.princeton.edu/java/45graph/, http://jgrapht.org/)
Would you see this feature a valuable addition to implement?
reference: https://en.wikipedia.org/wiki/Publish–subscribe_pattern#Message_filtering

Wildcards are now supported in the 1.1.0 release. Works similar to the built in stomp support in the Spring Framework. It uses the AntPathMatcher class to match destinations with wildcards.


Calling some functions without admin-rights leads to unpredictable behaviour

Describe the bug
Some actions of choco.exe needs admin-privileges to function normally.
If you do not have them you get a warning and can choose to continue anyway. The dialog times out after 20 seconds and defaults to 'N' (Not proceed).
The output of some ChocoMan-functions are unpredicatable, because the output cannot be parsed, so in the end you don't know if the commands were executed properly or not.
To Reproduce
Steps to reproduce the behavior:

Start powershell without administrator privileges
Execute Install-ChocoPackage -Name openscad
Wait at least 20 seconds
See output from function, like:

> Install-ChocoPackage "openscad"
Name     Status Version
----     ------ -------
openscad

Expected behavior
The affected ChocoMan-Functions should give a warning that they are not started with the needed priviliges.
Additional context
The output from the commands are different. It depends on what function is used and if the package is already installed or not.
One could use choco.exe without admin-privileges but this does not work for every package.
choco.exe checks if the Tag admin is present for the package and gives the above warning.
If the Tag is not present it just continues with the package installation/uninstallation/upgrade, but it depends on the package if this succeeds (maybe installing software in the users home directory)
This is also applicable for changing sources.
The above warning can not be seen when calling choco.exe with Invoke-ChocoCmd because it redirects all output to a variable.
You can only see it when calling choco.exe directly.
The warning is:
Chocolatey detected you are not running from an elevated command shell
 (cmd/powershell).

 You may experience errors - many functions/packages
 require admin rights. Only advanced users should run choco w/out an
 elevated shell. When you open the command shell, you should ensure
 that you do so with "Run as Administrator" selected. If you are
 attempting to use Chocolatey in a non-administrator setting, you
 must select a different location other than the default install
 location. See
 https://docs.chocolatey.org/en-us/choco/setup#non-administrative-install
 for details.

For the question below, you have 20 seconds to make a selection.

 Do you want to continue?([Y]es/[N]o):

@we-mi You mentioned an admin Tag for packages. I do not see that when listing all of them.
Do you know how I can get the package Tag?

Hey @regg00,
Sorry, my bad. You're completly right.
I've read somewhere that the admin-tag tells choco that administrative permissions are required, but this seems to be not true.
The admin-tag should be used for packages when an administrative helper-function is being used (see here).
The decision to show the warning about missing privileges is most likely tested by some other rules, which I sadly don't know.
My suggestion for this issue is to implement/show a preceding warning by your own functions and then exit the function without actually calling choco.exe unless the -Force (or another) parameter is specified in case the user knows what he's doing and tries to install/uninstall anything for which he doesn't need admin privileges for.

Nice to know I didn't miss something in the chocolatey doc.
Your suggestion make total sense.
I played a bit with #Requires -RunAsAdministrator for only some functions, but it makes the module a bit cumbersome to install for some reason, specifically if not all the commands require you to be an admin.
Having a function that checks if a user is an admin before actually running the choco command makes total sense. Something like: ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator") should return True or False depending if the user is an admin or not.

I simply added a check at every Admin function.
I couldn't find a parameter that allowed me to bypass the choco.exe Yes/No prompt
PS C:\Users\regg0\GitHub\ChocoMan> choco apikey -s=https://google.com -k=123
Chocolatey v2.1.0 Business
API key provided. Setting command to add.
Chocolatey detected you are not running from an elevated command shell
 (cmd/powershell).

 You may experience errors - many functions/packages
 require admin rights. Only advanced users should run choco w/out an
 elevated shell. When you open the command shell, you should ensure
 that you do so with "Run as Administrator" selected. If you are
 attempting to use Chocolatey in a non-administrator setting, you
 must select a different location other than the default install
 location. See
 https://docs.chocolatey.org/en-us/choco/setup#non-administrative-install
 for details.

 Do you want to continue?([Y]es/[N]o): n

PS C:\Users\regg0\GitHub\ChocoMan> choco apikey -s=https://google.com -k=123 -f -y
Chocolatey v2.1.0 Business
API key provided. Setting command to add.
Chocolatey detected you are not running from an elevated command shell
 (cmd/powershell).

 You may experience errors - many functions/packages
 require admin rights. Only advanced users should run choco w/out an
 elevated shell. When you open the command shell, you should ensure
 that you do so with "Run as Administrator" selected. If you are
 attempting to use Chocolatey in a non-administrator setting, you
 must select a different location other than the default install
 location. See
 https://docs.chocolatey.org/en-us/choco/setup#non-administrative-install
 for details.

For the question below, you have 20 seconds to make a selection.

 Do you want to continue?([Y]es/[N]o): n

PS C:\Users\regg0\GitHub\ChocoMan> choco apikey -s=https://google.com -k=123 -f -y -r --limit-output
API key provided. Setting command to add.
Chocolatey detected you are not running from an elevated command shell
 (cmd/powershell).

 You may experience errors - many functions/packages
 require admin rights. Only advanced users should run choco w/out an
 elevated shell. When you open the command shell, you should ensure
 that you do so with "Run as Administrator" selected. If you are
 attempting to use Chocolatey in a non-administrator setting, you
 must select a different location other than the default install
 location. See
 https://docs.chocolatey.org/en-us/choco/setup#non-administrative-install
 for details.

For the question below, you have 20 seconds to make a selection.

 Do you want to continue?([Y]es/[N]o): n


Provide a method to uninstall

It would be nice to have a way to uninstall mobymac. That could be some some section in the README offering guidance for a manual uninstall or an automated script.

I added an uninstaller script: https://github.com/dziemba/mobymac/commit/82e75efc353931e9bac9b9e6044e09d14499a451 🎉


Orientdb update to 3.1.0

update driver and image to 3.1.0
remove test for gremlin script that is not enable since 3.0.28: https://github.com/orientechnologies/orientdb/wiki/OrientDB-3.0-Release-Notes#3028---5-february-2020

With #2839 we're intending to deprecate the default constructor for all modules and start encouraging all users to specify a version explicitly. This is primarily to avoid the risk of us breaking users' builds by changing the docker image unexpectedly.
As such, I'll close this PR, as I'd expect that we will leave default image tags where they are until they eventually get removed altogether.

Ok, sounds reasonable to me. I wonder if I should at least open a PR that removes the gremlin test, because of this:
remove test for gremlin script that is not enable since 3.0.28: https://github.com/orientechnologies/orientdb/wiki/OrientDB-3.0-Release-Notes#3028---5-february-2020
WDYT?


fix: empty src attr in StrictMode

Update the Player handlePlayerMount method so that the progress load is always called.
Update the FilePlayer load method so that the src attribute always filled with value
This should fix #1530 #1520 #1508

@cookpete This is blocking us as well, and we can confirm that @Gerpea's fix works. A merge and publish would be amazing. Thanks!

same, experiencing the same issue here, fix would be awesome!

@cookpete Hi, we would appreciate it if you could review the fix

Yup! This is the "Fix" 🚀

@cookpete ?

Has anyone seen @cookpete on a ticket or git in the last few months? Maybe he has abandoned the repo (or is no longer able to manage it) and it's time to fork?

I’m here. I’m alive.
It’s been over seven years since I started this project. I never thought it would become this popular. Life changes a lot in seven years. I have much less free time now. I would love to spend more time on this. I will try to in the future. Bear with me. Apologies to keep everyone waiting for so long.

@cookpete No worries, thanks a lot for your continued support!

Thanks to @Gerpea for the original fix but it’s actually as simple as setting the src in the componentDidMount of FilePlayer.js
The original fix would have called load twice for every player, including calling getSDK twice, which loads all the third party scripts. It seemed quite bug prone so I simplified it a bit.
Regardless, thanks so much for the PR and pointing me in the right direction to fix this.

🎉 Thank you @cookpete

@cookpete Thank you for the fix. In which version will this fix come?

Published in v2.11.1


Enable watchos target for the Counter sample after Kotlin 1.5.31 update

The Counter sample has watchos targets temporary disabled, due to KT-48613.

Is there anything stopping this work of updating the project to kotlin 1.6.0 to fix the sample? Jetpack compose compiler?

Moved to https://github.com/arkivanov/Decompose/issues/3


[BUG] Expecting error showing whole script

Try to input a stat with the wrong timespan in this case, is a "MONTH" stat. The expected result is that the console will show the error stack. Not only that, it consoling the whole code too.

Speculate the bug maybe it's because of the code that has been minimized.

:tada: This issue has been resolved in version 1.1.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


procedure steps too deeply nested

Often, when a DocBook procedure is mapped to AsciiDoc, the steps in the numbered list are too deeply nested. For example, in the Fabric_Guide/get_start.xml file, there is an example of a procedure that gets mapped to a triply-nested numbered list (for no good reason!).

Effectively duplicates issue #16. The commit for #16 also fixes this issue.

Closing as duplicate.


Mangling: support of new mangling in the demangler.

It can now demangle the old “_T” and new “_S” symbol names.
(This change should have been part of my previous mangling PR)

@swift-ci Please smoke test and merge


[Snyk] Fix for 2 vulnerabilities

Snyk has created this PR to fix 2 vulnerabilities in the maven dependencies of this project.
Snyk changed the following file(s):

pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue
Score
Upgrade

Denial of Service (DoS) SNYK-JAVA-ORGSPRINGFRAMEWORK-7687447
  631
org.springframework:spring-web:  5.3.27 -> 5.3.38  No Known Exploit

Allocation of Resources Without Limits or Throttling SNYK-JAVA-ORGSPRINGFRAMEWORK-7687446
  551
org.springframework:spring-context:  5.3.27 -> 5.3.39  No Known Exploit

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)
🦉 Allocation of Resources Without Limits or Throttling

Checkmarx One – Scan Summary & Details – 3228965c-0988-4683-a8b1-7e9c78d2821f
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2024-22259
Maven-org.springframework:spring-web-4.3.30.RELEASE
Vulnerable Package

CVE-2024-22262
Maven-org.springframework:spring-web-4.3.30.RELEASE
Vulnerable Package

CVE-2021-28169
Maven-org.eclipse.jetty:jetty-http-9.4.27.v20200227
Vulnerable Package

Fixed Issues

Severity
Issue
Source File / Package

CVE-2023-24998
Maven-commons-fileupload:commons-fileupload-1.5

CVE-2007-2379
Npm-jquery-2.1.4

CVE-2007-2379
Npm-jquery-1.12.4

CVE-2007-2379
Maven-org.webjars:jquery-3.5.1

CVE-2014-6071
Maven-org.webjars:jquery-3.5.1

CVE-2014-6071
Npm-jquery-1.12.4

CVE-2014-6071
Npm-jquery-2.1.4


shooter

basic code - subsystem and command - for shooter. also did major changes on code's structure, adding some new packages of commands, subsystems and robotcontainer

new code is coming

new code is coming


Methods are listed in wrong category in Documentation

http://blockstack.github.io/blockstack.js/index.html
getGracePeriod, getNamePrice, etc. (the methods added as part of the last release) are all under "Storage". They don't belong there. We probably need categories for "Names" and "Accounts" (this one could also be part of "Profile").

Probably same as #555

Closing as this should be fixed in new version of docs


Hash Mismatch Crowsec Module

It looks like the crowdsec hash is mismatched:
  error: 1 dependencies of derivation '/nix/store/gix25jk899dcays39f8gnlqxsl4j8kn2-crowdsec-1.6.0.drv' failed to build

┏━ 1 Errors:
┃ error: hash mismatch in fixed-output derivation '/nix/store/ggpc2ak464sninqjqaf1xhc3i7jakv33-2868.patc…
┃          specified: sha256-RSfLhNZ3JVvHoW/BNca9Hs4lpjcDtE1vsBDjJeaHqvc=
┃             got:    sha256-KLoGgHGwkS3+e0vSrivL0HQVRCCZ+saH9NDWlH7/Zmw=

I found this is due to the fact I am using nixpkgs-unstable. I will do a PR on nixpkgs to push croudsec to v1.6.1. Then, I'll update my fork to work with nixpkgs-unstable. I will close this Issue and the PR connected.

Hi there, sorry for the late response.
There already is a PR to update crowdsec on nixpkgs.
It's not uncommon though for nixpkgs PRs to take a while until someone with commit access will merge it.
I will probably internalize the crowdsec package into this flake and add it to the overlay on the weekend to have a better shot at timely maintenance.


[1.12.1-4.0.1] Custom datapack settings not getting applied

Hey there,
I made a custom datapack with some different options, but seemingly some are not getting applied correctly. I can select the options when I create a new bingo game, but some parts from the game section aren't working (i.e. invulnerable, lockout, leaderboard and time from my testing). The teleport radius works correctly.
I'm using the mod version Bongo-1.20.1-4.0.1 with LibX-1.20.1-5.0.5.
These are the setting I tired to use:
{
  "game": {
    "win_condition": "bongo.default",
    "invulnerable": false,
    "pvp": false,
    "friendly_fire": false,
    "time": "3600",
    "consume_items": false,
    "lock_task_on_death": true,
    "teleports_per_team": 0,
    "leaderboard": true,
    "lockout": true
  },
  "level": {
    "teleporter": "bongo.default",
    "teleport_radius": 1000
  },
  "equipment": {
    "inventory": [],
    "backpack": [],
    "emergency": [],
    "offhand": {
      "item": "minecraft:air",
      "count": 0
    },
    "head": {
      "item": "minecraft:air",
      "count": 0
    },
    "chest": {
      "item": "minecraft:air",
      "count": 0
    },
    "legs": {
      "item": "minecraft:air",
      "count": 0
    },
    "feet": {
      "item": "minecraft:air",
      "count": 0
    }
  }
}

Here is an excerpt from the startup log:
[...]
[23:03:52] [main/INFO] [cp.mo.mo.LaunchServiceHandler/MODLAUNCHER]: Launching target 'forgeserver' with arguments []
[23:03:59] [modloading-worker-0/INFO] [ne.mi.co.ForgeMod/FORGEMOD]: Forge mod loading, version 47.1.0, for MC 1.20.1 with MCP 20230612.114412
[23:03:59] [modloading-worker-0/INFO] [ne.mi.co.MinecraftForge/FORGE]: MinecraftForge v47.1.0 Initialized
[23:03:59] [modloading-worker-0/INFO] [Dynmap/]: [Dynmap] Mod Support API available
[23:03:59] [Forge Version Check/INFO] [ne.mi.fm.VersionChecker/]: [bongo] Starting version check at https://assets.melanx.de/updates/bongo.json
[23:04:00] [Forge Version Check/INFO] [ne.mi.fm.VersionChecker/]: [bongo] Found status: BETA Current: 1.20.1-4.0.1 Target: null
[23:04:00] [Forge Version Check/INFO] [ne.mi.fm.VersionChecker/]: [libx] Starting version check at https://assets.melanx.de/updates/libx.json
[23:04:00] [Forge Version Check/INFO] [ne.mi.fm.VersionChecker/]: [libx] Found status: BETA Current: 1.20.1-5.0.5 Target: 1.20.1-5.0.5
[23:04:00] [Forge Version Check/INFO] [ne.mi.fm.VersionChecker/]: [forge] Starting version check at https://files.minecraftforge.net/net/minecraftforge/forge/promotions_slim.json
[23:04:00] [Forge Version Check/INFO] [ne.mi.fm.VersionChecker/]: [forge] Found status: OUTDATED Current: 47.1.0 Target: 47.2.0
[...]
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:plains
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:desert
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:windswept_hills
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:taiga
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:swamp
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:river
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:frozen_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:beach
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:windswept_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:jungle
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:deep_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:stony_shore
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:birch_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:dark_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:snowy_taiga
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:savanna
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:savanna_plateau
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:cold_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:windswept_gravelly_hills
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:nether_wastes
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:the_end
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:frozen_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:jagged_peaks
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:mushroom_fields
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:beach
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:windswept_savanna
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:windswept_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:jungle
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:deep_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:stony_shore
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:snowy_beach
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:dark_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:snowy_taiga
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:savanna
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:savanna_plateau
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:badlands
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:wooded_badlands
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:warm_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:lukewarm_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:cold_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:deep_lukewarm_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:deep_cold_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:deep_frozen_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:sunflower_plains
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:windswept_gravelly_hills
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:flower_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:ice_spikes
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:bamboo_jungle
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:soul_sand_valley
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:crimson_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:warped_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:basalt_deltas
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:plains
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:desert
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:windswept_hills
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:taiga
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:swamp
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:river
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:nether_wastes
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:beach
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:windswept_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:jungle
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:birch_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:dark_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:snowy_taiga
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:savanna
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:savanna_plateau
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:badlands
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:cold_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:deep_lukewarm_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:deep_cold_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:deep_frozen_ocean
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:soul_sand_valley
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:crimson_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:warped_forest
[23:04:16] [Server thread/ERROR] [bongo/]: Failed to validate task of type bongo.biome: Biome not registered: minecraft:basalt_deltas

I think that's everything related to bongo, hope I didn't miss something.

Your time value should not use quotation marks around the number. I'll publish an update that produces an error message instead of discarding the whole game block silently but you can fix that by removing the quotation marks.

Ahhh... Yeah, makes sense. Tested that and it works as intended. Thanks!


[mpir] build failure

Operating system
Windows
Compiler
MSCV
Steps to reproduce the behavior
./vcpgk install mpir:x86-windows

Failure logs
console output
Installing<EMAIL_ADDRESS>Building<EMAIL_ADDRESS>-- Downloading https://github.com/wbhart/mpir/archive/cdd444aedfcbb190f00328526ef278428702d56e.tar.gz -> wbhart-mpir-cdd444aedfcbb190f00328526ef278428702d56e.tar.gz...
-- Extracting source C:/Tools/vcpkg/downloads/wbhart-mpir-cdd444aedfcbb190f00328526ef278428702d56e.tar.gz
-- Applying patch enable-runtimelibrary-toggle.patch
-- Applying patch fix-static-include-files.patch
-- Using source at C:/Tools/vcpkg/buildtrees/mpir/src/428702d56e-def7e839da.clean
-- Getting CMake variables for x86-windows
-- Building build.vc14/dll_mpir_gc/dll_mpir_gc.vcxproj for Release
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: msbuild C:/Tools/vcpkg/buildtrees/mpir/x86-windows-rel/build.vc14/dll_mpir_gc/dll_mpir_gc.vcxproj /p:Configuration=Release /p:ForceImportAfterCppProps=C:/Tools/vcpkg/buildtrees/mpir/x86-windows/vcpkg_msbuild.props /p:ForceImportAfterCppTargets=C:/Tools/vcpkg/buildtrees/mpir/x86-windows/vcpkg_msbuild.targets /t:Rebuild /p:UseMultiToolTask=true /p:MultiProcMaxCount=3 /p:EnforceProcessCountAcrossBuilds=true /m:3 -maxCpuCount:3 /p:Platform=Win32 /p:PlatformTarget=x86 /p:PlatformToolset=v140 /p:WindowsTargetPlatformVersion=10.0.18362.0 /p:VcpkgApplocalDeps=false /p:VcpkgManifestInstall=false /p:VcpkgManifestEnabled=false /p:VcpkgEnabled=false /p:VcpkgTriplet=x86-windows /p:VcpkgInstalledDir=C:/Tools/vcpkg/installed
    Working Directory: C:/Tools/vcpkg/buildtrees/mpir/x86-windows-rel
    Error code: 1
    See logs for more information:
      C:\Tools\vcpkg\buildtrees\mpir\build-x86-windows-rel-out.log
Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-msbuild/vcpkg_msbuild_install.cmake:108 (vcpkg_execute_required_process)
  ports/mpir/portfile.cmake:52 (vcpkg_msbuild_install)
  scripts/ports.cmake:170 (include)
error: building mpir:x86-windows failed with: BUILD_FAILED
Elapsed time to handle mpir:x86-windows: 7.7 s

C:\Tools\vcpkg\buildtrees\mpir\build-x86-windows-rel-out.log
Microsoft (R) Build Engine version 14.0.25420.1
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 1/21/2024 1:39:05 PM.
     1>Project "C:\Tools\vcpkg\buildtrees\mpir\x86-windows-rel\build.vc14\dll_mpir_gc\dll_mpir_gc.vcxproj" on node 1 (Rebuild target(s)).
     1>C:\Tools\vcpkg\buildtrees\mpir\x86-windows\vcpkg_msbuild.targets(29,16): error MSB4066: The attribute "Update" in element <ClCompile> is unrecognized. [C:\Tools\vcpkg\buildtrees\mpir\x86-windows-rel\build.vc14\dll_mpir_gc\dll_mpir_gc.vcxproj]
     1>Done Building Project "C:\Tools\vcpkg\buildtrees\mpir\x86-windows-rel\build.vc14\dll_mpir_gc\dll_mpir_gc.vcxproj" (Rebuild target(s)) -- FAILED.

Build FAILED.

       "C:\Tools\vcpkg\buildtrees\mpir\x86-windows-rel\build.vc14\dll_mpir_gc\dll_mpir_gc.vcxproj" (Rebuild target) (1) ->
         C:\Tools\vcpkg\buildtrees\mpir\x86-windows\vcpkg_msbuild.targets(29,16): error MSB4066: The attribute "Update" in element <ClCompile> is unrecognized. [C:\Tools\vcpkg\buildtrees\mpir\x86-windows-rel\build.vc14\dll_mpir_gc\dll_mpir_gc.vcxproj]

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:00.46

### Additional context

This did work 6 months ago, so if nothing changed on the appveyor side (which is used to do this build as a dependency) then some of the changes here must have created this issue.
Also happens on x64. Works fine with newer MSVC/build environment.

Does this also apply to you: https://github.com/SpecFlowOSS/SpecFlow/issues/1250#issuecomment-415782071 ?

As noted the newer MSBuild (from VS2017) does work, but the goal is to run that with a VS2015 stack (which worked before).

@Neumann-A Can you please verify if this failure is related to your changes (and possibly how to work around that without reversing the commit)?

You should really be using VS 2022 with the v140 toolset instead of expecting that a 2023 change will work with VS2015.
There is probably a workaround by using an overlay for vcpkg-msbuild removing the problematic field but I am not going to investigate that possibility.

vcpkg says that VC2015 is expected to work.
It is not that I'd like to keep that forever, but I do know some people/companies still use VC2015 and have VC2015 generated DLLs that need to work toghether, so "just using a newer toolset" is likely not what will work there.
Is it possible to request to use an older definition? Maybe by updating the ports definitions, then manually downgrading the mpir definition to the last version that worked before installing?

V140 is the old toolset which can be installed via the installer. Just use a newer MSBuild/Visual Studio
If you use manifest mode you can pin whatever version you like.

Found the issue - it is actually a bug in vcpkg_msbuild_install, it works when moving back to the deprecated vcpkg_install_msbuild instead (only copy/replace).
@Neumann-A can you please do that?
.. wait, that builds but not install correctly:

C:\Tools\vcpkg\ports\mpir\portfile.cmake: warning: The folder ${CURRENT_PACKAGES_DIR}/include is empty or not present. This usually means that headers are not correctly installed. If this is a CMake helper port, add set(VCPKG_POLICY_CMAKE_HELPER_PORT enabled). If this is not a CMake helper port but this is otherwise intentional, add set(VCPKG_POLICY_EMPTY_INCLUDE_FOLDER enabled) to suppress this message.
C:\Tools\vcpkg\ports\mpir\portfile.cmake: warning: There should be no installed empty directories. Empty directories are not representable to several binary cache providers, git repositories, and are not considered semantic build outputs. You should either create a regular file inside each empty directory, or delete them with the following CMake. To suppress this message, add set(VCPKG_POLICY_ALLOW_EMPTY_FOLDERS enabled)
C:\Tools\vcpkg\packages\mpir_x86-windows: note: the directories are relative to ${CURRENT_PACKAGES_DIR} here
note: file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/include")
C:\Tools\vcpkg\ports\mpir\portfile.cmake: warning: Found 2 post-build check problem(s). These are usually caused by bugs in portfile.cmake or the upstream build system. Please correct these before submitting this port to the curated registry.
Stored binaries in 1 destinations in 860 ms.

Any hint what I need to add/adjust to get that fixed?


Close temp file on token persist

Fixes the
"The process cannot access the file because it is being used by another process."

issue on windows.

@colemickens

now it's like:

LGTM. Thanks.


Update privacy notice to include IP address

We are now sending the client IP address to Application Insights so we
state that in the notice.
I've tried to copy the GOV.UK use of IP address in their privacy notice,
I am no expert in this so we may want other eyes on the content?

 Update privacy notice

Thanks for all the comments. We are going to talk to the right people at DfE and get an answer. I'll close this now as it's such a small change, we can open or redo once we have an answer rahter than have this PR going stale.


Show Helm releases in cluster tree view

This adds a new top-level 'Helm Releases' node to clusters in the tree view.  At the moment there's not much you can do with this - viewing the node displays the helm get output as a text file, and that's it.
This is currently work in progress - it needs to be tested with large numbers of releases, and I would like feedback on whether to present the returned file as YAML (which it isn't, not really, but it colourises okay if you pretend it is) or as plain text.  Other feedback / suggestions welcome (but may be deferred to subsequent enhancements).
Fixes #245.

Huh, okay, so helm list actually returns releases in all namespaces (whereas helm install does install into the current kubectl namespace), so I made at least one wrong assumption there.  I kind of feel like our display should filter to the active namespace, otherwise it's going to be a bit misleading - but perhaps this would be confusing to Helm users...

After discussion with a Helm maintainer, the recommendation is to filter to the active namespace.

Seems to work okay with 500+ releases in the cluster.  I'm going to call that acceptable for our intended use case for now, and address paging if a customer hits a limit.

As ready to go as it's gonna get without some feedback.  @bnookala @technosophos @bacongobbler do you have time to take a look please?

Done, please re-review - thanks!


#18 fix list in ticket

add .netcore 2.1 support
bump .netstandard from 1.3 to 2.0
deadlocks
ReadFromFileAsync
write unit tests
bump version number

thanks @curtiswellborn: I already uploaded the updated nuget package!


Anyone cal help to migrate Preview-transition proyecto to Swift 3

Need help to migrate this proyect to Swift 3
https://github.com/Ramotion/preview-transition
Thx

done


Releases

@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/59454
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" b7e34fc9927323b1c475d44f3d1701b4a0af14e7
git push origin v0.1.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/59961
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" d2263926a82ece92719173ff22d54884e7c5b403
git push origin v0.1.1

@Wikunia maybe a new release?

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/65228
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" 2237971ab0c34c2e8e7d9f375cb39c5349ef7f9c
git push origin v0.1.2

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/81155
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.3 -m "<description of version>" 1f2640f1952df6d484d90e63e07ac027ed3d5de3
git push origin v0.1.3


sql: add SHOW USERS stmt

PR: https://github.com/cockroachdb/cockroach/pull/10088

@sploiselle, looks like we forgot this one as a part of our initial user management docs.


inline images and canvas h / w mismatch

Apologies if I'm misunderstanding what's going on here, but I've been having some strange sizing issues with inlineImages().
I have a D3 chart with a handful of different svg icons inline. The inlineImages() function seems to be interpreting the canvas height and width for each icon to be 150 and 300, respectively. The strange thing is, each inline svg image has been explicitly set to 48x48. Once the svg images have been converted to png format, they appear quite a bit smaller as 48x48 islands in the center of a 300x150 png image. See screenshots:
Expected:

Result:

I've found that by setting img.height and img.width to 150 inside the inlineImages() function, then adding an x-offset parameter to ctx.drawImage(), I'm able to work around this, but am not 100% sure why the issue has arisen in the first place. However, I freely admit that I don't know much about canvas or the toDataURL() function.

Could you provide some sample code that reproduces this problem? I'll add it to the test page and investigate where in the pipeline the mis-sizing is being introduced.


Fast Refresh

I'm running into cases where fast-refresh breaks when using zustand, not exactly sure why tho. If I remove zustand fast-refresh start working again

I'm having a similar issue but in reverse - fast refresh leads to the selectors not firing when I update a store.

for me fast refresh, kinda resets some of my state, ( need to investigate it more. ).

HMR not working in codesandbox. I assume they are using FastRefresh.

they do, but only if index.js is a clean ReactDOM.render(<App/>,...) and code is exposed in App.js.

Hmm, is this clean?
https://codesandbox.io/s/bold-bassi-v2fhq?file=/src/index.tsx

it doesn't trigger a re-render after RN fast refresh is triggered.

@dai-shi yes fastrefresh is enabled at least

the reset, i think that's just how fast refresh works. if you put the store into its own module it works as expected: https://codesandbox.io/s/dry-river-30mml?file=/src/App.tsx i doesnt seem like that's in our hands even, the store is a singleton that's outside of react. it wipes out the module and resets all singletons.

@dai-shi just noticed that v3 fixes it: https://codesandbox.io/s/dry-river-30mml?file=/src/App.js

@drcmda is there any timeline for v3?

today? tomorrow? something like that :-)


Migrate to Fastlane Match - import not working as expected

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I was trying to import our existing certificate and provisioning profiles to Fastlane match today, but it didn't quite work as expected. There's not much documentation on the import command, so it's a bit difficult to know what to expect: https://docs.fastlane.tools/actions/match/#import
I have an enterprise certificate and 26 provisioning profiles that use it. I thought I would be able to import all provisioning profiles in one go, but it only accepts the path to one specific provisioning profile. Providing the path to the directory containing the provisioning profiles or providing a star pattern, didn't work. I checked the source code and that is clearly not implemented. It surprises me, as having multiple provisioning profiles is very common.
Now, am I supposed to run the import command 26 times, once for each provisioning profile? All parameters are read from stdin, so that would be extremely tedious. The provisioning profile parameter is optional, but the .cer and .p12 are not, even though they would already have been imported and don't need to be re-imported. I feel like there is probably another way and that perhaps after importing the certificate and private key you could have match download all the provisioning profiles from the portal, but there is no mention of that in the documentation.
Unfortunately it's not just the provisioning profiles that are of concern. I have a .p12 file and as far as I understand, it contains both the certificate and the private key. If you import it to your keychain, you get both and you don't need a separate .cer file. It's easy enough to download the .cer file from the developer portal, but I don't understand why it is required. My .p12 file is also password protected, but at no point is Fastlane asking me for that password, so I have little hope that it will actually be able to use it. I could make a .p12 file without password protection, but it seems like Fastlane could and should support password protected .p12 files.
Command executed

fastlane match import --type enterprise

I don't think the output of the command or the Fastlane environment is relevant, as the behaviour of the command is quite clear just from reading the source code. The code arguably works as expected, but as an import feature, it's not living up to my expectations. It has fundamental shortcomings that need to be addressed. At the very least, the documentation should make those shortcomings clear. The documentation even says "provisioning profiles" in plural, even though there is no way to pass multiples of them.

I just came across this: https://docs.fastlane.tools/actions/match/#export-distribution-certificate-and-private-key-as-single-p12-file

match stores the certificate (.cer) and the private key (.p12) files separately. The following steps will repackage the separate certificate and private key into a single .p12 file.

So I guess that answers one of my questions, but there is nothing about that in the import section. I think it should explicitly state that you need the .p12 file to only contain the key and that it shouldn't be password protected (if that is the case). I also think that the import script should validate the .p12 file and not just copy it into the repository as seems to be the case currently.
https://docs.fastlane.tools/actions/match/ has an Edit on GitHub button, but it doesn't seem to be linking to the documentation: https://github.com/fastlane/fastlane/edit/master/fastlane/lib/fastlane/actions/match.rb
Shouldn't that button link to here: https://github.com/fastlane/docs/edit/master/docs/actions/match.md
I don't mind creating a PR for the documentation, but I would prefer if someone could confirm that my understanding is correct. In the meantime, I will continue trying to figure out how to properly import our certificate.


Create Dataloaders

Hi, is there any specific idea about creating a Dataloader for the case in the CAN tutorial?
Best,
Allen Wang


Add compat matrix; add JMESPath nesting

Adding Kyverno compatibility matrix (closes https://github.com/kyverno/website/issues/66) and nested JMESPath expressions (addresses https://github.com/kyverno/website/projects/1#card-52841871).

@JimBugwadia can you provide review, please?

@JimBugwadia can you provide review, please?


How to set font + color for the label.

Hey,
Is it possible to enable / disable the text label in runtime and change the text color and background?
This is stopping me to use this lib for my project.
Any help is appreciated
Thanks!
Manju

Right now there are no Java getters/setters for FloatingActionsMenu. This issue is already tracked in #49


dataProvider on test level doesn't work when we have method dataprovider.

TestNG Version 7.1.0

Note: only the latest version is supported

Expected behavior
@Test(dataProvider = "test2")
public class TesgNGUpliftDemo {
	@DataProvider(name = "test1")
    public Object[][] createDataMethodLevel() {
        return new Object[][] {
                { "Cedric", 36 },
                { "Anne", 37},
        };
    }

    @DataProvider(name = "test2")
    public Object[][] createDataClassLevel() {
        return new Object[][] {
                { "Pet", 16},
                { "Sun", 17},
        };
    }

	@Test(dataProvider = "test1")
    public void testClassAndMethodDataProvider(String name, int age) {
        JcatLoggingApi.setTestInfo("name: " + name + ", " + "age: " + age);
    }
}

dataProvider for test1 and test2 should be merged and executed.
Actual behavior
Only test1 dataProvider was useful.

Is the issue reproductible on runner?
Yes, it is.

[ ] Shell
[X] Maven
[ ] Gradle
[ ] Ant
[ ] Eclipse
[X] IntelliJ
[ ] NetBeans

Test case sample

Please, share the test case (as small as possible) which shows the issue

@kobebryant2007

dataProvider for test1 and test2 should be merged and executed.

Can you please point me to the documentation which leads you to believe that, this is how it should work ?
I don't remember TestNG ever merging data providers that were specified at the class level and the method level.
The attributes specified at the method level always override the values specified at the class level.
So unless you can point me to the official documentation which claims that this is the behaviour (which should be fixed and corrected for this discrepancy), I will have to close this bug with the resolution as Working as designed

Hi Krishnan,
Thank you for your quick response. I know this feature by your release note in google groups,the link is: https://groups.google.com/forum/#!topic/testng-users/HKujuefBhXA
You can now define a data provider at the class level @Test and also add specifics of a test method by specifying a @Test at method level and TestNG will merge both and run your test as a data driven test.
It said both will be merged.

@kobebryant2007
Ok, I think you misread that.

Support reading data provider information from Class level @Testannotation
You can now define a data provider at the class level @Test and also add specifics of a test method by specifying a @Test at method level and TestNG will merge both and run your test as a data driven test.

What I meant to say was that you could specify a data provider at the class level and add specifics with respect to other attributes of a "@Test" annotation at the method level and they would get merged. I don't think it meant that you could merge two data providers using this mechanism.

OK, then I think it's clear, Thank you again for explaining, I will close this issue.


Proposal: onDelete and onUpdate relation properties

Prisma on delete and on update behavior
A fundamental feature of Prisma is expressing relations between models. A relation can express many different concepts and can have many different meanings depending on the application domain: inclusion, association, dependence, state, etc. They are an essential tool of relational data model design.
As such, there is no single right answer to the question of what should happen when one side of a relation is changed or deleted.
This issue is a concrete proposal to enable that functionality and the result of multiple internal design discussions. Prisma Schema Language (PSL) syntax and client/migration/introspection behavior to consider will be outlined.
Please note that this proposal is only valid for SQL connectors for now. The behavior for other connectors will be considered separately in the future.
We are looking forward to any feedback on this proposal.
PSL Syntax Proposal
Without further ado, the following is an example of the syntax the internal working group settled on:
model User {
	id    String @id
	posts Post[]
}

model Post {
	id        String @id
	author_id String
	author    User   @relation(fields: [author_id], onDelete: Cascade, onUpdate: Cascade)
}

A note on terminology:

"Relation scalar fields": The fields that store the relation between two records, ie. the fields defined in fields of @relation. For 1-m and 1-1 relations, this is the fields in the fields property of @relation. In the example above, this would be author_id. M-n relations do not have relation scalar fields in the same sense as other relations, they only have their IDs (on both sides) as "referenced scalar fields" due to the underlying join table (see below).
"Referenced scalar fields": The fields that the relation scalar fields reference, ie. the field defined in references of @relation. For m-n relations, it's currently always the IDs of both models (which are stored as tuples in an implicit join table).

The semantics of onDelete and onUpdate are almost exactly how SQL expresses on update and on delete. For the example above: If the related author (User) of a Post is deleted (onDelete), delete all Post rows that are related to the deleted User (Cascade). If the id field of the related User is updated, also update author_id of all Posts that references that User.
Possible keywords for onDelete and onUpdate are:

Cascade: Deletes record if dependent record is deleted. Updates relation scalar fields if referenced scalar fields of the dependent record are updated.
Restrict: Prevents operation (both updates and deletes) from succeeding if any records are connected. This behavior will always result in a runtime error for required relations.
NoAction: Behavior is database specific. Either defers throwing an integrity check error until the end of the transaction or errors immediately. If deferred, this makes it possible to temporarily violate integrity in a transaction while making sure that subsequent operations in the transaction restore integrity.
SetNull: Sets relation scalar fields to null if the relation is deleted or updated. This will always result in a runtime error if one or more of the relation scalar fields are required.
SetDefault: Sets relation scalar fields to their default values on update or delete of relation. Will always result in a runtime error if no defaults are provided for any relation scalar fields.

Note that the availability of these keywords and the exact behavior depends on the provider. For example, SQL Server does not support Restrict, but the semantics of NoAction are identical to Restrict.
Limitation: Implicit Many-to-many
Prisma offers an implicit many-to-many relation syntax, for example:
model User {
	id    String @id
	posts Post[]
}

model Post {
	id      String @id
	authors User[]
}

Internally, this maps to a join table with two foreign keys. Providing onDelete/onUpdate behavior for m-n relations would be inconsistent with 1-1 or 1-m relations:

The definition would be inverted compared to other relation types.
Allowing onDelete/onUpdate on m-n misleads people into thinking that related records are deleted, when in fact they are only disconnected.

Elaborating on the first point, this is an example of an m-n relation written out with an explicit join table and onDelete:
model User {
	id    String @id
	posts JoinTable[]
}

model JoinTable {
	post_id String
	user_id String

	post Post @relation(fields: [post_id], references: [id], onDelete: Cascade)
	user User @relation(fields: [user_id], references: [id], onDelete: Cascade)

	@@id([post_id, user_id])
}

model Post {
	id      String @id
	authors JoinTable[]
}

To be consistent with other relations, the definition of delete or update behavior must happen on the join table as this is the place where the relations are actually defined and follow the logic of "if x happens with the related record, then something happens with this record". This leads into the second point, which is that having the syntax on implicit m-n would suggest different behavior to what it does. Let's write out a hypothetical onDelete example for implicit m-n:
model User {
	id    String @id
	posts Post[] @relation(onDelete: Cascade)
}

model Post {
	id      String @id
	authors User[] @relation(onDelete: Cascade)
}

To have consistent semantics with the other relations types, it would be expected that if a query deletes either a User or a Post record, dependent other records would be deleted. However, under the hood, because of the hidden join table, they would be disconnected, as the foreign keys are actually defined on the join table and only the join table records would be deleted. Even more, the construct has unclear implications, even if it would behave as expected - a Post may have many authors, deleting a post that triggers a user delete would in turn trigger deletes of more users, triggering more deletes of posts, ...
In conclusion, we feel that consistency of the schema is more important than expanding the Prisma-specific construct of implicit m-n relations. With this proposal, we will require users that want to customize their join table behavior to use explicit join tables. We understand that this will cause inconveniences, but we have m-n relation changes planned in the future that will greatly improve the query ergonomics of explicit join tables.
Emulation
For connectors without referential action support (e.g. MongoDB), we want to provide an emulated subset of actions for onDelete and onUpdate. The emulated versions try to be as close as possible to the semantics of those provided by the other connectors:

Cascade: Unchanged
Restrict: Unchanged
SetNull: Unchanged.
SetDefault: Unchanged.
NoAction: Signals that nothing will be done by Prisma. Will result in inconsistent data if not taken care of by the application.

We will gradually introduce these, the initial versions for MongoDB and co. may only support a few.
Defaults
This section discusses the current and desired default for onDelete/onUpdate for Prisma tools if the behavior is not specified explicitly in the Prisma schema. Note that the Prisma client emulates database behavior on the application layer, due to the fact that it can't know what the database behavior is without an annotation in the schema, so the current implementation chose to emulate sensible defaults.
Required relations:

When
Migrate
Client

onUpdate
Cascade
Cascade (assumed)

onDelete
Cascade
Restrict (emulated)

Optional relations:

When
Migrate
Client

onUpdate
Cascade
Cascade (assumed)

onDelete
SetNull
SetNull (emulated)

Note for Migrate and many-to-many relations: M-n is set to Cascade for both deletes and updates on the join tables, except for many-to-many self-relations on SQL Server, where we will use NoAction to avoid cycles.
Database Management Systems (DBMS):
All SQL DBMS Prisma supports have different defaults (if one creates schemas manually in SQL) than the ones Prisma currently uses:

onUpdate: NoAction (Restrict for MySQL)
onDelete: NoAction (Restrict for MySQL)

The Prisma schema follows the principle of optional complexity, which means that we strive to provide sensible defaults if a property is not defined in the schema. The above raises the question which defaults we want to follow when introducing onDelete and onUpdate.
We settled on the current Prisma defaults for referential actions (connectors without direct support emulate these):

When
Optional Relation
Required Relation

onUpdate
Cascade
Cascade

onDelete
SetNull
Restrict

We believe this is the best compromise to offer a smooth path forward for the following reasons:

It's more defensive about deleting data (ie. no delete cascade by default), reducing potential data loss errors.
It unifies migrate and client behavior. Users of migrate will see drift in their schema after update, which is easy to fix either via reintrospecting their database to keep the current behavior or accepting the change.
We keep the default query behavior as close as possible to the current state for developers already accustomed to how Prisma handles relations.

Concrete Feedback Questions

If you're not accustomed to how SQL handles onX behavior: Do you feel that you can easily understand the meaning of @relation(onDelete: ..., onUpdate: ...)? If not, would you prefer a naming scheme like @relation(onDeleteOther: ...) or @relation(onDeleteUser: ...)?
Do you feel that the suggested default behavior aligns with your expectations?

For required relations, my preference would be to align the default Migrate behaviour with the default at the database level (RESTRICT). One big downside is that it would be a breaking change.

Note: Amended the defaults section to now use agreed upon schema defaults.

I agree with implicit M2M tables being limited, but then prioritization needs to happen on #6135 and #2186.
We agree, but can't give anything more concrete at this point.

It is unclear if prisma will continue to emulate the database behaviour after this change.
Prisma will stop emulating any referential actions and rely on the database for all SQL connectors. Connectors that do not support referential actions at all (but really need them to be ergonomic) will behave differently, but we'll get there in time. Additionally, those will be clearly marked with behavior such as onDelete: EmulateCascade or similar.

It is a bit annoying to change the default behaviour for migrate since this means everybody will get a change out of nowhere and people might apply it without thinking of the implications. If this is still the way forward, it needs to be treated like a breaking change in the release notes.
It will be treated as a breaking change. To be clear, we can't circumvent a breaking change without being inconsistent in the schema <> engines behavior. We'll be careful how to communicate this.

We need some helpers to catch those errors on the application side and react to them, this means prioritize this #5040
This has technically nothing to do with this topic. You will get API errors on violation that have error codes and messages you can match against, not a generic error blob. Much like unique violations are exposed right now, for example. While I agree that this ticket improves ergonomics, it is not required to make it work on the application side.

Note: Amended error in defaults where onUpdate on optional relations was SetNull instead of Cascade.

Note: Added Emulation section and added defaults for emulated referential actions.

Looks good👍. Can't really think of anything that should be done differently. Besides maybe more examples in docs with more complicated associations and what exactly would happen when a model gets deleted(how it is going to cascade)

Just giving feedback: this is exactly how I feel things should be handled.

If you're not accustomed to how SQL handles onX behavior: Do you feel that you can easily understand the meaning of @relation(onDelete: ..., onUpdate: ...)? If not, would you prefer a naming scheme like @relation(onDeleteOther: ...) or @relation(onDeleteUser: ...)?

It's easy (and logical) to understand onDelete.

Do you feel that the suggested default behavior aligns with your expectations?

Yes.

@ErickPetru I agree on that with you, I think the vscode plugin could help a lot on that front by providing interactive documentation based on what the user is looking at.

Proposal implemented in https://github.com/prisma/prisma-engines/pull/1947

We settled on the current Prisma defaults for referential actions (connectors without direct support emulate these):

When
Optional Relation
Required Relation

onUpdate
Cascade
Cascade

onDelete
SetNull
Restrict

We believe this is the best compromise to offer a smooth path forward for the following reasons:

It's more defensive about deleting data (ie. no delete cascade by default), reducing potential data loss errors.

Am I reading this right as saying that, in the future, Prisma will default to ON DELETE RESTRICT for migrations, as well, if the onDelete prop isn't specified?

Am I reading this right as saying that, in the future, Prisma will default to ON DELETE RESTRICT for migrations, as well, if the onDelete prop isn't specified?

Exactly. If the relation has at least one scalar field that is NOT NULL, the default action will be conservative RESTRICT for deletions.

Thanks @pimeys that's wonderful! Really appreciate the amount of thought that's gone into Prisma and the quality of the communication and documentation

This has now been released as a preview feature flag. You can read about it in the release notes for 2.26.0: https://github.com/prisma/prisma/releases/tag/2.26.0 If you have any feedback, please use this issue: https://github.com/prisma/prisma/issues/7816


Added missing main heading

Added the missing main heading "MMF Culture and Arts Festival" to the news-post page
Styled to look like the desktop design

@stineknutsen  Could you resolve these conflicts?

Conflicts have been resolved

Remove the double text "MMF Culture and Arts Festival" before merging!

Removed the double text


'sampspec' warnings when selecting species

When using 'sampspec' with species = c('taxa1', 'taxa2', ...) function throws warnings:
In if (species == "All" | species == "") { :
the condition has length > 1 and only the first element will be used
We need to change the logic in the 'if' statement so that when species is a character vector of different taxa, this is handled without warnings.  The function seems to return the correct subset of taxa.
Mike

Fixed if statement logic to address multi-species case. No more warning message.


Regression in Fluxengine Cypress hexfile between FLUXENGINE_VERSION 14 and 15

Hi,
My problem description might be a little vague at the moment. I just want to document what I am experiencing.
I have a git checkout on my local harddrive from autumn 2020 where I tried to add support for a new format into the IBM encoder. Yesterday I was successful to make it work finally - on my Cypress thingy I had a firmware from September 2020 with FLUXENGINE_VERSION 14.
As my hack was good enough to work yesterday I wanted to prepare myself for a pull request and checked out your current git repo in a new folder. Then I discovered that my new builds now complained that the 14 on the Cypress thingy was too old. So I flashed the current hex file with version 15 to the Cypress. And then it stopped working for me:
Reading and writing IBM disks didn't work any more. (In my case I write 800 K images to DD disks with 10 sectors per track - Commodore 1581). Fluxengine goes through all 80 tracks when writing but a verify of the written disk shows that there is garbage on it.
So I stuck to the latest git checkout, I kept my hack in there, I changed in protocol.h the FLUXENGINE_VERSION back from 15 to 14 and reflashed the old hex file from September to the Cypress thingy - and it worked again with my current build of Fluxengine client.
Yes, I know, this could be more specific, but that's all at the moment I can come up with.

Just to confirm: writing a disk with FluxEngine and then reading it back fails, right? Have you tried writing a disk with a normal machine and then reading it with FluxEngine?
If so, I think I can guess what's going on...

Just to confirm: writing a disk with FluxEngine and then reading it back fails, right? Have you tried writing a disk with a normal machine and then reading it with FluxEngine?
If so, I think I can guess what's going on...

Just to confirm: writing a disk with FluxEngine and then reading it back fails, right?
Right. Writing finishes and then a "fluxengine read ibm" will complain about not a single complient track and do the maximum re-read allows.

Have you tried writing a disk with a normal machine and then reading it with FluxEngine?
Not yet. I will do that during the weekend.

Just to confirm: writing a disk with FluxEngine and then reading it back fails, right?
Right. Writing finishes and then a "fluxengine read ibm" will complain about not a single complient track and do the maximum re-read allows.

Have you tried writing a disk with a normal machine and then reading it with FluxEngine?
Not yet. I will do that during the weekend.

Yes, I can duplicate this:
  0.0: 247.21 ms in 80064 bytes
       42 records, 21 sectors; 1.02us clock (977kHz);
       Failed to read sector 17 (bad checksum);
       giving up
       logical track 0.0; 8704 bytes decoded.

I know what's happened: I fixed a firmware bug which was causing the timing of the output pulses to be just a bit too close together. Apparently I compensated for this when figuring out the IBM format timing, so now they're a little bit too far apart, which means it's running out of space on the track, and the last sector is truncated.
I'll fix it shortly.

Yes, I can duplicate this:
  0.0: 247.21 ms in 80064 bytes
       42 records, 21 sectors; 1.02us clock (977kHz);
       Failed to read sector 17 (bad checksum);
       giving up
       logical track 0.0; 8704 bytes decoded.

I know what's happened: I fixed a firmware bug which was causing the timing of the output pulses to be just a bit too close together. Apparently I compensated for this when figuring out the IBM format timing, so now they're a little bit too far apart, which means it's running out of space on the track, and the last sector is truncated.
I'll fix it shortly.

I know what's happened: I fixed a firmware bug...

Oh, good! It wasn't me! I was worried there for a bit. :smile:

I fixed a firmware bug which was causing the timing of the output pulses to be just a bit too close together.

Oh, dude. I noticed that the timing for a full track was a bit short with my I-should-really-make-a-PR Micropolis write support. I didn't care because it was small, but I should totally use the new firmware.

I know what's happened: I fixed a firmware bug...

Oh, good! It wasn't me! I was worried there for a bit. :smile:

I fixed a firmware bug which was causing the timing of the output pulses to be just a bit too close together.

Oh, dude. I noticed that the timing for a full track was a bit short with my I-should-really-make-a-PR Micropolis write support. I didn't care because it was small, but I should totally use the new firmware.

So, the issue seems to have been that the gap3 parameter was too big for the 1440kB format. It should have been 80, but was 108. The 720kB format seems fine (I can write a disk and read it back). I don't know what your 1581 disks use, but if they're based on --ibm-preset-720, they should work already. Are you setting --ibm-gap3-bytes?
I would suggest writing a disk, then reading back one track with --dump-sectors enabled. This will show more detailed information about which sectors have been seen. If the last one is missing, that suggests it's been truncated at the end of the track.

So, the issue seems to have been that the gap3 parameter was too big for the 1440kB format. It should have been 80, but was 108. The 720kB format seems fine (I can write a disk and read it back). I don't know what your 1581 disks use, but if they're based on --ibm-preset-720, they should work already. Are you setting --ibm-gap3-bytes?
I would suggest writing a disk, then reading back one track with --dump-sectors enabled. This will show more detailed information about which sectors have been seen. If the last one is missing, that suggests it's been truncated at the end of the track.

Yes, I use gap3. I am close to the gap values of the Atari ST pull request. I'm lacking in time at the moment. Solderer Greaseweazle F1 yesterday and am very impressed about how good Fluxengine client works with GW. I will post updates here once I find time. Only had time today.for the draft of the swapSides PR.

Yes, I use gap3. I am close to the gap values of the Atari ST pull request. I'm lacking in time at the moment. Solderer Greaseweazle F1 yesterday and am very impressed about how good Fluxengine client works with GW. I will post updates here once I find time. Only had time today.for the draft of the swapSides PR.

@davidgiven, are you sure the firmware fix was actually a fix? I flashed the new firmware and now my Micropolis encoder's written sectors are too large which causes hard sector misalignment and truncation of last sector.
With the new firmware, sectors are 12791 us long instead of 12500 us. (12791-12500)*12 MHz=3492 samples. Each sector has 6250 bitcells. My sector should have about 2295 flux transitions. I've only been able to push my logic analyzer to 8 MHz, so I can't see the drift on a small scale.

@davidgiven, are you sure the firmware fix was actually a fix? I flashed the new firmware and now my Micropolis encoder's written sectors are too large which causes hard sector misalignment and truncation of last sector.
With the new firmware, sectors are 12791 us long instead of 12500 us. (12791-12500)*12 MHz=3492 samples. Each sector has 6250 bitcells. My sector should have about 2295 flux transitions. I've only been able to push my logic analyzer to 8 MHz, so I can't see the drift on a small scale.

@ejona86 Well, I was. I'll double check. My logic analyser only works in Linux and I can only do firmware development from Windows, unfortunately...

@ejona86 Well, I was. I'll double check. My logic analyser only works in Linux and I can only do firmware development from Windows, unfortunately...

There was an extra tick in every interval. If you look in the writes branch, there may or may not be a fix --- something weird is going on with the Verilog which I don't understand, but it does pass a quick sanity test on my hardware.

There was an extra tick in every interval. If you look in the writes branch, there may or may not be a fix --- something weird is going on with the Verilog which I don't understand, but it does pass a quick sanity test on my hardware.

@davidgiven, the writes branch firmware produces writes similar to the previous behavior (not broken). I don't know Verilog, but I poke around at it some.

@davidgiven, the writes branch firmware produces writes similar to the previous behavior (not broken). I don't know Verilog, but I poke around at it some.

Tried hex file from writes branch with latest local Fluxengine build with my 1581 disk image. Disk written ok, disk read ok. MD5-Hashes Match for source image and reread image file. Looks very good to me so far!
(Side note - just observed : Floppy LED stays on "forever" after "fluxengine test bandwidth")

Tried hex file from writes branch with latest local Fluxengine build with my 1581 disk image. Disk written ok, disk read ok. MD5-Hashes Match for source image and reread image file. Looks very good to me so far!
(Side note - just observed : Floppy LED stays on "forever" after "fluxengine test bandwidth")

Excellent --- thanks for testing. Will merge and close the bug.

Excellent --- thanks for testing. Will merge and close the bug.


Write a specification for Data

We'd like to use the Plutus Data type for e.g. the values of metadata items.
We'd therefore like to have a standalone specification of it. This probably needs:

A formal description of the type, ideally using CDDL
A specification of how to encode/decode it from CBOR (should be straightforward if we do https://github.com/input-output-hk/cardano-ledger-specs/issues/1066)

It could probably also do with a better name than Data!

@michaelpj - This PR adds the necessary documentation as an appendix to the Shelley design document. It's not standalone, but I think both the shelley ledger spec and the plutus docs could reference it.

That's okay for now, although it'll be a bit weird for us to be referring to the "metadata value" type from the Shelley spec...


Redirect Tokens [SUPPORT]

I have a dispatcher in the contract to intercept the transfer action from the eosio.token contract, after which the event is processed, and at the end, it is necessary to redirect the tokens to another account. Redirect of tokens falls out with an error - not enough balance. Those. It seems that at the time of sending the redirect, eosio considers the balance not received. Is there any way to get around this problem, or is the redirect impossible?
Schema of one action:

Receive tokens on contract_a
Do things on contract_a
Transfer received tokens from contract_a to contract_b

Correct, the balance has not been finalized.  You could generate a deferred transaction, though you will need to keep an accounting of what balances should be transferred where in an internal table in the event the deferred transaction fails.  You'll need a contract action to retry.


trying using aria2c download is stuck at 0%

Hi thanks for the very useful code, I installed "git clone https://github.com/snobu/destreamer -b aria2c_forRealNow", followed the guide to build it, downloaded ffmpeg and pasted in the destreamer directory, I already installed aria2c with  the same process and I also set the variables.
When I run the command from prompt(same results using cmd ofc) :
PS C:\destreamerAria2\destreamer> ./destreamer.ps1 -o C:\Users...\Desktop\  -f C:\Users...\Desktop\videoStream.txt
I got this:
Access token still good for 49 minutes.
Parsing input file
Downloading video info, this might take a while...
Trying to launch and connect to aria2c...
Connected to aria2 daemon!
Downloading video no.1
Downloading video segments
progress [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0%   0 MB/s   0s
and it stays like that forever stuck until it appears some kind of aria2 download errors:
[ERROR] RECIVED URL TO RETRY, NOT IMPLEMENTED YET
[ERROR] {
"id": "getUrlForRetry",
"jsonrpc": "2.0",
"error": {
"code": 1,
"message": "The parameter at 0 has wrong type."
}
}
[ERROR] RECIVED URL TO RETRY, NOT IMPLEMENTED YET
[ERROR] {
"id": "getUrlForRetry",
"jsonrpc": "2.0",
"error": {
"code": 1,
"message": "The parameter at 0 has wrong type."
}
}
[ERROR] RECIVED URL TO RETRY, NOT IMPLEMENTED YET
[ERROR] {
"id": "getUrlForRetry",
"jsonrpc": "2.0",
"error": {
"code": 1,
"message": "The parameter at 0 has wrong type."
}
}
[ERROR] {"jsonrpc":"2.0","method":"aria2.onDownloadError","params":[{"gid":"b296a5cccf9712c4"}]}
[ERROR] {"jsonrpc":"2.0","method":"aria2.onDownloadError","params":[{"gid":"51bfad646202423c"}]}
[ERROR] {"jsonrpc":"2.0","method":"aria2.onDownloadError","params":[{"gid":"947ba997b59e4e3a"}]}
[ERROR] {"jsonrpc":"2.0","method":"aria2.onDownloadError","params":[{"gid":"3108f4fb13f7adb6"}]}
[ERROR] {"jsonrpc":"2.0","method":"aria2.onDownloadError","params":[{"gid":"9243de9867d0cfc0"}]}
[ERROR] RECIVED URL TO RETRY, NOT IMPLEMENTED YET
OS: Windows 10
Launch command used: ./destreamer.ps1 -o "path directory" -f "path txt file"

Verbose  log
PASTE VERBOSE LOG HERE
[VERBOSE] Using ffmpeg version 4.3.1-2020-10-28-essentials_build-www.gyan.dev Copyright (c) 2000-2020 the FFmpeg developers

[VERBOSE] Using aria2 version 1.35.0

[WARNING] Access token has expired!

Launching headless Chrome to perform the OpenID Connect dance...
Navigating to login page...

[ERROR] Error: net::ERR_NAME_NOT_RESOLVED at https://web.microsoftstream.com/
    at navigate (C:\Users\2019-2020\AppData\Roaming\destreamerAria2\destreamer\node_modules\puppeteer\lib\cjs\puppeteer\common\FrameManager.js:113:23)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async FrameManager.navigateFrame (C:\Users\2019-2020\AppData\Roaming\destreamerAria2\destreamer\node_modules\puppeteer\lib\cjs\puppeteer\common\FrameManager.js:88:21)
    at async Frame.goto (C:\Users\2019-2020\AppData\Roaming\destreamerAria2\destreamer\node_modules\puppeteer\lib\cjs\puppeteer\common\FrameManager.js:405:16)
    at async Page.goto (C:\Users\2019-2020\AppData\Roaming\destreamerAria2\destreamer\node_modules\puppeteer\lib\cjs\puppeteer\common\Page.js:826:16)
    at async DoInteractiveLogin (C:\Users\2019-2020\AppData\Roaming\destreamerAria2\destreamer\build\src\destreamer.js:59:5)
    at async main (C:\Users\2019-2020\AppData\Roaming\destreamerAria2\destreamer\build\src\destreamer.js:283:79)

[FATAL ERROR] Unhandled error or uncaught exception!
Please check your download directory/directories and try again.
If this keep happening please report it on github "https://github.com/snobu/destreamer/issues"

Tried  the same command on the plain version without aria2 and it works.  I can't figure it out how to set up properly aria2 ...

Sorry for the super very late response but I'm here. Aria2c was a rough build still, now it should be a little bit more stable. You could try again.
Again sorry for the late response but Uni was requiring all my time


Command Line Interface?

I'd like to get this running automatically via the command line, but it looks like it only runs as a Visual Studio extension. Is this correct?

You are correct. However, there is a command client called DevAudit which can do everything Audit.net can do and much, much more.

Great, thanks!


Adding Information To Readme

I was looking at the readme and noticed two sections that were missing that could be very helpful to have:

[ ] Environment variables and examples
[ ] Link to container on Dockerhub

Thanks

Good ideas; I'll add a section to the wiki on running silo from a docker container


fix: get rid of duplicate balance update dispatching

the updateBalances action is dispatched twice during wallet unlock:

once during Wallet.vue component creation (in created())
once in the UNLOCK_WALLET listener in background.js

When the wallet is unlocked the first component is always Wallet so we can get rid of the dispatch that happens in UNLOCK_WALLET

Tests reporting balance issue. Might be related to your change?


feat:filament doctor

basic troubleshoot and fix for common inquiry

idk if we should touch the user published views

@wychoong I'm happy to take this one over if you'd like?

@wychoong I'm happy to take this one over if you'd like?

sure :)

Will get this ready for a merge today :)

@Saifallak Yeah, that's what I'm waiting for :)

Replaced by https://github.com/filamentphp/filament/pull/3176


Feature request: New condition based on whether the PR author has merge permissions on the target

Hello! Thanks for the great action! This is a feature request -- if you're not open to those, no worries!

In some teams, people merge their own PRs once they are approved. However, when people without write access to the repo open a PR, someone on the team (that is, someone with merge permissions) needs to merge it because the author can't.
In such cases, it would be helpful to label PRs based on whether the author has write access.

Thanks @tylerbutler! Definitely open to requests (although I may not get to implementing them as fast as I'd like!)
The feature makes sense for me. I'll need to review the GH API to see whether it's possible to query for the author's permissions.

Looks like the new GH APIs should allow this based on -> https://github.com/google/go-github/blob/v50.0.0/github/repos_actions_allowed.go#L16


Progress Bar or Loading

How can we show the progress or loading spinner while the PDF is loading from the server. It takes a while before it actually displays the PDF so just a curious question if can show some spinner may be with pages loading

:+1: totally agree!

bump!

closed with b2d291182f9adec5e839d78e7d937e63c818f84c and 4b5dc9832cd052cbcc9dcc7035bab8d07951c79b

thanks for the suggestions again :smiley:  2 events are now exposed:

onLoad will be executed when the pdf is fully loaded (check docs)

onProgress will be executed with progress loaded and total details (check docs and example's browser console)


Browsing methods has issues

While selecting methods and checking class and instance (and also sometimes selecting the Variable tab by accident), I am seeing weird behavior in the project browser.
(1) sometimes there are blank lines within the list of categories.  And there are sometimes blank lines in the lists of methods.

(2) there are not infrequent halt: walkbacks. This may be the result of having the "Variable" tab selected rather than "Category", since I keep clicking on that as it's the right location for class methods. I think I've seen it other times, though.
I don't see a way to get a stack, but here's a picture:

The first issue should be fixed with the commit #978c253.

There was a patch put in place recently which should fix the second issue.
https://github.com/GemTalk/JadeiteForPharo/blame/12720953938ba7b3bb1672d96b5f0c0f755d8d41/RowanClientServicesClient/RowanServiceUpdater.class.st#L410


compileExprEx: ast.InitListExpr to []type{expr}[0]

fix https://github.com/goplus/c2go/issues/160
main.c
#include <stdio.h>

void test1(int a){}
void test2(int *b){}
void test3(char *c){}
void test4(const char** c){
    *c = "world";
}

int main() {
    int a;
    const char *b = "hello";
    test1((int){a});
    test2(&(int){a});
    test3(&(char){a});
    test4(&(const char*){b});
    printf("%s\n",b);
    return 0;
}

c2go  main.c
func _cgo_main() int32 {
	var a int32
	var b *int8 = (*int8)(unsafe.Pointer(&[6]int8{'h', 'e', 'l', 'l', 'o', '\x00'}))
	test1([]int32{a}[0])
	test2(&[]int32{a}[0])
	test3(&[]int8{int8(a)}[0])
	test4(&[]*int8{b}[0])
	printf((*int8)(unsafe.Pointer(&[4]int8{'%', 's', '\n', '\x00'})), b)
	return int32(0)
}

Codecov Report
Base: 88.80% // Head: 88.81% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (c0f954b) compared to base (df06408).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #170      +/-   ##
==========================================
+ Coverage   88.80%   88.81%   +0.01%
==========================================
  Files          10       10
  Lines        3341     3345       +4
==========================================
+ Hits         2967     2971       +4
  Misses        293      293
  Partials       81       81

Impacted Files
Coverage Δ

cl/expr.go
91.28% <100.00%> (+0.07%)
:arrow_up:

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

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

pls fix conflicts


Dapr sidecar keeps shutting itself down when deployed to container instances via az aks virtual node

In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

What version of Dapr?

1.1.x

Expected Behavior
Using dapr in combination with virtual-nodes on azure aks, should work
Actual Behavior
Pod deployed via:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: aci-helloworld
spec:
  replicas: 1
  selector:
    matchLabels:
      app: aci-helloworld
  template:
    metadata:
      labels:
        app: aci-helloworld
      annotations:
        dapr.io/enabled: "true"
        dapr.io/app-id: "myapp"
        dapr.io/log-level: "debug"
        dapr.io/app-port: "80"
    spec:
      containers:
      - name: aci-helloworld
        image: mcr.microsoft.com/azuredocs/aci-helloworld
        ports:
        - containerPort: 80
      nodeSelector:
        kubernetes.io/role: agent
        beta.kubernetes.io/os: linux
        type: virtual-kubelet
      tolerations:
      - key: virtual-kubelet.io/provider
        operator: Exists

The dapr sidecard keeps shutting itself down: https://pastebin.com/kDNaXb9d
Steps to Reproduce the Problem
kubectl apply -f dapr-test.yml
Release Note

RELEASE NOTE:
Fix dapr sidecard shutdown in container instances

Has anyone had similar experiences? Or tried to deploy and succeeded?

I'm having trouble with the same issue.
Has anyone had the same thing happen?


[DeviceRegistry] Generated SDK for Microsoft.DeviceRegistry API version 2024-09-01-preview

Generated SDK for Microsoft.DeviceRegistry API version 2024-09-01-preview.
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.DeviceRegistry


Added status badges

Issue
This repo's status is not displayed in the Charm Engineering Releases overview.
Solution
Added workflow badges for

CharmHub
Release
Tests

@a-velasco ,  @marceloneppel is on vacation, you can merge this IMHO.


Comment node loc.filename

This change was actually @loganfsmyth's, but I've confirmed that it resolves the issue I was experiencing.  When specifying multiple input source files to babel-generator, an invalid mapping error would occur due to a missing filename property in comment nodes' loc.  This change attaches the filename value if provided.
There is one failing test in master, as well as in this branch.  Looks like the issue is fixed in #76.
/cc @loganfsmyth

👍


Collection should prefetch items

Once prefetch support has landed in Simpla, a collection should start prefetching all the data its children need rather than waiting for DOM to be stamped and children to request data themselves.
pathChanged(path) {
  Simpla.prefetch(path)
}

This can work hand-in-hand #3, by prefetching the data for the next batch of items to be rendered so that infinite scrolling/lazy-loading is instantaeneous

Closing this as prefetch has been ditched in v3


Added cluster-group-upgrade package

@shaior can you resolve the merge conflicts? Other than that, looks good. Waiting for one more approval


AttributeError: 'dict' object has no attribute 'json'

from llama_parse import LlamaParse
documents = LlamaParse(result_type="markdown").load_data("uber_10q_march_2022.pdf")
Output--Started parsing the file under job_id c9d970f1-76ea-4fe2-89cc-859878869740
Error while parsing the PDF file 'uber_10q_march_2022.pdf': 'dict' object has no attribute 'json'
I am using colab notebook, btw it was working fine a day back.

Have a problem like that.

me too with python version 3.9

same, probably due to the introduction of the new json mode...

@JungeAlexander @MeTaNoV @mtsourma @jellchou @Nayal17
Fixed in v0.3.8
https://github.com/run-llama/llama_parse/pull/68


[Profiles] Adding Human readable PersonaStates

This gives you a nice human readable representation of the PersonaState.
   fmt.Fprintf(w, "%s is %s\n", user_info.PersonaName, user_info.PersonaState)

would print out
  "<user> is Online"

instead of the current approach that would print
  "<user> is 1"

This also lets you do things like:
  if user_info.PersonState.String() == "Online" {}

Why not simply do something like
switch p {
     case Offline:
           return "Offline"
    ...
}

?


api: add support for setting a container's hostname

Adds support for setting a container's hostname via the
ContainerSpec.Hostname. All containers in the service will get the
same value for the hostname.
This was implemented in a series of 5 commits by
Separate integration tests for CI
Signed-off-by: Nikolay Milovanov<EMAIL_ADDRESS>Added option hostname to docker service create
Signed-off-by: Vasil Yordanov<EMAIL_ADDRESS>Use Hostname field in agent/exec/container
Signed-off-by: Vasil Yordanov<EMAIL_ADDRESS>Added validation for hostname parameter
Signed-off-by: Vasil Yordanov<EMAIL_ADDRESS>Pre-compile the regexp for the hostname validation
Signed-off-by: Vasil Yordanov<EMAIL_ADDRESS>Signed-off-by: Stephen J Day<EMAIL_ADDRESS>Supersedes #1318.

LGTM

Current coverage is 56.15% (diff: 78.26%)

Merging #1688 into master will increase coverage by 0.07%

@@             master      #1688   diff @@
==========================================
  Files            89         89
  Lines         14475      14486    +11
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           8117       8134    +17
+ Misses         5278       5268    -10
- Partials       1080       1084     +4

Powered by Codecov. Last update f9c210a...1ce24f8

LGTM

LGTM

LGTM

@stevvooe thanks for merging this. For me and @vasil-yordanov  it was great experience be part of docker community.

@niau Thanks for sticking with it!


configure does not work with --enable-debug

I create two Makefiles with configure.
The first Makefile is created with --enable-debug=no, the secound one with --enable-debug=yes
I diff the files and the only different is a space in the CFLAGS argument.
CFLAGS =  -g -O2
CFLAGS = -g -O2

The --enable-debug flag only has an influence on the NODEBUG define of matioConfig.h.
Try to run ./configure --enable-debug=no CFLAGS="-O3" CPPFLAGS="-DNDEBUG" for an optimized release build.


CI: fix artifact copying for the custom profile

CI: fix artifact copying for the custom profile

Tested with temporarily moving deploy build steps into check-firmware (not included in this PR; check CI for builds).


Reuses stack in requireStackValues of func validation

goos: darwin
goarch: arm64
pkg: github.com/tetratelabs/wazero/internal/integration_test/bench
                                    │   old.txt   │              new.txt              │
                                    │   sec/op    │   sec/op     vs base              │
Compilation/with_extern_cache-10      117.0µ ± 0%   114.4µ ± 7%  -2.24% (p=0.026 n=7)
Compilation/without_extern_cache-10   2.282m ± 0%   2.276m ± 0%  -0.30% (p=0.004 n=7)
geomean                               516.8µ        510.2µ       -1.27%

                                    │   old.txt    │              new.txt               │
                                    │     B/op     │     B/op      vs base              │
Compilation/with_extern_cache-10      38.38Ki ± 0%   38.36Ki ± 0%       ~ (p=0.053 n=7)
Compilation/without_extern_cache-10   1.216Mi ± 0%   1.215Mi ± 0%       ~ (p=0.073 n=7)
geomean                               218.6Ki        218.5Ki       -0.03%

                                    │   old.txt   │              new.txt              │
                                    │  allocs/op  │  allocs/op   vs base              │
Compilation/with_extern_cache-10       538.0 ± 0%    516.0 ± 0%  -4.09% (p=0.001 n=7)
Compilation/without_extern_cache-10   7.525k ± 0%   7.503k ± 0%  -0.29% (p=0.001 n=7)
geomean                               2.012k        1.968k       -2.21%

yep, the validation and compilation phrase is sequential per Wasm binary!


Enable custom lighting in playblast

Currently playblast only uses default lighting, artist should be able to playblast with custom lighting

Implemented with #55


wtf?

Describe your bug here.
game wont compile on linux
Command Prompt/Terminal logs (if existing)
[ender@archlinux FNF-PsychEngine]$ haxelib run lime test linux
source/psychlua/HScript.hx:317: characters 89-96 : Type not found : TeaCall

Are you modding a build from source or with Lua?
Source
What is your build target?
Linux
Did you edit anything in this build? If so, mention or summarize your changes.
no

womp womp

Replace TeaCall with Tea

close notes: if linux then replace all TeaCall with Tea

womp womp

Instead of being helpful, you are just replying to other people's messages with "womp womp". What has this society become with "Womp Womp"? Be helpful for once.


Can I translate this guide to portuguese?

Yes please. 👍 . Just remember to follow the file naming convention (see the Chinese version) and also link back to English version on Portuguese README . Thanks

@kvnol I was wondering if you're still up for this :D


Probe disconnects without any error or warning

A freshly installed probe stop running after a random time.
The logging (including debug log) doesn't report anything out of the ordinary

Started a screen session with the probe manually started inside the screen session. Now it's just a matter of time until the probe crashes to see what goes wrong.

Have you checked the Log of the PRTG Core Server? Anything unusual there?
Also, are you able to reproduce the disconnect at will?

There is no entry in the logfile as i already stated in my initial request.
I can't reproduce it at an instant, that's why i started a screen session with the probe manually started in the screen session to see if the probe dumps a tracelog to the console when it crashes.

@eagle00789 just talked to the interface developer on core side and he is looking into this right now. It seems that he might have found the flaw and is already working on fixing the same. I'll keep this issue open until a fix is out.

Even though you think it's the core side, i will still monitor one of my probes to see what the tracelog prints when it fails (if it print's something at all)

my probe that i was monitoring with screen, just crashed and gave the following error on the console:
Traceback (most recent call last):
  File "probe.py", line 211, in <module>
    main()
  File "probe.py", line 182, in main
    logging.error("DATA Timeout: " + json_payload_data)
TypeError: cannot concatenate 'str' and 'list' objects

To fix this, replace line 182 in probe.py with the line below
logging.error("DATA Timeout: " + str(json_payload_data).strip('[]'))

@eagle00789 looking forward to the pull request. If done on the weekend it might get Monday until I can accept. Issue stays open therefore.

Closing this issue because of bugfix in pull request


Redesign DataFrame structure

Extension for #801
Implementation of new DataFrame structure based on lists instead of tuples
Improved df.count() codegen for testing
Example:
df = pd.DataFrame({'A': [1,2,3], 'B': [.5, .6, .7], 'C': [4, 5, 6], 'D': ['a', 'b', 'c']})

(['A', 'B', 'C', 'D'],)
([array([1, 2, 3], dtype=int64), array([4, 5, 6], dtype=int64)], [array([0.5, 0.6, 0.7])], [array(['a', 'b', 'c'], dtype=object)])

Reproduce:
@njit
def run_df():
    df = pd.DataFrame({'A': [1,2,3], 'B': [.5, .6, .7], 'C': [4, 5, 6], 'D': ['a', 'b', 'c']})

    print(df._columns)
    print(df._data)

    return df.count()

Hello @akharche! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file sdc/hiframes/pd_dataframe_ext.py:

Line 57:1: W293 blank line contains whitespace
Line 73:1: W293 blank line contains whitespace
Line 76:1: W293 blank line contains whitespace
Line 80:1: W293 blank line contains whitespace
Line 81:9: E303 too many blank lines (2)
Line 82:33: E231 missing whitespace after ','
Line 84:1: W293 blank line contains whitespace
Line 86:22: W291 trailing whitespace
Line 88:1: W293 blank line contains whitespace
Line 91:1: E302 expected 2 blank lines, found 1
Line 134:86: E202 whitespace before ')'

Performance results of DataFrame with mixed types of columns

Columns
Current compile time, s
New compile time, s
New/Current

4
11.092775
9.713415
0.875652

8
28.611168
20.057998
0.701055

16
128.307209
67.369364
0.525062

32
803.671405
310.529887
0.386389

Performance results of DataFrame with mixed types of columns
Columns	Current compile time, s	New compile time, s	New/Current
4	11.092775	9.713415	0.875652
8	28.611168	20.057998	0.701055
16	128.307209	67.369364	0.525062
32	803.671405	310.529887	0.386389

The results look very good.

@akharche examples failed


Fix dask chunks args to match length of shape.

Exposed when updating to dask 0.11.1.

This unblocks #1592.

Coverage remained the same at 89.587% when pulling 5a16c68517799a3e82a3440c736ed7073825ba89 on kwmsmith:bugfix/dask-chunks-args into f13352a82a79e847c4ac3587adee09f22d9c3082 on blaze:master.

Nice! This is blocking other work of mine so I am going to merge.