error:25066067:DSO support routines:dlfcn_load:could not load the shared library

Environment

Operating System version: Ubuntu 21.4
Firebase SDK version<EMAIL_ADDRESS>Firebase Product: admin.auth
Node.js version: 16.15
NPM version: 7.12.1
Yarn version: 1.12.19 (i use yarn)

The problem
import admin from 'firebase-admin'
admin.auth().createCustomToken(stringID, {
    id: stringID,
}) // throws the error below

 Error: error:25066067:DSO support routines:dlfcn_load:could not load the shared library
    at Sign.sign (node:internal/crypto/sig:131:29)
    at ServiceAccountSigner.sign (/node_modules/firebase-admin/lib/utils/crypto-signer.js:65:37)
    at /node_modules/firebase-admin/lib/auth/token-generator.js:135:44
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    // removed unimportant error lines from my own code
  opensslErrorStack: [
    'error:0E076071:configuration file routines:module_run:unknown module name',
    'error:0E07506E:configuration file routines:module_load_dso:error loading dso',
    'error:25070067:DSO support routines:DSO_load:could not load the shared library'
  ],
  library: 'DSO support routines',
  function: 'dlfcn_load',
  reason: 'could not load the shared library',
  code: 'ERR_OSSL_DSO_COULD_NOT_LOAD_THE_SHARED_LIBRARY'
}

Steps to reproduce:
Unfornutately I cannot find a way to reproduce this issue accross platforms. I ran it in a different system, even with the same lock file, i cannot reproduce it. I do think that the problem is tied to my own system. I just dont know where to look.

The same issue with me
Operating System version: Ubuntu 22.04
Firebase SDK version<EMAIL_ADDRESS>Firebase Product: admin.auth
Node.js version: 10.24.1
NPM version: 6.14.12

I think the issue is related to the internal nodejs crypto package on the new Ubuntu 22.04 LTS version.
so we need to open a bug ticket there to check, also I doubt it is the OpenSSL new version issue which was installed by default on Ubuntu 22.04 LTS. so yeah it is not firebase-admin issue

