Migrate results in 'Meta' object has no attribute 'private_fields' if using django-constance

Hi I tried to use this package in a existing project
when running python manage.py migrate it fails with AttributeError: 'Meta' object has no attribute 'private_fields'
in
File "/usr/local/lib/python3.6/site-packages/django/forms/models.py", line 143, in fields_for_model
    sortable_private_fields = [f for f in opts.private_fields if isinstance(f, ModelField)]

This happens while applying data_browser.0009_migrate_saved_views
This is a issue if you use django-constance
i was able to resolve it with:
from constance.admin import ConstanceAdmin, Config

class ConfigAdmin(ConstanceAdmin):
    ddb_ignore = True

admin.site.unregister([Config])
admin.site.register([Config], ConfigAdmin)

Thanks for the report.
I will take a look into this. Would you be able to paste the complete stack trace?
Also what versions of Django and Constance are you using?

Django: 2.2.17
django-constance: 2.8.0
Running migrations:
  Applying data_browser.0001_initial... OK
  Applying data_browser.0002_auto_20200331_1842... OK
  Applying data_browser.0003_remove_view_app... OK
  Applying data_browser.0004_auto_20200501_0903... OK
  Applying data_browser.0005_auto_20200516_1726... OK
  Applying data_browser.0006_auto_20200531_1450... OK
  Applying data_browser.0007_view_public_slug... OK
  Applying data_browser.0008_view_limit... OK
  Applying data_browser.0009_migrate_saved_views...Traceback (most recent call last):
  File "manage.py", line 21, in <module>
    main()
  File "manage.py", line 17, in main
    execute_from_command_line(sys.argv)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "/home/vscode/.local/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/core/management/base.py", line 364, in execute
    output = self.handle(*args, **options)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/core/management/base.py", line 83, in wrapped
    res = handle_func(*args, **kwargs)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 234, in handle
    fake_initial=fake_initial,
  File "/home/vscode/.local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 245, in apply_migration
    state = migration.apply(state, schema_editor)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/db/migrations/migration.py", line 124, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/db/migrations/operations/special.py", line 190, in database_forwards
    self.code(from_state.apps, schema_editor)
  File "/home/vscode/.local/lib/python3.6/site-packages/data_browser/migrations/0009_migrate_saved_views.py", line 10, in forwards
    forwards_0009(View)
  File "/home/vscode/.local/lib/python3.6/site-packages/data_browser/migration_helpers.py", line 56, in forwards_0009
    models = get_models(request)
  File "/home/vscode/.local/lib/python3.6/site-packages/data_browser/orm_admin.py", line 312, in get_models
    model_admins, admin_fields = _get_all_admin_fields(request)
  File "/home/vscode/.local/lib/python3.6/site-packages/data_browser/orm_admin.py", line 134, in _get_all_admin_fields
    get_common(model_admin, model)
  File "/home/vscode/.local/lib/python3.6/site-packages/data_browser/orm_admin.py", line 124, in get_common
    all_admin_fields[model].update(from_fieldsets(admin, False))
  File "/home/vscode/.local/lib/python3.6/site-packages/data_browser/orm_admin.py", line 95, in from_fieldsets
    fields = admin.get_fieldsets(request, obj)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/contrib/admin/options.py", line 330, in get_fieldsets
    return [(None, {'fields': self.get_fields(request, obj)})]
  File "/home/vscode/.local/lib/python3.6/site-packages/django/contrib/admin/options.py", line 321, in get_fields
    form = self._get_form_for_get_fields(request, obj)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/contrib/admin/options.py", line 659, in _get_form_for_get_fields
    return self.get_form(request, obj, fields=None)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/contrib/admin/options.py", line 705, in get_form
    return modelform_factory(self.model, **defaults)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/forms/models.py", line 551, in modelform_factory
    return type(form)(class_name, (form,), form_class_attrs)
  File "/home/vscode/.local/lib/python3.6/site-packages/django/forms/models.py", line 256, in __new__
    apply_limit_choices_to=False,
  File "/home/vscode/.local/lib/python3.6/site-packages/django/forms/models.py", line 142, in fields_for_model
    sortable_private_fields = [f for f in opts.private_fields if isinstance(f, ModelField)]
AttributeError: 'Meta' object has no attribute 'private_fields'

I've found a tidy way to detect this particular form of shenanigans. I have released that as 3.0.4


CockroachDB connection failed: "spawn: query engine errored"

Version
github.com/steebchen/prisma-client-go v0.35.0
Problem Description
I tried to use Go Prisma to connect my local single node CockroachDB in a demo
func TestConn(t *testing.T) {
	client := db.NewClient()
	err := client.Prisma.Connect()
	assert.NoError(t, err)
	defer client.Prisma.Disconnect()
}

But always got error on Connect()(100% reproducible): spawn: query engine errored: expected value at line 1 column 1
However, I can successfully pull exsiting table schema from CockroachDB by go run github.com/steebchen/prisma-client-go db pull.
Related Issue
I found issue 1128 reported the same problem. Its solution was to use a fix version go get github.com/steebchen/prisma-client-go@a10327f06445dd9aa8edd63759ef253caf491541. But that version didn't work for me, with the same error message.
Logs
Full log with PRISMA_CLIENT_GO_LOG=debug set:
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.868741 temp dir: /tmp
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.868788 query engine exists, not unpacking. 49.024µs. at /tmp/prisma/binaries/engines/0ca5ccbcfa6bdc81c003cf549abe4269f59c41e5/unpacked/v2/prisma-query-engine-debian-openssl-3.0.x
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.868898 ensure query engine binary...
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.868935 temp dir: /tmp
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.868957 global cache dir: /home/ubuntu/.cache
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.874228 checking for local query engine `prisma-query-engine-linux-static-x64` or `prisma-query-engine-debian-openssl-3.0.x`
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.874250 checking for global query engine `/tmp/prisma/binaries/engines/5a9203d0590c951969e85a7d07215503f4672eb9/unpacked/v2/prisma-query-engine-linux-static-x64` or `/tmp/prisma/binaries/engines/5a9203d0590c951969e85a7d07215503f4672eb9/unpacked/v2/prisma-query-engine-debian-openssl-3.0.x`
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.874262 checking for cached query engine `/home/ubuntu/.cache/prisma/binaries/cli/5.10.2/5a9203d0590c951969e85a7d07215503f4672eb9/prisma-query-engine-linux-static-x64` or `/home/ubuntu/.cache/prisma/binaries/cli/5.10.2/5a9203d0590c951969e85a7d07215503f4672eb9/prisma-query-engine-debian-openssl-3.0.x`
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.874689 exact query engine found in cache path: /home/ubuntu/.cache/prisma/binaries/cli/5.10.2/5a9203d0590c951969e85a7d07215503f4672eb9/prisma-query-engine-linux-static-x64 &{name:prisma-query-engine-linux-static-x64 size:22861456 mode:493 modTime:{wall:191010872 ext:63847114860 loc:0x1a5e1e0} sys:{Dev:2064 Ino:109207 Nlink:1 Mode:33261 Uid:1000 Gid:1000 X__pad0:0 Rdev:0 Size:22861456 Blksize:4096 Blocks:44656 Atim:{Sec:1711518061 Nsec:811010660} Mtim:{Sec:1711518060 Nsec:191010872} Ctim:{Sec:1711518060 Nsec:191010872} X__unused:[0 0 0]}}
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.889956 version check took 15.1788ms
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.890015 using query engine at /home/ubuntu/.cache/prisma/binaries/cli/5.10.2/5a9203d0590c951969e85a7d07215503f4672eb9/prisma-query-engine-linux-static-x64
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.890021 ensure query engine took 21.086237ms
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.891006 running query-engine on port 37489
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.891152 starting engine...
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.891386 connecting to engine...
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.891479 prisma engine payload: `{}`
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.892378 could not connect; retrying...
{"timestamp":"2024-03-27T05:49:09.901295Z","level":"INFO","fields":{"message":"Encountered error during initialization:"},"target":"query_engine"}
2024/03/27 12:49:09 expected value at line 1 column 1
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.993222 disconnecting...
[prisma-client-go] DEBUG: 2024/03/27 12:49:09.993247 query engine closed
--- FAIL: TestConn (0.12s)
    bench_test.go:13:
                Error Trace:    ...
                Error:          Received unexpected error:
                                spawn: query engine errored: expected value at line 1 column 1
                Test:           TestConn
FAIL

Can you share your URL string please if possible? Or can you try encoding the password in the DB string using encodeURIComponent()?

Can you share your URL string please if possible? Or can you try encoding the password in the DB string using encodeURIComponent()?

 datasource db {
  provider = "cockroachdb"
  url      = "postgres://root@localhost:26257/defaultdb?sslmode=disable"
}

This is a local deployed CockroachDB by cockroach start-single-node --insecure

That error message looks like https://github.com/prisma/prisma-engines/issues/4613 which is still unclear why it happens. Can you maybe try using url = ENV("DATABASE_URL") and setting the connection string with the DATABASE_URL env? Just to see if it is related to this bug or something different
also please set PRISMA_CLIENT_GO_LOG=debug and check if there are any other errors?

