document update needed

Missing description for  'Messaging > Immersive   reader for messages"
There is no org-wide settings group on TAC. This was moved to the 'Users' menu group
The content reference and pictures might need updating

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

ID: 042d7ce6-ee22-690f-8188-ff8a4a585847
Version Independent ID: 3e5bc99c-e08e-44e0-cda3-687ed3633175
Content: Turn on or turn off guest access to Microsoft Teams - Microsoft Teams
Content Source: Teams/set-up-guests.md
Service: msteams
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

@TheITguy666 thanks for pointing this out. Are you suggesting the screenshot needs to be updated?

This is the picture on the documentation where with Org-wide:
[cid:86837174-2bb5-44e0-bc5f-d76fb8771e2a]
And since last week is on the Users menu
[cid:9e5c9e10-d409-4fb7-a5a2-f6904ef963f2]

From: Lindsay @.>
Sent: Tuesday, September 28, 2021 11:09 AM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness @.>
Cc: Luis @.>; Mention @.>
Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] document update needed (#7907)
@TheITguy666https://github.com/TheITguy666 thanks for pointing this out. Are you suggesting the screenshot needs to be updated?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/7907#issuecomment-929003252, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANWXS2RJXT3FTBCS5KPTIVLUEGA4XANCNFSM5E22PFBA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

This is the picture on the documentation where with Org-wide: [cid:86837174-2bb5-44e0-bc5f-d76fb8771e2a] And since last week is on the Users menu [cid:9e5c9e10-d409-4fb7-a5a2-f6904ef963f2]
…
________________________________ From: Lindsay @.> Sent: Tuesday, September 28, 2021 11:09 AM To: MicrosoftDocs/OfficeDocs-SkypeForBusiness @.> Cc: Luis @.>; Mention @.> Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] document update needed (#7907) @TheITguy666https://github.com/TheITguy666 thanks for pointing this out. Are you suggesting the screenshot needs to be updated? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#7907 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANWXS2RJXT3FTBCS5KPTIVLUEGA4XANCNFSM5E22PFBA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thanks @TheITguy666 I'm unable to see your photos you posted here. @tiburd please can you assist to get the correct images added.

@TheITguy666 @lindspea Hi - I sent email to the author regarding this.


docs: Add doc for scanners that report individual layers

Describe the changes in this pull request using active verbs such as Add, Remove, Replace ...
Closes #764

will update version docs after the change is reviewed


RIFEX-58 Fixing node version

Current node version on package.json is not working, basically throws a bunch of errors, that's because node version was updated but not the dependencies

This affects the compilation process on the project

Wrong repo

Fixing repo


How to install?

Can I have instructions on how to install your script?

Do you mean self host?
Clone this repo, then go to https://vercel.com/new
Thant's all


Initial training speed extreemly (~100x) slow for generated data, and become faster and faster as each epoch progress

Click to expand!
Issue Type
Performance
Have you reproduced the bug with TF nightly?
No
Source
source
Tensorflow Version
2.8.0
Custom Code
No
OS Platform and Distribution
Ubuntu 18.04.5 LTS
Mobile device
No response
Python version
3.9.1
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
CUDA 11.1
GPU model and memory
GeForce GTX TITAN X, 12G
Current Behaviour?
My code is roughly like this:
  for i in range(data_n):
    if not train_data[i].npz exists:
      data = generate train_data[i].npz and save to disk
    else:
      data = read train_data[i].npz from disk

    model.fit(data)

data_n = 26,  when i less than ~20, everything is normal.
as i reach about 20, something strange start to happen:
I found if the data.npz is generated, the initial training speed is very slow, e.g ~x100 slower than the normal speed (when directly read from .npz file), and as the training Epoch progress, it become faster and faster, until it eventually runs full power on GPU, e.g.
_________________________________________________________________
Epoch 1/1000
732/732 [==============================] - 1524s 2s/step - loss: 3.0771 - accuracy: 0.2212 - val_loss: 3.0802 - val_accuracy: 0.2265
Epoch 2/1000
732/732 [==============================] - 931s 1s/step - loss: 3.0538 - accuracy: 0.2246 - val_loss: 3.0623 - val_accuracy: 0.2303
Epoch 3/1000
732/732 [==============================] - 833s 1s/step - loss: 3.0434 - accuracy: 0.2261 - val_loss: 3.0663 - val_accuracy: 0.2298
Epoch 4/1000
732/732 [==============================] - 757s 1s/step - loss: 3.0339 - accuracy: 0.2275 - val_loss: 3.0618 - val_accuracy: 0.2309
Epoch 5/1000
732/732 [==============================] - 663s 906ms/step - loss: 3.0316 - accuracy: 0.2279 - val_loss: 3.0692 - val_accuracy: 0.2297
Epoch 6/1000
732/732 [==============================] - 572s 782ms/step - loss: 3.0254 - accuracy: 0.2288 - val_loss: 3.0683 - val_accuracy: 0.2298
Epoch 7/1000
732/732 [==============================] - 406s 555ms/step - loss: 3.0201 - accuracy: 0.2291 - val_loss: 3.0638 - val_accuracy: 0.2305
Epoch 8/1000
732/732 [==============================] - 367s 502ms/step - loss: 3.0148 - accuracy: 0.2301 - val_loss: 3.0595 - val_accuracy: 0.2289
Epoch 9/1000
732/732 [==============================] - 321s 439ms/step - loss: 3.0098 - accuracy: 0.2311 - val_loss: 3.0599 - val_accuracy: 0.2299
Epoch 10/1000
732/732 [==============================] - 304s 416ms/step - loss: 3.0058 - accuracy: 0.2318 - val_loss: 3.0608 - val_accuracy: 0.2301
Epoch 11/1000
732/732 [==============================] - 286s 391ms/step - loss: 3.0053 - accuracy: 0.2317 - val_loss: 3.0562 - val_accuracy: 0.2320
Epoch 12/1000
732/732 [==============================] - 268s 366ms/step - loss: 3.0010 - accuracy: 0.2315 - val_loss: 3.0563 - val_accuracy: 0.2323
Epoch 13/1000
732/732 [==============================] - 252s 345ms/step - loss: 3.0003 - accuracy: 0.2320 - val_loss: 3.0518 - val_accuracy: 0.2332
Epoch 14/1000
732/732 [==============================] - 233s 319ms/step - loss: 2.9963 - accuracy: 0.2321 - val_loss: 3.0488 - val_accuracy: 0.2315
Epoch 15/1000
732/732 [==============================] - 217s 296ms/step - loss: 2.9926 - accuracy: 0.2326 - val_loss: 3.0515 - val_accuracy: 0.2329
Epoch 16/1000
732/732 [==============================] - 198s 271ms/step - loss: 2.9881 - accuracy: 0.2341 - val_loss: 3.0514 - val_accuracy: 0.2327
Epoch 17/1000
732/732 [==============================] - 181s 247ms/step - loss: 2.9883 - accuracy: 0.2326 - val_loss: 3.0527 - val_accuracy: 0.2333
Epoch 18/1000
732/732 [==============================] - 165s 226ms/step - loss: 2.9868 - accuracy: 0.2338 - val_loss: 3.0496 - val_accuracy: 0.2307
Epoch 19/1000
732/732 [==============================] - 153s 209ms/step - loss: 2.9831 - accuracy: 0.2333 - val_loss: 3.0438 - val_accuracy: 0.2336
Epoch 20/1000
732/732 [==============================] - 137s 187ms/step - loss: 2.9817 - accuracy: 0.2338 - val_loss: 3.0442 - val_accuracy: 0.2330
Epoch 21/1000
732/732 [==============================] - 123s 168ms/step - loss: 2.9779 - accuracy: 0.2340 - val_loss: 3.0434 - val_accuracy: 0.2344
Epoch 22/1000
732/732 [==============================] - 113s 154ms/step - loss: 2.9789 - accuracy: 0.2344 - val_loss: 3.0370 - val_accuracy: 0.2341
Epoch 23/1000
732/732 [==============================] - 102s 139ms/step - loss: 2.9743 - accuracy: 0.2351 - val_loss: 3.0392 - val_accuracy: 0.2356
Epoch 24/1000
732/732 [==============================] - 93s 127ms/step - loss: 2.9777 - accuracy: 0.2349 - val_loss: 3.0517 - val_accuracy: 0.2336
Epoch 25/1000
732/732 [==============================] - 82s 112ms/step - loss: 2.9716 - accuracy: 0.2352 - val_loss: 3.0279 - val_accuracy: 0.2369
Epoch 26/1000
732/732 [==============================] - 79s 107ms/step - loss: 2.9709 - accuracy: 0.2351 - val_loss: 3.0363 - val_accuracy: 0.2348
Epoch 27/1000
732/732 [==============================] - 67s 92ms/step - loss: 2.9672 - accuracy: 0.2354 - val_loss: 3.0344 - val_accuracy: 0.2343
Epoch 28/1000
732/732 [==============================] - 55s 75ms/step - loss: 2.9664 - accuracy: 0.2350 - val_loss: 3.0418 - val_accuracy: 0.2337
Epoch 29/1000
732/732 [==============================] - 45s 62ms/step - loss: 2.9690 - accuracy: 0.2356 - val_loss: 3.0439 - val_accuracy: 0.2340
Epoch 30/1000
732/732 [==============================] - 32s 44ms/step - loss: 2.9639 - accuracy: 0.2364 - val_loss: 3.0333 - val_accuracy: 0.2350
Epoch 31/1000
732/732 [==============================] - 28s 39ms/step - loss: 2.9631 - accuracy: 0.2362 - val_loss: 3.0373 - val_accuracy: 0.2353
Epoch 32/1000
732/732 [==============================] - 28s 38ms/step - loss: 2.9626 - accuracy: 0.2368 - val_loss: 3.0391 - val_accuracy: 0.2343
Epoch 33/1000
732/732 [==============================] - 26s 36ms/step - loss: 2.9598 - accuracy: 0.2355 - val_loss: 3.0339 - val_accuracy: 0.2356
Epoch 34/1000
732/732 [==============================] - 26s 35ms/step - loss: 2.9581 - accuracy: 0.2368 - val_loss: 3.0337 - val_accuracy: 0.2349
Epoch 35/1000
732/732 [==============================] - 25s 35ms/step - loss: 2.9601 - accuracy: 0.2366 - val_loss: 3.0306 - val_accuracy: 0.2363

As you can see, the 1st epoch took 1524s, while the 35th epoch took 25s; if the data is directly read from .npz an epoch took consistent ~18s.
Could this be a TF memory issue ? or it's a Python issue?
How and where I can debug such issue? or any suggestions I can try to improve the speed?
Thanks.
Standalone code to reproduce the issue
# My code is roughly like this:

  for i in range(data_n):
    if not train_data[i].npz exists:
      data = generate train_data[i].npz and save to disk
    else:
      data = read train_data[i].npz from disk

    model.fit(data)

### Relevant log output

_No response_</details>

Hi @mw66
Apologies for the delay. In order to expedite the trouble shooting process, please share complete reproducible code. Thank you!

It's hard to add a test case, but just want to add it could be related to memory/disk swapping in a long running jib. So is there a way in Python before each epoch to ensure that trainX and trainY are in memory?


Configure Timeout for XmlHttpRequest to prevent 504 Gateway Timeout

Some of APIs requires longer time to run (can reach upto 3 minutes). In Swagger UI, it times out the request while server is still processing the request and completes it.
Is there a way to configure timeout for API calls before swagger shows 504 timeout issue?

Is this project still being maintained?

It's absolutely being maintained but it's also done for free by volunteers. There's no SLA on responses and most of the work is peoples' free time. The best way to get help is to try helping yourself - submit a PR with the changes required for your request.

This is a UI concern. Swashbuckle leverages the swagger-ui but doesn't maintain it. So, if this is still causing issues for you, I recommend you submit an issue to the swagger-ui repo.
Alternatively, you could consider breaking down your documentation into multiple Swagger documents that can be navigated via a drop down in the swagger-ui. See the following readme sections for more details:
https://github.com/domaindrivendev/Swashbuckle.AspNetCore#generate-multiple-swagger-documents
https://github.com/domaindrivendev/Swashbuckle.AspNetCore#list-multiple-swagger-documents

This was never fixed by the way - can we please reopen it

Read the above comment


Pass in Hard Drives?

Can hard drives be passed in like a real DSM or can only paths be passed in?  Does that mean the host operating system needs to manage the hard drives?

The only thing I can think of is if you want to transfer real DSM drives to virtual dsm.

That's a good compromise.  Thanks.


update .gitignore and add setting.json

Create pull  request
Signed-off-by: caiyan.cai<EMAIL_ADDRESS>Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Additional context

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


fix: icon button should be disabled while loading

Description
Icon button should be disabled once clicked, just like the standard button.
Noticed the issue when a customer double-clicked on an icon-button to create an option from a form select component: the modal form is opened twice and the validation process fails.
Visual changes
None
Functional changes

[x] Code style has been fixed by running the composer cs command.
[x] Changes have been tested to not break existing functionality.
[ ] Documentation is up-to-date.

Good catch, thanks


fix: Forced refresh async queries are executed synchronously

SUMMARY

Deleted a cache check for async queries when cache is forced.
Attached screenshots (please, see below) to demonstrate logs that show expected behaviour after the change.
Fixes https://github.com/apache/superset/issues/24889
Context:
When chart data is forced to refresh in chart view, query is executed in synchronous manner, even when GLOBAL_ASYNC_QUERIES=True.
Expected results
Superset should:

Request chart data (POST /api/v1/chart/data?form_data=<fomr_data>)
Poll for results (GET /api/v1/async_event/?last_id=<last_id>)
Get results (GET /api/v1/chart/data/<cache_key>)

Actual results:
Superset sends POST /api/v1/chart/data and waits for that request to return results.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

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

@zhaoyongjie would you mind reviewing this? It seems, per here, that you may have authored this logic.

@zhaoyongjie would you mind reviewing this? It seems, per here, that you may have authored this logic.

Let me catch up the change....thanks for the mention.

Thanks for the review @zhaoyongjie - would love to get this merged so we can close https://github.com/apache/superset/issues/24889, which has been open for a long time.

Till we figure out a better solve
Moved the cache lookup behind an if statement checking the value of force


Split sounds into single knock

I split your main sound files into several knock sound files, now punching a door make only one random knock.
I think this gives a better feeling.

If you accept this PR, just note that I forgot to change the mod version in the gradle.properties

Hey @MokkaCicc! This change would also be very much welcome on the unofficial forge port of the mod. :D
https://github.com/ZandercraftGames/Door-Knocker-Forge

@ZandercraftGames I never touch a Forge mod in my life, I will maybe do it but this is not my top priority now. But since it's a fairly simple PR (split two sound files and modify a json file), I think you are capable to do it. You can reuse the split I made if you want to implemente this feature faster.

@ZandercraftGames I never touch a Forge mod in my life, I will maybe do it but this is not my top priority now. But since it's a fairly simple PR (split two sound files and modify a json file), I think you are capable to do it. You can reuse the split I made if you want to implemente this feature faster.

Oh, I'm definitely capable of doing it. The reason why I ask is so that you can get credit for your contribution by having your name on the commits.

@MokkaCicc Feature has been added to the Forge port and credit has been given :D
https://github.com/ZandercraftGames/Door-Knocker-Forge/pull/2

@ZandercraftGames Sweet!

Merged


Review.

I couldn't resist to change the indentation to 2 spaces. (Switch to "ignore whitespace" in the diff-view).
I tried to be picky. Partially, to show some nice tricks (like DUR0 < dur < DUR30), and partially to give an idea of the style we would like to see.
All in all a nice program!

Hi Florian,
Great, thanks for the improvements. I realised I'd left the external
address of my MQTT broker in the code so I have removed it. :oD
I'm now running the code as per Github on the clock...
Cheers
John

On 28/05/2022 16:01, Florian Loitsch wrote:

I couldn't resist to change the indentation to 2 spaces. (Switch to
"ignore whitespace" in the diff-view).
I tried to be picky. Partially, to show some nice tricks (like |DUR0 <
dur < DUR30|), and partially to give an idea of the style we would
like to see.
All in all a nice program!
—
Reply to this email directly, view it on GitHub
https://github.com/lazyoldjack/wallclock/pull/1#issuecomment-1140279549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFADTMSEM6S2Z4BFDAOU2LLVMIYNNANCNFSM5XGYCEFA.
You are receiving this because you are subscribed to this
thread.Message ID: @.***>

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Ft send mail 164785625

