Allow multiple blockToReplace in configuration.

Hey there I just open this as a proper issue instead on relying on Curse comments, I just found this repository.
It would be really cool if the configuration would allow to define multiple replacement blocks.
So instead of having an Object we could make an Array like the weightedBlocks have.
Before:
[
    {
        "blockToReplace": {
            "Block": "minecraft:stone",
            "Properties": {
                "variant": "stone"
            }
        },
        "generatorPriority": "LATEST",
        "generatorType": "STANDARDVARIABLECLUSTER",
        "frequency": 1,
        "minY": 0,
        "maxY": 128,
        "size": 100,
        "weightedBlocks": [
            {
                "Weight": 30,
                "Block": "gold_ore",
                "Properties": {}
            },
            {
                "Weight": 5,
                "Block": "iron_ore",
                "Properties": {}
            },
        ],
        "dimensions": [
            0
        ],
        "category": {
            "name": "Compound Biome Ores",
            "defaultEnabled": true
        },
        "chance": 0.15
    }
]

After:
[
    {
       "blockToReplace": [
            {
                "Block": "minecraft:stone",
                "Properties": {
                    "variant": "stone"
                }
            },
            {
                "Block": "minecraft:netherrack",
                "Properties": {
                    "variant": "stone"
                }
            }
        ],
        "generatorPriority": "LATEST",
        "generatorType": "STANDARDVARIABLECLUSTER",
        "frequency": 1,
        "minY": 0,
        "maxY": 128,
        "size": 100,
        "weightedBlocks": [
            {
                "Weight": 30,
                "Block": "gold_ore",
                "Properties": {}
            },
            {
                "Weight": 5,
                "Block": "iron_ore",
                "Properties": {}
            },
        ],
        "dimensions": [
            0
        ],
        "category": {
            "name": "Compound Biome Ores",
            "defaultEnabled": true
        },
        "chance": 0.15
    }
]

This is a good suggestion, I never really thought about it being necessary because I have only personally used standard vanilla "foundation rock generation" where it makes sense to just duplicate the entry with a different blockToReplace, they never have overlap. It would mean a lot of random and unnecessary entry bloat for something like minerology or geostrata if you want to specify what blocks can be replaced. I need to rewrite the parsing that I do, because I want to avoid breaking pre existing configs, and hate just asking people to delete their configs, but will get this implemented in the future.

One possibility to prevent breaking extant configs is to change the property name to blocksToReplace and deprecating blockToReplace, perhaps throwing a warning in the log if it is used. Another option would be to allow blockToReplace to contain either a JSON object or a JSON array and switch your handling based on the type the config's creator used. This is similar to how CoFH structured their world gen config.


Semantic similarity

This adds a base code to train a document similarity model. It includes

[x] Similarity model for transformers/tensorflow (ml/bert_semantic_equivalence.py)
[x] Tests and independent test platform for new versions of transformers that clash with spacy
[x] An example with 100 pairs of sentences

To test:
make test-transformers

 Implement a Sentence Matching tuning model for Scibert classifier

I''m getting the error
ERROR: spacy-transformers 0.5.1 has requirement transformers<2.1.0,>=2.0.0, but you'll have transformers 2.4.1 which is incompatible.
Installing collected packages: filelock, tokenizers, transformers, tensorflow
  Attempting uninstall: transformers
    Found existing installation: transformers 2.0.0
    Uninstalling transformers-2.0.0:
      Successfully uninstalled transformers-2.0.0
Successfully installed filelock-3.0.12 tensorflow-2.1.0 tokenizers-0.0.11 transformers-2.4.1
build/virtualenv/bin/pytest -m "transformers" --disable-warnings --cov-append --tb=line --cov=wellcomeml ./tests
/bin/sh: build/virtualenv/bin/pytest: No such file or directory

when I do make test-transformers

I''m getting the error
ERROR: spacy-transformers 0.5.1 has requirement transformers<2.1.0,>=2.0.0, but you'll have transformers 2.4.1 which is incompatible.
Installing collected packages: filelock, tokenizers, transformers, tensorflow
  Attempting uninstall: transformers
    Found existing installation: transformers 2.0.0
    Uninstalling transformers-2.0.0:
      Successfully uninstalled transformers-2.0.0
Successfully installed filelock-3.0.12 tensorflow-2.1.0 tokenizers-0.0.11 transformers-2.4.1
build/virtualenv/bin/pytest -m "transformers" --disable-warnings --cov-append --tb=line --cov=wellcomeml ./tests
/bin/sh: build/virtualenv/bin/pytest: No such file or directory

when I do make test-transformers

I think you need to create the virtualenv witth make virtualenv first. You might have to re-created if you created it a while ago, because it installs the pytest routines.

Codecov Report

Merging #43 into master will increase coverage by 0.75%.
The diff coverage is 88.17%.

@@            Coverage Diff             @@
##           master      #43      +/-   ##
==========================================
+ Coverage   79.12%   79.87%   +0.75%
==========================================
  Files          24       25       +1
  Lines         910      989      +79
==========================================
+ Hits          720      790      +70
- Misses        190      199       +9

Impacted Files
Coverage Δ

wellcomeml/ml/constants.py
100.00% <ø> (ø)

wellcomeml/ml/bert_semantic_equivalence.py
87.32% <87.32%> (ø)

wellcomeml/ml/__init__.py
90.90% <90.00%> (+5.19%)
:arrow_up:

wellcomeml/ml/bert_vectorizer.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Would you mind having another look @lizgzil @nsorros ? I think I implemented all the suggestions.

I also got the error ERROR: spacy-transformers 0.5.1 has requirement transformers<2.1.0,>=2.0.0, but you'll have transformers 2.6.0 which is incompatible. when I was building the transformers in . Which I guess you know about!

Yes, the error is intentionally induced at this point, to switch spacy off. I'll look into adding something about the rust error to readme


Small typo

"The data will be slower for query performance, which is acceptable if the partition is queries infrequently."

Should read

"The data will be slower for query performance, which is acceptable if the partition is queried infrequently."

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

ID: 4b8faf5d-ad57-f652-0970-2cdcdda2929c
Version Independent ID: af4c93c4-9959-fe9e-984d-876eddf06ff5
Content: Columnstore indexes - Design guidance - SQL Server
Content Source: docs/relational-databases/indexes/columnstore-indexes-design-guidance.md
Service: sql
Sub-service: table-view-index
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

@GabiRepare -- Gabriel, thank you for catching this.  I am updating the article.


Extension - AssetIndex - Integrate the PostgreSQL library

Issue #438 provided a library that supports PostgreSQL persistence. Integrate this library in a new AssetIndex extension.
Dominik Pinsel<EMAIL_ADDRESS>Daimler TSS GmbH, legal info/Impressum

duplicated


Update spice-client-jvm to 0.5.14

About this PR
📦 Updates com.outr:spice-client-jvm from 0.5.5 to 0.5.14
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.outr", artifactId = "spice-client-jvm" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.outr", artifactId = "spice-client-jvm" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, version-scheme:semver-spec, commit-count:1

Superseded by #317.


LED, Sound, and Vibration do not work on Android 8.0 using recommended "data" payload

Expected Behaviour

Notification should appear in status bar
LED should flash when notification is received with app in background
Device should vibrate when notification is received with app in background
Sound should play when notification is received with app in background

Actual Behaviour

Notification appears in status bar
Samsung Note 8 (Android 8.0.0): Sound, vibration, and LED indicators do not work
Samsung S5 (Android 6.0.1): Sound, vibration, and LED indicators do not work

Reproduce Scenario (including but not limited to)
Sending push message via FCM - https://fcm.googleapis.com/fcm/send
Place all message attributes into "data" key of the payload, per plugin readme: https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/PAYLOAD.md#notification-vs-data-payloads
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
Android 8.0.0
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Samsung Galaxy Note 8
Cordova CLI version and cordova platform version
cordova -version: 8.0.0
cordova platform: android 7.1.0
Plugin version
2.2.3
Sample Push Data Payload
{
"registration_ids": ["$deviceId"],
"data": {
"title": "Notification",
"body": "hello world"
"soundname": "default",
"ledColor": [ 255, 255, 128, 16],
"vibrationPattern": [250, 1000, 250, 500]
}
}
When the "title" and "body" portions of the payload are moved into a "notification" key, then the notification sound and vibration (pattern ignored) work on Android 8.0.0. However, adding a notification key breaks all 3 indicators (sound, vibration, and LED) on Android 6.0.1
Sample Code that illustrates the problem
const push = PushNotification.init({             android: { sound: true, vibrate: true},             ios: { alert: true, badge: true, sound: true }         });
push.on('notification', data => {             console.log(data);         });

@roland83 you are running into the notification vs data problem which is documented:
https://github.com/phonegap/phonegap-plugin-push#what-is-this
https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/PAYLOAD.md#notification-vs-data-payloads
Move everything from notification and into data and you should be okay.

@macdonst I already tried that as noted in the issue. Moving everything into data does not help. The LED and vibration does not work no matter how I arrange my payload.

@roland83 make sure you don't even put a notification section in your push payload. Can you reproduce the issue while running adb logcat | grep Push?

