Use a real browsers with Xvfb

Hello
Just wondering if you have considered using a real browser like Firefox or Chrome? (with Xvfb)
Most of all just a question, PhantomJS has always looked kind of unmaintained to me (no commits since 26 may and 1500+ issues).
Regards Kristian

Hey Kristian
I never considered using something else than PhantomJS for Screeenly, but I'm open for new technologies.
Will test it in the future.
(There's also something happening with a headless Chrome browser: https://twitter.com/samccone/status/739166801427210240)

(There's also something happening with a headless Chrome browser: https://twitter.com/samccone/status/739166801427210240)

Nice, in my research before this issue I stumbled on moz-headless-screenshot, but it was never merged it seems (https://bugzilla.mozilla.org/show_bug.cgi?id=headless).
In some older research I also stumbled on Selenium, which seems to be the perfect framework to use for taking screenshot.
Today I also stumbled on https://github.com/SeleniumHQ/docker-selenium , and Facebook has made a PHP framework to interact with Selenium (https://github.com/facebook/php-webdriver/wiki/Taking-Full-Screenshot-and-of-an-Element).
You could in theory combine it with docker-machine to get some sort of auto-scaling.
Now the big question is how it performance, (memory usage and how fast it can generate a screenshot). Running Firefox 45.0 currently (selenium/standalone-firefox-debug:2.53.0) which use 192MB which is much I think, not sure how fast Selenium can take a screenshot.

So I did a little benchmark.
docker run -t -i -p 4444:4444 -p 5900:5900 selenium/standalone-firefox-debug:2.53.0
and the following python file:
from selenium import webdriver

driver = webdriver.Remote("http://localhost:4444/wd/hub", webdriver.DesiredCapabilities.FIREFOX.copy())
driver.get("http://www.google.com")
driver.get_screenshot_as_file('google.png')
driver.quit()

$ time python2 test.py

real	0m5.970s
user	0m0.140s
sys	0m0.013s

It use a lot of the time to start Firefox, not sure how much time we save by "prestart" Firefox.
screeenly.com currently use 2 sec for the whole request, hm.

More benchmark
import time
from selenium import webdriver

driver = webdriver.Remote("http://localhost:4444/wd/hub", webdriver.DesiredCapabilities.FIREFOX.copy())
start_time = time.time()
driver.get("http://www.google.com")
driver.get_screenshot_as_file('google.png')
driver.quit()

print("--- %s seconds ---" % (time.time() - start_time))

$ time python2 test.py
--- 2.00333404541 seconds ---

real	0m6.207s
user	0m0.143s
sys	0m0.013s

2 seconds isn't bad, but then you need to have x Firefox instances running all time.

Thanks for your benchmarks!
I know screeenly isn't the fastest product out there. In my eyes it's still an early versions and it's still just a side project which runs on a small server.
As I said earlier, I will try to work on screeenly in the upcoming days / weeks. I really appreciate your work here and will try implementing it 😄.

node-webkit also looks like a good solution.
Good Things:

Easy to implement in node.js

var screenshot = require('node-webkit-screenshot');
var url        = process.argv[2];

screenshot({
    url : url,
    width : 1024,
    height : 1000,
    delay: 1
})
.then(function(buffer) {
    screenshot.close(); // Close Process
    var base64Image = new Buffer(buffer, 'binary').toString('base64'); // Generate base64 Image
    console.log(base64Image); // Output to console
});

### Bad Things:

Can't generate screenshot for 100% height; only pixel values
Can't set User Agent

### Things to consider

How does it perform when many requests are coming in

node-webkit also looks like a good solution.

It also require Xvfb it seems https://github.com/nwjs/nw.js/issues/769 .. If we gonna run X anyways, I still think a regular browser is the most ideal, but up to you :)

I'm closing this issue for now.
I'm still aware that screeenly doesn't work on 100% of all websites but I would like to move on and work on other projects in the future.
I'm still watching / observing projects which do screeeshot generation. If an opportunity opens to implement a new Screenshot Driver which works all the time I will gladly implement it.


Request for -> hot fix for 308 login error (challenge with + symbol) included in 4.38.1

Our iOS users are complaining of the following error while signing in

The operation couldn’t be completed. (com.facebook.sdk.login error 308.)

It appears to have been resolved in 4.38.1
https://github.com/facebook/facebook-objc-sdk/pull/922#issuecomment-436050897
I would greatly appreciate if you could upgrade the nuget packages.
Thanks 🙏

VS bug #751310

This will be updated in the following weeks.

Not sure about the rest but this error is easily reproducible in my iOS project. Very annoying as it aborts the login sequence and the user has to go through the entire sequence of Facebook screens again. Perhaps it deserves a higher priority? Thanks!

@zavalishin
In the meantime, I reverted to 4.35.0 and as far as I know it is working properly now.

Hello,
One of the apps I'm working has this issue as well.
Any ETA on when the new Facebook SDK NuGet package is released?

Just chiming in to say our app is affected by this as well. Looking forward to a fix for this issue.


[cxx-interop] Import ObjCPropertyDecl of type NS_OPTIONS fields as struct type

Try importing ObjCPropertyDecl field types the C++-Interop-NS_OPTIONS way. This will fix cases such as:
import UIKit

func f(gesture: UISwipeGestureRecognizer,
       direction: UISwipeGestureRecognizer.Direction) {
  gesture.direction = direction // error
}

because it will make sure the field inside class UIGestureRecognizer is of the enum-struct type and not the typedef-rawValue type when importing an ObjC class.
Note: Still working in test cases etc.

@swift-ci please test

@swift-ci please test

@swift-ci please test


Revert "Implement issue# 13996. Add File.tempFile."

Reverts D-Programming-Language/phobos#2956
because of https://issues.dlang.org/show_bug.cgi?id=14539

So what's the lesson here? We can't add a function because it increases the binary size? Ridiculous, please fix the compiler instead.

See https://github.com/D-Programming-Language/dmd/pull/4638 and Issue 13242 – imported aliases should be analyzed lazily.

The issue is this function cannot be added until whatever reason it bloats the executable size is fixed.

Auto-merge toggled on

This is why checks for executable size bloat should be in the test suite.

@MartinNowak do we have that check around yet? I recall you mentioned it at some point.

Yes, here https://github.com/D-Programming-Language/dmd/blob/82b031c22f18334a7edeff437260b6802070a9e3/test/runnable/test13117.d.
Someone should update the thresholds. We can lower the tolerance to maybe 1%, it cannot be zero because the would affect too many pull requests.

The issue is this function cannot be added until whatever reason it bloats the executable size is fixed.

Sure, but the right direction to fix bugs is going forward not backward.
It was a huge effort to get this functionality into phobos, and not it's reverted because of compiler issues the phobos devs aren't accountable for.

I'm sorry about that, but we should never pull something that causes regressions, even if it is not the fault of the new code. This is not about assigning blame.

Can we close the regression now? It's still open.

@MartinNowak instead of having a tolerance the better policy is to update it on a case basis where justified. @schveiguy yes, could you please close - thanks.


Ether-Proxy and MPOS

Hello,
i installed successfully the ether-proxy on my System. But now i want to configure it with the MPOS-System for the webinterface. I'm not sure about the config-file, in the global-inc.php of the MPOS i must configure the wallet and the algorithm.
What Kind of algorithm should i use? The documentation says following:
algorithm
•sha256d: Bitcoin and similar ones.
•scrypt: Litecoin and most of the all-coins.
•scryptn: Vertcoin and similar ones.
•x11: Darkcoin and similar ones
But for Ethereum??
Also i have a Problem with the rpc-wallet configuration. What port should i use? The web Port 8080, or the rpcport, that is in the geth.config? What username should i use, the wallet-adress or the username of the webinterface of ether-proxy?
Thanks for helping.
Best regards
Zimbo

I don't know.


add prefix filter

Adds the prefix filter to filters

Coverage increased (+0.1%) to 93.782% when pulling 651cf88501982cf02da626baaca05bb5bacdff72 on add-prefix-filter into 367a300f2f5e563e2ab6d4fcb4486bdad8656e65 on master.

Coverage increased (+0.1%) to 93.782% when pulling 7f057dad9fef96b01d07778ca968eb75be1d1a5e on add-prefix-filter into 367a300f2f5e563e2ab6d4fcb4486bdad8656e65 on master.


Cannot install the extension using pip

I encountered the following error while installing the extension using pip.

try pip install git+https://github.com/NERSC/jupyterlab-recents


Document convolve and correlate

These were missing from the API docs previously. So this just makes sure they are included.
cc @beckernick @awthomp

Jenkins, test this please.

Jenkins CI test (for commit 6b1158020d61a0e58db2499556871c13e4c19ca0, target branch master) succeeded!

Please let me know if anything else is needed 🙂


[AutoPR apimanagement/control-plane] typo: apimanagement/control-plane/Microsoft.ApiManagement/apimbackends.json

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4511

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/3388


Run + Attach on Android

Running an app on android emulator (using Run on Android command) and after that attaching with Attach on Android Emulator configuration fails with Connection timed out.

+1

+1 For me this happens when I use the babel hook.

+1 but only if i "Attach on Android Device"
Getting debug port
device: 9edfd1d8 debug port: 40000
Preparing for debug
Attaching to debug application
Command failed: Connection timed out
Closing debug connection
Terminating debug session

would be very nice if that would be available again.
Thanks Nicky

+1 attaching on Android device.
Getting debug port device: <IP_ADDRESS>:5555 debug port: 40000 Preparing for debug Attaching to debug application Command failed: Connection timed out Closing debug connection Terminating debug session

Mine is doing the same
Getting debug port device: emulator-5554 debug port: 40000 Preparing for debug Attaching to debug application Command failed: Connection timed out Closing debug connection Terminating debug session

Having the same issue when doing "launch with android"-
Command failed: Can't connect. Check the application is running on the device

+1. Have the same error. But it works if I start my app from terminal and then debug with "request": "attach"

+1

I've tried to reproduce this with 0.7.2 and honestly can't reproduce it. I tried tns create test and tns create test2 --tsc (the latter is TS based, so has hooks).
The I ran the apps and attached successfully to the running processes. I also ran on Android from the debugger dropdown and again everything seems fine.
So please reopen if you're on 0.7.2 (or newer) if you still experience this issue, but when doing so, please also include a demo app reproducing the issue so we can take an even closer look.


Larastan undefined property when accessing model properties

Hello,
First off I want to say thank you for all the hard work you've put into this amazing package.
I ran into an issue where Larastan is giving me errors when I access model properties that were defined in migrations using the package's Blueprint class. For example, given the following user migration:
<?php

use Illuminate\Database\Migrations\Migration;
use Tpetry\PostgresqlEnhanced\Schema\Blueprint;
use Tpetry\PostgresqlEnhanced\Support\Facades\Schema;

class CreateUsersTable extends Migration
{
    public function up()
    {
        Schema::create('users', function (Blueprint $table) {
            $table->uuid('id')->primary();
            $table->string('name');
            $table->caseInsensitiveText('email')->unique()->index();
        });
    }
}

Calling properties on the model with $user->name or $user->email will give the following error:
------ ----------------------------------------------------------
  Line   Data/AuthData.php
 ------ ----------------------------------------------------------
  49     Access to an undefined property App\Models\User::$name.
  51     Access to an undefined property App\Models\User::$email.
 ------ ----------------------------------------------------------

It's easy enough to work around by annotating the model.
/**
 * @property string $name
 * @property string $email
 */
class User extends Authenticatable

But since I'm using the package's phpstan extension I figured I'd ask if this is expected functionality or if I'm missing something obvious.
Thanks again!

Environment Details
composer.json
"php": "^8.1",
"laravel/framework": "^9.43",
"nunomaduro/larastan": "^2.2.9",
"tpetry/laravel-postgresql-enhanced": "^0.23.0"

phpstan.neon
includes:
    - ./vendor/nunomaduro/larastan/extension.neon
    - ./vendor/tpetry/laravel-postgresql-enhanced/phpstan-extension.neon

parameters:
    level: 8

Is the name property correctly detected if you use Laravel‘s blueprint and schema classes? You have to temporary use a string column for email to test it?

The migrations are in the default location under database/migrations and it's correctly detected when using Laravel's blueprint class. I was already using Larastan in my app and it only started giving errors when I added this package's Blueprint class to a few migrations.
I was able to reproduce the issue on a fresh Laravel install:
https://github.com/benbjurstrom/laravel-issues
In the example repo above, the users migration uses the blueprint class from this package and the posts migration uses the Laravel one. In the app the table properties are accessed in app/Data/UserData.php and app/Data/PostData.php respectively.
If you run
git clone https://github.com/benbjurstrom/laravel-issues.git
composer install
cd laravel-issues
php vendor/bin/phpstan analyse -c ./phpstan.neon

You get errors for accessing unknown User properties but not for Post.
 ------ ----------------------------------------------------------
  Line   Data/UserData.php
 ------ ----------------------------------------------------------
  19     Access to an undefined property App\Models\User::$name.
  20     Access to an undefined property App\Models\User::$email.
 ------ ----------------------------------------------------------

When testing this out one thing I've noticed is you sometimes don't see changes until you clear the phpstan cache with vendor/bin/phpstan clear-result-cache
Appreciate you taking a look. As I mentioned for now I can work around this by annotating the model so it's not super urgent.

@canvural Could it be that the larastan code checks for a specific class to be used and can't work with a class extending the default Laravel one? The email issue is totally understandable as Larastan doesn't know how to handle it. Could a plugin add those definitions?

I've worked on a fix to Larastan so that Eloquent attributes are still detected when my schema migrations are used (nunomaduro/larastan#1485).
As the Larastan package won't know the type information of these columns, they are mixed instead of a more correct one. So annotations are still needed for the email column to identify them as string correctly. The idea of @canvural could be implemented to add aliases but I am planning to add custom types soon and the suggested approach would fail there. So I will not go further that way, having them identified as mixed by default is enough for me.

With the newest Larastan release all PostgreSQL migration blueprints are now handled correctly.


HDDS-1817. GetKey fails with IllegalArgumentException.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
74
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

0
mvndep
23
Maven dependency ordering for branch

+1
mvninstall
616
trunk passed

+1
compile
373
trunk passed

+1
checkstyle
77
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
877
branch has no errors when building and testing our client artifacts.

+1
javadoc
162
trunk passed

0
spotbugs
430
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
622
trunk passed

_ Patch Compile Tests _

0
mvndep
26
Maven dependency ordering for patch

+1
mvninstall
549
the patch passed

+1
compile
366
the patch passed

+1
javac
366
the patch passed

+1
checkstyle
68
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
615
patch has no errors when building and testing our client artifacts.

+1
javadoc
147
the patch passed

+1
findbugs
638
the patch passed

_ Other Tests _

+1
unit
340
hadoop-hdds in the patch passed.

-1
unit
1944
hadoop-ozone in the patch failed.

+1
asflicense
41
The patch does not generate ASF License warnings.

7719

Reason
Tests

Failed junit tests
hadoop.ozone.client.rpc.TestSecureOzoneRpcClient

hadoop.ozone.client.rpc.TestMultiBlockWritesWithDnFailures

hadoop.ozone.client.rpc.TestOzoneAtRestEncryption

hadoop.hdds.scm.pipeline.TestRatisPipelineCreateAndDestory

hadoop.ozone.client.rpc.TestBlockOutputStreamWithFailures

hadoop.ozone.TestMiniOzoneCluster

hadoop.ozone.client.rpc.TestOzoneRpcClient

hadoop.ozone.om.TestScmSafeMode

hadoop.ozone.om.TestOzoneManager

hadoop.ozone.client.rpc.TestOzoneRpcClientWithRatis

Subsystem
Report/Notes

Docker
Client=19.03.0 Server=19.03.0 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1152/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1152

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 0bc089c7fcc3 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / cb69700

Default Java
1.8.0_212

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1152/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1152/1/testReport/

Max. process+thread count
4192 (vs. ulimit of 5500)

modules
C: hadoop-hdds/common hadoop-hdds/server-scm U: hadoop-hdds

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1152/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

@nandakumar131  Thank you for the contribution. I have committed this patch to both the trunk and Ozone-0.4.1 branches.


method callbacks should be called on main queue by default or configurable queue

Right now METMethodInvocation executes both _receivedResultHandler and _completionHandler. On the queue associated with the METMethodInvocationCoordinators NSOperationQueue.
This isn't a bug because you dont make any guarantees that callbacks be called on the main thread. But I'm going to suggest that this is much clearer to the users of the lib. API when calling methods in METDDPClient currently looks like this:
[self.ddpClient logoutWithCompletionHandler:^(NSError *error) {
      // WE'RE ON SOME BACKGROUND QUEUE HERE
}];

This forces the user to dispatch back to main queue where in fact I believe that will be the most common use case.
What do you think @martijnwalraven ?

Also if you have any suggestions on where to start in a pull request for this let me know.  I started working here to dispatch_sync back to main queue there, but this breaks the unit tests as they execute this method directly on the main thread.  Also dispatch_async here breaks unit tests as it can't verify that that handler is invoked after data updates are flushed. See this test;

Same goes for global NSNotifications that are exposed in METDDPClient

I completely agree. In most cases, being called back on the main queue is what you want so this should be the default to avoid a common source of bugs. Ideally, the queue would indeed be configurable. As far as I know, there is no reliable way to default to the queue that called a method (dispatch_get_current_queue is deprecated). We could add a queue: argument to all methods that take a callback block and that defaults to the main queue (but that wouldn't work for notifications) or specify this at a more global level. A callbackQueue property on METDDPClient is probably sufficient for most uses (other name suggestions welcome).
I'd have to look more into this to be sure, but maybeInvokeCompletionHandler seems like the right place to dispatch to a different queue. That might require changes to the unit tests. In other places, I use XCTestExpectation/waitForExpectationsWithTimeout: to test async code. Here the issue seems to be that I wanted to test that the callback isn't invoked when only one of didReceiveResult:error and didFlushUpdates: is called. But I don't like the dependency on synchronous invocation and would prefer to find another way to test this.
If you have any ideas about this, please try them out and let me know or make a pull request. I probably won't have time to work on this myself before next week.


Ruc CI both with sqlite and postgres

closes #908
Checklist before merging

[ ] I added an appropriate entry to CHANGELOG.md

Thanks @ychiucco! I've nothing to add, please go ahead and merge when it's ready.


WIP - sort composite tags immediately before serializing them

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Current dependencies on/for this PR:

main:

PR #23454 👈

This comment was autogenerated by Freephite.


Scrollable Results on Search Component

I'm displaying a large list of items when the user do a query in the Search Component, this is fine for Computer Users, but when it displays on mobile, the keyboard overlaps almost the whole list and can't be scrolled, so I wonder if there is a way to make it renderize a list that is scrollable.
I tried using CSS overflow: scroll; but it show a scroll in the SearchBar Component with the results within and it's completely unreadable.
I can show the code if it's needed

I'm not that is actually a bug, please move this to StackOverflow where it can be clarified.

I didn't understand your message, "I'm not that is actually a bug", it's a bug or not?


Support selective module loading

First, excellent work on this - it's saved me a fair bit of time and I really appreciate that. We're using your popover binding, but can't load in everything else because we have some conflicting utilities. We also have a custom template engine in place (for the amd-helpers) as well as our own version of the string template engine, so it would be tricky to try to include the whole library. Right now, we've pasted it (along with the utils) into a file but I would much prefer to require this in directly. It would be great if there was some way we could require in just the things we need like the popover binding. Perhaps you could write each file as its own AMD module so they could be required directly?
Alternatively, some sort of config option to alias or namespace the bindings might also work, but we'd still need a way to opt out of the template engine.

Another alternative might be to put each thing behind a set of initialization functions like https://mbest.github.io/knockout.punches/ does. You could have one for each binding and convenience once that include them all, etc.

Thank you for you comment!
I have thought about 2.0 version, which will provide each binding as umd module.
Also it may allow usage of some initialization options to customize binding namespace, if you want include all of bindings.
I have already made some experiments with this, so when I will have enough time, I think, I implement this feature.


Pretty much the same as before

Just an update of the underlying pogoprotos.
Probably need to do this again when Charizard gets its new move

This repo is now deprecated. See issue #47.
Please create a merge request on https://github.com/pokemongo-dev-contrib/pokemongo-game-master


bug(python): connect storage minio-s3

LanceDB version
v0.13.0
What happened?

When I use minio to store lancedb, I connect and cannot connect. Using connect without async, according to the code, there is api_key, region and async connection, even if I put all the mino-s3 parameters, are unable to connect
Are there known steps to reproduce?
No response

Hi there. I can't see the full error because it is cut off in our screenshot. But based on your parameters, I'm guessing it looks something like:

I would like to use MinIO object storage. Has anyone gotten this to work? I tried the tutorial at https://blog.min.io/lancedb-trusted-steed-against-data-complexity/  however, it comes back with this error:
OSError: LanceError(IO): Generic S3 error: Error performing list request: Error after 0 retries in 5.288µs, max_retries:10, retry_timeout:180s, source:builder error for url (http://localhost:9002/lance?delimiter=%2F&list-type=2&prefix=data-table-test.lance%2F_versions%2F): URL scheme is not allowed, /home/runner/work/lance/lance/rust/lance-table/src/io/commit.rs:104:26

It looks like your endpoint URL has the http scheme. That means it's not a secure connection. (Different from a URL that starts with https.) We require in that case you pass "allow_http": true in your storage options. This is in our docs under "Local servers".

Hi there. I can't see the full error because it is cut off in our screenshot. But based on your parameters, I'm guessing it looks something like:

I would like to use MinIO object storage. Has anyone gotten this to work? I tried the tutorial at https://blog.min.io/lancedb-trusted-steed-against-data-complexity/  however, it comes back with this error:
OSError: LanceError(IO): Generic S3 error: Error performing list request: Error after 0 retries in 5.288µs, max_retries:10, retry_timeout:180s, source:builder error for url (http://localhost:9002/lance?delimiter=%2F&list-type=2&prefix=data-table-test.lance%2F_versions%2F): URL scheme is not allowed, /home/runner/work/lance/lance/rust/lance-table/src/io/commit.rs:104:26

It looks like your endpoint URL has the http scheme. That means it's not a secure connection. (Different from a URL that starts with https.) We require in that case you pass "allow_http": true in your storage options. This is in our docs under "Local servers".

I see that the connection to minio is successful but I can't do anything with LanceDB's database. I tried both LanceDB's method and minio's suggested method and both have the same problem.

That's really odd :/ I don't know why minio would timeout like that. Are you able to successfully use things like the AWS cli to upload and download data to it?


Add Module to PowerShell Gallery

Is there anything that's preventing PowerCommander from being added to the PowerShell Gallery?
The use case would be to enable installation via Install-Module rather than copying the module in to %USERPROFILE%\Documents\WindowsPowerShell\Modules or C:\Program Files\WindowsPowerShell\Modules manually. More or less like how Nuget functions for the SDK itself.

Thank you for feedback.
Nothing prevents PowerCommander from being published to the PowerShell Gallery.
We just haven't had a request yet.
The request ticket is created.

Thank you for the quick reply! It would really help out to ease distribution/installation of this module if you all are able to get it published on to the gallery the regular.

I agree. A PowerCommander PS module would be helpful for us as well.

PowerCommander module was added as an example of using .Net SDK with PowerShell.
It's never been targeted as a mature "product" that is ready to be published to the PowerShell Gallery.

Even if this is a beta product, I think it would benefit all users to publish it to the Gallery.

@sk-keeper is this still the case? Looks like this module does see some development from time to time? Maybe you will reconsider adding it to the gallery now?

PowerCommander is finally published to PowerShell Gallery.
A few cmdlets have been renamed to comply with cmdlet naming convention.


create a --quick-start option

default configuration is for a production grade cluster.  however, this is not a great user experience for a new user so we should add a quick-start config to create a small and useable cluster to explore k8s with.

we may want to have miltpile default configs later but for now we don't need it


[Question] Element selector

Hello! Milkdown seems wonderful, I just have one basic question:
In the "Getting Started" code sandbox here where/how is the HTML container element being created or selected? (e.g. something like document.body.appendChild)
I dug into the source code to see if it was related to Editor or Context. I looked at the Vue and React implementation, went over some of the tests, etc. But sadly all my webdev experience has failed me, and I could not find the answer. I'm sure there's something very obvious and simple I'm missing.

Never mind, a Github search of document.body did the trick.
Here's the relevant doc for anyone with the same question:
https://github.com/Saul-Mirone/milkdown/blob/f9eae01c024ce04b852c6e7c001be561de8621b7/gh-pages/pages/guide/interacting-with-editor/index.md


Add dashboard 'view'

Rendered based on database queries

 Dashboard - list of requests

 Dashboard - open and closed

 Dashboard - time of request


Lack of important context on git errors

When syncing, colligo does not display important context (ex: directory) when displaying errors from git. This may make diagnosing more difficult than necessary.
% colligo --sync
Parsing manifest file: manifest.xml
Synchronize all projects
ERROR [colligo::git_version_control] [some/project] error: Your local changes to the following files would be overwritten by checkout:
        somefile.h
Please commit your changes or stash them before you switch branches.
Aborting

Error: CheckoutFailed

We can see which project failed, but we cannot directly know the corresponding directory, except by looking into the manifest file.

This will be resolved in the next release (v0.3.0).

Fixed in v0.3.0


Unnecessary Alert

The anticheat only clears progress if you have both less than 10 attempts and 50 jumps, yet the mod triggers an alert if either one of the conditions is true.

I tested this by saving and loading my stats onto my phone, and an insane 8 star that I beat in less than 10 attempts but with more than 50 jumps loaded complete entirely fine.

fixed in v1.0.1


Flickering of boards when course information is opened

Most boards flicker when opened to see course information, some do not.

I assume this refers to the fact that we have to fetch data for grade distribution, schedule of classes, etc. so initially those sections are empty until the data is received half a second later. While we can't do anything about needing to fetch data, we can implement a skeleton mode that displays an empty gray box of the same height/width of the information displayed while we are waiting for a response. This can prevent the section headings and width of the popup from shifting around.
https://github.com/icssc/peterportal-client/assets/8922227/140dc832-aa9b-4376-81fb-dba96e36a7ab
e.g. YouTube skeleton mode


Add mouse support for Diff ATAC

Currently only human (hg38) is supported. Add mouse (mm10) support

Built new R docker

works with v1.0.1


subdivide human activities by habitat

From Jenn Brown:
There are many static graphs that are coming up in habitat-specific in modal windows when they shouldn't be. For example: contaminants in mussels is for rocky shores habitat not deep seafloor, but it is showing up in deep seafloor (screenshot below).

The content for contaminants and all human activities/impacts are currently organized into single files (eg _contaminants.Rmd), currently included in their entirety if included in a habitat. I could break this down further, but can you please describe which tabs should be included in which habitats?
You generally shared this information in image_priorities - Google Sheets, but would be fantastically helpful to explicitly match human activity/impact to habitats in this spreadsheet:

Human Activities & Impacts vs Habitats - Google Sheets


Postprocessing fails to execute if tagging fails

If tagging fails (season not found in tmdb), then postprocessing will fail:
2020-07-27 17:40:31 - resources.mediaprocessor - ERROR - Error processing
Traceback (most recent call last):
File "/usr/local/sma/resources/mediaprocessor.py", line 72, in fullprocess
postprocessor.setEnv(mediatype, tag.tmdbid, season, episode)
UnboundLocalError: local variable 'tag' referenced before assignment

4125cfd14349f8fa05199d6d4769ea40b877b8c9
That should fix it, good catch

It actually didn't fix:
2020-07-30 18:31:05 - resources.mediaprocessor - ERROR - Error processing
Traceback (most recent call last):
File "/usr/local/sma/resources/mediaprocessor.py", line 73, in fullprocess
postprocessor.setEnv(mediatype, tmdbid, season, episode)
UnboundLocalError: local variable 'tmdbid' referenced before assignment

4c6c389d5ae772d0c62596ee0741e501d1b65f32
Looks like there was a typo earlier in the script I didn't see (tmbdid instead of tmdbid), try now


Refactor Publisher EventQueue to match Subscriber

In this PR I'm converting the existing worker queue to the approach introduced in the Subscriber queue. The main differences are protecting properties object thanks to copying it before passing to a worker and inlining all results and result handlers into worker object, which makes it easier to follow. Additionally, I've extracted PublisherInteractor interface from CorePublisher interface, to separate functions used by workers from functions used by DefaultPublisher.
resolves #781

@QuintinWillison Interactor interface was introduced to separate methods exposed to the DefaultPublisher via CorePublisher interface. The idea was to extract methods used by workers to the PublisherInteractor interface.  Thanks for pointing that out. I'll add a clarifying comment to those interfaces.
I didn't take a closer look at those methods to limit the refactor scope as much as possible. I think it would be an excellent next step to reorganize the update family to match what you did on the subscriber side


Bug: milestone planning report

Describe the bug
Unable to produce milestone planning report
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Device : Samsung A51
OS: Android
App Type [e.g. chrome, edge, mobile app]
Version [e.g. 2.2.2]

Additional context
Add any other context about the problem here.

Not able to reproduce the described issue based on the limited information provided.
Device: Samsung S22 Ultra
OS: Android
App Type: Mobile app
Version: V2.3.0

This is an intermittent issue that relates to the Terrain API, I am aware of this and am working on a solution. It can also happen in the chrome/edge versions.

Triple up button part is sorted in the latest release. The API issue will be solved as part of V3 which will integrate summit and terrain much more closely to reduce these sorts of issues.

This is fixed in the new V3 version.


fix: night build matrix

Resolves: #192
trigger run result: https://github.com/apache/pekko-connectors-kafka/actions/runs/9364905011

@pjfanning, it looks like you approved this before this PR is ready for review. can you take a look again? the nightly builds ci seem passed.


Fixed Microwin Mount & Unmount, Reformatted

After mounting drive, the value of the mounted drive letter was valued null - I Have replace this with a txt prompt asking for the drive letter where it mounted.
Also fixed the unmounting of the ISO after copying files to the microwin folder in C:\
Ran through default Powershell formatter in VS Code

Hey @NovaWilliamClark first of all thank you for getting engaged, because of people like you projects like this thrive. A couple of things, please take a look at a projects as a whole, winutil is a compiled script, it contains many scripts, so you can't directly "fix" winutil you have to fix corresponding functions that get compiled into winutil. Another thing is instead of presenting people with a dialog for choosing the drive (fixing the symptom) it would be better to track down the issue and figure out why it is failing and fix it. Please take a look at Invoke-WPFGetIso.ps1 in the public folder. This line suppose to mount the iso and return it's object, if that is not happening something is going on
$mountedISO = Mount-DiskImage -PassThru "$filePath"

I will also try to repro this on my machines, so far I was unsuccessful.

Thank you for looking into it with me, turns out I suspect a windows service or something regarding the Mount-DiskImage  & Get-Volume functionality might have not been active or was corrupt on my machine. After a fresh Windows install, it the Mount-DiskImage is now returning a value and seems to be mounting an dismounting properly. Not entirely sure why but there we go!

@NovaWilliamClark I still think it is a legit issue, if someone doesn't have a couple of services that are not running, which is a huge probability in this community, we should catch that issue and show a warning and tell people what to do and which services to start. I would still encourage you to keep looking to see how we can find the issue and show a warning to the user. Or if you could tell me how to repro this issue I could look into it.

@NovaWilliamClark I still think it is a legit issue, if someone doesn't have a couple of services that are not running, which is a huge probability in this community, we should catch that issue and show a warning and tell people what to do and which services to start. I would still encourage you to keep looking to see how we can find the issue and show a warning to the user. Or if you could tell me how to repro this issue I could look into it.

I'll continue to look into it and see if I can find what might have been causing the issue


Add mini chatbot to the website

This chatbot gives answers to every question and give fast response to users , Assign me I like to work on it @mdazafar2

Hey @rutikakengal, sorry for the late reply. I’ve been a little busy due to my health condition. We have converted the entire code to Next.js and Tailwind CSS for better backend integration. You raised a good issue, but it was based on the old HTML and CSS version. We’ve moved everything to Next.js and Tailwind CSS. Please look into that, and don’t forget to join our Discord Serverfor the latest website announcements and features.

And also please give Star us ⭐

Please don't be discouraged. I will close the issue for now, but you can raise a new one that is truly needed for our website. Thank you.


fanout and fanoutSteps recurses even after exhausting input processes.

During fanout and fanoutSteps, the catMaybes removes the processes which are stopped. If all processes are stopped, then fanout and fanoutSteps still enter the Await.. mode, causing it to continue infinitely.
Handling fanout if no input processes are given, then the machine is stopped.

Thank you! Pushed to hackage.


fix: Prevent falsy values from breaking the app

Description
Fixes breaking of app when the source data inside menu items evaluated to NULL.
Fixes #19106
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual
Jest

Test Plan

https://github.com/appsmithorg/TestSmith/issues/2128

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

Tested this PR and LGTM

Tested Dynamic source data with null values
Tested and verified no app breakage
Tested Menu Button type in Table widget too
Tested in shared app too

/ok-to-test sha=2ac940b


edit size specification warning

Description

Urgency

[ ] Blocker
[ ] High
[ ] Medium

Requirements

Test all commands and procedures.
Build content locally and test for formatting/links.
Add redirects to dcos-website/redirect-files.
Change all affected versions (e.g. 1.7, 1.8, and 1.9).
See the contribution guidelines.

@sascala is this only applicable for 1.9, or does it need backported too?

It's only 1.9. In 1.8 the bug was bigger.


Missing sample in write2dgtjson.py when num_data=-1 ?

Hi !
I think there is a small bug in the script when num_data is set to -1.
I believe the intended effect is to evaluate on all samples in this case, but currently it is skipping the last one.
Let me know if my understanding is correct :)

Totally correct, thanks for finding this. It should now be fixed, but please re-open if you find it elsewhere.


[CHANGE] video/3gpp

The mimetype affected
Please enter the mimetype here
The change to make
Add/remove/change description or link, etc
Supporting link
A link to somewhere that authoritatively says why this change should be made

Not sure what this issue is for, this is on the site.


blazor after visual studio update throws some strange warnings

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
after update visual studio to 17.11.3
in  some componentsthat i open VS  throw some worning as
Severity	Code	Description	Project	File	Line	Suppression State
Warning (active)	TS1109	(JS) Expression expected.	Miscellaneous	D:\xxx\Components\Core\DialogConfirmComponent.razor__virtual.html__virtual.js	9

as on screen

the issue is with this:
 OnClick="@(async () => await Validate())">
i causing this isasue
 @onclick="@(async () => await Validate())"> or  @onclick="Validate"
this one do not throws the warning
but BOTH should be correct and not throw any warning as OnClick is valid APi call on mudblazor button
https://mudblazor.com/api/button#properties
please fix that in visual studio - the error should be different / maybe pointing into correct line at least... ?
why this was valid in older versions ? why it shows the exception now ?
before update there was no such things...?
Expected Behavior
-it should not throw this warning
-doubleclick sould take to error line?
Steps To Reproduce
Minimal Reproducible Example

Have 17.11.3 Visual Studio
Dotnet new install MudBlazor.Templates
New project  - MudBlazor Web APP (server rendering mode / global)
Open counter component. delete all.
Paste into this counter component

    <MudButton Variant="Variant.Filled" Color="Color.Primary" DropShadow="false" OnClick="@(()=>blabla())">Validate</MudButton>
@code {

    public void blabla()
    {

    }

}

Save and see the warning

Exceptions (if any)
(JS) expression expected.
.NET Version
8.0.400

ok i found it
for future searchers
from version of visual studio 17.11.3
 OnClick="@(async () => await Validate())">
i causing this isasue
correct one is
 @onclick="@(async () => await Validate())">
i replaced in every place and now it is fine / no more warnings.
please fix that in visual studio - the error should be different / maybe pointing into correct line at least... ?
thanks and regards !

@dibarbet @MariaSolOs I thought we stamped out all of these in 17.10? Did something change/regress with misc TS files ?

@dibarbet @MariaSolOs I thought we stamped out all of these in 17.10? Did something change/regress with misc TS files ?

Nothing has changed on the TS side since then. @dibarbet have there been any suspicious modifications to the TS Roslyn client?

i was updating from 17.9 and there was no such warnings / no idea how it was on 17.10

i downgraded to visual studio 17.10.5 and NO WARNINGS so issue is only in 17.11.3.

I'm seeing the same behavior / problem
Take note, this as nothing to do with MudBlazor as I am not using it in the affected project (we are using Radzen and the error I get are on some internal component we made)

I'm seeing the same behavior / problem
Take note, this as nothing to do with MudBlazor as I am not using it in the affected project (we are using Radzen and the error I get are on some internal component we made)

i see so it is global issue with OnClick events in components that want to use  OnClick and handle itself the event

The general cause is attributes that look like JavaScript events, so the JavaScript LSP server analyzes the code and reports errors (which is correct because the C# is not valid JavaScript).
The Razor editor then filters out the errors, because it knows that the code is C# not JavaScript, which is why the error list doesn't have any entries from the razor file itself.
The issue here is that something else is also surfacing the errors directly from the virtual JavaScript documents, which is why the file names in the error list look like that.

any news on this? :) regards

phil-allen-msft why it is moved ? is it so hard to fix this?

This issue is still occurring in VS 17.11.5.

This issue is still occurring in VS 17.12.3


Add dynamic buffers in GetDiagRecs and GetErrorFromHandle and prevent buffer overflow on errors longer than 1024 characters

What changes are proposed in this pull request?
When using Databricks with Simba Spark ODBC drivers, long error messages from Spark were occasionally truncated. We traced it down to fixed buffer sizes in GetDiagRecs and GetErrorFromHandle when calling SQLGetDiagRecW.
We now allocate the buffer on the heap instead of stack, and reallocate it to be bigger when needed.
https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqlgetdiagrec-function?view=sql-server-ver15 documents the SQLGetDiagRec function bufferLength as:
BufferLength
[Input] Length of the *MessageText buffer in characters. There is no maximum length of the diagnostic message text.

suggesting that the message length should not be limited by SQL_MAX_MESSAGE_LEN when using this API.
Also, changed GetSqlState to use SQLGetDiagField to retrieve the SQLState. That function seems to not be used though. (Used by HasSqlState, which is not used anywhere in the codebase.)
How it was tested?
Now able to retrieve longer error messages using Simba Spark ODBC drivers and connecting to Databricks Spark Runtime.

Hi @mkleehammer ,
We're using pyodbc at Databricks to connect Redash to Databricks Runtime. We'd really love if the patch could make it into a pyodbc release, so we could use it from the official pyodbc release.

32k? That seems far too large... keep in mind that some platforms (e.g. Alpine Linux, popular with Docker containers and such) default to a 128k stack, and SQL_MAX_MESSAGE_LENGTH (512) is defined in the ODBC specification.
Also, this will cause OOM/stack overflow on platforms where short is also 32 bits...

There is pyodbc_malloc/pyodbc_free, used in the rest of the code.
10k is already a lot more than what Windows and unixODBC DMs have, a much smaller limit on their maximum error message length: https://github.com/lurcher/unixODBC/blob/master/DriverManager/__info.c#L4193

Thanks for pointing to pyodbc_malloc / pyodbc_free.
We have been getting repeated feedback from our customers that long error messages from Spark are truncated in python applications that use pyodbc + Simba Spark ODBC driver to connect to Spark.
It does not happen in native ODBC applications - Tableau or PowerBI return long error messages without problem.
I've looked at https://github.com/lurcher/unixODBC/blob/master/DriverManager/SQLGetDiagRecW.c. Is that what is being called by pyodbc? It doesn't seem to be limited there, up to the point where it calls SQLGETDIAGRECW.
#define SQLGETDIAGRECW(con,typ,han,rn,st,nat,msg,bl,tlp)\
                                    (con->functions[77].funcW)\
                                        (typ,han,rn,st,nat,msg,bl,tlp)

I believe this calls directly into the underlying driver?
We already worked with Simba to make sure that truncation does not happen inside the driver.

@v-chojas I changed it to allocate the message on the heap, and reallocate to a bigger one if needed and tested with Spark + Simba ODBC driver.
In an earlier commit I had the initial message be on the stack, and then allocate on heap if bigger is needed, but I think it's too much complexity for probably little gain (one could argue some heap fragmenation, but I think it's not a very hot function to cause that) https://github.com/mkleehammer/pyodbc/pull/881/commits/27cf95bdddf8d9c475e9b59e4b1195a93e91e4e7
Even more simple would be to just allocate a bigger message on the heap from the get go, heap size should not be so limited as stack size?
WDYT?

Thanks for doing this work, Julius!  It would certainly be an improvement to enable PRINT statements of any length.
It would be good to update the unit tests to cover this scenario though.  As a suggestion, perhaps update the unit test function test_cursor_messages_with_print() in tests3\sqlservertests.py with something like:
        for message in ('hello world', 'A' * 50000):
            self.cursor.execute("PRINT '{}'".format(message))
            self.assertTrue(type(self.cursor.messages) is list)
            self.assertEqual(len(self.cursor.messages), 1)
            self.assertTrue(type(self.cursor.messages[0]) is tuple)
            self.assertEqual(len(self.cursor.messages[0]), 2)
            self.assertTrue(type(self.cursor.messages[0][0]) is str)
            self.assertTrue(type(self.cursor.messages[0][1]) is str)
            self.assertEqual('[01000] (0)', self.cursor.messages[0][0])
            self.assertTrue(self.cursor.messages[0][1].endswith(message))

or something similar?  (By the way, best avoid using f-strings and underscores in numbers because they don't work in Python 3.5.)
For completeness, it would be good to make a similar change to the unit tests in these scripts too:
tests2\sqlservertests.py
tests2\pgtests.py
tests3\pgtests.py

I did some quick testing of Windows' DM and unixODBC, and once you get beyond 512 (SQL_MAX_MESSAGE_LENGTH), the behaviour varies subtly depending on whether the driver and application are Unicode/ANSI, and it also differs between Windows and unixODBC. Depending on the exact API and state upon which the error occurs, unixODBC may extract the diag recs from the driver immediately after the call, without the application calling the diag functions first, in which case the 512 limit applies. Otherwise it is a pass-through, and it doesn't. The Windows DM does something similar.
In other words,  enlarging the buffers in the application doesn't always work, and a driver should be splitting a long message into multiple diag recs of less than 512 bytes each.

@v-chojas Thanks for checking various code paths in Windows DM and unixODBC.

In other words, enlarging the buffers in the application doesn't always work, and a driver should be splitting a long message into multiple diag recs of less than 512 bytes each.

Would that cause this change to break, or would that cause that in some subset of cases where the diag recs are retrieved elsewhere, the message would be truncated to 512 bytes anyway?
It would already be helpful for us if pyodbc did not truncate error messages in those cases where this code is reached.

In other words, enlarging the buffers in the application doesn't always work, and a driver should be splitting a long message into multiple diag recs of less than 512 bytes each.

Unfortunately, getting multiple diag recs seems to be unconditionally disabled in pyodbc on UnixODBC altogether: https://github.com/mkleehammer/pyodbc/pull/881/files#diff-a776f769b92a9224299e940b7d4b8cb4de6ca70371732c05f7e5ea223be9aafcR321
Gluing the multiple diag recs together would right now also add extra formatting added by pyodbc, which would also be undesirable.

@keitherskine Thanks. I added tests as suggested, but used 30000 instead of 50000, because I think the length may be ultimately limited by the SQLGetDiagRecW len parameters being shorts...
Unfortunately, I don't have a Postgres or SQL Server environments handy to verify these tests.

@juliuszsompolski From the CI test results, it's interesting that Postgres appears to have returned 30 messages rather than 1.  It looks like it might have returned the 30K test string in chunks of 1,000 or so bytes each.  SQL Server returned only 1 message for the 30K test string but it doesn't appear to be the right value - maybe it was truncated?

Quite possibly then Postgres is doing what @v-chojas has suggested - splitting long messages into multiple records, while SQL Server (or its driver) might be truncating... Simba Spark ODBC driver was also truncating but they fixed it for us in their upcoming 2.6.17 release. I will take a look when I find a moment.

Would that cause this change to break, or would that cause that in some subset of cases where the diag recs are retrieved elsewhere, the message would be truncated to 512 bytes anyway?

The latter. Look for "DEFER_" in the unixODBC source to see the cases where that occurs.

Thanks @keitherskine for the help tweaking the tests, I very much appreciate the snippets - I do not have a SQL Server environment to debug myself; I have been testing with Simba Spark ODBC drivers, as this is the case I'm trying to solve for myself.

No problem at all @juliuszsompolski , I'm glad they helped.  Your updates make the ".messages" functionality much better (and more memory efficient) so many thanks indeed!

Thanks. Happy to help, and I'd be happy if this could get merged in, so that we can go back to pointing our dependencies at an official pyodbc release, instead of a forked commit.

Yes, it will be good to get this into the master branch and then into a release.  Only @mkleehammer can do that though.

@mkleehammer @keitherskine
The current pyodbc release and master actually SIGSEGVS in GetErrorFromHandle when an error longer than 1024 characters is returned from SQLGetDiagRecW.
This is because
ret = SQLGetDiagRecW(nHandleType, h, iRecord, (SQLWCHAR*)sqlstateT, &nNativeError, (SQLWCHAR*)szMsg, (short)(_countof(szMsg)-1), &cchMsg);

fills cchMsg with the actual size of the message that is available, which may be greater than the size of the buffer.
Meanwhile, a few lines below that
Object msgStr(PyUnicode_Decode((char*)szMsg, cchMsg * sizeof(ODBCCHAR), unicode_enc, "strict"));

uses cchMsg * sizeof(ODBCCHAR) for the size of buffer to decode, causing a buffer overflow.
I did not notice this before, because I was using my version, but now hit that crash when accidentally running in an environment with vanilla pyodbc installed.
This PR fixes that. A simpler fix to prevent the crash would use min(_countof(szMsg)-1, cchMsg) in PyUnicode_Decode.

I'm not sure what happened, but it wouldn't rebase cleanly so I did it manualy.  I put the author names into the commit message as co-authors which GitHub docs say should show up.  Let me know if there is a better way to do that in the future.

Several seemingly unrelated changes were included in the commit for this and some don't seem 100% right. For example in pyodbcmodule.cpp, qmark changed to paramstyle without changing the text below that talks about qmark, and in setup.py pyodbc.pyi is installed, but it ends up in (at least on my system) in /usr/local/pyodbc.pyi.

@sthen I am not sure what happened during the merge of this PR, but these changes were not a part of my branch. Something happened during the mkleehammer force-pushed the master branch from 7b8a44f to 7c7b1b1 6 months ago?
These seem to be the changes from https://github.com/mkleehammer/pyodbc/pull/864/, but they somehow show up in the diff of this PR?

@sthen I agree it looks like the #864 changes were rolled into this PR somehow which I can't explain, but to answer your other questions.
PEP 249 specifies a series of globals that should be part of any module that implements PEP 249, including paramstyle:
https://www.python.org/dev/peps/pep-0249/#paramstyle
For pyodbc, the value of this paramstyle global is "qmark".  Previously, the global name was documented as "qmark" which was not correct.  The global name and value are documented correctly now, I believe.
I appreciate the location of pyodbc.pyi on deployments is not ideal.  As explained here, deploying random files is not straightforward with Python.  If you know of a better way of doing this, I'm open to suggestions.

👋 Hi y'all,
I am running into the same issue: truncated error message when using pyodbc with Spark (Databricks). The PR is a bit confusing to me, it is closed but from the comments I understand changes were merged. I assume that we expect error message should not be truncated anymore. Is that correct?
On Github the latest release is the 8th of February in 2020. That is before this PR is merged. When is a new release made? Or do I miss something, the last release was two years ago.

@JCZuurmond this is merged, and should be available in the latest release on Pypi from Aug 2021: https://pypi.org/project/pyodbc/4.0.32/
After how many characters the message was truncated?
In the LInux (and linux only) version of the Spark ODBC driver there was another bug regarding truncating long error messages that was fixed last year; make sure to use the newest one from https://databricks.com/spark/odbc-drivers-download.
Even then, the default of the Linux Spark ODBC driver remains to truncate error messages after 512 characters. This limitation is because of another bug in some old versions of the unixODBC that caused buffer overflows for longer error messages... I don't remember when that was fixed, but long enough ago that you shouldn't have a version that hits it.
You can increase this limit in the Spark ODBC driver by setting ErrMsgMaxLen=16384 (or other length, but 16k should be enough) in the ODBC config.

@JCZuurmond you could also try using https://pypi.org/project/databricks-sql-connector, which we developed to connect to Databricks Spark directly without going via ODBC, using the same PEP-249 interface. See https://docs.databricks.com/dev-tools/python-sql-connector.html


TC-WIFIDIAG-3.1 - Wifi Diagnostics Cluster ResetCounts Command Failing

Problem
The ResetCounts Command for the Wifi Diagnostics cluster is failing for the following reason: CHIP:TOO: Default Failure Response: 0x01. The command should "reset BeaconLostCount, BeaconRxCount, PacketMulticastRxCount, PacketMulticastTxCount, PacketUnicastRxCount, PacketUnicastTxCount." attributes
Affected Command:
./chip-tool wifinetworkdiagnostics reset-counts 1234 0
Test Cases
TC-WIFIDIAG-3.1 | Command received functionality with server as DUT

https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/cluster/wifi_diagnostics.adoc#tc-wifidiag-3-1-command-received-functionality-with-server-as-dut

Testing Setup
chip-tool and chip-all-clusters-app: commit f51eeb39de1e58c8f55a13cfc59782e8e11c6948 (HEAD -> test_event_7, origin/test_event_7)
Logs
Chip-Tool Logs

ubuntu@matter-te-6:~/TE/connectedhomeip/examples/chip-tool/out/debug$ ./chip-tool wifinetworkdiagnostics reset-counts 1234 0
[1636584228.955056][1334860:1334860] CHIP:CTL: Generating NOC
[1636584228.955453][1334860:1334860] CHIP:CTL: Generating ICAC
[1636584228.960731][1334860:1334860] CHIP:DL: AUDIT: ===== RANDOM NUMBER GENERATOR AUDIT START ====
[1636584228.960782][1334860:1334860] CHIP:DL: AUDIT: * Validate buf1 and buf2 are <<<different every run/boot!>>>
[1636584228.960807][1334860:1334860] CHIP:DL: AUDIT: * Validate r1 and r2 are <<<different every run/boot!>>>
[1636584228.960831][1334860:1334860] CHIP:DL: AUDIT: * buf1: 923C7B1F1A3E9740469C7096450159C3
[1636584228.960853][1334860:1334860] CHIP:DL: AUDIT: * buf2: 0C545FC3540CE02FA249C45E45CF36AD
[1636584228.960921][1334860:1334860] CHIP:DL: AUDIT: * r1: 0xFDA4F6A1 r2: 0x51EC1692
[1636584228.960944][1334860:1334860] CHIP:DL: AUDIT: ===== RANDOM NUMBER GENERATOR AUDIT END ====
[1636584228.961540][1334860:1334860] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-xTidpF)
[1636584228.962126][1334860:1334860] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1636584228.962175][1334860:1334860] CHIP:DL: NVS set: chip-counters/reboot-count = 93 (0x5D)
[1636584228.963156][1334860:1334860] CHIP:DL: Got Ethernet interface: eth0
[1636584228.963772][1334860:1334860] CHIP:DL: Found the primary Ethernet interface:eth0
[1636584228.964393][1334860:1334860] CHIP:DL: Got WiFi interface: wlan0
[1636584228.964463][1334860:1334860] CHIP:DL: Failed to reset WiFi statistic counts
[1636584228.964515][1334860:1334860] CHIP:IN: UDP::Init bind&listen port=5541
[1636584228.964630][1334860:1334860] CHIP:IN: UDP::Init bound to port=5541
[1636584228.964658][1334860:1334860] CHIP:IN: UDP::Init bind&listen port=5541
[1636584228.964747][1334860:1334860] CHIP:IN: UDP::Init bound to port=5541
[1636584228.964772][1334860:1334860] CHIP:IN: TransportMgr initialized
[1636584228.964834][1334860:1334860] CHIP:DIS: Init fabric pairing table with server storage
[1636584228.965806][1334860:1334860] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-KrWIjV)
[1636584228.966458][1334860:1334860] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1636584228.966509][1334860:1334860] CHIP:DL: NVS set: chip-counters/GlobalMCTR = 97000 (0x17AE8)
[1636584228.966631][1334860:1334860] CHIP:CTL: System State Initialized...
[1636584228.971777][1334860:1334860] CHIP:DL: Avahi client registered
[1636584228.973341][1334860:1334860] CHIP:ZCL: Using ZAP configuration...
[1636584228.974229][1334860:1334860] CHIP:DIS: Verifying the received credentials
[1636584228.976629][1334860:1334860] CHIP:DIS: Added new fabric at index: 1, Initialized: 1
[1636584228.976795][1334860:1334860] CHIP:DIS: Assigned compressed fabric ID: 0x0DF4756F26F6D608, node ID: 0x000000000001B669
[1636584228.976831][1334860:1334860] CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0x0DF4756F26F6D608
[1636584228.977373][1334860:1334865] CHIP:DL: CHIP task running
[1636584228.977569][1334860:1334865] CHIP:DL: HandlePlatformSpecificBLEEvent 32785
[1636584228.977611][1334860:1334865] CHIP:TOO: Sending command to node 0x4d2
[1636584228.978658][1334860:1334865] CHIP:IN: Prepared plaintext message 0xaaaaecc0d810 to 0x0000000000000000 of type 0x30 and protocolId (0, 0) on exchange 38786i with MessageCounter:668828030.
[1636584228.978740][1334860:1334865] CHIP:IN: Sending plaintext msg 0xaaaaecc0d810 with MessageCounter:668828030 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER> msec
[1636584228.978978][1334860:1334865] CHIP:SC: Sent Sigma1 msg
[1636584228.983722][1334860:1334865] CHIP:EM: Received message of type 0x31 with protocolId (0, 0) and MessageCounter:854684611 on exchange 38786i
[1636584228.983792][1334860:1334865] CHIP:EM: Rxd Ack; Removing MessageCounter:668828030 from Retrans Table on exchange 38786i
[1636584228.983831][1334860:1334865] CHIP:EM: Removed CHIP MessageCounter:668828030 from RetransTable on exchange 38786i
[1636584228.983881][1334860:1334865] CHIP:SC: Received Sigma2 msg
[1636584228.983928][1334860:1334865] CHIP:SC: Peer assigned session session ID 24
[1636584228.988406][1334860:1334865] CHIP:SC: Sending Sigma3
[1636584228.989015][1334860:1334865] CHIP:EM: Piggybacking Ack for MessageCounter:854684611 on exchange: 38786i
[1636584228.989079][1334860:1334865] CHIP:IN: Prepared plaintext message 0xaaaaecc0d810 to 0x0000000000000000 of type 0x32 and protocolId (0, 0) on exchange 38786i with MessageCounter:668828031.
[1636584228.989135][1334860:1334865] CHIP:IN: Sending plaintext msg 0xaaaaecc0d810 with MessageCounter:668828031 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER> msec
[1636584228.989340][1334860:1334865] CHIP:SC: Sent Sigma3 msg
[1636584228.996629][1334860:1334865] CHIP:EM: Received message of type 0x40 with protocolId (0, 0) and MessageCounter:854684612 on exchange 38786i
[1636584228.996686][1334860:1334865] CHIP:EM: Rxd Ack; Removing MessageCounter:668828031 from Retrans Table on exchange 38786i
[1636584228.996721][1334860:1334865] CHIP:EM: Removed CHIP MessageCounter:668828031 from RetransTable on exchange 38786i
[1636584228.996767][1334860:1334865] CHIP:SC: Success status report received. Session was established
[1636584228.996804][1334860:1334865] CHIP:IN: New secure session created for device 0x00000000000004D2, key 24!!
[1636584228.996885][1334860:1334865] CHIP:TOO: Sending cluster (0x00000036) command (0x00000000) on endpoint 0
[1636584228.997060][1334860:1334865] CHIP:DMG: ICR moving to [AddingComm]
[1636584228.997115][1334860:1334865] CHIP:DMG: ICR moving to [AddedComma]
[1636584228.997229][1334860:1334865] CHIP:IN: Prepared encrypted message 0xaaaaecc0d810 to 0x00000000000004D2 of type 0x8 and protocolId (0, 1) on exchange 38787i with MessageCounter:0.
[1636584228.997279][1334860:1334865] CHIP:IN: Sending encrypted msg 0xaaaaecc0d810 with MessageCounter:0 to 0x00000000000004D2 at monotonic time:<PHONE_NUMBER> msec
[1636584228.997383][1334860:1334865] CHIP:DMG: ICR moving to [CommandSen]
[1636584228.997427][1334860:1334865] CHIP:EM: Sending Standalone Ack for MessageCounter:854684612 on exchange 38786i
[1636584228.997467][1334860:1334865] CHIP:IN: Prepared plaintext message 0xffff9a7cd8e0 to 0x0000000000000000 of type 0x10 and protocolId (0, 0) on exchange 38786i with MessageCounter:668828032.
[1636584228.997510][1334860:1334865] CHIP:IN: Sending plaintext msg 0xffff9a7cd8e0 with MessageCounter:668828032 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER> msec
[1636584228.997591][1334860:1334865] CHIP:EM: Flushed pending ack for MessageCounter:854684612 on exchange 38786i
[1636584229.000520][1334860:1334865] CHIP:EM: Received message of type 0x9 with protocolId (0, 1) and MessageCounter:1 on exchange 38787i
[1636584229.000576][1334860:1334865] CHIP:EM: Rxd Ack; Removing MessageCounter:0 from Retrans Table on exchange 38787i
[1636584229.000610][1334860:1334865] CHIP:EM: Removed CHIP MessageCounter:0 from RetransTable on exchange 38787i
[1636584229.000659][1334860:1334865] CHIP:DMG: InvokeCommand =
[1636584229.000695][1334860:1334865] CHIP:DMG: {
[1636584229.000725][1334860:1334865] CHIP:DMG:         CommandList =
[1636584229.000760][1334860:1334865] CHIP:DMG:         [
[1636584229.000794][1334860:1334865] CHIP:DMG:                 CommandDataIB =
[1636584229.000842][1334860:1334865] CHIP:DMG:                 {
[1636584229.000878][1334860:1334865] CHIP:DMG:                         CommandPathIB =
[1636584229.000921][1334860:1334865] CHIP:DMG:                         {
[1636584229.000968][1334860:1334865] CHIP:DMG:                                 EndpointId = 0x0,
[1636584229.001018][1334860:1334865] CHIP:DMG:                                 ClusterId = 0x36,
[1636584229.001064][1334860:1334865] CHIP:DMG:                                 CommandId = 0x0,
[1636584229.001112][1334860:1334865] CHIP:DMG:                         },
[1636584229.001193][1334860:1334865] CHIP:DMG:
[1636584229.001235][1334860:1334865] CHIP:DMG:                         StatusIB =
[1636584229.001282][1334860:1334865] CHIP:DMG:                         {
[1636584229.001329][1334860:1334865] CHIP:DMG:                                 status = 0x1,
[1636584229.001371][1334860:1334865] CHIP:DMG:                         },
[1636584229.001415][1334860:1334865] CHIP:DMG:
[1636584229.001453][1334860:1334865] CHIP:DMG:                 },
[1636584229.001496][1334860:1334865] CHIP:DMG:
[1636584229.001529][1334860:1334865] CHIP:DMG:         ],
[1636584229.001568][1334860:1334865] CHIP:DMG:
[1636584229.001598][1334860:1334865] CHIP:DMG: }
[1636584229.001654][1334860:1334865] CHIP:DMG: Received Command Response Status for Endpoint=0 Cluster=0x0000_0036 Command=0x0000_0000 Status=0x1
[1636584229.001691][1334860:1334865] CHIP:TOO: Default Failure Response: 0x01
[1636584229.001756][1334860:1334865] CHIP:DMG: ICR moving to [AwaitingDe]
[1636584229.001796][1334860:1334865] CHIP:EM: Sending Standalone Ack for MessageCounter:1 on exchange 38787i
[1636584229.001855][1334860:1334865] CHIP:IN: Prepared encrypted message 0xffff9a7cd8b0 to 0x00000000000004D2 of type 0x10 and protocolId (0, 0) on exchange 38787i with MessageCounter:1.
[1636584229.001902][1334860:1334865] CHIP:IN: Sending encrypted msg 0xffff9a7cd8b0 with MessageCounter:1 to 0x00000000000004D2 at monotonic time:<PHONE_NUMBER> msec
[1636584229.002032][1334860:1334865] CHIP:EM: Flushed pending ack for MessageCounter:1 on exchange 38787i
[1636584229.002317][1334860:1334860] CHIP:-: ../../third_party/connectedhomeip/zzz_generated/chip-tool/zap-generated/cluster/Commands.h:45: CHIP Error 0x000000AC: Internal error at ../../commands/common/CHIPCommand.cpp:84
[1636584229.002402][1334860:1334860] CHIP:TOO: Run command failure: ../../third_party/connectedhomeip/zzz_generated/chip-tool/zap-generated/cluster/Commands.h:45: CHIP Error 0x000000AC: Internal error
[1636584229.129209][1334860:1334860] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
[1636584229.129541][1334860:1334860] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-sL0pb1)
[1636584229.130360][1334860:1334860] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1636584229.130425][1334860:1334860] CHIP:DL: NVS set: chip-counters/total-operational-hours = 23 (0x17)
[1636584229.130452][1334860:1334860] CHIP:DL: Inet Layer shutdown
[1636584229.130550][1334860:1334860] CHIP:DL: BLE layer shutdown
[1636584229.130576][1334860:1334860] CHIP:DL: System Layer shutdown

