Telegram connector cannot handle empty text in hero cards

When you send a message activity to Telegram, it works fine when the activity's text property is empty. It also works fine if you send a hero card with only buttons and no title, subtitle, or text properties. However, if you set an empty string as one of those properties, you will get an error like this:
{
  "error": {
    "code": "ServiceError",
    "message": "Bad Request: message text is empty",
    "innerHttpError": {
      "statusCode": 400,
      "body": {
        "ok": false,
        "description": "Bad Request: message text is empty",
        "error_code": 400
      }
    }
  }
}

Telegram seems to be a channel that can separate one activity into multiple messages in situations like these. I suspect what's going on behind the scenes is that the connector looks at a hero card's title, subtitle, and text properties and tries to form a message out of them if they're not null. However, it runs into problems if the only available non-null strings are empty.
At least one customer is having issues because of this: https://github.com/microsoft/BotBuilder-V3/issues/157
Repro steps

Send a hero card to Telegram where at least one of title, subtitle, or text is an empty string and all of them are null or empty
See error

Expected behavior
The Telegram connector should treat empty strings the same as null in this case.

Fix available -- should be deployed before 10/18

I sent a hero card with empty title, subtitle and text and it worked fine:

If you still need a fix, please attach the exact repro case.
Do I understand correctly that using null instead of empty string works? If so, just use null.

I'm very sorry Artur! It looks like I did leave out some vital information from the original post. This can't be reproduced with just the empty strings, and it also can't be reproduced by including images in the card. It only happens when the card has buttons.
Here's a repro for C#:
public static async Task TestEmptyHeroCardAsync(ITurnContext turnContext, CancellationToken cancellationToken)
{
    HeroCard heroCard = new HeroCard(string.Empty, buttons: new List<CardAction>
    {
        new CardAction("imBack", "imBack title", value: "imBack value"),
    });

    await turnContext.SendActivityAsync(MessageFactory.Attachment(heroCard.ToAttachment()), cancellationToken);
}

Here's a repro for Postman:
POST /v3/conversations/123456789/activities HTTP/1.1
Host: telegram.botframework.com
Content-Type: application/json
Authorization: Bearer <token>
Cache-Control: no-cache
Postman-Token: <guid>

{
  "type": "message",
  "attachments": [
    {
      "contentType": "application/vnd.microsoft.card.hero",
      "content": {
      	"title": "",
      	"buttons": [
      	  {
      	    "type": "imBack",
      	    "title": "imBack title",
      	    "value": "imBack value"
      	  }
      	]
      }
    }
  ],
  "from": {
    "id": "YourBot",
    "name": "YourBot"
  }
}

Fix available. Deployment ETA 10/24

Fix deployed


proposal: Hide Test internals. Expose a delegate object instead.

We expose instances of Test to the user. It's the t in the following code:
test('title', t => {
  t.is(foo, bar);
});

That has all kinds of internal information on it, including

assertCount
planCount
duration
_timeStart
planStack
etc, etc, etc.

We are already looping over all the public methods and binding them to the test here so users can pass around methods without worrying about this bindings.
I suggest we copy those values (perhaps being a bit more careful to select only that which we truly want public), to a secondary object that we expose.

:+1: from me. @vdemedes ?

What if we just made them non-enumerable? So that we won't need to use this.options.assertCount instead of this.assertCount inside lib/test.js itself.

We would not need to do that. We would create a different object, and put methods on it that were bound to the test instance test:
Test.prototype._createPublicAPI = function () {
  var api = {};
  var self = this;
  listOfPublicMethods.forEach(function (methodName) {
    api[methodName] = self[methodName].bind(self);
  });
};

Or we could use delegates.
The problem with non-enumerable is that they can still be clobbered. I am working on #25 (registering custom assertion methods) - and we don't want to have to force them to avoid our internals as they name their method.

Oh, I get it now. delegates usage would be really good, love this module.


functions are running on different port while frontend is running on another port

Describe the bug
Netlify functions are not running on port 8888, the functions are listening on some random port 60248 which is causing error in running locally
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Run git clone git@github.com:owner/repo-with-cli-bug.git
Navigate to the cloned repository
Run netlify dev
See that the CLI exits with an error

Configuration

If possible, please copy/paste below your netlify.toml.
Please enter the following command in a terminal and copy/paste its output:

npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify-cli

Expected behavior
A clear and concise description of what you expected to happen.
CLI Output
If applicable, add the CLI output to help explain your problem.
Additional context
Add any other context about the problem here.

@croaky

Hi @saswatsam786, can you fill in the missing parts from the issue template?
Specifically To Reproduce, Configuration and Expected behavior.
Running the functions server on a different port is the expected behavior. Can you describe what issue it's causing for you?

Actually, the function addData is not working on (http://localhost:8888/.netlify/functions/addData)  as specified but it is working on port 60248.

Thanks @saswatsam786, can you share a reproduction scenario that reproduces the "not working on port 8888" and "working on port  60248".
The function should work on port 8888, so it would be great to understand the reason it doesn't

Is there some news about this problem? One year later and I have the exact same problem, functions are listening on some random port wich I can't call from my frontend. :(

Same problem here ... functions are running in a random port every time

I had Netlify CLI installed globally, I just tried installing it locally and it works!
npm install --save-dev netlify-cli
It may be worth it to try installing it locally if you're still experiencing issue like me!

Marking this as stale as it is is several years old. Please feel free to reopen if you are still having issues.


A few tweaks to give the junit reporter enough to work with

Supersedes https://github.com/webdriverio/wdio-mocha-framework/pull/5

Could we squash all these commits into one commit?

https://github.com/webdriverio/wdio-mocha-framework/pull/9


SSL reverse proxy support

With a web browser, if we try to access the AAR webapp behind the Traefik reverse proxy on the testbed, we have a blank page because the AAR webapp is not designed to work behind a reverse proxy. However, a reverse proxy is required for communication security, i.e. SSL/TLS protection. You can test it with an Apache or NGINX (with SSL enabled) instead of Traefik to reproduce the issue outside the testbed.

@thoobr : Can you please clarify:

how i can set up my local environment to test/reproduce this or
where i can access this in a hosted environment

any progress on this?


Merge prTesting_201905021039 branch to master branch

Docs Build status updates of commit 2732ce7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[INLONG-1984][Bug][InLong-Manager] Set Pulsar params for workflow form after submitting approval

Title Name: [INLONG-1984][Bug][InLong-Manager] Set Pulsar params for workflow form after submitting approval
Fixes #1984
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve?
Modifications
Describe the modifications you've done.
Verifying this change

[X] Make sure that the change passes the CI checks.

This change is a trivial rework/code cleanup without any test coverage.
Documentation

Does this pull request introduces a new feature? no

+1


Spatial analysis

Both the datasets have some unwanted columns so need to update pipeline to remove those column.

Add longitude and latitude column to dataset


[lecture12-2] [0619] Question about Non-Maximal Suppression Example.

Hello professor! I'm quiet curious about the NMS example.

By looking at the illustration, it is evident that only the box with an IoU of 0.7 has been filtered out during the IoU comparison process. This leads to two questions:

When performing the box removal process based on the 0.9 box, shouldn't the 0.6 (right) box also be removed, in addition to the 0.7 box, to achieve the prediction as shown in the left image?
If the IoU threshold is high and the 0.6 (right) box was not filtered out, would this 0.6 (right) box remain and be included in the final prediction? Consequently, would there be two prediction boxes for the car on the right side in the left image?

Thank you for taking the time to read my questions!
YongHyeon Jun

@imsongpasimin Thank you for the comment!

I think it depends on the setting of the NMS (Non-Maximum Suppression) threshold. Assuming that a box with a confidence score of 0.9 and a box with a confidence score of 0.6 (on the right) have an IOU (Intersection Over Union) of about 0.4, if we set the threshold tighter, we will remove the 0.6 box (on the right).
Yes, in our example, the 0.6 box (on the right) will remain in the final representation, which is not adequate. Therefore, setting the NMS threshold is also a critical factor for detection performance.

Have a nice vacation:)


Bump go version to support go modules in CAO

Prerequisite for https://github.com/openshift/cluster-autoscaler-operator/pull/118

/approve
/lgtm

/lgtm


fix(clerk-js): Fix color usage and redo variable api

Description

Adding a new variable api in this PR. It's mostly renaming and adding the secondary and secondaryForeground, along with a textTertiary for more design control.
Text colors have been corrected to match designs and I've used some tricks on the secondary/ghost button variants to achieve desired hover states without sacrificing DX.

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/backend
[ ] @clerk/chrome-extension
[ ] @clerk/clerk-js
[ ] @clerk/clerk-expo
[ ] @clerk/fastify
[ ] gatsby-plugin-clerk
[ ] @clerk/localizations
[ ] @clerk/nextjs
[ ] @clerk/clerk-react
[ ] @clerk/remix
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/themes
[ ] @clerk/types
[ ] build/tooling/chore

!preview

Hey @desiprisg, your preview is currently deploying and should be available shortly.

Status
Preview
Updated (UTC)

:cook: Deploying...
Inspect
Jan 30, 2024 05:58 PM

!preview

!preview

!preview

!preview

!preview


Allow non-users to submit issues

It would be great if there were a way for non-users to submit issues to public repositories. I wouldn't want to allow anonymous issues, however perhaps you could add GitHub authentication which defaults to a new User Type of Issues Only... just a suggestion. Great project.

+1

