craft.embeddedAssets.get() returns null for embed uploaded prior to 4.0 upgrade

Bug Description
We've just tested upgrading to V4.0, but now when we call craft.embeddedAssets.get() on a previously uploaded embed, the result is null. If we upload the same embed fresh, the call correctly returns an EmbeddedAsset model.
Steps to reproduce

Install Embedded Assets 3.2.0
Upload an embed (in our specific case this Vimeo video)
Upgrade to Embedded Assets 4.0

Expected behaviour
I would expect embeds uploaded prior to upgrading to 4.0 remain compatible with 4.0 codebase. If this can be resolved by
running the embeddedassets/refresh/all CLI command, then this should be specified in some sort of 4.0 upgrade guide.
Embedded Assets version
4.0.0
Craft CMS version
4.8.6

I've just tried running embeddedassets/refresh/all but it said, "0 embedded asset to be refreshed." Yet we have 27 embedded asset uploads.

If possible, could you please send one of the affected asset files to<EMAIL_ADDRESS>and we'll have a look.

Thanks for sending that @johndwells. I can confirm that the embedded asset is working as expected for me, including being detected by embeddedassets/refresh/all. Does it work for you if you import it into a different Craft install?

Odd. I've tried this a few times on this project and the results are the
same. We'll see if we can test this out on another install.
On Wed, Mar 27, 2024 at 6:08 PM Thomas Templeton @.***>
wrote:

Thanks for sending that @johndwells https://github.com/johndwells. I
can confirm that the embedded asset is working as expected for me,
including being detected by embeddedassets/refresh/all. Does it work for
you if you import it into a different Craft install?
—
Reply to this email directly, view it on GitHub
https://github.com/spicywebau/craft-embedded-assets/issues/254#issuecomment-2024129460,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABAXXTJSIVZNCJZPMCNNODY2NGOLAVCNFSM6AAAAABFLNIY26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUGEZDSNBWGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
▂
ONE DARNLEY ROAD
John D Wells
Technical Director
Unit 12, 39 Gransden Avenue
London, E8 3QA
+44 (0) 208 5259 292
onedarnleyroad.com
instagram https://www.instagram.com/onedarnleyroad/
linkedin https://uk.linkedin.com/company/one-darnley-road
twitter http://twitter.com/onedarnleyroad

I think we had some other issue going on that was causing this error. I'm closing, sorry to bother you!


[release-1.6] Fix ledger capacity size

This is an automated cherry-pick of #24529

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.6
3120150f6f4170607898627123b58e83def3fcf7
link
/test unit-tests_istio_release-1.6

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

/retest

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio_release-1.6
3120150f6f4170607898627123b58e83def3fcf7
link
/test integ-telemetry-k8s-tests_istio_release-1.6

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

/test integ-telemetry-k8s-tests_istio_release-1.6


Storage query performance optimization

fix #332

question: why we don't cache blockHash => Storage, and instead cache registry => Storage? It seems that we are repeating this deterministic query
const registry = await this.api.getBlockRegistry(u8aToU8a(blockHash));

question: why we don't cache blockHash => Storage, and instead cache registry => Storage? It seems that we are repeating this deterministic query
const registry = await this.api.getBlockRegistry(u8aToU8a(blockHash));

question: why don't we cache blockHash => Storage, and instead cache registry => Storage? It seems that we are repeating this deterministic query (is this line actually not deterministic?)
const registry = await this.api.getBlockRegistry(u8aToU8a(blockHash));

Also, do we have a limit for the cache? It can grow very big in long term

Because the registry only changes when the chain version is upgraded. This will not be very frequent.
apiAt creates a new object every time, which can cause a significant performance overhead. https://github.com/polkadot-js/api/blob/master/packages/api/src/base/Init.ts#L120


Proposal: Encode and read emit-affecting compiler options in declaration files

TL;DR
Put emit-affecting options at the top of .d.ts files like
// @esModuleInterop: true
// @module: commonjs
// @preserveConstEnums: true
// @useDefineForClassFields: true

so we can know what’s going on in JS files when we read in .d.ts files from external dependencies.
Super basic background
Type checking is designed to reason about what your JS code will do at runtime. When you change a compiler option that affects what JS code gets emitted, there is often a corresponding change to type checking behavior. For example, when emitting CommonJS modules, the esModuleInterop changes the JS emit for default imports so they can be used in more situations. Because of this emit change, a compiler error can go away:
import express from "express";
//     ^^^^^^^
// This module is declared with 'export =', and can only be used
// with a default import when using the 'esModuleInterop' flag.

Here, the compiler knows that the JS generated for the default import will not work with the "express" module. But if we enable esModuleInterop, the generated JS changes in a way that makes it compatible, and consequently the type checking error goes away. The presence or absence of the error is driven by accurate knowledge of the runtime JS.
The problem
When a project consumes a type declaration file, say from an external dependency, the declaration file is supposed to contain everything the compiler needs to know about the JS file it represents—no more and no less. But declaration files typically don’t change in any way as a result of modifying emit-affecting settings. The compiler makes assumptions about the contents of the corresponding JS files based on the compiler options of whatever project consumes the declaration files. Since type checking behavior is driven by knowledge about the runtime behavior of JS files, type checking can be incorrect when consuming libraries compiled with emit-affecting options different from the consuming project’s options.
Returning to the esModuleInterop example, this issue has led to conventional wisdom like “libraries should not use esModuleInterop.” The idea is that if a library uses esModuleInterop to silence an error on a default import like the one shown above, then publishes type declaration files containing that default import, then every user who consumes those declarations must also enable esModuleInterop. This conventional wisdom is probably the best we can do currently, but it’s also deeply flawed. Compiling without esModuleInterop also allows libraries to write (categorically incorrect!) code that produces errors when compiled with esModuleInterop:
import * as express from "express";
export type ExpressArgs = Parameters<typeof express>;
//                                   ^^^^^^^^^^^^^^
// Type 'typeof e' does not satisfy the constraint '(...args: any) => any'.
//  Type 'typeof e' provides no match for the signature '(...args: any): any'.(2344)
//
// index.d.ts(1, 1): Type originates at this import. A namespace-style import cannot be called
// or constructed, and will cause a failure at runtime. Consider using a default import or
// import require here instead.

The issue is bidirectional; neither value of esModuleInterop guarantees that consumers will not have to adopt the setting used by the library.
The problem is not unique to esModuleInterop; it applies to nearly all emit-affecting compiler options that result in a corresponding checking change. Other particularly relevant ones that come to mind are:

useDefineForClassFields
preserveConstEnums
module

Other emit-affecting options are either not semantically meaningful (removeComments) or tend to be relevant only in implementation files (downlevelIteration, jsxImportSource).
Proposal
I suggest encoding these relevant options into declaration files when emitting them, and reading and respecting them during checking. I’m not particular about syntax, but it needs to be human-writable so it can be used on DefinitelyTyped. Both the parsing and likely much of the checking infrastructure could be reused from https://github.com/microsoft/TypeScript/pull/49886, so I would advocate for reusing that syntax:
// @esModuleInterop: true

These directives would be unconditionally added to the top of all emitted declaration files. Any directive-controllable options that are not set with a directive should fall back to today’s behavior (use the consuming project’s options). Note that this means we cannot assume a default value for directives and elide ones that would be redundant with that default, since no directive means “use the user’s config,” which could have a value that disagrees with whatever default we set. So all options we think are relevant should always be encoded in declaration file emit.
What about project references?
Project references on the command line consume declaration files, while in TS Server, they use the referenced project’s source .ts files. The checker may need some changes to ensure that the value of directive-controllable options are read from the referenced project’s tsconfig.
People hand-writing definitions will mess it up!
The potential for messing up hand-written declarations is already so high that adding one more degree of freedom doesn’t move the needle at all. Careful checks will need to be implemented on DefinitelyTyped. Everyone else is on their own. I believe this will solve more problems than it creates.
Does this conflict with #49886?
I don’t think so. I suggest making such directives errors in implementation files, which may help preserve that space for #49886 if we find a way to make it viable performance-wise. Currently, none of the options I identified as interesting are targeted in #49886. If one of them was able to be overridden in an implementation file in the future, the directive would just have to be emitted as-is to the declaration file.
Will this affect performance?
I hope that the fact that this targets much fewer options than #49886, and ones that are checked somewhat less often than strictness flags, means the performance penalty will be negligible. But experimentation will be needed.
Alternatives
You can imagine a lot of ways to put something in a declaration file to encode extra information about imports, class fields, const enums, and others. I’m open to discussing very different syntax and potentially tackling a narrower scope than what I’ve discussed (I’m mostly invested in fixing esModuleInterop at the moment), but I can’t think of any way to do it without changing declaration file emit in some way. I think a file-level directive has merit because I think it can leverage existing work from #49886, and the settings cannot be changed more granularly than file-level anyway.

Related: #52779, some const enum ones, surely others