chip-all-clusters-app logs

[1636584228.978724][115367:115367] CHIP:EM: Received message of type 0x30 with protocolId (0, 0) and MessageCounter:668828030 on exchange 38786r
[1636584228.978827][115367:115367] CHIP:EM: Handling via exchange: 38786r, Delegate: 0x0xaaaae81765e8
[1636584228.978908][115367:115367] CHIP:IN: CASE Server received Sigma1 message. Starting handshake. EC 0xaaaae8176bf0
[1636584228.978964][115367:115367] CHIP:DIS: CASE handshake initiated, closing all BLE Connections
[1636584228.979018][115367:115367] CHIP:SC: Waiting for Sigma1 msg
[1636584228.979063][115367:115367] CHIP:IN: CASE Server disabling CASE session setups
[1636584228.979112][115367:115367] CHIP:SC: Received Sigma1 msg
[1636584228.979197][115367:115367] CHIP:SC: Peer assigned session key ID 166
[1636584228.979248][115367:115367] CHIP:DIS: Fabric (1) loaded from storage. Calling OnFabricRetrievedFromStorage
[1636584228.979297][115367:115367] CHIP:ZCL: OpCreds: Fabric 0x1 was retrieved from storage. FabricId 0x0000000000000000, NodeId 0x00000000000004D2, VendorId 0xFFF1
[1636584228.979347][115367:115367] CHIP:ZCL: OpCreds: Call to writeFabricsIntoFabricsListAttribute
[1636584228.979526][115367:115367] CHIP:ZCL: OpCreds: Writing fabric into attribute store at index 0: fabricId 0x0000000000000000, nodeId 0x00000000000004D2 vendorId 0xFFF1
[1636584228.979605][115367:115367] CHIP:ZCL: OpCreds: Stored 1 fabrics in fabrics list attribute.
[1636584228.979802][115367:115367] CHIP:DIS: Fabric (1) loaded from storage. Calling OnFabricRetrievedFromStorage
[1636584228.979860][115367:115367] CHIP:ZCL: OpCreds: Fabric 0x1 was retrieved from storage. FabricId 0x0000000000000000, NodeId 0x00000000000004D2, VendorId 0xFFF1
[1636584228.979909][115367:115367] CHIP:ZCL: OpCreds: Call to writeFabricsIntoFabricsListAttribute
[1636584228.980052][115367:115367] CHIP:ZCL: OpCreds: Writing fabric into attribute store at index 0: fabricId 0x0000000000000000, nodeId 0x00000000000004D2 vendorId 0xFFF1
[1636584228.980119][115367:115367] CHIP:ZCL: OpCreds: Stored 1 fabrics in fabrics list attribute.
[1636584228.982438][115367:115367] CHIP:EM: Piggybacking Ack for MessageCounter:668828030 on exchange: 38786r
[1636584228.982534][115367:115367] CHIP:IN: Prepared plaintext message 0xaaaae8176ae8 to 0x0000000000000000 of type 0x31 and protocolId (0, 0) on exchange 38786r with MessageCounter:854684611.
[1636584228.982615][115367:115367] CHIP:IN: Sending plaintext msg 0xaaaae8176ae8 with MessageCounter:854684611 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER> msec
[1636584228.982847][115367:115367] CHIP:SC: Sent Sigma2 msg
[1636584228.989001][115367:115367] CHIP:EM: Received message of type 0x32 with protocolId (0, 0) and MessageCounter:668828031 on exchange 38786r
[1636584228.989084][115367:115367] CHIP:EM: Rxd Ack; Removing MessageCounter:854684611 from Retrans Table on exchange 38786r
[1636584228.989132][115367:115367] CHIP:EM: Removed CHIP MessageCounter:854684611 from RetransTable on exchange 38786r
[1636584228.989190][115367:115367] CHIP:SC: Received Sigma3 msg
[1636584228.995307][115367:115367] CHIP:SC: Sending status report. Protocol code 0, exchange 38786
[1636584228.995402][115367:115367] CHIP:EM: Piggybacking Ack for MessageCounter:668828031 on exchange: 38786r
[1636584228.995485][115367:115367] CHIP:IN: Prepared plaintext message 0xaaaae8176ae8 to 0x0000000000000000 of type 0x40 and protocolId (0, 0) on exchange 38786r with MessageCounter:854684612.
[1636584228.995572][115367:115367] CHIP:IN: Sending plaintext msg 0xaaaae8176ae8 with MessageCounter:854684612 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER> msec
[1636584228.995823][115367:115367] CHIP:IN: CASE Session established. Setting up the secure channel.
[1636584228.995890][115367:115367] CHIP:IN: Marking old secure session for device 0x000000000001B669 as expired
[1636584228.995962][115367:115367] CHIP:IN: New secure session created for device 0x000000000001B669, key 166!!
[1636584228.996094][115367:115367] CHIP:IN: CASE secure channel is available now.
[1636584228.996156][115367:115367] CHIP:IN: CASE Server enabling CASE session setups
[1636584228.997083][115367:115367] CHIP:EM: Received message of type 0x8 with protocolId (0, 1) and MessageCounter:0 on exchange 38787r
[1636584228.997168][115367:115367] CHIP:EM: Handling via exchange: 38787r, Delegate: 0x0xaaaae8172410
[1636584228.997270][115367:115367] CHIP:DMG: InvokeCommand =
[1636584228.997334][115367:115367] CHIP:DMG: {
[1636584228.997388][115367:115367] CHIP:DMG:         CommandList =
[1636584228.997451][115367:115367] CHIP:DMG:         [
[1636584228.997510][115367:115367] CHIP:DMG:                 CommandDataIB =
[1636584228.997584][115367:115367] CHIP:DMG:                 {
[1636584228.997647][115367:115367] CHIP:DMG:                         CommandPathIB =
[1636584228.997724][115367:115367] CHIP:DMG:                         {
[1636584228.997803][115367:115367] CHIP:DMG:                                 EndpointId = 0x0,
[1636584228.997892][115367:115367] CHIP:DMG:                                 ClusterId = 0x36,
[1636584228.997973][115367:115367] CHIP:DMG:                                 CommandId = 0x0,
[1636584228.998100][115367:115367] CHIP:DMG:                         },
[1636584228.998185][115367:115367] CHIP:DMG:
[1636584228.998255][115367:115367] CHIP:DMG:                         CommandData =
[1636584228.998336][115367:115367] CHIP:DMG:                         {
[1636584228.998412][115367:115367] CHIP:DMG:                         },
[1636584228.998484][115367:115367] CHIP:DMG:                 },
[1636584228.998560][115367:115367] CHIP:DMG:
[1636584228.998618][115367:115367] CHIP:DMG:         ],
[1636584228.998687][115367:115367] CHIP:DMG:
[1636584228.998741][115367:115367] CHIP:DMG: }
[1636584228.998834][115367:115367] CHIP:DMG: Received command for Endpoint=0 Cluster=0x0000_0036 Command=0x0000_0000
[1636584228.999111][115367:115367] CHIP:DMG: ICR moving to [AddingComm]
[1636584228.999185][115367:115367] CHIP:DMG: ICR moving to [AddedComma]
[1636584228.999270][115367:115367] CHIP:EM: Piggybacking Ack for MessageCounter:0 on exchange: 38787r
[1636584228.999388][115367:115367] CHIP:IN: Prepared encrypted message 0xaaaae8176b00 to 0x000000000001B669 of type 0x9 and protocolId (0, 1) on exchange 38787r with MessageCounter:1.
[1636584228.999473][115367:115367] CHIP:IN: Sending encrypted msg 0xaaaae8176b00 with MessageCounter:1 to 0x000000000001B669 at monotonic time:<PHONE_NUMBER> msec
[1636584228.999704][115367:115367] CHIP:DMG: ICR moving to [CommandSen]
[1636584228.999768][115367:115367] CHIP:DMG: ICR moving to [AwaitingDe]
[1636584229.000028][115367:115367] CHIP:EM: Received message of type 0x10 with protocolId (0, 0) and MessageCounter:668828032 on exchange 38786r
[1636584229.000129][115367:115367] CHIP:EM: Rxd Ack; Removing MessageCounter:854684612 from Retrans Table on exchange 38786r
[1636584229.000192][115367:115367] CHIP:EM: Removed CHIP MessageCounter:854684612 from RetransTable on exchange 38786r
[1636584229.001488][115367:115367] CHIP:EM: Received message of type 0x10 with protocolId (0, 0) and MessageCounter:1 on exchange 38787r
[1636584229.001528][115367:115367] CHIP:EM: Rxd Ack; Removing MessageCounter:1 from Retrans Table on exchange 38787r
[1636584229.001552][115367:115367] CHIP:EM: Removed CHIP MessageCounter:1 from RetransTable on exchange 38787r