+1 definitely
----- Reply message -----
Von: "Julio Molina Soler"<EMAIL_ADDRESS>An: "takezoe/gitbucket"<EMAIL_ADDRESS>Cc: "Dwarfex"<EMAIL_ADDRESS>Betreff: [gitbucket] Allow non-users to submit issues (#208)
Datum: Di., Jan. 27, 2015 17:45
+1
—
Reply to this email directly or view it on GitHub.

+1

Merged with #1286


Build Errors on AARCH for S4J Adapter due to Out of Date Conscrypt Dependency

Describe the bug
My new mac is an M3 which is osx-aarch_64 - I am getting the following building nosqlbench:
[ERROR] Failed to execute goal on project adapter-s4j: Could not resolve dependencies for project io.nosqlbench:adapter-s4j:jar:5.21.4-SNAPSHOT
[ERROR] dependency: org.conscrypt:conscrypt-openjdk:jar:osx-aarch_64:2.5.2 (compile)
[ERROR] 	Could not find artifact org.conscrypt:conscrypt-openjdk:jar:osx-aarch_64:2.5.2 in central (https://repo.maven.apache.org/maven2)
[ERROR]

Basically org.conscrypt is a few years out of date. https://mvnrepository.com/artifact/org.conscrypt/conscrypt-openjdk
We are #4 on the usage list: https://mvnrepository.com/artifact/org.conscrypt/conscrypt-openjdk/usages
We have DS releases from April for DSE: https://mvnrepository.com/artifact/org.conscrypt/conscrypt-openjdk?repo=datastax-public-releases-local
Two questions:

Should we switch to the DS ones?
I know that a new version of S4J has been created and maybe an update to this adapter would fix this issue.

To Reproduce
Steps to reproduce the behavior:

mvn clean install

What was Expected
A completed build.
Additional context
Add any other context about the problem here.
OS: macOS w/Apple Silicon

Neither of the dse versions work out of the box.


Now glance's painting has only one 3D mode, actually, the 2D mode may more useful, is it in the TODO list?

Yes, that would be useful. The underlying paint widget already supports 2D mode, so hopefully it won't be too much of an effort to add it in. I'll look to add it in when I get the chance.

Yes, that would be useful. The underlying paint widget already supports 2D mode, so hopefully it won't be too much of an effort to add it in. I'll look to add it in when I get the chance, unless you would like to take a shot at it (check out vtk.js vtkPaintWidget and vtkPaintFilter).

I am looking forward to your great work. And I'm not familiar with vtk.js, but I will look into this, thank you very much.

:tada: This issue has been resolved in version 4.11.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


EMP Troubles in 1.14.3

Not quite related to #439 -- for that one I was able to get what I needed by using redstone blocks (still didn't work on any of the other powerables). Now in Spigot 1.14.3 (CraftBukkit version git-Spigot-d05d3c1-fca4157 (MC: 1.14.3) (Implementing API version 1.14.3-R0.1-SNAPSHOT)) I'm getting the "Something went wrong!" error using the default EMP spell -- won't fire at all now, and this error in console: https://gist.github.com/mercurialmusic/9ee64e5becf0cb7fe50309db606e57ea
Thanks!

I finally got this fixed in 7.7.5
Sorry for the long delay!

Thank you for this! It is functional now on buttons and we're very excited for that, but just for the sake of ironing out wrinkles, it does fail completely if the spell detects a redstone block in the area, error here: https://gist.github.com/mercurialmusic/14ea9b666548108027b3da26d06b6684

Oops, thanks! I think I've got that fixed, though I didn't get a chance to test it. Dev build is building now.


[9.x] Handle when $haystack is null in Str::contains

Fixes this deprecation message from str_contains:
str_contains(): Passing null to parameter #1 ($haystack) of type string is deprecated

The deprecation warning appears when running this in a fresh install:
LOG_DEPRECATIONS_CHANNEL=stderr php artisan route:list --name foo

I opted to place it first in the method since there is no need for anything else to run.
This also has the bonus to fix the potential deprecation warning of passing null to mb_strtolower

Okay. The problem, in this case, is these Str::contains checks.
https://github.com/laravel/framework/blob/692a634cba2c4b402734e7d0549bdf5328f0ccac/src/Illuminate/Foundation/Console/RouteListCommand.php#L243-L249
Not really sure what the best approach is to fix that

Cast those to a string, probably, before calling.

Likely this bug is also present on 8.x, so needs fixing there too?

This method does not allow passing a string. Typecast the value before passing.

I have a failing test for it here at least https://github.com/hmazter/framework/commit/efc8bc8ffb5831e4506bb2a0dddd513ee882d94d
Not sure what to do with it though


Doubly linked list with python

Have you read the Contributing Guidelines on Pull Requests?
YES
Description
I have added a doubly-linked list using python
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.

Related Issues or Pull Requests
Adding doubly linked list using python
Issue: #625
Fill up the DCP form
If you are a part of DCP 21, fill up this form after the PR is merged.
The links provided in the form will be checked thoroughly, if someone tries fooling around, strict actions will be taken against the individual.

Nicely done @kumarankm


Alt+Space conflicts with standard windows behavious for Powertoys Run

Description of the new feature / enhancement
Alt+Space shows the system menu on any Window in all versions of Windows. This cannot be changed.
Scenario when this would be used?
The Alt+Space settings is used if a mouse is not available or not functional.
Supporting information
Standard Windows shortcuts should not be avoided by applications.

/dup https://github.com/microsoft/PowerToys/issues/4533


cannot load such file -- mysql2psql/connection

/vagrant/mysql2postgres (2.1.3p242)
λ mysqltopostgres
/usr/local/lib/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- mysql2psql/connection (LoadError)
        from /usr/local/lib/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from /var/lib/gems/2.1.0/gems/mysqltopostgres-0.2.15/lib/mysql2psql/postgres_db_writer.rb:2:in `<top (required)>'
        from /usr/local/lib/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from /usr/local/lib/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from /var/lib/gems/2.1.0/gems/mysqltopostgres-0.2.15/lib/mysqltopostgres.rb:22:in `<top (required)>'
        from /usr/local/lib/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from /usr/local/lib/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:in `require'
        from /var/lib/gems/2.1.0/gems/mysqltopostgres-0.2.15/bin/mysqltopostgres:7:in `<top (required)>'
        from /usr/local/bin/mysqltopostgres:23:in `load'
        from /usr/local/bin/mysqltopostgres:23:in `<main>'

@paazmaya this issue is still happening, could you release a new version? :)

I am experiencing the same issue, my details:
➜  dailyalbum.us git:(to_pg) ✗ cat Gemfile | grep -i mysqltopostgres
gem 'mysqltopostgres'

➜  dailyalbum.us git:(to_pg) ✗ gem list | grep -i mysqltopostgres
mysqltopostgres (0.2.15)

➜  dailyalbum.us git:(to_pg) ✗ mysqltopostgres
/Users/ericlondon/.rvm/gems/ruby-2.2.3@dailyalbum/gems/mysqltopostgres-0.2.15/lib/mysql2psql/postgres_db_writer.rb:2:in `require': cannot load such file -- mysql2psql/connection (LoadError)
	from /Users/ericlondon/.rvm/gems/ruby-2.2.3@dailyalbum/gems/mysqltopostgres-0.2.15/lib/mysql2psql/postgres_db_writer.rb:2:in `<top (required)>'
	from /Users/ericlondon/.rvm/gems/ruby-2.2.3@dailyalbum/gems/mysqltopostgres-0.2.15/lib/mysqltopostgres.rb:22:in `require'
	from /Users/ericlondon/.rvm/gems/ruby-2.2.3@dailyalbum/gems/mysqltopostgres-0.2.15/lib/mysqltopostgres.rb:22:in `<top (required)>'
	from /Users/ericlondon/.rvm/gems/ruby-2.2.3@dailyalbum/gems/mysqltopostgres-0.2.15/bin/mysqltopostgres:7:in `require'
	from /Users/ericlondon/.rvm/gems/ruby-2.2.3@dailyalbum/gems/mysqltopostgres-0.2.15/bin/mysqltopostgres:7:in `<top (required)>'
	from /Users/ericlondon/.rvm/gems/ruby-2.2.3@dailyalbum/bin/mysqltopostgres:23:in `load'
	from /Users/ericlondon/.rvm/gems/ruby-2.2.3@dailyalbum/bin/mysqltopostgres:23:in `<main>'
	from /Users/ericlondon/.rvm/gems/ruby-2.2.3@dailyalbum/bin/ruby_executable_hooks:15:in `eval'
	from /Users/ericlondon/.rvm/gems/ruby-2.2.3@dailyalbum/bin/ruby_executable_hooks:15:in `<main>'

# then trying GH path in Gemfile:

➜  dailyalbum.us git:(to_pg) ✗ cat Gemfile | grep -i mysqltopostgres
gem 'mysqltopostgres', git: 'https://github.com/maxlapshin/mysql2postgres.git'

➜  dailyalbum.us git:(to_pg) ✗ bundle install
Updating https://github.com/maxlapshin/mysql2postgres.git
Fetching gem metadata from https://rubygems.org/............
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies...
Bundler could not find compatible versions for gem "activerecord":
  In snapshot (Gemfile.lock):
    activerecord (= 4.1.8)

  In Gemfile:
    activerecord (= 4.1.8) ruby

    mysqltopostgres (>= 0) ruby depends on
      activerecord (~> 3.2) ruby

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

thanks

I got similar problem:
WARN: Unresolved specs during Gem::Specification.reset:
i18n (>= 0.6.4, ~> 0.6)
multi_json (~> 1.0)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
/var/lib/gems/2.1.0/gems/mysqltopostgres-0.2.20/bin/mysqltopostgres:30:in <top (required)>': '' does not exist (RuntimeError) 	from /usr/local/bin/mysqltopostgres:23:in load'
from /usr/local/bin/mysqltopostgres:23:in `'

+1!

Same issue here. Would be good to release an updated gem with the latest changes!

This issue is very common
$ mysqltopostgres
/home/wilfried/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in `require': cannot load such file -- mysql2psql/connection (LoadError)
	from /home/wilfried/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in `require'
	from /home/wilfried/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/mysqltopostgres-0.2.15/lib/mysql2psql/postgres_db_writer.rb:2:in `<top (required)>'
	from /home/wilfried/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
	from /home/wilfried/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
	from /home/wilfried/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/mysqltopostgres-0.2.15/lib/mysqltopostgres.rb:22:in `<top (required)>'
	from /home/wilfried/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
	from /home/wilfried/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
	from /home/wilfried/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/mysqltopostgres-0.2.15/bin/mysqltopostgres:7:in `<top (required)>'
	from /home/wilfried/.rbenv/versions/2.2.3/bin/mysqltopostgres:23:in `load'
	from /home/wilfried/.rbenv/versions/2.2.3/bin/mysqltopostgres:23:in `<main>'

:+1:

Unfortunately I do not have the rights to publish... #85


fix(nativescript): with ivy

@hrueger This will get ya going - and with Ivy enabled.
npm run clean

Then
npm run android

@NathanWalker Yes, it works!!! Thank's a lot. I belive it was an error with the webpack.config.js file.


Allow Kap to be running without being moved to the Applications folder

Platform: MacOS V10.12.6 Sierra 2015 Macbook Air
Step to reproduce :  Download zip file and run the .app file.
Current behaviour: Alerts that program needs to be in applications folder and closes the program
Expected behaviour : Should alert you once, and not close the program
Workaround: Use an older version of Kap.

I run a school issued computer, so I cannot install .dmg applications, and I am not administrator, so I cannot move it to the Applications folder. It is a very useful application, and I hope you can make this available as a portable version or fix this issue.

We did this to work around an issue we were having, but hoping we can make it possible to run Kap without moving it to your Applications folder for our next major release (cc: @sindresorhus). Best of luck with your studies!

Thanks so much :)