@steebchen Thanks. The connection succeed with url = ENV("DATABASE_URL"). Debug log:
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.092567 temp dir: /tmp
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.092619 query engine exists, not unpacking. 54.494µs. at /tmp/prisma/binaries/engines/473ed3124229e22d881cb7addf559799debae1ab/unpacked/v2/prisma-query-engine-debian-openssl-3.0.x
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.092752 ensure query engine binary...
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.092784 temp dir: /tmp
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.092808 global cache dir: /home/ubuntu/.cache
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.096261 checking for local query engine `prisma-query-engine-linux-static-x64` or `prisma-query-engine-debian-openssl-3.0.x`
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.096294 checking for global query engine `/tmp/prisma/binaries/engines/473ed3124229e22d881cb7addf559799debae1ab/unpacked/v2/prisma-query-engine-linux-static-x64` or `/tmp/prisma/binaries/engines/473ed3124229e22d881cb7addf559799debae1ab/unpacked/v2/prisma-query-engine-debian-openssl-3.0.x`
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.096561 checking for cached query engine `/home/ubuntu/.cache/prisma/binaries/cli/5.12.0/473ed3124229e22d881cb7addf559799debae1ab/prisma-query-engine-linux-static-x64` or `/home/ubuntu/.cache/prisma/binaries/cli/5.12.0/473ed3124229e22d881cb7addf559799debae1ab/prisma-query-engine-debian-openssl-3.0.x`
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.096607 query engine found in cache path: /home/ubuntu/.cache/prisma/binaries/cli/5.12.0/473ed3124229e22d881cb7addf559799debae1ab/prisma-query-engine-debian-openssl-3.0.x &{name:prisma-query-engine-debian-openssl-3.0.x size:18388392 mode:493 modTime:{wall:566250604 ext:63848770587 loc:0x1b2d420} sys:{Dev:2064 Ino:287657 Nlink:1 Mode:33261 Uid:1000 Gid:1000 X__pad0:0 Rdev:0 Size:18388392 Blksize:4096 Blocks:35920 Atim:{Sec:1713173787 Nsec:666250599} Mtim:{Sec:1713173787 Nsec:566250604} Ctim:{Sec:1713173787 Nsec:566250604} X__unused:[0 0 0]}}
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.101492 version check took 4.831323ms
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.101524 using query engine at /home/ubuntu/.cache/prisma/binaries/cli/5.12.0/473ed3124229e22d881cb7addf559799debae1ab/prisma-query-engine-debian-openssl-3.0.x
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.101582 ensure query engine took 8.798098ms
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.102846 running query-engine on port 39263
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.103023 starting engine...
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.103364 connecting to engine...
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.103403 prisma engine payload: `{}`
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.104329 could not connect; retrying...
{"timestamp":"2024-04-15T09:38:43.109840Z","level":"INFO","fields":{"message":"Starting a postgresql pool with 17 connections."},"target":"quaint::pooled"}
{"timestamp":"2024-04-15T09:38:43.140801Z","level":"INFO","fields":{"message":"Started query engine http server on http://<IP_ADDRESS>:39263","ip":"<IP_ADDRESS>","port":"39263"},"target":"query_engine::server"}
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.204575 prisma engine payload: `{}`
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.206343 [timing] query engine raw request took 1.694211ms
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.206414 prisma engine response: `{"status":"ok"}`
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.206436 [timing] elapsed: 9µs
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.206462 [timing] just http: 1.685211ms
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.206471 [timing] http percentage: 99.47%
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.206503 connecting took 113.719797ms
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.206518 connected.
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.206522 disconnecting...
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.208226 disconnected.
[prisma-client-go] DEBUG: 2024/04/15 16:38:43.208244 query engine closed
PASS
ok      CR-Prisma  0.118s

Awesome thanks. I still have to figure out the actual error but at least you got it working for now


aws-sdk-go-v2 example

It would be great to have an example using aws-sdk-go-v2 in the README.

Hi @elgohr thanks for raising the topic. Anything particular in that regard, or simply how to use it with aws-sdk-go-v2?

I guess a v2 example would be enough.


I can't run the example

I wired it up with Firebase so had the example app working located at packages/google_ml_kit/example.
I included Chinese, Japanese and Korean but I know for sure it did not recognize Korean using Text recognition.
So do I have to limit it to one language?
But when I take out Chinese and Japanese from my build.gradle, now the app just stops abruptly.
My app level build.gradle
plugins {

  id 'com.android.application'
  // Add the Google services Gradle plugin
  id 'com.google.gms.google-services'

}

def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

apply plugin: 'com.android.application'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

android {
    compileSdkVersion 33

    lintOptions {
        disable 'InvalidPackage'
    }

    defaultConfig {
        applicationId "com.google_mlkit_example"
        minSdkVersion 21
        targetSdkVersion 31
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
        }
    }

    aaptOptions {
        noCompress "tflite"  // Your model's file extension: "tflite", "lite", etc.
    }
}

dependencies {
    implementation platform('com.google.firebase:firebase-bom:32.0.0')
    // Add language package you need to use
    implementation 'com.google.firebase:firebase-analytics-ktx'
    //implementation 'com.google.mlkit:text-recognition-chinese:16.0.0-beta5'
    // implementation 'com.google.mlkit:text-recognition-devanagari:16.0.0-beta5'
    //implementation 'com.google.mlkit:text-recognition-japanese:16.0.0-beta5'
    implementation 'com.google.mlkit:text-recognition-korean:16.0.0-beta5'
}

flutter {
    source '../..'
}

My project level build.gradle
buildscript {
    repositories {
        google()
        jcenter()
        mavenLocal()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:7.2.1'
        classpath 'com.google.gms:google-services:4.3.15'
    }
}