Hi Guys,
I found a workaround while facing this issue using firebase-admin.
Hence, we suggest you to comment out the lines providers = provider_sectin the file/etc/ssl/openssl.cnf` and restart application once.
I took it off https://help.zoho.com/portal/en/community/topic/cant-install-zoho-workdrive-app-in-ubuntu-22-04

@k0d3d thanks a lot! This does seem to work for me on my machine.

Thanks a lot! it works on my machine :') @k0d3d
for anyone who find the cnf file,
You can run the following command to get the location of openssl.cnf file:
openssl version -d
On my computer, the result is:
OPENSSLDIR: "/private/etc/ssl"
Finally, the path of openssl.cnf file:
/private/etc/ssl/openssl.cnf
source: https://stackoverflow.com/questions/21477210/correct-location-of-openssl-cnf-file

Thanks a lot for the workaround @k0d3d
It worked on my machine as well (fresh linux mint 21 / cinnamon install - ubuntu based)

Can anyone explain why did this happened?


Support for blackbox membership inference attack without true labels

Description
Support for blackbox membership inference attack without true labels. If not supplied, the attack is based only on model predictions.
This is not supported for 'loss' mode.
Fixes # (2154)
Type of change
Please check all relevant options.

[X] Improvement (non-breaking)
[ ] Bug fix (non-breaking)
[ ] New feature (non-breaking)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Testing
Created new tests for the feature.
Test Configuration:

OS: MacOS 12.6.8
Python version: 3.9
ART version or commit number
TensorFlow / Keras / PyTorch / MXNet version

Checklist

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[ ] My changes have been tested using both CPU and GPU devices

Codecov Report

Merging #2293 (a5087db) into dev_1.17.0 (c048a5c) will decrease coverage by 56.01%.
The diff coverage is 0.70%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

@@               Coverage Diff               @@
##           dev_1.17.0    #2293       +/-   ##
===============================================
- Coverage       85.94%   29.93%   -56.01%
===============================================
  Files             318      318
  Lines           28716    28789       +73
  Branches         5260     5279       +19
===============================================
- Hits            24679     8619    -16060
- Misses           2718    19859    +17141
+ Partials         1319      311     -1008

Files Changed
Coverage Δ

...ttacks/inference/membership_inference/black_box.py
8.47% <0.70%> (-83.87%)
:arrow_down:

... and 240 files with indirect coverage changes


[Bug] First Filter Appears and Won't Go Away When Selecting Any Other Filter

Bug report
What I did
I added the following filters to my Crud Controller within the setup() method.
$this->crud->addFilter([
            'name'  => 'invite_state',
            'type'  => 'dropdown',
            'label' => 'State'
        ], [
            0 => 'Invite Sent',
            1 => 'Accepted Terms',
            2 => 'Payment Provided',
            3 => 'Approved',
        ], function ($value) { // if the filter is active
            $this->crud->addClause('where', 'invite_state', $value);
        });

        $this->crud->addFilter(
            [
                'name'  => 'event_description',
                'type'  => 'select2',
                'label' => 'Event Code'
            ],
            function () {
                return \App\Models\HTOEvent::select('code', 'id')
                    ->whereExists(function ($query) {
                        $query->select(DB::raw(1))->from('hto_event_sponsors')->whereRaw('hto_event_id = hto_events.id');
                    })
                    ->get()->pluck('code', 'id')->toArray();
            },
            function ($value) {
                $this->crud->addClause('where', 'hto_event_id', $value);
            }
        );

        $this->crud->addFilter(
            [
                'name'  => 'account_description',
                'type'  => 'select2',
                'label' => 'Account'
            ],
            function () {
                return \App\Models\HTOAccount::select('company', 'id')
                    ->whereExists(function ($query) {
                        $query->select(DB::raw(1))->from('hto_event_sponsors')->whereRaw('hto_account_id = hto_accounts.id');
                    })
                    ->get()->pluck('company', 'id')->toArray();
            },
            function ($value) {
                $this->crud->addClause('where', 'hto_account_id', $value);
            }
        );

What I expected to happen
I expect to be able to use any of the filters without unwanted issues.
What happened
In this case if I select an option for the Event Code or the Account filter after I do so the State filters drop down list will show up. Once this happens I can not get the States drop down list to disappear without refreshing the page. Even if I clear the filters or select a State filter it will not go away.
What I've already tried to fix it
I've updated to the latest backpack version.
I've removed the State filter to see if this problem then happens with the Event Code filter. It does. So it is not specific to a filter it's just the fact that there are multiple filters on this page.
Backpack, Laravel, PHP, DB version
PHP VERSION:
PHP 7.3.15-3+ubuntu18.04.1+deb.sury.org+1 (cli) (built: Feb 23 2020 07:23:33) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.15, Copyright (c) 1998-2018 Zend Technologies
with Xdebug v2.9.8, Copyright (c) 2002-2020, by Derick Rethans
with Zend OPcache v7.3.15-3+ubuntu18.04.1+deb.sury.org+1, Copyright (c) 1999-2018, by Zend Technologies
LARAVEL VERSION:
v7.30.4@9dd38140dc2924daa1a020a3d7a45f9ceff03df3
BACKPACK VERSION:
4.1.42@9338f9711a393f82ecb09d68c0756bf24c56eafe

FYI. Just in case it's not apparent there are no javascript errors being thrown. Also, this is a non-starter for production use for me. I can't release this and expect users to refresh the page constantly.

@tabacitu This is a pretty significant bug if that is the case as it basically renders the ability to use multiple filters invalid. Is there any way this can be escalated?

I am on it @selected-pixel-jameson !

@pxpm Thank you sir! Appreciate it.

@selected-pixel-jameson sorry, didn't mean to look dismissive by assigning someone else - I didn't answer because I could not replicate the issue, filters seemed to work fine for me: the dropdown filter did not show up out of the blue, and when selecting a different filter it closed properly. Tried with select2 as the "trigger" an all other filters - everything seemed to behave as expected to me.
I tested in our online demo, for Monsters. Does the same thing happen to you there? If so... do you have any custom JS onpage?
Cheers!

@selected-pixel-jameson I am gonna need your help here.
This are my filters:
$this->crud->addFilter([
            'name'  => 'invite_state',
            'type'  => 'dropdown',
            'label' => 'State'
        ], [
            0 => 'Invite Sent',
            1 => 'Accepted Terms',
            2 => 'Payment Provided',
            3 => 'Approved',
        ], function ($value) { // if the filter is active
            $this->crud->addClause('where', 'select_from_array', $value);
        });

        $this->crud->addFilter([ // select2 filter
            'name' => 'select2',
            'type' => 'select2',
            'label'=> 'Select2',
        ], function () {
            return \Backpack\NewsCRUD\app\Models\Category::all()->keyBy('id')->pluck('name', 'id')->toArray();
        }, function ($value) { // if the filter is active
            $this->crud->addClause('where', 'select2', $value);
        });

https://recordit.co/ao77b7BSjW
I tried adding in setupListOperation and in setup.
Are you customizing filter files, or do you added any custom JS to that page ? What browser are you using ? I tested with Chrome v89.
Thanks for your patiente, we will figure this out!
Best,
Pedro

@tabacitu No problem at all.
@pxpm Ok. So this did shed some light on the possible issue.
I looked into the app.js file that we have setup for this project. This is what we use to inject our own JS and VueJS components.
I found this.
// We need to figure out why these aren't getting initialized by default.
$('.dropdown-toggle').dropdown()

$('.dropdown').dropdown()

If I take this code out the dropdown's no longer work at all. So I'm assuming this is the actual root of the problem. Do you have any insight into what might be preventing that code from getting initialized correctly?

Ok. Problem solved!
For some reason.
require('./bootstrap')
Was in our app.js file. I'm not sure why as this was implemented by a different developer, but removing it seems to fix all of our problems.
Not sure what it will break, but I'm assuming all that JS is loaded in a different spot anyway.

@selected-pixel-jameson not 100% sure, but probably bootstrap is beeing overriden by your functions ?
What I meant is, Backpack loads bootstrap (css and js), and I think inside bootstrap.js they already do those initializations, that's why in code we work only with classes and data-attributes.
The problem might be in the order they are loaded ? BS vs app.js ?
Maybe conflicting versions of BS ?
Not sure about the problem, but happy that you figured out, you usually bring us tricky problems, when I was unable to reproduce my legs started shaking 😄 😄
I am going to close this, but you know the deal, if you need help, ask, we try our best 👍
Thanks,
Pedro

@pxpm As always really appreciate your help. It's very apparent that you care about your platform and are passionate about it. Thank you!

Just to expand on this further in case someone else runs across a similar issue.
Within the app.js file in our application we have this.
/**
 * First we will load all of this project's JavaScript dependencies which
 * includes Vue and other libraries. It is a great starting point when
 * building robust, powerful web applications using Vue and Laravel.
 */

require('./bootstrap')
...

The bootstrap file contains this code.
window._ = require('lodash')

/**
 * We'll load jQuery and the Bootstrap jQuery plugin which provides support
 * for JavaScript based Bootstrap features such as modals and tabs. This
 * code may be modified to fit the specific needs of your application.
 */

try {
  window.Popper = require('popper.js').default
  window.$ = window.jQuery = require('jquery')

  require('bootstrap')
} catch (e) {}

/**
 * We'll load the axios HTTP library which allows us to easily issue requests
 * to our Laravel back-end. This library automatically handles sending the
 * CSRF token as a header based on the value of the "XSRF" token cookie.
 */

window.axios = require('axios')

window.axios.defaults.headers.common['X-Requested-With'] = 'XMLHttpRequest'

/**
 * Echo exposes an expressive API for subscribing to channels and listening
 * for events that are broadcast by Laravel. Echo and event broadcasting
 * allows your team to easily build robust real-time web applications.
 */

// import Echo from 'laravel-echo';

// window.Pusher = require('pusher-js');

// window.Echo = new Echo({
//     broadcaster: 'pusher',
//     key: process.env.MIX_PUSHER_APP_KEY,
//     cluster: process.env.MIX_PUSHER_APP_CLUSTER,
//     forceTLS: true
// });

If I remove the boostrap code entirely we run into issues with our VueJS components.
However, if I remove
  window.$ = window.jQuery = require('jquery')
  require('bootstrap')

Everything seems to be running appropriately.

@pxpm Thanks for the heads up. We are only using this app as an admin. There is no front-end so we are all good there.


[x86/Linux] Stack corruption pinvoke/string marshaling

I'm trying to run Hello World application on x86 (cross build on x64) but ILC compiler failed on jitStartup().
First  it goes to new JitHost:
#0  JitHost::getIntConfigValue (this=0x81435b0,
    name=0xeef845d6 L"\x6c0041\x4a0074\x740069\x69004c\x69006dt\x6c0041\x4a0074\x740069\x6b0053\x700069\x6e004f\x730041\x650073\x740072\x420000\x650072\x6b0061\x6e004f\x750044\x70006d\x6f0054\x65006bn\x650044\x750062\x420067\x650072\x6b0061\x6e004f\x650056\x690072\x690066\x610063\x690074\x6e006f\x610046\x6c0069\x720075e\x69004a\x440074\x660069\x610066\x6c0062\x440065\x730061m\x69004a\x4c0074\x6f006f\x480070\x69006f\x740073\x740053\x740061s\x69004a\x4c0074\x720073\x530061\x610074\x730074\x440000\x6d0075\x4a0070\x740069\x650074\x4d0064\x740065\x6f0068\x730064\x4a0000\x740069\x6e0045\x620061\x65006c\x430050\x650052\x41006c\x640064r\x6e0049\x650074\x700072\x650072\x650074\x460072\x6c0061\x62006c\x630061k\x69004a\x410074\x730073\x720065\x4f0074\x4d006e\x780061\x410052\x610050\x730073\x730065\x4a0000\x740069\x720042\x610065\x45006b\x69006d\x4f0074\x740075\x750070\x490074\x73006e\x720074\x4a0000\x740069\x720042\x610065\x4d006b\x72006f\x680070\x720054\x650065\x4a0000\x740069\x720042\x610065\x4f006b\x42006e\x640061\x6f0043\x650064\x4a0000\x540049\x720042\x610065\x4f006b\x4d006e\x6e0069\x70004f\x730074\x4a0000\x740069\x720042\x610065\x4f006b\x55006e\x73006e\x660061\x430065\x64006fe\x69004a\x430074\x6e0061\x730055\x530065\x450053\062\x69004a\x430074\x6f006c\x65006e\x6f004c\x70006fs\x69004a\x440074\x620065\x670075\x6f004c\x4c0067\x6f006f\x430070\x6f006c\x69006e\x67006e\x4a0000\x740069\x650044\x610066\x6c0075\x460074\x6c0069l\x69004a\x440074\x720069\x630065\x410074\x6c006c\x63006f\x4a0000\x740069\x6f0044\x620075\x65006c\x6c0041\x670069"..., defaultValue=0) at /home/alexander/src/corert/src/Native/jitinterface/jithost.cpp:61
#1  0xeec1472f in JitConfigValues::initialize (this=0xef09df98 <JitConfig>, host=0x81435b0) at /home/alexander/src/coreclr/src/jit/jitconfigvalues.h:14
#2  0xeeaf915b in jitStartup (jitHost=0x81435b0) at /home/alexander/src/coreclr/src/jit/ee_il_dll.cpp:87
...

JitHost::getIntConfigValue() execute JitConfigProvider::GetIntConfigValue() from corert/src/JitInterface/src/JitConfigProvider.cs which returns value successfully. After that JitHost::getIntConfigValue() crash on return statement. If I remove C# code invocation it work for next managed code invocation.
So it looks the stack is being corrupted after switching unmanaged/managed.
@jkotas do you know what code should be implemented for this logic?
cc @Dmitri-Botcharnikov @sergign60 @BredPet @am11

This looks like stdcall/cdecl calling convention confusion. I have submitted #4700 to use the default calling convention in all places. Give it a try and let me know whether it helps.

@jkotas unfortunately it failed on the same place.

@alpencolt I have pushed one more fix. If it still does not work, it needs to be debugged by looking at disassembly.

@jkotas it still the same.
I've debugged on disassembly and it goes to coreclr/src/vm/dllimportcallback.cpp, coreclr/src/pal/inc/pal.h and TheUMEntryPrestub () atcoreclr/src/vm/i386/umthunkstub.S.
Does it correct control flow?

Yes, it is correct control flow.

On latest master (d312715287eddf3d7f75e0fd7815beef6981000f) ILC started to fail on assert(opts.compCanUseSSE2); in coreclr/src/jit/compiler.cpp:2760.
jitStartup() works well.

ILC started to fail on assert(opts.compCanUseSSE2);

If it saves you some time looking, this should be fixable by setting JIT_FLAG_USE_SSE2 in getJitFlags method in CorInfoImpl.cs. We might want to only set it if the target is x86.

@MichalStrehovsky  thank you!
I've been looking for proper place where it should be set. I'll prepare PR for x86 later.


Clone directions for compatibility code in chiselCloneType

Does anyone know why this code doesn't clone directions for compatibility code?
@ducky64 @sdtwigg @ucbjrl

This was actually fixed by https://github.com/freechipsproject/chisel3/pull/617


Confusion on where self.key is coming in Authenticate the Client section

We're seeing users confused where the "self" properties are coming from in this section:
form_recognizer_client = FormRecognizerClient(endpoint=self.endpoint, credential=AzureKeyCredential(self.key))

form_training_client = FormTrainingClient(self.endpoint, AzureKeyCredential(self.key))

It's unclear in the quickstart that these variables were set as class variables:
endpoint = os.environ["FORM_RECOGNIZER_ENDPOINT"]
key = os.environ["FORM_RECOGNIZER_KEY"]

I'd suggest removing self and/or adding the above as part of that section like this:
endpoint = os.environ["FORM_RECOGNIZER_ENDPOINT"]
key = os.environ["FORM_RECOGNIZER_KEY"]

form_recognizer_client = FormRecognizerClient(endpoint=endpoint, credential=AzureKeyCredential(key))

form_training_client = FormTrainingClient(endpoint, AzureKeyCredential(key))

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

ID: 1e3de1b4-a118-efae-0e72-7953c8e891b3
Version Independent ID: 5ad38c9e-c775-8dbc-16ff-705a40b580e1
Content: Quickstart: Form Recognizer client library - Azure Cognitive Services
Content Source: articles/cognitive-services/form-recognizer/quickstarts/client-library.md
Service: cognitive-services
Sub-service: forms-recognizer
GitHub Login: @PatrickFarley
Microsoft Alias: pafarley

@kristapratico we will review your feedback and get back to you shortly. Thanks.

@PatrickFarley please review above feedback for doc enhancement. Thanks.

@kristapratico Has this affected more than one user? I'd thought the "self" construct was common enough in Python

I think the issue is that if a user just does copy/paste of the example, these properties aren't being defined in a class in the example so the user will need to delete the "self" from where the clients are being created. In this case, it adds inconvenience and also may confuse users like we saw so it seems worth it to remove. What do you think?

I've removed the self construct. I don't know why it was in the sample code to begin with, but the devs have removed it from there as well
#please-close


Page rendering is incorrect when changing the scrolling direction.

Describe the bug
Page rendering is incorrect when changing the scrolling direction
To Reproduce
Steps to reproduce the behavior:

Init example with ~10 elements
Begin scrolling to the right, and when you reach the fourth or fifth element, attempt to scroll to the left.

Expected behavior
You should see the previous element, but the carousel renders the same one.
Screenshots
https://github.com/dohooo/react-native-reanimated-carousel/assets/6501334/6394f9f0-3c23-44db-ba73-eeb3c548eed9
Versions (please complete the following information):

react: v18.2.0
react-native: v0.73.1
react-native-reanimated: v3.6.1
react-native-reanimated-carousel: v4.0.0-alpha.10
react-native-gesture-handler: 2.10.0

Smartphone (please complete the following information):

Device: iPhone11
OS: IOS 17.4
Browser
Version

Additional context
My review indicates that Reanimated's useSharedValue doesn't update the value immediately (scrollEndTranslation).
https://github.com/dohooo/react-native-reanimated-carousel/blob/d78784808f1a4d233708561354ca198122cfbb62/src/components/ScrollViewGesture.tsx#L342-L355
Consequently, we encounter an incorrect (previous) value in the endWithSpring function, which triggers the incorrect direction.
https://github.com/dohooo/react-native-reanimated-carousel/blob/d78784808f1a4d233708561354ca198122cfbb62/src/components/ScrollViewGesture.tsx#L138-L142

Probably the same issue as described in #535

Creating a patch with the changes @nmassey created here: https://github.com/dohooo/react-native-reanimated-carousel/pull/574 fixed this bug for me on ^4.0.0-alpha.10

I'm experiencing this in alpha.6 and above, for me it look like alpha.5 doesn't exhibit this.

Solved in https://github.com/dohooo/react-native-reanimated-carousel/releases/tag/v4.0.0-alpha.12


Allow creation of service connectors at application level

Is your feature request related to a problem? Please describe.
We are currently using service bindings to connect our apps to a cosmosdb database.
Service bindings are created at the application level. I mean, you don't need a deployment to create a service binding.
The advantage of this approach is that you can delete and create new deployments, they will automatically have the properties given by the service binding (spring.data.mongodb.uri in my case).
With service connectors, you need to have an existing deployment, to create the connector, as the attribute --deployment <deploymentname> is mandatory (https://learn.microsoft.com/en-us/cli/azure/spring/connection/create?view=azure-cli-latest#az-spring-connection-create-cosmos-mongo)
This involve that the first time you create your deployment, your app start will fail as the database connection string is not available before you create the service connector in a second time.
It's not such a big deal until you begin to do blue/green deployment and delete the Staging deployment, because when you delete a deployment, the service connector attached to this deployment is also deleted.
My actual deployment workflow is the following:

I find the name of my Production deployment (lets say blue)
I create a second deployment (lets say green) with my jar file and all the required configurations
When my app on Staging deployment has successfully started, I switch this deployment (green) to Production
And after the switch occurs, I delete the old Production deployment (blue)

With service connectors, this workflow won't work anymore. The working one will be :

I find the name of my Production deployment (lets say blue)
I create a second deployment (lets say green) with my jar file and all the required configurations
App will fail to start because of missing connection string
Create the service connector on the Staging deployment (green)
When my app on Staging deployment has successfully started, I switch this deployment (green) to Production
And after the switch occurs, I delete the old Production deployment (blue)

This is impactfull because:

I will have to wait for the app to start twice (the first time before the service connector creation where it will fail, and the second time before the switch)
Service connector creation is long, and we need to create one each time we do a new app deployment
As apps will fail the first time, this will pollute our logs with errors

Describe the solution you'd like
Allow creation of services connectors at the app level as it is for service bindings.
Or at least, do not delete the service connector attached to a deployment when this deployment is deleted, so that when we will recreate the deployment with the same name, the service connector is already there.
Describe alternatives you've considered
One solution would be to not delete our deployments after the switch, but to stop it instead.
By doing that, we keep the deployment AND the service connector until the next time we deploy a new app version.
We can deploy a new app version on a stopped deployment without restarting it at first.
After the new version is deployed, we can restart the deployment and the service connector will already be there.

Hi @julienbourgoin-maif, thanks for raising this issue. There're some differences of the design between service bindings and service connector, one of which is that the connections are part of the deployment properties rather than the app properties. And this leads to some changes in the usage.
For better understanding of your scenario, could you please describe more details for:

What's the frequency of this workflow? Is it part of CD workflow or occasional manual deployment?
As you mentioned "have to wait for the app to start twice". Is the impact from the launch time cost?

Hello @LGDoor,
Thank for your response.

What's the frequency of this workflow? Is it part of CD workflow or occasional manual deployment?

Every time we construct a new version of one of our microservices, we can choose to deploy it at the end of the build.
We can have dozens of deployments per day.
We also have every night some automated jobs which can make refresh of our dev environnements and means install many apps.

As you mentioned "have to wait for the app to start twice". Is the impact from the launch time cost?

Yes, as we are still on the workflow where we delete the staging deployment after the switch, we will need to recreate a new deployment with a new service connector each time we want to deploy a new app version.
As I explained : because we have to create the deployment (with our jar file which need database connection infos) before the service connector, the app will first start without the connection string and username/password, and then fail.
We will have to wait for the deployment to be created (the app may take 1 or 2 minutes to start and fail) and then, create the service connector (around 40 sec if you use username/password, more if you use passwordless connection)
So we may loose up to 4/5 minutes for an app deployment, in addition to the normal time to deploy a new app version, which may be avoided if the service connector was already present when creating a new staging deployment (as it is for the service bindings).
The result of this is:

the failing app will pollute my application logs with useless errors (startup errors because there is no database connection info available)
the time to deploy a new version is very long

We are thinking to move to a new workflow where we don't delete the old version deployment after the new version app as started, but stopping it instead.
And then, the next time I wan't to deploy a new app version, the stopped deployment will still be there, and will still have his service connector (we can deploy apps on a stopped deployment). Once the new app version is deployed on the stopped deployment, we can restart it and all should work as the service connector is still there, then we switch this deployement to production and stop the old production one.

@julienbourgoin-maif Glad to see you're unblocked with the workaround. Thanks for sharing such valuable information with us. Your explanation of this scenario is extremely helpful!
To resolve this issue, we are still conducting some internal discussions for the possibilities of introducing some new design. If any progress, I'll update it here.

Hi @LGDoor, any updates on this?

 What would you use for different deployment?
As deployment is the smallest runtime unit. While adding service connector at deployment level, it is not hard to create same service connector across different deployment. But if the service connector is added at app level, it is impossible to connect different target in different deployment (for example, connect to staging DB at staging deployment)

Hello @ChenTanyi
What about to let the possibility for the user to choose between app level or deployment level ?
In case the service connector is created at app level, you can't create another one at deployment level and vice versa.
The use of a staging DB is usefull if you don't switch your deployments from staging to production.
In our case, we are doing blue / green deployments and we are switching between each others, so we can't use a staging DB.

@julienbourgoin-maif
Yeah, it may be the most likely solution, but it would also introduce confusion when customers see creation failure in the other level. Therefore, we just want to know more scenarios to see if the app level is much better than deployment level at most case (or even Spring Service level).
Usually, if you all treat different deployments of App as multiple revisions rather than multiple environment. It is more reasonable to support App Connector rather than Deployment Connector.
And for your specific scenario, as you said before, you can just keep the deployment so that service connector would not be deleted rather than delete the deployment every time. It should be fine as deployment is designed to do re-deploy every time.
And also the deployment level have multiple independent runtime parameters, how do you deal with them? for example, the environment variables.  (As Service Connector serves like environment variables)
And indeed, the re-creation problem of Service Connector is still existing no matter which level it is. We try to find solutions of it, but it still under discussion at it may related to infrastructure problem. (Service Connector needs to depend on the deployment existence, so we could not take effect during deployment creation)

@ChenTanyi
Having the two deployments created any time is not the solution I would like, as the staging deployment for us is only usefull during a new app version deploy, to be sure that the app will start correctly, in order to not affect the production one. Once the app is correctly started and the switch from staging to production done, the old production deployment which is now staging is not needed anymore and I would like to delete it.
This is of course MY use case and other users may have a different one.
Having two deployment also requires to stop the staging one to avoid billing.
Every time I deploy a new app version on the staging deployment, I give all the informations like environment variables as they may be differents. Another example is the runtime as we are currently migrating ours apps from Java_11 to Java_17.
For the moment, we do not have implemented the fact to keep the two deployments in our deploy workflow, we are still deleting the old production deployment and creating a new one. But the day we will modify our deploy workflow to keep the two deployment, we may be facing problems if we need to change some parameters on the already existing one (cpu, memory, env, runtime, etc), I don't know if all will be updatable easily.

@julienbourgoin-maif
Thanks for your more information!
It makes sense just to delete deployment to avoid billing as it is just for rolling update. But in your case, it is more like a rolling update scenario. As far as I know, Azure Spring App has supported rolling update already, showed in "Plan comparison" part of pricing page. It is based on kubernetes deployment rolling update (create new pod then delete old pod after new pod ready). You don't need to do it manually, and you could change every properties in deployment as you need. Usually, you would only need to validate the update succeeded in the INT or Staging environment.
The problem is still under discussion as usual, but as it is more about user experience than technical problem. It is not so easy to make a final decision yet. So, appreciate your patience about it.

@julienbourgoin-maif
We are happy to add an update here. The Service Connector for Application Level is now available! And the Service Connector button in Spring Application portal page has been replaced.
You can use the portal or cli for it. Thanks!

Hi @ChenTanyi
Thank you for the update.
This is a great news and I will try this as soon as possible :)
I will now be able to use service connectors way more easily than before and move from deprecated service bindings to service connectors !
Thanks

Hi @julienbourgoin-maif! Is it fine for you of we close the issue?


Fix the jets3t dependency according to the Hadoop version

Fixes S3 support for Hadoop >= 2.3 (ZEPPELIN-111 https://issues.apache.org/jira/browse/ZEPPELIN-111)
Regression from PR #88.

Tested with Hadoop 2.4.

+1 on this :)

Looks good to me, thank you for taking care!

Thanks!
Looks good to me.


[Bug]: The run button loads in infinte loop

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
The run button loads in an infinite loop in data sources

Steps To Reproduce

I am facing the issue in the below app
https://release.app.appsmith.com/applications/61d2a525a201f119979dd6c9/pages/61d2a525a201f119979dd6cc

Environment
Release
Version
Cloud

Looks like a FE issue. The client is not making executeAction API call.

Re-opened this issue because an edge case was missed.
Reproduction steps
When we update the query very fast but the previous value and ending value remains same eg. ABCD we remove D and then add D so the ending data remains ABCD  and we hit CMD+ENTER for running the query. Then the loading state remains in the infinite loading state.

reopening the issue need to fix one corner case https://www.loom.com/share/45f67edbb70e46faa0169192c7152abd

Effort - 3 Days

@AmanAgarwal041 , @Nikhil-Nandagopal , @RakshaKShetty , is the bug still persisting? When I try to replicate the issue, it works fine for me. Could you please confirm?

@saiprabhu-dandanayak it looks like it was fixed


Quickswitcher (CTRL+K) results aren't sorted by tab order

Describe the bug
When opening the quickswitcher and typing a channel name in, if I have the channel open in two tabs I expect the order of the options in the quickswitcher to be sorted by which tab comes first.

To reproduce
Open two tabs bbb and aaa
In bbb, open channel pajlada
In aaa, open channel pajlada
Press CTRL+K, type in pajlada.
Options will be listed like this:
pajlada (in tab aaa)
pajlada (in tab bbb)

Screenshots

Chatterino version
https://github.com/Chatterino/chatterino2/commit/7002954aa953cc68ed532d20f876250ff31f07cd

Operating system
N/A

Additional information

Preferably, the Notebook class could provide a sorted list of SplitContainers. That way all components iterating through SplitContainers can rely on a consistent order,

@leon-richardt Sorted as in the user's personal arrangement of tabs, right? Might pick this up.

Sorted as in the user's personal arrangement of tabs, right?

I think that would make the most sense, yeah.
When implementing this, you might have to take care what happens with the order when users rearrange their tabs and how that interacts with window layout serialization. Not sure if it's actually going to be a problem but that could be a pitfall I would be on the look-out for

Fixed in #2561


Fix & Clean karpathy_game notebook

Since this seems to be the only up-to-date example available now. I believe it would be great to make it work for everyone.

tf.ops.reset_default_graph() throws exception in released tensorflow. Replaced it with from tensorflow.python.framework import ops & ops.reset_default_graph() which works fine
Removed from __future__ import print_function, since it seems not used.
Removed the cached results

Pls double check.

Dear Daniel,
Thank you for your pull request, great job! Before I can accept I have a few comments:

this is a relic of an old version of TF. Now it is just tf.reset_default_graph()
but maybe it was interesting? Don't I do print(...) somewhere? If yes now it is printed as tuple...
But I want to keep the results in case people just want to see what notebook would have outputed if they run it (github has online notebook viewer).

Let me know if this make sense for you!
What word becomes shorter when you add two letters to it?

Changed it to tf.reset_default_graph
brought it back
produced the results from another run. Works. Though github seems to have problem with rendering svg images.

additional changes:

changed to journalist.add_graph(session.graph) rather than journalist.add_graph(session.graph_def) since pass graph_def will be deprecated
fixed the last cell by changing x[:-2] to x[:-4] according to karpathy_game.py:83

The answer is short!

Wow, that's awesome thank you for your hard work! You solved the riddle ! ;)


Resolutions Table

Dear Community,
The "Resolutions" table is not visible in Dynamis 365 Field Service. Is there any additional step in order to see that table so we can relate to Incident types and work orders process?

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

ID: 24bd7cb6-73f5-8b18-e011-c329348d2855
Version Independent ID: 268b462b-5a63-8b1e-0014-3077f6129629
Content: Capture work order resolution details in Dynamics 365 Field Service
Content Source: ce/field-service/work-order-resolutions.md
Service: dynamics-365-customerservice
GitHub Login: @FieldServiceDave
Microsoft Alias: daclar

Hi! Thanks for raising this docs issue - if this is still an active question, we encourage you to post it on our community site for more active troubleshooting: https://community.dynamics.com/365/fieldservice


139 remove sample site

closes #139

:tada: This PR is included in version 1.0.2 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix call to NSWorkspace.selectFile:inFileViewerRootedAtPath:

The path parameter is declared as being non-null (in the Xcode 7 10.11 SDK)
so pass the empty string rather than nil.

Fixed by 24b4a3f7a490.


inconsistent es6/commonJs in Fragments?

Hi Jaap et al.
My coworker points out that the generated code for a fragment file (at least) uses require to bring in @apollo/client but exports using es6 style.. This seems to be a problem for webpack...5?
Any tips or plans to square that up? any way I can help?
Thanks
Alex
@cid8600 @mattloomis

If you are using template tags we need an inline require(..) to make it work reliably because ReScript doesn't have support for template tags. You can use templateTagAsFunction which is documented in rescript-apollo-client when you use a bundler that doesn't support require. It's a trade-off, template tags can have some benefits over strings. I would love to have a proper solution for this but I raised possible solutions in the rescript compiler that have not been addressed the past 2 years so I wouldn't hold my breath.

If the require is necessary can the exports be made to be commonjs instead?

im not recalling what a templateTag is

By the way, this shouldn't be a problem with webpack5, I have an webpack 5 website deployed that works fine. What is your configuration?

Hi Jaap
Sorry for the delay...I'm finding this issue again now looking for webpack alternatives.
The build system in question today is vite

(Not a pressing issue, but I would love to never see webpack again, personally)


How to get this run?

Hello Michael, would you please share how to get this run? My Setup is a Cerbo GX and Arduino Due. I was able to get data from the original TeslaBMS on Serial Monitor. I want to use an newer version to get a better battery balancing. Also i want to get the Battery data in Venus OS, SoC would be great.
Your TeslaBMSV2 is just for SimpBMS Boards? While on your TeslaBMS package i dont get any data on Serial Monitor.

Hi Gary,
Apologies for the sorry state of documentation on this project.  I was using it in more of a dev mode and never got to the point of an easy to install tool.  But, here are the highlights:

The Arduino Due running TeslaBMS is plugged into a USB port on the CerboGX
I SSH'd into the CerboGX, and manually stopped / blocked the in-built serial handling of the connected Due device using svc command.
I then start a screen instance and manually execute teslabms.py -p /dev/ttyXXX, using the proper path to the Due's USB tty.

Note that I was never able to get the i2c shunt working directly on the Due that is operating the BMS, even though it seems it should have been very possible.  I don't know if the serial timing hacks that is needed for the BMS to operate at  617647 baud that was causing i2c interfaces to fail.
For that reason, I moved the i2c shunt onto a separate Arduino Nano, then connected the serial pins from the Nano to one of the Serial pin sets on the Due.  This allowed me to get both the shunt and bms data in one connection to the CerboGX.  I just pushed the code for this into my ina219_shunt repo.
fwiw, I never found that the Tesla modules needed balancing, so I never pursued that functionality beyond mostly disabling it by setting such a high balance voltage.
I've since stopped full time RV travel, and have my coach up for sale with the Victron gear installed, so I won't be continuing the project personally.  If you would like to finalize the CerboGX side to be easily installed, I'd gladly accept a PR, or you are of course, more than welcome to fork the project as well.
I used a lot of info from dbus-serialbattery to get as far as I did.. It would be good to use their install process as a base for getting this project to be easier to install and run.
I'm happy to answer any other questions you may come up with along the way.

Thanks for the fast response, I will test the steps tomorrow 🙂

I've tried but i'm not able to get this run:
ps | grep ttyACM0
1367 root      1612 S    supervise dbus-serialbattery.ttyACM0
1370 root      1756 S    multilog t s25000 n4 /var/log/dbus-serialbattery.ttyACM0
22974 root      1612 S    supervise gps-dbus.ttyACM0
22987 root      1624 S    multilog t s25000 n4 /var/log/gps-dbus.ttyACM0
23074 root      1612 S    supervise vedirect-interface.ttyACM0
23085 root      1624 S    multilog t s25000 n4 /var/log/vedirect.ttyACM0
28327 root     20408 S    python /opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py /dev/ttyACM0
28353 root      2692 R    grep ttyACM0
I think this is the right device, used by dbus-serialbattery, by running /opt/victronenergy/teslabms/teslabms.py -p /dev/ttyACM0 i get the error: modulenotfounderror: no module named 'vedbus'
Any idea?

Hi Gary,
You can confirm the right tty by using dmesg.  It'll print a few lines whenever the Due is plugged in, including the tty device assigned.  However, ttyACM0 seems very likely to be correct.
Re: the no module named 'vedbus' message...
I just pushed an update to point to the correct path for the vedbus python modules ( based on what's in dbus-serialbattery code now.. )
Let me know if that takes care of it! :)
NOTE: With the other services using ttyACM0, it's likely you'll get a denial on trying to open the port.  The following, might terminate those other services and allow the teslabms.py code to use the port:
svc -d dbug-serialbattery.ttyACM0
svc -d vedirect-interface.ttyACM0
rm -rf /service/dbus-serialbattery.ttyACM0
rm -rf /service/vedirect-interface.ttyACM0
ln -s /service/dbus-serialbattery.ttyACM0 /dev/null
ln -s /service/vedirect-interface.ttyACM0 /dev/null

These commands should be copy/pasted as a block.  Delays between steps might allow the system time to re-create the services before you link them to /dev/null.
Unfortunately, I don't have a CerboGX to test on at this point.. so, ymmv.

First success... ive got the Tesla BMS Menu in Venus OS. But there are no Information from the Modules except the variables from teslabms.py. i have changed the Modules to 2.
How do you connected the can signal? had it working on pins 18 and 19 and 5V and GND on the original TeslaBMS.

Hi Gary,
In TeslaBMS config.h, the BMS serial is set to Serial1.  This defaults to pin 18/19 for tx/rx respectively.
Note that there's no CAN bus code in my version of TeslaBMS -- but the BMB comms are serial.. so that shouldn't be a problem.

Hi Gary,
Sorry I wasn't more clear.  There's no need for the dbus-serialbattery code or anything else to be installed for the code from my repo to work.
The Arduino TesaBMS I modified is needed for this venus-teslabms to work because I changed the output format and had it go directly into dumping the values with no input needed.
If you have data using the other TeslaBMS code, you should be able to flash my code and get data as well, just no menu to worry with ( although, most of the menu commands do still work ).
Note that no output will be generated by my fork of TeslaBMS unless it gets data from the Tesla BMB's.

That's even better, alright i will check again later! Thank you very much for helping me!

One more success... in my case I'm running 2 modules in series so it need to sum up the Voltages, would you help me to edit the code? My only help ist ChatGPT-4 and its dump even Code Interpreter...

Im closing this issue, in fact you helped me to get this working, so i will continue to edit it for my setup. Thanks for helping!

Hi @GaryCooper23 ... I'm concerned that your data doesn't include the high/low cell voltages and temperatures.   Feel free to open this, or another issue if you run into things you need further assistance with.
o/


Yellow Border  from VS CODE after cloning a git repository

Like the title says, my VS Code border changed to this yellow after cloning a git repository.  I've tried changing themes, but all this does is change what's inside the yellow borders.  I'm sure there's a way to change the color, but I can't find how to change it.  I'm attaching an image to show what it looks like.

@JSierra0918 can you check your user setting or workspace settings or project settings (under .vscode folder in the project) to see if you have any settings related to theme customization?

I was able to resolve the issue.  Turns out the guy repository was also
including a user setting in this weird folder.  I deleted it and it seems
to be working now
On Sun, Mar 15, 2020, 5:08 PM Peng Lyu<EMAIL_ADDRESS>wrote:

@JSierra0918 https://github.com/JSierra0918 can you check your user
setting or workspace settings or project settings (under .vscode folder in
the project) to see if you have any settings related to theme customization?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/92723#issuecomment-599264872,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALJGOIQGAUTSB7L6ESJIVSTRHU7URANCNFSM4LLCKX5Q
.


add union-find based dependency tracking

book/Phantom now evict things one MicroWave at a time
MicroWave now maintains its own staleness & size info
add a UF between MicroWaves, and track the total cost of each UF class
add heuristics & tests using the UF class

it should be easier to read commit-by-commit, starting from the new tock tree API one.

great great.
another thing:
when we actually evict a node, its UF cost will be different from what we are right now, because the UF keep changing.
can you add some code, that retest if the new cost is within [0.5, 2] range of the old cost? if so eviction continue as normal, if not it get re-added with the right value back into kinetic heap.


[javascript][v8] Support for swig 4.1.0

Support for swig 4.1.0
In swig 4.1.0, the complicated handling of "SWIG_V8_VERSION" has been cleaned up a bit. I made the same changes as in this swig.
Signed-off-by: Hirokazu MORIKAWA<EMAIL_ADDRESS>

Thanks for submitting a fix for #1040 and #969. I'd be really happy if someone can see this all the way so we can reenable node.js bindings. My only question, does this also need the SWIG changes to work?

@Propanu
SWIG 4.0.2 does not work with node v12.x (v8 7.8) & higher, so I verified it with node v10.x (v8 6.8).
I have also verified that it works with SWIG 4.1.0. No problems were found in either case.
node v10.24.1 (v8 6.8.275.32) (EoL)
swig v4.0.2
mraa v2.2.0 + patch   -> OK
upm v2.0.0 + patch    -> OK

swig v4.1.0 ((in progress)
mraa v2.2.0 + patch	-> OK
upm v2.0.0 + patch	-> OK

I will test node v12.x v14.x v16.x.　It may take some time.

@nxhack thank you for checking the latest node.js versions. You will need to accept the Eclipse Committer Agreement (ECA) in order for us to merge these changes. It would also help to add a patch file in the MRAA project with the SWIG changes so we can apply that during our CI checks, but that's something we can worry about later.

@Propanu
I agree with ECA, CI is now green.

@Propanu
I will not make any changes to SWIG, as I have heard their implementation policy. In the upcoming SWIG 4.1.0, MRAA v8 related code with this PR will be able to build successfully.

I am very sorry not to be able to  follow regularly your work. I am building raspberryPi debian Oses with mraa and upm at the moment. I can spend some time on tests. I feel that we are very close to a clean build. Let me know what tests you want me to make; my goal is to build in a bullseye with the most recen node and swig if possible.

@Propanu I can see it is approved but I confirm that the patch works perfectly with the following context
Many many thanks again :+1:  to @nxhack  for the great work and for the   git  training session ;-) . Here are the version used and what I did :
Linux myPi 5.12.6-v7 #1 SMP Mon May 31 18:19:07 CEST 2021 armv7l GNU/Linux
SWIG Version 4.1.0
gcc version 10.2.1 20210110 (Debian 10.2.1-6)
node v16.2.0
npm 7.15.0

cmake .. -Wno-dev -DCMAKE_INSTALL_PREFIX=/usr -DENABLEEXAMPLES=0 -DBUILDSWIGNODE=ON -DSWIG_EXECUTABLE=/usr/local/bin/swig -DV8_ROOT_DIR=/usr/local/include/node -DNODE_ROOT_DIR=/usr/local/include/node     -DPYTHON2LIBS_FOUND=FALSE        -DPYTHON2INTERP_FOUND=FALSE   -DWERROR=OFF -DCMAKE_CXX_STANDARD=17


printing from blazor webassembly

Hi Luke,
excuse me for perhaps a nonsense question: Is it possible to implement your library in a blazor webassembly application and print to a network printer ?
Regards,
Fabianus

Hey Fabianus,
The byte builder part of the library should all be usable. The network printer may not work since it is expecting to be able to open direct TCP connections. The image processing functions in image sharp probably won’t work but maybe they will?
Typically if you are making a web app and you want local printing support, you would implement this by building a local webserver and then making RPC calls to it from your web app to local host, and that server would have privileges to connect to serial ports and such. This is how other solutions accomplish this, eg:
https://www.neodynamic.com/articles/How-to-print-raw-ESC-POS-commands-from-Javascript
https://www.printnode.com/en
This should be pretty easy to do with .net core and kestrel, but would require the end user to run an app on their device like these other solutions. If you want to try to accomplish this without that setup you will need to be able to make http or https calls to the printer, which is unlikely if you’re trying to print esc/pos.
If this is a use case you really want to explore, perhaps as a commercial endeavor, I’d love to help out and would be available to build this out if you’d like. We could also do this open source too. It would be a helpful extension to this lib.

Hey Luke thanks a lot for all the details!
I think this is a really fundamental question as printing from web applications to pos printers is probably one of the most common use cases of printing from those applications. Having to install a local printing server is a detour that creates all kinds of troubles. If a blazor webassembly application would be capable to print tickets, bills etc. without any additional preparation - wow.
Your write that making http calls to the printer is unlikely f or print esc/pos. I am not sure to understand all implications but wouldn't that be possible without any detour with this model ?
https://www.epson.eu/viewcon/corporatesite/products/mainunits/overview/11357#specifications

Fabianus,
I researched this more, and I was wrong about this.  If you wanted cross-platform support for TCP/IP printing (against a server) that is already built into the library.  However if you want to print directly from a browser to a receipt printer without any software in between, this is in fact possible with Epson printers.  The TM intelligent printers have a built in server that you can directly connect over http(s) using the Epson oPOS Javascript SDK.    Here is a list of "intelligent" printers that have the embedded webserver: https://download.epson-biz.com/modules/pos/index.php?page=genre&pcat=52
If you wanted to pursue this, we would love to have a PR!  I don't have a TM-Intelligent printer so I can't assist with development, but it seems possible to create an interop between Blazor and the Epson JS API and then print directly to the printer that way with nothing else in between.
This would be epson-specific and would only support these TM-I printers.  If you did it with the separate webserver as I mentioned before, it would be universal for all ESC/POS printers (even cheap non-epson printers).

@fabianus76  one other thing to keep in mind would be the fact that a $35 Raspberry Pi can be used for this webserver - the library works great on Raspberry Pis directly to USB printers - and you would be able to buy MUCH cheaper printers then as you would be able to use USB printers.  Something to keep in mind, as the price of these intelligent printers (and network printers in general) is generally much more than $35.  This would also give you compute on the edge which would let you potentially do other POS-related operations.  Not sure what you're building or your business model but something to keep in mind.

Here is something you could use to run on the raspberry pi if you wanted to pass through the bytes directly from a websocket to a TCP connection, but will still require something like a raspberry pi to run it: https://github.com/novnc/websockify

Hey Luke, what should I say. I am amazed about the research and very thankful for all the information you put together.
Both ideas (TM intelligent printers and an intermediate raspberry) are very interesting. I agree that Epson printers are not the cheapest, but from my long term experience they are worth the money (I have 4 TM-T88V in production since 10 year - not one incidence so far).
I would love to tell you more about my project and will PM you.

@fabianus76  happy to help!  Where do PMs go in GitHub?  I'm not sure if you haven't messaged me yet or if I just don't know where they go.

Thanks Luke, I tried to find your e-mail address on https://www.paireepinart.com/ but couldn't find it there. Would you mind to send me yours at fabianus (a) gmail ?


Resolve 'Never' keyword issue with TypeScript

Added void type to setMainView

:tada: This PR is included in version 3.5.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


repository-services client addEntity failed

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
when I use repository client to add entity, the server return 404.
Expected Behavior
the right url would be " https://localhost:9443/servers/{serverName}/open-metadata/repository-services/..."
but the request url was "https://localhost:9443/open-metadata/repository-services/..."
Steps To Reproduce
No response
Environment
- Egeria:3.12-SNAPSHOT
- OS:centos7
- Java:11
- Browser (for UI issues):
- Additional connectors and integration:

Any Further Information?
No response

Hello @DLaoLiu.  The "/servers/{serverName}" part of the URL is supplied on the constructor of the client.  I am not sure which client you are using but they both work with the same base class, so the logic is similar.  Here is the JavaDoc for the LocalRepositoryServicesClient:
    /**
     * Create a new client with no authentication embedded in the HTTP request.
     *
     * @param repositoryName name of the repository to connect to (used in error messages)
     * @param restURLRoot the network address of the server running the repository services.  This is of the form
     *                    serverURLroot + "/servers/" + serverName.
     *
     * @throws InvalidParameterException bad input parameters
     */
    public LocalRepositoryServicesClient(String repositoryName,
                                         String restURLRoot) throws InvalidParameterException
    {
        super(repositoryName, restURLRoot, "/");
    }

If you update your restURLRoot to https://localhost:9443/servers/{serverName} when you call the client, all should be well.
This is different from most of Egeria's other REST clients which typically take the platformRootURL.  However the respository services may have to call servers that are not Egeria and not multi-tenant.  This is why the /servers/{serverName} part of the URL is parameterised in the constructor.

Yes, I did not add /servers/{serverName} while calling. I will try again. Thanks for your reply!

Assuming all ok now


Flexget discover error

Hello im using flexget and discover, everything was working fine but last few day im getting error:
2016-04-23 14:18 CRITICAL task          get_tvshows     BUG: Unhandled error in plugin discover: 'NoneType' object has no attribute '__getitem__' Traceback (most recent call last):   File "/usr/local/lib/python2.7/dist-packages/flexget/task.py", line 438, in __run_plugin     return method(*args, **kwargs)   File "/usr/local/lib/python2.7/dist-packages/flexget/event.py", line 22, in __call__     return self.func(*args, **kwargs)   File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/input/discover.py", line 274, in on_task_input     entries = self.estimated(entries, estimation_mode)   File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/input/discover.py", line 190, in estimated     est_date = estimator.estimate(entry)   File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/estimators/est_released.py", line 28, in estimate     estimate = estimator(entry)   File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/estimators/est_release_series_tvmaze.py", line 51, in estimate     episode = lookup(**kwargs)   File "/usr/local/lib/python2.7/dist-packages/flexget/utils/database.py", line 31, in wrapper     return func(*args, **kwargs)   File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/api_tvmaze.py", line 520, in episode_lookup     series = APITVMaze.series_lookup(session=session, only_cached=only_cached, **lookup_params)   File "/usr/local/lib/python2.7/dist-packages/flexget/utils/database.py", line 28, in wrapper     return func(*args, **kwargs)   File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/api_tvmaze.py", line 467, in series_lookup     pytvmaze_show = get_show(**prepared_params)   File "/usr/local/lib/python2.7/dist-packages/pytvmaze/tvmaze.py", line 415, in get_show     show_web_channel, embed=embed)   File "/usr/local/lib/python2.7/dist-packages/pytvmaze/tvmaze.py", line 467, in _get_show_by_search     show = _get_show_with_qualifiers(show_name, qualifiers)   File "/usr/local/lib/python2.7/dist-packages/pytvmaze/tvmaze.py", line 444, in _get_show_with_qualifiers     country = show.web_channel['country']['code'].lower() TypeError: 'NoneType' object has no attribute '__getitem__'
Could you please help me solve this :) Im using last version of flexget 1.2.521

I was waiting to see if liiight wanted to check this out since he is the one implementing pytvmaze in flexget, but after looking into it it I think I see the issue.  We're naively assuming that country code info exists for a given show.  I'll work on a fix but might not get to this before the weekend.

I must have missed this one till now

@liiight All good, looks to me like we just need to do a little checking to see if those values exist before trying to get them.  I might have time for this after work today.

The above commit should fix this @brothell - let me know!


Not respecting links

I installed this a couple days ago and imported my Obsidian vault, when I looked at the pages in the Journal none of the links were maintained, they were all text. Is there only a certain format the plugin expects for links?

The page in Obsidian

Thanks for providing those screenshots! That helps a ton. Nothing seems wrong with those links just from looking at them.
I have to ask the obvious just in case: were the notes associated to those links imported as well? This could happen if you import a subfolder and it contains links that were not imported.

Side by Side in Foundry and Obsidian. I'm assuming the one in Foundry is/was the one in Obsidian. :)
Showing the obsidian versions in edit mode so you can see that the data in both files match. Also figured edit mode might show anything 'off'.
What I find really odd is in both pages, the link to the Eberron 'parent' page (the page under which all the imported files belong) is linked. But that's the only one.

Did you receive an "import complete" message? I am wondering if there is some underlying bug that stopped the link replacement from completing.
I did fix one bug. Could you please try upgrading the module to the latest version and seeing if you can still reproduce the issue?

Negative, same result. Even deleted that world and created a new one and reimported. Same pages, same results, no linkage.

Just saw you question about the "Import Complete" messaged so I created another world and imported again, this time with the debug console open. Sure enough, it threw an error in the console:
SyntaxError: Invalid regular expression: /\[\[(Calendar|Eberron/Modules/Eberron Campaign Setting (3)\]\]/: Unterminated group     at new RegExp (<anonymous>)     at MDFileInfo.getKeyRegex (lava-flow.js:313)     at Function.updateLinks (lava-flow.js:210)     at Function.importVault (lava-flow.js:77)     at async LavaFlowConfig._updateObject (lava-flow.js:260)     at async LavaFlowConfig._onSubmit (foundry.js:3822)
So I did some further digging. The files it's complaining about below is actually titled Eberron Campaign Setting (3.5). I renamed it, removing the (3.5) and everything imported without issue.
At first I thought it might not like the extra period in 3.5 so I renamed another file, adding an extra couple of periods but that also imported without issue. So I then renamed another file called Forgotten Forge to Forgotten Forge (3.5) and it failed again with the same error message as above, 'Unterminated group'
It doesn't like having a period (a.k.a. 'separator') inside the parens. I'm guessing that on line 309 in lava-flow.js, when you split on the separator for this filename it's returning Eberron Campaign Setting (3. as the fullKey which the regex freaks out about because of the open paren.
I can easily work around this by removing the '(3.5)'. I don't know if a lot of people will do things like this,  but it's something to maybe think about in the future. At least for cases when someone else reports the issue :)
Anyway, great work!

My next suggestion was going to be to open the console, so thanks for anticipating!
Yeah I need to do some regex escaping. You shouldn't have to remove that stuff for it to work. I'll update when I have a fix for that, but glad to hear you have a workaround.

Release 1.0.3 resolves this issue. Thanks for your feedback!


slance/tenancy without tenant.php

currently, I'm using slance/tenancy package for the dynamic database by the domain name but when I have a new route I need to add to api.php and tenant.php also. it possible or not if I use only inside api.php if it is possible please tell me the solution how to do that than

https://tenancyforlaravel.com/docs/v2/tenant-routes/#custom-groups


[SPARK-18119][SPARK-CORE] Namenode safemode check is only performed on one namenode which can stuck the startup of SparkHistory server

What changes were proposed in this pull request?
Instead of using the setSafeMode method that check the first namenode used the one which permitts to check only for active NNs
How was this patch tested?
manual tests
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
This commit is contributed by Criteo SA under the Apache v2 licence.

Here is the pull request for apache master branch: https://github.com/apache/spark/pull/15648
Will see then how to do the same for 1.6 branch


How to suppress IBM Notifier: Opening Install now up to date notification

While trying to use the Install Now functionality i would like to make it seamless for unattended installs.  One issue identified is that after all updates install, IBM notifier shows a final message stating "Apple System software is already up to date or is the latest version allowed by management.   Looking for ways to suppress this message or make it go away on its own.  currently requires end user to hit OK for it to go away.   The super.log shows it as  "IBM Notifier: Opening Install now up to date notification"

A few scenarios of the above also keeps a window of "Apple Software Update Starting" that never quits.  again this is after it has installed all updates and performs the last reboot.  only way to get rid of the "Update starting" window is to kill the IBM Notifier app from Activity Monitor.

--install-now is intended for Self Service situations, where you do want those extra dialogs. If you do not want them, do not use --install-now.
See https://github.com/Macjutsu/super/wiki/User-Initiated-Workflows#install-macos-updates-now for more information.

@wacko is correct regarding the purpose and design for --install-now. However, the default for super (if a user is logged in) is to prompt the user for a restart. Thus if @yinfante356 want's to start the workflow without asking, you actually want to use a hard deadline that has passed. For example, use --hard-count=0.
Given that there is a solution in super to accomplish the actual goal of installing while unattended. I'm closing this issue.

Thank you for the feedback @wakco and @Macjutsu . i appreciate the fast response on this matter.


Crop the circles when zoomed in

This is the view on zoom currently

Obviously, that cannot be in our final product. We need to either crop the canvas, or somehow filter the dots that get drawn. We could filter them to the specific state you click on, but seeing as hydrology does not obey political boundaries, it would probably be useful to see nearby gage conditions. If we did want to just show the ones for the state someone clicked on then I could add the state code to each points data and filter on that.

Oh, I was referring to the cropping as this:

I'm not bothered as much by dots in adjacent states for the MVP. But dots in the footer...we should get those cleaned up.

Ah - didn't see that. I wonder how that's even possible. The canvas layer doesn't go down that far. I'm also thinking we need to clean up the way the legend is crowded by the dots on zoom for the MVP.

Oh, you know what. It does go down that far. And for a very obvious reason: https://github.com/USGS-VIZLAB/gage-conditions/blob/master/js/app.js#L31


Can I edit a running assistant

Can I transition from running an assistant to editing the assistant? Can I have an edit button when running my assistants?

@thedadams I'm filing this under the work you are doing around "Save as.." and thus assigning to you.

Using this issue for the basic "save as" functionality without knowledge.
That PR is here: https://github.com/gptscript-ai/desktop/pull/351

The basic (without knowledge) save-as functionality is in.
There is another more comprehensive PR adding the knowledge stuff to this functionality.

Tested with latest build from  090c16f8a
"Save Assistant" and "Save Assistant As" options are available and working as expected.
Other issues seen when testing this workflow will be logged a separate issues.
Scenario 1:

Chat with Tildy.

Add few tools  using "Add tool from catalog"

Have conversations relating to the tools that was added.

Use "Save Assistant As.." option to make a new assistant.
This results in a new assistant being created with tools added from step2 and current thread starts using this assistant.

Able to chat with the new assistant that was created in step4 with the tools that were added in step 2.

Scenario 2:

Create an assistant with some tools.
Chat this is assistant.
Add another tool to the thread using  "Add tool from catalog".
Use "Save Assistant" option.
This results in a new tools being added to the existing assistant.


nodePackages: init hsd, hs-airdrop, hs-client

Motivation for this change
This adds a few tools related to the handshake decentralized naming system.
The following tools are added:

hsd
hs-client
hs-airdrop

Things done

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

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

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

Updated commits and rebaed on master. Thanks for the help!!

rebased on master, would be great to get this merged...

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/286

This is a huge diff! I am a bit afraid of it.

Unfortunately, this is unavoidable due to the way node packaging is done in nixpkgs. The source of the huge diff is node-packages.nix, which is generated automatically by this script here: https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/node-packages/generate.sh

Well, if nothing can be done...

@d-xo What's the purpose of having hs-client in nixpkgs. It's only a JS library.


Horizontal axis tracking with azimuth angle that isn't 180°?

Dear bifacial team,
first off, thanks for all of your great work, it has taught me A LOT.
As a part of my studies I've been given the task of performing an irradiance + shading analysis (front side, back side, ground beneath) of a horizontal axis tracking system with an orientation that isn't the standard 180° azim e-w orientation, despite my protests against this design. It's a southwest facing array, 225° azim.
I consistently get surface_azimuth errors when trying to run my code and am at the limit thinking it's not really possible after studying main.py. Do you have any insight on this problem?
Thanks ahead, even if the answer is negative.

Hi metavektor, thanks for the query.   Please provide more details on your specific error(s).  I'd also recommend updating to the latest bifacial_radiance 0.3.4 version that was just released yesterday which fixed a few bugs.  I haven't seen specific issues with arbitrary tracker azimuth angles in the past, but please provide the error messages for us to investigate.  Thanks!

Hey cdeline,
thanks for the response. I found another post from shirubana that likely covers this, as I'm getting the following error as well.

OK, this is fixed in master by commit https://github.com/NREL/bifacial_radiance/commit/3b44160f7b6d2f4d89b7c7bf30af9b3facca5b2c.  It'll be included in the next release.  If you don't want to wait, you can download the fix by cloning the repository and installing from there with pip install -e .  Thanks!

Will give it a shot, thank you!


new version of whatsapp

Hello everyone,
when i use whatsapp version(2.21.4.x) then it works but when i use whatsapp version(2.21.7.x) then it throw a error
line 44, in getattr
wapi_functions = dir(self)
TypeError: 'NoneType' object is not iterable

You mean that works differently when using different versions of whatsapp in the phone?
That's really incredible, because whatsapp works in the web version.
I saw that problem few issues before...
wapi_functions = dir(self)
TypeError: 'NoneType' object is not iterable
Mine still working without issues.


Unexpected: The content server has unexpectedly rejected the request with: LengthRequired when using Dependabot

Describe the bug
We are using Dependabot to keep our dependencies updated. This runs scheduled on every monday morning at 7am. Pull requests created in our repository, automatically trigger a workflow that will create a staging site to see the changes in the pull request.
One of the steps in the workflow is the Azure/static-web-apps-deploy@v1 action. For every pull request created by Dependabot the workflow will fail at the Azure/static-web-apps-deploy@v1 step with the following error:

Now the strange thing is, if I restart this workflow, it does work. Until yesterday :) I have restarted multiple times now but it keeps failing with the same error.
Other pull requests created directly by developers work fine and are correctly deployed to a staging environment.
I have searched online, but I couldn't find a lot about this specific error (LengthRequired)
I'm unable to share the full workflow YAML file, but here is the excerpt for the specific step (runs on ubuntu-latest):
- name: Build API & Deploy
        id: builddeploy
        uses: Azure/static-web-apps-deploy@v1
        with:
          azure_static_web_apps_api_token: ${{ secrets.VERY_SECRET_TOKEN }}
          repo_token: ${{ secrets.GITHUB_TOKEN }} # Used for Github integrations (i.e. PR comments)
          action: 'upload'
          ###### Repository/Build Configurations - These values can be configured to match your app requirements. ######
          # We follow the procedure where we control the build ourselves: https://docs.microsoft.com/en-us/azure/static-web-apps/build-configuration?tabs=github-actions#skip-building-front-end-app)
          # For more information regarding Static Web App workflow configurations, please visit: https://aka.ms/swaworkflowconfig
          skip_app_build: true # Skip app build - optional
          app_location: 'dist' # App source code path
          api_location: 'api' # Api source code path - optional
          output_location: '' # Built app content directory - optional
          ###### End of Repository/Build Configurations ######

The contents of the staticwebapp.config.json file are the following:
{
  "navigationFallback": {
    "rewrite": "index.html"
  },
  "platform": {
    "apiRuntime": "node:14"
  }
}

Expected behavior
I expect automatically created pull requests to build successfully as well. Also if it does fail, I would expect a more descriptive message to give me some hints where I should look.
Device info (if applicable):
The workflow runs on ubuntu-latest and the action is at V1. The workflows are run from Github.
Thanks in advance!

Hi @boy-incerta do you know if the secret that is passed into azure_static_web_apps_api_token was edited at all from the default generated secret? If it was, can you try updating the value of the secret again (you can find the deployment token in portal as per https://docs.microsoft.com/en-us/azure/static-web-apps/deployment-token-management#reset-a-deployment-token, but no need to actually reset the token). I would keep an eye out to make sure the value you put into the secret does not have any extra spaces or newlines at the beginning or end as well.

Hi @joslinmicrosoft, I think if the token would be incorrect the deployment would never work instead of what is happening right now. Anyways, I tried updating the secret again but with the same result: The content server has unexpectedly rejected the request with: LengthRequired

@joslinmicrosoft Did you investigate this any further? We are still experiencing this.

Hi @joslinmicrosoft did you investigate this any further? We are still experiencing this issue, which blocks us in using Dependabot together with azure/static-web-apps

Hi @boy-incerta sorry for the delay here. Just to confirm, when you checked the secret, did you check the Dependabot secret to make sure it is correct, or just the GitHub action secret? The reason why I keep asking is that the behavior seems different depending on if the workflow actor is Dependabot or not; the main difference relevant to our action is how secrets are accessed: https://docs.github.com/en/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions#responding-to-events.
This would be consistent with why the Dependabot PRs fail but those run by developers succeed. Furthermore, it seems that around the time you created this incident, there was a change made to use the privileges of the original triggering actor instead of the executing actor on re-runs: https://github.blog/changelog/2022-07-19-differentiating-triggering-actor-from-executing-actor/. This would explain why restarts worked before (as they were using your privileges, with GitHub action secrets) but now are using Dependabot's privileges even on manual restart.

Hi @joslinmicrosoft ,
I think this was the problem. It's been a while since august so not sure, but I'm afraid I didn't check the Dependabot token. Updated both now and looks like it is working! 🎉  Thanks for your support! If I can add any suggestion that would be to make that error a bit more detailed than just LengthRequired.


Test Scaffolding/ QoL

What :computer:

Added new scripts in package.json
Added new scripts for running and killing dev node
Added formatting script & CI
Add Yarn Workspaces support

Why :hand:

Ensure code formatting checking for consistency
Improve DX by having 1-button way to start and stop nodes
Adding packages to our stack so we can write richer tests
Workspaces make working with lots of packages in a monorepo far easier

This will allow for root level commands without having to rely on a brittle makefile definitions. For example, each package can own its build script, whilst running yarn build will build for all packages.
Additionally, you can run yarn commands from any location, rather than always having relational paths to where your scripts are running. i.e. you can execute yarn dev:start from any location in repo

Evidence :camera:
❯ yarn dev:start
Node is running and accepting requests!
Node launched successfully, PID: 462981 ✅

Single command to build all packages:
❯ yarn build
➤ YN0000: Compiling contracts for zkSync Era with zksolc v1.3.13 and solc v0.8.17
➤ YN0000: Compiling 2 Solidity files
➤ YN0000: Successfully compiled 2 Solidity files
➤ YN0000: Compiling 45 Solidity files
➤ YN0000: Generating typings for: 45 artifacts in dir: typechain-types for target: ethers-v6
.....
➤ YN0000: Successfully generated 86 typings!
➤ YN0000: Successfully compiled 45 Solidity files
➤ YN0000:
➤ YN0000: Done in 19s 226ms

Notes :memo:

[!NOTE]
Workspaces are such a timesaver in the long run and are relatively cheap to implement at the beginning of a repo like this. We should definitely consider either yarn or pnpm workspaces feature to manage dependencies across multiple package.json. In trying a few things for this PR I've already found it helpful being able to juggle the multiple pkg vers, like @matterlabs/hardhat-zksync-solc

[!NOTE]
Ideally we want to make this an ESM project, for future proofing and access to the latest libraries - however hardhat sadly is still using ts-node. I've put a comment to suggest they switch to tsx but we may be waiting a while for that.

[!IMPORTANT]
Please disregard the stupendous amounts of commits in this PR. Work was done to try to get coverage to work with the GihubActions workers, but it seems like there's no getting around this needs to be a self-hosted only workflow, due to the process being too heavy.

@dutterbutter we can close this PR if we don't want to invest more time in e2e. We can always revisit it later if needed

Going to close out this PR and re-open from a fresh commit. We should avoid touching the etc/system-contracts directory for ease of upgradability (as it comes from an upstream repo). I'll keep the changes for .github/, e2e-tests/, and scripts/ directories


Missing ontology scope

According to OBO Foundry principle 5, we should specify the scope of the OPL ontology.
OBO Foundry principle 5: "The scope of an ontology is the extent of the domain or subject matter it intends to cover. The ontology must have a clearly specified scope and content that adheres to that scope."
Any suggestion on it?
My suggestion: life cycle stage, parasite organism

I agree with @zhengj2007 suggestions. I think they cover the scope for OPL.

Added and showed on OBO Foundry website


[Docs] "Helper Message" section of "AutoComplete" component examples don't match descriptions

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
See issue title; that's pretty much it.  Neither example actually does what the textual descriptions say.
Expected Behavior 🤔
Examples should match descriptions and vice versa.  Really, that shouldn't have to be said.
Steps to Reproduce 🕹
<!--
  Provide a link to a live example (you can use codesandbox.io) and an unambiguous set of steps to reproduce this bug.

Go to https://material-ui.com/components/autocomplete and read "helper message" section. Try the examples. Experience cognitive dissonance.

https://material-ui.com/components/autocomplete


Scaphandre does not see other namespaces, only the one its deployed in

Bug description
Deployed on rke cluster, the scaphandre pod is deployed using helm as described and the prometheus and grafana pods are deployed using kube-prometheus-stack. All three are deployed in monitoring namespace. When I go to grafana dashboard, I can only see monitoring namespace. Other namespaces are missing.
To Reproduce

Install prometheus and grafana on the cluster:
helm install kube-prometheus-stack prometheus-community/kube-prometheus-stack --namespace monitoring

In order for scaphandre to "see" the prometheus, add release: kube-prometheus-stack in helm/scaphandre/templates/servicemonitor.yaml

otherwise, scaph metrics are not visible on grafana

deploy scaphandre
helm install scaphandre helm/scaphandre   --set serviceMonitor.enabled=true   --set serviceMonitor.namespace=xyz   --set serviceMonitor.interval=30s   --namespace monitoring

go to grafana, select scaph_process_power_consumption_microwatts{namespace="xyz"}

No data

Expected behavior
expected scaph process metrics for pods/containers in the "xyz" namespace
Environment
Linux 5.15.0-119-generic #129~20.04.1-Ubuntu SMP Wed Aug 7 13:07:13 UTC 2024 x86_64 x86_64 x86_64
GNU/Linux

Hi @smaitra53
So do you suggest release: kube-prometheus-stack to the service monitor ?
@rossf7 @mmadoo and other k8s advanced users, do you have any suggestion regarding this ? :)


Refactor mocks to avoid circular imports

We hadn't regenerated mocks since the last time the awsclient was modified. Doing so as is resulted in a circular import (code in awsclient was referring to mock which refers to awsclient).
This commit moves the mock-related IBuilder implementation into the mock package to obviate this circular import.
It also syncs the go:generate directive and the generated file's name as zz_generated.mock_client.go. (The zz_generated prefix, in addition to being a nice eyecatcher, will cause the generated file to be ignored for code coverage reporting when that's put in place later.)

/lgtm
Pulled and ran locally without issue.
Thanks for the extra comments about the file movement/generation @2uasimojo!!

/lgtm
/approve

/lgtm
/approve

/retest

/retest

/retest

/retest


Changed target RPM for flywheel to 1450 (low goal shooting) to adjust…

… to gear ratio

Looks good :+1:


Can't run even a simple example.

The problem
Hi there! I have a problem with pyth since yet a simpliest example from README doesn't work for me.
Your environment
pytg 0.4.10, Python 3.5, OS: Ubuntu 16.04 running on ODroid-C1
Steps to reproduce
The code is:
# -*- coding: utf-8 -*-
from pytg import Telegram
tg = Telegram(
    telegram="/telegram/tg/bin/telegram-cli", # path is correct!
    pubkey_file="/telegram/tg/tg-server.pub")
receiver = tg.receiver
sender = tg.sender
sender.send_msg("my_username_or_id_tried_both", "Hello World!")

And error outputs after 2 runs in a row (one after another to compare errors) are:
root@odroid:/telegram# python3.5 testbot1/bot.py
change_user_group: can't find the user telegramd to switch to
Traceback (most recent call last):
  File "testbot1/bot.py", line 10, in <module>
    sender.send_msg("MY_ID_WAS_HERE", "Hello World!")
  File "/usr/local/lib/python3.5/dist-packages/pytg/sender.py", line 630, in command_alias
    return self.execute_function(command_name, *args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/pytg/sender.py", line 354, in execute_function
    raise e
  File "/usr/local/lib/python3.5/dist-packages/pytg/sender.py", line 351, in execute_function
    return result_parser(message)
  File "/usr/local/lib/python3.5/dist-packages/pytg/result_parser.py", line 55, in success_fail
    raise FailException(json.error_code, json.error)
pytg.exceptions.FailException: Error 38: 'can not parse arg #1' (command "[disable_preview] msg MY_ID_WAS_HERE 'Hello World!'\n")
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/lib/python3.5/subprocess.py", line 1072, in communicate
    stdout, stderr = self._communicate(input, endtime, timeout)
  File "/usr/lib/python3.5/subprocess.py", line 1700, in _communicate
    input_view = memoryview(self._input)
TypeError: memoryview: a bytes-like object is required, not 'str'
read: Connection reset by peer
root@odroid:/telegram# python3.5 testbot1/bot.py
change_user_group: can't find the user telegramd to switch to
bind: Address already in use
Traceback (most recent call last):
  File "testbot1/bot.py", line 10, in <module>
    sender.send_msg("MY_ID_WAS_HERE", "Hello World!")
  File "/usr/local/lib/python3.5/dist-packages/pytg/sender.py", line 630, in command_alias
    return self.execute_function(command_name, *args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/pytg/sender.py", line 354, in execute_function
    raise e
  File "/usr/local/lib/python3.5/dist-packages/pytg/sender.py", line 351, in execute_function
    return result_parser(message)
  File "/usr/local/lib/python3.5/dist-packages/pytg/result_parser.py", line 55, in success_fail
    raise FailException(json.error_code, json.error)
pytg.exceptions.FailException: Error 38: 'can not parse arg #1' (command "[disable_preview] msg MY_ID_WAS_HERE 'Hello World!'\n")

Here's also DEBUG log:

root@odroid:/telegram# python3.5 testbot1/bot.py
INFO:pytg:Starting Telegram Executable: "/telegram/tg/bin/telegram-cli -R -W -P 4458 -k /telegram/tg/tg-server.pub --json --permanent-peer-ids --permanent-peer-ids"
DEBUG:pytg.sender:Parsing raw: Argument help - <command> (needed)
DEBUG:pytg.sender:Sending command >[disable_preview]  help
<
INFO:pytg:CLI did not responde.
change_user_group: can't find the user telegramd to switch to
DEBUG:pytg.sender:Parsing raw: Argument help - <command> (needed)
DEBUG:pytg.sender:Sending command >[disable_preview]  help
<
DEBUG:pytg.sender:Socket Connected.
DEBUG:pytg.sender:All Sent.
INFO:pytg:CLI available.
DEBUG:pytg.sender:Parsing send_msg: Argument MY_ID_HERE - <peer> (needed)
DEBUG:pytg.sender:Parsing send_msg: Argument Hello World! - <text> (needed)
DEBUG:pytg.sender:Sending command >[disable_preview] msg MY_ID_HERE 'Hello World!'
<
DEBUG:pytg.sender:Socket Connected.
DEBUG:pytg.sender:All Sent.
Traceback (most recent call last):
  File "testbot1/bot.py", line 13, in <module>
    sender.send_msg("MY_ID_HERE", "Hello World!")
  File "/usr/local/lib/python3.5/dist-packages/pytg/sender.py", line 630, in command_alias
    return self.execute_function(command_name, *args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/pytg/sender.py", line 354, in execute_function
    raise e
  File "/usr/local/lib/python3.5/dist-packages/pytg/sender.py", line 351, in execute_function
    return result_parser(message)
  File "/usr/local/lib/python3.5/dist-packages/pytg/result_parser.py", line 55, in success_fail
    raise FailException(json.error_code, json.error)
pytg.exceptions.FailException: Error 38: 'can not parse arg #1' (command "[disable_preview] msg MY_ID_HERE 'Hello World!'\n")
INFO:pytg.sender:Quit Sending. Not allowing sending anymore.
WARNING:pytg.sender:Terminating currently sending request.
INFO:pytg.sender:Currently not Sending.
INFO:pytg:Closing Connections.
DEBUG:pytg:Closing sender.
DEBUG:pytg.sender:Already did quit Sending. Not allowing sending.
WARNING:pytg.sender:Terminating currently sending request.
INFO:pytg.sender:Currently not Sending.
DEBUG:pytg:Closing sender.
DEBUG:pytg.receiver:receiver thread existing: Not created.
INFO:pytg:Asking to CLI to stop.
DEBUG:pytg:Sender already stopped. Unable to issue safe_quit or quit to exit via socket.
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/lib/python3.5/subprocess.py", line 1072, in communicate
    stdout, stderr = self._communicate(input, endtime, timeout)
  File "/usr/lib/python3.5/subprocess.py", line 1700, in _communicate
    input_view = memoryview(self._input)
TypeError: memoryview: a bytes-like object is required, not 'str'
read: Connection reset by peer

Expected behaviour
A message should be sent to chat with my another account
Actual behaviour
Error happens!

Error 38: 'can not parse arg #1'  indicates that MY_ID_WAS_HERE was wrong in some way.
Best to start the CLI yourself (The debug output indicated /telegram/tg/bin/telegram-cli -R -W -P 4458 -k /telegram/tg/tg-server.pub --json --permanent-peer-ids --permanent-peer-ids) and try yourself how what argument you need.
After that failed, it is shutting down (everything after INFO:pytg.sender:Quit Sending. Not allowing sending anymore.) because your script is done.

As for the argument you can try @my_username, userid#1234, user#1234

Well, after running cli beforehand, script started working, thanks!

change_user_group: can't find the user telegramd to switch to #81


Move DocC and integration tests into separate CI pipelines

Motivation
Like many other projects, we have a soundness script which runs in CI. It started out with some fast policy and style tests but has grown over time. It currently has:

Check for broken symlinks
Check for unacceptable language
Check all files have a license headers
Run swift-format lint
Check DocC compiliation has no warnings
Run integration test

On my machine, (5) takes 11s and (6) takes 1m13s.
The soundness script should be cheap to run so as not to disclosure running it often—potentially even adding it to a precommit hook.
Removing (5) and (6) from the soundness suite means it takes 3s, which is more reasonable.
Modifications

Add integration-test to Compose file.
Add docc-test to Compose file.
Stop running DocC and integration tests in soundness.sh.

Result
Running soundness.sh takes 3s (was ~1m30s).
Test Plan
The following commands all succeed when run locally:

./scripts/soundness.sh
docker-compose -f docker/docker-compose.yaml run soundness
docker-compose -f docker/docker-compose.yaml run docc-test
docker-compose -f docker/docker-compose.yaml run integration-test

Notes
This PR should be used to stand up the new CI pipelines and shouldn't be merged
until we see them passing.

@yim-lee (same again please...) would you be so kind as to help us set up two additional pipelines for this project on the CI server? One for each of the following Compose targets:

docc-test
integration-test

Thanks in advance 🙏

@swift-server-bot test this please


JBDS-3778 2 methods: getSHA256(filename) & createSHA256File(filename)

JBDS-3778 2 methods: getSHA256(filename) & createSHA256File(filename)

This was working great w/ 100% sync methods until I tried it on something bigger than the cygwin.exe file. So, I've added a bunch of async methods but line 233 isn't working yet.
Need some help/suggestions how to make the async call properly do the isExistingSHA256Current() check and return true into the prefetch task on line 250.


Reference Webpacking docs in the FAQ

done
https://github.com/SAP/chevrotain/commit/db625074a61791352de6cb486f28dce2505c1558


update github workflows

libegl1-mesa does not exist in Ubuntu 24.04 which is now used by github actions servers, will see if libegl1-mesa-dev which does exist is a substitute. @almarklein also relevant for pygfx, wgpu . See https://github.com/fastplotlib/fastplotlib/actions/runs/11323476618/job/31486223347#step:5:12
update all our actions verisons

@clewis7 should be gtg, after you merge I can rebase the other 2 small PRs that are waiting

Thanks for the heads-up!


Update scala-library to 2.12.14

Updates org.scala-lang:scala-library from 2.12.11 to 2.12.14.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (2.12.11).
You might want to review and update them manually.
.github/workflows/ci.yml

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

labels: library-update, semver-patch, old-version-remains

Superseded by #84.


[hotfix][shell] Add stderr when 1 flink-dist*.jar cannot be resolved.

What is the purpose of the change
When adding jars to the /lib directory any extra jar files that match the pattern flink-dist*.jar provoke an error when trying to use BashJavaUtils to get JVM parameters and dynamic configurations in config.sh. Although niche, this can be difficult to debug because there is no error message to describe the issue.
We already print a useful error message if no flink-dist*.jar can be found at all. This pull request adds another error message when more than one flink-dist*.jar is found at this point.
Brief change log

Fix minor typo in README.md
Add error message for when more than one file matching flink-dist*.jar exists in /lib.
Actioned a few minor shellcheck issues on the lines changed.

Verifying this change
This change can be verified as follows:

./mvnw clean install -DskipTests -Dfast
cp flink-dist-scala/target/flink-dist-scala_2.12-1.16-SNAPSHOT.jar build-target/lib/
build-target/bin/start-cluster.sh
You should see the error message "[ERROR] Multiple flink-dist*.jar found in /path/to/lib. Please resolve."
rm build-target/lib/flink-dist-scala_2.12-1.16-SNAPSHOT.jar
build-target/bin/start-cluster.sh
The cluster should start successfully.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): No
The public API, i.e., is any changed class annotated with @Public(Evolving): No
The serializers: No
The runtime per-record code paths (performance sensitive): No
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: No
The S3 file system connector: No

Documentation

Does this pull request introduce a new feature? No
If yes, how is the feature documented? Not applicable

Thanks for the contribution @rudikershaw. LGTM, however as per the guidance, [hotfix] tag is mainly for documentation and typos. I understand this is a no-op change on the happy path, but please raise a Jira, rebase and add the Jira tag to the commit message.


Supply and demand Zones - rectangles

Hello I would like to have a possibility to draw rectangle on the chart.
I need this to simulate suply and demand zones.
To draw that kind of rectangle we should have possibility to enter parameters like this:

starting date of rectangle and price level
ending date of rectangle and price level
possibility to fiil this rectangle by colours.

Other functionality is scaling this rectangle when we zoome in or zoome out the chart.
https://www.mql5.com/en/charts/2798176/eurpln-h1-fxpro-financial-services

Any update about this feature? I am also looking at the same scenario. I wanted to draw rectangles on the x-y axis programatically. Also with real time data as the time axis moves this rectangles moves(shifts) as well..


Set page bottom padding to --page-spacing

Previously we would always leave 80px space before the page footer, but this is problematic with small viewport heights on projects page for example. I think it' ideal that we use --page-spacing which is already in use for spacing on top of the page.
The secondary-nav margin is also adjusted as I see no value why this shouldn't be the same value.

Why not 80px? I'm suitable to have more space.

Take for exampe project view on small viewport height:

In this case, a third of the height is wasted by this empty space.

Likely should use a new variable like --page-margin-y or --page-margin-bottom.

Take for example project view on small viewport height:

In this case, a third of the height is wasted by this empty space. With 16px, the space is used much more efficiently:

Not sure how common such viewport heights are but I often see this problem when I have DevTools open.

I personally don't think they are a waste. I like the first one. I like the relaxed feeling. Maybe --page-margin-bottom is a better name.


MissingPluginException

pubspec.yaml文件中29-36行
platforms:
# This plugin project was generated without specifying any
# platforms with the --platform argument. If you see the fake_platform map below, remove it and
# then add platforms following the instruction here:
# https://flutter.dev/docs/development/packages-and-plugins/developing-packages#plugin-platforms
# -------------------
some_platform:
pluginClass: somePluginClass
应该是 @qq326646683 你生成的吧，造成安卓和ios都无法引用这个插件了
应该改为
androidPackage: com.jinxian.flutter_tencentplayer
pluginClass: FlutterTencentplayerPlugin
@yxwandroid @qq326646683

谢谢提醒，0.9.0修复