It works for me having it in ~/Applications

I can't make it work neither in /Applications nor in ~/Applications
All I get is: "Please move Kap to your Applications folder to ensure it runs correctly."

Closing for lack of response. This is most likely fixed in v3.


[BUG] "Version to Install" Not Showing

Please confirm these before moving forward

[X] I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
[X] I have tested that this issue has not been fixed in the latest (beta or stable) release.
[X] I have checked the FAQ section for solutions.
[X] This issue is about a bug (if it is not, please use the correct template).

UniGetUI Version
3.1.4
Windows version, edition, and architecture
Windows 11 Home
Describe your issue
Even though UniGetUI seems to be detecting past versions of a package, it's not putting them in the dropdown and allowing me to change the version to install.
Steps to reproduce the issue

Right-click any package
Observe the unusable "version to install" dropdown

UniGetUI Log
[12/19/2024 4:43:40 PM] Found 218 versions for package Id=google-api-python-client on manager Pip

Package Managers Logs
Logged subprocess-based task on manager Pip.  It may be removed/changed in a future release without prior warning.

Return code: SUCCESS (0)

Relevant information
This has been the case for any package I view the installation options for, even though I can see that UniGetUI is detecting the versions internally through the logs.
Screenshots and videos

When updating a package, you can't change the install option, as the update command does not accept a version parameter. You should reinstall the package in order to get the option to change the version

That makes sense. However, in trying to reinstall the program I uninstalled to test this (appdirs) the search feature wasn't coming back with any Pip results, and running the commands to search for the package came back with this error. Although, I feel like I've seen this error way prior than a day or so ago; has it always been like this? And if so, why is parse_pip_search suddenly failing to work?
Perhaps this is part of the problem referenced by #3079?
C:\Users\<username>\Projects\Windows\UniGetUI>C:\Users\<username>\AppData\Local\Programs\Python\Python312\Scripts\parse_pip_search.exe appdirs
 Package | Version | Description
---------------------------------

C:\Users\<username>\Projects\Windows\UniGetUI>pip search appdirs
ERROR: XMLRPC request failed [code: -32500]
RuntimeError: PyPI no longer supports 'pip search' (or XML-RPC search). Please use https://pypi.org/search (via a browser) instead. See https://warehouse.pypa.io/api-reference/xml-rpc.html#deprecated-methods for more information.