@macdonst In fact, putting everything into data makes the problem worse. When I split the payload between notification and data, my Android 8.0.0 device plays the notification sound.
When I put everything into data the notification will come through but there is no sound, LED Indication or vibration.
Here is the payload with everything in the data field (except the device ID, as that results in a failure response from FCM with no message sent
{
"to": "dg4l_EUJBQ.....",
"data": {
"title": "Test Notification",
"body": "hello",
"soundname": "default",
"ledColor": [255, 255, 128, 16],
"vibrationPattern": [250, 1000, 250, 500]
}
}
If I'm doing something wrong please help me understand. Appreciate your quick reply to the issue.

I attempted to use adb logcat while troubleshooting yesterday but struggled to get output. Do you have a link that provides more details on it's use?

@roland83 yeah, we'll need some logs to figure it out.
https://developer.android.com/studio/command-line/logcat

@macdonst Thank you. I got logcat working (my issue yesterday was writing the output to a file, no trouble at all piping output to grep)
I notice at the end vibrate=null, sound=null, color=0 so that seems consistent with the behavior. Is there something wrong with my payload? I sent the same one as listed above.
adb logcat | grep Push output
06-15 10:58:06.479 18669 19875 D Push_FCMService: onMessage - from:<PHONE_NUMBER>32
06-15 10:58:06.482 18669 19875 D Push_FCMService: sender id =<PHONE_NUMBER>32
06-15 10:58:06.483 18669 19875 D Push_FCMService: normalize extras
06-15 10:58:06.483 18669 19875 D Push_FCMService: key = soundname
06-15 10:58:06.483 18669 19875 D Push_FCMService: replace key soundname with sound
06-15 10:58:06.484 18669 19875 D Push_FCMService: key = body
06-15 10:58:06.484 18669 19875 D Push_FCMService: replace key body with message
06-15 10:58:06.484 18669 19875 D Push_FCMService: no locale found for key = message, error Value hello of type java.lang.String cannot be converted to JSONObject
06-15 10:58:06.484 18669 19875 D Push_FCMService: key = title
06-15 10:58:06.484 18669 19875 D Push_FCMService: replace key title with title
06-15 10:58:06.484 18669 19875 D Push_FCMService: no locale found for key = title, error Value Test of type java.lang.String cannot be converted to JSONObject
06-15 10:58:06.484 18669 19875 D Push_FCMService: key = vibrationPattern
06-15 10:58:06.484 18669 19875 D Push_FCMService: replace key vibrationPattern with vibrationPattern
06-15 10:58:06.485 18669 19875 D Push_FCMService: key = ledColor
06-15 10:58:06.485 18669 19875 D Push_FCMService: replace key ledColor with ledColor
06-15 10:58:06.485 18669 19875 D Push_FCMService: background
06-15 10:58:06.485 18669 19875 D Push_FCMService: message =[hello]
06-15 10:58:06.485 18669 19875 D Push_FCMService: title =[Test Notification]
06-15 10:58:06.485 18669 19875 D Push_FCMService: contentAvailable =[null]
06-15 10:58:06.485 18669 19875 D Push_FCMService: forceStart =[null]
06-15 10:58:06.485 18669 19875 D Push_FCMService: create notification
06-15 10:58:06.486 18669 19875 E Push_FCMService: Number format exception - Error parsing notId: s == null
06-15 10:58:06.492 18669 19875 D Push_FCMService: Using channel ID = PushPluginChannel
06-15 10:58:06.492 18669 19875 D Push_FCMService: Using channel ID = PushPluginChannel
06-15 10:58:06.496 18669 19875 D Push_FCMService: stored icon=null
06-15 10:58:06.496 18669 19875 D Push_FCMService: stored iconColor=null
06-15 10:58:06.496 18669 19875 D Push_FCMService: stored sound=true
06-15 10:58:06.496 18669 19875 D Push_FCMService: stored vibrate=true
06-15 10:58:06.497 18669 19875 D Push_FCMService: no icon resource found - using application icon
06-15 10:58:06.502 18669 19875 D Push_FCMService: create actions: with in-line
06-15 10:58:06.508  3415  3415 D EdgeLightingManager: showForNotification : isInteractive=false, isHeadUp=false, color=0, sbn = StatusBarNotification(pkg=com.entrologic.Eatza user=UserHandle{0} id=0 tag=Eatza key=0|com.entrologic.Eatza|0|Eatza|10252: Notification(channel=PushPluginChannel pri=0 contentView=null vibrate=null sound=null tick defaults=0x0 flags=0x11 color=0x00000000 number=0 vis=PRIVATE semFlags=0x0 semPriority=0 semMissedCount=0))

Here's the data that the plugin is passing send up to Javascript layer in the notification event
** .on('notification', data => { console.dir(data) }); **
Object >
additionalData:
coldstart: false
foreground:true
ledColor: (4) [255, 255, 128, 16]
vibrationPattern: (4) [250, 1000, 250, 500]
Object >
message: "test"
sound: "default"
title: "Test Notification"

When I remove the "notification" key from payload, Android 6.0.1 does not get the notification at all.

@macdonst I have some additional details:
Removing the "notification" key from the payload gets everything to work as expected on Android 6.0.1. The sound is played, vibration works, LED is flashing and an entry is created in the notification bar.
On my Note 8 (Android 8.0.0), removing the notification key from the payload gives me an entry in the notification bar (with icon, title, and body) as well as a badge number on the app icon. But I do not get a sound, vibration, or LED indicator.

Partial workaround: When sending a push message to Android 8.0.0, including the "notification" key in the payload gets the sound to play and the device to vibrate (only tested with default sounds so far and the vibration pattern seems to be ignored)
Sending a push message to Android 6 (and presumably 7) must put all parameters in the "data" portion of the payload.

@roland83 Okay, I'm glad you got it working for an Android 6 device. I cannot stress enough how important it is not to include a notification area in your payload. That will just bypass this plugin altogether and use the OS to display the push. None of the options you provide in the data section of the payload will be read.
With the Android 8 device I'm going to have to retest. There might be an issue with the default message channel as you pointed out. I will get to this as soon as I can but right now I'm travel for a conference talk.

@macdonst Thanks again for your help
Message channels don't seem to be working as expected for me. For example I created a new channel and included the android_channel_id in my payload but I'm not getting any of the defined behavior for that channel.
Also, the plugin always creates the default channel, even though I'm calling PushNotification.init in the success callback of createChannel. My understanding was that plugin wouldn't create the default channel if you defined your own before calling init.
I will open a new issue with further details.

@roland83 sorry, I can't reproduce this. I'm wondering if it is something Samsung is over-riding with regards to push messages.

I dont see how you can set led color and vibration pattern server side as the default channel is created on first launch of the app, simply you cant. I made it work by hard coding led color and vibration pattern (plugin version 2.1.2, for now i stay on cordova android 6.3.0):
  @TargetApi(26)   private void createDefaultNotificationChannelIfNeeded(JSONObject options) {     // only call on Android O and above     if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {       final NotificationManager notificationManager = (NotificationManager) cordova.getActivity()           .getSystemService(Context.NOTIFICATION_SERVICE);       List<NotificationChannel> channels = notificationManager.getNotificationChannels();       if (channels.size() == 0) {         NotificationChannel mChannel = new NotificationChannel(DEFAULT_CHANNEL_ID, "PhoneGap PushPlugin",             NotificationManager.IMPORTANCE_DEFAULT);         mChannel.enableVibration(options.optBoolean(VIBRATE, true));         **mChannel.enableLights(true);         mChannel.setLightColor(0xFF0000FF);         mChannel.setVibrationPattern(new long[]{0, 1000, 500, 1000});**         mChannel.setShowBadge(true);         notificationManager.createNotificationChannel(mChannel);       }     }   }

@Stefano1964, the createChannel method does not include any params whatsoever related to the LED or its color. Therefore, setting the LED color via payload is, I'm afraid, not only perfectly valid, but actually the only way.

@andreszs the createChannel it's Android and yes you can set LED Color in crating a channel

@Stefano1964 Right, after inspecting the PushPlugin.java file I see that indeed it can set the LED color, however this is not documented, how can we know the possible values/format for this parameter?

The format it's argb


How to trigger the slack notification manually

Manually as in? Manually from GitHub actions or do you want to run it from your local machine?

see, I want to send slack notification conditionally. for example, I have build/deply jobs inside a workflow, so i only wanna send slack notification if the branch is master then send otherwise dont

Please go through events that trigger workflows GitHub doc.
Particularly for your use case check this.
on:
  # Trigger the workflow on push or pull request,
  # but only for the master branch
  push:
    branches:
      - master


chore: use peer deps for api category for cdk and constructs

Description of changes
Use Peer dep for api category to ensure we're more easily aligned w/ the CLI moving forward. Related PR in CLI https://github.com/aws-amplify/amplify-cli/pull/12937
CDK / CloudFormation Parameters Changed
N/A
Issue #, if available
N/A
Description of how you validated changes
Unit + E2E tests
Checklist

[x] PR description included
[ ] yarn test passes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1664 (77d165e) into main (d14d82f) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main    #1664   +/-   ##
=======================================
  Coverage   63.76%   63.76%
=======================================
  Files         370      370
  Lines       21772    21772
  Branches     5211     5211
=======================================
  Hits        13882    13882
  Misses       7168     7168
  Partials      722      722

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fusiondirectory: Init at 1.2.3

Motivation for this change
I'm using Fusiondirectory to manage my LDAP tree with users, groups and associated permissions.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@joachifm I redid and rebased the PR, hopefully it's ok now ;)

It doesn't appear that my comments have been addressed. Or is that merely a github UI issue?

Nah, just me being too dumb to use git :/ Pushed now

Ping again @joachifm

Are there still reasons to not merge this?

@GrahamcOfBorg build fusiondirectory

@dasJ do you have access to a mac so that you could fix the build error on x86_64-darwin?

Stale, it's outdated


Add wrappers as submodule

Add qMRWrappers as submodule to the External directory.

@jvelazquez-reyes I am adding qMRWrappers as submodule to the repository, so the latest Docker images include BIDS wrappers. Sourcing files from GitHub within a process fails every now and then due to connection issues, this would prevent that as well.
After this is merged, when the qMRLab is cloned using:
git clone --depth 1 --recurse-submodules https://github.com/qmrlab/qmrlab

will have External/qMRWrappers.  For now it can stay in the External dir, we can move it to the root later on.
You can keep working on your developments at the wrappers front. Just wanted to inform you what this means.


Question about optional tileMatrixSetDefinition

I see that tileset metadata is required to have only one of the following: tileMatrixSetURI, tileMatrixSetDefinition, or tileMatrixSet.  It looks like the tileMatrixSetURI do not resolve to a tile matrix set definition.  I'm curious what the thinking is around how a client might determine the tile matrix set definition given a tileMatrixSetURI.
If a client is built with definitions for all of the tile matrix sets registered with the OGC NA definition service, this only works until a new tile matrix set definition is registered.  Meaning all client libraries would need to be updated, and all clients would have to be redeployed any time a new tile matrix set definition is registered.
It would be more forward compatible if the spec required that servers host tile matrix set definitions even if they conform to a definition registered with the OGC NA definition service.  This seems like a minor burden on server implementations (to always host the definitions for the tile matrix sets that they support), and it would allow clients to continue working even after new tile matrix sets are defined and registered.
If the tileMatrixSetDefinition (or tileMatrixSet) were required any time tileMatrixSetURI were used, clients that already know the definition for a specific URI could skip fetching the definition.  At the same time, clients that come across a tileMatrixSetURI that is not recognized (perhaps it was registered after the client was built), the client could rely on being able to fetch the tileMatrixSetDefinition.
If the spec required one of tileMatrixSetDefinition or tileMatrixSet and said tileMatrixSetURI was optional, clients could optionally skip fetching the definition where tileMatrixSetURI was available and recognized, but could always rely on being able to get the definition (in case tileMatrixSetURI is not recognized).

@tschaub The intent is that it should resolve to a TileMatrixSet definition.
In the mean times, those TileMatrixSets currently registered are all defined in the 2D TMS standard.
I think it would make sense to at least make it a recommendation that the server also provides a tileMatrixSetDefinition locally.
The tileMatrixSetURI is still important for simpler clients implementing support only for specific TMS without the capability to parse, understand and support arbitrary TMSes.

I agree about the benefits of tileMatrixSetURI as an identifier for clients that are built with an internal mapping to the corresponding tile set definition.
However, I think the spec overlooks the drawbacks of making the tileMatrixSetDefinition or tileMatrixSet optional.  Unfortunately, a mere recommendation to include one or the other is not enough (a reliable client can only depend on spec requirements).
If the idea is that eventually all tileMatrixSetURI will resolve to a tile matrix set definition, there are additional concerns to consider:

Mixed-Content: The current http protocol URI (e.g. http://www.opengis.net/def/tilematrixset/OGC/1.0/WebMercatorQuad) will likely be blocked by clients hosted with the https protocol.
CORS: The OGC hosted tile matrix set definitions, even if available via https, would need to be configured to allow cross-origin requests from all origins and properly handle CORS-preflight requests.

If the spec required that either tileMatrixSetDefinition or tileMatrixSet be included, a client would be guaranteed a way to understand the tile matrix set.  This would still allow for clients to take advantage of the optional tileMatrixSetURI if it were available.  The additional requirement would mean that servers would need to provide access to the tile matrix set definition.  This minor additional requirement comes with the benefit of being able to deploy client/server implementations that are free from mixed-content or cross origin resource sharing issues.
In short, I think this would make for a better tileSet.json spec:
{
  "$schema": "https://json-schema.org/draft/2019-09/schema",
  "title": "Tile Set Metadata",
  "description": "A resource describing a tileset based on the OGC TileSet Metadata Standard",
  "allOf": [
    {
      "type": "object",
      "properties": {
        // additional optional properties here...
        "tileMatrixSetURI": {
          "description": "Reference to a Tile Matrix Set on the OGC NA definition server (http://www.opengis.net/def/tms/). Required if the tile matrix set is registered on the definition server.",
          "type": "string",
          "format": "uri",
          "examples": [
            "http://www.opengis.net/def/tilematrixset/OGC/1.0/GNOSISGlobalGrid"
          ]
        }
      }
    },
    {
      "description": "At least one of 'TileMatrixSet' or 'TileMatrixSetDefinition' SHAL be provided",
      "anyOf": [
        {
          "type": "object",
          "required": [
            "tileMatrixSet"
          ],
          "properties": {
            "tileMatrixSet": {
              "description": "Tile matrix set definition",
              "$ref": "tileMatrixSet.json"
            }
          }
        },
        {
          "type": "object",
          "required": [
            "tileMatrixSetDefinition"
          ],
          "properties": {
            "tileMatrixSetDefinition": {
              "description": "Reference to a tile matrix set definition following the Tile Matrix Set Standard. Optional for tile matrix sets defined on the OGC definition server; required for custom Tile Matrix Sets.",
              "type": "string",
              "examples": [
                "http://data.example.com/tileMatrixSets/WorldMercatorWGS84Quad"
              ]
            }
          }
        }
      ]
    }
  ]
}

@tschaub Thank you for bringing up this issue -- I understand your additional concerns. @joanma747 I suggest we discuss this at our next OGC API - Tiles SWG meeting.

We agreed 2021-06-03 on requiring tileMatrixSet or tileMatrixSetDefinition independently of having a tileMatrixSetURI.

Change applied everywhere.


Fix link

The composer install link was not correct.

We probably don't want to link directly to the linux/unix/OSX directions—we might confuse the poor Windows users. How about just removing the hash portion of the link?

Yeah that works, I was just copying the link that was further up in the doc. :)

Thank you!


[TTGlyphPen] Fix NotImplementedError with open contours

Fixes #2365

failed CI build reproducing #2366
https://github.com/fonttools/fonttools/pull/2366/checks?check_run_id=3079162289#step:5:391


How can I check if a token is valid?

I have a collection that I have set so that only my node backend with admin permissions can modify, but I want users that are logged in to be able to modify the collection (through the node backend that runs some special logic). I can pass the user's token to the backend, but how can I check that the token is valid to prove the user is logged in?

We don't have a dedicated token verification endpoint.
Instead you can send the token with the authRefresh() call. It throws an error on invalid or expired token, on success - returns a new token token with refreshed exp claim and up-to-date user data.
pb.authStore.save(yourToken, null);

await pb.collection("users").authRefresh();


operator [O] splunk (2.0.0)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[x] Is your submission signed?
[x] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/unhold

/retest

Dear @vivekr-splunk, Some errors and/or warnings were found while doing the check of your operator (splunk/2.0.0) against the entire suite of validators for Operator Framework with Operator-SDK version v1.19.1 and the command $ operator-sdk bundle validate <bundle-path> --select-optional suite=operatorframework.
Errors (🐛) must be fixed while warnings (⚠) are informative, and fixing them might improve the quality of your solution.
Type	Message
⚠	Value enterprise.splunk.com/v1beta2, Kind=Standalone: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta3, Kind=SearchHeadCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta1, Kind=ClusterMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v2, Kind=ClusterMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta1, Kind=LicenseMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta3, Kind=IndexerCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta3, Kind=LicenseMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta3, Kind=Standalone: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1, Kind=SearchHeadCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1alpha1, Kind=SearchHeadCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta3, Kind=ClusterMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta2, Kind=IndexerCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1alpha1, Kind=LicenseMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta1, Kind=SearchHeadCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v2, Kind=SearchHeadCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1alpha1, Kind=ClusterMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1, Kind=IndexerCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1, Kind=LicenseMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta2, Kind=LicenseMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1, Kind=Standalone: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v2, Kind=Standalone: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta2, Kind=ClusterMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1alpha1, Kind=IndexerCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta2, Kind=SearchHeadCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1alpha1, Kind=Standalone: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1, Kind=ClusterMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v2, Kind=IndexerCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v2, Kind=LicenseMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta1, Kind=IndexerCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta1, Kind=Standalone: provided API should have an example annotation
⚠	Value : found olm.properties annotation, please define these properties in metadata/properties.yaml instead

Dear @vivekr-splunk, Some errors and/or warnings were found while doing the check of your operator (splunk/2.0.0) against the entire suite of validators for Operator Framework with Operator-SDK version v1.19.1 and the command $ operator-sdk bundle validate <bundle-path> --select-optional suite=operatorframework.
Errors (🐛) must be fixed while warnings (⚠) are informative, and fixing them might improve the quality of your solution.
Type	Message
⚠	Value enterprise.splunk.com/v1beta2, Kind=Standalone: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta3, Kind=SearchHeadCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta1, Kind=ClusterMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v2, Kind=ClusterMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta1, Kind=LicenseMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta3, Kind=IndexerCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta3, Kind=LicenseMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta3, Kind=Standalone: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1, Kind=SearchHeadCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1alpha1, Kind=SearchHeadCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta3, Kind=ClusterMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta2, Kind=IndexerCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1alpha1, Kind=LicenseMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta1, Kind=SearchHeadCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v2, Kind=SearchHeadCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1alpha1, Kind=ClusterMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1, Kind=IndexerCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1, Kind=LicenseMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta2, Kind=LicenseMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1, Kind=Standalone: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v2, Kind=Standalone: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta2, Kind=ClusterMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1alpha1, Kind=IndexerCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta2, Kind=SearchHeadCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1alpha1, Kind=Standalone: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1, Kind=ClusterMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v2, Kind=IndexerCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v2, Kind=LicenseMaster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta1, Kind=IndexerCluster: provided API should have an example annotation
⚠	Value enterprise.splunk.com/v1beta1, Kind=Standalone: provided API should have an example annotation
⚠	Value : found olm.properties annotation, please define these properties in metadata/properties.yaml instead

can we add 'allow/longer-deployment' label, its creating emptydir as volume. i am not sure if that is taking time or its failing due to the above volume. let me know what log files I can check. locally it works.

@vivekr-splunk I noticed following. What do you think?
    conditions:
    - lastProbeTime: null
      lastTransitionTime: "2022-08-05T16:18:18Z"
      message: '0/1 nodes are available: 1 Insufficient cpu.'
      reason: Unschedulable
      status: "False"
      type: PodScheduled
    phase: Pending
    qosClass: Burstable

I have changes the resource limit , will it work now
               resources:                   limits:                     cpu: 500m                     memory: 2000Mi                   requests:                     cpu: 100m                     memory: 500Mi

/merge possible

/merge possible


Django 1.9 support

I'm on my way of upgrading a project that uses django-hijack to Django 1.9. Is Django 1.9 already supported? Thanks in advance

Hi @vladir.
In general we already support Django 1.9. As you can see here, the tests pass for Python 2.7, 3.4, and 3.5.
So if you use one of the Python versions above you should be fine with upgrading. :+1:

Hi @walterrenner,
Thanks a lot for your quick response, I really appreciate that. I will be ok, I'm using Python 2.7 ;), and I will soon upgrade to Python3. Thanks again mate :)

you're welcome.


Publish 05/10/2022 3:30 PM PT

Docs Build status updates of commit ca89290:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Enable-Mailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Export-MailboxDiagnosticLogs.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-OrganizationConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

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


Implement RejectedExecutionException.

as always, just avoid linking errors.

Can one of the admins verify this patch?

Akka ... ActorSystem throws it

I believe @sjrd ment the cause parameter ;)