Update for TE 7.5: Same Failures
commit: b0af6ba42b6ce494748f18ecf3e054a400b8f45b
Same issue persists across the entire issue filed above.
Lines of Interest from Logs

./chip-tool wifinetworkdiagnostics reset-counts 1234 0

[1642732716954] [90578:3884772] CHIP: [TOO] Run command failure: ../../third_party/connectedhomeip/zzz_generated/chip-tool/zap-generated/cluster/Commands.h:2502: CHIP Error 0x000000AC: Internal error

Logs
consolidated_mac_accessory_TC-WIFIDIAG-3-1.txt

Closing this issue
Moving to duplicate issue to track the problem from now on: https://github.com/project-chip/connectedhomeip/issues/13418#issuecomment-1018837380


Element not found Error

This error pops up whenever I try to start the session.

That is probably because of the windows 10's latest feature update (i read it somewhere). Uninstalling it might solve the problem.
I am not facing it though.

wsl -u root --exec "/usr/.bin/bash"
Still gives me the element not found error, seems like there's no way to recover.

Installing...
ERROR:Installation Failed!
HRESULT:0x80070490
Press any key to continue...

Trying to reinstall gives this error now.

Did you try uninstalling windows 10's latest feature update?

Nope, I don't really wanna downgrade.

Well then, there is nothing that anyone can do about it.