Parse-pip-search seems to have broken.
In fact, the original pip-search (https://pypi.org/project/pip-search/), from where I forked and created parse-pip-search, seems to not be working either.
C:\>pip_search pyside
   🐍 https://pypi.org/search/?q=pyside 🐍
┏━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━┓
┃ Package ┃ Version ┃ Released ┃ Description ┃
┡━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━━╇━━━━━━━━━━━━━┩
└─────────┴─────────┴──────────┴─────────────┘


'Viewpoint Detector' Question

Hi,
In the dataset which is 'cviqd_resize_imgtrain' and 'cviqd_resize_imgtest' folder, containing 20 viewport images.
It is described in Viewpoint Detector (in the paper). I want to dive into this work, and it seems like lack of this work in your project.  Can you provide more about it?

Hi,
In the dataset which is 'cviqd_resize_imgtrain' and 'cviqd_resize_imgtest' folder, containing 20 viewport images.
It is described in Viewpoint Detector (in the paper). I want to dive into this work, and it seems like lack of this work in your project. Can you provide more about it?

The code for 'Viewpoint Detector' is on another server. We will organize the code and release it soon.

thank you


[Bug] Another issue with MoM (Steam) 1.9.3 - Tiles/Monsters/Actions

Team,
I discovered another issue with Valkyrie 2.5.8 and MoM (Steam) 1.9.3.  In addition to the aforementioned inability to find the files, anytime Valkyrie runs, it displays an odd characteristic at certain points.  The lettering changes to ALL CAPS.
This occurs at the "choose investigators" page and at other points in the program.  This happens with Tiles, Objects, and Monster actions.  I have attached screenshots.
Additionally, when interacting with monsters, the attack function and evade function are unplayable, as can be seen in the screenshots.  I believe this has something to do with Valkyrie not recognizing the MoM 1.9.3 files.
Thank you.

@MRex21z , it looks like a typical problem with the import file. Try to reimport the files from the official app, if possible.

I don't know what that means.
Valkyrie won't reimport the data...at all.  When I click on "reimport data," a window opens up where I can navigate to the MoM (Steam) assets where I can click on the MoM executable.  When I do that, nothing happens.

Closed. Issue has been fixed in Release https://github.com/NPBruce/valkyrie/releases/tag/release%2F2.6%2F2.6.0a.


Add PoS support

When submit block fo PoS coin (I 've tried CryptogenicBullion CGB) got error:
2014-09-19 08:48:18,772 [jobmanager] [INFO] Block failed to submit to the server <IP_ADDRESS>:8395 with submitblock! Unable to sign block, wallet locked?
2014-09-19 08:48:18,772 [jobmanager] [ERROR] {u'message': u'Unable to sign block, wallet locked?', u'code': -100}
Traceback (most recent call last):
  File "/home/vital/tmp/powerpool/powerpool/jobmanager.py", line 188, in submit_block
    res = conn.submitblock(block)
  File "/usr/local/lib/python2.7/site-packages/bitcoinrpc/authproxy.py", line 127, in __call__
    raise JSONRPCException(response['error'])
CoinRPCException: Unable to sign block, wallet locked?

The signing would be wrong because it is missing the pubkey and instead is using the address.

how about how much would that be worth ?


Simplifications, more debug

some simplifications reading PNG_INFO_... flags, avoids further png_get_valid calls.
add a message saying that libpng_api.jl is auto-generated
added checks on valid_bKGD and valid_PLTE
simplify png_set_gamma logic (strictly equivalent)
more debugging info when JULIA_DEBUG=PNGFiles is set

Happy to merge this once the CI is green

Happy to merge this once the CI is green

It hangs :(


Interactive debugger (CLI and DAP Server) for probe-rs

This introduces some changes to probe-rs library as well as a new debugger component to allow interactive debugging on top of probe-rs.
There is still lots of room for additions/completion, but I'm submitting it now because there is enough structure and functionality to demonstrate what is possible, and allow others to contribute in parallel.
For now the binary is called probe-rs-debugger, and in conjunction with the VSCode debug extension , provides the following capabilities:

[x] Launch: Automatcially launch probe-rs-debugger executable and connect to it, or ...
[x] Attach: Use TCIP/IP port to connect to an existing probe-rs-debugger server
[x] Connect to probe with probe-rs

[x] Supports connect-under-reset
[ ] Only tested against STM32H745, using the Cortex-M7 core of this multi-core chip.

[x] Flash the chip with your own binary.

[x] Supports reset-after-flashing
[x] Supports halt-after-reset. This will allow you to set breakpoints in your main() function.

[x] Set, clear, disable, enable Breakpoints
[x] Step Over executing code

[x] Step Over works at 'instruction' granularity, so sometimes requires multiple steps per line of code
[ ] Stepping at 'line' level, Step Into, Step Out, does not work yet

[x] Variables View

[x] View values of core Registers, and changes during code execution

[ ] TODO: Expand to show additional architecture registers

[x] View values of Locals variables, and changes during code execution.

[x] Shows datatypes and values for the following Rust datatypes.

[x] Base types, including &str
[x] Enumerations
[x] Structures
[x] Pointers
[x] Variants

[ ] TODO: Add support for all data types, such as Arrays, Unions, Generics, etc.
[ ] TODO: Filter the list of local variables to ONLY display variables that are in scope of the current register PC value. Currently ALL local variables are shown.

[ ] TODO: Expose Static and Global variables

[x] Call Stack View

[x] Supports a single thread, for a single core of the chip, but will allow selection of any frames that are in the current thread
[ ] TODO: Support multiple threads
[ ] TODO: Support chips with multiple cores

[ ] TODO: Watch View
[ ] TODO: Support for ITM or RTT

If you run git rebase master on your branch, and then force push it, this should get rid of the overwrites. Just ensure the master branch is updated before you run it.

Sorry for doing these comments in separate reviews, this should be the last of them.

No worries, this was a big PR, and I really appreciate the attention to detail in your review. I'm working my way through them, and will check-in an update soon. Or would you prefer smaller pushes?

@Yatekii ... Some comments below for futher discussion,

When trying to halt the core in vscode the DAP server crashes with Probe(ProbeSpecific(CommandFailed(SwdApWdataError))). Did you experience that too? I feel like this is a probe-rs issue in general, but I think the DAP server should not crash.

No, I don't get that error on halt. If it persists for you we should try to trace it and catch it. In general, I find that the probe-rs Error structs catches errors behind a single string, and that obfuscates what the root cause of the error was. Perhaps we can think about a more consistent error handling for probe-rs components?
Currently the DAP Server serves a single session, and then exits. If that session encounters an error with the Probe, it ends the DAP Client session - I do this because for Probe errors, it is hard to know how to reliably re-synch the DAP client to the new state. When the DAP Client session ends, it terminates the server. I've added a TODO to extend it to reconsider this behaviour, but it will need a larger implementation than I think will fit in this PR. Are you OK if we park it with a TODO for now?

I feel like if I add and remove a few breakpoints, after some time it does not set them properly anymore. VSCode shows a hover info that the breakpoint is scheduled for placement (grey breakpoint).

Yes, I can reproduce this. It seems that the underlying probe-rs clear_all_hw_breakpoints() do not always succeed when it returns with an Ok, and then the debug_adapter tries to add more than the allowable number of hardware breakpoints. I am working on trying to pinpoint and fix this.

It seems to not get nice enough debug info from LLVM, but not much we can do here atm.

Agreed. What is the specific debug info you are looking for?

It does not log much info and RUST_LOG=debug has no influence on logs.

RUST_LOG is now fixed (will be pushed soon).
I did not add a lot of rust log/warn/info statements,  because I chose to do logging via the DAP Client Debug Console, so that the user can see logs in the same UI where they are debugging. I'm open to discussion, and I have a TODO to find a way of integrating rust logs with DAP Client Debug Console logs.

When I start the extension from within VSCode it prints no logs at all. When I start it externally and connect via TCP I see some logs in VSCode, but not really much useful stuff. Where does that difference come from.

VSCode extenion logs are of marginal use (my humble opinion). I chose to implement user facing logs that shows up in the Debug Console for users who install the Extension the normal way. This is also the way gdb/openocd tends to work when you specify log levels in the launch.json. As always, I am open to discussion on that. Did you look at the "Debug" setting for "console_log_level" in the launch.json?

After I fixed the macOS specific error @Tiwalun already pointed out, it went quite smooth, appart from the things you already pointed out in the PR description :)
I think we can very well coordinate efforts from on here to fix existing papercuts :)

@Yatekii ... Thanks. I appreciate all the positive feedback and help getting this PR cleaned up.  Some final notes before I check this in ...

I've done some digging on the breakpoints, and think I've got it figured out ... will fix it after this PR is through.
I ran a global regex search and replace, and added a space between /// and //, and their following text ... just because it's so easy to fix.

Thanks a lot!
bors r+


ANDROID:  useTestOrchestrator: true Does not work for Apps targeting API 30

ANDROID ISSUE
Current behavior
I've updated my configuration to include:
https://docs.saucelabs.com/testrunner-toolkit/configuration/espresso/
testOptions:
clearPackageData: true
useTestOrchestrator: true
My APP targets API 30.
When I run on Sauce, Pixel Device OS 11, target SDK 30,  I get
https://app.saucelabs.com/tests/bdbe1b0118e54312ac8d38eab3f1f15d
Your class does not have any tests.
When I run on Sauce, Pixel Device OS 11, target SDK 29, I get
https://app.saucelabs.com/tests/64532f77916e49f9bf6944dd1d6fd24b#1
Tests found, they run, but with failures.
Desired behavior
Tests are found and run.  clearPackageData is respected.
Config to reproduce
testOptions:
clearPackageData: true
useTestOrchestrator: true
Targets SDK 30.
Versions
Saucectl 0.65/0.66
Please update Test Orchestrator from 1.1.1 to 1.4.0+.  Version 1.1.1 was released on March 7th, 2019.
See:
https://developer.android.com/jetpack/androidx/releases/test

Can we get an update on this?  If I set to compile/target 28 it works.  But version 28 does not meet the minimum for submitting to the play store.
https://developer.android.com/distribute/best-practices/develop/target-sdk

I pinged our mobile engineers on this, since this isn't strictly saucectl related. I'll let you know once I hear back!
PS: For platform related issues/concerns/help, it's best to create a ticket with the Sauce Labs Support directly 🙇

To speed things up, @sanderson82 would you mind opening a ticket via https://support.saucelabs.com/hc/en-us/requests/new ? Our support crew is awesome 💪 and we'll be able to track & delegate this better!

@sanderson82
Can you please open a ticket with Sauce Support Team:
https://support.saucelabs.com/hc/en-us/requests/new
Feel free to link to this issue as well as your sauce username.
We'll help!


alternative geometries for lumped thermal models

At the moment the lumped thermal models assume a pouch cell geometry. We could get users to specify the cell surface area and volume in the parameters file so that the correct ratio can be applied in the Newton cooling. This would be useful if you wanted to do a 1D electrochemical model, with a lumped thermal model for a specific cell geometry.
The Nplus1D thermal models also assume a pouch cell model and will probably remain this way for now as they account for cooling from the face of the current collector (which would be would up in a jelly roll and therefore not open to the air for cooling). It should probably be clearer that these models are for pouch cells only.

If I understand correctly this affects only the cooling area that multiplies the cooling coefficient. If that is the case, should we just let the user specify this area, so there is no need to consider the different cases separately (pouch, prismatic and cylindrical)?

yeah exactly, my picture was when the user puts in parameters, they explicitly add surface area (but surface area for cooling, as you suggest, is more precise) and volume for that cell. and then in the submodel we use those params so we don't care what the geometry actually was

In fact, unless you need the volume of the cell for some other calculation, you could just pass the surface area for cooling per unit of volume (similar to the specific area defined for the electrode particles). Or maybe that can be confusing for the users?

yeah i'd be happy with either. might be useful to have volume for other calculations after the fact such as variable x per unit volume.

Makes sense. Then I would define cell volume (which if undefined could be calculated from the electrode thickness and so on) and the cell cooling area so users can play with it.

Following this discussion from a few months ago, it seems that the idea is to pass battery cooling surface area and battery volume as parameters (within the cell parameters, in the macroscale geometry section).
Would it make sense to define that if these two variables are not defined then it assumes a pouch cell? Or is it better to leave it to break and update all the parameter files?

Maybe we should be explicit in making people define the cooling area and volume. I think the less we assume the better, as people might easily miss assumptions that are hidden away.

Not sure what the latest is on this, but my thoughts for how to do this to best fit into the structure would be to pass an option geometry to the lumped model which can, for now, be "arbitrary" (default) or "pouch". Then just put an if statement in the either uses the surface area to volume ratio for cooling param or computes the cooling for the pouch (we could add other popular geometries if we wanted).
Then was choosing the thermal model as an option to the battery model we could do "lumped", "lumped (pouch)", etc.
In the parameters csv we can just put a single value in for the urface area to volume ratio for cooling  which we leave people to compute, along with a comment saying what geometry that was computed for.

Sounds good. Do we want to pass as a cell parameter the surface area to volume ratio or pass surface area AND volume?

not sure on that. probably pass both as the volume is fixed, but the cooling area can change (e.g. only cooling part of the cell)


Improve naming of remove methods

This PR

Deprecates the remove method for a more descriptive method remove_value
Deprecates the empty method for a more description method remove_empty
Uses swap_remove in a test where the order doesn't matter so why not

Why?
Using the standard lib as a North Star, remove should be a method that takes a key and removes that key from the map. In evmap, remove is meant to take a key and a value and remove just that value from the value bag for the key. To make that more clear, we deprecate remove and rename it to remove_value.
Unfortunately we can't then rename empty (evmap's version of the std HashMaps remove) to remove for backwards compatibility. Instead, we rename it to remove_entry.

This change is

Oh, and that code coverage is a good point - I imagine we should still be testing deprecated methods?

Hmm... No, I think it's fine to leave them out.


Adding back envoy next to Istiod, part 1

Option to run a sidecar/gateway alongside Istiod, as we did in 1.4 - but without the hardcoded
envoy config. Instead it will use localhost and the certs generated by istiod.
Currently envoy will configure itself as a gateway - we may use this for 'tiny' deployments
of istio or tests, and as a separate gateway for control-plane components, possibly using
internal load balancers. If someone choose to take advantage of this feature - the 'main' gateway will continue to be used for normal ingress, and the istiod-gateway can be used for control
plane or multi-network, without an external IP.
In addition this mode will allow us to possibly do better load balancing.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@costinm: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
0dbc909f533f588bca34dd4554d86b92bacc897e
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
0dbc909f533f588bca34dd4554d86b92bacc897e
link
/test gencheck_istio

lint_istio
0dbc909f533f588bca34dd4554d86b92bacc897e
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

When Istiod terminates connection after 15mins, will this envoy interfere with that lifecycle?

Yes, it will, see https://github.com/istio/istio/issues/11181
On Fri, Jun 19, 2020 at 10:51 AM mandarjog<EMAIL_ADDRESS>wrote:

When Istiod terminates connection after 15mins, will this envoy interfere
with that lifecycle?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/24821#issuecomment-646790779, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXL67CYXZH7XHOOFEWDRXOQTZANCNFSM4OC5JOYQ
.