XD ... ok ...
just copy paste from:
https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/RejectedExecutionException.html#RejectedExecutionException(java.lang.Throwable)

Just don't forget pass it to the extends RuntimeException(message, cause).

argh... yep doing it!

done! Tnx!

That is all

please double check the style targeting your comment.

done

LGTM

Jenkins, test this please

Note: No merge at the moment because we're in the release process.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3052/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/3960/
Test FAILed.

fixed... sorry.. forgot to run scalastyle

This can now be rebased on top of master.

here you are, just to know can I expect a 6.10 release before scala days berlin?

@sjrd I think it might be sensible to roll a bugfix release pretty soon (end of May?). Quite some things lined up in 0.6.10 already. WDYT?

LGTM, Jenkins, test this please

@gzm0 I would aim for ~ June 4-7 period, one week before Scala Days Berlin.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3065/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/3977/
Test PASSed.


Postgresql vs Mysql

Proposed title of article
Postgresql vs Mysql
Introduction paragraph:
We will focus on the special features that have made Postgresql and Mysql remain relevant and widely used database management system. The two were developed slightly over two decades ago and have ranked among the best and most popular database systems. So exactly why have they stood the test of time? Lets find out!
Key takeaways:

What is Postgresql
What is Mysql
The key features of both
Conclusion.