allprojects {
    repositories {
        google()
        jcenter()
        mavenLocal()
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

Yes, it only runs when I uncomment Chinese.  Then it doesn't really recognize any Korean at all on Text Recognition.
What am I doing wrong here?

Check our example app after merging this PR: https://github.com/flutter-ml/google_ml_kit_flutter/pull/459
Each instance of TextRecognizer only recognizes one kind of character set at a time:   Chinese, Devanagari, Japanese, Korean or Latin character sets.
If you want to detect multiple character sets you need to create as many character sets as you need.
In our example app, the UI is configure to detect only one at a time, but you can certainly change it an play with it:

When I change to Japanese, it works:


Need Bit Clarification

i could not figure out ,whats'the logic behind this.But it is working fine .Based on What you are taking these sdp values ?is it a Px based or Dp Based ?
For example,if i want  my app to support from 240 width screen to 720 width screen,what should i do ?should i ask my Designer to give  the UI(.psd)  in 240px width ?

The logic is dp based. Yes, it will be better to get 240px width design in this case.


what is tls?

FEATURE REQUEST

Please describe the feature you are requesting.
i don't know what is tls?
when i see the code in class NamesrvController and we look at the method initialize(),so you will see a judgement "if (TlsSystemConfig.tlsMode != TlsMode.DISABLED) ",so i don't
understand what is TLS.

Provide any additional detail on your proposed use case for this feature.
the rocketmq source code version is 4.7.1

https://en.wikipedia.org/wiki/Transport_Layer_Security
RocketMQ can turn on TLS to increase data transfer security.
Issues are generally used for bug reports and feature requests, so if you have any questions about     Apache  RocketMQ, it is recommended to discuss it on the mailing list first, the mailing list address. I will close the Issue first, but please feel free to reopen it if you have any other issues.


Fix char boundary panic

Filter empty tokens before inserting them in the AhoCorasick automaton, avoiding a char boundary panic
Related issue
Fixes partially https://github.com/meilisearch/meilisearch/issues/4574

@Kerollmops because until it's not fully merged in Meilisearch, it does not completely fix the issue. I did not want this PR to close the MEilisearch issue.


Overflow in confirmation buttons (simplify them to Confirm, or even remove the confirmation step)

What

[ ] Overflow in confirmation buttons (simplify them to Confirm, or even remove the confirmation step)

Should we just use a ✔ and a ❌ icon buttons there instead of the text buttons and maybe add these terms as tool-tips to them?
Something like we have on the analytics page


Performance issues in stable ecto with MySQL

There is a change in ecto, how it generates the queries.
In at least 0.12.0, the queries wer generated using parameters:
SELECT ... WHERE ID == ?, [id]

Which leads to prepared query: "SELECT ... WHERE ID == ?"
Now, ecto generates queries as:
SELECT ... WHERE ID == 1

Which leads to prepared query:  "SELECT ... WHERE ID == 1"
This leads to, that the cache query will be very fast full and that prepared query are not really cached(as they must be cleaned, and there much uniq queries due this using). With a problem of MariaDB, where prepared queries are taking 40ms, this leads to performance degradation.
Want to ask, if I should get back text protocol for all non parameterised queries in mariaex back or it is a bug in ecto, that it doesn't use prepared queries right more?

Or, we are using on one place ecto wrong, as it inserts literals to query.
I'll close temporary.

Sorry, it was really own error.


Example pipeline for gridMET

Source Dataset

gridMET is a dataset of 4km daily surface meteorological data covering the CONUS domain from 1979-yesterday.

http://www.climatologylab.org/gridmet.html
NetCDF
One file per year-variable
How are the source files accessed: HTTP download or OPENDaP

HTTP: https://www.northwestknowledge.net/metdata/data/
OPENDaP: http://thredds.northwestknowledge.net:8080/thredds/reacch_climate_MET_catalog.html

Any special steps required to access the data: No

Transformation / Alignment / Merging

Files should be concatenated along the time dimension and merged along the variable dimension
Output Dataset

1 Zarr store - chunks oriented for both time series and spatial analysis.

This recipe requires us to resolve https://github.com/pangeo-forge/pangeo-forge/issues/50 and https://github.com/pangeo-forge/pangeo-forge/issues/39.

This recipe requires us to resolve https://github.com/pangeo-forge/pangeo-forge/issues/50 and https://github.com/pangeo-forge/pangeo-forge/issues/39.

This recipe is now ready to be implemented.

Hey there @sharkinsspatial, definitely interested in working on the gridMET recipe. Can probably take a stab at it in the coming week.


[Feature Request] Support multiple json-like encodings for display

Is your feature request related to a problem? Please describe.
We have a situation where we use a custom data converter to sometimes encode using Jackson and sometimes encode using Gson. For this to work, we have to use two encoding types even though both encoders produce JSON. Temporal Web will only display the encoding type "json/plain" (well also protobuf...) and everything else is shown as base64.
Describe the solution you'd like
Perhaps a way to configure a list of encodings to treat at json or generally better support for plugging in decoders in web.

@skrul would like to understand better
Are you using data converter interface to encode payloads? If so, have you also tried enabling decryption of payloads for UI using tctl dataconverter web  --web_ui_url <url> ?

@feedmeapples This may be a newer feature, I'm still using 1.8. I don't see any docs for tctl dataconverter on temporal.io... but perhaps this is a way for tctl and the web UI to leverage a temporal worker to decode a payload for non-standard encoding types? that would be nice!

@skrul yes it's a newer feature and seems it's not yet described in the docs. I'll communicate with our docs team to see if this can be prioritized
Meanwhile you can look at this go example on how to convert payloads https://github.com/temporalio/samples-go/tree/master/cryptconverter
Then you can use tctl to enable the decryption for the Web UI using
tctl dataconverter web --web_ui_url <url>

And following the link that tctl outputs. Following the link will let the WebUI know that the payloads need to be decrypted and it will communicate to tctl's data converter for decryption


No Dvorak support

Ydco u.aygp. b..eo yr x. cmln.m.by.e pcidy a,af!

I don't think that it will be supported in approx. the next 120 years or so.


Assets are not shown on the default presets

Hi,
I am trying to show a success message but can't get the image to show. Couldn't "SuccessMessageIcon.png" in the project folder.
Using pods and the latest (swift) version.

What version of RMessage are you using the 2.x.x series or 3.x.x? Please retest.


Better argnodes.

This is a general overhaul of the argnode/dependents-system.
Previously, a dynamic/functionNode simply stored references to their argnodes + the argnodes a reference to their dependents. That works as long as

all nodes are available at the time the references are created and
the node that is depended upon isn't removed (and newly added).

It will fail if eg. a functionNode depends on a node inside a choiceNode, which is currently not visible (or on a node that doesn't even exist yet, perhaps due to it being generated by a dynamicNode).
One (pretty big, but practical) example for what is possible with the new system:
local ai = require("luasnip.nodes.absolute_indexer")

s("class", fmta([[
	---@class <>
	local <> = {<>}

	<>
]], {
	rep(1), -- parent-relative indexing still works.
	i(1, 'MyClass'),
	i(2),
	c(3, {
		fmta([[
			<>function <>:new(o)
				o = o or {}
				setmetatable(o, self)
				self.__index = self
				return o
			end
		]], {
			i(1),
			rep(ai[1]) -- refers to first `insertNode` relative to surrounding snippet.
		})
		t''
	}),
}))

(The absolute_indexer can be constructed as

ai[1][2][3]
ai(1,2,3)
ai{1,2,3}
(I prefer the []-version, but that may be too much to type, which is why the others are implemented))

Concerns:

Right now, a node may only update if all argnodes are visible. One alternative could be to just update, but use the old text for missing nodes. The prior approach is probably easier, but I'm unsure if the latter may be better.
Performance: The absolute positions have to be resolved on each update. I haven't experienced any noticeable lag so far, but I'd like to be certain that it performs comparably to the current system before merging into master.
Currently we assume that the current node will remain valid after an update, but that may not be the case if the current node is inside a dynamicNode with cyclic dependencies, which can cause it to be updated as a result of changing text inside it.
Right now the snippet will just be unlinked, it's possible to handle it so the snippet stays active,
but that doesn't seem worth it as I can't think of something practical that could be achieved with cyclic dependencies.

I'd like to get some opinions (...perhaps also some early testing :P), so feel free to give some feedback before this is merged.

I tried the above example on this branch, but it gives an error on expanding. Is it still incomplete?
local ls = require("luasnip")
local s = ls.snippet
local sn = ls.snippet_node
local isn = ls.indent_snippet_node
local t = ls.text_node
local i = ls.insert_node
local f = ls.function_node
local c = ls.choice_node
local d = ls.dynamic_node
local r = ls.restore_node
local rep = require("luasnip.extras").rep
local fmta = require("luasnip.extras.fmt").fmta
local ai = require("luasnip.nodes.absolute_indexer")

ls.snippets = {
    lua = {
        s(
            "class",
            fmta(
                [[
	---@class <>
	local <> = {<>}

	<>
]],
                {
                    rep(1), -- parent-relative indexing still works.
                    i(1, "MyClass"),
                    i(2),
                    c(3, {
                        fmta(
                            [[
			<>function <>:new(o)
				o = o or {}
				setmetatable(o, self)
				self.__index = self
				return o
			end
		]],
                            {
                                i(1),
                                rep(ai[1]), -- refers to first `insertNode` relative to surrounding snippet.
                            }
                        ),
                        t(""),
                    }),
                }
            )
        ),
    },
}

E5108: Error executing lua .../packer/start/LuaSnip/lua/luasnip/nodes/functionNode.lua:108: bad argument #1 to 'ipairs' (table expected, got nil)
stack traceback:
        [C]: in function 'ipairs'
        .../packer/start/LuaSnip/lua/luasnip/nodes/functionNode.lua:108: in function 'set_dependents'
        .../pack/packer/start/LuaSnip/lua/luasnip/nodes/snippet.lua:982: in function 'set_dependents'
        .../pack/packer/start/LuaSnip/lua/luasnip/nodes/snippet.lua:612: in function 'fake_expand'
        .../pack/packer/start/LuaSnip/lua/luasnip/nodes/snippet.lua:654: in function 'get_docstring'
        ...e/pack/packer/start/cmp_luasnip/lua/cmp_luasnip/init.lua:35: in function 'get_documentation'
        ...e/pack/packer/start/cmp_luasnip/lua/cmp_luasnip/init.lua:114: in function 'resolve'
        .../nvim/site/pack/packer/start/nvim-cmp/lua/cmp/source.lua:342: in function 'resolve'
        ...e/nvim/site/pack/packer/start/nvim-cmp/lua/cmp/entry.lua:431: in function 'resolve'
        ...re/nvim/site/pack/packer/start/nvim-cmp/lua/cmp/core.lua:344: in function <...re/nvim/site/pack/packer/start/nvim-cmp/lua/cmp/core.lua:341>
        ...te/pack/packer/start/nvim-cmp/lua/cmp/utils/feedkeys.lua:51: in function <...te/pack/packer/start/nvim-cmp/lua/cmp/utils/feedkeys.lua:49>

Ah, I only tested expanding it normally, very possible I missed something about get_docstring. I'll have to remember to add tests for those... Ty!

Ok. I'm looking forward to it as it seems useful!


AutoscaledPool.run wont stop if isTaskReadyFunction or isFinishedFunction failed

Hi,
Just upgraded to version 0.8 and I noticed that if isFinishedFunction or isTaskReadyFunction function failed the pool will continue to run.
Here is an example that produces an endless pool:
let Apify = require('apify');

// start crawl
let pool = new Apify.AutoscaledPool({
    runTaskFunction: () => {
        // do something
    },

    isFinishedFunction: () => {
        throw 'b';
    },

    isTaskReadyFunction: () => {
        throw 'c';
    },
});

(async () => {
    await pool.run().catch(() => {
        // Expect to be called when isTaskReadFunction or isFinished failled
    });
})();

In our specific use case we would need somehow the pool.run promise to be rejected when isFinishedFunction or isTaskReadyFunction fails because if an error produces here we just want to stop the script as errored.
That might be done via option like rejectOrError.

Hi @gsouf, we will probably implement this, but it most likely won't land earlier than in 2 weeks time.
For now, please consider using something like this:
isFinishedFunction: () => {
    try {
        throw 'b';
    } catch (err) {
        if (pool.reject) pool.reject(err);
    }
}

I think this feature definitely makes sense. If there's any uncaught error, the pool should fail completely. The user is responsible for handling their errors.

Fixed in https://github.com/apifytech/apify-js/pull/257


CMD0 response error, expect 0x1, response 3

I've ported at_sdspi_host driver to my MCU, but sending the CMD0 by using at_spi_cmd_go_idle_state() doesn't return the correct response.
E sdspi_transaction: CMD0 response error, expect 0x1, response 3
E sdspi_transaction: Please restart slave and test again,error code:264
E sdspi_transaction: CMD0 response error, expect 0x1, response 3
E sdspi_transaction: Please restart slave and test again,error code:264
E sdspi_transaction: CMD0 response error, expect 0x1, response 3

I've added 50K pull-up resistors on ESP32-D2WD.
Any thoughts? Thanks!

As per the cmd data structure:
typedef struct {
    // These fields form the command sent from host to the card (6 bytes)
    uint8_t cmd_index : 6;
    uint8_t transmission_bit : 1;
    uint8_t start_bit : 1;
    uint8_t arguments[4];
    uint8_t stop_bit : 1;
    uint8_t crc7 : 7;
    /// Ncr is the dead time between command and response; should be 0xff
    uint8_t ncr;
    /// Response data, should be set by host to 0xff for read operations
    uint8_t r1;
    /// Up to 16 bytes of response. Luckily, this is aligned on 4 byte boundary.
    uint32_t response[4];
    /// response timeout, in milliseconds
    //int timeout_ms;
} sdspi_hw_cmd_t;

👉Response data, should be set by host to 0xff for read operations
The 8th bytes of MISO should output 255, in my case, I received 254. The response code should output 1 from ESP32 slave, in my case, I received 3. The interesting thing is that if we move the waveform of MISO only one bit backward, could it be the expected result?

Hi, have you ever tried two esp32 to communicate(One ESP32 as SDIO HOST)? CMD0 response error usually hardware connection or SDIO SPI init problems.

@ESP-Coco Two ESP32 work fine. But the output waveform is quite different from my MCU<->EPS32.

It is too strange, The communication of SDIO is controlled by the protocol and has nothing to do with the hardware platform. What MCU are you using? I am doing the migration work on the STM32 platform. Maybe I can give you some useful advice when I'm done.

Thank you @Jacques-zhao, I'm using our own platform which is based on STM32 and nRF52840.

@Jacques-zhao Since I've finished porting the driver, maybe we can have some more discussion about this issue. If it is convenient for you, may I have your WeChat ID, you can send it to my Email 👉<EMAIL_ADDRESS>Thanks!

I have already passed the initialization process with the STM32 development board, so I still suspect there is a problem with your hardware. The following is the log I printed with STM32.

You can send an email to our business<EMAIL_ADDRESS>) to apply for a SDIO development board. which has already debugged the hardware. You only need to use Dupont line to connect to your MCU.

Thank you @ESP-Coco . Apart from the hardware issue, I also have a concern about the driver.
As per the comment inside sdspi_host.c driver, it should clock out 80  cycles (10 bytes) .
/// Clock out 80 cycles (10 bytes) before GO_IDLE command
void go_idle_clockout()

I did the same thing on my MCU(on the left side in the picture):

But when I use ESP32 as ESP-AT master, it clocks out only two bytes?

It was the hardware issue, pretty much the EMI issue, changing the board helped.


Does not work with Mulitple SIDS

When using multiple Service IDs, it throws an error:
404:Service does not exist or bad path requested. Method: PUT, Path: /service/I4k1GkMXUSAxyR7QoHvyX,7jfv9fh81eWWVY9DIrkoam,5fVEXEJLLEWi0YBDZAWI5z,HIBkockf4TZ6vX1YmRAAW/change_customer/4rzwkpWl3ViAc9Tsp04F1I?password=M%40ryjan31910 Message from API: {"msg":"Record not found","detail":"Cannot find service 'I4k1GkMXUSAxyR7QoHvyX,7jfv9fh81eWWVY9DIrkoam,5fVEXEJLLEWi0YBDZAWI5z,HIBkockf4TZ6vX1YmRAAW'"}
In theory it should iterate through the array of service ids, instead it's being treated as a single string.

This was due to me running an old version and using git clone instead of git pull origin master to try to bring it up to date.  🤦♂


fix: switch to ClientException

Bug fix
What is the current behavior?
We only catch SocketException, which in only thrown in native Dart, but not for example in dart2js
What is the new behavior?
We instead use ClientException, which is also thrown in js runtime as documented here
Additional context
This was meant to fix #641, but this would require the removal of File, which im very unsure about. I think it makes things MUCH easier to be able to work with File on native platform, but somehow not being able to compile this to dart web is a bummer. I'm wondering why this package compiles for Flutter web though.

It sounds like dart2js support will not be possible without removing the use of File, correct?
How about we changing the .storage.upload() method to accept a Uint8List and get rid of the .storage.uploadBinary() method. It's a bit disruptive, but I always thought having two methods is a bit confusing. It might provide better DX if we had a single method for those storage operations.

It might be also pretty disruptive to drop support for uploading File object, so might not be a good idea. I personally wouldn't worry too much about supporting dart2js though. The use cases are very limited, and the SDK works just fine on Flutter Web. I'm more than happy to just close https://github.com/supabase/supabase-flutter/issues/641 as won't do.

I think I was able to fix the issue :tada: I created a stub for File which is used on js platform. The webdev build went well with only stubbing the used methods. This is actually no breaking change, so we could also merge this in main. :thinking:

I moved the commits now to the main branch, so we can ship this as well to v1.


feat: add eio 3.0.1 release

update eio with release 3.0.1

:tada: This PR is included in version 1.199.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


NSURLConnection has been deprecated, please use NSURLSession

We will achieve this by replacing our custom network component with AFNetworking which allows using NSURLSession or NSURLConnection

Why not to use raw NSURLSession ? I think there is no need to add dependency to other network for that

+1 against adding AFNetworking as a dependency.

Another +1 against adding AFNetworking as a dependency.

+1 against adding AFNetworking as a dependency.

This has been going on for more than a year now.
https://github.com/rs/SDWebImage/issues/823
https://github.com/rs/SDWebImage/issues/1318
It would be good to have some clarity. We need to know if and when the migration to NSURLSession is planned for, and if it'll depend on AFNetworking. Could we please have an update?

I think the migration will be to AFNetworking, I hope I can find the time for that and the other things that need to be done

+1 against. I would probably find another image cache if SDWebImage depended on AFNetworking. NSURLSession is capable, won't add code size, and typically only requires you to call a convenience method or two.

I agree with @kconner.

I’d also find another image cache if AFNetworking were added as a dependency. Because NSURLConnection is deprecated, people will be migrating to NSURLSession anyway, so supporting both isn’t really that important, right?

Guys, help me out here. I was almost sure that not having to maintain networking code for this library is a good thing and relying on a library like AFNetworking for the network component would add value. Is adding a dependency the issue here?

Yeah, I'd say that adding AFNetworking as a dependency is the issue. The code you write for NSURLSession would be almost as short, if that helps. I'd rather not have child dependencies, because I use SDWebImage as a drop-in solution for fetching images. I like it because it feels fast and light and won't complicate my namespaces more than necessary. Libraries like AFNetworking are useful to me, some of the time, but I'd rather make that decision per-app. SDWebImage, on the other hand, I want to use in nearly every app, so I don't want it to feel like it will cost more code size, link time, security risk, etc.

@bpoplauschi I avoid using AFNetworking in basically all my projects now. It’s a lot of code that doesn’t really do much that can’t also be accomplished with NSURLSession. But SDWebImage is still something I like and rely on. Having it bring along a huge dependency (and its potential bugs) makes SDWebImage less attractive.
FWIW, I was able to strip all of AFNetworking out of a project and replace it with NSURLSession in about a day. AFNetworking’s value is much diminished at this point.

Ok, got it. I will rethink this and try to do it without AFNetworking. (The reasoning was to avoid all kinds of fixes for the networking component and I can definitely say AFNetworking is still properly maintained and has a good code quality, but I understand what you are saying).

Seems like using AFNetworking would be more work then just fixing the single depreciation no?

Resolved by #1578

3.8.0 version was just released.

👍


Add icon to WindowDesciptor

This PR adds an optional icon to WindowDescriptor and updates
window_settings example to use it.
Fixes #1031

If possible, I think it would be nice if we could load icons using the asset system (ex: make the window descriptor take a Handle<Texture>). But imo thats only really an option if we can set the winit icon after creating the window. Otherwise we're blocking window construction (and various app startup / gpu allocations) on an image being loaded.


OpenTelemetry collector

Sample for .NET: https://github.dev/open-telemetry/opentelemetry-dotnet/tree/98cb28974af43fc893ab80a8cead6e2d4163e144/examples/AspNetCore
Instrument for MassTransit: https://github.dev/open-telemetry/opentelemetry-dotnet-contrib/tree/main/test/OpenTelemetry.Instrumentation.MassTransit.Tests
Open Telemetry Collector: https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter
Serilog with Otel. Is it a good approach? See https://github.com/serilog/serilog/issues/1577

Sample to run on nomad can be found: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/examples/nomad


Missing dependency on MacOS: libpcre for nightly download

Trying out the pre-compiled nightly release from commit d7f3dd5. Looks like kcr expects a Perl regular expressions library in /usr/local/opt. I believe this path is created by homebrew, but I don't have brew installed.
Is is possible to statically link this library, or specify it as a dependency in the Installation section of the README and let us set the DYLD_LIBRARY_PATH environmental variable to point to libpcre?
~/Downloads/kakoune.cr-nightly-x86_64-apple-darwin
❯ ./bin/kcr
dyld: Library not loaded: /usr/local/opt/pcre/lib/libpcre.1.dylib
  Referenced from: /Users/mike/Downloads/kakoune.cr-nightly-x86_64-apple-darwin/./bin/kcr
  Reason: image not found
Abort trap: 6

Same problem here. @mogenson could you find a solution for this?


Cljs support (WIP)

This is just a start; there's a bunch of stuff that'll need to be changed and I wanted to go through some of it in a somewhat interactive form rather than going too far down the rabbit hole and finding out that wasn't a direction we agreed on.

At a high level, I have some thoughts:

JavaScript does not have an inheritance model in the same way that Java does. We can check that a given object satisfies an interface, for instance, but there isn't really chained inheritance the way there is in Java.
Checking for basic types is obviously going to be different. We would dispatch on js/Number rather than java.lang.Integer etc.
I find the puget.dispatch namespace confusing.

I don't really understand how the library works right now, so just at a high level I'd like some clarification that I really understand what's going on. My understanding of the code is as follows:

We have various maps, for instance, puget.printer/java-handlers, where the keys are references to classes and the values are the print-functions
When we try to call dispatch on a value, it looks up the corresponding value for its key in the map based on the results of a call to class on the value, and calls that on itself to try to print the value. If it can't find anything it falls back to a default print method of java.lang.Object

It would seem to me that since class doesn't exist in ClojureScript, we'd end up adopting a very different approach - one based first on checking type, and then after that using satisfies? to check against known interfaces (possibly). Unlike in Java, we don't have the option of calling, .getInterfaces on the class itself.
Thoughts @greglook ?

JavaScript does not have an inheritance model in the same way that Java does.

This is going to be a little different, but I think the cljs code should check direct implementations/protocols rather than worrying about inheritance. That should solve most of the use-cases.

I find the puget.dispatch namespace confusing.

A lot of the code is for logical dispatch, to factor out common patterns for doing inheritance-style lookups in Java land. In a way, it's a simplified version of Clojure's multimethod/hierarchy dispatch.

It seems like a lot of the changes are format-related - please don't change the existing code style. It also makes the diff harder to read.

Yeah, sorry, I just ran cljfmt on the project and it changed a bunch of things. Would you be open to a separate alignment PR for the cljfmt stuff?

Upstream PR for arrangement will need to happen for this as well: https://github.com/greglook/clj-arrangement/pull/1


feat(CLI): replace --robot with an ETCHER_CLI_ROBOT env var

The --robot option of the CLI causes the program to output
machine-parseable strings, which can be easily consumed by the GUI to
update progress and other information.
The problem is that if the CLI fails to parse its command line arguments
when being called from the GUI for whatever reason, the .fail() Yargs
handler will be called, which doesn't output error information in the
usual "robot" format, causing the GUI to not understand the error
message.
Since the .fail() Yargs handler doesn't have access to the passed
options, we moved the "robot" functionality to an environment variable,
which we can easily check from there.
As a bonus, this PR refactors the whole robot logic into
lib/shared/robot.js and adds unit tests to it.
See: https://github.com/resin-io/etcher/issues/986
Change-Type: major
Changelog-Entry: Replace the --robot CLI option with an ETCHER_CLI_ROBOT environment variable.
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

I wonder if it'd make sense to spin out this "robot" functionality into its own NPM module? Or is it too etcher-specific? (obviously you'd want to make the env-var that it checks for configurable)

We had a discussion today about creating an "Etcher SDK", which will basically consists of the code that can be re-used between the CLI, the GUI, and any application based on Etcher.
Some things we will include here:

Drive detection
Image writing
Extended formats
The Redux store

etcetera.
So this would definitely include the robot functionality as well.

Drive-detection and image-writing are already handled by various modules so I wonder if it makes sense to continue that pattern, and simply have the "Etcher SDK" be a collection of additional modules?


Native TOML support for tox

Fixes #455. In order to do this, have also switched from tox-gh-actions to tox-gh. Has been tested in https://github.com/astro-informatics/sleplet/pull/420, https://github.com/astro-informatics/sleplet/pull/421.

[x] Will need to check if templating works correctly

I would just filter .pyc files out of the comparison (like the .git folder is) to make it a bit easier

Ah, thanks, that bit was annoying me. Guessing it is a difference between tox-gh and tox-gh-actions.

Thanks @dstansby!

This looks great. We should probably add it to our recommendations page? Because toml-er is better.

👍 have raised https://github.com/UCL-ARC/python-tooling/issues/461


hockey : fails to uploads dSYM when apps contains watch app (or extension)

Hi,
I am having trouble uploading the dSYM file of an application with a Watch app using the hockey action.
Actually the default value DSYM_OUTPUT_PATH sat up in gym.rb point to a ZIP file containing 2 dSYM packages (one for the app, the other for the extension) where hockey apparently only needs the app one.
http://i.imgur.com/KZKxESQ.png
I have thought of the following solution but not sure which one is the best before eventually submitting a PR:

Contacting HockeyApp : might be an issue to solve on their side
Adding a little shell script to unzip the APPNAME.app.zip file created by gym, zip only the app symbols within and override the FL_HOCKEY_DSYM parameter for the hockeyaction
Do something within gym.rb to detect if there are several symbol files but I am not sure how this can be achieved without manually adding a parameter to gym (makes me wonder how the provisionning_profile parameter is relevant when you have extension if you are no using env var like specified in the code signing guide ?)

Has anyone experienced the same issue or any though on this?
Nicolas

Got an answer for Hockey.
Even if the appId is specified the bundle from the app and the one declared on HockeyApp must match in this case


Error Running Tool

Attempting to use the plugin to anonymize a contact table. I get the following error:

I did think that maybe it's because the org is OnPremise 9.2 and you may be using Dataverse only methods. It has a correct count so is reading ok but doesn't process anything. There's also no log file to troubleshoot.
Appreciate this will be tricky to troubleshoot without a log file. Feature request for log file please. Thanks.

@JohnRogerson
There was indeed an issue with on-premise instances (version <=9.1). They should be fixed in the just published version of the tool (0.5). It should be available in the toolbox within a few hours.
Please let me know if it fixed the error.

That has resolved the issue. Successfully running in our OnPremise environments. Thanks.


box-sizing css missing in css file

.colpick, .colpick *{ direction:ltr; box-sizing:content-box; }
bootstrap is setting the box-sizing to border-box witch causing some problems in the layout

Done.

Fix merged!


Rick: React to .NET 9 Preview 3 features

Parent issue #32042

completed via Parent issue https://github.com/dotnet/AspNetCore.Docs/issues/32042


View Zone Alignment Bug

{
    "languageId": "markdown",
    "base": "---\ntitle: Migration Container Runtime Engine\nlang: en\npermalink: /imke/clusterlifecycle/clustermigrations/containerruntimeengine/\nnav_order: 5000\nparent: Cluster Lifecycle\nhas_children: false\n---\n\n## General Container Runtime Information\n\nFor a long time now Docker (or rather the dockershim to be more precise) has\nbeen used as the default Container Runtime Engine in the underlying\ninfrastructure of Kubernetes. But maintaining this dockershim on the\ndevelopment side has become a heaven burden on the Kubernetes maintainers.\nTo reduce this burden the CRI standard has been implemented, but unfortunately\nDocker itself does not implement this standard (hence the dockershim!).\n\nWith the Kubernetes v1.20 release the deprecation of the dockershim has been\nannounced, scheduled for the release of v1.24. So to be able to upgrade to\nKubernetes v1.24 we will need the Kubernetes nodes to run a different\ncontainer runtime engine which is CRI-standard compatible. For iMKE this\nwill be containerd.\n\n## Changing the Container Runtime Engine Config\n\nTo upgrade from docker to containerd the following steps are needed:\n\n1. edit the cluster configuration\n\n   ![edit-cluster-config](edit-cluster.png)\n\n1. change the value of the *Container Runtime* field from *docker* to *containerd* and save the changes\n\n   ![switch-cre-config](switch-cre.png)\n\n\n## Activating the Config Change\n\nFor the change to take effect you need to rotate your worker nodes once.\nThis can be done by either upgrading to a new Kubernetes version or by\ndoing a restart of the rollout of your MachineDeployment. While the prior\ncan be done in the webUI easily (and is already covered by [here](/imke/clusterlifecycle/upgradingacluster/)),\nthe latter will be shown below.\n\n1. check which container runtime your workers are currently using:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   ```\n\n   Here we see in the output that docker is still used as the container runtime.\n1. restart the MachineDeployment by\n    1. clicking on the MachineDeployment of the cluster\n\n       ![choose-machinedeployment](choose-machinedeployment.png)\n\n    1. clicking on the restart button\n\n       ![click-on-restart-button](click-on-restart-button.png)\n\n    1. confirming the restart of the MachineDeployment\n\n       ![confirm-restart](confirm-restart.png)\n\n   Now one after another a new machine will be added and an old machine will be removed after it's workload has been transferred into the rest of the cluster. After the last old machine has been removed the restart of the\n   MachineDeployment is complete.\n1. now to check again which container runtime powers your worker nodes now:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   ```\n\nThis concludes the migration of your Kubernetes clusters container runtime\nfrom *docker* to *containerd*.\n\n## Learn More\n\nMore background information on the container runtime engines for Kubernetes can be\nfound here:\n\n* <https://kubernetes.io/blog/2020/12/02/dockershim-faq/>\n* <https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/>\n",
    "input1": "---\ntitle: Migration Container Runtime Engine\nlang: en\npermalink: /gks/clusterlifecycle/clustermigrations/containerruntimeengine/\nnav_order: 4600\nparent: Cluster Lifecycle\nhas_children: false\n---\n# Migration Container Runtime Engine\n\n## General Container Runtime Information\n\nFor a long time now Docker (or rather the dockershim to be more precise) has\nbeen used as the default Container Runtime Engine in the underlying\ninfrastructure of Kubernetes. But maintaining this dockershim on the\ndevelopment side has become a heavy burden on the Kubernetes maintainers.\nTo reduce this burden the CRI standard has been implemented, but unfortunately\nDocker itself does not implement this standard (hence the dockershim!).\n\nWith the Kubernetes v1.20 release the deprecation of the dockershim has been\nannounced, scheduled for the release of v1.24. So to be able to upgrade to\nKubernetes v1.24 we will need the Kubernetes nodes to run a different\ncontainer runtime engine which is CRI-standard compatible. For GKS this\nwill be containerd.\n\n## Changing the Container Runtime Engine Config\n\nTo upgrade from Docker to containerd the following steps are needed:\n\n1. Edit the cluster configuration.\n![edit-cluster-config](../../images/MigContRun01.png)\n\n1. Change the value of the *Container Runtime* field from *docker* to *containerd* and save the changes.\n\n![switch-cre-config](../../images/MigContRun02.png)\n\n## Activating the Config Change\n\nFor the change to take effect, you need to rotate your worker nodes once.\nThis can be done by either upgrading to a new Kubernetes version or by\ndoing a restart of the rollout of your MachineDeployment. While the prior\ncan be done in the Web UI easily (and is already covered by [here](/gks/clusterlifecycle/upgradingacluster/)),\nthe latter will be shown below.\n\n1. Check which container runtime your workers are currently using:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   ```\n\n   Here we see in the output that docker is still used as the container runtime.\n1. Restart the Machine Deployment as follows:\n    1. Click on the Machine Deployment of the cluster.\n![choose-machinedeployment](../../images/MigContRun03.png)\n\n    1. Click on the Restart button.\n![click-on-restart-button](../../images/MigContRun04.png)\n\n    1. Confirm the restart of the Machine Deployment.\n\n ![confirm-restart](../../images/MigContRun05.png)\n\n   Now one after another, a new machine will be added and an old machine will be removed after its workload has been transferred into the rest of the cluster. After the last old machine has been removed, the restart of the\n   MachineDeployment is complete.\n2. Now check again, which container runtime powers your worker nodes:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   ```\n\nThis concludes the migration of your Kubernetes clusters container runtime\nfrom *docker* to *containerd*.\n\n## Learn More\n\nMore background information on the container runtime engines for Kubernetes is available here:\n\n* <https://kubernetes.io/blog/2020/12/02/dockershim-faq/>\n* <https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/>\n",
    "input2": "---\ntitle: Migration Container Runtime Engine\nlang: \"en\"\npermalink: /imke/clusterlifecycle/clustermigrations/containerruntimeengine/\nnav_order: 5000\nparent: Cluster Lifecycle\nhas_children: false\n---\n\n## General Container Runtime Information\n\nFor a long time now Docker (or rather the dockershim to be more precise) has\nbeen used as the default Container Runtime Engine in the underlying\ninfrastructure of Kubernetes. But maintaining this dockershim on the\ndevelopment side has become a heaven burden on the Kubernetes maintainers.\nTo reduce this burden the CRI standard has been implemented, but unfortunately\nDocker itself does not implement this standard (hence the dockershim!).\n\nWith the Kubernetes v1.20 release the deprecation of the dockershim has been\nannounced, scheduled for the release of v1.24. So to be able to upgrade to\nKubernetes v1.24 we will need the Kubernetes nodes to run a different\ncontainer runtime engine which is CRI-standard compatible. For iMKE this\nwill be containerd.\n\n## Changing the Container Runtime Engine Config\n\nTo upgrade from docker to containerd the following steps are needed:\n\n1. edit the cluster configuration\n\n   ![edit-cluster-config](edit-cluster.png)\n\n1. change the value of the *Container Runtime* field from *docker* to *containerd* and save the changes\n\n   ![switch-cre-config](switch-cre.png)\n\n## Activating the Config Change\n\nFor the change to take effect you need to rotate your worker nodes once.\nThis can be done by either upgrading to a new Kubernetes version or by\ndoing a restart of the rollout of your MachineDeployment. While the prior\ncan be done in the webUI easily (and is already covered by [here](/imke/clusterlifecycle/upgradingacluster/)),\nthe latter will be shown below.\n\n1. check which container runtime your workers are currently using:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   ```\n\n   Here we see in the output that docker is still used as the container runtime.\n1. restart the MachineDeployment by\n    1. clicking on the MachineDeployment of the cluster\n\n       ![choose-machinedeployment](choose-machinedeployment.png)\n\n    1. clicking on the restart button\n\n       ![click-on-restart-button](click-on-restart-button.png)\n\n    1. confirming the restart of the MachineDeployment\n\n       ![confirm-restart](confirm-restart.png)\n\n   Now one after another a new machine will be added and an old machine will be removed after it's workload has been transferred into the rest of the cluster. After the last old machine has been removed the restart of the\n   MachineDeployment is complete.\n1. now to check again which container runtime powers your worker nodes now:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   ```\n\nThis concludes the migration of your Kubernetes clusters container runtime\nfrom *docker* to *containerd*.\n\n## Learn More\n\nMore background information on the container runtime engines for Kubernetes can be\nfound here:\n\n* <https://kubernetes.io/blog/2020/12/02/dockershim-faq/>\n* <https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/>\n",
    "result": "---\ntitle: Migration Container Runtime Engine\nlang: \"en\"\npermalink: /gks/clusterlifecycle/clustermigrations/containerruntimeengine/\nnav_order: 4600\nparent: Cluster Lifecycle\nhas_children: false\n---\n# Migration Container Runtime Engine\n\n## General Container Runtime Information\n\nFor a long time now Docker (or rather the dockershim to be more precise) has\nbeen used as the default Container Runtime Engine in the underlying\ninfrastructure of Kubernetes. But maintaining this dockershim on the\ndevelopment side has become a heavy burden on the Kubernetes maintainers.\nTo reduce this burden the CRI standard has been implemented, but unfortunately\nDocker itself does not implement this standard (hence the dockershim!).\n\nWith the Kubernetes v1.20 release the deprecation of the dockershim has been\nannounced, scheduled for the release of v1.24. So to be able to upgrade to\nKubernetes v1.24 we will need the Kubernetes nodes to run a different\ncontainer runtime engine which is CRI-standard compatible. For GKS this\nwill be containerd.\n\n## Changing the Container Runtime Engine Config\n\nTo upgrade from Docker to containerd the following steps are needed:\n\n1. Edit the cluster configuration.\n![edit-cluster-config](../../images/MigContRun01.png)\n\n1. Change the value of the *Container Runtime* field from *docker* to *containerd* and save the changes.\n\n![switch-cre-config](../../images/MigContRun02.png)\n\n   ![switch-cre-config](switch-cre.png)\n\n\n## Activating the Config Change\n\nFor the change to take effect, you need to rotate your worker nodes once.\nThis can be done by either upgrading to a new Kubernetes version or by\ndoing a restart of the rollout of your MachineDeployment. While the prior\ncan be done in the Web UI easily (and is already covered by [here](/gks/clusterlifecycle/upgradingacluster/)),\nthe latter will be shown below.\n\n1. Check which container runtime your workers are currently using:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   ```\n\n   Here we see in the output that docker is still used as the container runtime.\n1. Restart the Machine Deployment as follows:\n    1. Click on the Machine Deployment of the cluster.\n![choose-machinedeployment](../../images/MigContRun03.png)\n\n    1. Click on the Restart button.\n![click-on-restart-button](../../images/MigContRun04.png)\n\n    1. Confirm the restart of the Machine Deployment.\n\n ![confirm-restart](../../images/MigContRun05.png)\n\n   Now one after another, a new machine will be added and an old machine will be removed after its workload has been transferred into the rest of the cluster. After the last old machine has been removed, the restart of the\n   MachineDeployment is complete.\n2. Now check again, which container runtime powers your worker nodes:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   ```\n\nThis concludes the migration of your Kubernetes clusters container runtime\nfrom *docker* to *containerd*.\n\n## Learn More\n\nMore background information on the container runtime engines for Kubernetes is available here:\n\n* <https://kubernetes.io/blog/2020/12/02/dockershim-faq/>\n* <https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/>\n",
    "initialResult": "---\ntitle: Migration Container Runtime Engine\n<<<<<<< HEAD:docs/_imke/clusterlifecycle/clustermigrations/containerruntimeengine/index.en.md\nlang: \"en\"\npermalink: /imke/clusterlifecycle/clustermigrations/containerruntimeengine/\nnav_order: 5000\n=======\nlang: en\npermalink: /gks/clusterlifecycle/clustermigrations/containerruntimeengine/\nnav_order: 4600\n>>>>>>> main:docs/_gks/clusterlifecycle/clustermigrations/containerruntimeengine/index.en.md\nparent: Cluster Lifecycle\nhas_children: false\n---\n# Migration Container Runtime Engine\n\n## General Container Runtime Information\n\nFor a long time now Docker (or rather the dockershim to be more precise) has\nbeen used as the default Container Runtime Engine in the underlying\ninfrastructure of Kubernetes. But maintaining this dockershim on the\ndevelopment side has become a heavy burden on the Kubernetes maintainers.\nTo reduce this burden the CRI standard has been implemented, but unfortunately\nDocker itself does not implement this standard (hence the dockershim!).\n\nWith the Kubernetes v1.20 release the deprecation of the dockershim has been\nannounced, scheduled for the release of v1.24. So to be able to upgrade to\nKubernetes v1.24 we will need the Kubernetes nodes to run a different\ncontainer runtime engine which is CRI-standard compatible. For GKS this\nwill be containerd.\n\n## Changing the Container Runtime Engine Config\n\nTo upgrade from Docker to containerd the following steps are needed:\n\n1. Edit the cluster configuration.\n![edit-cluster-config](../../images/MigContRun01.png)\n\n1. Change the value of the *Container Runtime* field from *docker* to *containerd* and save the changes.\n\n<<<<<<< HEAD:docs/_imke/clusterlifecycle/clustermigrations/containerruntimeengine/index.en.md\n=======\n![switch-cre-config](../../images/MigContRun02.png)\n\n>>>>>>> main:docs/_gks/clusterlifecycle/clustermigrations/containerruntimeengine/index.en.md\n## Activating the Config Change\n\nFor the change to take effect, you need to rotate your worker nodes once.\nThis can be done by either upgrading to a new Kubernetes version or by\ndoing a restart of the rollout of your MachineDeployment. While the prior\ncan be done in the Web UI easily (and is already covered by [here](/gks/clusterlifecycle/upgradingacluster/)),\nthe latter will be shown below.\n\n1. Check which container runtime your workers are currently using:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   ```\n\n   Here we see in the output that docker is still used as the container runtime.\n1. Restart the Machine Deployment as follows:\n    1. Click on the Machine Deployment of the cluster.\n![choose-machinedeployment](../../images/MigContRun03.png)\n\n    1. Click on the Restart button.\n![click-on-restart-button](../../images/MigContRun04.png)\n\n    1. Confirm the restart of the Machine Deployment.\n\n ![confirm-restart](../../images/MigContRun05.png)\n\n   Now one after another, a new machine will be added and an old machine will be removed after its workload has been transferred into the rest of the cluster. After the last old machine has been removed, the restart of the\n   MachineDeployment is complete.\n2. Now check again, which container runtime powers your worker nodes:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   ```\n\nThis concludes the migration of your Kubernetes clusters container runtime\nfrom *docker* to *containerd*.\n\n## Learn More\n\nMore background information on the container runtime engines for Kubernetes is available here:\n\n* <https://kubernetes.io/blog/2020/12/02/dockershim-faq/>\n* <https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/>\n"
}

This is caused by line wrapping.


ImportError: No module named vss_connection

How to reproduce

I have executed 'pip install vsts' - see [A]
I have written the code to display the projects list [B]
I execute 'python vsts.py'

I am not interested by any other solution such as "run vsts-cli" :-)
An ERROR is generated:
c:\VSTS>python vsts.py
Traceback (most recent call last):
File "vsts.py", line 1, in
from vsts.vss_connection import VssConnection
File "c:\VSTS\vsts.py", line 1, in
from vsts.vss_connection import VssConnection
ImportError: No module named vss_connection
[B] list projects
https://github.com/Microsoft/vsts-python-api
[A] pip install vsts