Just to reiterate what I've said that'll end up in the design meeting notes, I don't really like the idea of encoding this in comments just because we fear a break. This is definitely semantic information, and should be treated appropriately. Moreover, any "syntax" (comment or otherwise) people are going to try and use/abuse in non-declaration files. It would be helpful if we could actually error on that case, which would be troublesome for a comment (erroring on a comment never feels right - it's a decent indicator it shouldn't have been a comment if it could be avoided).
IMO, it would also be useful to be able to say "resolve this import as though it had an interop helper" for any type-only import, not just declaration file ones. Like, if you write
import type mod from "x" in a non-esModuleInterop project, but you want the interop import behavior (because, eg, that's what "x"'s docs say you should do), it's pretty reasonable to say that you want the helper behavior applied to the import. In real JS, you could always explicitly tslib.__importDefault(mod) (or, more likely, hardcode mod = mod.default) as a one-off, but there's no type equivalent (mostly because type constructors can't transform namespaces easily).
I'd be much more comfortable with an explicit syntax on the import (eg, a with attribute) that we can allow on all non-implementation imports. We already have tools like downlevel-dts and typesVersions to make changes like this more palatable.


Possible use of uninitialized memory in assembler function

This error seems harmless from code inspection, but might be worth fixing.
https://build.chromium.org/p/tryserver.webrtc/builders/linux_msan/builds/16972
[ RUN      ] VideoProcessorIntegrationTest.Process0PercentPacketLossH264
==7018==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x7433e9 in ?? third_party/openh264/src/codec/encoder/core/src/svc_encode_mb.cpp:271:9
#1 0x768fe8 in ?? third_party/openh264/src/codec/encoder/core/src/svc_encode_slice.cpp:470:3
#2 0x72b5c3 in WelsMdIntraSecondaryModesEnc third_party/openh264/src/codec/encoder/core/src/svc_base_layer_md.cpp:2040:3
#3 0x72b5c3 in WelsMdIntraMb third_party/openh264/src/codec/encoder/core/src/svc_base_layer_md.cpp:961:0
#4 0x769e58 in WelsISliceMdEnc third_party/openh264/src/codec/encoder/core/src/svc_encode_slice.cpp:552:5
#5 0x774a78 in ?? third_party/openh264/src/codec/encoder/core/src/svc_encode_slice.cpp:936:24
#6 0x6b2db4 in WelsEncoderEncodeExt third_party/openh264/src/codec/encoder/core/src/encoder_ext.cpp:3736:29
#7 0x80ffd7 in EncodeFrameInternal third_party/openh264/src/codec/encoder/plus/src/welsEncoderExt.cpp:405:35
#8 0x80fca2 in ?? third_party/openh264/src/codec/encoder/plus/src/welsEncoderExt.cpp:382:35
#9 0xbf1b84 in Encode webrtc/modules/video_coding/codecs/h264/h264_encoder_impl.cc:356:36
#10 0x5b074c in ProcessFrame webrtc/modules/video_coding/codecs/test/videoprocessor.cc:229:39
#11 0x574b4a in ProcessFramesAndVerify webrtc/modules/video_coding/codecs/test/videoprocessor_integrationtest.cc:456:24
#12 0x5734d9 in TestBody webrtc/modules/video_coding/codecs/test/videoprocessor_integrationtest.cc:613:3
#13 0x96e761 in HandleExceptionsInMethodIfSupported<testing::Test, void> testing/gtest/src/gtest.cc:2458:12
#14 0x96e761 in Run testing/gtest/src/gtest.cc:2474:0
#15 0x970b8f in Run testing/gtest/src/gtest.cc:2656:11
#16 0x972279 in Run testing/gtest/src/gtest.cc:2774:28
#17 0x991f3d in RunAllTests testing/gtest/src/gtest.cc:4647:43
#18 0x990c94 in HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool> testing/gtest/src/gtest.cc:2458:12
#19 0x990c94 in Run testing/gtest/src/gtest.cc:4255:0
#20 0x5b4883 in RUN_ALL_TESTS testing/gtest/include/gtest/gtest.h:2237:46
#21 0x5b4883 in main webrtc/test/test_main.cc:49:0
#22 0x7f166a294f44 in __libc_start_main /build/eglibc-oGUzwX/eglibc-2.19/csu/libc-start.c:287:0
#23 0x4297d8 in _start ??:?
Uninitialized value was created by an allocation of 'aMax' in the stack frame of function '_ZN7WelsEnc12WelsEncRecUVEPNS_22TagWelsFuncPointerListEPNS_5TagMBEPNS_10TagMbCacheEPsi'
#0 0x742100 in ?? third_party/openh264/src/codec/encoder/core/src/svc_encode_mb.cpp:246:0
@henbos did some initial analysis.

In several places of svc_encode_mb.cpp local uninitialized variables aMax (arrays) is used when calling function pointed to by pfQuantizationFour4x4Max. This is set here and here to WelsQuantFour4x4Max_c or WelsQuantFour4x4Max_sse2.
A range of aMax is passed by address and is set by these functions. The memory sanitizer of Chromium bots warn that this is use of uninitialized variables. If there isn't a bug in the code, calling pfQuantizationFour4x4Max is doing just that though: initializing aMax.

Hi @henbos , you are right, aMax is initialized (or set) in pfQuantizationFour4x4Max. It is not a bug. Can the warning be removed by other methods?

If no update, will close this days afterwards.

@henbos the temporary fix (that allowed us to land twas to turn off assembler if ASAN is active. This seems like a sad thing to do (if there are memory errors, ASAN won't catch them).

@alvestrand I assume this above should be Warning level in Valgrind, not Error, seen as "==7018==WARNING: MemorySanitizer: use-of-uninitialized-value"
We can check every warning carefully in ASAN tests. Errors in valgrind should be blocked surely.
As you know, the module is used with very high frequency in encoding module. Given the guarantee the usage is safe, make unnecessary initialization would affect the encoding speed.


store status in elasticsearch

We should store the status of each run in ES. Today, results and metadata are stored there however different tools have different index structures.
One example is snafu (benchmark-wrapper) has a concept of a run_id which allows the user to add some descriptive string to each run, where kube-burner has no concept of a run_id. I am sure there will be other things we integrate that suffer the same issue. We could add run_id to kube-burner, but I feel it would be better for us to encode run specific details in our own index.
{
 "timestamp" : "date",
 "platform" : "GKE,OpenShift,EKS,AKS",
 "k8version" : "version",
 "kernel" : "[ list of kernels? or just a single kernel assumption is that all nodes are the same kerenl ]",
 "benchmark" : "what ran",
 "uuid" : "id from kube-burner or benchmark-wrapper",
 "num_nodes" : "number of nodes"
 "region" : "what region or location the cluster was deployed"
 "state" : "pass/failed"
}

PR #25 addresses this... I should of tagged it in the PR.


Overwrite to_info_dict() method in Context and command classes

The click context object has a method .to_info_dict() that's useful to go through the whole CLI structure, for example to write documentation.
It would be good to have an equivalent with cloup, so that all the other info cloup adds (eg. Aliases and help) can be exposed in the same way

Hi! This method seems to exist to generate a JSON representation of the CLI to be consumed by external tool. Do you know any of these external tool that make use of it? Note that this method not really useful for traversing the CLI: by converting to dict, you lose type information and autocomplete, which can only worsen your DX.
Anyway, you're welcome to contribute!

This one does, which creates an auto-complete for Fig: https://github.com/withfig/autocomplete-tools/blob/main/integrations/click/click_complete_fig/fig.py
But as I played with it yesterday (after starting this thread), I came to the same conclusion and converted to traverse the click/cloup object model instead. Really not complex, and in 10 min, the conversion was done and now I also have access to all of cloup's info...

I'll keep this open for whoever wants to contribute.


Fixes #20: Pass access_token on after uploads.post()

The access_token was not passed on to subsequent calls of _check() after
a file upload via uploads.post(). This caused authorization issues if
the token was not maintained in the central strava_config file but passed
in explicitly.

I think the better choice would be to not use ES6 features that require babel or polyfills to run with 0.12.x to keep the library as lean as possible.
If you agree, I'm more than happy to replace the arrow functions.
As far as I know, 0.12 is in maintenance until sometime late 2016. After that, it may be a good idea to drop support for this node version with a new major version of the library and refactor the library to use more ES6 syntax. This would definitely make the code more readable and concise.

I'm all for that - when the respective branches have been edited to pre ES6 compliance I'll continue w/ the merge+publish

Replaced the arrow functions with regular functions. The unit tests are now running fine all the way down to v0.10.x.
Also added a Promise polyfill to allow using promises in the unit tests without breaking compatibility with older node versions.


Rename email field when viewing users.

For Feature Requests
Desired Feature: Theres an annoying auto-fill "bug" in Safari (and likely other browsers), where the email address for users gets set to whatever email you use normally in the browser, and if you don't notice, it tries to set the user's email to your auto-filled one.
Would be nice if the field could be renamed to something like current_email, or somehow disable auto-fill on that field.

Sounds more like an extension is doing this? In  Firefox, Google Chrome and Microsoft Edge I don't see this? I know for me LastPass will sometimes do things like this. @DaneEveritt

Doesn't appear to happen in Chrome, Firefox, or IE in v0.29.3. Can likely be closed, given the age of the issue.

Thanks for testing  confirming @alexmannuk and @Shackelford-Arden.
Since this has not been reported since this issue was created 3 years ago I'll close this off. If it remains problematic and re-producible feel free to open a new issue, referencing this one.


Update metrics.md

Add new Authentication Operation - ExchangeTeamsUserAccessToken

@jutik0 : Thanks for your contribution! The author(s) have been notified to review your proposed change. @probableprime

#sign-off

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @probableprime

@GrantMeStrength  - Can you review this PR?
Unable to locate another reviewer, but feel free to reassign if need be.
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

I noticed now that this didn't go against the -pr repo, I'll restart the changes..


[WIP] Initial take on a lab plugin.

Still have lots of errors, but we can start working on them now
that the javascript is loading. This is definitely still a work in progress.

woot !

hi, is it suppose to work with latest jupyterlab/ipywidgets ? I don't succeed but I may have done something wring

No, this was using an older iteration of the JupyterLab extension system.

any progress ?

Unfortunately we didn't get a chance to work on it while at JupyterCon.

Closing in favor of #21.


[CARBONDATA-3720] Support alter table scenario for new insert into flow

Why is this PR needed?
Currently, the rearrange logic is based on schema ordinal.
For alter table drop and add columns with/without partition, schema ordinal based re arrange may not work as index will be outside the projection size. This logic become complex to handle.
Hence don't use schema ordinal for rerrange, implemented a position map based rearrange.
What changes were proposed in this PR?
implemented a position map based rearrange.
Does this PR introduce any user interface change?

No

Is any new testcase added?

No

Build Failed  with Spark 2.4.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/404/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2105/

Build Failed  with Spark 2.4.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/408/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2109/

Build Success with Spark 2.4.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/415/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2116/

Build Success with Spark 2.4.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/434/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2134/

Build Success with Spark 2.4.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/443/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2143/

Build Success with Spark 2.4.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/452/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2153/

@jackylk : Handled the comments. Build passed. PR is ready.

LGTM


Failed to authenticate using the given account Credentials

i enter the right credentials but the display the error ( Failed to authenticate using the given account Credentials)

Do you have 2FA enabled?

Do you have 2FA enabled?

no

@Rishikant181

Did you try enclosing you credentials in double quotes like this?: rettiwt auth login "email" "username" "password"

Did you try enclosing you credentials in double quotes like this?: rettiwt auth login "email" "username" "password"

no

Try it and see if it works

i do it with "" and without "" but the same result

@Rishikant181 it is diplay it

Try logging in to Twitter from a browser using the same account, then try rettiwt auth again.

Try logging in to Twitter from a browser using the same account, then try rettiwt auth again.

i already try that

the credentials are 100% right

@Rishikant181

Okay I have a temporary workaround:

Open your browser and go to twitter/X.
Open browser developer tools
Navigate to Applications->Cookies (for Chrome) or Storage->Cookies (for Firefox)
Copy the values of the 4 fields: auth_token, ct0, kdt, twid. Store them temporarily somewhere
Open NodeJS in a terminal and execute the command: auth_token=<auth_token_value>;ct0=<ct0_value>;kdt=<kdt_value>;twid=<twid_value>
The output  string is your API_KEY

I'll be trying to reproduce the error. So far, I couldn't.

Duplicate of #493

@Char0nDev All updates regarding this issue will be tracked at #493

@Char0nDev The earlier posted code was incorrect, please check again.


"BOLDEȘTI-SCĂENI" is listed in the drop-down menu

Description:
"BOLDEȘTI-SCĂENI" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "BOLDEȘTI-SCĂENI" in the search bar.
Expected results
The location is listed in the drop-down menu as "Oraș BOLDEȘTI-SCĂENI, PRAHOVA (BOLDEȘTI-SCĂENI)"


Can't upload to test site via Twine

My pypirc looks like (with other servers and username/password omitted)
[distutils]
index-servers =
   pypitest

[pypitest]
repository=https://test.pypi.org/legacy
username=****
password=****

When I try to run the following twine command
twine upload -r pypitest myPackage.whl

I get this error
RedirectDetected: "https://test.pypi.org/legacy" attempted to redirect to "https://test.pypi.org/legacy/" during upload. Aborting...

I am using the latest version of twine as of yesterday and am on High Sierra.

Hello, please make sure to check that the name is spelt correctly ".pypirc, and change the heading of your pypi test to just test, like this:
[distutils]
index-servers =
    pypi
    test

[test]
repository:https://test.pypi.org/legacy/

If that still doesn't work, check back. Thanks

Take a look at https://packaging.python.org/guides/using-testpypi/#setting-up-testpypi-in-pypirc
The correct URL is https://test.pypi.org/legacy/ (with a trailing slash). Does changing it in your .pypirc fix your issue?

@AaronV77 The header doesn't need to change, it can be whatever they want, as long as it's the same as what they're passing via -r.

Yep adding the trailing slash worked. Thank you!


add multiplication with vectors method

This seems to fix an oversight. Previously, there was no specialized *(::BlockDiagonal,::AbstractVector) method, such that this combination was handled by some generic LinearAlgebra method. Not surprisingly, this yields a giant performance gain.
I have kept the changes simple and minimal. There is quite some code duplication with the corresponding *(::BlockDiagonal,::AbstractMatrix) method, which can be reduced by means of a helper function and using selectdim(y, 1, st:ed) if desired.

🎉 Thanks a lot! LGTM

There is quite some code duplication with the corresponding *(::BlockDiagonal,::AbstractMatrix) method, which can be reduced by means of a helper function and using selectdim(y, 1, st:ed) if desired.

That'd be a great follow-up PR, if you have time for that?
For this PR, would you mind posting a simple benchmark giving a quick illustration of the speed-up (it'd be helpful when one day making proper benchmarks for the package #19)
And please bump the package version -- will tag a new release straight away!

Here is a quick benchmark, slightly adopted from the test suite:
using BlockDiagonals, BenchmarkTools
N1, N2, N3 = 30, 40, 50
N = N1 + N2 + N3
b1 = BlockDiagonal([rand(N1, N1), rand(N2, N2), rand(N3, N3)])
a = rand(N)
@benchmark $b1*$a

Master:
BenchmarkTools.Trial:
  memory estimate:  4.41 MiB
  allocs estimate:  43921
  --------------
  minimum time:     1.702 ms (0.00% GC)
  median time:      1.852 ms (0.00% GC)
  mean time:        2.195 ms (11.26% GC)
  maximum time:     7.055 ms (44.17% GC)
  --------------
  samples:          2270
  evals/sample:     1

This PR:
BenchmarkTools.Trial:
  memory estimate:  2.63 KiB
  allocs estimate:  9
  --------------
  minimum time:     1.121 μs (0.00% GC)
  median time:      1.227 μs (0.00% GC)
  mean time:        1.633 μs (4.68% GC)
  maximum time:     180.318 μs (97.38% GC)
  --------------
  samples:          10000
  evals/sample:     10


Fix UIBarButtonItem onTap animation

Since it is a custom button, fading effect on button tap is removed. This adds back onTap fading effect.

Travis failed for some certificate problem. My change didn't cause this :)

Actually I am working on it already. I have made changes also. Give me half an hour, I will update the repo and publish pod as well.

I just pushed all my changes. They are available in .
I will be closing this PR in favor of those changes.
Thank you for your contribution.


Specify to_parquet keys explicitly to ensure ordering

Previously we used delayed functions here, which don't order things in
an obvious way.  Our task ordering heuristics use keys as tie-breakers
so they were performing sub-optimally when writing parquet data to disk
In the future, when convenient, we should endeavor to make our keys look
like the following:
('name-hash', int)

[ ] Tests added / passed
[ ] Passes flake8 dask
[ ] Fully documented, including docs/source/changelog.rst for all changes
and one of the docs/source/*-api.rst files for new API

I will probably wait on #3271 to deal with this


Add Application.getSettings() API

This adds a new getSettings API to Application that can be used to get all the configured options with their defaults.
This can be helpful when debugging to ensure options are being set/interpreted correctly.

@kevinsawicki I left a couple comments here ICYMI


Asm temp marshmallow fix

Summary of Changes
Include a summary of changes then remove this line
Tests
What tests did you add or modify and why? If no tests were added or modified, explain why. Remove this line
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes make test

I think https://github.com/amundsen-io/amundsenmetadatalibrary/pull/286/files obviates this? (pls reopen if not)

yeah this was a temporary thing never meant to be merged sorry


I hava installed powertoy 15.01，but i did not see the launcher and the keyboard manager specs on setting page.

I can see other specs ,but the new features specs don't display.
Environment
Windows build number: 1909[run "ver" at a command prompt]
PowerToys version: 15.01
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce

Expected behavior

Actual behavior

Screenshots

those were added in .18 release


Auto save and load appearance parameters

Add the ability to automatically save the current map appearance parameters when the application is closed and attempt to load them when the application is next opened. Could be saved in a temp directory and silently continue loading defaults if there is a problem loading the files or they are not present.

Implemented as part of https://github.com/Killeroo/SC4Cartographer/pull/16


[Bug] Controls not connecting with UI

Describe the bug

Updating a control does not update the component
When creating a story with preset args, it adds a duplicate control

More specifically in the story/component below, the "color" component is causing the issues.
Steps to reproduce the behavior
Here's the story.
<script>
    import { Meta, Template, Story } from '@storybook/addon-svelte-csf';
    import Badge from './badge.svelte';

    const meta = {
        title: "Badge",
        component: Badge,
        argTypes: {
            children: {
                control: {
                    type: 'text',
                },
                defaultValue: 'Hello world',
                name: 'children',
                type: { name: 'string', required: true }
            },
            size: {
                control: {
                    type: "select",
                    options: ['primary', 'secondary', 'error', 'highlight', 'warning', 'success'],
                },
                name: 'color',
                description: 'This is the color of the badge',
                type: { name: 'string', required: false }
            },
        },
     };

</script>

<Meta {...meta} />

<Template let:args>
  <Badge {...args}>{args.children}</Badge>
</Template>

<Story name="Default"/>

<Story name='With color' args={{color: 'primary'}} />

And here's the component.
<script lang='ts'>
    type Color = 'primary' | 'secondary' | 'error' | 'highlight' | 'warning' | 'success'
    export let color: Color = 'secondary'

    const COLOR_MAP: Record<Color, string> = {
        primary: 'bg-primary',
        secondary: 'bg-secondary',
        // etc…
    }
</script>

<span class={`rounded ${COLOR_MAP[color]} font-semibold text-xs px-2 py-1`}>
    <slot></slot>
</span>

Expected behavior

Updating a control via the UI updates the component
Setting a default value does not add an additional control

Screenshots and/or logs
Here's the storybook: https://ui-svelte-9adyxhbbc-nick-mazuk.vercel.app/?path=/story/badge--default
Environment

OS: macOS 11.2
Node.js version: v12.17.0
PNPM version: 5.18.8
Browser: Brave
Browser version: 1.21.77

Additional context
I am brand new to Storybook, so it's possible that I'm just missing something obvious that I couldn't figure out. Though it doesn't look like this package is documented anywhere.

I'll check that!
Does it works with the "standard" (js) CSF ?

And why is the property called 'size' and not 'color' ?

That was it. Changing it from size to color fixed everything! Thanks for spotting that and sorry about the hassle.


Version of govuk-prototype-kit downloaded is based on the version number in this repo

What
Change the download route to point users to the latest release archive, rather than relying on the version number in the package.json file of this repo.
Why
Currently the code to create the download link is a legacy from when this site was part of the prototype kit repo. Now the two have been split we probably want a different release process for this site, and to be able to make a release of the kit without having to update this repo.
Who needs to work on this
Developer
Who needs to review this
Developer
Done when

[ ] We can release a new version of the kit and the docs site points users to it without making any changes to this repo

in v13 there is no download link, closing


Create target folder if it doesn't exists

Can we have an option to create the target folder if it doesn't already exists?
The thing is, I rotate my backup storage and at each rotation, the backup storage is wiped clean.
When the target folder doesn't exists, this add on writes to the root of the share instead.
Thank you!

Is there a reason why you're skipping the pre-checks? Otherwise the addon would stop immediately if the target directory is not found instead of writing to the root.
I think I could change that to at least try to create the target directory if it does not exist. However, I would only add that to the pre-checks as this is the place where the configuration is checked.

Thanks for getting back.
Just checked, I'm not skipping the pre-checks, it is disabled.

So then this means that the target directory exists when you start the addon, but somewhere between startup and the backup you delete the directory. Actually that's not really how this addon should be used.
Is it an option for you to configure a second share with the full path to your desired folder and leave target_dir empty?

Ok sure, I take it you want to be coding to a strict set of mechanical logic.
In that case, why copy backup to the root when target no longer exist? I mean, strictly speaking, it should just fail right?
I feel that samba is a network resource and they are prone to being unavailable. I guess the question is, what should the software do when target is unavailable, and when resource itself is unavailable.

In that case, why copy backup to the root when target no longer exist? I mean, strictly speaking, it should just fail right?

That's the behavior of smbclient. I wasn't aware of that to be honest.

If I may ask, what is the concern to check and create the target_dir before each backup?

I'll think about it. Probably you're right and I can adapt the current functionality.

That's the behavior of smbclient. I wasn't aware of that to be honest.

Thanks, that is new to me too... strange why they did it this way. I'm digressing, but imagine cp bigfile /non-existent/path/ and it goes to /.
Thank you for the consideration!


Different stats because of different sources.

Stats api give different values comparing to gender api (Confirmed number is different from( male+ female cases ), maybe because we are using different data source for stats?
What about using same source as /wilayas api and get stats out of it?

what do you think @sohaibafifi ?, if you agree i can open a pr.

also maybe better if we include gender api into stats api?, to have one endpoint for general stats?

What about using same source as /wilayas api and get stats out of it?

Yes we can, using another endpoint. I noticed that the sum between wilayas is wrong!

Here is the endpoint

Cool, then i will create a pr to update stats api.
This new endpoint will just give us le cumul which is confirmed cases. so I will use /wilayas api to get deaths/ recovered?, what do you think?
btw sum of death/recovered is same as actual stats api.


would you please open source your ssdmobilenet pretrained model?

dear friend ,thanks for your open source,  i am trying to recurrent the mobilenetv2 ssd, so would you please open source your ssdmobilenetv2 pretrained model  './pretrain_model/mobilenetv2_1.0-0c6065bc.pth',  need your help please

@jsnoc Sorry for reply so late.
I download the MobileNet-V2 pre-train model from d-li14's work. This is the repo d-li14/mobilenetv2.pytorch,
The pre-train model is mobilenetv2_1.0-0c6065bc.pth.
Enjoy it!

awesome！！！


Smarter Stream Creation

Right now the client always checks if the stream is available and creates if needed - I think this should be opt-in behavior.

I think the auto-stream provisioning could be an optional parameter, rather than forced.
And it depending on that option there should be:

Provisioning missing channels on boot
Ensure that all channels are provisioned

I think it will need to be "lazy" if enabled with the way watermill subscriptions work but it should be easy to make provisioning optional.

Keep this in mind https://github.com/nats-io/nats.go/issues/874

@zdraganov i made this opt-out through configuration for now.  The underlying nats client mostly supports it (see above issue).  As I work w jetstream more I'm sure I will develop opinions about how to do it better, it's probably a different option for publish than subscribe eventually.


Avoid quadratic memory blowup in TermDag::to_string

Zulip
Current version of TermDag::to_string caches a string for each DAG node. This results in quadratic memory blowup (these strings contain each other) which prevents vector benchmark from running on my machine.
This PR fixes the issue by building one result string and using string ranges to refer to already built substrings. Memory consumption should now be proportional to the length of the string. This also avoids quite a few allocations.
With these changes I am finally able to run the benchmark (it used to OOM for me). In conjunction with the other PR, full running time is now under a second.

For reference, generated string is 889MB! We most definitely don't actually want to compute it!


Add an option to use custom domain when copying Blob URLs

Storage Explorer Version: 1.14.0
Build: 20200616.5
Branch: rel/1.14.0
Platform/OS: Windows 10/ macOS Catalina / Linux Ubuntu 18.04
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Expand one storage account -> Blob Containers.
Create a blob container -> Upload one blob.
Right click the blob -> Check the 'Copy URL' action on its context menu.

Expect Experience:
Display a sub-menu for 'Copy URL' action.
Actual Experience:
No sub-menu displays for 'Copy URL' action.

@v-xianya the submenu only appears if there is a custom domain configured for the storage account. Is there a custom domain configured for the account you were using to test?

Hi @MRayermannMSFT Thanks for your clarification. We tried to figure out configure a custom domain for one storage account but still no idea how to create a storage account with a custom domain. Is there an storage account can be provided?🙃

@craxal will help y'all set something up.

Hi @craxal Thank you for the help.
Also there are two things need to confirm with you😀 Are these expected?

For one new created blob container, It requires a refresh to show the 'Custom Domain'.
For one new created blob container and its property 'Custom Domain' already shows, then upload one blob to it. It need to reopen the blob container to make the sub-menu of Copy URL shows.

@v-xianya

Hi @craxal Thanks for the updates

Yes, It needs to refresh 'Blob Containers' node to show the 'Custom Domain' for one new created blob container.
(New bug: 3110)


import error

ImportError: cannot import name pesq

You named your file as pesq.py change it to something else and it should work!


Update the sample to use the new Text to Speech

Hey @nfriedly can you please update this to use the GA version of Text to Speech

Yep, I'll get it updated.


newer values replaced by old ones if comparator returns false

New values should never be replaced by old ones ($timestamp), even if comparator returns true

for reference, @jhusain filed this issue after our conversation about set improvements, specifically set now respects time stamps on values

I assume this is fixed since new set has this issue fixed.


Enhancing the css styling of the scroll back button by adding a timeline on it for ALL pages.

Enhancing the css styling of the scroll back button by adding a timeline on it for ALL pages.
issue no. : #1201
https://github.com/user-attachments/assets/62603181-b9c1-4a2c-9030-bd6cf341c262

can you change theme back to the older one.

can you undo the change. and raise new PR

@HimangshuSharma01


better defaults - import maps for browsers

Improving the defaults would be a great deal.
First - add as a defaults all self library import maps for the browser based configurations.

Fixed, will be released next version.


Replaced serverName with shortHashedServerName in haproxy configs if ...

…sticky options are used, so as not to leak information about hostnames/ports

Looks good, thanks!


"preventInteractionOnTransition = false" not working with loop

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 4.3.5

Platform/Target and Browser Versions: Chrome on macOS

What you did
Initialized a looped slider with preventInteractionOnTransition = false.
Expected Behavior
Clicking on the navigation while the slide changes (for example clicking the "next" button twice) should work and change the slide according to the clicks.
Actual Behavior
Clicking has no effect during the slide transition and only works again after the transition has finished.

This is still a problem. It can be observed in the demos: the non-looped demos change slides as soon and often you click the next or previous button—the looped demo only responds again when the last slide transition has finished.

This is by design in loop mode


iOSexample aria1 aria5

Marc, please checkout the iOS_example-ARIA1_ARIA5, and if everything look okay please merge them to the remove master. <Thank you!>

Marc, please review the branch iOS_example-ARIA1_ARIA5. And if everything look fine. please merge it to remove master

Hi Marc, the are some unresolved conflicts that I need help merging. Thanks, Jack

Closing due to merge conflicts - test results pulled in via a different branch


Added Good First Issues Tool In The Open Source Tools Subcategory

Closes #1330
Changes proposed

Added the good first issue tracker tool in the opensource tools subcategory.

Screenshots

Note to reviewers

hey @rupali-codes , can you review this? thanks!


TestsetGenerator with custom LLM : 'ChatOpenAI' object has no attribute 'set_run_config'

Hi, I'm trying to use the TestsetGenerator to generate a dataset from Langchain document.
Here's my code:
from langchain_openai import ChatOpenAI
from langchain_community.embeddings import HuggingFaceEmbeddings
from ragas.llms.base import LangchainLLMWrapper
from ragas.embeddings.base import LangchainEmbeddingsWrapper
from ragas.testset.generator import TestsetGenerator
from ragas.testset.evolutions import simple, reasoning, multi_context
from langchain.document_loaders import TextLoader

loader = TextLoader(doc_filename)
documents = loader.load()

llm_api = ChatOpenAI(
    model=model,
    openai_api_key=key,
    openai_api_base=base,
)

embeddings = HuggingFaceEmbeddings(
    model_name=model_name_embedding,
)

generator_llm = LangchainLLMWrapper(llm_api)
critic_llm = LangchainLLMWrapper(llm_api)
embeddings_model = LangchainEmbeddingsWrapper(embeddings)

splitter = RecursiveCharacterTextSplitter(chunk_size=250, chunk_overlap=20)
keyphrase_extractor = KeyphraseExtractor(llm=generator_llm)

docstore = InMemoryDocumentStore(
    splitter=splitter,
    embeddings=embeddings_model,
    extractor=keyphrase_extractor,
)

generator = TestsetGenerator(
    generator_llm=generator_llm,
    critic_llm=critic_llm,
    embeddings=embeddings_model,
    docstore=docstore
)

testset = generator.generate_with_langchain_docs(documents, test_size=10, distributions={simple: 0.5, reasoning: 0.25, multi_context: 0.25})

With this code I get the following error: "AttributeError: 'ChatOpenAI' object has no attribute 'set_run_config'.
It happens here:
in Evolution.set_run_config(self, run_config)
     91     self.docstore.set_run_config(run_config)
     92 if self.generator_llm:
---> 93     self.generator_llm.set_run_config(run_config)
     94 if self.node_filter:
     95     self.node_filter.set_run_config(run_config)

Is this an error on my part or a bug?
Thanks.

I tried again and now it seems to be working.
However, it doesn't seem to work when I have so many documents that the generation remains at 0%. If I only have one, it goes to the end of the generation and the time is resonable. Is this normal?

When I have several documents, I get this error: ValueError: Node(page_content='something', doc_id='merged') is not in list. Any solution?


python tests shouldn't keep files after execution

After running yarn python:test we can see that two new untracked files are created: does_not_exist.json and to_be_mocked.json.
We should either ignore them or make sure they are removed.

CC @gjreda

@cguedes Where do you see these files getting written? Running yarn python:test and then git status does not reveal any untracked files.

I see them as you can see in the image. Do you have a global ignore file with them?

Running from main ...

Could this be caused by a change you have on your branch?

You are right. Must be something in the branch. I've just tested in main (a322cd07ac40499cc08a4dd2ded329123f50a3db) and I don't see the files!

I've now merged #425 into main and now we have this issue in main!
Can you spot anything weird in the changed files?

That change is causing the files to be created even though the tests in question here are simply trying to mock the object.
I missed that in my review, but I don't think we should automatically be trying to create the file.

Good catch. Would that file be automatically created on the first call? Bc I've had to add this code to prevent an error calling the backend.

As long as ingest has been successfully run, .storage/references.json should exist.

The issue is that the app try to get ingested references before any ingestion and that would fail because of this missing file.

Ah, I think I understand the issue. This would come up with the user tries to view references, but there aren't any yet?
If so, I think a simple backend fix is just gracefully handling a FileNotFound exception for this particular call, rather than generating the files no matter what.

Exactly. Ok, I think that that would work.


Return types give an error

In this project I am trying to use return type annotations.
Which in this minimal case give a error:
def foo [
    test: string
    ] nothing -> string {
         $test
}
foo bla

My best guess is, that in this line the return sequence is defined with a colon, which maybe should be a thin_arrow:
https://github.com/nushell/tree-sitter-nu/blob/7e0f16f608a9e804fae61430ade734f9f849fb80/grammar.js#L148

It's fixed in this commit, but it may take long before merged.
For now, you can add colon before the return type:
def foo [
    test: string
    ]: nothing -> string { # <-----
         $test
}
foo bla

Correct, we might should just close this and not fix it in tree-sitter-nu because improper syntax should show errors, right?
def foo [test: string]: nothing -> string { $test }
                      ^
                      |___ Nushell is supposed to require this colon. It is a bug in nushell that an error isn't thrown.

@fdncred oh there is supposed to be a colon there, gosh I didn't consider that at all.
Makes totally sense, and yes this is not TS-nu's fault then 😄

@petrisch right. the problem is that nushell doesn't currently enforce the colon to be there, but it should. that's a bug in nushell.


do not test query-batchSize when using default batchSize

Fixes PHP Fatal error:  Cannot use object of type stdClass as array in /home/travis/build/alexispeter/CM/tests/library/CM/MongoDb/ClientTest.php on line 158 occurring on boxes running  mongodb driver v1.6.x

please review @njam

lgtm


Adapt all documentations and features to fit CoDoc

There are still many traces of the parent program AddressBook left in many areas.
Need to fix them along development before the final delivery of the program (v1.4).

Currently working on UserGuide.md.
Noted needed changes in the name of the jar file (currently addressbook.jar) and also the JSON file for data storage (currently addressbook.json)


Undefined type 'dlib::pixel_traits<pixel_type>' in cv_image class

I am not sure if this issue is platform-related or due to the poor C++11 support by MSVC (Windows 7 + VS2015, Dlib version 19.4)
Would you please advise the possible root cause? Thank you in advance.
#include <dlib/image_processing.h>
#include <dlib/image_transforms.h>
#include <dlib/opencv.h>

using namespace dlib;

cv::Mat getFaceChipImage(cv::Mat src_img, unsigned long size, double padding) const {
	cv_image<array2d<rgb_pixel>> dlib_cvimg(src_img);     // <<<< Apparent
	cv_image<array2d<rgb_pixel>> face_chip;
	extract_image_chip(dlib_cvimg, get_face_chip_details(shape, size, padding), face_chip);
	cv::Mat mat = toMat(face_chip);
	return mat;
}

Compilation of above function encountered the following errors in dlib\include\dlib\opencv\cv_image.h:
line 28:
- Error C2027:	use of undefined type 'dlib::pixel_traits<pixel_type>'
- Error C2146:	syntax error: missing '>' before identifier 'basic_pixel_type'
- Error C2065:	'num': undeclared identifier

line 36:
- Error C2027:	use of undefined type 'dlib::pixel_traits<pixel_type>'
- Error C2146:	syntax error: missing '>' before identifier 'basic_pixel_type'
- Error C2065:	'num': undeclared identifier

Yeah that looks like an error in MSVC.  Try it in gcc, I'm pretty sure it will work.
Also make sure you have all the updates for MSVC 2015 since there are many: http://dlib.net/faq.html#HowcanIusedlibinVisualStudio.  Although maybe you have discovered yet another bug in MSVC related to C++11 support.


CLI: Auto-extend program accounts by default

issue #564
Problem
When you deploy a program, it initially takes up 2x the program size. At a later date if you try to deploy larger than the currently allocated size, you get the following error:
Error: Deploying program failed: Error processing Instruction 0: account data too small for instruction
The correct way to solve this is to use solana program extend <PROGRAM_ID> <MORE_BYTES> to extend the program, then deploy it again.
Developers attempting to calculate this amount over and over again have become frustrated and some have just spent the money to allocate way more than they should. Some even as much as 10mb. This is bad both for the cluster and developer experience.
Summary of Changes

Add Checks in do_process_program_upgrade fn to calculate additional bytes required to extend the program and throw an error if auto-extend-program flag is not passed with message to use solana program extend
Add --auto-extend-program flag to solana program deploy command and use this to auto extend solana program data account in case of overflow

Nice! Not a bad idea, and thanks for rolling tests and nice output logs.
I'm wondering if we should just make this the default behavior, rather than requiring an option to trigger it. It seems to me like 10/10 times the user who encounters that error message instructing them to use --auto-extend-program is going to immediately retry with the option.
Instead, your program data account will always be extended automatically on deployment. Maybe we can also offer an option for --no-extend to do opposite, for those rare cases where someone might want that.
What do you think?

Yeah sounds good to me , I can change logic to auto extend and add no-extend flag as well

@buffalojoec  have changed the logic

I know you're trying to give the user a little log message about the program size being too small, but since we've flopped this option around to be explicitly "do not attempt to extend", I think it's fine to allow the transaction to fail as it currently does, if --no-extend is provided.
With that being said, I think you can simplify this approach by sliding the block of code that does the program data account lookup down into the initial_instructions setup step.
Basically, you could condense everything you've changed in do_process_program_upgrade into something like this and place it on line 2521.
if !no_extend {
    // Attempt to look up the existing program's size, and automatically
    // add an extend instruction if the program data account is too small.
    let program_data_address = get_program_data_address(program_id);
    if let Some(program_data_account) = rpc_client
        .get_account_with_commitment(&program_data_address, config.commitment)?
        .value
    {
        let program_len = UpgradeableLoaderState::size_of_programdata(program_len);
        let account_data_len = program_data_account.data.len();
        if program_len > account_data_len {
            let additional_bytes = program_len.sub(account_data_len);
            let additional_bytes: u32 = additional_bytes.try_into().map_err(|_| {
                format!(
                    "Cannot auto-extend Program Data Account space due to size limit \
                        please extend it manually with command `solana program extend {} \
                        <BYTES>`. Additional bytes required: {}",
                    program_id, additional_bytes
                )
            })?;
            initial_instructions.push(bpf_loader_upgradeable::extend_program(
                program_id,
                Some(&fee_payer_signer.pubkey()),
                additional_bytes,
            ));
        }
    }
}

What do you think?
P.S. clippy is yelling at you about something!

sounds good to me ! ,i have resolved this

Codecov Report
Attention: Patch coverage is 29.16667% with 17 lines in your changes are missing coverage. Please review.

Project coverage is 81.9%. Comparing base (f133697) to head (e225def).
Report is 6 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #791   +/-   ##
=======================================
  Coverage    81.9%    81.9%
=======================================
  Files         855      855
  Lines      232134   232157   +23
=======================================
+ Hits       190134   190160   +26
+ Misses      42000    41997    -3

Hey @Nagaprasadvr try running:
cargo clippy --workspace --tests --bins --examples --features dummy-for-ci-check -- --deny=warnings --deny=clippy::default_trait_access --deny=clippy::arithmetic_side_effects --deny=clippy::manual_let_else --deny=clippy::used_underscore_binding

Hey @Nagaprasadvr try running:
cargo clippy --workspace --tests --bins --examples --features dummy-for-ci-check -- --deny=warnings --deny=clippy::default_trait_access --deny=clippy::arithmetic_side_effects --deny=clippy::manual_let_else --deny=clippy::used_underscore_binding

nice , this worked

Awesome work! I went ahead and added the test for you :)
Thanks for contributing!

your welcome , looking forward to contribute more


Infrared Spectrometry 1 should be Biome Specific

Infrared spectrometry doesn't seem to exist, perhaps you meant infrared radiometry? If so, ROK doesn't touch the situation/biome mask for RP0infraredRad1, so it depends on RP-1.
For what it's worth, in my configCache it's the same, consistent situation/biome mask = 48 for all the 4 tiers of the experiment. Maybe you meant some other line of instruments?


docker-compose: 1.5.1 -> 1.5.2

1.5.1 introduced an obnoxious bug that's fixed in 1.5.2: https://github.com/docker/compose/issues/2481


Custom toolchain cannot be set

$ rye toolchain register /usr/bin/python3 -n=ubuntu
Registered /usr/bin/python3 as<EMAIL_ADDRESS>$ rye pin<EMAIL_ADDRESS>Error: unsupported/unknown version for this platform

It should work with rye pin<EMAIL_ADDRESS>


Possible to use tokens in more things than command strings?

I'd like to be able to use tokens anywhere in a check definition if possible, not just command strings.

Where else would they need to be applied?

In the handler(s) parameter in the check definition but they may also be
useful elsewhere.
On Dec 4, 2015 4:14 PM, "Sean Porter"<EMAIL_ADDRESS>wrote:

Where else would they need to be applied?
—
Reply to this email directly or view it on GitHub
https://github.com/sensu/sensu/issues/1126#issuecomment-162107360.

👍 to this. It would be very helpful when combined with Uchiwa so one can embed links to Graphite/Grafana for service-specific checks that auto-fill the hostname based on tokens.

@davpx, @hany: this has been implemented in Sensu Core version 0.24, released earlier this week. \o/
See here:

Release: https://sensuapp.org/blog/2016/06/07/sensu-core-v0-24-0.html
New "check token substitution" docs: https://sensuapp.org/docs/latest/reference/checks.html#check-token-substitution


Publication to introduce the package

Dear Stuart McHattie, Stefano Borini, Khader Shameer,
Is there any publication to introduce Omicsfold package?
Thanks.
Shicheng

Hi Shicheng,
Apologies for the late reply. We are working on the publication and are hoping to submit for peer review shortly. Here is a link to a conference publication on OmicsFold. https://onlinelibrary.wiley.com/doi/full/10.1002/lrh2.10300. @shameer


Sidenav and Toolbar buttons are highlighed automatically

Bug, feature request, or proposal:
Bug
What is the expected behavior?
When the sidenav is opened and the user move the cursor on one of buttons the first button is always highlighted automatically.
Moreover, when the sidenav is closed the menu button on the toolbar is highlighted automatically until the user click somewhere else.
What is the current behavior?
Highlights should be shown only if the user moves the cursor on button.
What are the steps to reproduce?
Plunker -> https://plnkr.co/edit/ve5Ez0WSinNyowxI46LO?p=preview
Which versions of Angular, Material, OS, browsers are affected?
"@angular/common": "2.4.7",
"@angular/compiler": "2.4.7",
"@angular/core": "2.4.7",
"@angular/flex-layout": "^2.0.0-beta.4",
"@angular/forms": "2.4.7",
"@angular/http": "2.4.7",
"@angular/material": "^2.0.0-beta.2",
"@angular/platform-browser": "2.4.7",
"@angular/platform-browser-dynamic": "2.4.7",
"@angular/platform-server": "2.4.7",

Is there anything else we should know?

This is related to the md-button directive. The first md-button in the sidenav shows this behavior. As a workaround, you can set a 'dummy' anchor tag or button at the start of the sidenav with an md-button attribute, then set its height to 0 and position it absolutely.
http://stackoverflow.com/questions/42442406/angular-2-material-sidenav-focus-on-the-first-navigation-item/42443947#42443947

Just looked into this. It's WAI that the sidenav focuses the first focusable element upon opening, though as @joh04667 pointed out the md-button is treating the programmatic focus from the focus-trap as a keyboard focus and applying the keyboard focus styling. I'll prepare a PR to switch md-button over to using the new FocusOriginMonitor which handles this edge case.

@mmalerba just to be clear....it's WAI to have the keyboard focus only show up and stick to the first element when any md-button element is hovered over? And for it to lose keyboard focus when an empty space in the sidenav is clicked? This doesn't seem like a very good feature to me; the keyboard focus is not shown initially and is able to be removed trivially.
Here's a simpler Plunker with that behavior: https://plnkr.co/edit/wPWpZINvhfhyhViXc9Jt?p=preview

It's WAI for the first focusable element in the sidenav to be focused when the sidenav is opened. However buttons should only have the darkened background style when they are focused via they keyboard (i.e. pressing tab).

2018 update: I'm still having this problem 1 year later, I was able to solve it using a variation of @joh04667's hacks, adapted to the current angular version.

force the first button in the side nav to stay unfocused => still works
force the menu button outside the side nav to stay unfocused => calling _removeKeyboardFocus() didn't work for me, instead I came up with the following hack

template:
<mat-sidenav #sidenav (close)="handleClose(menuButton)">
  <!--...-->
</mat-sidenav>
<mat-sidenav-content>
  <button #menuButton mat-icon-button (click)="sidenav.toggle()">
    <mat-icon>menu</mat-icon>
  </button>
  <!--...-->
</mat-sidenav-content>

controller:
  @ViewChild('menuButton') menuButton: MatButton;

  handleClose = (button: MatButton) => {
    // <any> needed to satisfy ts compiler, otherwise it won't allow accessing MatButton's private methods
    (<any>button)._focusMonitor.stopMonitoring(button._getHostElement());
  }

This might not be the best solution, but it seems like the easiest from what I have read. I just simply overrode the focus class (in my case, .mat-list-item-focus) to background-color: inherit !important; since it is just slightly changing the background color and isn't doing anything else. Then I made a custom class that I apply with routerLinkActive.
Obviously, this only works assuming you're using Angular routing, but could easily be modified to suit your situation.

2018 update: I'm still having this problem 1 year later, I was able to solve it using a variation of @joh04667's hacks, adapted to the current angular version.

force the first button in the side nav to stay unfocused => still works
force the menu button outside the side nav to stay unfocused => calling _removeKeyboardFocus() didn't work for me, instead I came up with the following hack

template:
<mat-sidenav #sidenav (close)="handleClose(menuButton)">
  <!--...-->
</mat-sidenav>
<mat-sidenav-content>
  <button #menuButton mat-icon-button (click)="sidenav.toggle()">
    <mat-icon>menu</mat-icon>
  </button>
  <!--...-->
</mat-sidenav-content>

controller:
  @ViewChild('menuButton') menuButton: MatButton;

  handleClose = (button: MatButton) => {
    // <any> needed to satisfy ts compiler, otherwise it won't allow accessing MatButton's private methods
    (<any>button)._focusMonitor.stopMonitoring(button._getHostElement());
  }

Note that this is still a hack, so if someone knows a cleaner solution please, let me know!

IMO a better way to handle this is to put the stopMonitoring line in ngOnInit in the containing component. Remove the close handler, add the ViewChild variable to your containing component, and in ngOnInit call of the enclosing component, put (menuButton)._focusMonitor.stopMonitoring(menuButton._getHostElement()); There's no need to call stopMonitoring every time you close the sidenav.

so is this issue still open? I can see the same issue with what I am doing right now..

Yes, it's still a issue. You'll have to do the hacky ways in this thread to get around it. At least in 6.4.6. Haven't tested in version 7+

I believe this is related to https://github.com/angular/material2/issues/10402? Found this thread via google long before that one and was stuck for a while.


[#106] Converted UUID to Long

@adriancole can you check this out? Especially where I

do the conversions from Long to String
modified the PercentageBasedSampler and all related to that

Thanks for putting a work in progress out.
I think after some unneeded types and abstracting is removed, it will shred far more code.
Also, we need a test somewhere that proves hex is the representation form. ex some assertion where traceId is equal to literally "abcd..." as a side-effect of the long conversion to string.

I think this is still missing the change to make span ids hex encoded?

Much better. :ship: when ready

Done in https://github.com/spring-cloud/spring-cloud-sleuth/commit/82ed9f78a16ef34db48979762e7bec606d20ff9c


debug build crashing on rspack/packages/rspack/tests/cases/context/issue-3873

System Info
None
Details
Using rspack debug build
    {
      target: 'node',
      context: '/Users/bytedance/github/rspack/packages/rspack/tests/cases/context/issue-3873',
      entry: { main: './' },
      mode: 'development',
      devServer: { hot: false },
      infrastructureLogging: { debug: false },
      output: {
        path: '/Users/bytedance/github/rspack/packages/rspack/tests/cases/context/issue-3873/dist'
      }
    }

Reproduce link
No response
Reproduce Steps
.

fixed in #3196


Possible to support SHA2 512 hash alg in addition to the current SHA3?

Currently, the spec requires the hash to be computed using SHA3 512.
Would it be possible to also (or instead) support SHA2 512? (My main reason for the request is - WebCryptography API in the browser supports SHA2 but not 3).

I picked SHA3 initially because I had support for it in my implementation stack and it was a newer alg. It was simpler to build with just one for now, but what I think we actually need to do is some kind of crypto agility. Like the client sends this request:
callback: {
  uri: "https://client.foo/callback?state=blab",
  nonce: "12356431",
  alg: "SHA3-512"
}

Or even if the client sends a set of supported algorithms:
alg: ["SHA3-512", "SHA2-512", "ROT13"]

And when the server returns its nonce it also returns the chosen alg:
server_nonce: "6544321",
alg: "SHA2-512"


calico-node fails to start when using ETCD_AUTHORITY=localhost:2379 and hostname is set to localhost

I'm trying to run a Kubenetes master using the cloud-config from the the Vagrant demo (https://github.com/projectcalico/calico-containers/tree/master/docs/cni/kubernetes/vagrant-coreos/cloud-config), but modified to use Kubenetes 1.2.0 and calico 0.18.
The master is failing to start - the relevant logs appear to be:
Apr 05 17:51:44 localhost calicoctl[16945]: Running Docker container with the following command:
Apr 05 17:51:44 localhost calicoctl[16945]: docker run --restart=always --net=host --privileged --name=calico-node -e HOSTNAME=localhost -e IP=<IP_ADDRESS> -e IP6= -e CALICO_NETWORKING=true -e AS= -e NO_DEFAULT_POOLS= -e ETCD_AUTHORITY=localhost:2379 -e ETCD_SCHEME=http -v /var/log/calico:/var/log/calico -v /var/run/calico:/var/run/calico calico/node:v0.18.0
Apr 05 17:51:44 localhost calicoctl[16945]: Calico node is running with id: 12cdb4a9fc1ed443da0cc7df5a32a00f590cb29c81c694576ff74881b0725b60
Apr 05 17:51:44 localhost calicoctl[16945]: Waiting for successful startup
Apr 05 17:51:44 localhost calicoctl[16945]: Traceback (most recent call last):
Apr 05 17:51:44 localhost calicoctl[16945]: File "startup.py", line 295, in <module>
Apr 05 17:51:44 localhost calicoctl[16945]: main()
Apr 05 17:51:44 localhost calicoctl[16945]: File "startup.py", line 251, in main
Apr 05 17:51:44 localhost calicoctl[16945]: warn_if_hostname_conflict(ip)
Apr 05 17:51:44 localhost calicoctl[16945]: File "startup.py", line 192, in warn_if_hostname_conflict
Apr 05 17:51:44 localhost calicoctl[16945]: current_ipv4, _ = client.get_host_bgp_ips(hostname)
Apr 05 17:51:44 localhost calicoctl[16945]: File "/usr/lib/python2.7/site-packages/pycalico/datastore.py", line 132, in wrapped
Apr 05 17:51:44 localhost calicoctl[16945]: "running?" % (fn.__name__, e.message))
Apr 05 17:51:44 localhost calicoctl[16945]: pycalico.datastore_errors.DataStoreError: get_host_bgp_ips: Error accessing etcd (Connection to etcd failed due to MaxRetryError("HTTPConnectionPool(host='localhost', port=2379): Max retries exceeded with url: /v2/keys/calico/bgp/v1/host/localhost/ip_addr_v4 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f70f88882d0>: Failed to establish a new connection: [Errno -2] Name does not resolve',))",)).  Is etcd running?
Apr 05 17:51:44 localhost calicoctl[16945]: Calico node failed to start

If I run calicoctl node it seems to work:
core@localhost ~ $ sudo calicoctl node
Running Docker container with the following command:
docker run -d --restart=always --net=host --privileged --name=calico-node -e HOSTNAME=localhost -e IP= -e IP6= -e CALICO_NETWORKING=true -e AS= -e NO_DEFAULT_POOLS= -e ETCD_AUTHORITY=<IP_ADDRESS>:2379 -e ETCD_SCHEME=http -v /var/log/calico:/var/log/calico -v /var/run/calico:/var/run/calico calico/node:v0.18.0
Calico node is running with id: 4a2274e837104c5ef9e81aecd228924a816d1823787abe094d23ab932ee5ba2a
Waiting for successful startup
No IP provided. Using detected IP: <IP_ADDRESS>
Calico node started successfully

And the difference between the two seems to be the use of ETCD_AUTHORITY=<IP_ADDRESS>:2379 in the working case.

I've tried changing the hostname with hostnamectl <name> and rebooted the master.  I'm still getting the same calico-node error.

The following command works for me docker run --net=host --privileged --rm -e HOSTNAME=localhost -e IP=<IP_ADDRESS> -e IP6= -e CALICO_NETWORKING=true -e AS= -e NO_DEFAULT_POOLS= -e ETCD_AUTHORITY=localhost:2379 -e ETCD_SCHEME=http -v /var/log/calico:/var/log/calico -v /var/run/calico:/var/run/calico calico/node:v0.18.0
Can you confirm that a simple ping works? docker run --net=host --privileged --rm -e HOSTNAME=localhost -e IP=<IP_ADDRESS> -e IP6= -e CALICO_NETWORKING=true -e AS= -e NO_DEFAULT_POOLS= -e ETCD_AUTHORITY=localhost:2379 -e ETCD_SCHEME=http -v /var/log/calico:/var/log/calico -v /var/run/calico:/var/run/calico calico/node:v0.18.0 ping localhost
If so, then the issue is probably somewhere in python or urllib3
Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f70f88882d0>: Failed to establish a new connection: [Errno -2] Name does not resolve',))",)).

Can we at least detect this case and print a warning from calicoctl.  Feels sufficiently obscure to diagnose that errorring out might be the right approach.

Our company is evaluating Calico currently, but calico node we pulled down does not work.
We have to switch to weave. Below is the error we got:
Pulling Docker image calico/node:latest
Running Docker container with the following command:
docker run -d --restart=always --net=host --privileged --name=calico-node -e HOSTNAME=ip-10-224-15-53.aws.domainname.comec2.internal -e IP= -e IP6= -e CALICO_NETWORKING=true -e AS= -e NO_DEFAULT_POOLS= -e ETCD_AUTHORITY=<IP_ADDRESS>:2379 -e ETCD_SCHEME=http -v /var/log/calico:/var/log/calico -v /lib/modules:/lib/modules -v /var/run/calico:/var/run/calico calico/node:latest
Calico node is running with id: 32334c6563a91c627e80ee10eb003f26378b5559e935865ee1af54243330c32e
Waiting for successful startup
No IP provided. Using detected IP: <IP_ADDRESS>
Traceback (most recent call last):
File "startup.py", line 310, in
main()
File "startup.py", line 264, in main
f.write("IP=" + ip)
File "/usr/lib/python2.7/site-packages/netaddr/ip/init.py", line 421, in add
new_value = int(self._value + num)
TypeError: unsupported operand type(s) for +: 'int' and 'str'
Calico node failed to start

@padgyx it looks like the issue you're seeing is different from the one @lwr20 was seeing.  Could you open a separate issue for it?
I'd also recommend trying one of our released calico/node images.  The latest is v0.19.0.  The latest tag is built from master and is not always stable.

Thanks for the quick reply. The problem is when user run calicoctl node
command, it will pick up the latest version of calico node image. We have
no way to tell what version of image to use. I have tried the docker run
like this:
sudo docker run -d --restart=always --net=host --privileged
--name=calico-node -e
HOSTNAME=ip-10-224-15-36.aws.domainname.comec2.internal -e IP= -e IP6= -e
CALICO_NETWORKING=true -e AS= -e NO_DEFAULT_POOLS= -e ETCD_AUTHORITY=
<IP_ADDRESS>:2379 -e ETCD_SCHEME=http -v /var/log/calico:/var/log/calico -v
/lib/modules:/lib/modules -v /var/run/calico:/var/run/calico
calico/node:v0.9.0
but it does not work. It complains the BGP is not configured
properly: calico KeyError: 'BGP configuration for host not found'
On Wed, Apr 27, 2016 at 2:17 PM, Casey Davenport<EMAIL_ADDRESS>wrote:

@padgyx https://github.com/padgyx it looks like the issue you're seeing
is different from the one @lwr20 https://github.com/lwr20 was seeing.
Could you open a separate issue for it?
I'd also recommend trying one of our released calico/node images. The
latest is v0.19.0. The latest tag is built from master and is not always
stable.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/projectcalico/calico-containers/issues/906#issuecomment-215179630

@padgyx if you're using a released version of calicoctl node then it fixes the version of the docker image to be the same version as calicoctl.  If you build calicoctl yourself from master then it pulls calico/node:latest.
I think there's a typo in your docker run command above, looks like you've got v0.9.0 rather than v0.19.0, which is current.

It's wrong to use 'localhost' as the HOSTNAME (certainly if there's more than one node).
The best place to get calicoctl from is the Releases page on github (https://github.com/projectcalico/calico-containers/releases).  This should avoid problems with master not always being stable.

@matthewdupre @lwr20 what's up with this guy?

I'm waiting for a diags fix - as @fasaxc says: "Can we at least detect this case and print a warning from calicoctl. Feels sufficiently obscure to diagnose that errorring out might be the right approach."

I'm closing this as wontfix.


getSignalStrength not working give ever noting back

Hello the function getSignalStrength not working give ever 0 back... (and yes i have rssi 18-20 when i direct ask the module)
struct WorkStruct
{
    char phone[16];
    char datetime[24];
    char gprsBuffer[64];
    char message[50];
    float temp;
    float hum;
    int oled_modus;
    int signal_level;
} Work;

  bool ok = gsm.getSignalStrength(Work.signal_level);
  Serial.println("QQ");
  Serial.println(ok);
  Serial.println(Work.signal_level);

Thanks for helping

@sn2k Could you try to type "AT+CSQ" manually in Serial Debug mode? See what you'll get.
What I got as below,
OK
AT+CSQ

+CSQ: 23,0

Manuali thats functione....
But i have a big problem the libory needs too many ram 38% is too much, its not stable...

That is why it uses Software Serial and his buffers.


Request

hey Morten :-)
Was wondering if it was possible to add community maps to the server-launcher ?
Like if I want to host a local Pool_day server (like good old days)
Or am I missing the option ?
On the account I subscribed to poolday, but not able to change to it in the launcher.
Hope you se this :)

Hello there, thank you for reaching out!
I could add an option for inputting your own map, which I think would solve this issue.
Would this be a good solution for you?
Morten

Hey Morten,
Sounds super :-) I'll give it a go and let you know if I have issues :)
// TIG

Hey Morten,
Seems like the update dosn't function as expected. When I try to launch the server, it just shuts the program down.
Also - before it worked with a config file, now it's hardcoded to a folder - any chance to have this feature back ? :-)
Best
TIG

I just ran the release on another PC, gave me this:

Maybe check if the config file is present in the same folder as the new .exe file?

Hey Morten,
We tried to update the path, it runs as expected, but when I hit launch, it just closes down.

Hey Morten,
Had a chance to dig further ? :-)

Hi, sorry, been quite busy, will try look into it asap.
I will probably release a version that outputs any kind of error before terminating.


Unable to query any public repos

Currently unable to query any public GH or gitlab public repos. This was working yesterday (or day before) and suddenly stopped working. Your documentation discusses uninstalling/reinstalling "plugins" whereas ChatGPT no longer uses the "plugin" nomenclature but rather talks of custom GPTs.
Having googled, plugins seem to have been deprecated in favour of custom GPTs. I'm currently paying askthecode for a service... and currently cannot use it. I don't think it's a client-side issue as a) it was working fine before and b) I've tried it using various clients (iOS app, desktop webapp) and still get the same problem.
Please see attached screenshot of what happens if I ask any question querying a github repo.

Thanks.

Same issue here. Ask TheCode won't open any public repos. I didn't log in using my GitHub account, just used the magic code to the email address. It used to work, but doesn't now.

@dsomok - it's working again. Thanks!

happy to hear that, thanks for your feedback and sorry for the inconvenience!


Value not refreshed in the controller

Bonjour :

The meeting starts at {{ meeting }}.

self.onChange = function() {
       console.log($scope.meting);
};

console.log return the old value . Is this normal ?

Mmmh @marco10024, you're right! That's not a correct behavior, that's why I'm going to change it. However, at the moment you can use the two parameters passed through your $ctrl.onChange method:
self.onChange = function (newValue, oldValue) {
   console.log(
      'newValue = ', newValue,
      'oldValue = ', oldValue
   );
};

Last release, v0.5.5, contains the update above.
Now when change is fired model value contains the new date.
Thank you @marco10024!


fix(portainer): update the check status to only target portainer server

Thank you for making MicroK8s better
Please reference the issue this PR is fixing, or provide a description of the problem addressed.
Also verify you have:

[x] Read the contributions page.
[x] Submitted the CLA form, if you are a first time contributor.

#Fixes 165
Update the check_status for Portainer to match for only a Portainer server installation, and not a Portainer agent installation.

@neoaggelos or @ktsakalozos let me know any feedback you have, and if it's ok to merge. Cheers!

Looks reasonable and harmless. Will do a review soon.

@testA113 this does not work because the checks are performed only against resources shown by kubectl get all -A and PVCs are not in there.

Thank-you for pointing this out @ktsakalozos! I'm just double checking with the team about another option. It'll likely still need a PR to this repo with a different check_status no matter what we decide, so make this PR a draft until it's ready in a day or two. Cheers!

Sure, you can keep this PR. Remember you can test the changes you do by doing something like:
sudo microk8s.addons repo remove community
sudo microk8s addons repo add community https://github.com/testA113/microk8s-community-addons --reference fix-portainer-check-status-to-only-target-server
microk8s.enable portainer

@testA113 let me know when you want me to review this PR.

Hey @ktsakalozos this PR along with a PR for MicroK8s is ready for review - let me know your feedback and thank-you for keeping the related issue open :)

Hi @testA113, sorry for taking long. I appreciate the effort of introducing check_status_regex, though I would like to keep this simple.
Would it be possible to check availability by using a service name instead, e.g. service/portainer-$something ? This sounds like a simpler fix, which would also work with older microk8s versions.
Essentially, adding a new field in the addons.yaml could break older microk8s versions and we would like to avoid it if possible. Thanks!

Thanks for the reply @neoaggelos!
I was looking for easier solutions too, but came up against the same false positive issue for all resources that portainer server has (and that the portainer agent resources contain):
.
The thread for this PR above goes through some solutions that didn't work:

Using a persistent volume claim as the check_status (not included in the kubectl get all command)
Using a file path as the check_status that portainer creates after install (when running microk8s status, it would not show as enabled on other nodes).

We also considered updating the Portainer helm chart used for the community addon, but this could create issues for users installing the new helm chart with an older microk8s version.
Adding the regex_check_status seems like the best solution for portainer and other community addons which may also have false positives when running microk8s status. These PRs are also made in a way that still keeps full check_status functionality, keeping check_status as a required field and working in the is_enabled microk8s function (regex_check_status is optional).
For these PRs to be considered, are there any particular concerns that you have with breaking older microk8s versions? I'd be keen to make any changes to help. Or if you have any other suggestions, I'm open to them too.

Ah, thanks for the context, I see where you are coming from. I wonder if pulling out a cheap trick like this would work check_status: "deployment.apps/portainer " (notice the empty space)

Nice suggestion! I noticed it uses the whole row from kubectl get all so it might work :) Will report back soon

Your cheap tricks work @neoaggelos! I'm guessing that you would prefer this small change to the portainer check_status instead of introducing regex_check_status ?

I've removed the regex_check_status and this PR now only has a simple check_status change.
Let me know if you're happy with the change and I'll also close the microk8s PR that handled the regex_check_status.

Hey @neoaggelos let me know if you're happy with the change - I'm happy with it from testing

Thanks @testA113, LGTM.
FYI, I had to rebase your PR on the latest main to include linter CI fixes.

Thankyou @bschimke95!

@bschimke95 will this change take effect immediately, or after a new microk8s release?

Excuse my ignorance, but how do we get this released?
If I try with MicroK8s latest/stable at the current moment (1.28.3 at present) and I then deploy the Portainer Agent on my cluster, and I run a microk8s status, I can still see Portainer Server showing up in the output as enabled. Hence, I don't think this change is kicking in yet.

@jamest-portainer you should have this available on the 1.29/stable channel. Please do not use latest/stable as this will update yous k8s clusters without you knowing.

The addons are considered part of the user workload and as the workloads do not get updated when the microk8s moves to a new version so do the addons. To get the latest community addons after refreshing to 1.29 try:
sudo microk8s addons repo update community


Compile error - Edit.js

Step to reproduce:
Install fresh by following README
Default kali versions:
npm -v
7.5.2
node -v
v12.22.5
Backend starts fine:
npm start

<EMAIL_ADDRESS>start
node ./bin/www

Listening on port 4000
UI doesn't compile:
Failed to compile
./src/Pages/Edit.js
Syntax error: Unexpected token (246:41)
244 |
245 |         const parse = require('color-parse')

246 |         let initCol = parse(props.color ?? 'orange')
|                                          ^
247 |
248 |         setState({
249 |             displayColorPicker: false,

This error occurred during the build time and cannot be dismissed.

I have seen this very error with an install attempt that failed to install deps. Delete that git clone, grab it again and try to eyeball for any failures during the npm ci install
I'm also not certain if that older node version is involved. I'll have to grab a Kali image, and check it out myself.
If a second npm ci install on a fresh git clone also fails... dump it again, and just go with a generic npm install

Hey @LaBuse56, I tried it out on Kali and it gets up and running, no need to update node either. I suspect your issue was also a failed npm install. I hope the fresh clone and npm ci install clears you up. Don't forget to configure your .env file. It's a pretty boring experience without any integrations.

I agree.. Looks like my setup had a glitch... Still having issues but definitively on my side!


DIOS-3740 Fix sse events retrieval

You should hide white space, i do not understand why it is doing that in github review.

needs rebasing

needs rebasing
done


Add Python Solution for Problem Of The Day | 22 January 2023

Comment below if you're interested in working on this issue and would like to be assigned to it.

@maddy020 ,
Someone has already submitted the code for this issue, but he has not commented here. So I can't assign him, and I'm also not removing you from this issue. Because this was his first pull request, I approved it..


WebSocket dies with handler return

Hi
I am using flask to run a long-running task in the background. I now want to use flask-sockets to send progress updates to the user. Consider this example where queue is filled with progress updates as they become available:
@sockets.route('/progress')
def progress(ws):
    while not ws.closed:
        ws.send(queue.get())

In principle, this code is running fine, but the flask application is blocked until the handler returns. I see how this is consistent with flask's single process architecture, but I expect websockets to work asynchronously, too. I tried introducing an explicit thread like this:
@sockets.route('/progress')
def progress(ws):
    def target(ws,queue):
        while not ws.closed:
            ws.send(queue.get())
    threading.Thread(target=target, args=(ws, queue)).start()

Unfortunately, the thread dies with the exception WebSocketError: Socket is dead. It looks like the socket is closed by the server as soon as progress returns and is then considered dead, although it is still available in target's context.
Is sending from background threads unsupported or am I missing something? In case it is depending on the server used, I am using the pywsgi.WSGIServer as shown in the example code.
Kind regards

After digging further, I noticed #15 containing information regarding gunicorn, gevent and the chat example. It looks like a flask-sockets handler is already threaded implicitly using gevent, but I need to prevent premature handler return and allow switching to another thread explicitly by invoking gevent.sleep() like this:
@sockets.route('/progress')
def progress(ws):
    def target(ws,queue):
        while not ws.closed:
            ws.send(queue.get())
    threading.Thread(target=target, args=(ws, queue)).start()
    while not ws.closed:
        gevent.sleep(10)

It looks a bit backwards at first, but it is not busy waiting.


Symbol description property should not forget its value.

🔎 Search Terms
symbol, description
🕗 Version & Regression Information

This is a crash
This changed between versions ______ and _______
This changed in commit or PR _______
This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
I was unable to test this on prior versions because _______

⏯ Playground Link
https://www.typescriptlang.org/play?esModuleInterop=false&declaration=false&target=9&jsx=0&module=7&stripInternal=false&noErrorTruncation=true&ts=5.4.0-dev.20231124&ssl=10&ssc=48&pln=1&pc=1#code/MYewdgzgLgBBCeBbGBeGBlJAjEAbAFAOQBmIIhAlAFBUD0tMUAFgJYQwCGEELA5mIgCmYWBCYgArrgAmMAO4gATgGsqoSLAAeALgDe0wRGCKWABygtw2kmUIBfVHCQ16jVuwUqOiyWFnSQQxgwEFhPVXVoGHhHBGQuGHwJMBYARwlBJ0QcXBgAMhh9Q2MzCysbcjtqOgZmNnklZXYsCVhBRS4guJyYZLSMsEMINXAogC9YpE52fG68fMKDIxNzSzBrUkqKIA
💻 Code
const sym = Symbol('foo')

// this assignment should work
const x:{description:'foo'} = sym

// this workaround does not work
const y = sym as (unique symbol & {description:'foo'})

// this works but erases symbol uniqueness
const z = sym as (symbol & {description:'foo'})

🙁 Actual behavior
The assignment fails with

Type 'typeof sym' is not assignable to type '{ description: "foo"; }'.

Typescript infers sym as a unique symbol with a readonly description property of type string | undefined.
Note that you can't correct this with an intersection type (as also illustrated in the example)
🙂 Expected behavior
Typescript should infer that description is of type "foo" and permit the assignment.
Additional information about the issue
No response

You’re looking for
- const y = sym as (unique symbol & {description:'foo'})
+ const y = sym as (typeof sym & {description:'foo'})

@andrewbranch You're right! Adding a wrapper type works.
It seems an assertion does as well:
const sym = Symbol('foo')
assert(sym.description === 'foo')

@andrewbranch why did you mark this as a question? Is there a design reason the auxiliary type or the assertion should be needed at all?

Yes, this is working as intended; I sometimes use "Question" to indicate that the OP was trying to solve a problem and found a solution, even if they went in thinking they were seeing a bug.


Preparation of meeting and guide for verification of research projects results - 2024#1

The following actions are to do, in order to prepare the meeting and the guide:

[x] #1048

[x] #1049

[x] #1050

All done.


Update troubleshoot-a-full-transaction-log-sql-server-error-9002.md

Modifying the instruction on how to open the notebook.

@MsSQLGirl : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off


try-runtime CLI might have exited prematurely

In https://github.com/paritytech/polkadot/pull/4772#issuecomment-1031443213 the try-runtime CLI might have exited prematurely for some reason.
The process exited normally (exit code 0) according to what I observed in the logs (time 2022-02-07T13:00:57.220898488Z, ts 2022-02-07T13:00:57.341Z, tsNs<PHONE_NUMBER>341432060 on Grafana). However, from @kianenigma on Matrix:

https://github.com/paritytech/polkadot/pull/4772#issuecomment-1031443213
seem to have worked until somewhere at least
but either died, or the logs are truncated too much
if you compare the comment from the bot with what shawntabrizi posted next, the bot seem to have died midway while scraping stuff. This is not about RUST_LOG.

This is still an issue. See https://github.com/paritytech/polkadot/pull/5322#issuecomment-1098145377

This is still an issue. See paritytech/polkadot#5322 (comment)

@coderobe what is the full output?

The expected output should end in something like TryRuntime_on_runtime_upgrade executed without errors. The log in the linked issue comment is heavily truncated (or killed) way before any of this happened, making it essentially useless.

I recall that in the past part of the issues related to try-runtime where that the instances running it would run out of resources. If that's still the case, I strongly think we are creating a self-inflicted problem. We should allocated more dedicated machines to this with enough resources.

I couldn't come back to this so far due to lack of time, but from what I suspect the issue doesn't have to do with host resources, it's something else. I expect to come back to this tomorrow or early on Monday.

I couldn't come back to this so far due to lack of time, but from what I suspect the issue doesn't have to do with host resources

Ok I take it back, it seems like the process is being killed by the host... This wasn't being caught
I'll request more resources for that host from DevOps

Opened https://github.com/paritytech/devops/issues/1589. This issue can be closed once that's done.

Closed https://github.com/paritytech/devops/issues/1589 as per https://github.com/paritytech/devops/issues/1589#issuecomment-1120393781 but the problem hasn't been dealt with yet. It should be taken care of by https://github.com/paritytech/try-runtime-bot/pull/57.

Fixed by https://github.com/paritytech/command-bot/pull/57


openstack add floating_ip

Hi
We are trying to deploy bucc to openstack but we dont know how to add a floating ip to the machine. We need it in order to reach it as only through floating ip the machine is reachable.
For us is not clear these 2 variables
openstack_vip_ip: {floating_ip}
openstack_vip_net_id: ??
When deploying interpolating all the files we had to use ~/workspace/bosh-deployment/external-ip-with-registry-not-recommended.yml and -v external_ip="{floating_ip}".
How can I express the same with bucc?
Thanks in advanced

Hi
I found out that there is a --debug. I can modify the manifest from there.
Sorry


[BUG]: Citations do not correspond to the true chunk locations.

How are you running AnythingLLM?
Docker (local)
What happened?
I am using a Docker file and embedding texts in the AnythingLLM Database. When I use it, the citation section shows the wrong positions of the chunks used to provide the answer. Please help me fix this issue, and if there is a way to do it, please provide guidance!
Set up the Environment:
Ensure Docker is installed and running on your machine.
Use the provided Docker file to set up the AnythingLLM environment.
Start the Docker container.
Embed Texts in AnythingLLM Database:
Use the embedding function to add texts to the AnythingLLM Database.
Ensure that the texts are divided into chunks correctly during the embedding process.
Query the Database:
Perform a query that triggers the citation functionality.
Observe the results and note the positions of the cited chunks.
Identify the Issue:
Compare the cited positions with the actual positions in the original text.
Note any discrepancies where the citation positions do not match the correct locations of the chunks

This is not a bug if I am reading this correctly, this is just how RAG works. They are ranked by "similarity" not their inherent order in the original document. In fact, embeddings do not preserve their order in the source document at all and are purely linked via metadata alone.


Make sure at least surefire 2.22.2 is used.

Otherwise tests won't run in a plain maven build but only in an IDE that replaces the default runner (like IDEA does) when recognizing JUnit 5.

Thanks Michael


fix: properly accumulate custom headers

Hi @onnovos. I'm so sorry, but my original fix to this was incorrect. To be honest, I am not sure how it worked? This should properly handle the custom headers now.
I didn't see anywhere in the tests where I could add this and make sure it is properly being generated, but maybe I am missing something?
There is no rush on this - I am using the fork for now.

I'll roll out a release in the morning when I'm at my desk 👍
Thank you! 🙏

Release of v1.0.4 is done @jhosteny 👍

@onno-vos-dev fantastic, thanks again!