I'm not sure: AFAIK Envoy has or we can add a way to terminate a connection after some time.
If it is a problem for Istiod load balancing connection - it would also be a problem for any other server handling long-lived connections.
So we should check with @PiotrSikora  and envoy people if it is already possible, if not it shouldn't
be extremely hard.
In addition we should be able to solve the problem WITHOUT closing connections - the real issue
is that a Istiod will get too many connections. Envoy has circuit breakers - it is a bit more complicated setup, but no different from what we would use with the normal Gateway and non-istiod applications that handle long-running connections. Again - if it is a problem that envoy can't handle, we should fix envoy so all apps benefits instead of a istio specific hack.

In other words:

backup plan: envoy terminates connections after 15 min, new setting if not already possible.

backup plan 2: Pilot sends a 'Go away' message, possibly with the IP of another less loaded istiod. Envoy may need to change to support this - or if we use agent as a proxy we can handle it without envoy changes

my preference (maybe in 1.8): the gateway will forward to 2 clusters, localhost and 'all other istiod'. For the second cluster we may need a second port ( that goes only to localhost ) to avoid loops.

Http protocol options supports max_connection_duration  and max_stream_duration   Which I think will work.

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
0dbc909f533f588bca34dd4554d86b92bacc897e
link
/test gencheck_istio

lint_istio
0dbc909f533f588bca34dd4554d86b92bacc897e
link
/test lint_istio

analyze-tests_istio
0dbc909f533f588bca34dd4554d86b92bacc897e
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@costinm: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
0dbc909f533f588bca34dd4554d86b92bacc897e
link
/test gencheck_istio

analyze-tests_istio
0dbc909f533f588bca34dd4554d86b92bacc897e
link
/test analyze-tests_istio

lint_istio
738f1de41d9b56b8717b8bfb47b72dae8f204a35
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
0dbc909f533f588bca34dd4554d86b92bacc897e
link
/test analyze-tests_istio

lint_istio
738f1de41d9b56b8717b8bfb47b72dae8f204a35
link
/test lint_istio

gencheck_istio
738f1de41d9b56b8717b8bfb47b72dae8f204a35
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
0dbc909f533f588bca34dd4554d86b92bacc897e
link
/test analyze-tests_istio

gencheck_istio
738f1de41d9b56b8717b8bfb47b72dae8f204a35
link
/test gencheck_istio

lint_istio
17dc6b9229cebde25f8e7ed2782bd6950ad35720
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
0dbc909f533f588bca34dd4554d86b92bacc897e
link
/test analyze-tests_istio

lint_istio
17dc6b9229cebde25f8e7ed2782bd6950ad35720
link
/test lint_istio

gencheck_istio
17dc6b9229cebde25f8e7ed2782bd6950ad35720
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
0dbc909f533f588bca34dd4554d86b92bacc897e
link
/test analyze-tests_istio

lint_istio
17dc6b9229cebde25f8e7ed2782bd6950ad35720
link
/test lint_istio

gencheck_istio
17dc6b9229cebde25f8e7ed2782bd6950ad35720
link
/test gencheck_istio

unit-tests_istio
17dc6b9229cebde25f8e7ed2782bd6950ad35720
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@costinm is this something you had in mind for 1.7? Branch cut happens tomorrow.

@costinm: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Base64url support?

Hi, aklomp i was searching for a nice base64 library and ended here but my low level C is a bit rusty, so i would like to ask you if this library could be used to handle base64URL variant? or at least some tips on how to add it?(i would post patches back if i made it)
Thanks  you very much for your time

Hi! Currently this library only supports the standard Base64 alphabet.
It would probably be feasible, but difficult, to add support for additional alphabets. It could be non-trivial to add that support to the SIMD codecs, because they do arithmetic on the raw character values. Here's an encoder example and here's a decoder.
My intuition is that it would probably be possible to find an arithmetic-based solution that works with the alternative alphabet since the differences are small. However, it would require duplicating a lot of code, and adding some sort of user-visible flag to the API to indicate which alphabet to use. Maybe it could be a compile-time flag to not incur runtime penalties or complexities.

since the differences are small. However, it would require duplicating a lot of code

Yeah, it's possible. I've done this for C#, but as @aklomp says there's a lot of duplication and the nice tricks applied to standard base64 don't work so nice with base64Url. Especially on the decoding side for input-validation.

Thank you very much for your time.
Yeah, i see your point and probably will be easier to handle base64url to base64 translation externally in the c++17 side of thing since the chunk are small and this library already give me a nice speed up so i have some wiggle room.

There's an example of translation in https://github.com/mayeut/pybase64/blob/1e2f3ec63549085f06b3118671818edb969c1e3d/pybase64/_pybase64.c#L71
The translation is done in-place for encoding.
The translation is done out-of-place for decoding (warning, the translation is not safe here to mimic python behavior, c.f. inline comment)

well for now a very simple std implementation seems to do the job with very small assembly output
https://godbolt.org/z/8J2zKG

What is being asked is to just accept base64url format when decoding.  Replacing characters 62 and 63 is best done at https://github.com/aklomp/base64/blob/master/lib/tables/tables.c Supporting encoding would require more work...

a sample lookup table used in https://github.com/emmansun/base64
// The input consists of six character sets in the Base64 alphabet, which we
// need to map back to the 6-bit values they represent. There are three ranges,
// two singles, and then there's the rest.
//
//  #  From       To        Add  Characters
//  1  [45]       [62]      +17  -
//  2  [48..57]   [52..61]   +4  0..9
//  3  [65..90]   [0..25]   -65  A..Z
//  4  [95]       [63]      -32  _
//  5  [97..122]  [26..51]  -71  a..z
// (6) Everything else => invalid input
//
// We will use lookup tables for character validation and offset computation.
//
// For offsets:
// Perfect hash for lut = ((src >> 4) & 0x0F) - ((src > 0x5e) ? 0xFF : 0x00)
// 0000 = garbage
// 0001 = garbage
// 0010 = -
// 0011 = 0-9
// 0100 = A-Z
// 0101 = A-Z
// 0110 = _
// 0111 = a-z
// 1000 = a-z
// 1000 > garbage
//
// For validation, here's the table.


Release 10.7.0

Changelog
[10.7.0] - 03.02.2023
Components changes

Tooltip:

Remove redundant css rules

Sidebar:

Added functionality for scrolling on first level
Added max-width for correct text break
Added text-align: center

Dropdown:

Update z-index

Button:

Update button-group css rules: display flex & flex-wrap & gap style

Design Guide documentation changes

Interactive playground:

As part of our new component preview, we softly introduce to you the ability to directly tweak and test our components in a sandbox.
Patterns: Form and Login, has the new component preview.

NPM dependencies upgrade

Azure/CLI
ESlint
Webpack-CLI
@Babel/core
PostCSS
Favicons

Table component documentation

Added some more information regarding tables and mobile devices.

Badge component documentation

Added documentation about using classes badge-default, badge-inactive and badge-warning
Added correct font for PayEx brand

Redirect to newest version (ground work)

Added writing a new latestVersion.json fil in our Azure container. This is a future task for ensuring users know they are on a older version of DG while browsing.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: eskilsen:white_check_mark: goldenraphti:x: hmosvollYou have signed the CLA already but the status is still pending? Let us recheck it.


Example viz vignette

This isn't finished yet, just thought I'd put my current progress up for comment.

Coverage increased (+6.9%) to 67.021% when pulling f81f98f2388dce49fb49ca68c80b164783a63961 on wdwatkins:master into 57f570c8aa666c4dcff5d7ceea800899e09a2fbd on USGS-VIZLAB:master.

Coverage remained the same at 66.294% when pulling 5c0c813cb7cd3a7a928e3e2363f2395441956aab on wdwatkins:master into 4753dc03d2950ee09623127827a3cd972d7cd3cb on USGS-VIZLAB:master.


No module named 'somewhere_else'

from somewhere_else import access_id, secret
No module named 'somewhere_else'

ok somewher my setting file for id ,secret
tnx


use reporters

Using reporters will allow modular implementation of the CLI, allowing different experiences for the users.
A good example of this kind of implementation can be found at https://github.com/peerigon/updtr.

Fixed in v0.4.0


fix: adjust banner text

What it solves
Updated banner text.
How this PR fixes it
The banner text now reads:
Safe's new official URL is app.safe.global, with a fully rebranded and refurbished application. The old app will run in parallel and we will announce its deprecation in time.

How to test it
Open the app and observe the new banner text.
Screenshots

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.003%) to 41.902%

Files with Coverage Reduction
New Missed Lines
%

src/components/PsaBanner/index.tsx
1
0%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
4777

Relevant Lines:
10406

💛  - Coveralls


Use NonBlocking instead of ConcurrentDictionary

Maybe we can increase the speed when https://github.com/VSadov/NonBlocking is used instead of ConcurrentDictionary?

Thanks, I'll take a look at this once I complete work on ConcurrentLfu.


Add Halftone Effect

Related issue: #588
Description
Adds a halftone effect to the v7 branch. Halftone effect is a port of the Three.js effect.

@vanruesc Thanks for your reviews and help, think I've addressed all your notes :)

Thank you!


[BUG] Icons are swapped when KES is run in conjunction with subscriptions panel

Reposted from https://kbin.social/m/kbinMeta/t/183928/kbin-Enhancement-Suite-a-community-curated-script-manager-that-lets-you#entry-comment-741493
Describe the bug
A clear and concise description of what the bug is.
The visual glitch also appears if I disable the Notifications Panel and Better Page Navigation scripts, so it seems to be something in the interaction between KES and Subscriptions Panel.
If it makes a difference, I use Firefox on Windows with Tampermonkey.
KES version:

Version number 1.1.3

Desktop (please complete the following information):

OS: Windows
Browser: Firefox