c:\VSTS>pip install vsts
Requirement already satisfied: vsts in c:\python27\lib\site-packages
Requirement already satisfied: msrest>=0.4.5 in c:\python27\lib\site-packages (from vsts)
Requirement already satisfied: isodate>=0.6.0 in c:\python27\lib\site-packages (from msrest>=0.4.5->vsts)
Requirement already satisfied: requests-oauthlib>=0.5.0 in c:\python27\lib\site-packages (from msrest>=0.4.5->vsts)
Requirement already satisfied: requests~=2.14 in c:\python27\lib\site-packages (from msrest>=0.4.5->vsts)
Requirement already satisfied: certifi>=2017.4.17 in c:\python27\lib\site-packages (from msrest>=0.4.5->vsts)
Requirement already satisfied: enum34>=1.0.4; python_version < "3.4" in c:\python27\lib\site-packages\enum34-1.0.4-py2.7
.egg (from msrest>=0.4.5->vsts)
Requirement already satisfied: six in c:\python27\lib\site-packages (from isodate>=0.6.0->msrest>=0.4.5->vsts)
Requirement already satisfied: oauthlib>=0.6.2 in c:\python27\lib\site-packages (from requests-oauthlib>=0.5.0->msrest>=
0.4.5->vsts)
Requirement already satisfied: idna<2.7,>=2.5 in c:\python27\lib\site-packages (from requests~=2.14->msrest>=0.4.5->vsts
)
Requirement already satisfied: urllib3<1.23,>=1.21.1 in c:\python27\lib\site-packages (from requests~=2.14->msrest>=0.4.
5->vsts)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in c:\python27\lib\site-packages (from requests~=2.14->msrest>=0.4.
5->vsts)