Microsoft has a gift for you.
https://blogs.windows.com/windows-insider/2020/09/22/announcing-windows-10-insider-preview-build-19042-541-20h2/


Compiler flag for other Timers

Hello, I've been using the library for a project at my Uni - and forked it to so I can use the TIMER4 on a MEGA2560. At the moment it is only functionally I just use sed -i -f regexes.sed ./src/*ISR_avr.cpp to do so. See ixil/FastAccelStepper. (The other difference were just when I was testing it).
Would you be interested/would it be possible to use some preprocessor magic (or better, modern c++) so I do not need to follow your fork?
Thanks for the useful library

Please check out atmega2560 branch
Here the timer module 4 is hard coded.
I am searching standard way, how the application programmer can configure a library in arduino and platformio.
In platformio I can define preprocessor variables in platformio.ini. Not sure, how to do this in arduino and what is the standard way of doing so.
Background:
For mega2560 I like to be able to use all four 16bit timers. If this is hardcoded in the library, for every timermodule the respective ISRs are defined. This yields a collision, if the application or another library wants to use another timer module and defines its own ISR.

BTW: apparently the atmega2560 can support even three steppers per timer due to a third compare unit.

Released 0.13.0 with atmega 2560 support and three steppers, linked to timer 4
Hope it works for you