Reference image:

This is most likely related to behavior of the nav-icons mod

This appears to be resolved (at least, in 1.2.0). I'm running LibreWolf though, a fork of Firefox.

There is actually a fourth icon that KSP tries to insert to the left of the three icons adjacent to your profile. Try forcing the viewport to mobile size and seeing if the "Kbin Subscriptions Panel" mobile icon appears to the left of the search icon.

Yep, it pops the subscription panel to the left of the search icon (note: this is the same functionality I had prior to updating to KES).

I was able to reproduce the original bug in Firefox (I think it should affect most browsers, as the positional index of an element was being inserted incorrectly into the page CSS, because the KSP icon is nth-of-type(1). I just wasn't able to reproduce whether it was working again, because KSP stopped functioning for me. I think this is fixed, let's wait for confirmation from @Prouvaire

Thanks @aclist - glitch has been fixed:


Push Segue Problem

i make a subclass of SLKTextViewController, called slackViewController
this is how i do:
rootViewController is a UINavigationController which its root is a ViewController, then i push to slackViewController, then in slackViewController i push again to newViewController, and then i press back so im back to slackVewController, when i tap the textInputBar the keyboard shows up bat the textInputBar does not goes up and cant even send (disabled)

i have fixed the problem, I removed the line [[NSNotificationCenter defaultCenter] removeObserver:self] from viewWillDisappear, and now it's working.


[bug]: Setup wizard doesn't accept product key when migrating from 0.2x with NO_KEY=1

Prerequisites

[X] I have searched for existing issues that already report this problem, without success.

EmbassyOS Version
0.3.0
Device
Laptop/Desktop
Device OS
MacOS
Device OS Version
10.14.6
Browser
Firefox
Browser Version
94.0.2
Current Behavior
After going straight to recovery as it should, it returns to Product Key entry

This is expected I believe, but the product key for the 0.2x build I am migrating from does not work.
Expected Behavior
That product key should work.
Steps to Reproduce
Build 0.3.0 with flag NO_KEY=1
Attempt to migrate from 0.2x
Enter product key from 0.2x
Anything else?
This might be a dupliacte of https://github.com/Start9Labs/embassy-os/issues/1040

fortunately the screenshot you sent includes enough of the error :)
in future bug reports, please copy the contents of error.details, and error.debug into the ticket.

Just tested - this works now.


Add Go 1.21 image

This adds an image with Go 1.21.3

/retest

1.21.3 was released yesterday with a security fix, let's update?

1.21.3 was released yesterday with a security fix, let's update?

done, thanks

/approve
and lgtm
/assign @tnozicka


Use Ginkgo directly in E2E tests

Currently we use kubetest in the e2e tests, however this has the drawback that it limits the config options we can pass into Ginkgo, which is the Framework that executes the actual tests.
Acceptance criteria

We use Ginkgo instead of Kubetest for the E2E tests

After discussion, we decided that kubetest is working very well for us, so there is no need to migrate to Ginkgo.
/close


Fix pdftoppm invocation for Poppler pdftoppm

pdftoppm treats any second non-flag parameter as a PPM-file-prefix, creating files starting with "-", like "--1.pgm" instead of outputting to stdout. Omitting the prefix however, outputs to stdout.
Checked on pdftoppm 0.86.1 and 21.08.0.

Ok so Poppler pdftoppm is different from the original (upstream) Xpdf pdftoppm?

To make things clear - we need a solution that works for both Xpdf and Poppler, as Xpdf requires the “-“.

Ah, i had not realized anyone was still using xpdf. That explains it (and makes this PR incorrect).
So, yes, they are different. Checked latest xpdf, and it does indeed not just support the "-", but require it.

Having given it some more thought; checking for presence of Poppler/poppler (oppler?) in pdftoppm -h is still the only way that comes to mind.
But i'd need some ++ to my C to make a solution that i'd be good enough contributing.

Please file a bug against the poppler project on this - Xpdf has used this command syntax for a very long time.
I will look at adding a configure-time check for this, but such things are notoriously unstable.

After doing some research, it seems Poppler and Xpdf have introduced the ability to output to stdout independently of, but likely inspired by, each other.
It seems Xpdf has had it from version 3.03 (2011), which is after the main Poppler forking point AFAIK.
Poppler introduced its version in 0.6.0 (2007).
But since Xpdf seems to not keep public repos it is of course not possible to know for sure who was first.
It is not in 3.02 (earlier in 2007) but also not in any of the subsequent published patches, so first published version is still in 2011 that i can see.
BTW, how are other CUPSy things not hit by this left right and center?
Most distros have switched (defaults and outright) from Xpdf years ago. (Redhat seemingly in '15, and Ububntu in '20)
Also; just to clarify, this is not something i mean to push to fulfill my own needs, i'm just trying to help give back to something i see as valuable.
If you still think it is valuable, i can definitely take the question to Poppler, but i wouldn't count on them being favorable towards it.

Added a Poppler specific invocation behind an ifdef.
TBD obviously if that is the correct name and way to do it, but the command line works well at least.
Since Poppler willl also need specific scaling options to get perfectly floored dimensions, i don't think there is a point to ask for allowing "-" as output prefix to mean stdout.

 Poppler is far from perfect, and the maintainer is indeed not much of a fan of the standalone tools it seems... But Poppler is much more actively maintained than XPDF (last release 9 months ago, and no public repo it seems). And from what i could find Linux distros switched over ages ago. I'm inclined to trust their judgement.
It's not that i'm asking that XPDF support is thrown out... just saying that it's going to be broken to most people. And for that matter i made my own tools long ago since i can accept GPL "infection"... I just think it's a shame to have the "standard" one be broken.

@attah What I mean is that Xpdf can be easily configured to only built non-desktop bits for use on a server. The same is not true of Poppler. Also, the Xpdf author provides more than just the official open source releases - it isn't a bleeding-edge public git repository but if you find a bug he will get you a fix pretty quickly and can provide licensing when the GPL becomes a problem.
Anyways, I do want to resolve this somehow because yes, many people do use Poppler and we should be compatible with both versions of pdftoppm. I'm just unwilling to remove Xpdf support because of it.

Updated with possible solution. Consider it a draft still... and please do point out any issues you see with it.

I'm not crazy about looking at the "help" output...  Also, I'm not sure that forcing width/height to the media size is the correct behavior either (might result in asymmetric scaling, need to check...)

Agreed... but compared to a define, i think it is preferable. And at least it is quite clear what it does.
Forcing dimensions will certainly produce interesting results if the input is not already the correct size.
But then again, anything that is not the correct size will fail generally. This will "just" produce bad output instead of failing in some cases.
e.g. letter document with media set to a4, or for extra spice: https://wiki.debian.org/CUPSPdfToPdf?action=AttachFile&do=view&target=mixed.pdf (which neither succeeds on)

Using -scale-to for the long axis is probably the way to go, and the code needs to crop/expand the output as needed.