try running: python -m pip list, which will list all packages installed for the instance of python that is in your path.  If vsts is not listed, you can run python -m pip install vsts, to install it for this instance of python.

this is happening for me too. python -m pip list is returning as expected.
Package                       Version
----------------------------- ---------
vsts                          0.1.14

@eltoncezar, can you share sample code and stack trace of the error?

Sure. Sample code is the same as provided in Getting Started. I only changed the token and team_instance variables.
I also tried to add the path C:\Python27\Lib\site-packages\vsts to the PYTHONPATH var.
Stack trace:
$ cd "c:\dev\python" ; env "PYTHONIOENCODING=UTF-8" "PYTHONUNBUFFERED=1" "C:\Python27\python.exe" "c:\Users\elton.cezar\.vscode\extensions\ms-python.python-2018
.7.1\pythonFiles\PythonTools\visualstudio_py_launcher.py" "c:\dev\python" 62926 34806ad9-833a-4524-8cd6-18ca4aa74f14 RedirectOutput,RedirectOutput "c:\dev\pytho
n\vsts.py"
Traceback (most recent call last):
  File "c:\dev\python\vsts.py", line 2, in <module>
    from vsts.vss_connection import VssConnection
  File "c:\dev\python\vsts.py", line 2, in <module>
    from vsts.vss_connection import VssConnection
