Some NCCL operations have failed or timed out. Due to the asynchronous nature of CUDA kernels

预训练 Zero3。 8*H100. 7B 模型
这种问题有办法解决吗
0%|          | 0/50000 [00:00<?, ?it/s][WARNING|logging.py:290] 2023-10-28 02:00:04,787 >> You're using a LlamaTokenizerFast tokenizer. Please note that with a fast tokenizer, using the __call__ method is faster than using a method to encode the text followed by a call to the pad method to get a padded encoding.
[E ProcessGroupNCCL.cpp:474] [Rank 1] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=879, OpType=ALLGATHER, NumelIn=2097152, NumelOut=16777216, Timeout(ms)=1800000) ran for 3487087 milliseconds before timing out.
[E ProcessGroupNCCL.cpp:474] [Rank 2] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=879, OpType=ALLGATHER, NumelIn=2097152, NumelOut=16777216, Timeout(ms)=1800000) ran for 3487086 milliseconds before timing out.
[E ProcessGroupNCCL.cpp:474] [Rank 3] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=879, OpType=ALLGATHER, NumelIn=2097152, NumelOut=16777216, Timeout(ms)=1800000) ran for 3487087 milliseconds before timing out.
[E ProcessGroupNCCL.cpp:474] [Rank 4] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=879, OpType=ALLGATHER, NumelIn=2097152, NumelOut=16777216, Timeout(ms)=1800000) ran for 3487088 milliseconds before timing out.
[E ProcessGroupNCCL.cpp:474] [Rank 5] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=879, OpType=ALLGATHER, NumelIn=2097152, NumelOut=16777216, Timeout(ms)=1800000) ran for 3487088 milliseconds before timing out.
[E ProcessGroupNCCL.cpp:474] [Rank 7] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=879, OpType=ALLGATHER, NumelIn=2097152, NumelOut=16777216, Timeout(ms)=1800000) ran for 3487087 milliseconds before timing out.
[E ProcessGroupNCCL.cpp:474] [Rank 6] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=879, OpType=ALLGATHER, NumelIn=2097152, NumelOut=16777216, Timeout(ms)=1800000) ran for 3487088 milliseconds before timing out.
[E ProcessGroupNCCL.cpp:488] Some NCCL operations have failed or timed out. Due to the asynchronous nature of CUDA kernels, subsequent GPU operations might run on corrupted/incomplete data.
[E ProcessGroupNCCL.cpp:494] To avoid data inconsistency, we are taking the entire process down.
[E ProcessGroupNCCL.cpp:915] [Rank 3] NCCL watchdog thread terminated with exception: [Rank 3] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=879, OpType=ALLGATHER, NumelIn=2097152, NumelOut=16777216, Timeout(ms)=1800000) ran for 3487087 milliseconds before timing out.

预处理超时了？

我也遇到了这个问题 不太确定是不是版本库的问题

解决方案：https://github.com/hiyouga/LLaMA-Factory/issues/1196#issuecomment-1784737793

--preprocessing_num_workers 128，我是通过设置该参数解决的。


taskfiles: refresh root release

Motivation: it contains inconsistent state, e.g., installation instruction and provided changelog.

Example https://github.com/kamilsk/go-tools/releases/tag/goimports

curl -sSfL https://install.octolab.org/kamilsk/goimports | sh -s -- -b /usr/local/bin

the actual is https://github.com/kamilsk/go-tools/releases/tag/v0.11.1, or more correct is https://github.com/kamilsk/go-tools/blob/extended/CHANGES.md

fixed


forc-deploy v0.44.0 cannot deploy to fuel-core v0.20.3 with --unsigned flag

Deploying to a test-net is functioning correctly, with signatures coming from either forc-wallet integration or manual flow. But --unsigned flag is problematic. This is pretty important as it is both blocking local workflows (testing against local node quickly) and also fuelup compatibility checks.

closed by #4957


How is this different from your Locon extension?

I already had the Locon extension installed, and had no issue using Lycoris files from the regular Models/Lora folder.  I'm just confused as to how this differs from this one - https://github.com/KohakuBlueleaf/a1111-sd-webui-locon

just use more better way to impl it
to avoid lot of conflict fro mother lora extensions

OK, so the Locon extension is deprecated & you recommend this Lycoris extension as a replacement?

@B00Berry Yes

@B00Berry Yes

So do LoHa models still go in the Lora folder, or into the new LyCoris folder?  A general overview of correct usage and setups would be really helpful here.  Thanks for all your work!