OK, I opted to use the "-v" (version) output, and also updated the code to use -scale-to for Poppler's pdftoppm and to crop/expand the bitmap we get as needed.
[master 2fc9274] Update ipptransform to support both Xpdf and Poppler pdftoppm (Issue #267)


Need help.

So i have everything installed but Idk how to set the bot up please help.

Do you mean setting up a Discord Bot?

Sure, here's the steps:

Go to The Developer Pane for Discord (while you're logged in) and click on "My Apps"
Add a new app; this is your bot, name it accordingly
in the new app you just created, make sure to upgrade the bot to a "Bot User"
Copy and paste the token for the Bot User you just created into the config for my text adventure bot (make sure its in config.json not config.json.example)
Add the bot to whatever servers you want via these instructions
start your bot up with node app.js from the bot directory

And that should be all you need! Let me know if that helps or you have more questions!

well this is what I have so far lol.

Alright. Did you follow the instructions to install Node/NPM?

@TastyCookies124 are you still having issues? Can I help?


Possible fix for broken callbacks

Callbacks aren't working for me with 2.0.2.  I believe the condition I've changed was to blame.

@jamiebuilds ?

I hit this bug too. Any chance of it getting merged? Or documenting the bug somewhere?

I'm having the same problem and this commit fixed it.
@jamiebuilds Probably is a big bug, if you need some help to test it, i'll be happy to try.

Created a CodeSandbox demonstrating the issue: https://codesandbox.io/s/k9n8x5p447.
In the current release of unstated (2.0.3) setState callbacks are unusable. Given that a goal of this library (as I understand it from here: https://github.com/jamiebuilds/unstated/pull/1#discussion_r171713105) is to make it as seamless as possible to refactor component state into container state and that React's setState supports callbacks, I think this is an issue worth addressing.
What needs to happen to get this fix merged?
Thanks for all the hard work that goes into building and maintaining this!


Due to meta knowledge + 10 to all lore and knowledge checks, as well as Perception when it comes to finding traps.

These sound amazing! I'll add them in the next update.

Ultimate Computer Programmer: increase initiative by 10 and increase to damage for all weapon types. Also gives a bonus to perception and knowledge arcana and knowledge world. You are aware you are in a world that is a game and thus can exploit that knowledge to your advantage allowing you to outrun enemies, strike harder and see things that others can't. Basically Kirito exploit

maybe "beta tester" would be a more appropriate name?

Dimensional Bag as background? IMO it should stay as an OP ability, but if anything, just change its name to 'Inventory', because in isekai most character get their unlimited storage space as inventory ability rather than an infinite bag of holding.
#38

yeah i put a ❓ because i wasn't sure about it. I like the name change, makes it sound more game-like.


handheld-daemon: 1.1.0 -> 1.3.14

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for handheld-daemon is: Linux support for handheld gaming devices like the Legion Go, ROG Ally, and GPD Win
meta.homepage for handheld-daemon is: https://github.com/hhd-dev/hhd/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.3 with grep in /nix/store/rid6cgd8fm95h1bdhggdk1f7vxcc4bp8-handheld-daemon-1.3.3
found 1.3.3 in filename of file in /nix/store/rid6cgd8fm95h1bdhggdk1f7vxcc4bp8-handheld-daemon-1.3.3

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
handheld-daemon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rid6cgd8fm95h1bdhggdk1f7vxcc4bp8-handheld-daemon-1.3.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/3e193898a650453c7d201821f82c35ce2cc9672a#handheld-daemon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rid6cgd8fm95h1bdhggdk1f7vxcc4bp8-handheld-daemon-1.3.3
ls -la /nix/store/rid6cgd8fm95h1bdhggdk1f7vxcc4bp8-handheld-daemon-1.3.3/bin

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

1 package built:

handheld-daemon

Maintainer pings
cc @appsforartists for testing.

Thanks @ryantm!
There's a new env variable that still needs to be set and tested.
The latest versions of hhd also default to handling the power button, which I fear might conflict with Jovian's power button handling.  It can be disabled in ~/.config/hhd.
I'm new to Nix.  Is it possible/accepted to write a file to the user's home directory during nixpkg installation?
If so, maybe we should have a NixOS-optimized default config and write it there.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for handheld-daemon is: Linux support for handheld gaming devices like the Legion Go, ROG Ally, and GPD Win
meta.homepage for handheld-daemon is: https://github.com/hhd-dev/hhd/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.6 with grep in /nix/store/s1nhfcri8kxmagc1i6wr1ngv2cz22qi6-handheld-daemon-1.3.6
found 1.3.6 in filename of file in /nix/store/s1nhfcri8kxmagc1i6wr1ngv2cz22qi6-handheld-daemon-1.3.6

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
handheld-daemon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s1nhfcri8kxmagc1i6wr1ngv2cz22qi6-handheld-daemon-1.3.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/725ade276815a247d5ef27d9cb893b323c051c76#handheld-daemon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s1nhfcri8kxmagc1i6wr1ngv2cz22qi6-handheld-daemon-1.3.6
ls -la /nix/store/s1nhfcri8kxmagc1i6wr1ngv2cz22qi6-handheld-daemon-1.3.6/bin

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

1 package built:

handheld-daemon

Maintainer pings
cc @appsforartists for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for handheld-daemon is: Linux support for handheld gaming devices like the Legion Go, ROG Ally, and GPD Win
meta.homepage for handheld-daemon is: https://github.com/hhd-dev/hhd/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.7 with grep in /nix/store/mv5vj603f7d5355b9m2dwwm88a3w1fgp-handheld-daemon-1.3.7
found 1.3.7 in filename of file in /nix/store/mv5vj603f7d5355b9m2dwwm88a3w1fgp-handheld-daemon-1.3.7

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
handheld-daemon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mv5vj603f7d5355b9m2dwwm88a3w1fgp-handheld-daemon-1.3.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/daafcb2090fa77394a4199455f55b13b286b3793#handheld-daemon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mv5vj603f7d5355b9m2dwwm88a3w1fgp-handheld-daemon-1.3.7
ls -la /nix/store/mv5vj603f7d5355b9m2dwwm88a3w1fgp-handheld-daemon-1.3.7/bin

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

1 package built:

handheld-daemon

Maintainer pings
cc @appsforartists for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for handheld-daemon is: Linux support for handheld gaming devices like the Legion Go, ROG Ally, and GPD Win
meta.homepage for handheld-daemon is: https://github.com/hhd-dev/hhd/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.9 with grep in /nix/store/d1irkbrmfpv66aass7971kmx5zxbckvx-handheld-daemon-1.3.9
found 1.3.9 in filename of file in /nix/store/d1irkbrmfpv66aass7971kmx5zxbckvx-handheld-daemon-1.3.9

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
handheld-daemon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d1irkbrmfpv66aass7971kmx5zxbckvx-handheld-daemon-1.3.9 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/69a99d7eabccac026f6b9e0da6b783b2ad5bbf94#handheld-daemon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d1irkbrmfpv66aass7971kmx5zxbckvx-handheld-daemon-1.3.9
ls -la /nix/store/d1irkbrmfpv66aass7971kmx5zxbckvx-handheld-daemon-1.3.9/bin

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

1 package built:

handheld-daemon

Maintainer pings
cc @appsforartists for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for handheld-daemon is: Linux support for handheld gaming devices like the Legion Go, ROG Ally, and GPD Win
meta.homepage for handheld-daemon is: https://github.com/hhd-dev/hhd/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.10 with grep in /nix/store/1nbv67n8sd72pnfwiixbfiqjzdy7n474-handheld-daemon-1.3.10
found 1.3.10 in filename of file in /nix/store/1nbv67n8sd72pnfwiixbfiqjzdy7n474-handheld-daemon-1.3.10

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
handheld-daemon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1nbv67n8sd72pnfwiixbfiqjzdy7n474-handheld-daemon-1.3.10 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/cb2e6a8460af1b1ea463e08ace3630c39280be07#handheld-daemon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1nbv67n8sd72pnfwiixbfiqjzdy7n474-handheld-daemon-1.3.10
ls -la /nix/store/1nbv67n8sd72pnfwiixbfiqjzdy7n474-handheld-daemon-1.3.10/bin

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

1 package built:

handheld-daemon

Maintainer pings
cc @appsforartists for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for handheld-daemon is: Linux support for handheld gaming devices like the Legion Go, ROG Ally, and GPD Win
meta.homepage for handheld-daemon is: https://github.com/hhd-dev/hhd/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.14 with grep in /nix/store/4kyiw1sxz558vn4z5irrg2cj6bj3xgyc-handheld-daemon-1.3.14
found 1.3.14 in filename of file in /nix/store/4kyiw1sxz558vn4z5irrg2cj6bj3xgyc-handheld-daemon-1.3.14

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
handheld-daemon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4kyiw1sxz558vn4z5irrg2cj6bj3xgyc-handheld-daemon-1.3.14 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/68d1837052c121e900375134fba48b4829d7f026#handheld-daemon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4kyiw1sxz558vn4z5irrg2cj6bj3xgyc-handheld-daemon-1.3.14
ls -la /nix/store/4kyiw1sxz558vn4z5irrg2cj6bj3xgyc-handheld-daemon-1.3.14/bin

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

2 packages built:

handheld-daemon
handheld-daemon.dist

Maintainer pings
cc @appsforartists for testing.

Superceded by #303846


[1.12] Tank cannot handle any liquid

The tank, that is supposed to handle lava in order to smelt resonating ore, cannot handle any liquid.
Deep Resonance : 1.4.8.
https://image.noelshack.com/fichiers/2017/28/4/1499972958-2017-07-13-15-08-33.png
On this screenshot, the tank is set to blue. It doesn't work either for orange.
We tryed to right click with a lava bucket to fill the tank, but it doesn't work either.
When a mod has this kind of bug, it's not a release, it's a beta, or an alpha.

Well it works for me. Is the fluid conduit below it configured correctly? Did you try with other fluid transportation mechanisms?

Tryed blue and orange. Tryed with a simple Lava Bucket. Doesn't work!
How it is supposed to work?

I mean, is the fluid conduit itself configured correctly (not the tank)?

Hmm, but it is indeed not working with a bucket. That's a bug

The fluid pipe has not setting to put a liquid into a tank. Just a "Servo" to withdraw it.
Where your Tank is supposed to take liquid? Under? Over? Sides?

Nm, there is something wrong. I'll investigate.
@Elec332 can you look at this?

McJty, you said it worked for you, so during your test, how you did the lava inside the tank?

I must have tested the wrong version or something because it isn't working for me anymore either

Ok, we'll wait for a fix.

Can confirm this issue. Seems as though the block is remembering its fluid level state. I can remove the tank and look at it in my inventory it will say 6000mb or so. Then when i place it somewhere else on the ground theres no fluid in it. Then if i place a newly crafted tank in the same location under the smelter it then appears as if it has the same amount of lava the previous tank had in it. So thats not allowing more to be piped in im guessing. Same issue occurs with the tanks that have liquid crystal in it. I remove the block, it says theres fluid in it, place down it on ground, no fluid. Then place a new tank where it was above the smelter and i see the fluid but now it doesnt register the percentages of the fluid. I hope this helps track down the issues. Thanks for all your hard work.

I too have this problem, in AllTheMods/ATM-3 as Darkere has referenced.
The mod is almost completely unusable in multiplayer because tanks will randomly "break." "Break" as in refuse to accept/transfer any liquids and will not interact with its fellow deep resonance machines, smelter, crystalizer, etc, or other mods. Breaking and replacing "broken" tanks will not fix the issue. The only way to fix this "break" is to simply reload the server, easy in single player, but you see how it becomes troublesome when trying to play with friends, which in my case is through LAN.
I'm having trouble replicating this error because I am cannot seem to figure out what triggers the tanks to "break." One thing I am positive about, at least to an extent since I tested it in a single player world, is that newly placed tanks automatically "break" upon placement and require the restart.
Finally there seems to be a similar error effecting both the smelter and valve, simply breaking them and replacing them will fix it though.
Here is my personal experience: I'm playing on a LAN server my friend is hosting. Last night my crystal factory's crystalizer, the factory you helped me build with your guide, seemed to be broken so I just said "f*** it* and quit. Today I rejoined, and voila, the crystalizer that wasn't crystalizing before had gone from 20% to about 70% while I was gone. But then I noticed it wasn't working AGAIN, because there was still RCL in the tank. Eventually I realized today's error was because of the previously mentioned tank "break." I am sadly clueless about last night's though.

We are investigating this bug. Hopefully it will get resolved soon

We can use the mod if we place the tank on the ground, restart the server and don't move the tank after.

I have a similar bug to this, but its kind of weird, I'll try to explain.
I put a tank on the floor and grab a bucket of lava. So I put in the lava in the tank. All good, then I break the tank (dispose that tank an grab a new one from creative tab) and put 3 tanks using the same location as the tank from before and it seems to remember how much of the lava was in the previous tank.
Same with smelted material, these tanks behave really weird.

UPDATE: Keeping the chunks loaded seemed to fixed the tank from randomly breaking. LAN world reopened and upon joining tanks were in perfect working order, BUT smelter, valve, AND crystalizer stopped working, forcing me to break and replace them to get them to work again. Luckily my crystalizer was at 0%, but this glitch could have serious consequences.

Please update to latest ElecCore


无法打开“vs_code_welcome_page”

Issue Type: Bug
无法打开“vs_code_welcome_page”: Unable to resolve resource walkThrough:/e%3A/VS%20Code/resources/app/out/vs/workbench/contrib/welcome/page/browser/vs_code_welcome_page?%7B%22moduleId%22%3A%22vs%2Fworkbench%2Fcontrib%2Fwelcome%2Fpage%2Fbrowser%2Fvs_code_welcome_page%22%7D。
VS Code version: Code 1.57.1 (507ce72a4466fbb27b715c3722558bb15afa9f48, 2021-06-17T13:28:07.755Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No

Thanks for reporting, do you have editorAssociations: {'*': 'default'} set anywhere in your settings by chance?


Missing task texts in the task settings

Expected behavior:
All task text (see "text" in: themetasks.js) appear automatically in the text field of the task settings.
Actual behavior:
This does not work for task texts of task types with different answer types.

Done.


DBContext wrapping and GetContextFromConstantExpression

Hello. I have my own Repository/UnitOfWork mechanism which uses different DB types (mysql, mssql).
In this case custom UnitOfWork looks like this:
public class ItemInBaseChild
{
    public int Id {get; set;}
    public int IdParent1 {get;set;}
    public int IdParent2 {get;set;}
}

public class ItemInBaseParent
{
    public int Id {get; set;}
}

public class UnitOfWorkBase
{
   ...some initialization code...
   public DBContext Context {get;set;}
   public DBSet<ItemInBase> ItemsChilds { get { return Context.Set<ItemInBaseChild>(); } }
   public DBSet<ItemInBase> ItemsParents { get { return Context.Set<ItemInBaseParent>(); } }
}

So, it works nice but one moment is broken.
When i try to use query like this
var uof = new UnitOfWorkBase();
var list = from child  in uof.ItemsChild
               from parent in uof.ItemsParents.Where(x => x.Id == child.IdParent1 || x.Id == child.IdParent2)
               select new {child, parent};

i have an error like "only primitive types are supported in this context". The reason of this is that query builder failes to convert "from parent in uof.ItemsParents.Where(" in DbQueryVisitor.VisitMethodCall/DbQueryVisitor.VisitMember. You can see this code in the screenshot. "node.Member.DeclaringType" is UnitOfWorkBase, not DBContext.
Is there any hack or any way to solve this problem?

One way is to change EF sources then use compiled binaries, but this way needs to create my own public key (otherwise i have an error "Strong name validation failed").
But some NuGet packages (Hangfire, for example) use EF and they are need to use public key b77a5c561934e089.

Problem was solved by creating own copy of DBQueryProvider and DBQueryVisitor and replacing EF DBQueryProvider with custom in runtime.


Composable event sourcing

This is a design exploration of composability / orchestration patterns.
Resources as context

"COMPOSABLE EVENT SOURCING WITH MONADS"
http://www.lambdadays.org/static/upload/media/1519724460390566danielkrzywickieventsourcing.pdf

https://stackoverflow.com/questions/51160457/event-sourcing-without-cqrs

https://microservices.io/patterns/data/saga.html

"The Application of Petri Nets to Workflow Management"
http://wwwis.win.tue.nl/~wvdaalst/publications/p53.pdf

"State-based instead of event-based In contrast with many other process modeling techniques, the state of case can be modeled explicitly in a Petri net.  Today’s workflow management systems are typically event-based, i.e., tasks
are modeled explicitly and states between subsequent tasks are suppressed. The distinction between an event-based and a state-based description seems to be very subtle, but examples in this paper (e.g. Figure 16) show that this is of the utmost importance for workflow modeling. For example, in most
workflow management systems which abstract from states it is not possible to use the implicit OR-split."

Questions.

Are event sourcing and CQRS welded together in Aecor or can they be used separately?

Can Aecor be used to implement all use cases from "COMPOSABLE EVENT SOURCING WITH MONADS"  ? (please skim through presentation to offer an initial assessment if any show stoppers exist before going deeper to prove)

How to implement ~checkpointing~ rolling snapshots with Aecor (could be thought of related to composability). (see https://cqrs.files.wordpress.com/2010/11/cqrs_documents.pdf for definition)

In the banking app example the assumption of all account transactions being held in memory is not realistic. Thinking that if in a real implementation the transactions would be stored in another persistent repository and the aggregate would keep the transactions not yet checkpointed.  If so, then these methods would need to be implemented differently https://github.com/notxcain/aecor/blob/be6b979f322f7268e62ca9b9b88428cfc2cf420f/modules/example/src/main/scala/aecor/example/account/EventsourcedAlgebra.scala#L42-L46.
If this line of thinking is agreeable with you then please share some thoughts on techniques to achieve this. Maybe to suspend the ~ rolling snapshots in a separate effect ?
update 2018/01/06 : Found "Scaling Event-Sourcing at Jet" very useful.
I have a number of real applications with non trivial such business logic it seems it would be warranted to encapsulate in separate effects (could use the other effects like Sync and MoandError for example).
Disclaimer: I know this is rough, sorry, and still working through how composition / orchestration is done in https://github.com/vpavkin/ticket-booking-aecor/blob/master/booking/src/main/scala/ru/pavkin/booking/ProcessWirings.scala (seems CQRS based).

@SemanticBeeng Since you reference my example, I'll try to address some questions of yours.

Are event sourcing and CQRS welded together in Aecor or can they be used separately?

For sure you can use them separately. As I show in Part 3 of the series, you can launch an eventsourced behavior without any read side. In theory, you can even read the whole state from the same aggregate, although such solution is much harder to scale properly.
Actually there's not a lot Aecor has to offer in terms of CQRS. You can just get a partitioned stream of entity events. That's it, then you do whatever you want with it.

still working through how composition / orchestration is done

Could you please elaborate on what you mean here by orchestration? There are several processes here, which are all different. More specific questions about a specific process would be much easier to answer.
Anyway, Aecor itself does NO orchestration whatsoever. The only remotely related thing it does is it distributes processing over the cluster (and only when it's possible - it requires event stream to be properly partitioned).
Overall, the way processes are defined in my example is inspired by Process Manager pattern, which is much more on choreography side, rather than orchestration.
I plan to dedicate Part 5 of the series to this matter, maybe it will clarify some questions as well :)

"behaviors belong to the domain layer and runtime is out there in the infrastructure layer"

Key design choice indeed.

"what you mean here by orchestration?"
As per https://stackoverflow.com/a/29808740/4032515
"Orchestration employs a centralized approach for service composition."
"Choreography employs a decentralized approach for service composition."

Above mean to focus on composition with functional programming - at a programming model level and less at an architectural level.
Will follow up and improve this answer.

@SemanticBeeng is there anything I can help with?

Can Aecor be used to implement all use cases from "COMPOSABLE EVENT SOURCING WITH MONADS" ? (please skim through presentation to offer an initial assessment if any show stoppers exist before going deeper to prove)

Sure, MonadActionReject is all you need for that.

I think the gist of my pursuit at that time was to see how to write event sourcing based logic without being forced to side effect the events as with persistent actor based implementations.
Since asking this have learned more about Aecor and believe I understand better.
Still, it would be great if you could sketch the functionality of the example from this article in an Aecor when you can afford a couple of hours. :-)


Provide feature info

Please provide some information about which Defender for Endpoint features are actually available for MacOS

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

ID: 82e9b530-4f11-0483-ed65-42b23082f9f6
Version Independent ID: 38263c08-7cab-7d52-552d-e724ede401aa
Content: Microsoft Defender for Endpoint for Mac
Content Source: microsoft-365/security/defender-endpoint/microsoft-defender-endpoint-mac.md
Product: m365-security
Technology: mde
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@Dansimp Please help in resolving this issue. Thanks.

At this point - out of scope.


Spevacus: Watch hendrickwellnesscenter.com

Spevacus requests the watch of the watch_keyword hendrickwellnesscenter\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

hendrickwellnesscenter\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Daniil in Charcoal Test


bug: Disabling dynamic injection causes an error when opening a test file

Did you check existing issues?

[X] I have read all the tree-sitter docs if it relates to using the parser
[X] I have searched the existing issues of tree-sitter-PARSER_NAME

Tree-Sitter CLI Version, if relevant (output of tree-sitter --version)
No response
Describe the bug
After setting vim.g.tstest_dynamic_injection = false, an error indicating that a handler forset-lnaguage-from-grammar! doesn't exist.
Traceback

Steps To Reproduce/Bad Parse Tree

Install the plugin
Set vim.g.tstest_dynamic_injection = false
Open a test/corpus/*.txt file

Expected Behavior/Parse Tree
There shouldn't be any error and no grammar should be injected in the input region of each test.
It seems that the directive is not registered if vim.g.tstest_dynamic_injection is false, which causes the error because one injection query uses it.
https://github.com/tree-sitter-grammars/tree-sitter-test/blob/4a27fc54b88a58ea384ddfcf466d64cfef261ef3/plugin/tstest.lua#L42-L44
Repro
No response

Why are you setting that variable?