What this PR does?

Creates user able to send an email message to an individual
Add tests for user send email
Modifies README.MD file

Tasks completed

updating my message model class
controller logic for sending an email message
Creating the endpoint resource
Tested the endpoint with the postman app
writing tests for the endpoint

How should this be tested?

After cloning the repo, checkout ft-create-or-send-email-164785625 branch, run server by; python run.py and test the following endpoints
POST/api/v1/auth/signup
{"firstname": "firstname", "lastname": "lastname", "email": "email", "password": "password" }
POST/api/v1/auth/login
{" "email": "email", "password": "password" }
POST/api/v1/messages
{"subject": "subject", "message": "message", "receiver": "receiver", "ParentMessageID":"parentMessageId"}

Run tests by pytest or pytest --cov

Pivotal stories attached to the PR
[#164785625, user able to send an email message]
kindly review and give me feedback on necessary improvements
@Emmanuelaaron, @alexxsanya, @nakimera, @kyakusahmed, @neelxie @nanfuka @Wabuluka

Would you remove the commented out code

I shared a resource on the channel that could help you improve your commit messages moving forward

I removed the comments on my latest work and it now up to date on develop branch.
For commit messages, I have read the resource and improving on it in my next commits. Thanks alot


ci(.github/workflows): remove ruby and pact, add race for test

:heavy_check_mark: Checklist:

[x] Have only one commit (if not, squash them into one commit)
[ ] Tests for the changes have been added (for features / bug fixes / refactoring)

Codecov Report

Merging #243 (8379eeb) into main (da87702) will increase coverage by 6.20%.
The diff coverage is 65.85%.

@@            Coverage Diff             @@
##             main     #243      +/-   ##
==========================================
+ Coverage   66.84%   73.04%   +6.20%
==========================================
  Files          10       15       +5
  Lines         368      564     +196
==========================================
+ Hits          246      412     +166
- Misses        111      120       +9
- Partials       11       32      +21

Impacted Files
Coverage Δ

internal/api/find.go
0.00% <0.00%> (ø)

internal/config/config.go
100.00% <ø> (ø)

internal/openapi3/parse.go
37.83% <38.88%> (+3.22%)
:arrow_up:

internal/openapi3/build.go
54.23% <54.23%> (ø)

internal/openapi3/openapi3.go
60.00% <60.00%> (ø)

internal/api/apischema.go
73.33% <73.33%> (ø)

internal/openapi3/schema.go
75.00% <75.00%> (ø)

internal/faker/faker.go
96.92% <100.00%> (+1.64%)
:arrow_up:

internal/logger/logger.go
100.00% <100.00%> (ø)

internal/openapi3/example.go
100.00% <100.00%> (ø)

... and 6 more

Continue to review full report at Codecov.

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


Virtual keyboard labels v2

Adjusting the Virtual Keyboard to display notes info into V2.
Note: It was not possible to display labels because it looks like the V2 doesn't have this feature.

The state from v2 doesn't same the same pros as v3, I will need to finish the adjustments later.

@frostburn Would you mind reviewing this v2 backport? Thanks

SW2 doesn't have user-defined labels, but it does have names. See how TuningTable.vue populates the name field of TuningTableRow.vue.

Looking good in general. :+1:

@frostburn I have added the required adjustments. Thanks


fix: make full_registration on default operator

Description
Fixes the operator_full_registration command which was broken in the operator_whitelist step because the OPERATOR_ADDRESS was not being loaded from the config. The fix conditionally loads OPERATOR_ADDRESS from the config file if the OPERATOR_ADDRESS is not explicitly provided.
Type of change
Please delete options that are not relevant.

[ ] New feature
[ ] Bug fix
[ ] Optimization
[ ] Refactor

Checklist

[ ] “Hotfix” to testnet, everything else to staging
[ ] Linked to Github Issue
[ ] This change depends on code or research by an external entity

[ ] Acknowledgements were updated to give credit

[ ] Unit tests added
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

[ ] This change is an Optimization

[ ] Benchmarks added/run

[ ] Has a known issue

Link to the open issue addressing it

[ ] If your PR changes the Operator compatibility (Ex: Upgrade prover versions)

[ ] This PR adds compatibility for operator for both versions and do not change batcher/docs/examples
[ ] This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible

Closing this one in favour of #1544.


File is corrupted if i download it when validateResponse is true

I made an api with an endpoint that returns/download a file (application/pdf for now)
But when i download the file and open it it's corrupted, however when i disable validateResponse in swaggerValidator middleware the file will be downloaded perfectly ! it seems like this middleware is altering the response
Is there a way to fix this?

make sure the header sets:
res.setHeader('Content-Length', file.size);
res.setHeader('Content-Type', 'application/pdf');
res.setHeader('Content-Disposition', 'attachment; filename=file.pdf')
If it still not work, you can try to update your swagger-ui version to 3.0.0+


Modified projectile knockback is ignored when hitting NPCs

Description
Modifying knockback in any of these hooks has no effect:
ModProjectile.ModifyHitNPC
GlobalProjectile.ModifyHitNPC
ModNPC.ModifyHitByProjectile
GlobalNPC.ModifyHitByProjectile
ModPlayer.ModifyHitNPCWithProj
Steps to Reproduce

Have a GlobalProjectile that overrides ModifyHitNPC
In ModifyHitNPC, always set knockback to 0

Expected behavior
NPCs should no longer experience knockback from any projectiles.
Actual behavior
NPCs are still knocked back by projectiles.
Reproduction frequency
Always
Versions
v0.10.1
v<IP_ADDRESS>
Mods
None (Except a Test mod made to reproduce this issue)
Additional Information
This is most definitely caused by a typo, as the calls to StrikeNPC and StrikeNPCNoInteraction in Projectile.Damage both use the instance variable Projectile.knockBack, instead of the local variable knockback.

Yep, seems to be a typo. Thanks, should be an easy enough fix.

It looks like there's 2 variables knockback and knockBack (this.knockBack, whereas knockback is local and adjustable), notice the capital letter. So yes, you are right.


BUG: Docker image creation fails due to missing "libarchive"

Describe the bug
A missing binary library causes docker image creation to fail
To Reproduce
docker build . --file Dockerfile
Expected behavior
Succesful build.
Screenshots

Github action is still failing although my local test succeeds. More efforts is needed... :(
https://github.com/NRCan/geo-deep-learning/actions/runs/6151233995/job/16691513798


add installify

would be cool to be able to put installify in the repo and like have auto installs all over the place. Yeah that'd be cool C:

https://github.com/hughsk/installify

maybe

(if you do add it, make it optional?)

yeah that sounds alright hah (:

ok nah not gonna do this I think


Wang Tiles support for Autotile

I love the way new autotile system works but currently I'm working on a top-down RPG game which would really benefit from having a possibility to specify multiple tile types in one autotile. So I think that adding the Wang tiles system to autotile could be really useful.
I won't go into describing the system here because the best description is on this website: http://www.cr31.co.uk/stagecast/wang/intro.html

I would like to see the implementation of Wang tiles as in Tiled. (3х3 Wang tiles)

I would like to see the implementation of Wang tiles as in Tiled. (3х3 Wang tiles)

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


fix: Elasticsearch index settings - ignore-malformed

See
https://www.elastic.co/guide/en/elasticsearch/reference/7.17/ignore-malformed.html

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.858%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5215

Relevant Lines:
6074

💛  - Coveralls


forced to log in to the game to access spreadsheet

Not sure if it's intentional but in a previous version, I can access the spreadsheet by just running the app without logging into the game.

It's intentional.


Filter NAD by namespace when creating new nic raw

When getting network resource for a nic we want to filter it by namespace.
Currently we filter by namespace on the web-ui-component side [1] but we may want to remove this filter for cases that do not have a namespace.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1687917
[1] https://github.com/kubevirt/web-ui-components/pull/316

@rawagner Thanks for finding the issue that caused the bug :100: ,
As you suggested off line the bug happen when we filter by missing namespace, In this PR I'm trying to filter by namespace on the UI side.
Does that make sense, do we need this, can it break something eles ?

@yaacov filtering on web-ui side is great! I do not think it will break anything

@suomiy @rawagner applied the namespace refactor, please re review.


When a screen status is set for a submission, remove the button "Screen application" button from "Actions to take", and add a smaller link in the "Screening status" box for "Change status"

Buttons should not move around. I will move it permanently to the "Screening status" box. Can change the label on the button depending on if it have been screened or not.

Glad to start here.


Remove serve-static from direct dependencies

Notice the lockfile doesn't change because serve-static is still an indirect dependency via express framework.
Fixes #25

Hi @atz, if your can rebase this branch, I'll merge this PR into master.
Thanks,
Jeremh


Add EIA860, EIA860m, & EIA923 2022 early release data

PR Overview
This includes: adding new zenodo doi archive values, adding the new year of data to fast and full etl yml files, add the new year to the working_partitions in the metadata, update the package data, fix encoding errors, update validation tests for row count.
PR Checklist

[ ] Merge the most recent version of the branch you are merging into (probably dev).
[ ] All CI checks are passing. Run tests locally to debug failures
[x] Make sure you've included good docstrings.
[x] For major data coverage & analysis changes, run data validation tests
[x] Include unit tests for new functions and classes.
[x] Defensive data quality/sanity checks in analyses & data processing functions.
[x] Update the release notes and reference reference the PR and related issues.
[ ] Do your own explanatory review of the PR to help the reviewer understand what's going on and identify issues preemptively.

Lingering things / findings that will be made into new issues once this is merged:

The need to lower case things
A check that upper cases encoding stuff

also do you know why the tests failed? it looks like they were stopped but pretty late in the process?

I think they failed because now the fast tests include three years of data instead of two to accommodate the lack of FERC data and that was too heavy a lift for the ci.

hmmm if the ci will fail with three years of data then we need a new solution. can we duplicate some ferc-eia training data for the new year? it doesn't have to be a full duplication of the last year of training data. even a few records would suffice i think.

Have you been able to run the full ETL and data validations locally? Always hard to evaluate these big updates to the CSVs.

Yes!


1:1 checkin meetings in the lab

Kirstie & Aida - Wednesdays every 2 weeks
Kirstie & Arielle - Wednesdays every 2 weeks
Kirstie & Malvika - Mondays every 2 weeks
Kirstie & Georgia - Wednesdays every 2 weeks
Kirstie & Maria - Thursdays every 2 weeks
Kirstie & Emma - Mondays every week
Kirstie & Ismael - Tuesdays every 2 weeks
Kirstie & Sarah - ad hoc, tbc
Kirstie & Sophia - ad hoc, tbc
Kirstie & Isla - ad hoc, tbc
Kirstie & Maxine - ad hoc, tbc
Kirstie & Patricia - ad hoc, tbc
Kirstie & Laura - ad hoc, tbc

Arielle & Patricia - Mondays every 2 weeks

Arielle & Malvika every 2 weeks on Thursdays + community co-working as desired 🦩

Aida & Sarah - Wednesdays every 2 weeks
Minutes here #441

Aida and I will be taking a break from mentoring sessions while I transition roles and enjoy my down-time. Sessions due to restart on 24th June.


Issue with MacDown

Received message that macdown file was corrupted and could not be run.
Installed from both Homebrew and downloaded  zip file.
Macbook Air
Mac OS Mojave 10.14.5

Hi @davidmichael47! I think you might have filed this in the wrong place. This is the repository for the Markdown Guide docs only. The GitHub repo for MacDown is over at https://github.com/MacDownApp/macdown — I'm sure they'll be able to help you over there. Thanks, and good luck.


Modified the create post form

Resolves issue #123 .
here is the result.

@Aarav238 please change the background color of the card and also make it more appealing

Because of no respone from your side for more than 2 weeks, closing the pr.


Fix random bugs

Actually just fixed a bunch of the remaining bugs from PE-D.

Fixes #183
Fixes #167
Fixes #197
Fixes #198
Fixes #199

Codecov Report

Merging #262 (6cb374c) into master (270492e) will not change coverage.
The diff coverage is 83.33%.

@@            Coverage Diff            @@
##             master     #262   +/-   ##
=========================================
  Coverage     65.21%   65.21%
  Complexity      604      604
=========================================
  Files            93       93
  Lines          2199     2199
  Branches        271      271
=========================================
  Hits           1434     1434
  Misses          687      687
  Partials         78       78

Impacted Files
Coverage Δ

src/main/java/coydir/commons/core/Messages.java
0.00% <ø> (ø)

...c/main/java/coydir/logic/commands/ViewCommand.java
0.00% <0.00%> (ø)

...in/java/coydir/logic/commands/AddLeaveCommand.java
100.00% <100.00%> (ø)

...main/java/coydir/logic/commands/DeleteCommand.java
100.00% <100.00%> (ø)

...java/coydir/logic/commands/DeleteLeaveCommand.java
80.00% <100.00%> (ø)

...c/main/java/coydir/logic/commands/EditCommand.java
95.87% <100.00%> (ø)

...c/main/java/coydir/logic/commands/RateCommand.java
92.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Lousy. Merge approved.


To avoid error 112 (Address already in use), set socket to Reuse Addr… (IDFGH-1306)

…ess. Ensure listening socket is closed when client disconnects.
This is a quick fix to the example as it is written. However a better example would probably not close and reopen the listening socket each iteration. There is no need to continually close and rebind this socket when clients disconnect.
Therefore I suggest that this PR be considered for the time being, but that this example be revisited to behave in a more standard manner.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.David Antliff seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@DavidAntliff Thanks for the contribution and sorry for the slow turnaround. We have been looking into PR, thanks.

I have discussed this issue here, along with others. I think that there is still a problem (qv).


feat: Include Deno.serve functionality based on serveHttp op

What kind of change does this PR introduce?
Include Deno.serve functionality based on serveHttp op. Fixes #161

let's add an integration test for this?


If caller out of scope risk shall not be created for code backdooring rule

Yevhen Zavhorodnii
11:40 AM
@Joerg Reichelt
/
@Christian Schneider
I believe code backdooring rule is not correct, please take a look at PR with fix: https://github.com/Threagile/threagile/pull/73
Joerg Reichelt
6:01 PM
@Yevhen Zavhorodnii
can you explain the scenario? usually risks are created for all assets that are in scope but we don't usually skip rules what adjacent assets (callers, etc.) are out of scope. if you could explain your scenario it would help a lot understanding the reasoning. thanks
Yevhen Zavhorodnii
10:21 PM
What we're saying currently: "if caller is over the internet without VPN or caller is out of scope (even when call make over the VPN)" create risk.
Why is it a risk if call make from caller out of scope if it made over VPN?
Yevhen Zavhorodnii
10:42 PM
Perhaps caller.OutOfScope shall be removed from if condition at all
10:42
Why adding OutOfScope to the caller is adding a risk?
Joerg Reichelt
12:41 AM
I don't think it should make any difference if the caller is in scope or not, I agree with that. this risk should always be created as long as the target is in scope. code backdooring can happen with any code modification, no matter if the caller (source) is in scope of not
12:42
for example, you may pull in code from an open source project. those contributors and the source repo wouldn't be in scope. however, the imported code can still create a backdoor
12:44
similarly, your own developers can introduce a backdoor intentionally (insider threat) or not (by mistake). the developers, their development machine and the repo they push code to would likely be in scope


acme-sh: 2.8.9 -> 2.9.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/acme.sh/versions.
meta.description for acme-sh is: "A pure Unix shell script implementing ACME client protocol"
meta.homepage for acme-sh is: "https://acme.sh/"
meta.changelog for acme-sh is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/x44p8k5nqcmg3xrp2pb2sq701l38l4qw-acme.sh-2.9.0/bin/acme.sh passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 2.9.0 with grep in /nix/store/x44p8k5nqcmg3xrp2pb2sq701l38l4qw-acme.sh-2.9.0

found 2.9.0 in filename of file in /nix/store/x44p8k5nqcmg3xrp2pb2sq701l38l4qw-acme.sh-2.9.0

directory tree listing: https://gist.github.com/69cae13333aeb871ac5e71a54a4722a6

du listing: https://gist.github.com/3ce76be5aed005dae3009d3628940e54

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

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
acme-sh

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/x44p8k5nqcmg3xrp2pb2sq701l38l4qw-acme.sh-2.9.0
ls -la /nix/store/x44p8k5nqcmg3xrp2pb2sq701l38l4qw-acme.sh-2.9.0/bin

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

1 package built:

acme-sh

Maintainer pings
cc @balsoft @mkaito for testing.

Result of nixpkgs-review pr 125568 at 804dc91a run on x86_64-linux 1

1 package built successfully:

acme-sh

2 suggestions:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/tools/admin/acme.sh/default.nix:15:3:
   |
15 |   installPhase = ''
   |   ^

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/tools/admin/acme.sh/default.nix:33:5:
   |
33 |     license = licenses.gpl3;
   |     ^

Changelog:
ACME v1 is removed.
Bug fixes.


[14.0.x] ISPN-14418 Stable topology recovery after shutdown backports

A batch with fixes I failed to backport.
https://issues.redhat.com/browse/ISPN-14418 (#10733)
https://issues.redhat.com/browse/ISPN-15504 (#11739)
https://issues.redhat.com/browse/ISPN-15432 (#11672)

Thanks @jabolina


HDD doesn't exist at all

HDD does not exist!

The HDD peripheral is available as 'fs' in DiskOS, you can see how that happens in C:/boot.lua.
Note: The HDD/FS API is not available to the games.

Another thing, Yay you found the CC12 project :P, To install CraftOS replace the C drive with allthe files of that repo, and start with boot.lua

Btw, why did you leave the Discord Server ?

Btw, why did you leave the Fantasy Consoles Server ?

I didn't

Okay, thanks

kernel.lua runs on boot, and also runs bios.lua automatically, and yeah it works


docs: broken format displayed for TLSSettings reference

Description:
See https://gateway.envoyproxy.io/latest/api/extension_types/#tlssettings

Repro steps:
Same with https://github.com/envoyproxy/gateway/issues/2239, a new line breaks the format.
https://github.com/envoyproxy/gateway/blob/316a0a215ca4c040697bc0231f2ded9dabf59909/api/v1alpha1/tls_types.go#L12-L40
Environment:
latest
Logs:

Include the access logs and the Envoy logs.

/assign


Automation editor doesn't support templates in service calls

Home Assistant release with the issue:
0.102.1
Last working Home Assistant release (if known):
Unknown
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Integration:
https://www.home-assistant.io/docs/automation/editor/
Description of problem:
Creating an automation that uses a template in the data field for a service call, does not work unless manually editing automations.yaml to change data: to data_template:.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Created by the editor and does not work:
- id: '1574627781238'
  alias: Shades Home
  description: Set shades to position when home
  trigger:
  - entity_id: sensor.house_status
    from: Away
    platform: state
    to: Home
  condition:
  - condition: state
    entity_id: input_boolean.guest_mode
    state: 'off'
  action:
  - data:
      entity_id: cover.shade
      position: '{{ states("input_number.shade_home_position") }}'
    service: cover.set_cover_position

Manually edited automations.yaml that does work:
- id: '1574627781238'
  alias: Shades Home
  description: Set shades to position when home
  trigger:
  - entity_id: sensor.house_status
    from: Away
    platform: state
    to: Home
  condition:
  - condition: state
    entity_id: input_boolean.guest_mode
    state: 'off'
  action:
  - data_template:
      entity_id: cover.shade
      position: '{{ states("input_number.shade_home_position") }}'
    service: cover.set_cover_position

Traceback (if applicable):

Additional information:

@bramkragten I know you recently did a lot of work on the automation editor (thank you!) and I wanted to make you aware of this.

Related:
https://github.com/home-assistant/home-assistant-polymer/issues/3577
https://github.com/home-assistant/home-assistant-polymer/issues/3258

With 0.103 you can at least edit it in the editor in YAML mode. I'll close this issue as it belongs in the frontend repo and it already exists there.

@bramkragten Thank you, that's acceptable. Yes the YAML mode editor seems to be a good workaround. Also, I created this before I knew about that repo so my apologies.


Login page

I changed regex of the email. Please, check of this and commit your registration page

Good


Update texture coordinate test docs

Massive improvement!
(also highlights that perhaps node, node1 , and node2 should be renamed for clarity)


Switch autoComplete field to textArea

Hi there I'm trying to allow 2 lines worth of address to be visible by the user.
Can i somehow use textArea?

@basiclaser Thank you for opening this issue. This feature is not currently in my project roadmap, but I'll keep this issue open in case other people request for the same feature 👍

Closing this since we haven't gotten similar feature requests in a long time.

Hey @kenny-hibino, please have a look for PR #69, as currently we need this feature in place for our situation


Progress animation stopped working when app moves background and then foreground

When MKProgress view is visible. Move app in background and then move app in foreground, Progress animation stopped working.

@satishazad Thanks for reporting the issue. I will verify and push the fix.

Please update pod version to 1.0.9 for the fix.

@kamirana4 Thanks


Make difference between taps and holds

Tap event fires after release hold (holded for more than 2-5 secs). Is there a way to prevent onTap firing after releasing holds? So adding some time span that determines what should be considered tap vs hold (time between touch start and end).
Thanks a lot!

@geritol I forked & made some experimental changes to avoid sending an onTap after an onPress is triggered. I'll be testing it with some users next week. (Not ready to PR it yet since I'll likely have made mistakes after a crazy and exhausting coding week.
@JedWatson Any specific guidelines for a PR?

My changes seem to work fine, currently using it in production.
@JedWatson Still hungry for PR guidelines. Thanks. :-)


Update code to work with version 3.3.4 of Bosch driver

Probably I shouldn't make pull request, because this updated code doesn't work perfectly - it works as expected only with very low i2c clock speeds, like 40000.
If master_clk is ~ 100000 only pressure and humidity are sent by sensor,
if master_clk is 400000 or more - only humidity is sent (as non zero value).
I spent some time, but didn't find root of this issue, but it would be great, if you can help. Expect of this problem this commit fully supports lastest Bosch driver (v3.3.4)

I got the your Pull #2 to work with the latest Bosch drivers (Master Branch as of today) by changing the I2C speed to 100000 from 40000. I also changed the return type of the BME280_I2C_bus_write function to the correct uint8_t type. I'm even running it on the Master Branch of ESP-IDF using a ESP32-S2-Saola-1R board. I'm using it in the Smart Outlet example and uploading the data instead of using the examples random Temperature data.


Bug: running gollama -v should print the version

Describe the bug
gollama -v should print the version which should be set by the go build flags, but it's just printing 'development' which is the placeholder version string.
To Reproduce
Steps to reproduce the behaviour:
go install github.com/sammcj/gollama@latest
gl -v
development

no go with that PR @jralmaraz


Incorporating Mason (optionally)

This is not really a problem, but more of a usability feature.
I guess it would be nice to extend the lazy.nvim window to show and handle mason.nvim functionality optionally, for those who use Mason. Lazy.nvim's control window could then become a kind of "control center" for not only plugins but also for linters, language servers, ...
An additional benefit would be, that there could be one place and command to start and review all updates.
Maybe this could also then be extended for treesitter parsers.

yeah, no. That's not going to happen. Mason is a different plugin. Makes no sense.


fixing PageGrid.js passing primaryKey as token

For some reason PageGrid.js is calling createStore() in widget/IDMappingGrid.js by passing the primaryKey (sorting) as the auth token .
Fixes https://github.com/BV-BRC/issues/issues/752

This PR also enables metaspades usage on metagenomic binning with a single SRR


🍒[Swift 6.0]: Update Generic Unix linker selection

Cherry-Picking https://github.com/apple/swift-driver/pull/1545 back to Swift 6.0
Not all generic-"unix" environments have the Gold linker available to them, and in some cases, the vendor of the toolchain may provide their own linker. In these cases, the driver should be internally consistent with the toolchain that it is shipped with.
Now that we have the clang-linker, we can lean on the linker selection in the clang-linker to determine a default linker. If the clang-linker, and thus, the swift compiler driver, are part of a specific toolchain, that clang-linker should be built for that platform with the appropriate linker defaults set. If someone overrides the linker with -use-ld, we should still honour that, but should otherwise be consistent with the appropriate toolchain linker.
This will enable building and linking on AmazonLinux 2023 without requiring folks to always pass additional flags. It also means we can produce a self-contained toolchain that is internally consistent using lld as the linker.
LLD removes the start/stop symbols as of https://reviews.llvm.org/D96914, which the Swift runtime used to register the runtime type metadata and other runtime metadata tables. I'm waiting to merge this until https://github.com/apple/swift/pull/72061 merges as we won't know when to pass nostart-stop-gc with this change.
Fixes: rdar://123061492

Explanation: This patch has the Swift driver fallback on the clang-linker for default linker selection instead of hard-coding gold on Linux. The clang-linker can be configured to choose a different linker at build time, which means that we can have a toolchain that "just works" on Amazon Linux 2023, which does not have gold, but does have lld.
Original PR: https://github.com/apple/swift-driver/pull/1545
Reviewed By: @compnerd, @keith, @shahmishal, @artemcm, @finagolfin
Resolves: rdar://123061492
*Tests:*Several driver tests do not pass an explicit linker, those would fail if a linker weren't being chosen. This is also tested by any part of the SDK build that uses the Swift driver for linking (or clang as it is the clang-linker).

@swift-ci please test

We'll also need to back-port the corresponding change to the default linker in the clang-linker or the Linux builds will fail: https://github.com/apple/swift/pull/73463

@swift-ci please test


feat: update "installation" page

Updated /installation content according to Slack doc
Fixed the <Code /> component to correctly render the empty state linking to GitHub edit page for current pathname, i.e. leaving some empty will render this:

I was thinking we could use [some other theme from **shikiji** ](https://shikiji.netlify.app/themes) that looks a bit more fancy, the one we used to have with a purple background looked cool 🙌🏽

Yeah I'm up for playing with the themes, lets do it in its own PR thoguh :pray:


Dynamic Lazily imported component doesn't work in preview

Describe the bug
I'm adding components dynamically based on IntersectionObserver ie when the component is in the browser view.
Lazy component will load when necessary the component:
<Lazy
  componentName="./Thing"
  let:intersecting
  let:component
  >
  {#if intersecting}
	  <svelte:component this={component} />
  {/if}
</Lazy>

// the interesting part from <Lazy>
...
 export let componentPath = "";
 const initialize = () => {
      observer = new IntersectionObserver(
          (entries) => {
              entries.forEach(async (_entry) => {
                  entry = _entry;

                  if (_entry.isIntersecting) {
                      component = (await import(`${componentPath}.svelte`)).default;
                  }
                  intersecting = _entry.isIntersecting;
              });
          },
          { root, rootMargin, threshold }
      );
  };
...

In dev mode all is fine and components loads but not in preview (it loads an HTML instead of the component js).
I'm suspecting the path to the component isn't correct in preview mode.
Perhaps it's a matter of specifying a static path that will work in both dev and preview?
Unfortunatly $lib doesn't work.
Reproduction
import a component via a function that takes the component path as a parameter such as
export async function loadComp(path) {
    return  (await import(`${path}.svelte`)).default;
}

and run it in preview mode.
Logs
No response
System Info
@sveltejs/kit 1.0.0-next.370
@sveltejs/vite-plugin-svelte 1.0.0-next.49
vite 2.9.13
node v18.4.0

Severity
blocking prod usage of SvelteKit
Additional Information
No response

This is probably due to the dynamic path you are using.
Vite statically analyzes dynamic imports with these restrictions: https://github.com/rollup/plugins/tree/master/packages/dynamic-import-vars#limitations
This essentially means you only get to have one dynamic segment in your import path, and the path should be relative.

Thanks! I didn't knew that.
The problem I can see is if I specify a path like ./components/${name}.svelte it works in dev but not in preview
Anything I'm missing there?

It works in dev because all of the files are there and are compiled on demand - while in your production build, everything's compiled ahead of time. I'm going to close this as working-as-intended.

Thanks for the quick feedback. My problem is that I haven't found a way to make this work in preview.
Any recommendation would be greatly appreciated.

Ok thanks @f-elix, I had more than one dynamic segment in the path.


Hi, it's planned, yes. #12

Can't wait to get it!


[v0.2] Recording with resolution other than "Window" gives an error

Starting recording and using any resolution other than "Window" gives an error, If resolution is set to Window and game view resolution is set manually everything works as expected.

Using 2017.2.0b10

I've used every single version of Recorder. I never had this problem, now when I'm trying to render a movie with resolution other than "Window" i see this:

Strange thing is that it only happens in a project that used other Recorder builds, in a empty project there is no errors.

Deleting and re-importing Recorder doesn't fix the problem.

Q: if you 1st restart the editor, then delete the recorder directory, does it still occur?
Any chance you can attach a stripped down version of the project that has the error?

A: Still happens.
I don't know why but i don't get this error in empty project, Could i just sent you my main project? (It's around 1GB size) Just send me your email address.

that's too large for email. can you try attaching here? I've no idea what the Github attachement size limit is.

I don't really want to upload my private project here, I wanted your email so i could upload it to Dropbox or some cloud and send you the link privately.

I sent you a msg on the unity forum, for email privacy.

Issue fixed.


Support multiple files in checkstyle formatter

PR checklist

[ ] Addresses an existing issue: #0000
[X] New feature, bugfix, or enhancement

[X] Includes tests

[ ] Documentation update

What changes did you make?
Found an issue when integrating tslint with jenkins (using checkstyle formatter), the formatter did not generate separate file nodes in the outputted XML, instead simply reporting all errors under the first file.
To fix this I:

Modified checkstyleFormatter.ts to sort failures by filename, and generate file nodes for each unique filename
Modified test case to test failures in multiple files

Is there anything you'd like reviewers to focus on?
The checkstyleFormatter test was reusing another formatter's test input file, I've followed this pattern to add a second file in the test. It might be better to create two test input files specifically for the checkstyleFormatter...

Thanks for your interest in palantir/tslint, @fsahmad! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.

@fsahmad thanks!


iOS utilities BuildAction

It would be useful to have a build action that enabled the configuration of iOS-specific build settings (e.g. development team and provisioning profile IDs) on a per-build basis

This could also potentially be combined with the Xcode project manipulation functionality from #11.


Fix join using for nested joins

Summary of the changes / Why this improves CrateDB
Fix join using for nested joins
This extracts the relation names for lhs and rhs for the join using
clause from the outputs of the Join Relation. This makes the following
statement work:
SELECT * FROM t1 JOIN (t2 JOIN t3 ON t2.y = t3.y) USING(x)

It also adds additional validation to make sure the pre-conditions for join using are met.
Follow-up for https://github.com/crate/crate/commit/e9624a9dcd64c40e8fd26b8285e187394e289adf
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

retest this please

retest this please

retest this please


Crash when manual or automatic 2D zones picking

@jobo322 @lpatiny

@jobo322
I updated the nmr-processing package to the last release do i have to return back to the old one

I did a PR, could you check if this solves your problem?


camlistored/ui: on download, form submission error

As reported by e-mail by Attila, while downloading items in the web UI, he gets the "Form submission canceled because the form is not connected" error.
That is because we create an ephemeral form, that we don't connect to the DOM, to send the request to the server, and as of apparently Chrome 56, https://html.spec.whatwg.org/multipage/forms.html#form-submission-algorithm, step 2. was enforced.

https://camlistore-review.googlesource.com/9969


Incorrect File Path Displayed in Title Bar

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Opening a file that does not belong to a project folder that has been added to the current session results in an incorrect file path being displayed on the title bar, making it look like the open file is actually part of the first project folder in the list.
Steps to Reproduce

Open Atom on a macOS machine
Add some project folders if none exist
Using finder, open a file outside of any project folder currently added
Note that the file path displayed in the title bar points to the first project folder in the list, not the actual file location.

Expected behavior: Opening any file in Atom displays the correct path to the file, always.
Actual behavior: Opening a file that is not part of an 'added' project folder displays an incorrect path to the file in the title bar.
Reproduces how often: 100%
Versions
Atom    : 1.12.7
Electron: 1.3.13
Chrome  : 52.0.2743.82
Node    : 6.5.0
Additional Information
See screenshot - the  correct path to ISSUE_TEMPLATE.md is displayed in the status bar (~/Desktop), but not in the title bar (~/Projects/node-steam)

This was fixed by https://github.com/atom/atom/pull/13475 and will be available in Atom 1.14.


Scene name validation

Currently we can add scene with empty name and I think it is not a good behavior.
With this fix we can not add new scene with empty or blank name:

Good catch! I did not know empty scene names were being allowed.


Support for adding custom image at runtime using map.addImage

Mapbox-gl allow to add custom images at runtime using loadImage and addImage, I don't think loadImage is necessary, instead user should pass an HTMLImageElement to addImage and query for the image by their own using new window.Image().
In term of API I am not sure what is best between using prop of Layer component:
<Layer
  addImage={image}
>
</Layer>

Or having a component for that:
<ImageSource image={image}/>

See: https://www.mapbox.com/mapbox-gl-js/api/#map#addimage

For reference, the prop images has been added to react-mapbox-gl with the release 2.5.0, it can be use this way:
const image = new Image(30, 30);
image.src = 'image_source_url_or_base64';

const images = ['myImage', image];
...
<Layer
  layout={{ icon-image: 'myImage' }}
  images={images}
/>

Hey, when I try this, I get the following error:
react-dom.development.js:12879 Uncaught DOMException: Failed to execute 'drawImage' on 'CanvasRenderingContext2D': The HTMLImageElement provided is in the 'broken' state.
Any idea why?

This works for me (shows the image) but gives me a few errors when removing the  the new image is associated with:
const image = new Image(40, 60);
image.src = '/img/new-icon.svg';

const images = ['newIcon', image];

{show && (
<Layer
  type="symbol"
  layout={{ 'icon-image': 'newIcon' }}
  images={images}
>
...
)}

Errors when !show:
mapbox-gl.js:484 Uncaught TypeError: Cannot read property 'style' of undefined
    at e.removeImage (mapbox-gl.js:484)
    at Array.forEach (<anonymous>)
    at Layer../N:/Dropbox/Work/wildcrowd-web-app/node_modules/react-mapbox-gl/lib/layer.js.Layer.componentWillUnmount (layer.js:129)
    at ReactCompositeComponent.js:406
    at measureLifeCyclePerf (ReactCompositeComponent.js:73)
    at ReactCompositeComponentWrapper.unmountComponent (ReactCompositeComponent.js:405)
    at Object.unmountComponent (ReactReconciler.js:76)
    at ReactCompositeComponentWrapper.unmountComponent (ReactCompositeComponent.js:415)
    at Object.unmountComponent (ReactReconciler.js:76)
    at Object.updateChildren (ReactChildReconciler.js:128)
    at ReactDOMComponent._reconcilerUpdateChildren (ReactMultiChild.js:204)
    at ReactDOMComponent._updateChildren (ReactMultiChild.js:308)
    at ReactDOMComponent.updateChildren (ReactMultiChild.js:295)
    at ReactDOMComponent._updateDOMChildren (ReactDOMComponent.js:944)
    at ReactDOMComponent.updateComponent (ReactDOMComponent.js:758)
    at ReactDOMComponent.receiveComponent (ReactDOMComponent.js:720)
    at Object.receiveComponent (ReactReconciler.js:122)
    at ReactCompositeComponentWrapper._updateRenderedComponent (ReactCompositeComponent.js:751)
    at ReactCompositeComponentWrapper._performComponentUpdate (ReactCompositeComponent.js:721)
    at ReactCompositeComponentWrapper.updateComponent (ReactCompositeComponent.js:642)
    at ReactCompositeComponentWrapper.receiveComponent (ReactCompositeComponent.js:544)
    at Object.receiveComponent (ReactReconciler.js:122)
    at Object.updateChildren (ReactChildReconciler.js:107)
    at ReactDOMComponent._reconcilerUpdateChildren (ReactMultiChild.js:204)
    at ReactDOMComponent._updateChildren (ReactMultiChild.js:308)
    at ReactDOMComponent.updateChildren (ReactMultiChild.js:295)
    at ReactDOMComponent._updateDOMChildren (ReactDOMComponent.js:944)
    at ReactDOMComponent.updateComponent (ReactDOMComponent.js:758)
    at ReactDOMComponent.receiveComponent (ReactDOMComponent.js:720)
    at Object.receiveComponent (ReactReconciler.js:122)
    at ReactCompositeComponentWrapper._updateRenderedComponent (ReactCompositeComponent.js:751)
    at ReactCompositeComponentWrapper._performComponentUpdate (ReactCompositeComponent.js:721)
    at ReactCompositeComponentWrapper.updateComponent (ReactCompositeComponent.js:642)
    at ReactCompositeComponentWrapper.performUpdateIfNecessary (ReactCompositeComponent.js:558)
    at Object.performUpdateIfNecessary (ReactReconciler.js:154)
    at runBatchedUpdates (ReactUpdates.js:148)
    at ReactReconcileTransaction.perform (Transaction.js:141)
    at ReactUpdatesFlushTransaction.perform (Transaction.js:141)
    at ReactUpdatesFlushTransaction.perform (ReactUpdates.js:87)
    at Object.flushBatchedUpdates (ReactUpdates.js:170)
    at ReactDefaultBatchingStrategyTransaction.closeAll (Transaction.js:207)
    at ReactDefaultBatchingStrategyTransaction.perform (Transaction.js:154)
    at Object.batchedUpdates (ReactDefaultBatchingStrategy.js:60)
    at Object.batchedUpdates (ReactUpdates.js:95)
    at dispatchEvent (ReactEventListener.js:145)

and
An image with this name already exists.
    at t.addImage (mapbox-gl.js:374)
    at e.addImage (mapbox-gl.js:484)
    at layer.js:89
    at Array.forEach (<anonymous>)
    at Layer._this.initialize (layer.js:88)
    at e.Layer._this.onStyleDataChange (layer.js:101)
    at e.Evented.fire (mapbox-gl.js:510)
    at e._onData (mapbox-gl.js:484)
    at e.Evented.fire (mapbox-gl.js:510)
    at t.Evented.fire (mapbox-gl.js:510)
    at t.update (mapbox-gl.js:374)
    at e._render (mapbox-gl.js:484)

@Valid Yep, same exact issue when trying to remove a layer with an associated image. Have you found a work around for this?

Nope, haven't found a workaround yet. @alex3165 should this be re-opened, or another issue created?

Related? https://github.com/alex3165/react-mapbox-gl/issues/278

Hi, sorry for the late reply, it is related to https://github.com/alex3165/react-mapbox-gl/issues/464 and I have created a PR on mapbox-gl-js to get this fixed https://github.com/mapbox/mapbox-gl-js/pull/5775. I am just waiting to have thismap.hasImage released with mapbox v0.43 to fix it.

@alex3165 well mapbox v0.43 with map.hasImage is released since 7 days :stuck_out_tongue:

I have the same issue with  "react-mapbox-gl": "^3.8.0", and "mapbox-gl": "^0.46.0",

any updates ...

import Icon from './download.svg';
const image = new Image(30, 30);
image.src = Icon;
const images = ['myImage', image];
const point =  [
{-70.903827,
42.584152},
{-71.905205,
42.211716},
{-70.903827,
42.584152},
];
<Layer
type="symbol"
id="point"
layout={{
'icon-image': 'myImage',
'icon-allow-overlap': true
}}
images={images}
>
{point.map((point, i) => (

))}

Try something like that. This working in react.

some solution?

Try this code above.

I've already tried

worked for me, thanks @alex3165


add docs this way more efficiently

I found the docs on https://godoc.org/gopkg.in/olivere/elastic.v2, but sadly there are huge numbers of apis need to view except the basic apis (index, update, search, delete and so on).
This project's wiki pages help me again but do not solve all my problems when i want to implement a complex search query (because there are still only some basic apis)
I wish there are more docs about (the specific elasticsearch api implement by what type or function) rather than i look all the type may implement the api to check it's the right type.

Hi! You're right in that documentation for the APIs could be better. However, Elasticsearch has an API with over 600 REST endpoints (last time I counted), and probably more than a thousand parameters and options. As I do this library in my spare time, I simply don't have the time to document them all.
But don't worry. Here's what I found to be the best way to get used to Elasticsearch (and elastic): First, there's The Definite Guide which I recommend as a must read for anyone getting started with Elasticsearch. Read at least the "Getting Started" chapter. If you're ready to get into the details, there is the API documentation. It is well written, comes with examples, and has many useful tips and tricks. Once you get the concepts and endpoints of Elasticsearch, using elastic becomes natural. The endpoints match up with the services, the parameters are (mostly) the same as they are in the documentation. And if you're still missing something (and God knows elastic has its rough edges), consult the tests. They serve not only as tests but as a "how to" for using elastic as well. Yes, it takes a little time. But sometimes there are no shortcuts.
What other ways of improving documentation do you have in mind?

yeah, I'm working at your way. maybe when i finished view all the apis. I'll contribute an api docs in my spare time.
thanks anyway~


Add observability (o11y) examples using honeycomb.io

As an operations stakeholder
I want to make use of the observability maturity model adoption
In order that scaled out and production services can be efficiently and responsively managed
This example will introduce observability instrumentation for us with the honeycomb.io service offering.

OpenTelemetry support is probably on the cards for this effort.


Scanner: The ScanCode maxVersion parameter ignores patch version

I'm trying to set the ScanCode version range to use for cache search so that only cache for version 3.2.1-rc2 is taken into account.
The ort.conf has following entry:
  scanner {

    options {
      ScanCode {
        minVersion = "3.2.1-rc2"
        maxVersion = "3.2.1-rc3"
      }
    }
  }

With these values ORT can't find cache entry
org.ossreviewtoolkit.scanner.scanners.scancode.ScanCode - Found stored scan results for 0 packages and ScannerCriteria(regScannerName=ScanCode, minVersion=3.2.1-rc2, maxVersion=3.2.1-rc3, configMatcher=(kotlin.String) -> kotlin.Boolean)

The same happens for maxVersion = "3.2.2"
org.ossreviewtoolkit.scanner.scanners.scancode.ScanCode - Found stored scan results for 0 packages and ScannerCriteria(regScannerName=ScanCode, minVersion=3.2.1-rc2, maxVersion=3.2.2, configMatcher=(kotlin.String) -> kotlin.Boolean).

Only maxVersion = "3.3.0" works as expected:
org.ossreviewtoolkit.scanner.scanners.scancode.ScanCode - Found stored scan results for 14 packages and ScannerCriteria(regScannerName=ScanCode, minVersion=3.2.1-rc2, maxVersion=3.3.0, configMatcher=(kotlin.String) -> kotlin.Boolean).

I assume there is a bug that cause ORT to ignore patch version of the maxVersion parameter when searching in the cache and work with major.minor versions only.

Thanks for the report. While I'd not expect maxVersion = "3.2.1-rc3" to work (as there are no semantic attached to the string "rc" in Semver, so Semver4j does not know that "rc3" is more recent than "rc2"), I would expect maxVersion = "3.2.2" to work.
While looking around for the cause, I cleaned stuff up a bit and added a test in https://github.com/oss-review-toolkit/ort/pull/4791/commits/e8f21a0ace5e5cdfb03641691c761391ae08cc20, but that test actually succeeds, so I'm not sure what going wrong yet.

Closed as part of backlog grooming. Feel free to comment if you would like to contribute to this.


SUPESC-581: Computop prevent sending unnecessary shAmount

Developer(s): @michbeck

Ticket: https://spryker.atlassian.net/browse/SUPESC-581

Docs PR: https://github.com/spryker/spryker-docs/pull/911

Release Group: https://release.spryker.com/release-groups/view/4133

PR Overview: https://release.spryker.com/release/pull-request-eco/Computop/47

merge: squash

Release Table

Module
Release Type
Constraint Updates

Computop
patch {skip}

Not a patch {skip}
because of following changes:
src/SprykerEco/Zed/Computop/Business/Hook/Mapper/Init/InitPaydirektMapper.php
src/SprykerEco/Zed/Computop/Business/Hook/Mapper/Init/InitPaydirektMapper.php


Remove dataset

Enable user configurable dataset location

This does not fix anything for previous commits, but is related to #44


Option to invert window colors without decorations

It would be nice to have an option for inverting only window contents without decorations, it would make sense for people (like me) who use themes like Adwaita-Dark.

I have looked into this and it is impossible to do with the method used to invert in this extension because the decorations and the actual window content are treated as one block. so implementing the feature you are requesting would require another method. one method I can think of is updating the gnome.css used to render the window but I don't know if that can be made specific to a window. I will look at some source code and search online for inspiration.

Modifying the theme CSS wouldn't be enough, as decorations are rendered by the window manager, which ignores any per app CSS. Worse, client side decorations, which are per app, may be rendered by different widget libraries. In short, there's no simple, noninvasive, reliable or consistent way to single out decorations to selectively apply an effect.

Despite the window and its decorations being treated as one block, would it be possible to invert the color of just a subset of that block? If the height of the window titlebar is fixed and the height of the window is known, then it would be easy to define the rectangle covering just the window contents.


Made focus area filtering work for Publications. Currently disbaling for

projects as there is no obvious way to filter.

I’m OK w/ merging this to try it out.
I’d love to see the hand-rolled JQuery stuff get cleaned up.  In the Angular world, the Navigation would be a directive that would automatically react to the navigation state and we wouldn’t need to involve JQuery at all.


[Q] POST Text instead of Params

Following up on #71, here is another POST outlier.
First of all, here is a sample of normal POST in a .har file:

The POST has Params in PostData.
Now,

This one, The POST has Text  in PostData instead.
How to send such Text in POST?
Would that be something like this?
            http('POST /url/...') {
                body "POST Text here"
            }

Hi, if POST request is not form data you just use body to sent any data with the POST. Remember that you need to set header with Content-Type 'application/json'.
I don't know if you try but https://github.com/smicyk/groovy-harventer but it converts .har to groovy files. It should handle it I hope at least.

Thank you for all your answers.


Unhandled Exception: MissingPluginException(No implementation found for method getPlatformVersion on channel zkfinger)

I cloned the repo. run the xample but I got below can you tell me what the cause?
The Flutter DevTools debugger and profiler on TPS360 is available at:
http://<IP_ADDRESS>:9104?uri=http://<IP_ADDRESS>:56705/9F2_EWmC25I=/
E/flutter ( 9172): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: MissingPluginException(No implementation found for method getPlatformVersion on channel zkfinger)
E/flutter ( 9172): #0      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:332:7)
E/flutter ( 9172):
E/flutter ( 9172): #1      _MyAppState.initPlatformState (package:zkfinger10_example/main.dart:66:25)
E/flutter ( 9172):

Hi, thanks for opening an issue, can you run "flutter doctor" and tell us what it prints

PS C:\dev\new\zk_finger_10\example> flutter doctor
Flutter assets will be downloaded from https://storage.flutter-io.cn. Make sure you trust this source!
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.22.3, on Microsoft Windows [Version 10.0.22631.3880], locale en-NG)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Build Tools 2022 17.7.5)
[!] Android Studio (version 2022.3)
X Unable to find bundled Java version.
[!] Android Studio (version 2023.3)
X Unable to determine bundled Java version.
[√] Android Studio (version 2024.1)
[√] VS Code (version 1.92.0)
[√] Connected device (4 available)
[√] Network resources
! Doctor found issues in 2 categories.

Hey bro, I was able to run the sample, but I have the same error when integrating it into my own project. Were you able to resolve it? Let's see if your solution can help me in any way.
`════ Exception caught by services library ══════════════════════════════════
The following MissingPluginException was thrown while activating platform stream on channel com.mamasodikov.zkfinger10/finger_image:
MissingPluginException(No implementation found for method listen on channel com.mamasodikov.zkfinger10/finger_image)
When the exception was thrown, this was the stack:
#0      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:332:7)
platform_channel.dart:332

#1      EventChannel.receiveBroadcastStream. (package:flutter/src/services/platform_channel.dart:676:9)
platform_channel.dart:676

════════════════════════════════════════════════════════════════════════════════
════════ Exception caught by services library ══════════════════════════════════
MissingPluginException(No implementation found for method listen on channel com.mamasodikov.zkfinger10/status_change)`

Hi, thanks for opening an issue,
Have you stopped app and re run after adding plugin to your project?

i got same issue

t

¡Tengo el mismo problema! Reinicié la aplicación 2 o 3 veces, pero sigue igual. ¿Puedes ayudarme?@Mamasodikov¿Debería ser necesario conectar el dispositivo de huellas dactilares?
no se está inicializando E/flutter (9601): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Excepción no controlada: MissingPluginException(No se encontró implementación para el método getPlatformVersion en el canal zkfinger) E/flutter (9601) : #0 MethodChannel._invokeMethod (paquete:flutter/src/services/platform_channel.dart:332:7) E/flutter (9601): E/flutter (9601): #1 _MyAppState.initPlatformState (paquete:zkfinger10_example/main.dart :66:25) E/aleteo (9601): E/aleteo (9601):

I was able to fix it, downgrade Flutter to version 3.19.0 with fvm and in the app build.gradle configure minSDK = 21 and targetSdk = 31.

Thanks Bro! @israUSA Working fine now.

Hi, i change the grale version in gradle-wrapper.propierties to7.5 and change the flutter version to 3.19.0, I don't think any other changes were necessary, but in any case, I'm going to detail the changes I made correctly.


When run build task, there are strange words in error message.

VSCode Version: Code 1.7.1 (02611b40b24c9df2726ad8b33f5ef5f67ac30b44, 2016-11-03T13:53:14.822Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

html-snippets
abusaidm
0.0.18

vscode-javascript-snippet-pack
akamud
0.1.5

bower
donjayamanne
0.0.3

jquerysnippets
donjayamanne
0.0.1

xml
DotJoshJohnson
1.6.0

vscode-html-css
ecmel
0.0.30

emoji-code
idleberg
0.1.6

format-indent
Kasik96
1.3.0

vscode-JS-CSS-HTML-formatter
lonefy
0.2.1

phpcsfixer
makao
0.0.1

vscode-autoprefixer
mrmlnc
2.0.0

csharp
ms-vscode
1.4.1

js-atom-grammar
ms-vscode
0.1.10

debugger-for-chrome
msjsdiag
2.2.0

debugger-for-edge
msjsdiag
0.4.1

debugger-for-ios-web
msjsdiag
0.1.2

vscode-icons
robertohuertasm
3.0.7

code-bing
SirTobi
0.2.0

php-formatter
Sophisticode
0.1.3

cordova-tools
vsmobile
1.2.3

bootstrap-3-snippets
wcwhitehead
0.0.8

JavaScriptSnippets
xabikos
1.2.0

Steps to Reproduce:
I try to transpiling Sass and Less into CSS by the steps from website:
CSS, Sass and Less
but, on step 4, after I pressing Ctrl+Shift+B, the error message show:

'node-sass' ���O�����Υ~���R�O�B�i���檺�{���Χ妸�ɡC

I don't know what does it means.
How could I do to let it shows the true language words?

First of all, the reason that all characters are encoded incorrectly. Secondly, it's dup of #14948

I understand there is an error about Native dependencies.
But, my another question is how to solve all characters are encoded incorrectly in error message.
Is there any set should I do?


zOBjGraph.draw() fails at zFnGraph.clear() if isoContour is empty

void clear() override
{
if (graphObj->graph.vertices != NULL) // fials at this point
....
}

fixed.


add Facebook login

now being handled by dlx-org: https://github.com/digitallinguistics/dlx-org/issues/13


OTLP ingestion creates too many metrics

What did you do?
If we advertise that we support OTLP, the logical thing to do is to setup an simple http server and test this out:
https://gist.github.com/roidelapluie/fdb0435b368ba8caba7841012e02bb8e
OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf" OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://<IP_ADDRESS>:9090/api/v1/otlp/v1/metrics go run main.go
./prometheus --enable-feature=otlp-write-receiver
What did you expect to see?
Reasonable metrics coming into prometheus
What did you see instead? Under which circumstances?
Labels like http_user_agent, net_sock_peer_port, which make a unique metric for every request.
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="33240"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="33248"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="33252"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="33264"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="33280"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="33296"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="33312"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="33320"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="33334"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="33344"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="39454"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="39464"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="39466"}
1
http_server_duration_count{http_flavor="1.1", http_method="GET", http_scheme="http", http_status_code="200", http_user_agent="curl/8.1.1", job="unknown_service:otlprom", net_host_name="<IP_ADDRESS>", net_host_port="7777", net_sock_peer_addr="<IP_ADDRESS>", net_sock_peer_port="39480"}

System information
Linux 6.3.13 x86_64
Prometheus version
prometheus, version 2.46.0 (branch: main, revision: 6ea6def0d3d31531696010e467bc2fb6c93edfef)
  build user:       roidelapluie@nixos
  build date:       19800101-00:00:00
  go version:       go1.20.2
  platform:         linux/amd64
  tags:             netgo,builtinassets,stringlabels

Prometheus configuration file
Empty file (really)

Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response

https://github.com/open-telemetry/semantic-conventions/blob/main/docs/http/http-metrics.md
The semantic conventions don't mention those labels, not sure why the instrumentation exports them. Will file an issue upstream.

I think this is known issue for instrumentation library of net/http
https://github.com/open-telemetry/opentelemetry-go-contrib/issues/3765
For now, we could only use View to remove those unnecessary labels which cause high cardinality, which is just like the way that opentelemetry-collector does.
https://github.com/open-telemetry/opentelemetry-collector/pull/7543/files
In the longterm, I think the instrumentation library should consider different label sets for span and metric, like this comment said https://github.com/open-telemetry/opentelemetry-go-contrib/issues/3765#issuecomment-1532570222

Yes, you almost never want to have the span and metric label sets bet the same. They're just different use cases. But this is also exactly why at my $dayjob we use separate libraries and calls for tracing and metrics. Having them be the same has led to too many problems.

This is what we need to iterate the solution and become a great backend for OTEL.
I assume the instrumentation SDKs can improve over time to send less high cardinality data based on configuration but on our side we can probably have a similar approach to the metric relabel config during scrapes so if SDK misses a flag or there is an issue the user can solve cardinality with the prometheus config.
I was chatting with @gouthamve earlier. This is not a new problem, we've seen high cardinality issues repeatedly although from experience is mostly due to mistakes during instrumentation i.e when extracting metrics out of logs for example. This is one of the reasons why we have all the relabel configs.
What I'm noticing here is that OTLP ingestion shares with remote write the nature of being push based and neither ingestion path applies relabeling (maybe I missed it for remote write but I was checking the code and saw nothing).
So what does everybody think about having a remote write ingestion relabel config specific to these two paths that users can use in case they have high cardinality writes?

There is no way to do anything useful here with relabeling.

There is. Drop the metrics altogether, not just a label or two. Not perfect, but it protects Prometheus from blowing up.

There is no way to do anything useful here with relabeling. It doesn't work to drop a label like net_sock_peer_port - you won't get an accumulated count from all the individual metrics.

 The only way to solve that is through aggregation but that gets trickier :see_no_evil:

Seems the symptom described is from an upstream library.
How can Prometheus fix this?  Write its own library?