ImportError: No module named vss_connection

My enviroment is:
Python 2.7 running through VSCode on Windows 10 x64

Actually, I gave up. But thanks for your help!


Fix rpm-jenkins patching

need to blow away /jenkins/deploy/current in the jenkins-rpm script when a deploy gets detected as failing

Sorry :-) @ericvaandering how about this one?

Let's keep it.

@ericvaandering, this is fixed isn't it?

It's not causing problems anymore. We deploy from scratch.


Can't post visualization back to python

Hi developers,
i am using your cool tool to visualize a network. But i don't have the option to post my visualization back to python as you have in your tutorial on https://netwulf.readthedocs.io/en/latest/python_api/post_back.html Instead i have the option to upload or save a json. Screenshot of my display
I have tried to reinstall your package but it still only gives me the option to upload or save a json file.
What am i doing wrong?
kind regards

For some reason it works now :)
Awesome application that you guys have made.
Such a nice feature that you can model the network inside the app and then get the coordinates of each node back in python.
Makes plotting networks in matplotlib so much easier, thanks again!

Thanks for using it! Happy that it works for you :).


Location spoof mode added to home menu

To test user location posting:

Run the server
Approve geolocation access
Open javascript console (inspect element/f12)
Ensure message "server got location and response is 200" is in log
Ensure data is being sent on the network graph