References:
N/A
Templates to use as guides
N/A

sounds like a good topic - approved @amchilos01
if you haven't already please go through our published articles (via the search bar) to make sure this does not overlap with past works. Or which articles could be used as references 👍

👍


{"code":"UNABLE_TO_VERIFY_LEAF_SIGNATURE"}

I'm getting this error "UNABLE_TO_VERIFY_LEAF_SIGNATURE" and googled and tried process.env['NODE_TLS_REJECT_UNAUTHORIZED'] = '0'; and since this is a bad idea i thought of using ssl-root-cas module and added the below line in my code,
require('ssl-root-cas/latest').inject();
Even after adding this i get the same error.. Any reason why? I'm simply trying to post and retrieve data's to/from an end point on a node service code.

I'm still stuck with this issue, any help would be greatly appreciated.

Take a look at these two examples:

https://github.com/coolaj86/nodejs-self-signed-certificate-example
https://github.com/coolaj86/nodejs-ssl-example

If your company or organization uses their own self-signed root CA you'll need to add that using addFile('/certs/our-root-ca.pem').


Implement createTable command

Closes #26
This module is awesome! Since we already have addColumn and deleteColumn, mirroring deleteTable with createTable seems to make sense.
This command is designed to accept row counts, column counts and cell attributes. For common use case, creating a m x n table from popover or user input can be simply implemented by calling createTable(m, n), with text selection inside first cell as default.

Hi @bradleyayers any idea to implement this, I think this should be quickly implemented, :disappointed:

@doodlewind there're a bunch of handful methods related to tables in prosemirror-utils including  createTable, feel free to use those. I wasn't sure I want to copy/move it here as I wanted to keep prosemirror-tables lightweight.


setting default-user and default-uid has no effect

First of all: awework work! saved me a lot of time (i've installed Arch on WSL manually before, that was quite some work, this time it was a breeze thank you)...
one small problem I ran into: I'm not able to set the default user. I've tried with 'Arch.exe config --default-user luke' and  'Arch.exe config --default-uid 1000' but when I start Arch.exe afterwards I'm always root.
'Arch.exe get --default-uid' returns 1000 as expected.
As root I can sudo into luke, and running the id command shows i'm uid 1000.

This can be alleviated without a restart by simply restarting the LxssManager service.
From a privileged command prompt:
sc stop LxssManager
sc start LxssManager

I tried Arch.exe config --default-user myuser and the command hanged, even after reboot. Then I used Arch.exe config --default-uid 1000 and it succeeded.
In case anybody faces  the same item, try --default-uid.

If still persist u can try this:
.\Arch.exe config --default-user "youruser"

when i run the command Arch.exe config --default-user {username}  it gives me this ('Arch.exe' is not recognized as an internal or external command, operable program or batch file.) I've tried just Arch by itself and it doesn't work either.

I'm using Windows 11 here, and when following the instructions and typing exit, the terminal window closes completely.
So I opened up Windows Terminal again (which defaults to powershell) and went to the folder where i installed ArchWSL.
I couldn't run the command from powershell (even with adding .\ infront).
After that i tried running the command from CMD and it worked like a charm.

If still persist u can try this: .\Arch.exe config --default-user "youruser"

A bit curious, what exactly does this config command do in the WSL instance (say what configuration file it updates, etc.) to make the changes take effect?

If still persist u can try this: .\Arch.exe config --default-user "youruser"

worked well bro, thanks


Why bright cyan has different color?

Hello,
It looks like all colors except black and white use the same value for both bold/non-bold colors. Except cyan.
Why do bright cyan has a different color? For instance, color14 is set to nord7 instead of nord8.

There is not other way to include almost all colors of Nord. The palette is limited to 16 colors only and using the same colors for the bright variations would completely exclude nord7 next to nord10. If you'd like to have the same color for the normal and bright palette color you're free to modify the file to fit your needs, but I had to define the initial layout and decided to implement it the way it is now.


Template Transform ignored/lost?

Hello friends!
One thing that came up in the workshop today - we're setting a template transform, but it's seemingly dropped from the resulting artifact. I probably did something wrong, but here's the code
public class BrelandmEuDevConDemoLambdaWebsiteStack extends Stack {

    public BrelandmEuDevConDemoLambdaWebsiteStack(App parent, String name) throws IOException{
        super(parent, name);
        String swaggerPath = System.getenv("SWAGGER_PATH");

        String swagger = new String(Files.readAllBytes(Paths.get(swaggerPath)), StandardCharsets.UTF_8);
        ServerlessWebappProps serverlessProps = ServerlessWebappProps
            .builder()
            .withHostedZoneName("brelandm.not-used-for-prod.workshops.bones.a2z.com")
            .withStage("personal")
            .withHandler("com.amazon.brelandmeudevcondemolambda.activity.BrelandmEuDevConDemoLambdaEntryPoint::handleRequest")
            .withSwagger(swagger)
            .build();

        // We rename these becuase the Swagger that Coral2Swagger generates does not know the generated CDK Name.
        // In the future, the CDK Constructs will have better first class support for imported swagger :)
        // The CDK generates names - these were pre-computed. If you change where the serverless function is attached, this will break :/
        // Keep an eye out for an announcement for a huge imprvement to this soon
        this.renameLogical("TheAppLambda981F0DA4", "LambdaFunction");
        this.renameLogical("TheAppAPIGatewayExecutionRoleCB4E23C4", "APIGatewayExecutionRole");

        ServerlessWebapp serverless = new ServerlessWebapp(this, "TheApp", serverlessProps);
        this.getTemplateOptions().setTransform("AWS::Serverless-2016-10-31");

    }
}

The line being the last one - It just doesn't seem to take.
Am I missing something? Is it legal to attach this at the Stack (I thought so...)

@mindstorms6 is this still relevant?

I recall this not being an issue anymore, but haven't verified. Will check when back in office - I don't mind closing this - I can re-open if it's a problem.


Also import ScopeStorage from Base with Julia >= 1.11

While migrating from ContextVariablesX.jl, we needed an "empty scope" in place of empty ContextSnapshot{T}. To do that in a way that is works both before and after Julia 1.11, we needed this hack:
const _EMPTY_SCOPE = ScopedValues.Scope(
    isdefined(ScopedValues, :ScopeStorage) ?
        ScopedValues.ScopeStorage() :
        Base.ScopedValues.ScopeStorage()
)

Since ScopeStorage is not imported to the package from Base in 1.11.
Could we please import it?:)