That was super quick of you! I will have access to the robot on Monday (I hope) so I can test my existing stuff with that then - I can't really test from home sorry.

In platformio I can define preprocessor variables in platformio.ini. Not sure, how to do this in arduino and what is the standard way of doing so.

The Arduino platform is regrettable really.
From the other libraries I surveyed, they normally just require a flag #define USECHANNEL1 in the .ino or a combination of class templates combined with more preprocessor magic to make the register/bit/ISR strings.
In pseudo cpp, maybe something like:
#define STRING(T) "T" /*my macro magic skills are poor */
enum class ChannelEnum { A, B, C};
template <size_t timer>
AVRAccelStep { AVRAccelStep(ChannelEnum channel){ switch(channel){}}; };

edit: looking at your code, I think you handle it better than what I could come up with. I don't really know how to fix the Scoping with the Macros and have it encapsulated.

Background: For mega2560 I like to be able to use all four 16bit timers. If this is hardcoded in the library, for every timermodule the respective ISRs are defined. This yields a collision, if the application or another library wants to use another timer module and defines its own ISR.

Looking at the avr library, you could do a #ifdef _VECTOR(41) and through an #error I'm not sure that's particularly scalable though.
See avr/sfr_defs.h and the avr/io.h

The issue is still, that the library would need to source a header file from the application. Just have opened arduino IDE and I could not find any place to add a compiler define, which would be applied to the whole project including libraries. In platformio, this is feasible.
And for sourcing an application header file into the library, I do not know, if there is any kind of standard like this. Or if the library manager (managing all the libraries) would reject this. I have had this before and the culprit was, that symbolic links are forbidden.
The avr/sfr_defs.h and the avr/io.h is part of the avr ecosystem. FastAccelStepper is a library, which is not part of that ecosystem and not part of the application.