To test location spoofing:

Run the server
Approve geolocation access
Click "enable spoof mode"
Click on map
Open javascript console (inspect element/f12)
Ensure message "server got location and response is 200" is in log
Ensure data is being sent on the network graph
Disable spoof mode
Verify location posting works again

Details:
Added spoof mode and button
Made spoof mode a toggle option
Modified posting code
Enabled location posting (sent as json file {"lat":lat, "lon":lon})
Got rid of unnecessary functions
TODO:
In template, ensure spoofing scripts and button only render if user is either gamemaster or superuser
i.e include {% if %} blocks to control who can access this feature

 Get user's current location and pass it to Django.


Gradle update to v3.2.1

To prevent build issues like "Could not find com.android.tools.build:gradle:2.3.1" in common CI system like Travis or Jitpack the gradle version and build tools need to be updated.

I fixed your Travis issue, but I have no permission to push in your branch, so I made a new PR https://github.com/googlemaps/android-maps-utils/pull/495 based on your changes.
To fix Travis, I don't handle api25 and switched to Android P immediate

Merged in #495
Thankyou


📃: Text Classification for Spam Detection

:red_circle: Title : Text Classification for Spam Detection
:red_circle: Aim : Create a text classification system to detect spam messages using machine learning techniques.
:red_circle: Brief Explanation :

Gather a dataset of text messages labeled as spam or not spam.
Preprocess the text data and extract relevant features.
Train a machine learning model (such as Naive Bayes, SVM, or logistic regression) to classify messages as spam or not spam.
Develop an interface where users can input text messages and receive predictions on whether they are spam or not.

Screenshots 📷

N/A

:white_check_mark: To be Mentioned while taking the issue :

Full name :
What is your participant role? (Mention the Open Source Program name. Eg. GSSOC, SSOC, JWOC, etc.)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

My name is Sharayu Anuse and I am a contributor in GSSOC-Extd 2024. Can you assign this issue to me?

Full name : Siddharth Gupta
GSSoc'24 Extended

Please assign this topic to me

@sid7219 @saniyaahemad12 tell me the approach and dataset used for the same?

Approach:
Dataset : Use the public dataset "SMS spam collection dataset"
Text preprocessing : using libraries like pandas, nltk to tokenizing, lowering, remove stop words and perform stemming or lemmatization.
Feature extraction : extract features using TF-IDF vectorizer
Train the model : for training, use naive bayes (good for classification tasks)
User interface : develop using streamlit components
Name : Ramu
Role : GSSoC contributor
Assign this issue to me, to work on this!

Here is the approach for text classification for spam detection
Data Collection: Use a labeled dataset like the SMS Spam Collection dataset.
Data Preprocessing:
Clean text by removing special characters and stopwords.
Tokenize and apply stemming/lemmatization.
Feature Extraction:
Use TF-IDF to convert text into numerical vectors.
Optionally, use Bag of Words model.
Model Selection:
Train models using Naive Bayes, SVM, and Logistic Regression.
Model Training and Testing:
Split data into training/testing sets, apply cross-validation.
Model Evaluation:
Use accuracy, precision, recall, and F1-score to evaluate performance.
Interface Development:
Develop a user interface with Tkinter for input and spam prediction.
If you like the technique please assign this topic to me.

@ramu-nukavarapu In PR attach the screenshot of the accuracy of the model during training and testing.

@Avdhesh-Varshney okay

i like to solve this issue please assign it to me
Name : Aakash


Move Folder

It should be possible to move empty folder and with planElements in a another directory.

Done :+1:


Added tutorials

This PR takes the tutorials that we wrote for Summit and adds them to the Maistra.io website.

Unrelated, but I still don't understand in which cases netlify uploads a preview and which it doesn't

This is interesting. I didn't know about the white/blacklisting with listchecker

/honk

/honk

Will be addressing these in a separate PR. Thanks for the comments.


chore: use get_type_hints

This PR switches from using __annotations__ to using get_type_hints, resolving forward refs

Is this part of PEP 649 or something? I am not up on this magic

It's a utility builtin to the typing and typing extensions modules.


Result for text exercies displays additional letters

Describe the bug
When viewing the result for a team text exercise, some characters stand  isolated from all other text blocks with - for me at least - no clear pattern
To Reproduce

so far, I have only seen this in EIST T02E01. The T01 text exercises and all "normal" text exercises worked without a flaw. Maybe @MaisiKoleni could comment further on what he did
Expected behavior

The text should be displayed "normally" as in the other text exercises.
Screenshots

Environment

 - OS: Windows 10 x64
 - Browser: Firefox
 - Version77.0.1

I might be mistaken, but I do not see a bug here.
From my experience of assessing text exercises, the assessing tutor made use of the automatic text block detection and did not manually mark the text blocks. (So for the headlines - Usability, Portability, ... - that are useful for structuring the contribution but do not contribute to the content of the explanation, no points are awarded)
As the headlines have not been assessed, they are not highlighted. Do I miss your point @NiOHar?

This is fixed.


[http] fix: use url.URL

url.URL from the standard library should be used instead of the global URL which comes from the dom lib.
Signed-off-by: Naseem<EMAIL_ADDRESS>Fixes #938
Seems to be the only two instances of the dom lib URL in both packages.
cc @dyladan @OlivierAlbertini

Codecov Report

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

@@            Coverage Diff             @@
##           master     #960      +/-   ##
==========================================
+ Coverage   94.75%   95.84%   +1.09%
==========================================
  Files         248      222      -26
  Lines       11288    10184    -1104
  Branches     1079      877     -202
==========================================
- Hits        10696     9761     -935
+ Misses        592      423     -169

Impacted Files
Coverage Δ

packages/opentelemetry-plugin-http/src/http.ts
97.57% <ø> (ø)

...ckages/opentelemetry-core/src/common/NoopLogger.ts
60.00% <0.00%> (-20.00%)
:arrow_down:

...metry-core/src/trace/instrumentation/BasePlugin.ts
81.57% <0.00%> (-5.27%)
:arrow_down:

...es/opentelemetry-exporter-collector/test/helper.ts

...entelemetry-plugin-xml-http-request/src/version.ts

...ckages/opentelemetry-web/test/registration.test.ts

...ackages/opentelemetry-web/src/WebTracerProvider.ts

...entelemetry-plugin-user-interaction/src/version.ts

...opentelemetry-context-zone-peer-dep/src/version.ts

.../opentelemetry-plugin-document-load/src/version.ts

... and 19 more


Mekanism Induction Matrix

Hey,
I'm unable to connect the program to an Induction Matrix.
It's giving me an error saying it can't find an energy storage.

I have tried connecting the wired modem to both the induction casing and the induction port (in input mode). Haven't tried the induction port on output mode. The network does recognize the Matrix (giving it the name "Induction Matrix_#" with a valid number for #) and modem turns red.

In this case, your Matrix is indeed recognized by the computer. It probably uses a different function to get the energy value from the Matrix (something different then "getEnergyStored()"). Since I am working on Version 3.0 of the program anyway, I'll take a look at this, too. This will take some more time though.
I recommend using a different Energy Storage in the meantime.

allright, thanks for you reply anyway. I'll try to find a solution for it as well. Looking forward to the 3.0 version.

by the way, do you know if the draconic energy core works with this program?

The Draconic Core works fine. You have to put the modem on one of the Energy Pylons.

just checked another program that could read current and max power levels in an induction matrix.
code they used was:
for max power --> cube.getMaxEnergy()
for current power --> cube.getEnergy()
full program code here:
http://www.computercraft.info/forums2/index.php?/topic/19381-power-monitor-program-works-with-any-mods-power-storage/
hope this helps


Add ability to set offset in consumer group

To reply message/debug someone might need to get messages from begging or specific offset

The docs say this: You can configure start offset for new consumers in settings (earliest, latest).
How do I go about view prior offsets in the tool?
I can only view new messages that come after I start the consumer.

The docs say this: You can configure start offset for new consumers in settings (earliest, latest).
How do I go about view prior offsets in the tool?
I can only view new messages that come after I start the consumer.

@mblandgithub I have implemented some POC using debezium (Kafka connect) for publishing and Node.js subscription resolvers for consuming. I haven't used GraphQL PubSub interface because it has some obvious problems.
Debezium will publish messages in order (partitioning is based on table/id.
POC does couple things
Producing

Debezium publishes events from datasource
Events are used as marker for change (not containing data itself for speed and low storage)

Consuming

New consumer group created everytime user connect (for each user). Client side need to always send unique ID)
Subscription requires sending offset from client. One can also persist offsets somewhere on backend but that will be less reliable to network glitches
Each message is send back with offset to client that keeps it in cache