@B00Berry
1, If you want to use old locon ext, put LyCORIS model in lora folder
2, If you want to use new lycoris ext, put LyCORIS model in LyCORIS folder
Only lycoris ext can support all type of LyCORIS model, (for example: locon ext doesn't support dylora)

@catboxanon If you want to disagree this decision
please make sd-webui be better for extension to make new functionality in the built-in things.
Do you know how annoying that every one send issue to locon extension and almost all of that is casued by other extension?
If I can just avoid these things by just make a stand alone system
Why I need to maintain the old one and worry about sd-webui's update and worry about other extensions
And, BTW, your script forget ckpt and pt file.


Total  memory consumption for training with 32 batch size.

I have tried training the convmae detector (as provided in this repository) with 2 GPUs with each 32GB (V-100). It looks like I can carry out training with only batch size = 2. Going beyond batch-size 2 raises CUDA out of memory. Also with such small batch size training does not seem to produce any well-trained model. Could you tell me the recommended memory size for training the model with batch size  = 32?
Thank you so much.

ConvMAE base detector with 32 batch size is trained by 8 A100 (80G). The GPU memory is approximately 40-50GB/GPU. You are recommend to use the updated ConvMAE Det with the following github link:
https://github.com/OpenGVLab/Official-ConvMAE-Det

Thanks for the github link. It seems the installation of default detectron2 will not work with the given repository as the detectron2 with the given repostiroy is different. Could you tell a bit on how to install the given detectron2 (that comes with this repository)?

Will it be possible to share the compiled version of the custom detectron2 (as changes were made in this repository)?

Our ConvMAE implementation do not modify detectron2 lib as shown below.
https://github.com/OpenGVLab/Official-ConvMAE-Det/blob/main/projects/ConvMAEDet/modeling/convmae.py
Official detectron2 lib should support ConvMAE.

I see. It seems the source version of detectron2 is way ahead of the compiled version available.

Please compile an environment support official ViTDet first.


Multidb changes for review.

Unit tests are failing - would like to review these and submit changes if this PR looks ok.


Add typescript definition

I have done a d.ts prototype to the ones using typescript. There is a lot missing but it makes the job. I'm using it in production.

I thumbs up TS work on PhysicsJS!


Fix Map Race by Moving Locking closer to the Write

Fixes #2444
I think we are protecting only the map as mentioned in the above issue. This is much cleaner and will avoid the race when there are multiple providers (We are launching a go routine per provider and not serializing access there).
The only question I have is whether this line needs to be protected: https://github.com/prometheus/prometheus/blob/master/discovery/discovery.go#L236

@fabxc Could you have a look?

Mh, okay – tricky section to touch but seems generally sound.
However, in updateProviders() we reset the tgroups to an empty map. Updating go routines might not have exited yet in response to the context cancelation and may still write into it. So the reset at least has to be guarded as well.

Hmm, true @fabxc. But I decided to ignore it as it was the behaviour before this PR too. A go routine in a previous loop could update the current set. I was hoping it would even out in the next run of the update.
Incase we want to do it right, the context would need to cancel the update midway too. Let me see if I can patch that.

This introduces another place where we check the context. However, we are not guaranteed at all that the updating goroutines even run after the context gets canceled. So a possible interleaving could be that:

update function checks for context, its not canceled, after the select statement it gets unscheduled
reload is called and it cancels the context and proceeds to overwriting tgroups with an empty map.

At any time during 2., the goroutine from 1. may be resurrected, thinking the context is still alive and continuing with modifying tgroups.
So line 321 must be mutex protected either way. The additional checking of the context reduces the likelihood of a race but does not remove it.
Adding more context checks is usually only helpful if the processing time in between calls may be long, which is not the case here I think. So we might want to drop it again.

Oh wow! Never thought of that! What do you suggest? Drop the latest commit and proceed with the first commit? I will rollback this commit then.
Also, I am not able to get a good idea of how we can actually fix this. Just writing it down for (my) clarity: The update go routine keeps running in the background and when a reset is requested, it needs to exit. But by the time it learns about the reset, it might be midway updating the map!

Yes, as you summarized.
So guarding line 231/236 with another locking of the mutex in addition should solve the issue.

ping @fabxc

LGTM


Add benchmarks for ECVRF

Fore reference, here are the benchmarks run on my laptop:
ECVRF Ristretto key generation
                        time:   [31.628 µs 31.731 µs 31.836 µs]
                        change: [-0.8404% -0.3259% +0.2225%] (p = 0.24 > 0.05)
                        No change in performance detected.
Found 1 outliers among 100 measurements (1.00%)
  1 (1.00%) high mild

ECVRF Ristretto proving time:   [130.41 µs 130.84 µs 131.29 µs]

ECVRF Ristretto verification
                        time:   [158.36 µs 158.87 µs 159.41 µs]
Found 2 outliers among 100 measurements (2.00%)
  2 (2.00%) high mild

For comparison, here are benchmarks for signing and verifying BLS12381 signatures. Note that proving/signing is about the same if we use MinSig, but verification with ECVRF is about x4 times faster than MinSig and x5 faster than MinPk mode:
Sign/BLS12381MinSig     time:   [138.05 µs 138.66 µs 139.28 µs]
                        change: [+1.0652% +2.0322% +3.1337%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 1 outliers among 20 measurements (5.00%)
  1 (5.00%) high severe

Sign/BLS12381MinPk      time:   [306.88 µs 308.04 µs 309.54 µs]
                        change: [+1.7329% +2.1874% +2.6502%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 3 outliers among 20 measurements (15.00%)
  1 (5.00%) low mild
  1 (5.00%) high mild
  1 (5.00%) high severe

Verify/BLS12381MinSig   time:   [641.00 µs 644.32 µs 648.58 µs]
                        change: [+1.1418% +1.9667% +2.9040%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 1 outliers among 20 measurements (5.00%)
  1 (5.00%) high severe

Verify/BLS12381MinPk    time:   [738.40 µs 743.03 µs 748.39 µs]
                        change: [+1.0877% +1.6979% +2.3319%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 1 outliers among 20 measurements (5.00%)
  1 (5.00%) high mild

Interesting comparison results, I'm surprised they are so close. For Ed25519 we've found that the sweet point was at about 40x, but here it's only 4x. I can only imagine it makes sense because in ECVRF we use a) map to point b) operations over non group generator G (in which for ed25519 we applied precomputed tables)

Interesting comparison results, I was originally surprised they are so close because for Ed25519 we've found that the sweet point was at about 40x, but here it's only 4x. I can imagine the results makes sense because in ECVRF we use

map to point (which doesn't exist in ed25519)
operations over non group generators (every H(m) and ChaumPed proofs result to unknown points) (and for ed25519 we applied precomputed tables which improve performance by far)
Ristretto implementations are slightly more expensive than pure ed25519 in Rust.
we don't utilize aG + bP double scalar mul optimizations.

There are a multiple different operations and libraries in play which makes it hard to compare them, so I suggest that we create benchmarks for basic operations (hash-to-curve, arithmetic) for the groups we support to make comparison easier.
We don't utilise double scalar multiplication, but I'll check if it's possible.


Navigate and select without Vintage

Thanks for the great package.
I've noticed that when ignoring the "Vintage" package there is no way to navigate the todo list or select a todo to go to the source. The arrow keys just navigate the cursor and enter just breaks the line. With "Vintage" active there's no problem. On OS X.
Is this by design? I thought from the documentation that I should be able to navigate the same as if I was in VIM mode but with the arrow keys.

I have Vintage disabled and can move between todo entries using the j and k keys.
I intend to improve the experience in this regard, however.

There must be something else going on that is different on my system because j and k just insert the letters "j" and "k" when I push them.
Sublime Text 3; OS X; installed via Package Control... idk, guess I'll just use Vintage. haha.

I'm closing this issue. The problem appears to have something to do with a sequence of opening Sublime from the command line and then changing projects or something like that I haven't quite figured out. It does appear to be working property now after a restart.


PR request for "companion" plugin stabilize.nvim

I made a plugin to stabilize buffer content when opening splits.
The original idea came from wanting to get rid of the visually jarring window open/close events when using the auto_open feature from trouble.nvim. The thing is, stabilize.nvim currently requires a workaround for some window events and auto_open seems to be one of them.
Don't fully understand yet why this is required here and if it can be avoided for all cases inside stabilize.nvim but I thought I would ask if the following diff would be accepted as a PR:
diff --git a/lua/trouble/init.lua b/lua/trouble/init.lua
index bfb2d92..7ee34f5 100644
--- a/lua/trouble/init.lua
+++ b/lua/trouble/init.lua
@@ -62,6 +62,7 @@ function Trouble.open(...)
   else
     view = View.create(opts)
   end
+  vim.cmd("doautocmd User StabilizeRestore")
 end

 function Trouble.toggle(...)

Closing this in favor of https://github.com/luukvbaal/stabilize.nvim/commit/52303e5003659eb796c68c3016ca337ac23b9ce3 following discussion in https://github.com/neovim/neovim/issues/16255#issuecomment-962602011.


Content types missing createdAt, updatedAt and publishedAt attributes

Let me know if I can I can help!

Hi @SeedyROM thank you for letting me know about this one!
I've already fixed it, and I'm doing some tests before committing & pushing the code, so I don't need help this time, but it is much appreciated that you offered it! :)

Hi @SeedyROM I just published the 1.1.1 version with this fix and also the one you made in https://github.com/mancku/strapi-plugin-schemas-to-ts/pull/3


Exception "Cannot read properties of undefined (reading 'ok')"

I've been trying to debug why sometimes this plugin gets stuck in a state where it doesn't refresh/poll for updates.
While debugging I noticed this in my Homebridge debug logs. I don't think this is the same issue, but it's interesting nevertheless.
C:\Users\Long\AppData\Roaming\npm\node_modules\homebridge-daikin-airbase\src\airbase-controller.js:129
        if (!response.ok) {
                      ^
TypeError: Cannot read properties of undefined (reading 'ok')
    at DaikinAircon.sendRequest (C:\Users\Long\AppData\Roaming\npm\node_modules\homebridge-daikin-airbase\src\airbase-controller.js:129:23)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at DaikinAircon.exec [as getControlInfo] (C:\Users\Long\AppData\Roaming\npm\node_modules\homebridge-daikin-airbase\src\utils.js:15:20)
    at DaikinAircon.updateSubscribedServices (C:\Users\Long\AppData\Roaming\npm\node_modules\homebridge-daikin-airbase\src\airbase-controller.js:213:39)
[10/10/2022, 8:59:46 pm] [Daikin Airbase] Child bridge process ended
[10/10/2022, 8:59:46 pm] [Daikin Airbase] Process Ended. Code: 1, Signal: null

The relevant code is this https://github.com/yenoiwesa/homebridge-daikin-airbase/blob/master/src/airbase-controller.js#L113-L131
I haven't fully debugged the issue but I believe if it fails 3 times because of a FetchError, then response will remain undefined, trying to execute !response.ok will throw.
I think one fix would be to check for response being undefined too
        if (!response) {
            throw `Request failed after ${RETRY_ATTEMPTS} attempts`;
        }

Hi @longzheng, thank you for the pull request!
I understand how the AirBase could not respond and end up with a FetchError (maybe the AirBase is busy and the request times out, or it purposely ignores it and does not respond), however I do not think this error will always be linked to three failed attempts so I will change the error thrown to something more generic.

No actually it's not even that, it's just that the request was never sent okay.

I published version 3.2.5 of the plugin on npm, Thank you for your contribution @longzheng!


hangup issue

Test environmental:  CentOS 8
I use gargs for parallel task . but get hangup signal even with nohup.
The same issue.
https://stackoverflow.com/questions/64479821/why-hangup-signal-is-caught-even-with-nohup

Hi, I'd accept a PR to fix this in gargs.


Can we get a dashboard link on the developer.microsoft.com landing page?

Very small QOL improvement request, but one i feel would be worth doing :)
Can we get a link to the dashboard added to the landing page at https://developer.microsoft.com/en-us/? Once you're past this page every other page has the link... but not the main landing page.
This just adds extra complexity to getting into an area of the site that is so important to developers. It also makes walking thru the process with someone who isn't familiar with the site more complex than it needs to be:
"go to developer.microsoft.com and click on Dashboard" becomes "go to developer.microsoft.com and scroll down to the get started section, then select windows, then on the new page select dashboard"
or alternatively "please go to developer.microsoft.com forward slash en-us forward slash dashboard"
it's just a bit clunky - and there's plenty of room for a button next to the search icon. Would reduce friction and would likely lead to more people visiting the landing page, rather than just bookmarking past it.

@XboxNinge Thanks for your feedback. @jialge Can you follow up this item?

Thanks @XboxNinge for the feedback.  We will discuss it internally to see how we may want to surface the developer advocates site on the developer.microsoft.com homepage.

I'm reviewing some of the developer.microsoft.com feedback here but I don't have context of this request. Is this still applicable?

Things have changed quite a lot since I first reported this :) the link to the "dashboard" i was refering to is found top-right in the "Windows" area if you select it from the "Start building on these Microsoft products" section.
However, this is actually now the only sub section where the dashboard link makes sense. It used to be in other areas as well, but the site has been restructured and it doesnt really make sense to have this on the main landing page any more as the Dashboard is only relevant for Windows/Xbox developers.
That said, I find it interesting that the developer.microsoft.com site doesn't have any links for Xbox development? That would be a nice thing to have there - for example a link to Xbox.com/ID

There's a link to game development on the homepage - maybe a bit hidden at the moment

It takes you to https://developer.microsoft.com/en-us/games/.
I'll chat about this dashboard request with @GrantMeStrength and @QuinnRadich since I'm not familiar with that site.


Revert some formatting and errors in example code

It looks to me at some point someone ran all the codes through a formatter (which added ";" to all the lines, removed extra spaces that are used to align comments, replaced all single quotes to double quotes, etc.). It went wrong (i.e. broke the code) at a few places, and argurably make the example harder to understand at some other places.
This commit does the following:

Fix totally broken ones
Revert some examples to its original form because they are meant to look obfuscated or other intended formatting to present the code in an easier to understand way

I didn't touch anything else (like the spaces to align comments or ";") but I'm honestly not sure if it's better than the original.

Prettier doesn't seem to work reliably with such code :(


Moving default data tenant from old BC build to new

I'm trying to move data tenant from one build of bcsandbox-master to another, but I'm not sure I am applying all the steps in correct order or I am missing some. I guess the same steps should apply when moving tenant from one nav container to another.
In container A, I have tenant 'default' and installed extension. I can create SQL backup of tenant database using Backup-SqlDatabase. I'm now creating new container B and installing same extension to it's default tenant.
I want to Restore-SQLDatabase of a backup file of tenant from container A to container B and sync it, but I'm getting errors saying that either app is missing, tenant is not mounted or in sync, etc.
From that point I'm not able to re-install app, sync tenants or app.
What are the steps of moving 'default' tenant from one BC container to another?

Simplest plan I can think of assuming the builds have minimal changes between them:
Assuming single tenant with default tenant mode as you have said

Use Export-NavData to export ONLY tenant data (-IncludeGlobalData -AllCompanies) for the specified tenant
Make sure the same extensions (same versions too) are published & synced on the destination service. They do NOT need to be installed there
Use Import-NavData to import your file into the new service with the same flags as in 1

This process assumes schema (base and extension) is identical between the two, so it will not work as a migration across versions where those kinds of differences exist.
If the move scenario involves differences, you're in more traditional upgrade territory. I do not believe you can count on this working for arbitrary master -> master builds (data upgrade paths do not exist from all builds to all other builds). However, you should be able to try something like:

Set up both servers as multitenant (split app DB and tenant DB)
Set up the destination environment with whatever extensions you will need (have them published)
Dismount the tenant from the source
Mount the tenant on the destination
Sync-NavTenant
If extension versions have changed -> Sync-NavApp on each
Start-NavDataUpgrade (should run upgrade code from base and extensions)
Tenant should be operational

@cmrudolph-msft Thanks for the detailed steps provided.
The first scenario mentioned might be hard to pull of because of all the Microsoft's extensions already published, and they have different versions as well on two builds. It's also unlikely that we will have our extension with same version running on two different base app builds.
Import-NavData breaks as soon as it detects different app versions between apps on source and destination, and not to mention that base app schemas are different. This might work only in case where we need to transfer data between two environments on same build.
I think we fall into second scenario you mentioned, where data tenant is dismounted from one build and mounted to destination build (that has recent base app and extensions installed). Since we are talking here about two different BC containers, along with steps Dismount tenant from source and mount tenant to destination (Steps 3 & 4), I would need to first do SQL-Backup of source tenant and restore it to destination container, (where build01 and build02 are two BC containers running on different builds with same apps installed but different version):
Enter-NavContainer build01

Backup-SqlDatabase
  -ServerInstance "BUILD01\SQLEXPRESS"
  -Database "test"
  -BackupFile "C:\Run\my\test.bak"

After moving .bak file into new container, I can successfully restore tenant db into new environment:
Enter-NavContainer build02

Restore-SqlDatabase
  -ServerInstance "BUILD02\SQLEXPRESS"
  -Database "test"
  -BackupFile "C:\Run\my\test.bak"
  -ReplaceDatabase

However, when I try to mount this database to new application:
Enter-NavContainer build02
Mount-NavDatabase
  -DatabaseServer "build02"
  -DatabaseInstance "SQLEXPRESS"
  -ServerInstance "NAV"
  -DatabaseName "test"
  -TenantId "test"

I receive this message:
Mounting Database for template on server BUILD02\SQLEXPRESS
Mount-NAVTenant : The tenant template could not be mounted because the following installed NAV extensions are missing, matching content could not be
found, or have a higher version than those that are published and synchronized: "My Solution" by Ivan, version 11.19281.1.1.
At C:\Run\HelperFunctions.ps1:360 char:5
+     Mount-NAVTenant -ServerInstance $ServerInstance `
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (0:Int32) [Mount-NAVTenant], FaultException`1
    + FullyQualifiedErrorId : MicrosoftDynamicsNavServer$NAV/template,Microsoft.Dynamics.Nav.Management.Cmdlets.MountNavTenant

Even though I see my extension installed in both containers (in this case I have same app version):
ServerInstance : MicrosoftDynamicsNavServer$NAV
PSComputerName : da0e390e74629475ede654ccbc9383327a3619eddc5a2974596d83521c577871
RunspaceId     : 1b4f72f2-d68b-4e96-81b5-72e7ef62e7b8
AppId          : xxxxx-xxxx-xxxx-xxxx-xxxxxxx
Name           : My Solution
Publisher      : Ivan
Version        : 11.19281.1.1
ExtensionType  : ModernDev
Scope          : Global

If the extension is published on both services, the rules for successful binding on mount are:
Older Version
Not allowed for obvious reasons.
Newer Version
Always allowed - will mount into a state requiring a sync & upgrade to become operational.
Same Version
Allowed as long as the content of the package is the same. This means one of two things must be true. Either the package ID must be the same (a byte-for-byte match) or the internal content hash must match (a rebuild of package but with identical contents). Both of these values can be inspected by looking in the NAV App table in the app DB. If you aren't sure about the exact content state, can you check these values?
If your case involves a content change, you must change the version for the package to be bound successfully on the new service.


Help setting cloud_roleName using Azure SDK for Python

I need help setting the cloud_roleName while retrieving metrics using the Azure SDK for Python. I found some links where this is done using different programming languages or using the Application Insights SDK:
https://docs.microsoft.com/en-us/azure/azure-monitor/app/app-map#set-cloud-role-name
https://github.com/microsoft/ApplicationInsights-Python/issues/147
https://westerndevs.com/app_insights_appname/
I would like to know how I can filter metrics and use this setting to do it, if possible. If this setting is only available when using the Application Insights SDK for Python, please be kind and let me know.
Thanks in advance.

Hi @bulkware
That's a good question, I unfortunately don't know the answer which is Azure specific and not Python specific. Maybe @tjprescott or @alexeldeib would know?

Yes, you would need to use the App Insights Python SDK to set the cloud role name. Please note that this is not currently a supported SDK and not recommended for production use.


Remove beta article "Grant Access to Data in Audit Indexes'

Purpose of this pull request
This pull request removes this beta article:
https://help.sumologic.com/docs/manage/security/audit-indexes/audit-index-access/
Since the new "RBAC for Indexes" feature will replace this old beta feature, we'll publish the PR when the "RBAC for Indexes" article goes live (with PR #3393):
https://help.sumologic.com/docs/manage/users-roles/roles/rbac-for-indexes/
Issue: Asana ticket "RBAC for Indexes - Remove beta article "Grant Access to Data in Audit Indexes""

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions, .clabot
[x] Update Content - Revisions, updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

PLEASE READ
Following a recent back-end update, all contributors with a local clone or fork of our repository are required to run yarn install. This does not apply to direct page edits.

[x] Yes, I've run yarn install
[ ] No, does not apply to me

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1205712234148895

Closing this PR because it's replaced by this commit on PR #3393: "Remove 'Grant Access to Data in Audit Indexes' article"


BUILD_FAILED Building package grpc:x86-windows

Using vcpkg that was cloned half an hour before this build attempt - so should be the latest available version. Built the 64-bit version successfully just prior to this attempt.
Building package grpc[core]:x86-windows...
-- Note: grpc only supports static library linkage. Building static library.
-- Using cached C:/dev/projects/vcpkg/downloads/grpc-grpc-v1.23.1.tar.gz
-- Using source at C:/dev/projects/vcpkg/buildtrees/grpc/src/v1.23.1-ebfd5c51df
-- Configuring x86-windows
-- Building x86-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:136 (message):
Command failed: C:/dev/projects/vcpkg/downloads/tools/cmake-3.14.0-windows/cmake-3.14.0-win32-x86/bin/cmake.exe --build . --config Debug --target install -- -v
Working Directory: C:/dev/projects/vcpkg/buildtrees/grpc/x86-windows-dbg
See logs for more information:
C:\dev\projects\vcpkg\buildtrees\grpc\install-x86-windows-dbg-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_cmake.cmake:91 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
ports/grpc/portfile.cmake:77 (vcpkg_install_cmake)
scripts/ports.cmake:94 (include)
Error: Building package grpc:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: grpc:x86-windows
Vcpkg version: 2019.09.12-nohash
Additionally, attach any relevant sections from the log files above.

Hi, @khalprin Thanks for reporting this issue.
I can not reproduce this issue in my machine.
could provide us failure logs?

install-x86-windows-dbg-out.log

Errors are similar to the ones in the #9282

I tried removing openssl from the packages folder, the download folder and the buildtrees folder. Attempting to build gRPC still failed. I then completely removed vcpkg and all of its subfolders and started from scratch again. It resulted in the same error.
I'm using Visual Studio 2017 version 15.9.18
Here is the console output:
Starting package 6/6: grpc:x86-windows
Building package grpc[core]:x86-windows...
-- Note: grpc only supports static library linkage. Building static library.
-- Downloading https://github.com/grpc/grpc/archive/v1.23.1.tar.gz...
-- Extracting source C:/dev/projects/vcpkg/downloads/grpc-grpc-v1.23.1.tar.gz
-- Applying patch 00001-fix-uwp.patch
-- Applying patch 00002-static-linking-in-linux.patch
-- Applying patch 00003-undef-base64-macro.patch
-- Applying patch 00004-link-gdi32-on-windows.patch
-- Applying patch 00005-fix-uwp-error.patch
-- Applying patch 00006-crypt32.patch
-- Applying patch 00007-disable_grpcpp_channelz.patch
-- Applying patch 00008-fix-duplicate-gettid.patch
-- Using source at C:/dev/projects/vcpkg/buildtrees/grpc/src/v1.23.1-ebfd5c51df
-- Configuring x86-windows
-- Building x86-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:136 (message):
Command failed: C:/dev/projects/vcpkg/downloads/tools/cmake-3.14.0-windows/cmake-3.14.0-win32-x86/bin/cmake.exe --build . --config Debug --target install -- -v
Working Directory: C:/dev/projects/vcpkg/buildtrees/grpc/x86-windows-dbg
See logs for more information:
C:\dev\projects\vcpkg\buildtrees\grpc\install-x86-windows-dbg-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_cmake.cmake:91 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
ports/grpc/portfile.cmake:77 (vcpkg_install_cmake)
scripts/ports.cmake:94 (include)
Error: Building package grpc:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: grpc:x86-windows
Vcpkg version: 2019.09.12-nohash
Additionally, attach any relevant sections from the log files above.
I've included logs.
config-x86-windows-out.log
install-x86-windows-dbg-out.log
x86-windows.vcpkg_abi_info.txt

-- Found OpenSSL: optimized;C:/dev/projects/vcpkg/installed/x86-windows/debug/lib/libeay32.lib;debug;C:/OpenSSL_1.1.0f-Win32/lib/VC/libcrypto32MDd.lib (found version "1.0.2s")

-- Found OpenSSL: optimized;C:/dev/projects/vcpkg/installed/x86-windows/lib/libeay32.lib;debug;C:/OpenSSL_1.1.0f-Win32/lib/VC/libcrypto32MDd.lib (found version "1.0.2s")

It looks like there's a different OpenSSL version installed and the build tries to link against different release of OpenSSL.

Ah...that's it. I had a different version of openssl on my drive. I had forgotten about that. It seems a bit strange that the build wouldn't have used the download/package path of openssl that vcpkg had created...
Thanks for finding that.


ROCm 5.0 Segmentation fault

Hi
/opt/rocm/bin/rocminfo works just fine and shows GPUs, but when I try to make and run a simple helloworld program, I get a segmentation fault.
I have RDNA2 GPU (6800m). What could be the problem? I am not running kernel module from ROCm 5.0 package, but instead I am running vanilla Linux kernel 5.16.9. Has ROCm 5.0 kernel module been already incorporated to upstream Linux kernel?
--- The simple helloworld.cpp ---
#include
#include <hip/hip_runtime.h>
int main(int argc, char* argv[])
{
std::cout << "Before." << std::endl;
hipDeviceProp_t devProp;
hipGetDeviceProperties(&devProp, 0);
std::cout << "After." << std::endl;
return 0;
}

--- GDB showing the crash dump ---
Core was generated by `./helloworld'.
Program terminated with signal SIGSEGV, Segmentation fault.
warning: Section `.reg-xstate/887' in core file too small.
#0  0x00007f79e0257688 in rocr::image::ImageRuntime::GetImageInfoMaxDimension(hsa_agent_s, hsa_agent_info_t, void*) () from /opt/rocm-5.0.0/hip/lib/../../lib/libhsa-runtime64.so.1
[Current thread is 1 (Thread 0x7f79e00fdec0 (LWP 887))]
(gdb) bt
#0  0x00007f79e0257688 in rocr::image::ImageRuntime::GetImageInfoMaxDimension(hsa_agent_s, hsa_agent_info_t, void*) () from /opt/rocm-5.0.0/hip/lib/../../lib/libhsa-runtime64.so.1
#1  0x00007f79e02567b1 in rocr::image::hsa_amd_image_get_info_max_dim(hsa_agent_s, hsa_agent_info_t, void*) () from /opt/rocm-5.0.0/hip/lib/../../lib/libhsa-runtime64.so.1
#2  0x00007f79e0194679 in rocr::AMD::GpuAgent::GetInfo(hsa_agent_info_t, void*) const () from /opt/rocm-5.0.0/hip/lib/../../lib/libhsa-runtime64.so.1
#3  0x00007f79e01ba0ff in rocr::HSA::hsa_agent_get_info(hsa_agent_s, hsa_agent_info_t, void*) () from /opt/rocm-5.0.0/hip/lib/../../lib/libhsa-runtime64.so.1
#4  0x00007f79e0c45bb6 in ?? () from /opt/rocm-5.0.0/hip/lib/libamdhip64.so.5
#5  0x00007f79e0c4738d in ?? () from /opt/rocm-5.0.0/hip/lib/libamdhip64.so.5
#6  0x00007f79e0c47c79 in ?? () from /opt/rocm-5.0.0/hip/lib/libamdhip64.so.5
#7  0x00007f79e0c02fde in ?? () from /opt/rocm-5.0.0/hip/lib/libamdhip64.so.5
#8  0x00007f79e0c3af56 in ?? () from /opt/rocm-5.0.0/hip/lib/libamdhip64.so.5
#9  0x00007f79e0a7bdfe in ?? () from /opt/rocm-5.0.0/hip/lib/libamdhip64.so.5
#10 0x00007f79e0a9c365 in hipGetDeviceProperties () from /opt/rocm-5.0.0/hip/lib/libamdhip64.so.5
#11 0x0000000000201b09 in main (argc=, argv=) at helloworld.cpp:10

Is your configuration APU(Cezanne or Renoir) + RX6800M?
Cezanne and Renoir series APU have problems in ROCm 5.0 release.
For your issue, if you want to run hip application on  RX6800M.
First, identify RX6800M deviceIndex, either 0 or 1.
Assume it is 0. Then, run like this
hipDeviceProp_t devProp;
hipGetDeviceProperties(&devProp, 0);
$ ROCR_VISIBLE_DEVICES=0 ./helloworld

Hi,
Yes, I have a laptop with 5900HX + 6800M.
Thank you! Running with ROCR_VISIBLE_DEVICES=0 worked!
BTW: Apparently it is 0, but how can I identify 6800M deviceIndex? Is it somewhere visible in rocminfo output (I did not see such field)?

You can use following fields in rocminfo.
Node:                    1
Device Type:             GPU
If Device Type is GPU, then device index should be Node-1.
You can confirm it with following code.
Check its name/gcnArchName/pciDeviceID, etc.
`
hipDeviceProp_t props;
hipGetDeviceProperties(&props, deviceIndex);
std::cout << props.name << std::endl;
std::cout << props.gcnArchName<< std::endl;
std::cout << props.pciDeviceID<< std::endl;
`

Thanks @sampie for reaching out.
Looks like your issue is resolved with the suggestions given by @xfyucg.
Please note that ROCm does not work on integrated GPUs and APUs. So always try on discrete GPUs by mapping the corresponding node.
Thank you.

Yes, the main issue is resolved and 6800M seems to work under rocm with all the code that I have run with it so far.
However, I guess, if possible, it would be good to try to fix rocm in such a way that it would not crash if ROCR_VISIBLE_DEVICES is not set. It looks like rocminfo works just fine, so I wonder why hipGetDeviceProperties does crash.


framac: 18.0 -> 19.0

Motivation for this change
Things done

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

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

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

Notify maintainers
cc @thoughtpolice @amiddelk

@GrahamcOfBorg build framac

Closing as #63494 has been merged.


fix: cache-warmup fails

SUMMARY
This PR addresses #30900, which reports a "400 Bad Request: The CSRF session token is missing" error during cache warmup. The issue was due to missing header updates with the CSRF token and cookie (expecting session='session_cookie'). This PR ensures the token is correctly fetched and included in headers during the warmup process, resolving the error.
Fixes https://github.com/apache/superset/issues/30900
Fixes https://github.com/apache/superset/issues/31283
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Success:
...
...
[2024-11-26 19:00:00,054: INFO/ForkPoolWorker-62] cache-warmup[cad28d1b-df9c-4800-98bd-a09ec3af5d73]: Loading strategy
[2024-11-26 19:00:00,054: INFO/ForkPoolWorker-62] cache-warmup[cad28d1b-df9c-4800-98bd-a09ec3af5d73]: Loading DashboardTagsStrategy
[2024-11-26 19:00:00,055: INFO/ForkPoolWorker-62] cache-warmup[cad28d1b-df9c-4800-98bd-a09ec3af5d73]: Success!
[2024-11-26 19:00:00,131: INFO/ForkPoolWorker-62] fetch_url[90921f09-84a0-49ee-8b66-790864c72524]: Fetching https://sample.example.com/api/v1/security/csrf_token/
[2024-11-26 19:00:00,130: INFO/ForkPoolWorker-62] fetch_url[90921f09-84a0-49ee-8b66-790864c72524]: URL 'https://sample.example.com/api/v1/chart/warm_up_cache' is secure. Adding Referer header.
[2024-11-26 19:00:00,207: INFO/ForkPoolWorker-62] fetch_url[90921f09-84a0-49ee-8b66-790864c72524]: Fetching https://sample.example.com/api/v1/chart/warm_up_cache with payload {"chart_id": 1}
[2024-11-26 19:00:00,593: INFO/ForkPoolWorker-62] fetch_url[90921f09-84a0-49ee-8b66-790864c72524]: Fetched https://sample.example.com/api/v1/chart/warm_up_cache with payload {"chart_id": 1}, status code: 200
....
....
[2024-11-27 01:00:00,015: INFO/ForkPoolWorker-16] cache-warmup[35eba83f-4d8a-420c-9965-2a4a0411c891]: Loading strategy
[2024-11-27 01:00:00,016: INFO/ForkPoolWorker-16] cache-warmup[35eba83f-4d8a-420c-9965-2a4a0411c891]: Loading DashboardTagsStrategy
[2024-11-27 01:00:00,016: INFO/ForkPoolWorker-16] cache-warmup[35eba83f-4d8a-420c-9965-2a4a0411c891]: Success!
[2024-11-27 01:00:00,091: INFO/ForkPoolWorker-64] fetch_url[e9a5874d-0123-4d9b-8919-48b3bddd9ece]: Fetching https://sample.example.com/api/v1/security/csrf_token/
[2024-11-27 01:00:00,090: INFO/ForkPoolWorker-64] fetch_url[e9a5874d-0123-4d9b-8919-48b3bddd9ece]: URL 'https://sample.example.com/api/v1/chart/warm_up_cache' is secure. Adding Referer header.
[2024-11-27 01:00:00,163: INFO/ForkPoolWorker-64] fetch_url[e9a5874d-0123-4d9b-8919-48b3bddd9ece]: Fetching https://sample.example.com/api/v1/chart/warm_up_cache with payload {"chart_id": 1}
[2024-11-27 01:00:00,548: INFO/ForkPoolWorker-64] fetch_url[e9a5874d-0123-4d9b-8919-48b3bddd9ece]: Fetched https://sample.example.com/api/v1/chart/warm_up_cache with payload {"chart_id": 1}, status code: 200
...

TESTING INSTRUCTIONS
Since we are now explicitly fetching the CSRF token, we can enable WTF_CSRF_ENABLED = True or safely remove WTF_CSRF_EXEMPT_LIST for any cache warmup-related endpoints. This ensures that all requests, including those for cache warmup, are properly validated with CSRF protection, thereby enhancing application security.
If CSRF protection is disabled or the endpoint is exempted, no CSRF checks will be performed. However, the ChartRestApi.warm_up_cache endpoint still requires a session cookie (session=session_cookie) to determine the user's context and permissions. Without this, the request will fail with a 401 Unauthorized error.
This PR ensures the session cookie is correctly updated in the request headers under the Cookie field, enabling the user context to be accurately resolved for authorization.
ADDITIONAL INFORMATION

[x] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@nsivarajan I have tried it. But when I access the chart, it doesn't use the warmed up cache, but creates a different cache.

@AnTapTanhCode, thanks for checking this. I have verified the behavior in my test environment, and the cache-warmup process successfully caches, and the charts/dashboards retrieve data as expected.
It seems that your case, where a different cache is fetched and cached instead of the warm-up-cached data, might require further investigation. However, I believe this issue is unrelated to this PR. If needed, please open a new issue with reproducible steps, and we can debug it further later.

Looks to me like this ticks all the boxes of test coverage, proper cookie formatting, and HTTPS validation, but since this is so close to security concerns, I'm hopeful that someone more qualified (perhaps @dpgaspar and/or @mistercrunch) can take a look.

Thanks for your guidance and support!


 Fix all the below:
Planning

[x] Feels stuck in long responses
Soln: Made action stack status a list of terms that give the impression of progress

Completed actions

[x] Takes too much space
[x] No real info here
[x] Need to show the contents

Added decorators to the actions to specify labels and renderer fns. Eventually should move the action descriptions here as well (or better still, infer from the function)

Looks great!


Notify the previous route when pushing and popping

This makes HeroController ignore StateRoutes when deciding where to
animate heroes to and from.

LGTM


pyo3::prepare_freethreaded_python() gets another python interpreter.

echo $PYO3_PYTHON
/home/user/csp/software/anaconda3/envs/DB/bin/python

But when I run the following test,
#[test]
pub(crate) fn prepare_interpreter() {
    pyo3::prepare_freethreaded_python();
    Python::with_gil(|py| {
        // py.run(
        //     "import sys ; print(f\"pyo3 interpreter= {sys.executable}\",flush=True)",
        //     None,
        //     None,
        // )
        let sys = PyModule::import(py, "sys").unwrap();

        let py_path:&str = sys.getattr("executable").unwrap().extract().unwrap();
        let version_info:&str = sys.getattr("version").unwrap().extract().unwrap();

        println!("\npyo3 interpreter info:\n{}\n{}\n\n", py_path, version_info);
    });
}

Another python path shows.
pyo3 interpreter info:
/home/user/csp/software/anaconda3/envs/bbn2/bin/python
3.11.6 | packaged by conda-forge | (main, Oct  3 2023, 11:02:03) [GCC 12.3.0]

The latter python path is of a conda env used when cargo build and running this program.

The PYO3_PYTHON environment variable is only to determine the interpreter properties during build and will not influence how your operating system resolves references to e.g. libpython3.11.so when the final executable is running. That is determined by the usual methods like setting $PATH and $LD_LIBRARY_PATH, e.g. in your case most likely by activating the corresponding Conda environment.

Ah, I see. My fault.

@Crispy13 For what it's worth, I'm aware that prepare_freethreaded_python is a bit too minimal and have a hope that we'll introduce something better once we drop 3.7 support and can use the new interpreter initialization types. There are quite a few pain points around virtualenvs and PyO3 with different platforms which I think we can at least make smoother.


[Question]

Question
shenyu网关部署完成 测试bootstrap代理时报错

配置基本没有改动  存储方式变成mysql了
本地测试代码(走非mvc方式)  localhost:19000/test/test（已测试能通）
shenyu-bootstrap的端口是19195
当请求localhost:19195/test/test

如果路径错误 则会报普通的json错误

Please follow https://shenyu.apache.org/zh/docs/plugin-center/http-process/contextpath-plugin, and https://github.com/apache/incubator-shenyu/tree/master/shenyu-examples/shenyu-examples-http guide and try again, may this help u.
And please submit your plugin configuration and more details.
Thanks for your issue, and please use english to submit issue.

Changed a server
The test was successful once
This is a screenshot

I changed the port of bootstrap to 19195

This is the port and path of my test case

This is my selector configuration

This is my rule configuration

This is the plug-in I used in the bootstrap project
But when I visit again later
It's wrong！！！
This is the wrong log
error (3).txt

You are following this document https://shenyu.apache.org/zh/docs/quick-start/quick-start-http/, right?
Sorry I could not understand why you place your jars in ext-lib file and it may need some other dependency jars , and I can't see it in your jar dir, and you used 2.4.2 bootstrap, it's better use 2.4.2 divide and httpclient jar, maybe this caused the classClassException.

invalid title name


Revert removing public_map_deps files

Related issue https://github.com/CartoDB/support/issues/2048
Context
This issue has been solved by adding the public_map_deps that was removed when cleaning the dashboard dependencies. I haven't seen any other missing dependencies in these files.

Acceptance

Login: https://2048publicmap.carto-staging.com (2048publicmap)
Create map
Publish map
Access to published map public link
Open the console and check it's requesting the required files and rendering properly

@elenatorro I'm still getting the error when I open the public_map: https://2048publicmap.carto-staging.com/viz/c5659cbf-d178-465c-928f-28ed09554689/public_map

However, it doesn't happen when I open the embed map: https://2048publicmap.carto-staging.com/viz/c5659cbf-d178-465c-928f-28ed09554689/embed_map

I see! it seems it's still not working when the user is not logged in. Checking that!

I don't know why it works in one page and not in the other one. It shouldn't work in either of those.
The 403 error comes from S3 and that's because you didn't changed editor assets version, thus the new (or old :joy:) file is not generated because editor assets are not being generated.

Yes! I had the first thought when looking at the screenshot, it's now deployed again 👍


Extension considered signed in when personal address is saved

Reviewer: @GioSensation
Asana: Possibly related to https://app.asana.com/0/1198567644089701/1203172395139030/f
Description
We've had support issues that users sometimes can't log in. I don't believe this is the cause, but the symptoms match what's reported, so fixing this will hopefully remove a possible occurrence of this issue.
Previously the exntension was only considered signed in when both a personal and private address were available. However, it's possible that the extension won't be able to generate a private duck address (e.g. invalid token, firewall, API down, etc.) This updates the logic to consider the extension to be signed in when just a personal address is saved.
Steps to test

Sign up for a Duck Address using Firefox on sandbox site
Extension attempts to generate a private duck address using sandbox API token against production, which fails
You are not logged in to the web app, although the extension shows as logged in from the extension settings page

Mhm, I think this is just masking the problem.

We use the private address specifically because if you don't have a private address autofill won't work. The current UI expects both options to be available.
If the token is invalid something is very wrong, we can't just pretend the user has enabled Email Protection when that's not actually the case.

If we want to do something, we can report errors back to the web app (via autofill) and display an error in the web app. That will be more complex.
Do you have a strong reason to proceed with this PR and override my points above?

@GioSensation I'm not strongly opinionated as I don't think it's the state users have gotten into. For the points you've made:

"autofill won't work" -- I'm more concerned about users not being able to access the web app (so they can sign out, delete account, change forwarding address), than for autofill not working.
My example was an invalid token, but I don't see why there couldn't be other issues, e.g. firewall, API down, etc.
Same answer as point 1

If the token is invalid something is very wrong, we can't just pretend the user has enabled Email Protection when that's not actually the case.

To follow this though, if something is very wrong, should the extension (or any device) log the user out of it's not able to generate an initial private duck address? This would prevent us from being in the dual state of the extension showing the user as logged in but the web app showing the user as logged out.

I'm more concerned about users not being able to access the web app (so they can sign out, delete account, change forwarding address), than for autofill not working.

That's why I was suggesting to report errors back to the web app. This makes it look like you're signed in, but you're not, you're halfway there and for all we know you're in a broken state.

there couldn't be other issues, e.g. firewall, API down, etc.

If it's a firewall it's likely that the firewall will always stay in place, so in practice is the same state: the device is not properly set up. If the API is down we have a logic that retries again on 1m interval (IIRC) for a few times, and again at browser startup. Until then, though, it doesn't really matter. The device is not properly set up 🤷 .
I don't see this as a fix. This is pushing the problem further away and getting into another confusing state where autofill won't work, the extension doesn't think Email Protection is enabled, yet the web app thinks you're enabled and lets you in without any further notice. I don't think it's an improvement over what we have. It's a different shade of broken 🙃.
If we think this happens frequently enough we should prioritise a proper fix. And I think we're getting to a state where we do want to prioritise it.


text-directive with no $watch

http://jsfiddle.net/lega911/fqnhv94q/
http://jsfiddle.net/lega911/njqso7b8/


JAMES-3589 Allow tailor-made servers to customize their mailet container

This enables those who want to adopt alternatives to the existing CamelMailetContainer, allowing to bypass existing bugs like JAMES-3589.
The issue is that Mailet container is pre-bundled in GuiceJamesServer thus do not allow overrides.

I am merging it as it unstuck me and allow to bypass the issue on my deployments. No behavioural changes either way.


cosmic-edit: unstable-2023-11-02 -> unstable-2023-11-29

Description of changes
Updating the build for newer unstable base. This also moves it to by-name from applications.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 271454 run on aarch64-linux 1

1 package built:

cosmic-edit


”Roteni”, ”Stejeriș”, ”Suveica”, ”Vălenii” are listed in the drop-down menu

Description:
When user writes ”Roteni”, ”Stejeriș”, ”Suveica”, ”Vălenii” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Roteni"

Expected results
The location appears in the drop-down menu as "Sat Roteni, MUREȘ (Acățari)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Stejeriș"

Expected results
The location appears in the drop-down menu as "Sat Stejeriș, MUREȘ (Acățari)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Suveica"

Expected results
The location appears in the drop-down menu as "Sat Suveica, MUREȘ (Acățari)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Vălenii"

Expected results
The location appears in the drop-down menu as "Sat Vălenii, MUREȘ (Acățari)".


Create production.yml

Would love to have a concise Agile definition

"Production" has become such an overloaded term, especially in light of layering modern SRE practices overtop of these traditional definitions, i.e. https://www.pivotalk.io/t/are-slis-slos-taking-over-the-concept-of-production/28101

Would love to have a concise Agile definition

Do you have a definition to contribute?
Or was the intention simply to stub it out & encourage crowd sourcing of a definition from there??


perf: change icon size

Before:

After:

Thanks for your PR @Chanzhaoyu!
This is only happening when you have an external mouse connected, a proper fix would be to implement the Radix ScrollArea component as it sits on top of the content and doesn't cause any wrapping.
If you'd like to take a stab there's an example in the prompts component folder that needs to be converted to tailwind and moved to the global components folder.

Thanks for your PR @Chanzhaoyu! This is only happening when you have an external mouse connected, a proper fix would be to implement the Radix ScrollArea component as it sits on top of the content and doesn't cause any wrapping.感谢您的公关@Chanzhaoyu！ 这仅在连接了外部鼠标时发生，正确的解决方法是实现 Radix ScrollArea 组件，因为它位于内容之上并且不会导致任何换行。
If you'd like to take a stab there's an example in the prompts component folder that needs to be converted to tailwind and moved to the global components folder.如果你想尝试一下，提示组件文件夹中有一个示例，需要转换为顺风并移动到全局组件文件夹。

Ok, I'll try again.


Multiple plot windows?

Hi I would like to be able to plot multiple buffers to compare and view different data at the same time, could you give me some clues on how to implement this? Also how would I add the ability to plot a 2d array using imagesc? Thanks so much, this package works very well.

To plot multiple things on the same plot, just give multiple arguments to the plot command. For example, to simultaneously plot x, y, and z, run plot x y z.
I'm not familiar with imagesc, but a quick Google suggests that it's a Matlab command for 2D heatmaps? If so, I would take a look at the plot.py file, so you can add a new plot command. I imagine it will look similar to the existing Plot3D class given that it's for plotting 2D data, except you'll replace the matplotlib command for 3D plotting with 2D heatmaps. In the past, I've used imshow to achieve that.

Ahh sorry I mean that right now I need to close a previous window for the next plot window to show up, is there a way to get it to open a new window every time a plot call is made in gdb?

It took me way too long to figure it out and its still very very buggy, but instead of using the global plt space if you encapsulate the plotting function in a object i.e. figureObj = plt.figure() and newplot = figureObj .add_subplot(111), if you use figureObj.show() with a pause call it allows you to have a new window every time you call plot, there are a bunch of bugs however with some windows randomly blanking themselves sometimes when another is created, the windows also become non-interactive, and will immediately close without a short pause call (dont know why a few milisecond pause is needed), but this is a step towards getting multiple windows to work properly.

It seems the blanking bug is that when a window is placed ontop of another, the overlap is blanked and it is not redrawn when the overlying plot is moved away, when you make another plot it does a full redraw of all visible windows and fixes the blanking on anything not being covered.

I have solved the issue myself by creating a new thread process for each plot call, all window functions work and I can spawn as many windows as I want.


dancelist validate should support yaml anchors

I’ve just tried to create a PR for the Vienna events (#447). According to my local schema validations the yaml file is fine, but it fails to validate with dancelist validate because I’ve used anchors to spare me some copy&paste.
I’m not a rust programmer but according to https://stackoverflow.com/questions/73311581/how-to-use-yaml-references-with-rusts-serde-yaml serde_yaml (which seems to be used by this project) supports anchors. Therefore I’m not sure what’s wrong with dancelist validate.

This might be the issue from https://github.com/dtolnay/serde-yaml/issues/317, which also mentions a workaround.


Localize rest of strings

Now that https://github.com/microsoft/vscode-livepreview/pull/220 is in, localizing the rest of the strings should be straightforward.
Step 1: localize calls
For every file that contains a user facing string, you'll do the following:

include the import (order doesn't matter, just needs to happen after that setup import from above):

import * as nls from 'vscode-nls';

You must use this import format and not import { ... } from 'vscode-nls';. Please see: https://github.com/microsoft/vscode-nls-dev/issues/36

Load the messages (this can go right after your imports):

const localize = nls.loadMessageBundle();

Replace all user-facing strings with a call to localize(). Here are some examples:

// simple
localize('some unique-to-this-file id', 'User facing string to translate');

// parameters
localize('some unique-to-this-file id', 'User facing string to {0}', translate);

// comments with a way to ensure something isn't translated
localize({
  key: 'some unique-to-this-file id',
  comment: [
    // This is magic localization syntax to enforce that this part of the string must not be translated.
    "{Locked='](command:donttranslateme)'}",
    "Do not translate the 'command:*' part inside of the '(..)'. It is an internal command syntax for VS Code"
  ]
}, '[translate me](command:donttranslateme)');

NOTE: It's ok to be iterative here. Convert a few strings over to use localize, then in a follow up PR, do more.

Additional context around the localize call
Let's take this example:
localize(
  {
    key: 'some unique-to-this-file id',
    comment: [
      // This is magic localization syntax to enforce that this part of the string must not be translated.
      "{Locked='do not translate me'}",
      "Do not translate the 'do not translate me' part"
    ]
  },
  'translate me but do not translate me but also here is a parameter: {0}',
  'foo'
);

The first parameter is either just a string which represents the key or an object that has a key and a comment property.
The key isn't really important, it's just an identifier of the string. You can put whatever you want there, it just has to be unique to the TS file that contains the string. Yes, this means that you could reuse the same key across different TS files so if that makes sense for you, don't be afraid to do that.
The comment section is a way to manipulate how the string is translated. You can either use the special {Locked=''} syntax which is called "functional commenting" (docs on functional commenting), or you can use a normal comment which will be shown to the translator responsible for translating the string. Using both is ideal because the functional commenting also applies to the Pseudo Language generation which a human is not involved with and the normal comments help describe our code better.
The next thing we have is the actual literal string that will be sent to translators. Let me be clear. The EXACT string that a translator will see is translate me but do not translate me but also here is a parameter: {0} (even with the {0} part). This is because our strings are sent over at build time - not runtime. It's important that this parameter is completely static (no concatenation, no interpolation, nothing) because we scan the TS for the strings and do not run the code at all.
The final parameter(s) of our call are the segments of the string that will be filled in at runtime. When VS Code runs, it will take the value of these parameters and replace the {0} {1} {2} etc syntax with the respective parameters passed in after the string to be translated.
Step 2: package.nls.json
The other strings that we need to translate are found in your package.json. You'll have plenty of strings in the contributes section. These strings can be moved over to a package.nls.json file and look like so:
{
  "displayName": "Remote Repositories",
  "description": "Remotely browse and edit git repositories",
  "colors.added": "Color for added resources",
  "colors.modified": "Color for modified resources",
  "colors.deleted": "Color for deleted resources",
  "colors.conflict": "Color for resources with conflicts",
  "colors.incomingAdded": "Color for incoming added resources",
  "colors.incomingModified": "Color for incoming modified resources",
  "colors.incomingDeleted": "Color for incoming deleted resources",
  // NOTICE THE LONG FORM WITH COMMENTS:
  "viewsWelcome.explorer": {
    "message":"You can remotely open a repository or pull request without cloning.\n[Open Remote Repository](command:remoteHub.openRepository)",
    "comment": [
      "{Locked='](command:remoteHub.openRepository)'}",
      "Do not translate what's inside of the '(..)'. It is an internal command syntax for VS Code"
    ]
  },
  // etc
}

The keys of these strings are then referenced in the package.json with % around them like so:
{
  "name": "remote-repositories",
  "private": true,
  "displayName": "%displayName%",
  "description": "%description%",
  // etc
}

NOTE: It's ok to be iterative here. Convert a few strings over to use package.nls.json, then in a follow up PR, do more.

verif steps:

download newest live preview:
ms-vscode.live-server.0.2.14.zip
try translating to something like Czech


Updates lodash, require only functions needed

lodash < 2.0.0 throws warning when running npm install : updates lodash to 4.0.0
lodash 4.0.0 is a modular npm package, we can require only the functions needed.

@sokra @chiplay does this seem reasonable to you ?

:+1:

Thanks for your contribution.


Release 3.2 NuGet package?

With all of the recent changes (new indicators, performance improvements, bug fixes), shall we release 3.2 nuget package?

Yes, i'm preparing the package & the documents for the recent change. May complete uploading today.


HPCC-28181 update README.md files and handling non default region

Add help scripts for adding nfs inbound rule and stop EKS cluster
@g-pan please help reviewing following README.md
./EFS-CSI/README.md
./EKS/one-node-pool/README.md
./EKS/README.md
./IAM/README.md
./README.md

@arjunachala and @dcamper it is ready to merge.


Cargo conflicts with main branch and bevy_rapier2d

Bevy version
f4776f2ec413bb80ff4ee51e04bb57f0a44d9983
(Latest commit)
Operating system & version
Arch linux
What you did
cargo new
add
[dependencies]
bevy = { git = "https://github.com/bevyengine/bevy", rev = "f4776f2ec413bb80ff4ee51e04bb57f0a44d9983" }
bevy_rapier2d = "0.11.0"

to Cargo.toml
cargo run
What you expected to happen
The test program compiles and runs with latest versions of bevy_rapier and bevy
What actually happened
    Updating git repository `https://github.com/bevyengine/bevy`
    Updating crates.io index
error: failed to select a version for `syn`.
    ... required by package `wasm-bindgen-macro-support v0.2.73`
    ... which satisfies dependency `wasm-bindgen-macro-support = "=0.2.73"` of package `wasm-bindgen-macro v0.2.73`
    ... which satisfies dependency `wasm-bindgen-macro = "=0.2.73"` of package `wasm-bindgen v0.2.73`
    ... which satisfies dependency `wasm-bindgen = "^0.2.73"` of package `wgpu v0.9.0`
    ... which satisfies dependency `wgpu = "^0.9"` of package `bevy_wgpu v0.5.0 (https://github.com/bevyengine/bevy?rev=f4776f2ec413bb80ff4ee51e04bb57f0a44d9983#f4776f2e)`
    ... which satisfies git dependency `bevy_wgpu` of package `bevy_internal v0.5.0 (https://github.com/bevyengine/bevy?rev=f4776f2ec413bb80ff4ee51e04bb57f0a44d9983#f4776f2e)`
    ... which satisfies git dependency `bevy_internal` of package `bevy v0.5.0 (https://github.com/bevyengine/bevy?rev=f4776f2ec413bb80ff4ee51e04bb57f0a44d9983#f4776f2e)`
    ... which satisfies git dependency `bevy` of package `junk_bevy v0.1.0 (/home/figes/Desktop/junk_bevy)`
versions that meet the requirements `^1.0.67` are: 1.0.80, 1.0.79, 1.0.78, 1.0.77, 1.0.76, 1.0.75, 1.0.74, 1.0.73, 1.0.72, 1.0.71, 1.0.70, 1.0.69, 1.0.68, 1.0.67

all possible versions conflict with previously selected packages.

  previously selected package `syn v1.0.65`
    ... which satisfies dependency `syn = "=1.0.65"` of package `bevy v0.5.0`
    ... which satisfies dependency `bevy = "^0.5"` of package `bevy_rapier2d v0.11.0`
    ... which satisfies dependency `bevy_rapier2d = "^0.11.0"` of package `junk_bevy v0.1.0 (/home/figes/Desktop/junk_bevy)`

failed to select a version for `syn` which could resolve this conflict

Additional information
I have tried removing the Cargo.lock and running cargo clean, but that doesn't seem to help.

Looking at the Cargo file  of bevy_rapier they depend on the latest published Bevy version 0.5. You are using the latest commit from GitHub, but there have been quite a few breaking changes since version 0.5 so I would say this is expected not to work. Please try depending on Bevy version 0.5.


Night vision flashing due to short potion effect time

The warning flash that happens when night vision is running out starts at 10 seconds, but with fancy trinkets the potion starts at 13/14 and does not renew till it is lower then 10. Most mods in my pack that add potion effect trinkets, seem to have the potion start at 30 seconds to avoid this

Hmm weird. That didn't happen for me. I'll have to investigate. What version?

Seemed to be a mod interfering, and I was unable to figure out what mod it was, but updating them fixed the issue, so you can probably close this


Webpart sample under folder '02-custom-fields' not getting loaded to workbench.

When I tried to run the webpart project sample for 'custom property pane field using React & Fluent UI' (folder: 02-custom-fields), gulp serve completed successfully but the webpart is not getting loaded to page. Getting the below error.

I haven't made any changes to the project. Just did npm install on the project folder and tried to gulp serve the webpart.

I believe the issue is because of the React version. SPFx v1.19.0 needs React v17.0.1.

Did npm install<EMAIL_ADDRESS><EMAIL_ADDRESS>and boom.. it worked. Successfully wasted my 2 days because of this error. Finding these spfx related errors are really a PIA.


[ROCM]: enable linalg_test.py::test_tridiagonal_solve.

@jakevdp  @hawkinsp Can you please review this?
Thanks!

@hawkinsp @jakevdp  That's one thing we want to get going. That is add a ROCm/AMD CI for JAX. We are also currently working on doing the same on the XLA side.
Please let me know how can we get this started and what's the process.


gulpfile build.prod task wrong html_css

The gulpfile.ts 'build.prod' task contains a 'build.html_css' instead of 'build.html_css.prod'.

Hi @ggaborx,
that is not an error, the file was renamed with this commit 254ccc92ecba1b3d90a334ba4e3cd584858ecb64
Greetings
Christian


Update readme

here's all the bits for the readme.
NB

if you want to 'tidy up' the files will need to edit the action
the roadmap stuff will be added in a future PR

Hurrah! I'm calling that done then


Remove git submodules of algebra, proof-systems and redux-rs

Patch them in Cargo.toml instead

Looks good to me. The failure I see in drone is unrelated to these changes, everything seems to build fine.

@sebastiencs wouldn't it be better to make them  workspace dependencies?

@akoptelov You're right, I will update the PR

@akoptelov I've made them workspace dependencies locally, but that requires some changes to mina-p2p-messages
Cargo.toml.
Could you first merge mina-p2p-messages  into openmina ?
Or we merge this PR as-is and we make workspace dependencies later

@sebastiencs it is already merged, please rebase.

Done, I still patch ark-* crates because we want to override them in all our dependencies tree, including proof-systems


Fix typo in basic k8s example

Hey, I just made a Pull Request!
Simple typo fix - backend service should be conditionally enabled based on .Values.backend.enabled not .Values.app.enabled.
:heavy_check_mark: Checklist

[x] All your commits have a Signed-off-by line in the message. (more info)

Good catch 👍


Roll Plugins from d7125cdb91c0 to 6047b3f1bbb9 (4 revisions)

https://github.com/flutter/plugins/compare/d7125cdb91c0...6047b3f1bbb9
2021-03-18<EMAIL_ADDRESS>Fix cosmetic variations in copyrights and license files (flutter/plugins#3730)
2021-03-18<EMAIL_ADDRESS>Add an AUTHORS file to each plugin (flutter/plugins#3725)
2021-03-18<EMAIL_ADDRESS>[google_sign_in] Adds support to send clientId as a parameter (flutter/plugins#3640)
2021-03-17<EMAIL_ADDRESS>Prep for alignment with Flutter analysis options (flutter/plugins#3703)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-plugins-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Commit queue failed; closing this roll.


consul_connect_enabled not working properly for bootstrap node

https://github.com/dockpack/ansible-consul/blob/master/templates/config.json.j2
    {## Enable Connect on Server ##}
    {% if (item.config_version == 'server') and consul_connect_enabled %}
    "connect": {
        "enabled": true
    },

this block skipped if you explicitly set consul_node_role=bootstrap
now i set consul_node_role=server without specifying bootstrap node (like readme recommends),
but maybe template need to be fixed?

sorry, missed this
https://github.com/dockpack/ansible-consul/pull/370


could not find user in database while running cargo run

Do you want to request a feature or report a bug?
bug
What is the current behavior?
Getting error: thread 'main' panicked at 'connection url's contain enough detail: could not find user in 'postgresql://postgres@localhost:5432/graph-node''
Sep 28 06:40:04.162 INFO Creating transport, capabilities: archive, traces, url: https://mainnet.infura.io/v3/..., provider: mainnet-rpc-0
Sep 28 06:40:04.163 INFO Successfully connected to IPFS node at: http://<IP_ADDRESS>:5001/
Sep 28 06:40:05.199 DEBG Creating firehose networks [1 chains, ingestor default]
Sep 28 06:40:05.199 DEBG Creating firehose networks [1 chains, ingestor default]
Sep 28 06:40:05.199 WARN Expensive queries file not set to a valid file: /etc/graph-node/expensive-queries.txt
Sep 28 06:40:05.199 DEBG Cleaning up large notifications after about 300s, channel: store_events, component: NotificationListener
thread 'main' panicked at 'connection url's contain enough detail: could not find user in `postgresql://postgres@localhost:5432/graph-node`', node/src/store_builder.rs:103:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

while running:
cargo run -p graph-node --release -- \
  --postgres-url postgresql://postgres@localhost:5432/graph-node \
  --ethereum-rpc mainnet:https://mainnet.infura.io/v3/...... \
  --ipfs <IP_ADDRESS>:5001 \
  --debug

It says it couldn't find user in the database but I do see the postgres user when I do:

psql -U postgres
then running \du gives:

                                     List of roles
 Role name |                         Attributes                         | Member of
-----------+------------------------------------------------------------+-----------
 postgres  | Superuser, Create role, Create DB, Replication, Bypass RLS | {}

The error seems to be coming from node/src/store_builder.rs:103:14 according to the error message. Since I don't know rust, I couldn't get any info from that file.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
I have followed all the steps as mentioned in the getting-started.md file, which were:

ipfs init
ipfs daemon
initdb -D .postgres -U postgres
pg_ctl -D .postgres -l logfile start
createdb graph-node -U postgres

logfile:
2022-09-28 07:03:52.858 UTC [5367] LOG:  starting PostgreSQL 14.5 (Ubuntu 14.5-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
2022-09-28 07:03:52.858 UTC [5367] LOG:  listening on IPv6 address "::1", port 5432
2022-09-28 07:03:52.858 UTC [5367] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2022-09-28 07:03:52.885 UTC [5367] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2022-09-28 07:03:52.916 UTC [5371] LOG:  database system was shut down at 2022-09-28 07:03:49 UTC
2022-09-28 07:03:52.933 UTC [5367] LOG:  database system is ready to accept connections

What is the expected behavior?
The graph node should run without error.
Any help on this would be very appreciated.

You're not proving a password in your PostgreSQL endpoint. While the error message says that the user is not found, that's not really the problem. graph-node requires passing a password even if the PG user has no password requirement. Can you try to provide a password e.g. foobar?

Closing this, but please feel free to reopen if the issue persists.


How to integrate in wordpress?

Hello,
I would like to know how I can integrate it in my wordpress website?
Is there something what I need to care of or just put in the js folder?
Exist a plugin for that to minimize the work?
I have a team which is creating content on this page, but it is impossible to tell everyone what they need to put for a code as custom HTML part in the page.
Would be glad if someone could help.
Thanks

Hey @petrk94
All you need to do is:

enqueue this minified script in your theme BEFORE your main script file
put something like var Blazy=new Blazy(); in the beginning of your main script file
add a class "b-lazy" to all images you want to lazyload
replace "src" attributes with "data-src" and add some little dummy image to src attribute
You should end up with something like this:

This image will lazyload just before user scrolls onto it.

@unnamedfeeling is there a tutorial how to make it the right way?
doesnt seems to be easy to realize :/

@petrk94 I personally found tutorials on the official site - http://dinbror.dk/blog/blazy and googled alot to get it working.
Official site did not give me 100% answers for all my questions but it was a good starting point.
My results are - 60MB > 3MB (of initial page size) mostly with the help of this plugin.
You will end up with implementing something like i wrote you about before - give it a try.
Or you could try one of these - https://premium.wpmudev.org/blog/6-lazy-load-plugins-to-make-your-wordpress-site-faster/
I dont know your situation - as for me - plugin was not an option.

 the_title_attribute( array('echo' => false)),
					'class' => 'b-lazy',
					'data-src'=> 'data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw=='
				) );
				?>

<?php 				the_post_thumbnail( 'full', array( 					'alt' => the_title_attribute( array('echo' => false)), 					'class' => 'b-lazy', 					'data-src'=> 'data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==' 				) ); 				?>

As of current time i can tell that using a base64 encoded images as preloaders for many images is bad idea - all of the images are decoded on the fly every time browser loads the page and are not cached. The best way to load transparent image i found is 1x1px gif image - smallest size, lightest impact processor (and paint time) and cacheability.
@zakirsajib src sould be the placeholder and the data-src should contain your placeholder. Your example won`t work((( I ended up on a custom wp-based function for this


Support 12 word mnemonic in ethdo helper script

Because apparently that’s a thing …

Closed with #1303


Send response to server before calling value_updated callback.

Fix error: IOTCLT-566 Retransmission issue when working with payload that is large than CoAP block

Change the name of boolean variable from execute_callback to something like value_updated , which would indicate the flag usage.

LGTM, +1


Add support for other pipelines like TASOC

Lightkurve v2 allows the usage of other pipelines than SPOC. Therefore we can add this support to SHERLOCK.

Done in the next release.


Sqoop import data into hive succeeded,but task instance shows failed!

When I use sqoop import data into hive,the dolphinscheduler log shows success,but the task instance shows failed!

Fellow Worker log.
/dolphinscheduler/install/logs

Fellow Worker log.
/dolphinscheduler/install/logs

It seems that has a error log in dolphinscheduler-worker.log

if it is a single resourcemanager, you only need to configure one host name. If it is resourcemanager HA, the default configuration is fine.
singleYarnIp="ark1"
I find this config in install.sh ,my yarn is HA,so is this right?

It is best to configure both

It is best to configure both

OK,by the way ,if I change this singleYarnIp="cdh201",should I execute the install.sh shell？Or I just need to restart dolphinscheduler?Thank you!

Only restart worker-server.

Modify the yarn.application.status.address of the /opt/dolphinscheduler/conf/common.properties file so that you can just restart the worker.

Modify the yarn.application.status.address of the /opt/dolphinscheduler/conf/common.properties file so that you can just restart the worker.

Now my common.properties has “yarn.application.status.address=http://ark1:8088/ws/v1/cluster/apps/%s
” ，my resourcemanager is HA,I think should change yarn.resourcemanager.ha.rm.ids=cdh201,cdh202,
am I right?

I found this issue can solve this error
https://github.com/apache/incubator-dolphinscheduler/issues/2491

Modify the yarn.application.status.address of the /opt/dolphinscheduler/conf/common.properties file so that you can just restart the worker.
After I set yarn.resourcemanager.ha.rm.ids=cdh201,cdh202,another error happens,even if the sqoop task succeeded!

The worker log ?
It doesn't look like a yarn problem. At present, Sqoop's support does not seem to be very good. It is recommended that you try using a shell to see if the error is reported.

The worker log ?
It doesn't look like a yarn problem. At present, Sqoop's support does not seem to be very good. It is recommended that you try using a shell to see if the error is reported.
The dolphinscheduler-worker.log shows this log.

This seems to be a problem with your sqoop command. It is recommended that you go to the full log of your sqoop command on MAPREDUCE. Generally there will be a complete sqoop execution log.

This seems to be a problem with your sqoop command. It is recommended that you go to the full log of your sqoop command on MAPREDUCE. Generally there will be a complete sqoop execution log.

I have checked the mr sqoop execution log,there is no error.The result of the sqoop task succeeded,but the dolphinscheduler web task instance shows failed!How can I solve this problem?
Thanks a lot!

If you are sure that it is not a sqoop problem but a DS problem, you can try to change the log level of the DS worker to debug. If not, you can only look at the source code.

please check the config of your cloudera-manager
'yarn.resourcemanager.max-completed-applications'
if too small, the appIds's state will not return 'SUCCESS'
then shell task's state is FAILURE.
you can add a checking use historyserver,but you have to check the config:mapreduce.jobhistory.max-age-ms first

please check the config of your cloudera-manager
'yarn.resourcemanager.max-completed-applications'
if too small, the appIds's state will not return 'SUCCESS'
then shell task's state is FAILURE.
you can add a checking use historyserver,but you have to check the config:mapreduce.jobhistory.max-age-ms first
The 'yarn.resourcemanager.max-completed-applications' is 10000.

I met the same error , here the error message
 [taskAppId=TASK-14-45-114]:[189] - Conversion = ';' java.util.UnknownFormatConversionException: Conversion = ';' 	at java.util.Formatter.checkText(Formatter.java:2579) 	at java.util.Formatter.parse(Formatter.java:2565) 	at java.util.Formatter.format(Formatter.java:2501) 	at java.util.Formatter.format(Formatter.java:2455) 	at java.lang.String.format(String.java:2940) 	at org.apache.dolphinscheduler.server.worker.task.AbstractCommandExecutor.isSuccessOfYarnState(AbstractCommandExecutor.java:410) 	at org.apache.dolphinscheduler.server.worker.task.AbstractCommandExecutor.updateState(AbstractCommandExecutor.java:241) 	at org.apache.dolphinscheduler.server.worker.task.AbstractCommandExecutor.run(AbstractCommandExecutor.java:170) 	at org.apache.dolphinscheduler.server.worker.task.shell.ShellTask.handle(ShellTask.java:105) 	at org.apache.dolphinscheduler.server.worker.runner.TaskScheduleThread.run(TaskScheduleThread.java:147) 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 	at java.util.concurrent.FutureTask.run(FutureTask.java:266) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at java.lang.Thread.run(Thread.java:748) [ERROR] 2020-05-21 16:13:40.973  - [taskAppId=TASK-14-45-114]:[107] - shell task failure java.lang.RuntimeException: process error . exitCode is :  -1 	at org.apache.dolphinscheduler.server.worker.task.AbstractCommandExecutor.run(AbstractCommandExecutor.java:190) 	at org.apache.dolphinscheduler.server.worker.task.shell.ShellTask.handle(ShellTask.java:105) 	at org.apache.dolphinscheduler.server.worker.runner.TaskScheduleThread.run(TaskScheduleThread.java:147) 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 	at java.util.concurrent.FutureTask.run(FutureTask.java:266) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at java.lang.Thread.run(Thread.java:748) [ERROR] 2020-05-21 16:13:40.973 org.apache.dolphinscheduler.server.worker.runner.TaskScheduleThread:[153] - task scheduler failure java.lang.RuntimeException: process error . exitCode is :  -1 	at org.apache.dolphinscheduler.server.worker.task.AbstractCommandExecutor.run(AbstractCommandExecutor.java:190) 	at org.apache.dolphinscheduler.server.worker.task.shell.ShellTask.handle(ShellTask.java:105) 	at org.apache.dolphinscheduler.server.worker.runner.TaskScheduleThread.run(TaskScheduleThread.java:147) 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 	at java.util.concurrent.FutureTask.run(FutureTask.java:266) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at java.lang.Thread.run(Thread.java:748) [INFO] 2020-05-21 16:13:40.974  - [taskAppId=TASK-14-45-114]:[262] - cancel process: 28845 [INFO] 2020-05-21 16:13:40.986 org.apache.dolphinscheduler.server.worker.runner.TaskScheduleThread:[161] - task instance id : 114,task final status : FAILURE

I met the same error , here the error message
 [taskAppId=TASK-14-45-114]:[189] - Conversion = ';' java.util.UnknownFormatConversionException: Conversion = ';' at java.util.Formatter.checkText(Formatter.java:2579) at java.util.Formatter.parse(Formatter.java:2565) at java.util.Formatter.format(Formatter.java:2501) at java.util.Formatter.format(Formatter.java:2455) at java.lang.String.format(String.java:2940) at org.apache.dolphinscheduler.server.worker.task.AbstractCommandExecutor.isSuccessOfYarnState(AbstractCommandExecutor.java:410) at org.apache.dolphinscheduler.server.worker.task.AbstractCommandExecutor.updateState(AbstractCommandExecutor.java:241) at org.apache.dolphinscheduler.server.worker.task.AbstractCommandExecutor.run(AbstractCommandExecutor.java:170) at org.apache.dolphinscheduler.server.worker.task.shell.ShellTask.handle(ShellTask.java:105) at org.apache.dolphinscheduler.server.worker.runner.TaskScheduleThread.run(TaskScheduleThread.java:147) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) [ERROR] 2020-05-21 16:13:40.973 - [taskAppId=TASK-14-45-114]:[107] - shell task failure java.lang.RuntimeException: process error . exitCode is : -1 at org.apache.dolphinscheduler.server.worker.task.AbstractCommandExecutor.run(AbstractCommandExecutor.java:190) at org.apache.dolphinscheduler.server.worker.task.shell.ShellTask.handle(ShellTask.java:105) at org.apache.dolphinscheduler.server.worker.runner.TaskScheduleThread.run(TaskScheduleThread.java:147) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) [ERROR] 2020-05-21 16:13:40.973 org.apache.dolphinscheduler.server.worker.runner.TaskScheduleThread:[153] - task scheduler failure java.lang.RuntimeException: process error . exitCode is : -1 at org.apache.dolphinscheduler.server.worker.task.AbstractCommandExecutor.run(AbstractCommandExecutor.java:190) at org.apache.dolphinscheduler.server.worker.task.shell.ShellTask.handle(ShellTask.java:105) at org.apache.dolphinscheduler.server.worker.runner.TaskScheduleThread.run(TaskScheduleThread.java:147) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) [INFO] 2020-05-21 16:13:40.974 - [taskAppId=TASK-14-45-114]:[262] - cancel process: 28845 [INFO] 2020-05-21 16:13:40.986 org.apache.dolphinscheduler.server.worker.runner.TaskScheduleThread:[161] - task instance id : 114,task final status : FAILURE

Which version do you use? It's better to take a screenshot of some more logs

DS version : 1.2.1
Hadoop version: hdp 2.7.3 installed with ambari
maybe yarn resources web analysis error

please check worker logs for this sqoop job. when sqoop job finished, ds-worker will check the yarn app status through yarn apis. So you should check the yarn conf in dolphinscheduler. single yarn ip or yarn HA ips in dolphinscheduler/conf


MatPaginator page select expands the wrong direction

Bug, feature request, or proposal:
When resizing the browser, the MatSelect in the MatPaginator can expand outside of the visible part of the page (expanding to the bottom)
What is the expected behavior?
The MatSelect should expand to the top instead
What is the current behavior?
It expands to the bottom and gets out of browser bounds
What are the steps to reproduce?

Open this blitz: https://stackblitz.com/angular/godjgllxvxr?file=app%2Ftable-pagination-example.ts
Ensure there is some blank space below the MatTable when loading the preview
Click a first time on the MatSelect in the MatPaginator
Resize the preview to set the browser limit just below the MatTable
Try to open the MatSelect again : it displays itself to the bottom instead of the top

What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Running:
Windows 7 64bits
Chrome 65
@angular 5.2.10
@angular/material 5.2.4
Is there anything else we should know?

Thanks for reporting, it is an issue but has been fixed. See this issue for more details: #10560


Move Generate Payment Request feature

You can move Generate Payment Request feature to the bottom menu. Right now it's very hard to find.

Which version of AW is this? Is the Moonpay version that was copied onto the testing forum? AFAIK the code hasn't been committed. If it's on the Moonpay branch then I'll re-assign it to Justin.

@justindg is this from the payment request branch you're working on?

Update:
@mpaschenko Currently when you open "My Wallet Address" screen you will see an icon in the top right corner. This is to trigger "Generate Payment Request".

Remove this feature from that place, instead use the additional menu in Ether token.

Just add "Generate Payment Request" at the top or bottom of "Buy ETH"


maximal lending duration fixed categories

User stories
As a lender I want to have default maximal lending durations
in order to reduce the number of steps when creating an Item
Dependencies
none
UI Mockup

Acceptance Criteria

[ ] possibility of changing maximal lending duration
[ ] dropdown options are: infinite (default), 2 mon, 1 mon, 2 week, 1 week, custom
[ ] when custom is selected you should be able to enter a custom number of days
[ ] should get displayed on item view

changed to #220


Add support to reset attempts on the cache handler

Fixes #454
Line 40 in axes/handlers/cache.py could be replaced with cache.clear() - but seems like a bad idea if a shared cache is being used - the default, for example.

Good looking PR, thank you! CI seems to be failing due to unsupported Django versions, let's upstream and fix that in the main branch.

Line 40 in axes/handlers/cache.py could be replaced with cache.clear() - but seems like a bad idea if a shared cache is being used - the default, for example.

One option would be to fetch all keys by prefix, if that is supported by the cache backend, but afaik only some cache backends have that feature baked in, so it wouldn't be possible to use unless it is supported (documented) feature in Django.

Released in version 5.13.0.


Add switchable color theme with cache

For GitHub API rate limit

:tada: This issue has been resolved in version utterances-react-component-v1.1.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Deleted Maths module-4

Trial-1

@SanidhyaDakhera The pr looks good, Just add a little informative description as a good practise.


Compile without LTO for symbol sizes

Change linker script flash size and make file optimization flags to compile without sacrificing app symbol sizes in map file.
Compile with make firmware and search through map file for app symbol names by searching for string 'ZN'.
Format of map file lines of interest:    .text._    0x    0x


replace hardcode dummy data with real values

We have currently hardcoded the values for usernames and other sound data like duration:

This task outlines replacing these values with the actual ones. See the freesound-client Sound API page for which values you can replace the values with. Should be something as simple as {track.duration} in SoundList.js

Fixed


CTD on tactical reload

Another day, another useless weapon pack.
Only this time it broke the reloads of shell-fed shotguns, as well as any other gun with an interruptible reload like the Repeater and Peacemaker.
Application has crashed: C++ exception
mods/IRE AND FIST REBORN/lua/newraycast.lua:704: attempt to call upvalue 'old_reload_exit_ne_expire' (a nil value)
SCRIPT STACK
_update_reload_timers() @mods/IRE AND FIST REBORN/lua/playerstandard.lua:729
_update_check_actions() lib/units/beings/player/states/playerstandard.lua:883
original() lib/units/beings/player/states/playerstandard.lua:441
update_original() @mods/base/req/core/Hooks.lua:288
update() @mods/IRE AND FIST REBORN/lua/BurstFire.lua:350
original() lib/units/beings/player/playermovement.lua:272
@mods/base/req/core/Hooks.lua:288

The crash occurs when the last round is about to be loaded. Dry reloads seem to work fine (for now, at least).

Which mod does this happen with, exactly?

I meant to refer to the new DLC weapon pack that just came out. I should've been clearer on that, my bad.

Ah I see, interesting. Will get on it soon.

having the same issue. any firearm with an interrupt to the reload, such as tube-fed shotguns, the Colt SAA, etc, crash after loading the first 1-2 rounds/shells in.