The version 0.13.1 will try to include an application defined header-file using this:
#if __has_include("fas_config.h")
#include "fas_config.h"
#endif

Now I wait till it shows up in library manager.

This header file inclusion has not worked.
So 0.14.0 evaluates a preprocessor flag called FAS_TIMER_MODULE.
With platformio just add it to build_flags in platformio.ini.
For Arduino-IDE, I don't know.

Robots were unavailable, so I'm not sure when I'll be able to test (covid + Christmas etc) - possibly tomorrow

For Arduino-IDE
I imagine with Arduino-IDE enduser just needs to do #define FAS_TIME_MODULE at the top of .ino sketch.

The pin mappings look incorrect to me, I've sent a pr: #19

In the pull-request I have updated the build target to the arduino atmega, rather than plain ATMega2560

Thanks for the pull request. Already integrated.
So this issue can be closed ?

I think the issue can be closed, I am having problems using the newer version of the library, but that's not this issue

Maybe this should be reopened: I seem to be hitting some under behavior (board is continuously resetting, and I'm not sure why yet)
So until I've tested this should probably be open

stalled. if the reset issue is related to FastAccelStepper, then please open a new issue.

stalled. if the reset issue is related to FastAccelStepper, then please open a new issue.


Deno support?

Any plan to add Deno support for markdown-wasm, and Deno developer can use this module to render Markdown quickly.
Now I  have following Deno typescript code, such as demo.ts
import * as markdown from "https://raw.githubusercontent.com/rsms/markdown-wasm/master/dist/markdown.es.js";
await markdown.ready
console.log(markdown.parse("# hello\n*world*"))

I got the error with deno run demo.ts
Download https://raw.githubusercontent.com/rsms/markdown-wasm/master/dist/markdown.es.js
Check file:///Users/xxxx/demo.ts
error: Uncaught ReferenceError: document is not defined
    at https://raw.githubusercontent.com/rsms/markdown-wasm/master/dist/markdown.es.js:1:1908

Is it possible to produce a js file for Deno?  such as markdown.deno.js, and the code alike following:
import {parse} from "https://denopkg.com/rsms/markdown-wasm/dist/markdown.deno.js";
console.log(parse("# hello\n*world*"))

I find a way to support Deno.   Add deno build in wasmc.js:
module({ ...m,
  name:   "markdown-deno",
  out:    outdir + "/markdown.deno.js",
  embed:  true,
  format: "es",
})

then add `var document = {};'   at the beginning of markdown.deno.js.

Thanks! Please remember to add the license for markdown-wasm and md4c in your repo at https://github.com/linux-china/markdown-wasm since it's public, to avoid legal trouble :–)
Q: Did you close this issue by accident or did you change your mind? If the latter, care to elaborate?


'react-scripts start' fails on MacOS

see log file
npm-debug.log.txt

Have you tried removing the package-lock.json file ?

Thank you for writing back, Gildas.
No, I did not, and I am not sure why I have to (I am a bit of a newby on node.js things).
If I could ask you for some instruction, that would be very much appreciated.
You have a very innovative AR product!

Dean

On Aug 28, 2017, at 4:16 PM, Gildas Garcia <notifications<EMAIL_ADDRESS>wrote:
Have you tried removing the package-lock.json file ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/marmelab/sketch-by-phone/issues/30#issuecomment-325278580, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABa66BnG43yRh0sDdW2mFwGCTSW2ZsFmks5scmlTgaJpZM4PECeF.

Thanks :)
You're the second person saying it doesn't work on osX, for different reasons though.
I see that you're on node 6 and npm 3. Can you try upgrading those ? Maybe using nvm ?

Gildas:  Ok, I see that I did not install sketch-by-phone in the right order (didn’t go down enough to see the makes).
It seems to be running out of localhost fine now.  Fake issue, I am sorry I posted it.
When iOS11 comes out, I will be ready to cast some image templates to students in the lecture hall for use in iClicker assignments!

Dean

On Aug 28, 2017, at 4:42 PM, Gildas Garcia <notifications<EMAIL_ADDRESS>wrote:
Thanks :)
You're the second person saying it doesn't work on osX, for different reasons though.
I see that you're on node 6 and npm 3. Can you try upgrading those ? Maybe using nvmhttps://github.com/creationix/nvm ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/marmelab/sketch-by-phone/issues/30#issuecomment-325283451, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABa66CQNJkUaX0tRa4KoihSkqVZNz9ACks5scm9TgaJpZM4PECeF.

No problem :)

Hello Gildas
I did not get sketch-by phone to turn on camera on my iPhone6 properly with iOS 6.  (Etennie's ar.js demo display great however.  Any ideas?
[image1.png]
Sent from my iPhone ... Dean

sketch-by-phone doesn't work on iOS, that's a known limitation.

Francois:
We updated the ar.js and three.js libraries and sketch-by-phone NOW WORKS on iOS (Safari only, Chrome has usual WebRTC problem).
Behaves same as on Android, showing some skewing of images — but on MacOS no skewing shows.
We are redeveloping it as an AR aid in the lecture hall, as previously stated.
Thank you very much for the great tutorial. - Dean
On Sep 29, 2017, at 5:22 AM, Francois Zaninotto <notifications<EMAIL_ADDRESS>wrote:
sketch-by-phone doesn't work on iOS, that's a known limitation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/marmelab/sketch-by-phone/issues/30#issuecomment-333077069, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABa66BqBkbmGy432XLMc8c7d4lJ09Dvhks5snLbKgaJpZM4PECeF.


visitor-badge.lithub.cc SSL certificate expired

ZeroSSL certificate expired Thu, 28 Mar 2024 23:59:59 GMT.
Therefore any recent browser won't connect to the website, and the counter won't work (HTTPS Everywhere / HTTPS-only requires you to add an exception).
P.S.: "Let's Encrypt" ftw: It's free!

thx for report! it has been fixed now, please try it again~


Key backup: add PUT /room_keys/version/{version}

to allow matrix clients to add signatures to an existing backup or update any information in the auth_data field.

There's a race condition in this API for use with updating signatures.  If the user is setting up backup on two devices A and B, they both fetch the backup version info, and then both sign the backup info, and then both send their updates to the server, then the server will only end up with one of the signatures.  This might not be too bad in practice, but clients should do what they can to avoid this situation (e.g. re-fetching the backup info just before signing and sending, so that they have as much up-to-date information as they can get).

I'm wondering, though, if we should say that the server will ensure that the public key in the auth_data is the same as the previous value, though that means that the server must understand the different backup formats.

Given we specify m.megolm_backup.v1.curve25519-aes-sha2 in this spec, we could require the server to make additional check when encountering that format.

There's a race condition in this API for use with updating signatures

You are right. Client should manage it.


Add Tim

Motivation
Add Tim
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
This is it

Seems like a nice guy

not sure...


vi.doMock does not override previous mock

Describe the bug
vi.resetModules does not reset mocks created with doMock
vi.doMock does not override previous mock
Reproduction
Example source file:
const getToken = () => 'token';

module.exports = { getToken };

Example test file:
// beforeEach(() => {
//  vi.resetModules();
// });

test('getToken 1', async () => {
  vi.doMock('./getToken', () => ({
    getToken: () => 'token1',
  }));
  const { getToken } = await import('./getToken');
  expect(getToken()).toBe('token1');
});

test('getToken 2', async () => {
  vi.doMock('./getToken', () => ({
    getToken: () => 'token2',
  }));
  const { getToken } = await import('./getToken');
  expect(getToken()).toBe('token2'); // <-- This should be 'token2'
});

Error thrown:
 FAIL  doMock.spec.js > getToken 2
AssertionError: expected 'token1' to be 'token2' // Object.is equality
 ❯ doMock.spec.js:18:22
     16|   }));
     17|   const { getToken } = await import('./getToken');
     18|   expect(getToken()).toBe('token2');
       |                      ^
     19| });

  - Expected   "token2"
  + Received   "token1"

System Info
System:
    OS: macOS 13.1
    CPU: (8) arm64 Apple M1 Pro
  Binaries:
    Node: 18.13.0 - ~/Library/Caches/fnm_multishells/65073_1676392486717/bin/node
    Yarn: 3.4.1 - ~/Library/Caches/fnm_multishells/65073_1676392486717/bin/yarn
    npm: 8.19.3 - ~/Library/Caches/fnm_multishells/65073_1676392486717/bin/npm
  npmPackages:
    vitest: ^0.28.5 => 0.28.5

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Documentation for vi.doMock https://vitest.dev/api/vi.html#vi-domock

vi.resetModules doesn't clear mocks registry by design, as far as I'm aware. Not sure if it was the right decision though 🤷🏻

The documentation for vi.resetModules

Resets modules registry by clearing cache of all modules.

From the documentation, it looks like it should clear the mock registry.

The documentation for vi.doMock

The same as vi.mock, but it's not hoisted at the top of the file, so you can reference variables in the global file scope. The next import of the module will be mocked.

From the definition, doMock should override previous cache, even if vi.resetModules doesn't clear the mock registry.

I'd like to take this.


spatio_temporal_voxel_layer: 1.2.0-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository spatio_temporal_voxel_layer to 1.2.0-0:

upstream repository: https://github.com/SteveMacenski/spatio_temporal_voxel_layer.git
release repository: https://github.com/SteveMacenski/spatio_temporal_voxel_layer-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.6.9
previous version for package: 1.1.4-2

I know it's going to wait until after the sync :+1:


xcodebuild Warning: Conflicting class XCBuildConfiguration

When I use xcodebuild I get the following warning:
objc[30712]: Class XCBuildConfiguration is implemented in both /Applications/Xcode6.1.app/Contents/PlugIns/Xcode3Core.ideplugin/Contents/Frameworks/DevToolsCore.framework/Versions/A/DevToolsCore and /Users/seandawson/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Auto-Importer.xcplugin/Contents/MacOS/Auto-Importer. One of the two will be used. Which one is undefined.
There may be a conflicting class in this project that needs to be renamed or not included in the final package.

This is an annoyance. I think it can be fixed by just renaming the XCBuildConfiguration class in this project. Here's another project with a similar issue
https://github.com/markohlebar/Peckham/issues/27

This is an issue from this dependency: https://github.com/jasperblues/XcodeEditor, can't simple rename the class in the auto-importer project.

Ah, I see. Opened the issue there:
https://github.com/jasperblues/XcodeEditor/issues/44

closing since it's not a warning from this project but from one of the dependencies.

@johnboiles awesome thanks, project updated now.

Sorry for the delay: I saw the Peckham issue a while back, but the comments suggested a pull request was forthcoming so I didn't log it.
@NoxHarmonium, I would appreciate if your Readme notes that Auto-Importer uses the XcodeEditor library, as you've done with Peckham :+1:

@jasperblues :+1:


glib: 2.58.2 -> 2.58.3

Motivation for this change
closes https://github.com/NixOS/nixpkgs/issues/55999
~Just targeting master to get reliable builds on all the platforms, will change to staging afterwards (so don't merge before that).~
Things done

Built on platforms:

[x] x86_64-linux
[x] x86_64-darwin
[x] aarch64-linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] 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)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Interesting Darwin failure on staging (unrelated to PR, of course)

That one should be fixed by 18fe630281 – let me merge staging-next to staging to get rid of that :-)

Double checked that there isn't any outstanding bugs open for 2.58.3 which we should backport, and couldn't find any. So I'm going to merge.


Bugfix Azure AD auth config field 'expired-on': checking an int against time.struct_time

Compare two time.struct_time objects instead of an int and a
time.struct_time, which will throw a TypeError exception.
This fixes https://github.com/kubernetes-client/python-base/issues/84
This pull request is to https://github.com/kubernetes-client/python-base/pull/85 but this is an effort to revive the fix.

I am having some issues registering with LinuxFoundation. I'll have the CLA signed once I get my account with LinuxFoundation sorted.

Codecov Report

Merging #121 into master will decrease coverage by 0.22%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #121      +/-   ##
==========================================
- Coverage   92.11%   91.88%   -0.23%
==========================================
  Files          13       13
  Lines        1217     1220       +3
==========================================
  Hits         1121     1121
- Misses         96       99       +3

Impacted Files
Coverage Δ

config/kube_config.py
83.07% <0%> (-0.79%)
:arrow_down:

Continue to review full report at Codecov.

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

Can confirm this patch fixed #84

I'm new at this whole github contributing thing, but if you change the _load_azure_token(self, provider) function to the following, it fixes the ValueError: invalid literal for int() with base 10:

@lbach Any chance this can be finished? It'd be a huge help to us to have this working. Thanks!

#84 gets fixed by #141. Closing this in favor of that one

Verified this is broken in kubernetes==10.0.1 and working in prerelease kubernetes==11.0.0b2

Verified this is broken in kubernetes==10.0.1 and working in prerelease kubernetes==11.0.0b2; looking forward to a GA release of 11.

Thanks for the verification! We are working on releasing 11.0.0 GA. I added an item in the bi-weekly meeting agenda. cc @palnabarun


Yosys Verilog Parsing Error: Unable to Synthesize After Reading File

Version
yosys 0.41+126
On which OS did this happen?
Linux
Reproduction Steps
Hello,
I encountered an error while using Yosys to read a Verilog file. The steps and the error message are as follows:

After this error, the parsing process is interrupted. I have checked the Verilog file for syntax errors but couldn't find any obvious issues. I am using the latest version of Yosys.
Attached is the Verilog file (design.v) that triggers the error.
Thank you in advance for your attention to this matter.
I look forward to hearing from you regarding this issue.
design_file.zip
Expected Behavior
synthesis success
Actual Behavior
synthesis fail

Changing lines 31 and 32 to the following makes it compile fine:
                  reg289[(3'h6):(3'h5)] : {"Q",
                      ($unsigned((8'hb6)) ? "t" : "e")}));

Looking at the source where the assert is being raised it seems to be a problem with the parsing of string constants: // create an AST node for a constant (using a string in bit vector form as value).  The git blame in that section also has the commit message "Fixed constant "cond ? string1 : string2" with strings of different size," which leads me to suspect that this is the same bug that was previously believed to be fixed.

Minimal example:
module top ();
wire [23:0] x = {"1", "\0", "1"};
endmodule