This is complex so I'm trying to see if there is a way to make some simple sample app and blog post but not convinced yet that this is the most elegant solution (it is definitely opiniated one

@mblandgithub I have implemented some POC using debezium (Kafka connect) for publishing and Node.js subscription resolvers for consuming. I haven't used GraphQL PubSub interface because it has some obvious problems.
Debezium will publish messages in order (partitioning is based on table/id.
POC does couple things
Producing

Debezium publishes events from datasource
Events are used as marker for change (not containing data itself for speed and low storage)

Consuming

New consumer group created everytime user connect (for each user). Client side need to always send unique ID)
Subscription requires sending offset from client. One can also persist offsets somewhere on backend but that will be less reliable to network glitches
Each message is send back with offset to client that keeps it in cache

This is complex so I'm trying to see if there is a way to make some simple sample app and blog post but not convinced yet that this is the most elegant solution (it is definitely opiniated one

I agree this would be nice. I've been wanting to redo the consumer part a bit for a while to make it a bit more flexible instead of just letting a single consumer group be registered.
Similar to producers being created with a kafka file, i've been thinking of a similar approach to consumers. Something along the lines of this (needs some more thoughts but should show the gist of it):
CONSUMER test
topics: topic-a
from: [earliest | latest | <offset>]
to: [latest | <offset>]

I agree this would be nice. I've been wanting to redo the consumer part a bit for a while to make it a bit more flexible instead of just letting a single consumer group be registered.
Similar to producers being created with a kafka file, i've been thinking of a similar approach to consumers. Something along the lines of this (needs some more thoughts but should show the gist of it):
CONSUMER test
topics: topic-a
from: [earliest | latest | <offset>]
to: [latest | <offset>]

@jlandersen we discuss about this idea with kafka file with @fbricon but we wonder how to manage menu Start consumer from the treeview and kafka files (ex: menu from treeview item must introspect all kafka files in workspace to know which start consumer exists?)
That's why we think to manage those start consumer with a webwiew like I tried to explain in https://github.com/jlandersen/vscode-kafka/issues/88 liek Conduktor does:

Because there is not only offset confuguration, there is format configuration (to envoid encoding problem), etc
Perhaps we could manage start consumer with both solution (kafka file and webview), but I though next week to start to manage  "start consumer) with webview. Are you OK with that?

@jlandersen we discuss about this idea with kafka file with @fbricon but we wonder how to manage menu Start consumer from the treeview and kafka files (ex: menu from treeview item must introspect all kafka files in workspace to know which start consumer exists?)
That's why we think to manage those start consumer with a webwiew like I tried to explain in https://github.com/jlandersen/vscode-kafka/issues/88 liek Conduktor does:

Because there is not only offset confuguration, there is format configuration (to envoid encoding problem), etc
Perhaps we could manage start consumer with both solution (kafka file and webview), but I though next week to start to manage  "start consumer) with webview. Are you OK with that?

@jlandersen we discuss about this idea with kafka file with @fbricon but we wonder how to manage menu Start consumer from the treeview and kafka files (ex: menu from treeview item must introspect all kafka files in workspace to know which start consumer exists?)
That's why we think to manage those start consumer with a webwiew like I tried to explain in #88 liek Conduktor does:

Because there is not only offset confuguration, there is format configuration (to envoid encoding problem), etc
Perhaps we could manage start consumer with both solution (kafka file and webview), but I though next week to start to manage "start consumer) with webview. Are you OK with that?

I wouldn't consider a consumer from a file the same as "Start consumer" from the menu, but rather they are two separate approaches to start / register a consumer.

The quick right-click and Start consumer from menu i'd like to keep as an easy way to create a consumer for a particular topic
Consumer from files is the more detailed approach to creating one, which can also be shared in a project repository, similar to producers. It is not related to a consumer started from the menu though. You could right click start consumer on topic A and create a consumer via file to consume topic A at the same time.

I'm definitely open to having a UI for starting a consumer as well, but functionally I'd expect it to work exactly the same as from whatever format we use in files (that is, any field you'd have in the UI would map to a property in the file format).

@jlandersen we discuss about this idea with kafka file with @fbricon but we wonder how to manage menu Start consumer from the treeview and kafka files (ex: menu from treeview item must introspect all kafka files in workspace to know which start consumer exists?)
That's why we think to manage those start consumer with a webwiew like I tried to explain in #88 liek Conduktor does:

Because there is not only offset confuguration, there is format configuration (to envoid encoding problem), etc
Perhaps we could manage start consumer with both solution (kafka file and webview), but I though next week to start to manage "start consumer) with webview. Are you OK with that?

I wouldn't consider a consumer from a file the same as "Start consumer" from the menu, but rather they are two separate approaches to start / register a consumer.

The quick right-click and Start consumer from menu i'd like to keep as an easy way to create a consumer for a particular topic
Consumer from files is the more detailed approach to creating one, which can also be shared in a project repository, similar to producers. It is not related to a consumer started from the menu though. You could right click start consumer on topic A and create a consumer via file to consume topic A at the same time.

I'm definitely open to having a UI for starting a consumer as well, but functionally I'd expect it to work exactly the same as from whatever format we use in files (that is, any field you'd have in the UI would map to a property in the file format).

'm definitely open to having a UI for starting a consumer as well, but functionally I'd expect it to work exactly the same as from whatever format we use in files (that is, any field you'd have in the UI would map to a property in the file format).

Ok so I will give up webview UI stuff for the moment and I will start to work on kafka files with CONSUMER. @fbricon is it OK for you?

'm definitely open to having a UI for starting a consumer as well, but functionally I'd expect it to work exactly the same as from whatever format we use in files (that is, any field you'd have in the UI would map to a property in the file format).

Ok so I will give up webview UI stuff for the moment and I will start to work on kafka files with CONSUMER. @fbricon is it OK for you?

I'm working on start/stop CONSUMER with kafka file. See the demo https://github.com/jlandersen/vscode-kafka/pull/98#issuecomment-770436966

I'm working on start/stop CONSUMER with kafka file. See the demo https://github.com/jlandersen/vscode-kafka/pull/98#issuecomment-770436966

Fixed with https://github.com/jlandersen/vscode-kafka/pull/98 by using from  into CONSUMER kafka file.
See documentation https://github.com/jlandersen/vscode-kafka/blob/master/docs/Consuming.md#kafka-file for more information.


v3.8.0-release

Describe your changes and provide context
Testing performed to validate your change

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

Project coverage is 62.64%.  Consider uploading reports for the commit 4e2d206 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1420      +/-   ##
==========================================
- Coverage   62.69%   62.64%   -0.05%
==========================================
  Files         257      257
  Lines       16867    16867
==========================================
- Hits        10574    10566       -8
- Misses       5791     5798       +7
- Partials      502      503       +1

Files
Coverage Δ

app/upgrades.go
40.74% <ø> (ø)

... and 2 files with indirect coverage changes


bower.json

in bower.json
"main": "./dist/ng-datepicker.js",
but will be
"main": "./dist/ng-eternicode-datepicker.js",

Thanks for the hint! I'll fix that.

Is project alive?


Ensure long EF titles do not outgrow their cells

Cell titles can be long, can we improve the way they are shown?

They don't! We're good there. The font was resized in master already, closing.


hyperspace: init at 1.1.4

Motivation for this change
Mastodon client :).
(electron-based)
FWIW, the license is new to us and not widely used.
Added it to the list, but am unsure how it should be handled.
Hopefully it's alright to include software under this license,
but I mention it because I would appreciate a second opinion O:).
Fixes #57357.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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 nix-review --run "nix-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)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

The software works, would be nice to have it in nixpkgs...

Updates/notes for anyone reading this in the future:

NPL is a bit of a mess, it seems? Not free (I think we discussed this somewhere previously too), according to hyperspace discussion on changing its license (not linking to avoiding bombing them with mention, LMK if curious/can't find), bumped to v4 from the v1 included with this PR originally.  Authoritative URL for this version is tricky, it seems NPL author wants folks using v7+ and deprecated the v4 repository ... anyway this seems correct for hyperspace, which explicitly uses "NPLv4".
As I recall, the runtime deps are needed because they're looked for but not linked against explicitly, now that we have to pull in mesa for libgbm I'm unsure if that makes sense re:libGL.  Leaving as I think libGL is preferred unless mesa itself is explicitly needed.
There's an appimage alternative they provide which might be preferred (if simpler to package), I don't know if there's a reason I went for the .deb.  Seems less opaque :).  In theory we could maybe bundle this ourselves but I haven't explored this, as the tooling isn't very Nix-compat (node).  Staying the course for now.

Addressed review feedback, thank you! Sorry for delay! :)

Tested the result and seems to work as expected so far.
The icon is... X11 logo? Which suggests something strange happening but I don't think is critical.
--
Well anyway, here's the latest hyperspace :).

Please rebase

Closing because of lack of activity from the author. Please re-open if you plan to work on this.


Make the system stop auto-rebooting for 10 seconds when a core crashes at boot time.

Let the system stop automatically restarting for 10 seconds when the core crashes during startup, so that users can have time to record startup errors, and you can analyze the problem.
e.g BSOD
https://github.com/helloSystem/ISO/issues/455
https://github.com/helloSystem/ISO/issues/457
https://github.com/helloSystem/ISO/issues/413
https://github.com/helloSystem/ISO/issues/335

You can add the following line to the /etc/sysctl.conf file:
kern.panic_reboot=0

We have this:
https://github.com/helloSystem/ISO/blob/b80e110fca87277dee732979a711e6a209e01ecd/overlays/boot/boot/init_script#L153
So, when booting in verbose or single user mode, it should wait 30 seconds before rebooting. Please comment here if it doesn't work.

In A1278, it will not restart immediately when there is self-suspend for the first time, but it will restart immediately when it is used next time.  Version:0.9.0


added name for privkey.pem

on OS X, using libressl v2.6.5, needed to provide explicit name for keyout file so that later step referencing privkey.pem would work

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

expired


bump upper bound on base

This library does not define any Monoid instances, so there's no breakage from Semigroup becoming a superclass of Monoid.

Done