Why do you need an empty Scope? Scope is not something user-facing and I would like to examine the pattern first,
before we commit to supporting something.

Hey Valentin, sure -- we have a TaskGroup construct that runs "TaskQueueEntries" (which are similar to Base.Tasks) according to their priority, and we store the scope in each of these TaskQueueEntries like this:
task_scope = @something(ScopedValues.current_scope(), _EMPTY_SCOPE)

When running our task, we reconstruct the scope using enter_scope (and its variant for Julia 1.11+).

Enter_scope is not public and we need to be careful with the semantics here. Long-term I want to be able to support compiler optimization over scoped values and letting the user manipulate the scope directly would break those.
We can discuss snapshotting (x-ref https://github.com/vchuravy/ScopedValues.jl/pull/6), but I am not comfortable with user packages directly manipulating the internals.

Gotcha, thanks, too bad there seems to be no way to implement snapshotting in userspace. Any time estimate for the snapshotting feature to be finalized? Once done, would it be possible to snapshot the current_scope()? Any way I could help?

@Drvi I think the best thing would be to help with #6


Bug: consumption of connector source will hang forever if encounters an error

Describe the bug
If the connector source throws an error up to the source executor, the consumption of the source will stop forever:
https://github.com/risingwavelabs/risingwave/blob/6f39f43892b29aa4be798d9c29ab48e5294071f4/src/stream/src/executor/source/reader.rs#L61-L62

2023-01-04T11:56:46.373988Z  INFO risingwave_connector::source::kafka::source::reader:135: kafka message error: Err(KafkaError (Partition EOF: 11))
2023-01-04T11:56:46.375555Z  INFO risingwave_connector::source::kafka::source::reader:135: kafka message error: Err(KafkaError (Partition EOF: 11))
2023-01-04T11:56:46.376565Z ERROR risingwave_stream::executor::source::reader:61: hang up stream reader due to polling error: internal error: Partition EOF: 11
2023-01-04T11:56:46.377123Z ERROR risingwave_stream::executor::source::reader:61: hang up stream reader due to polling error: internal error: Partition EOF: 11

But the barrier messages can still pass to downstream executors:
https://github.com/risingwavelabs/risingwave/blob/98ae6ceb4ad6bbbcb849c61c86a478a27083e94a/src/stream/src/executor/source/reader.rs#L90-L95
I am not sure whether this problem is a by-design feature.
To Reproduce
Manually construct an error in the KafkaSplitReader and propagate it to the upper layer.
diff --git a/src/connector/src/source/kafka/source/reader.rs b/src/connector/src/source/kafka/source/reader.rs
index ab993dfde..e24706f76 100644
--- a/src/connector/src/source/kafka/source/reader.rs
+++ b/src/connector/src/source/kafka/source/reader.rs
@@ -21,6 +21,7 @@ use futures::StreamExt;
 use futures_async_stream::try_stream;
 use rdkafka::config::RDKafkaLogLevel;
 use rdkafka::consumer::{Consumer, DefaultConsumerContext, StreamConsumer};
+use rdkafka::error::KafkaError;
 use rdkafka::{ClientConfig, Message, Offset, TopicPartitionList};

 use crate::source::base::{SourceMessage, SplitReader, MAX_CHUNK_SIZE};
@@ -129,6 +130,8 @@ impl KafkaSplitReader {
         #[for_await]
         'for_outer_loop: for msgs in self.consumer.stream().ready_chunks(MAX_CHUNK_SIZE) {
             for msg in msgs {
+                let fake_msg = Err(KafkaError::PartitionEOF(11));
+                let my_msg = fake_msg?;
                 let msg = msg?;
                 let cur_offset = msg.offset();
                 bytes_current_second += match &msg.payload() {

Then start the cluster with the full config and run the tpch-bench script to ingest data.
Expected behavior
IIUC, when executors encounter an error in other scenarios, the error will report to the Meta via the barrier collection mechanism (https://github.com/risingwavelabs/risingwave/issues/6319). Then Meta will enter the recovery process to recover the whole streaming graph.
But for the scenario of connector source failure, the upstream system may become available after a while or the failure is unrecoverable indeed. So it may be a waste to let Meta recover the cluster blindly:
https://github.com/risingwavelabs/risingwave/blob/1ba6981b2a42abcb0346086ccdb0b0726acff9fe/src/meta/src/barrier/mod.rs#L772-L780
Candidate solutions:

Employ a bounded retry strategy for connector sources
When a connector source encounters an error, we will try our best to recover the consumer client. For example, we can drop the current consumer and create a new one to try to resume consumption. If we fail to recover the consumer, we can choose to hang up the connector source stream and prompt users to drop the source and troubleshoot the upstream system.

Hang up the connector source stream forever as the current implementation did and prompt users to drop the source and troubleshoot the upstream system. For example, we can prompt an error to users when they query the downstream MVs of the broken source.

Additional context
No response

so we expect the connector itself to retry in the case of temporary service unavailable as much as possible.

Indeed, I was not sure where we might find this issue. We should indeed report this error every time the input chunk is an Err

internal error: Partition EOF: 11

I believe that in this case, it's not an unrecoverable error. Is this accurate? @tabVersion

It also seems that we need to classify errors into recoverable and unrecoverable errors.

Employ a bounded retry strategy for connector sources
When a connector source encounters an error, we will try our best to recover the consumer client. For example, we can drop the current consumer and create a new one to try to resume consumption. If we fail to recover the consumer, we can choose to hang up the connector source stream and prompt users to drop the source and troubleshoot the upstream system.

+1 for this. I think we should bounded exponential retry (default: up to few hours? - to give the user/SRE time to respond, perhaps restart the source) and report the user error in the meantime.
If we believe the error is recoverable, I do not think it is necessary to suspend the job immediately.

But the barrier messages can still pass to downstream executors:

I don't think this should be the behaviour now.
In impl StreamConsumer for DispatchExecutor, the error from StreamExecutorResult<Message> will be propagated into BarrierStream, and Actor::run_consumer will terminate, triggering context.lock_barrier_manager().notify_failure(actor_id, err);
I believe that select_with_strategy will still propagate errors if they are available while a barrier has not yet arrived.
We should check that the above scenario indeed triggers this behaviour.

After discussion with @tabVersion , we are in agreement on the following:

For the connector side, we expect both recoverable and unrecoverable errors. We will not make any effort to categorize the errors into these two categories. Instead, we will attempt to handle both scenarios by an exponential backoff up to 1 hour (by default). This will be implemented as a wrapper around the connectors. Once the max timeout/max retries are reached, we will emit the error to stream side.
The behaviour for stream will currently be to restart from checkpoint (the current behaviour is retry every 10 seconds and infinite...see: https://github.com/risingwavelabs/risingwave/pull/6531), but we should eventually implement suspending the MV for this type of error. This means that recoverable/irrecoverable error distinction is made on the stream side.


geoocation not returning anything when device has no internet connection

this.geolocation.getCurrentPosition(this.options).then((resp) => {
this above method doesn't return any thing when there is no internet connection in old redmi and lenovo mobiles, but when internet if on it returns the lat and long.
this issue arises on
"cordova-plugin-geolocation": "^4.1.0",

"@ionic-native/geolocation": "^5.32.0",

import { Geolocation } from '@ionic-native/geolocation/ngx';
but the same isssue is not happending in old versions of plugin
"cordova-plugin-geolocation": "^4.0.1",

"@ionic-native/geolocation": "^4.18.0",

import { Geolocation } from '@ionic-native/geolocation';

If the device doesn't have an active GPS satellite fix, it can take a significant amount of time (>= 15 mins sometimes) to obtain a GPS location from the satellites.
A-GPS features, if supported & enabled, solves that issue, (using wifi, bluetooth, cellular towers, internet etc). If you have older phones, it's possible that they don't have complete A-GPS features implemented and disabling internet forces it to solely rely on GPS satellites.
Also note that Cordova doesn't maintain an actual geolocation implementation for Android. The plugin is purely for managing the required permissions and android project configuration. The geolocation implementation is provided by the system webview itself, so any bugs with the webview geolocation API needs to be brought to the Chromium team. (But in this case, I think on those devices, when internet is disabled, it solely relies on GPS satellites which is accurate, but extremely slow)
I also have a bigger spiel on location accuracy / timeout reasons that may be relevant to you: https://gist.github.com/breautek/d6231fa33d6942c269296546892afb5e
I'm closing this issue as I don't believe this is a bug with cordova-plugin-geolocation. If you can be sure you're in a healthy location spot (e.g. other apps can obtain GPS fine in the same device configuration) and still have problems, I'd recommend trying to isolate the issue by using a simple cordova reproduction app without using the ionic framework. With the sample reproduction app that contains only cordova packages we can provide better insight.
Kind regards,
Norman


Pre-updates Failing for Genshin/Honkai past few versions.

Recent Honkai log provided below, I usually have to completely restart the update or use an Hoyo official launcher to get it to properly install.

System.NullReferenceException: Oops, the launcher cannot finalize the installation but don't worry, your game has been totally updated.
Please report this issue to our GitHub here: https://github.com/neon-nyan/CollapseLauncher/issues/new or come back to the launcher and make sure to use Repair Game in Game Settings button later.
Throw: System.NullReferenceException: Object reference not set to an instance of an object.
at Hi3Helper.Http.Http.InitializeMultiSession() in C:\myGit\Collapse-Legacy\Hi3Helper.Http\Class\Session\SessionManager.cs:line 188
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Hi3Helper.Http.Http.Download(String URL, String Output, Byte ConnectionSessions, Boolean Overwrite, CancellationToken ThreadToken) in C:\myGit\Collapse-Legacy\Hi3Helper.Http\HttpMulti.cs:line 47
at CollapseLauncher.InstallManagement.StartDownloadAsync() in C:\myGit\Collapse-Legacy\CollapseLauncher\Classes\InstallManagement\InstallManagement.cs:line 195
at CollapseLauncher.Pages.HomePage.UpdateGameDialog(Object sender, RoutedEventArgs e) in C:\myGit\Collapse-Legacy\CollapseLauncher\XAMLs\MainApp\Pages\HomePage.xaml.cs:line 1406
---> System.NullReferenceException: Object reference not set to an instance of an object.
at Hi3Helper.Http.Http.InitializeMultiSession() in C:\myGit\Collapse-Legacy\Hi3Helper.Http\Class\Session\SessionManager.cs:line 188
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Hi3Helper.Http.Http.Download(String URL, String Output, Byte ConnectionSessions, Boolean Overwrite, CancellationToken ThreadToken) in C:\myGit\Collapse-Legacy\Hi3Helper.Http\HttpMulti.cs:line 47
at CollapseLauncher.InstallManagement.StartDownloadAsync() in C:\myGit\Collapse-Legacy\CollapseLauncher\Classes\InstallManagement\InstallManagement.cs:line 195
at CollapseLauncher.Pages.HomePage.UpdateGameDialog(Object sender, RoutedEventArgs e) in C:\myGit\Collapse-Legacy\CollapseLauncher\XAMLs\MainApp\Pages\HomePage.xaml.cs:line 1406
--- End of inner exception stack trace ---

Apologizes for late update but we are aware of the issue and neon is currently working on a fix.
Tracking issue over at #96

Referencing issue #96, this is now being closed as 1.69.7 fixes this issue!
Thank you for the report!


Stop producing Microsoft.VisualStudio.Web.CodeGeneration.Msbuild

These binaries are shipped in the .Tools package. We don't need the .MSbuild package.

:bell:


Discovery Enable Error

Is this a bug or a feature request?
What did you expect?
What happened?
What version are your using?
How can your issue be reproduced?
Could you share your log output?

When I activate the discovery enable, the docker console pulls the following error, every second.
postgresql_as_1  | ERROR:  division by zero postgresql_as_1  | STATEMENT:   postgresql_as_1  | 			select postgresql_as_1  | 				g.* postgresql_as_1  | 			from gateway g postgresql_as_1  | 			inner join network_server ns postgresql_as_1  | 				on ns.id = g.network_server_id postgresql_as_1  | 			where postgresql_as_1  | 				ns.gateway_discovery_enabled = true postgresql_as_1  | 				and g.ping = true postgresql_as_1  | 				and (g.last_ping_sent_at is null or g.last_ping_sent_at <= (now() - (interval '24 hours' / ns.gateway_discovery_interval))) postgresql_as_1  | 			order by last_ping_sent_at postgresql_as_1  | 			limit 1 postgresql_as_1  | 			for update appserver_1      | time="2018-03-27T15:52:37Z" level=error msg="send gateway ping error: get gateway for ping error: select error: pq: division by zero"

Thanks, that should have been raised a validation error when configuring. For now, please set the interval value at something larger than 0 :-)


Train fail (can't do any training at all)

Here is the problem:

This warning repeats a lot and eats all the memory, than container fails due allocatin memory (looks like memleak or smth).
How do i fix it?

This warning is thrown when the program reads training data and generally does not affect training.


Documentation for V2

The V2 documentation is gone. We still have many projects using V2. Are the V2 docs accessible somewhere?

Any update on when documentation will return?

here is a mirror i hosted for test several months ago, but the feature list is broken. You may need see find your feature list in v3 documentation.
https://polyfill.lazyguy.cn/v2/docs/api

Where are the restored v2 docs hosted?


chore: update status badges in README [skip ci]

Description
Some badges are no longer relevant and need removal:

Bower version: it's always the same as for npm so we can remove it and only show npm version,
Build status: we have moved away from Travis and do not build on push to master anymore,
Gitter: we stopped using Gitter and now use Discord (added the corresponding badge),
Coveralls: related to the above, we no longer upload code coverage to Coveralls service,
Directory rating: in this case the badge is broken and IMO one Directory badge is enough.

Type of change

[x] Internal change

Good point about the V14 version but we don't have a dedicated tag for it, so for now let's show the latest one.


Option for generators.toINI to preserve order

Describe the bug
I use generators.toINI and my source data has an intentional order. It would be helpful if the result has also this order. An option would be fine but would it harm anyone if it would be default behavior?
To Reproduce
Steps to reproduce the behavior:

$ echo 'lib.generators.toINI {} { general = { user="test"; password="secret"; host="localhost"; }; }' | nix repl '<nixpkgs>'

"[general]\nhost=localhost\npassword=secret\nuser=test\n"
(the order seems alphabetical)
Expected behavior
$ echo 'lib.generators.toINI { preserveOrder = true; } { general = { user="test"; password="secret"; host="localhost"; }; }' | nix repl '<nixpkgs>'
"[general]user=test\npassword=secret\nhost=localhost\n"
Would that be possible somehow or does Nix evaluate the data as unordered set?
Metadata

system: "x86_64-linux"
host os: Linux 4.19.107, NixOS, 19.09.2196.00115f2f9c7 (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.3
channels(davidak): ""
channels(root): "nixos-19.09.2196.00115f2f9c7, nixos-hardware, nixos-unstable-20.09pre215702.1459b34afa9"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: lib.generators.toINI
# a list of nixos modules affected by the problem
module:

While we're putting requests in... https://github.com/NixOS/nixpkgs/issues/81986

This is not possible as Nix doesn't maintain the order of attribute sets internally (and it would be very weird if it did, as { a = 0; b = 1; } wouldn't be the same as { b = 1; a = 0; } anymore).
@aanderse I guess you meant to link to https://github.com/NixOS/nixpkgs/issues/82205, which has since been implemented :)

And indeed, attribute sets are defined to be alphabetically sorted (which also allows some optimizations).

Ha! Yeah looks like a copy+paste gone bad. As always thank you for your wonderful work @Infinisil!


Removing a large vote that was placed in previous epoch could result in negative votedTotal

@Luivatra has this been resolved?


Update README.md

Rename

Deploy preview for wanikani-knowledgebase processing.
Building with commit b89eb977673d9902f7a23b20b0f18cb0dd8c3510
https://app.netlify.com/sites/wanikani-knowledgebase/deploys/5f72579a1e07740008d812a0


Sorting of 4K torrents

Expected Behavior
I have a 4K HDR television so I'm often searching for 4K content. I'd like to be able to sort the results so that 4K content appears first.

Current Behavior
Elementum config has the sort options, but it only lists "1080p, 720p, 480p" which can then be reordered to any order.. But there is no 4K selection! 4K videos are not sorted at all, they appear in random order in torrent listing, between lower resolution videos.
I'm not sure if this happens on Android only. Android is special in that Kodi always runs in 1080p, so perhaps Elementum thinks there are no higher resolutions available? But in reality 4K works even if Kodi GUI is in 1080p.

Possible Solution
Add 4K into "1080p, 720p, 480p", or perhaps just change the config item to "highest resolution first"?

Your Environment

Version used:

Latest elementum

Environment name and version:

Kodi 19.1

Operating System and version:

Android 9, Sony Bravia TV

Link to Kodi debug log:

I'm always getting the 4k results first by setting "Order: Quality" and "Sort: 1080p, 720p, 480p", also check in Burst settings - "Resolution: 4k". No problem on PC (Don't think it matter).

@HobloBoblo There is no separate option for 4k, because it will make too much variant of sorts in settings. Kodi does not allows simple way of managing such things.

I think just ascending and descending would be enough.


Added double_post function

Kept send_function

Build failed, please fix the style issues.

What happened to the send_to_story function?

It's still there: https://github.com/viggibear/pysnap/blob/patch-4/pysnap/init.py#L378


 This is surprising, since it was meant to be deployed in exactly this way.
-----> Python app detected
-----> Installing python-2.7.9
     $ pip install -r requirements.txt
       Collecting sasl (from -r requirements.txt (line 1))
         Downloading sasl-0.2.1.tar.gz
       Collecting psycopg2 (from -r requirements.txt (line 2))
         Downloading psycopg2-2.6.1.tar.gz (371kB)
       Obtaining airflow[postgres,crypto] from git+git://github.com/airbnb/airflow@ba35124d75a3ad23266c324d729e80d5267e161f#egg=airflow[postgres,crypto] (from -r requirements.txt (line 3))
         Cloning git://github.com/airbnb/airflow (to ba35124d75a3ad23266c324d729e80d5267e161f) to ./.heroku/src/airflow
         Could not find a tag or branch 'ba35124d75a3ad23266c324d729e80d5267e161f', assuming commit.
       Collecting rauth (from -r requirements.txt (line 4))
         Downloading rauth-0.7.2.tar.gz
       Collecting flask-sslify (from -r requirements.txt (line 5))
         Downloading Flask-SSLify-0.1.5.tar.gz
       Collecting six (from sasl->-r requirements.txt (line 1))
         Downloading six-1.10.0-py2.py3-none-any.whl
       Collecting alembic<0.9,>=0.8.0 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading alembic-0.8.6.tar.gz (961kB)
       Collecting celery<4.0,>=3.1.17 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading celery-3.1.23-py2.py3-none-any.whl (520kB)
       Collecting chartkick<0.5,>=0.4.2 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading chartkick-0.4.2.tar.gz
       Collecting dill<0.3,>=0.2.2 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading dill-0.2.5.tgz (60kB)
       Collecting flask<0.11,>=0.10.1 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Flask-0.10.1.tar.gz (544kB)
       Collecting flask-admin==1.2.0 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Flask-Admin-1.2.0.tar.gz (790kB)
       Collecting flask-cache<0.14,>=0.13.1 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Flask-Cache-0.13.1.tar.gz (45kB)
       Collecting flask-login<0.3,>=0.2.11 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Flask-Login-0.2.11.tar.gz
       Collecting flower<0.8,>=0.7.3 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading flower-0.7.3.tar.gz (2.5MB)
       Collecting future<0.16,>=0.15.0 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading future-0.15.2.tar.gz (1.6MB)
       Collecting gunicorn<20.0,>=19.3.0 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading gunicorn-19.4.5-py2.py3-none-any.whl (112kB)
       Collecting jinja2<3.0,>=2.7.3 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Jinja2-2.8-py2.py3-none-any.whl (263kB)
       Collecting markdown<3.0,>=2.5.2 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Markdown-2.6.6.zip (412kB)
       Collecting pandas<1.0.0,>=0.15.2 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading pandas-0.18.0.tar.gz (7.1MB)
       Collecting pygments<3.0,>=2.0.1 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Pygments-2.1.3-py2.py3-none-any.whl (755kB)
       Collecting python-dateutil<3,>=2.3 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading python_dateutil-2.5.3-py2.py3-none-any.whl (201kB)
       Collecting requests<3,>=2.5.1 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading requests-2.9.1-py2.py3-none-any.whl (501kB)
       Collecting setproctitle<2,>=1.1.8 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading setproctitle-1.1.9.tar.gz
       Collecting sqlalchemy<0.10,>=0.9.8 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading SQLAlchemy-0.9.10.tar.gz (4.3MB)
       Collecting statsd<4.0,>=3.0.1 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading statsd-3.2.1-py2.py3-none-any.whl
       Collecting thrift<0.10,>=0.9.2 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading thrift-0.9.3.tar.gz
       Collecting cryptography>=0.9.3 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading cryptography-1.3.1.tar.gz (383kB)
       Collecting Mako (from alembic<0.9,>=0.8.0->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Mako-1.0.4.tar.gz (574kB)
       Collecting python-editor>=0.3 (from alembic<0.9,>=0.8.0->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading python-editor-1.0.tar.gz
       Collecting kombu<3.1,>=3.0.34 (from celery<4.0,>=3.1.17->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading kombu-3.0.35-py2.py3-none-any.whl (240kB)
       Collecting pytz>dev (from celery<4.0,>=3.1.17->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading pytz-2016.4-py2.py3-none-any.whl (480kB)
       Collecting billiard<3.4,>=<IP_ADDRESS> (from celery<4.0,>=3.1.17->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading billiard-<IP_ADDRESS>.tar.gz (151kB)
       Collecting Werkzeug>=0.7 (from flask<0.11,>=0.10.1->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Werkzeug-0.11.9-py2.py3-none-any.whl (306kB)
       Collecting itsdangerous>=0.21 (from flask<0.11,>=0.10.1->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading itsdangerous-0.24.tar.gz (46kB)
       Collecting wtforms (from flask-admin==1.2.0->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading WTForms-2.1.zip (553kB)
       Collecting tornado>=3.2.0 (from flower<0.8,>=0.7.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading tornado-4.3.tar.gz (450kB)
       Collecting MarkupSafe (from jinja2<3.0,>=2.7.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading MarkupSafe-0.23.tar.gz
       Collecting numpy>=1.7.0 (from pandas<1.0.0,>=0.15.2->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading numpy-1.11.0-cp27-cp27m-manylinux1_x86_64.whl (15.3MB)
       Collecting idna>=2.0 (from cryptography>=0.9.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading idna-2.1-py2.py3-none-any.whl (54kB)
       Collecting pyasn1>=0.1.8 (from cryptography>=0.9.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading pyasn1-0.1.9-py2.py3-none-any.whl
       Collecting enum34 (from cryptography>=0.9.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading enum34-1.1.4-py2.py3-none-any.whl (61kB)
       Collecting ipaddress (from cryptography>=0.9.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading ipaddress-1.0.16-py27-none-any.whl
       Collecting cffi>=1.4.1 (from cryptography>=0.9.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading cffi-1.6.0.tar.gz (397kB)
       Collecting anyjson>=0.3.3 (from kombu<3.1,>=3.0.34->celery<4.0,>=3.1.17->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading anyjson-0.3.3.tar.gz
       Collecting amqp<2.0,>=1.4.9 (from kombu<3.1,>=3.0.34->celery<4.0,>=3.1.17->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading amqp-1.4.9-py2.py3-none-any.whl (51kB)
       Collecting backports.ssl-match-hostname (from tornado>=3.2.0->flower<0.8,>=0.7.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading backports.ssl_match_hostname-<IP_ADDRESS>.tar.gz
       Collecting singledispatch (from tornado>=3.2.0->flower<0.8,>=0.7.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading singledispatch-<IP_ADDRESS>-py2.py3-none-any.whl
       Collecting certifi (from tornado>=3.2.0->flower<0.8,>=0.7.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading certifi-2016.2.28-py2.py3-none-any.whl (366kB)
       Collecting backports-abc>=0.4 (from tornado>=3.2.0->flower<0.8,>=0.7.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading backports_abc-0.4-py2.py3-none-any.whl
       Collecting pycparser (from cffi>=1.4.1->cryptography>=0.9.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading pycparser-2.14.tar.gz (223kB)
       Installing collected packages: six, sasl, psycopg2, sqlalchemy, MarkupSafe, Mako, python-editor, alembic, anyjson, amqp, kombu, pytz, billiard, celery, chartkick, dill, Werkzeug, jinja2, itsdangerous, flask, wtforms, flask-admin, flask-cache, flask-login, backports.ssl-match-hostname, singledispatch, certifi, backports-abc, tornado, flower, future, gunicorn, markdown, python-dateutil, numpy, pandas, pygments, requests, setproctitle, statsd, thrift, idna, pyasn1, enum34, ipaddress, pycparser, cffi, cryptography, airflow, rauth, flask-sslify
         Running setup.py install for sasl: started
           Running setup.py install for sasl: finished with status 'error'
           Complete output from command /app/.heroku/python/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-1eO0Xp/sasl/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-eDjHFH-record/install-record.txt --single-version-externally-managed --compile:
           running install
           running build
           running build_py
           creating build
           creating build/lib.linux-x86_64-2.7
           creating build/lib.linux-x86_64-2.7/sasl
           copying sasl/__init__.py -> build/lib.linux-x86_64-2.7/sasl
           running egg_info
           writing requirements to sasl.egg-info/requires.txt
           writing sasl.egg-info/PKG-INFO
           writing top-level names to sasl.egg-info/top_level.txt
           writing dependency_links to sasl.egg-info/dependency_links.txt
           warning: manifest_maker: standard file '-c' not found

           reading manifest file 'sasl.egg-info/SOURCES.txt'
           reading manifest template 'MANIFEST.in'
           writing manifest file 'sasl.egg-info/SOURCES.txt'
           copying sasl/saslwrapper.cpp -> build/lib.linux-x86_64-2.7/sasl
           copying sasl/saslwrapper.h -> build/lib.linux-x86_64-2.7/sasl
           copying sasl/saslwrapper.pyx -> build/lib.linux-x86_64-2.7/sasl
           running build_ext
           building 'sasl.saslwrapper' extension
           creating build/temp.linux-x86_64-2.7
           creating build/temp.linux-x86_64-2.7/sasl
           gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -Isasl -I/app/.heroku/python/include/python2.7 -c sasl/saslwrapper.cpp -o build/temp.linux-x86_64-2.7/sasl/saslwrapper.o
           cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default]
           In file included from sasl/saslwrapper.cpp:254:0:
           sasl/saslwrapper.h:22:23: fatal error: sasl/sasl.h: No such file or directory
            #include <sasl/sasl.h>
                                  ^
           compilation terminated.
           error: command 'gcc' failed with exit status 1

           ----------------------------------------
       Command "/app/.heroku/python/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-1eO0Xp/sasl/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-eDjHFH-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-1eO0Xp/sasl/
 !     Push rejected, failed to compile Python app

This is caused when you try to deploy the app the typical way (directly from a GitHub repo) instead of via heroku docker:release.


2.2 UDAF java

After compiling branch-2.2, it still can't be adjusted. There are three functions, one can and two can't work. The error information is as follows:

@stdpain PTAL


url not put to browser link after running autotests on real device

hello everyone.
I have issue: i run my autotests on iOS emulators - via appium + Xcode - works fine.
But when i connect a real device - I see that WebAgent works, open safari browser and nothing in the end.
Error:
E       selenium.common.exceptions.WebDriverException: Message: cannot create session safari-MOBILE on any hosts after 1 attempt(s), last host error was: An unknown server-side error occurred while processing the command. Original error: operation timed out
PS. "Trust" was select in Setting-General, + Safari -> Advanced: JavaScript, Web Inspectors are enabled
Can you help me how to fix it

Have you tried to use solutions like https://www.browsersync.io or https://ngrok.com ? They helps me a lot with this type of tests.

Please use StackOverflow for questions/help, where a wider community will be able to help you. We reserve the issues tracker for issues only.
Thank you!


Gate Examination Analysis

Pull Request for ML-Crate 💡
Issue Title : Gate Examination Analysis

Info about the related issue (Aim of the project) : Performed EDA on the dataset

Name: Debjit Pal

GitHub ID: debjitpal5040

Idenitfy yourself:

[x] JWOC Participant ☃

Closes: #158
Describe the add-ons or changes you've made 📃
Performed various EDA to gather useful information from the dataset
Type of change ☑
What sort of change have you made:

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested? ⚙
Describe how it has been tested
Describe how have you verified the changes made
Checklist: ☑

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

Your PR is approved and merged @debjitpal5040


Rop Publish (bgeo.sc / vdb / abc)

In GitLab by @kekefreedog on Mar 1, 2023, 09:46

From Olivier Osotimehin

Need
Add a Rop in Houdini to be able to publish :

bgeo.sc
vdb
abc

Comment
pipelined path and versioning for caches

generative fx : like smoke, fire, things that comme 100% from houdini
specific asset fx : hair, cloth of specific character/asset

For generative fx the artist would be able to specify a custom name
For specific asset artist would be able to choose among the existing asset in the database of project. Fe : choosing the name of a character to export the hair (which help identify which hair is which if there are multiple character)

copy .hip file for each caches into a safe place

project\seq\shot\publish\fx\customName\version\cacheName.abc project\seq\shot\publish\fx\assetName\version\cacheName.abc
Dependency graph for caches

Multiple caches can be submitted and the caches dependent on other will wait til the one they need are complete

Ynput Pr for Farmcahing in houdini:  https://github.com/ynput/OpenPype/pull/4903
and Pr to use standalone render : https://github.com/ynput/OpenPype/pull/5420

Dependency cache system Test
Dependency between instance to render in Houdini.pdf


Removing private endpoints from Online RI

For now this is a proposal to remove the private endpoints from the -Online RI. We still of course have them in the -Connected RI.
Reasons:

Faster deployment
Cleaner resource groups (no DNS zones, PE, NICs)
Cleaner Terraform templates
Easier debugging since you can directly connect e.g. to CosmosDB without IP whitelisting

So overall: just easier learning curve again.
Downside: Does not appear to be as secure as before. But then again, we were actually not enforcing private connections-only to Key Vault (only to Cosmos and Event Hub). So I would argue the easier learning outweighs this.
Thoughts? @hjscherer @heoelri @nielsams @msimecek

Faster deployment

😍😍

The only/main reason why this was implemented in the first place is that this was brought up at first in every single review/conversation/.. am open to drop it out of the online version. Or to keep it. Don't have a strong preference here.

The only/main reason why this was implemented in the first place is that this was brought up at first in every single review/conversation/.. am open to drop it out of the online version. Or to keep it. Don't have a strong preference here.

yep. For anybody security-conscious, we would point them to -Connected now anyway

I think we'd Threat Modeling in our backlog - maybe we should do that exercise first and decide then.

I'd also say to do that only on -Connected. Even with the Private Endpoints here we are plenty of gaps as we leave Key Vault etc open to the public

Talked to @CalCof and he also agreed it's ok to remove the PEs from -online
@heoelri would you mind giving this a review? :) thanks!

Talked to @CalCof Callum Coffin FTE and he also agreed it's ok to remove the PEs from -online
@heoelri Heyko Oelrichs FTE would you mind giving this a review? :) thanks!

Yes, for sure. When not using PE - does it make sense to consider using vNet-integration and per-Service firewall settings to lock down access to specific services then? First example that comes to my mind are the Storage Accounts used. Key Vault needs to be accessed from the hosted agents, ACR as well. And afaik is Azure DevOps (Microsoft-hosted Agents) not in the list of "Trusted Service"(s).

The only services for which we could do that are Event Hub and the private storage account. For the others we would need special handling for the build agents and for cosmos it's not even reasonably possible with service endpoints.
Hence I would opt to not use network restrictions at all here

The only services for which we could do that are Event Hub and the private storage account. For the others we would need special handling for the build agents and for cosmos it's not even reasonably possible with service endpoints. Hence I would opt to not use network restrictions at all here

Yeah, and even for the rest is the benefit is fairly limited - it prevents access from unknown/unallowed sources, but it doesn't prevent data exfiltration etc.


setup terraform dev infrastructure

What is this PR trying to achieve?
We now have dev infrastructure.
No more deleting load balancers! Now more grey hair on adding S3 buckets!
There is probably more we can pull out to minimise the footprint of the stack, but this will do (our costs are so low anyway).
What does it look like?
😇

As a point - this is a movement towards being able to redirect the blog.


Extension activation failed, run the 'Developer: Toggle Developer Tools' command for more information.

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

VS Code Version:
OS Version:

Steps to Reproduce:

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!


Abstract Render Collector: Preserve instance id when replacing with new instance

Changelog Description
The abstract render collector converts a Render Instance and adds it to the publishing context, but for After Effects and Fusion these "replaced" existing instances (pyblish.api.Instance). However, by nature of removing the original instance and adding a new one this basically meant that now the new instance would not inherit the original instance's id and thus any logs generated on the original instance being replaced would not show in the publisher UI for the new instance.
This PR changes it so that it doesn't replace the original instance at all - but just updates the source instance with the data from the render instance's data.
Additional info
This implements a different fix as was implemented in this PR https://github.com/ynput/ayon-core/pull/217
Testing notes:

[ ] Submitting renders from Fusion should still work as expected
[ ] Submitting renders from After Effects should still work as expected.

I am missing app_version in Fusion Deadline submission, investigating when it disappeared


On double tap ,  image is not centered and zoomed, bottom part of image is zoomed instead? Is there any event to control double tap?

@AkashSalunkhe111  did you find any solution?


AV option

I think a really useful option is an offline AV scanner.
Personally, I use the AVG Rescue CD via PXE but unsure if it can be used in terms of licensing issues, but any other suggestions are also welcome!

have tested & managed to get my normal PXE server to boot a local copy of the ISO with memdisk!
Now to try opening the iso over t'internet...


Pytorch Deep CFR example uses wrong value for Policy Network layers

The policy network seems to be created using the advantage network parameters and the policy network layer parameters appear to be unused.
https://github.com/deepmind/open_spiel/blob/1506d1c7b14c0f7dfcc091c41824c5a0dbe1971e/open_spiel/python/pytorch/deep_cfr.py#L269

Good catch, thanks! I've fixed it, will get merged in next update (Monday).


Module 1 exercises [Benedict Arkhurst]

Please "drag & drop" exercise 1 pdf file below.

Please "drag & drop" exercise 2 pdf file below.

Please UPDATE THE TITLE of this "Issue" in the title bar above with your name.

If you haven't done so, please go back to Module 1 and make sure to take
the post-training survey. Participating in surveys is required for receiving
the "GALUP Certificate" by the University of Florida.

Exercise-1-Gh Population-2018.pdf
Exercise-2-Ghana Population Density-2018.pdf