2FA ISSUE [BUG]

MAJOR ISSUE HERE
I was trying to get my code to login considering when you ask for help the creator of this repository is incredibly unhelpful.
I tried using the TOTP thing on this repository and it turned on my 2FA.
Now I am completely logged out of my account.
I need help with this ASAP!!!

what can i do for you?

I ran some code from your repository. The TOTP part.
It turned on 2FA on my account and I didn’t get any code. Now I cannot get
into my account as instagram is requesting a code and I am not getting one.
On Fri, Jun 9, 2023 at 01:05 asimfarrukh @.***> wrote:

what can i do for you?
—
Reply to this email directly, view it on GitHub
https://github.com/adw0rd/instagrapi/issues/1381#issuecomment-1583980554,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN6IDDWL775SQOFWVPE63BDXKKVIVANCNFSM6AAAAAAY7QPZS4
.
You are receiving this because you authored the thread.Message ID:
@.***>

I ran some code from your repository. The TOTP part. It turned on 2FA on my account and I didn’t get any code. Now I cannot get into my account as instagram is requesting a code and I am not getting one.
…
Same thing happened to me but thanks to Blackhathacker111 who helped me get recovered my lost account ,message him on telegram his telegram username is https://t.me/Blackhathacker111

Can someone verify if this blackhathacker dude is legit?
Not trying to drop $300 on a scam.

Can someone verify if this blackhathacker dude is legit?
Not trying to drop $300 on a scam.

Sure he his he did a great work for me

Can someone verify if this blackhathacker dude is legit? Not trying to drop $300 on a scam.

I didn't work with him and I don't know who he is

Idk sounds sketch. I think I've lost my account.
@adw0rd , please put a note on your repository about the 2FA.
If your code fails after enabling it you will lose your account.
Does anyone here know someone at instagram? Their help page is pretty bad

Idk sounds sketch. I think I've lost my account.
@adw0rd , please put a note on your repository about the 2FA.
If your code fails after enabling it you will lose your account.
Does anyone here know someone at instagram? Their help page is pretty bad

No he’s saying the truth,that hacker helped me one time get back my instagram account

Idk man sound sketch. I need hella people to say that same guy helped them

Idk sounds sketch. I think I've lost my account.
@adw0rd , please put a note on your repository about the 2FA.
If your code fails after enabling it you will lose your account.
Does anyone here know someone at instagram? Their help page is pretty bad

No he’s saying the truth,that hacker helped me one time get back my instagram account

Your account was created an hour ago

Idk sounds sketch. I think I've lost my account.
@adw0rd , please put a note on your repository about the 2FA.
If your code fails after enabling it you will lose your account.
Does anyone here know someone at instagram? Their help page is pretty bad

No he’s saying the truth,that hacker helped me one time get back my instagram account

Your account was created an hour ago

It's more and more like a scam

That’s some bullshit I came on here to report a case on blockchain then saw this no one is forcing him he can do it or leave it,just stop saying things you don’t know


Alpha issue: inverted geometry

When alpha is one, all is good:

But if I set alpha to 0.99, the geometry becomes inverted:

As a side note, there's an additional alpha under the 'Color' part of the properties panel that ranges from 0 to 255. It seems to do nothing.
I believe @siyuanfeng-tri and @TristanThrush were experiencing similar inversion issues, but possibly unrelated to alpha.
This is with version 0.1.0-130-g4109097.

The geometry does not look natural with alpha=0.99 because of the drawing order of triangles.  To correctly visualize transparent geometry Director needs to enable VTK's depth peeling rendering feature.  It is currently disabled for 1) support of antialiasing on more systems 2) performance.  It would be nice to add a toggle to enable depth peeling, currently it can only be done by modifying C++ code and recompiling.
If you set alpha to something much lower like 0.10 the effect will not be very bad.  alpha=0.99 is the worst case scenario.
Sorry for the confusing about the 4-component color property editor.  Only the 3 RGB components are actually used.

I think there is also a bug where the alpha value can get set to 0.999 but the spinbox editor rounds it up and displays 1.0.  If you manually enter 1.0 then it takes the correct value.

Thanks for the quick response.

I think there is also a bug where the alpha value can get set to 0.999 but the spinbox editor rounds it up and displays 1.0. If you manually enter 1.0 then it takes the correct value.

That could explain why Siyuan and Tristan were having these issues.


Production EC2 instances

OK this is done. Servers are running and attached to the ELB behind https://collections.mplus.org.hk


Fixing multiple refresh bug in filter_box

Addresses https://github.com/mistercrunch/panoramix/issues/170
@williaster, cranking up the lint max-params for functions to accept 4 params as it's acceptable in many cases. This allows us to be 100% lint free.

sgtm, jordan's original lint file had it set to 2 which seems a little conservative ... I like 4 :)
:+1:


Use standard Program.cs for samples.

What does the pull request do?
Use a standard Program.cs from our templates for samples.
Also merge ControlCatalog.NetCore into ControlCatalog.Desktop, dual targetting netfx and netcore in the same project.

I think single-targeted net core project was there because of full .net targeting issues on non-windows platforms. I'm not sure that they are completely solved.

With the newly released framework targeting pack NuGet packages, we should be able to alleviate those issues most likely.

You have also removed /dev/fb0 platform support from the catalog.

Ah ok, I thought the problems that required two projects had been solved. Should I restore the dual control catalog projects?

You have also removed /dev/fb0 platform support from the catalog.

Ah yes, that was only in netcore. I will add that back in.

@kekekeks i've reinstated ControlCatalog.NetCore.

Closing this as it's out-of-date. We probably want to revisit though.


Untangle CheckoutSessionMixin

I recently had to work on a checkout REST API based on Oscar, and had to get the shipping address and method stored in the session. The mixin currently carries the request and session data as state around and is initialised in dispatch. That makes sense when it's used in views, but there's a lot of methods in there that could be helpful outside of that context.
I'm not entirely sure what the right approach is. Maybe limiting the scope of the mixin to handle the  validating the pre and skip conditions makes sense. All other logic could live in individual methods.

Yes, it does make sense to decouple CheckoutSessionMixin into two classes:

session validation mixin, with all methods which require request parameter and with the initiation in dispatch method;
order submission data mixin.

Backwards compatibility would be supported by inheriting both mixin classes under the old name, but will make the whole functionality more re-usable.

Made attempt to decouple, hence reviewed mixin again and now not sure if it does make sense, since checkout methods are interrelated, e.g.:
check_a_valid_shipping_address_is_captured calls get_shipping_address, skip_unless_payment_is_required calls get_shipping_address and get_order_totals.


Investigate Missing Testimony in Search

Problem
After we successfully got the Typesense sync job running again, we noticed an odd discrepancy in the data - exactly 2 testimonies were missing after the job completed (in the dev environment). To ensure there isn't the potential for more serious data loss on Prod, we should investigate what went wrong here and fix the job if we discover the issue.
Success Criteria

Discover which 2 testimonies are not syncing correctly to the Typesense index

If found, see if there's a common link that needs to be addressed in the job logic to ensure a successful sync
If no link is apparent, add additional error logging to the sync job (so we can try to collect more data on the next sync, if the issue re-occurs)

Looks like no testimonies are missing after all! But we’ll need a new ticket to add the 'admin' role into the category mapping.


Example is broken: whisk.NewClient(http.DefaultClient, nil)

From the README example:
client, _ := whisk.NewClient(http.DefaultClient, nil)
action, resp, err := client.Actions.List("hello")

But this breaks, since inside the NewClient() code it calls if config.Insecure {..} on a nil config, which panics with panic: runtime error: invalid memory address or nil pointer dereference

@tleyden I have resolved this issue. Please verify.
If it still exists, feel free to reopen it.


Switching code editor tabs slow in workspace with many tests (~150,000)

Does this issue occur when all extensions are disabled?: No

VS Code Version: 1.95.3
OS Version: Windows 11 23H2

Version: 1.95.3 (system setup)
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631

Steps to Reproduce:

Open a vscode workspace with many tests (in my case ~150,000)
Wait for the language extension to discover all the tests in the project. In my case this is done by C# Dev Kit, though I doubt this matters.
switching between code editor tabs takes a full second for vscode to become responsive again.

I profiled the extension host while it was hanging, which show practically 0% CPU usage.
Next, I profiled the main window. See Trace-20241211T121347.json
The bulk of time is spent in encodeURIComponentFast which is triggered by testingDecorations.ts:

Notes:

This happens on all editors in the window, even on file types not associated with the tests. E.g. switching between Markdown files is slow too. Though, switching to e.g. the "Settings" tabs doesn't have this problem, presumably because it isn't a code editor.
The delay is the same regardless of whether the open file contains any tests or not.
I have the Test Gutter disabled, so AFAIK, there no need to be computing this information in the first place.
Observation as someone not familiar with this codebase all: I notice the code in question already "spawns" an async function to prevent blocking. Though, looking at the profile, all await points end up being scheduled on the microtask queue of the original mousedown event handler, so the UI rendering is blocked anyway.

I wasn't able to quite reproduce performance as bad as you had, but I made some changes which I think should resolve your issue. Please let me know.

First of all, thanks for the quick response! However, the problem still appears. I've taken a new profiler snapshot: Trace-20241216T201448.json
Most time is still spent in encodeURIComponentFast, like above.
I'm on:
Version: 1.97.0-insider (user setup)
Commit: ce50bd4876af457f64d83cfd956bc916535285f4
Date: 2024-12-16T05:04:30.005Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631


CompleteMultipartUpload Request body error

I found a bug in the XML parsing for the complete-multipart-upload operation.
the root object should have the name CompleteMultipartUpload but is CompletedMultipartUpload
// src/ops/generated.rs:11490
impl<'xml> xml::Deserialize<'xml> for CompletedMultipartUpload {
    fn deserialize(d: &mut xml::Deserializer<'xml>) -> xml::DeResult<Self> {
-        d.named_element("CompletedMultipartUpload", |d| d.content())
+        d.named_element("CompleteMultipartUpload", |d| d.content())
    }
}

I am not that familiar with the code generator maybe you could give me some directions and I could make a pull request

Thanks! I have just updated the readme and added some guides. I'm looking into this bug right now.


Auto-resizing of text boxes in Ubuntu Firefox

When running Firefox on an Ubuntu VirtualBox, text boxes resize too aggressively, becoming less than the height of the text in the box.

Also in the category of weird Ubuntu Firefox errors: the right-click canvas menu disappears immediately after right-clicking, making it impossible to add or delete canvases.


chunk-NRQ5LZ2P.js:97 [Vue warn]: onUnmounted is called when there is no active component instance to be associated with

Environment

Operating System: Windows_NT
Node Version:     v18.16.1
Nuxt Version:     3.6.1
Nitro Version:    2.5.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      devtools, app, css, modules, build, runtimeConfig, quasar, image, anime, dayjs
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction


L10n plural & select didn't support argument with underscore

Steps to Reproduce

The following ARB was working before :'(
the issue seems to be around underscore inside placeholder variables.

Execute flutter gen-l10n

arb-dir: lib/l10n/arb
output-dir: lib/l10n/generated
template-arb-file: app_en.arb
output-localization-file: l10n.dart
output-class: L10N
synthetic-package: false
nullable-getter: false

the following not work
"test_quantity_bonus_string": "{quantity_issue, plural, =1{{quantity_issue} quantity to collect {bonus} points} other{{quantity_issue} quantities to collect {bonus} points}}",
  "@test_quantity_bonus_string": {
    "placeholders": {
      "quantity_issue": {
        "type": "int"
      },
      "bonus_issue": {
        "type": "int"
      }
    }
  }

the following work
"test_quantity_bonus_string": "{quantity, plural, =1{{quantity} quantity to collect {bonus} points} other{{quantity_issue} quantities to collect {bonus} points}}",
  "@test_quantity_bonus_string": {
    "placeholders": {
      "quantity": {
        "type": "int"
      },
      "bonus_issue": {
        "type": "int"
      }
    }
  }

Expected results:
no issue
Actual results:
ICU Lexing Error: Unexpected character

Code sample

Logs

[✓] Flutter (Channel stable, 3.7.1, on macOS 13.1 22C65 darwin-arm64, locale fr-FR)
    • Flutter version 3.7.1 on channel stable at /Users/earminjon/fvm/versions/3.7.1
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7048ed95a5 (5 days ago), 2023-02-01 09:07:31 -0800
    • Engine revision 800594f1f4
    • Dart version 2.19.1
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/earminjon/Library/Android/Sdk
    • Platform android-33, build-tools 33.0.1
    • ANDROID_HOME = /Users/earminjon/Library/Android/Sdk
    • Java binary at: /Users/earminjon/Library/Java/JavaVirtualMachines/corretto-11.0.17/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment Corretto-<IP_ADDRESS>.1 (build 11.0.17+8-LTS)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version 2022.1)
    • Android Studio at /Users/earminjon/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9514443/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] IntelliJ IDEA Ultimate Edition (version 2022.3.2)
    • IntelliJ at /Users/earminjon/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 72.0.4
    • Dart plugin version 223.8617.8

[✓] IntelliJ IDEA Ultimate Edition (version 2022.3.2)
    • IntelliJ at /Users/earminjon/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/223.8617.56/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (3 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 13 (API 33) (emulator)
    • macOS (desktop)             • macos         • darwin-arm64   • macOS 13.1 22C65 darwin-arm64
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 109.0.5414.119

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

@EArminjon
Please check this comment and see if it helps in your case.

@EArminjon
Please check this comment and see if it helps in your case.

Not working.

@EArminjon
I added both (not working and working) samples  in app_en.arb file and ran flutter gen-l10n which gave me below console error:
dhs@Dhss-MacBook-Pro test_app % flutter gen-l10n
The arb file lib/l10n/app_en.arb has the following formatting issue:
FormatException: Unexpected character (at character 29)
"test_quantity_bonus_string": "{quantity_issue, plural, =1{{quantity_issue}...

I tried above using latest master version.
If this does not represent your use case, please provide complete steps to replicate.

@darshankawar   : https://github.com/EArminjon/l10n-issue
Using flutter 3.7.1
flutter pub get
flutter gen-l10n
Because l10n.yaml exists, the options defined there will be used instead.
To use the command line arguments, delete the l10n.yaml file in the Flutter project.

[app_en.arb:test_quantity_bonus_string] ICU Lexing Error: Unexpected character.
    {quantity_issue, plural, =1{{quantity_issue} quantity to collect {bonus} points} other{{quantity_issue} quantities to collect {bonus} points}}
             ^
Found syntax errors.

@EArminjon I looked at the repo you shared and some pieces were missing from it.
For example:
generate: true in pubspec.yaml.
The directory structure inside lib folder:

l10n.yaml:
arb-dir: lib/l10n
template-arb-file: app_en.arb
output-localization-file: app_localizations.dart

Making above changes and then running your repo didn't give me the reported error:
dhs@Dhss-MacBook-Pro l10n-issue % flutter gen-l10n
dhs@Dhss-MacBook-Pro l10n-issue %

I tried above using latest master version.

@darshankawar i updated (force pushed) my repo (to add generated: true and a little fix inside the arb)
I still can reproduce the issue. Can you try again using flutter 3.7.1 ?

@EArminjon
I verified your repo on latest stable and it does throw the reported error:
[app_en.arb:test_quantity_bonus_string] ICU Lexing Error: Unexpected character.
    {quantity_issue, plural, =1{{quantity_issue} quantity to collect {bonus}
    points} other{{quantity_issue} quantities to collect {bonus} points}}
             ^
Found syntax errors.
dhs@Dhss-MacBook-Pro l10n-issue %

But running the same on latest master works as expected and the app_localizations_en.dart file is generated successfully.
This indicates the behavior is fixed on master and should be available in next stable release.


Missing Github Workflows Steps for Creating a New GitHub Repository

Summary
To incorporate the api-test folder, I needed to create a new GitHub repository. However, I overlooked the requirement to add GitHub workflows (actions), which was not mentioned in the CONTRIBUTING.md guidelines. I didn't realize I needed to check the GitHub workflow repository and add relevant workflows to my repository.
Tasks

[ ] Modify the CONTRIBUTING.md to add the workflows steps when creating a new repo

Acceptance Criteria

Steps are detailed for adding GitHub workflows during the creation of a new repository.
The added steps should be clear and concise, providing comprehensive guidance for contributors.
Upon completion, contributors should be able to follow the revised instructions seamlessly to include GitHub workflows when initiating new repositories within the organization.

As discussed elsewhere, a doc explaining what is required to setup a new repository should be done within dev-rel-docs, perhaps linked from CONTRIBUTING.md as additional documentation. CONTRIBUTING focuses on the day to day contribution to a repo (pull requests work).
Note that there are some minimal backend documentation that starts with setting up a repository but does not specify the workflow:
https://github.com/ai-cfia/dev-rel-docs/blob/main/Minimal-Backend-Setup-Guides/PYTHON-BACKEND-SETUP.md


Rinkeby VRF Coordinator updated

The old Rinkeby VRF Coordinator value written here does not work. Hence updated with the new value.

Hello @meetjain74,
thank you very much for your contribution. Actually, the address is correct, 0x6168499c0cFfCaCD319c818142124B7A15E857ab is the Rinkeby coordinator address of VRF v2.
the address that you mentioned 0xb3dCcb4Cf7a26f6cf6B120Cf5A73875B7BBc655B is the Rinkeby coordinator address  of VRF v1 , which you can also find  in here.
To get familiar with VRF v2, I recommend starting with Get random number tutorial which explains how to get a random number using VRF v2.
I'm going to close this pull request but don't hesitate if you have questions or remarks.
thanks again for your help.

Great and thanks
But I first used the address for v2 i,e  0x6168499c0cFfCaCD319c818142124B7A15E857ab but it didn't work and transactions were not happening on it.
I don't know what the issue is!

@meetjain74
what is the issue exactly? Have you tried first to get familiar with  VRF v2 using this tutorial ? If not, I suggest that you follow the tutorial then get back in case you have queries

I followed this tutorial.
I was facing this issues when I used that address and the issue was solved when I changed the address. Do you know the reason?

@meetjain74
I see that you are not using the right functions.
fulfillRandomness expects bytes32 requestId and uint256[] memory randomWords. You can share the whole code in here but I understand that you are using a consumer which is compatible with VRF v1 , you should adapt it to make it work with VRF v2.
This link Migrating to VRF v2 will be useful to you

Thanks for having my doubts clear.
I should use the correct function name like fulfillRandomwords, etc to work with V2. Gotcha

@meetjain74 no problem 👍   . By the way, you can also join our discord Channel if you have not already. It is much faster for obtaining help


Managed Service Administrator role title seems to be out of date

The "Managed Service Administrator" role does not reflect the built in role visible in the portal and now seems to have changed to "Teams Rooms Pro Manager"
This also applies to details on other pages such as https://learn.microsoft.com/en-us/microsoftteams/rooms/rooms-pro-rbac

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

ID: 5f92b3e4-3b95-271d-6926-f31704caae5f
Version Independent ID: 8089fb49-82fe-3e20-1ae6-6b98bf2b2516
Content: Accessing the Pro Management portal - Microsoft Teams
Content Source: Teams/rooms/enrolling-mtrp-managed-service.md
Service: msteams
GitHub Login: @altsou
Microsoft Alias: altsou

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Jar for retrofit logansquare

Hi,
Where can i find jar of this library ?

The library is distributed via jcenter. If you really need to include a JAR, you can grab it from there.


option to keep certain number of kernels

it would be amazing if the module had an option to allow it to keep back a certain number of kernels
currently it removes all old kernela excluding the latest you have installed OR the latest one if you havent restarted yet to apply it
an option like maybe --keep 3 to say keep the 3 latest kernels

I agree with you

anybody looks for this feature
a fork has implemented this feature to leave behind 2 kernels for recovery purposes - https://github.com/rhyven/pvekclean

This feature has been added to version 1.3 (just released). Thank you all for your patience with this being added.


[HUDI-3032] Do not clean the log files right after compaction for met…

…adata table
Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@prashantwason : Would you mind taking a look at this PR.

@hudi-bot run azure


[wip] testMatch and testRegex + presets

Warning: #753 must be merged first

[x] fixes #756 - CLI command config:migrates overrides testMatch if the user uses testRegex
[x] adds 3 presets (see discussion in #740):

ts-jest/presets/default: same as the old ts-jest preset (the old one is now an alias to this one)
ts-jest/presets/js-with-ts: for users who have allowJs: true in their tsconfig file and wants js files to be compiled by TypeScript thru ts-jest
ts-jest/presets/js-with-babel: for users who want to have babel-jest to compile their js without going thru ts-jest

[ ] update the config:migrate CLI command so that it takes the appropriate preset
[ ] document the new presets
[ ] document the fact that presets uses testMatch as Jest defaults, so if one wants to use a preset AND testRegex (instead of testMatch), he must also set testMatch to null

reviewers: Since this includes commits from #753, the diff of this PR only is visible there

Pull Request Test Coverage Report for Build 1891

13 of 13 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 91.112%

Totals

Change from base Build 1889:
-0.03%

Covered Lines:
976

Relevant Lines:
1021

💛  - Coveralls


Implement SimSockets by having 2 SimFiles for send/recv

Replace each socket fd with 2 SimFiles, one for send and one for recv.
posix.sockets still contains a list of current sockets
posix.dumps now can take a SimSocket and returns a SocketResult namedtuple that contains the results of concretizing the two SimFiles for the socket.
i.e.
for socket_fd, curr_socket in f.state.posix.sockets.iteritems():
    result = f.state.posix.dumps(curr_socket)
    # result.send contains concretized send
    # result.recv contains concretized recv

There is also a test case for sockets included as well.

So we're in the process of getting our binaries repo on github. When this happens, would you mind moving the testcase binaries there and moving the testcases that use angr to the angr repo? Should be later today; I'll give you another ping when it's ready.

I would have no problems at all with that. Should I simply remove the test cases with this PR?

Hey! Really sorry for the delay on this. When I get super busy, I start packet dropping, and this packet got dropped.
I pushed the binaries repo: https://github.com/angr/binaries. Could you put the binaries in that repo, and the testcases that use angr in the angr repo?
Thanks for the contribution!

Moved the binaries and test suite to the right repos... i think..

Ok, how does this look? ;-)

Hey! Just letting you know we haven't forgotten about this -- there's a big conference deadline coming up and we're all working furiously, but I'll get to this next Friday!

@zardus ping!

Sorry, this PR totally fell through the cracks last Usenix deadline.
Looking over it again, I am a bit concerned that state.posix.dumps can return two different types -- a string (for files), and a namedtuple (for sockets). I don't have a good solution, but I'd like to avoid this sort of type mixing.
In general, we might take this opportunity to do the "dialog refactor" that we've always wanted to get to -- unifying files and sockets in a more generic SimStream or something?

Now that simuvex has been merged into angr, I'm going to close this PR. This should be much easier on the new angr, but we should do the work in the angr repo.
Thanks!


PostgreSql Question

I'm trying to switch over from using Azure to using Digital Ocean. I want to switch from SqlServer to PostgreSql, but I'm not sure what exactly is needed. I'm not getting the code from Nuget - I'm getting it directly from github so that I can modify stuff.
I have a version of linux running, and .net core is running as well. I'm just not clear on how to connect to the database.
Is the code for Blogifier.Core.PostgreSql available somewhere? Can I just use the Blogifier.Core project and point my webapp to PostgreSql for the database? I guess I'm not exactly clear on how to make this work on Linux with a different type of database.

The PostgreSql package built on the fly from Core by replacing SQL Server specific code with PostgreSql code, there is no separate project.
If you asking about connection string, this is what I'm using on Digital Ocean:
"User ID=blogifier;Password=yourpass;Host=localhost;Port=5432;Database=blogifier;Pooling=true;"
I did have to do some odd things like have to name user and DB with the same name and run SQL script to create database because EF migrations would not run, but I kind of expected some extra effort from Linux environment.
I really need to write a blog post on setting up with Digital Ocean, will do when have time.

I have a few improvements you guys might be interested in.
I modified the Blogifier.Core project so that it doesn't have any dependencies on SqlServer (or Postgres, etc). You now pass the database options from the host application to Blogifier.Core, and it configures itself for the appropriate database. This should allow for a single Blogifier.Core project that supports many databases, not just SqlServer. Also, i don't think there's a need anymore for a separate Blogifier.Core.PostgreSql package if you guys accept these changes.
Also, I added some attributes to BaseEntity, which allowed me to do a migration to PostgreSql. This still needs to be tested for a clean install of SqlServer (I didn't do that), but I was able to create a blog without running any SQL scripts on PostgreSql, and everything seems to be working properly.
The commit with all the necessary changes is located at: https://github.com/murst/Blogifier.Core/commit/12385cb8deb59b8e4f79867c24655655371c159f
There's also a small fix to retrieving a post, because I ran into an error when my blog did not contain any posts.

Edit: Also, I just realized that my startup.cs has some code about forwardedheaders. That was needed to get it to work on linux. Just ignore that. Sorry.

Just a quick update: the changes I made to BaseEntity seemed to work on my Windows PostgreSql db; however, it doesn't appear to work on Linux.  Basically, I can't get the primary keys for the tables to auto-increment in PostgreSql on linux using code-first. I'll try working on it some more later.

Ok, please let know if you'll get it working - I would love to consolidate all in single package.

You can actually use the code in the commit to make everything into a single package already. What's not working is the database migrations in PostgresSql on Linux, but AFAIK, that doesn't work in the current packages either.
I'll let you know if I come up with a fix for the primary key in BaseEntity.

ok, got it working now. Had to update the migrations since they had specific code for SqlServer, but nothing for PostgreSql.
https://github.com/murst/Blogifier.Core/commit/ca2d7c359e0734ec8d3bea92506ca81a3a2899d5
If you update the code w/ the changes from the 2 commits linked in this thread, you should be able to have a single package that supports both SqlServer and PostgreSql, and the migrations should be working for both.
If you want to support more databases (such as MySQL), the only thing that would be needed (I think) is just updating the migrations with annotations specific to the new database.

Cool, will check it out tomorrow. That latest commit with migration - it was generated by EF based on annotation you added to base entity, right? Or updated manually?

I added that manually.
When I added the the attributes to BaseEntity (and before I manually added the annotations), I was able to generate the correct SQL when running it on PostgreSql on Windows. However, it didn't generate the correct SQL on Linux. I'm not sure if that is because of the different OSes, or if it was because I applied the migrations to different states of the database.
After I manually added the annotations to the migration script, the website generated the correct SQL when creating the tables in PostgreSql (I had already created an empty database in Postgres that had the same name as the user in my connection string).

I updated code with few minor changes and set it pass SQL server as an option to the core. Will have to regenerate migrations to check how it works but should be fine, going to do it later.


ErrorCatcher renderers do not have access to the response object.

What steps will reproduce the problem?
#146 issues would require you to add headers to the response. It is also required for other applications where a change in the cache header is warranted in the response, e.g. if the error is persistent, it may be appropriate to use stale-if-error with a higher value.
What do you get instead?
It is not currently available.

Q
A

Version
3.0.x-dev

PHP version
-

Operating system
-

I see multiple ways solving it:

We may merge ErrorCatcher and ErrorHandler. But I don't like the solution because ErrorHandler is used also for fatal errors that aren't in the context of PSR-7 request-response.
We may make renderer return headers as well. That would work but we have to rename it somehow since it won't be strictly rendering anymore.

We may make renderer return headers as well. That would work but we have to rename it somehow since it won't be strictly rendering anymore.

I prefer this solution. What you may need:

override headers (array list)
status code override (int)
At the moment, I think these are enough.

class ThrowableRenderer
{
    // ...
    public function render(\Throwable $t): RenderedError;
}

class RenderedError
{
    public function getBody(): string;
    public function getHeaders(): array;
    public function getStatusCode(): int;
}

Like this?

yes


Terraform Provider Updates

DEVOPS PULL REQUEST
Related Issue

#5408

Changes Proposed

Minor Upgrades

pagerduty
random
azurerm
okta

Some changes are based on deprecation warnings.

enabled_log in ops/services/alerts/app_service_metrics/exceptions.tf
enabled_log in ops/services/app_gateway/main.tf'
Setting up dynamic rules with the enabled flag in ops/services/web_application_firewall/main.tf

Testing

Don't deploy to an environment because they can't be rolled back. Feel free to poke dev if you'd like to see an environment running with these updates. Here is the deployment for that.
Here are the terraform plans for production and staging
Run this job if you want to see an ad-hoc terraform plan for a particular environment

Checklist for Primary Reviewer
Infrastructure

[ ] Consult the results of the terraform-plan job inside the "Terraform Checks" workflow run for this PR. Confirm that there are no unexpected changes!

Security

[ ] Changes with security implications have been approved by a security engineer (changes to  authentication, encryption, handling of PII, etc.)
[ ] Any dependencies introduced have been vetted and discussed

Cloud

[ ] Oncall has been notified if this change is going in after-hours
[ ] If there are changes that cannot be tested locally, this has been deployed to our Azure test, dev, or pentest environment for verification

Documentation

[ ] Any changes to the startup configuration have been documented in the README

LGTM! with questions. Also is there a way to unify where these versions are declared, it would be a lot cleaner and less error prone if its set in one place

We need to have these provider blocks defined in the directory where we terraform init.
We could condense them if we wanted to update our environments to utilize terraform workspace feature. That comes with its own set of challenges that we are not really prepared for. It's just different and I would say it ends up being more prone to catastrophic errors.


do not hard depend on mock

I am not sure whether you need to support all versions on python 3, but in case that yes, could you please consider something like
Index: schedule-1.1.0/test_schedule.py
===================================================================
--- schedule-1.1.0.orig/test_schedule.py        2021-03-07 11:49:24.000000000 +0100
+++ schedule-1.1.0/test_schedule.py     2021-09-08 10:48:44.066906764 +0200
@@ -1,8 +1,11 @@
 """Unit tests for schedule.py"""
 import datetime
 import functools
-import mock
 import unittest
+try:
+    import unittest.mock as mock
+except ImportError:
+    import mock

 # Silence "missing docstring", "method could be a function",
 # "class already defined", and "too many public methods" messages:

import unittest.mock as mock should be enough


change SQLite database with something else

SQLite require CgO and is hard to cross compile.
Thinking about an unstructured DB, like filesystem or embeded nosql

Idea : store everything on disk with git to version configurations.

starting a pipeline triggers a commit


3D models appear upside down when rotated

Phenomenon：

I try to fix it:

But it still happpened.
Sandcastle example:
https://sandcastle.cesium.com/index.html?src=3D Tiles Clipping Planes.html
Browser:
Any browser.
Operating System:
Any windows system.

Hi @ABoyCDog, I'm not sure I completely understand the issue. Is the model itself rotated, or is this unexpected behavior after using the default camera controller?

The second, is this unexpected behavior after using the default camera controller.
It apper when the camera is on the model bottom view, and then rotateUp the camera, it happened.
Thanks for answer that. @ggetz

And on the top view, it won't happen.

Hi @ABoyCDog, I'm not able to reproduce the problem. Can you tell us the position of the camera that results in this upside-down appearance?
See the Performance Testing Guide for an explanation of how to capture the camera position.
Thanks!

I'm closing this issue due to inactivity. If you believe this is still an issue, please feel free to re-open. Thanks!


Introduce USDT trace points

Description
Add systemtap into the builder to allow defining USDT, and add one to capture events when a new process was discovered.
Checklist

[ ] Investigated and inspected CI test results
[ ] Updated documentation accordingly

Automated testing

[ ] Added unit tests
[ ] Added integration tests
[ ] Added regression tests

If any of these don't apply, please comment below.
Testing Performed
Manual testing.

Will this be part of release builds? Do you need to make any changes to midstream or konflux environments?

Will this be part of release builds? Do you need to make any changes to midstream or konflux environments?

Indeed, Konflux is failing now. From what I see it doesn't use the builder image, this should fix it: https://github.com/stackrox/collector/pull/1646


Errors field is wrong with nested array

Current Behavior
I'm building a form with nested fields, up to 3 level down.
uploadSelector: Yup.string().required(i18n.t`Please select an option`),
inboxes: Yup.array().of(Yup.string()).min(1).required(i18n.t`At least one inbox should be selected`),
patients: Yup.array<PatientForm>().of( .  // LEVEL 1
    Yup.object<PatientForm>().shape({
        id: Yup.string().required(i18n.t`Patient should have a local id`),
        firstName: Yup.string().required(i18n.t`First Name is required`),
        lastName: Yup.string().required(i18n.t`Last Name is required`),
        .......................
        import: Yup.boolean().notRequired(),
        studies: Yup.array<StudyForm>().of(               // LEVEL 2
             Yup.object<StudyForm>().shape({
                 id: Yup.string().required(i18n.t`Study should have a local id`),
                 import: Yup.boolean(),
                 modality: Yup.string().when('import', {
                    is: true,
                    then: Yup.string().required(i18n.t`Date of birth is required`),
                  }),
                studyDescription: Yup.string().when('import', {
                   is: true,
                   then: Yup.string().required(i18n.t`Study description is required`),
                 }),
                 .....
                series: Yup.object<SeriesForm>().shape({ .  // LEVEL 3
                    instances: Yup.array().of(Yup.mixed()),
                    description: Yup.string(),
                    modality: Yup.string().required(i18n.t`Series modality is required`),
                });
        )).min(1, 'At least one patient is required'),

The errors field reports a wrong error path with no value inside the object.
The touched field instead has the correct path of the touched field.

Here is a screenshot with the form values. The field patients[0].studies[0].studyDescription should report the error but it's not.

I'm sorry I can't recreate a working example because it's too complex to reproduce now.
I'm using FieldArray components to render the form
Expected behavior
When a field is not valid the formik errors field should report the exact path with the error message.

Software
Version(s)

Formik
1.4.2

React
16.6.3

TypeScript
3.1.1

Browser
chorme

npm/Yarn
npm

Operating System
OSX HighSierra

For what it's worth, I'm also running into this issue.

Closing as stale for long, feel free to reopen


Adjust the priority to 900 can solve constraint warning, like "Unable to simultaneously satisfy constraints"

func setHeight(height: CGFloat) {
    if self.heightConstraint == nil {
        self.heightConstraint = NSLayoutConstraint(
            item:self.view,
            attribute:NSLayoutAttribute.Height,
            relatedBy:NSLayoutRelation.Equal,
            toItem:nil,
            attribute:NSLayoutAttribute.NotAnAttribute,
            multiplier:0,
            constant:height)

        //Adjust the priority to 900 can solve the constraint warning, like "Unable to simultaneously satisfy constraints"
        self.heightConstraint!.priority = 900

        self.view.addConstraint(self.heightConstraint!) // TODO: what if view already has constraint added?
    }
    else {
        self.heightConstraint?.constant = height
    }
}

Good to know! Does this still set the custom height of the keyboard correctly?

Yes, can also set the custom height of the keyboard correctly！

yay!! thanks @durgiya, I was debugging that and just find your answer, really annoyed by the Constraints breaking messages.

@durgiya thanks, it works

thanks,well done.


QSU Group Key Reification

Group keys are now first-class identities along side shift ids and reducer buckets. This allows them to be properly reified when referenced in an autojoin.
Fixes #3170.
Fixes #3252.

@djspiewak resolving them now...

@djspiewak @edmundnoble Conflicts resolved.

Will merge once built


Update Codable snippet to use explicit typing

This updates the snippet for using Codable to fetch data to use explicit typing introduced in https://github.com/firebase/firebase-ios-sdk/pull/9101
Signed-off-by: Peter Friese<EMAIL_ADDRESS>

The Firestore version in these snippets is pretty heavily outdated, so you'll need to update it before CI passes.


Does it support Server Side Routing

Hi @technige , I hope you're having a great time at Elastic m8 .
Wondering if you would be aware of any issues py2neo could have with Neo4j's SSR ?
Cheers !

Hey @ikwattro - I never actually used SSR, so the real answer here is that it might work, and might not. I assume that since you've opened an issue though, it probably isn't.
I never considered the design of Neo's SSR to be particularly well thought out, which is largely why I've avoided it. While I was certainly never against the idea in theory, the architecture that emerged consisted of too many random independent ideas, which generally weren't considered from an holistic perspective. And so this made system configuration harder than it needed to be, and I therefore never spent time trying to work out the exact combination of settings to made everything work together.
So ultimately, there's a very high probability that py2neo won't work with SSR in its current form, although I've never tested that.

@technige Indeed, it seems it's not using the right node when using SSR, that's ok, I just wanted to get an idea if it were supposed to be so after looking inside the codebase and tests where I couldn't find relevant ssr stuff.


refactored integration tests + add slo workloads paths

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

Codecov Report
Base: 62.76% // Head: 62.71% // Decreases project coverage by -0.05% :warning:

Coverage data is based on head (d54c8e5) compared to base (27a45b8).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #572      +/-   ##
==========================================
- Coverage   62.76%   62.71%   -0.05%
==========================================
  Files         221      221
  Lines       21539    21539
==========================================
- Hits        13518    13508      -10
- Misses       7352     7363      +11
+ Partials      669      668       -1

Flag
Coverage Δ

1.16.x
62.20% <ø> (-0.23%)
:arrow_down:

1.19.x
62.53% <ø> (-0.01%)
:arrow_down:

1.20.x
62.49% <ø> (+0.13%)
:arrow_up:

insecure
52.76% <ø> (-0.01%)
:arrow_down:

integration
53.28% <ø> (+0.02%)
:arrow_up:

macOS-latest
44.38% <ø> (-0.01%)
:arrow_down:

secure
53.16% <ø> (+0.03%)
:arrow_up:

ubuntu-latest
62.70% <ø> (-0.03%)
:arrow_down:

unit
44.39% <ø> (-0.10%)
:arrow_down:

windows-latest
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

internal/wait/wait.go
28.57% <0.00%> (-14.29%)
:arrow_down:

internal/xerrors/operation.go
69.62% <0.00%> (-2.54%)
:arrow_down:

internal/topic/topicreaderinternal/reader.go
68.25% <0.00%> (-2.39%)
:arrow_down:

internal/table/client.go
84.18% <0.00%> (-0.86%)
:arrow_down:

...al/topic/topicreaderinternal/stream_reconnector.go
93.00% <0.00%> (-0.42%)
:arrow_down:

retry/retry.go
91.34% <0.00%> (+4.80%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[spi_device/passthrough] CMD_INFO slots 0-10 reset values

CMD_INFO slots 0 to 10 are reserved for specific commands. If it is the case, why reset values (at least for opcodes) are not set to these command values instead of 0's ? Also, why are they writable?
As it stands now we can have illegal data written to these registers and provoke OnlyOneDatapath_A assertion error.

CMD_INFO slots 0 to 10 are reserved for specific commands. If it is the case, why reset values (at least for opcodes) are not set to these command values instead of 0's ? Also, why are they writable?

That is due to the multireg feature not allowing arbitrary reset values per register. And the read commands may have different dummy size, and address requirements. So that's why those fields are configurable

As it stands now we can have illegal data written to these registers and provoke OnlyOneDatapath_A assertion error.

Could you share me the waveform?

#9834 PR - command:
./util/dvsim/dvsim.py hw/ip/spi_device/dv/spi_device_sim_cfg.hjson -i spi_device_pass_cmd_filtering --fixed-seed 3 --waves --xprop-off -v h --max-parallel 1

Looks like, the programmed opcode is not unique. The logic assumed the programmed opcode should be unique in each cmd slot.
By the way, after introducing the valid bit in CMD_INFO slot, I think the cmdparse should see the valid bit also. Let me quickly revise the design to check the validity.
Thanks!

On Dec 28, 2021, at 1:03 PM, kosta-kojdic @.***> wrote:
#9834 https://github.com/lowRISC/opentitan/pull/9834 PR - command:
./util/dvsim/dvsim.py hw/ip/spi_device/dv/spi_device_sim_cfg.hjson -i spi_device_pass_cmd_filtering --fixed-seed 3 --waves --xprop-off -v h --max-parallel 1
—
Reply to this email directly, view it on GitHub https://github.com/lowRISC/opentitan/issues/9833#issuecomment-1002280809, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJDG3XFZZ7NGZ6MCGAUAJ3UTIQZPANCNFSM5K34VXXA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were assigned.

@eunchan any updates on this issue? Did you make some design revisions?

The pending PR addresses the valid bit issue. But firstly please make sure you programmed the cmd_info slot correctly.

The pending PR addresses the valid bit issue. But firstly please make sure you programmed the cmd_info slot correctly.

By programming CMD info slot correctly, do you mean programming all fixed slots (the ones before the slot I programmed) with proper values?

Yes. Do not  program the same opcode value into two slots. Then the assertion won't fire.

On Jan 10, 2022, at 8:26 AM, kosta-kojdic @.***> wrote:
The pending PR addresses the valid bit issue. But firstly please make sure you programmed the cmd_info slot correctly.
By programming CMD info slot correctly, do you mean programming all fixed slots (the ones before the slot I programmed) with proper values?

OK, so if we keep reset values for some slots, even if these slots are not enabled, assertion will fire?

Yes, in the current design. After PR #9875 is merged, it won't.

On Jan 10, 2022, at 8:38 AM, kosta-kojdic @.***> wrote:
OK, so if we keep reset values for some slots, even if these slots are not enabled, assertion will fire?
—
Reply to this email directly, view it on GitHub https://github.com/lowRISC/opentitan/issues/9833#issuecomment-1009084142, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJDG3T6QFWK3CCQUZZY3ULUVMDRHANCNFSM5K34VXXA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.


How can I detect mouse clicks?

I know that each CDOTAPlayer entity has m_iCursor.0000/0001 to show the player's mouse position at any given moment, but I'm wondering if there is some kind of event log for player's mouse click locations, and if there's a way to differentiate a move, attack-move, ping, right vs left click on objects/items to select/buy/use, or any other click-related action.
Thank you!

There's two user messages, CDOTAUserMsg_SpectatorPlayerClick and CDOTAUserMsg_SpectatorPlayerUnitOrders which clarity will serve with @OnMessage. The second one has a position-property, which likely is coordinates a players ordered a unit to move/attack to. Other than that, I don't think there's something.

Thanks a lot @spheenik ! I'll take a look at that and see what I can get.


Internalize OnServerAddPlayer Safety Checks

Functionally the same, but moves safety checks to an internal method that is registered as the handler and calls the virtual method.
From reviewing user code samples, my observation is that when OnServerAddPlayer is overridden, devs often don't call the base method (for good reasons) and never include these safety checks in their override, and IMHO they shouldn't have to.  Virtual methods should be empty or as tiny as possible so that overrides don't have to copy a bunch of code.

Turns out, uMMORPG in fact does override OnServerAddPlayer, and in fact leaves out the exact safety checks in the PR, and should throw "The PlayerPrefab is empty on the NetworkManager. Please setup a PlayerPrefab object." error. 😄
That's too funny!

Turns out, uMMORPG in fact does override OnServerAddPlayer, and in fact leaves out the exact safety checks in the PR, and should throw "The PlayerPrefab is empty on the NetworkManager. Please setup a PlayerPrefab object." error. 😄
That's too funny!

It's not called in uMMORPG because it would log 'empty player prefab' errors otherwise, because uMMORPG doesn't use the player prefab slot.
about your code: what about the cases where autoCreatePlayer is disabled but some calls AddPlayer even though playerPrefab is null?

about your code: what about the cases where autoCreatePlayer is disabled but some calls AddPlayer even though playerPrefab is null?

I already put in checks for autoCreatePlayer being false...what'd I miss?

which checks do you mean exactly?
when looking at this commit, it seems like if someone has autocreate disabled then he wouldn't see the 'playerprefab is null' message

@vis2k It works as expected in all cases.  If Auto-create is not checked and there's no prefab, as in uMMORPG, it stays quiet as it should.  If Auto-create is checked, it will complain about the missing prefab.  You've excluded the warnings in your override in uMMORPG for the exact reason this PR fixes, because you also disabled Auto-create.  Moving the errors to an internal method that runs ahead of the virtual / override protects devs from inadvertently hiding the errors from themselves.

:tada: This PR is included in version 3.14.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Raw API concerns

I have concerns about the current Prisma Client JS raw API.
The tagged template literal raw API is indeed nice to use:
var id = "title"
await client.raw`SELECT * FROM Post WHERE title = ${id}`

That works fine. No sql injections here because we handle that for the user.
However, since we’re encouraging users to use that syntax, I can imagine sooner or later a user will invoke the method directly instead and not change the variables in the template string to parameters for the function:
var id = "'title'; DROP TABLE User;"
await client.raw(`SELECT * FROM Post WHERE title = ${id}`)

and boom, SQL injection!
It seems that the editor's autocomplete feature also uses parentheses per default.
We need to think how we can prevent this from happening. My suggestion is that we only accept the template literal method for one method, and create a new function which makes it clear that the input does not get escaped, like rawNoEscape(...), similar to react's dangerouslySetInnerHtml.

After some more discussions, here is the detailed situation as of today:
Escaping happens whenever using the tagged template form of call.
Escaping doesn't happen when using other forms.
This means that, the following examples don't get escaped:
Example A:
const result: number = await prisma.executeRaw('UPDATE User SET active = $1 WHERE email = $2;', true<EMAIL_ADDRESS>DROP ALL TABLES')
// Will result in an injection 😱

Example B:
let evilmail: string =<EMAIL_ADDRESS>DROP ALL TABLES'
const result: number = await prisma.executeRaw(`UPDATE User SET active = ${true} WHERE email = ${evilmail};`)
// Will result in an injection 😱

But this one will get escaped:
Example C:
let evilmail: string =<EMAIL_ADDRESS>DROP ALL TABLES'
const result: number = prisma.executeRaw`UPDATE User SET active = ${true} WHERE email = ${evilmail};`
// Will be properly escaped 🥰

I created an issue to ensure we escape parameters to cope with Example A above as I believe that this behavior doesn't match the expected standard. (cf. details in the issue #755)
About Example B, while this can indeed be confusing, we can not really expect to differentiate usages where queries are created using some custom complex logic (concatenating strings within a function using multiple conditional statements or loops for example) from simply using template literals. This comes from the TS language to a degree as well.
Executing unparametrized raw queries is necessary to support even if it involves a risk depending on how the query is composed.
The option you're proposing is meant as a strong mean to raise awareness about the risk. The problem with that breaking change is that it adds friction to upgrade, and still requires to know how you should proceed with an escaped query execution, which is not dangerous to execute (defeating the new name of the function).
The need here is to ensure we explain (if not educate) about the risk and explain how it should be done.
I will thus create another issues in the docs for that purpose and we'll see how much more would be needed there.

This should also be safe.
const result: number = await prisma.executeRaw('UPDATE User SET active = $1 WHERE email = $2;', [true<EMAIL_ADDRESS>DROP ALL TABLES'])

Looking at the code https://github.com/prisma/prisma/blob/master/src/packages/client/src/runtime/getPrismaClient.ts#L361 I don't see how example B can work / which code path it uses.

I did a few more tests and it turns out the the examples I had provided did work with proper escaping indeed.
I'll dig deeper into how this is all handled and post an update, but the general proposal for this specific issue is to mostly update our docs, for what I've opened a separate issue here.

After a few more tests and checking with the team, there are two main behaviors:

queryRaw(sql) and executeRaw(sql) will only be executing a single statement, which means some injections won't work (the one with multiple queries trying to drop tables for example) but some will (unveiling additional data using UNION for example)
queryRaw(sql, params) and executeRaw(sql, params) are translated to prepared statements which are inherently secure
queryRaw`sql` and  executeRaw`sql` are translated to prepared statements the same way and are also inherently secure

We need to keep the ability to execute SQL that is prepared elsewhere, leaving users the responsibility to sanitize those, as there are plenty of cases where custom logic can be used to generate an SQL query, or take them from another place without getting the parameters map details which would allow for preparing a statement.
Renaming the method being a breaking change, we will only update the docs to make it clear.
I'll thus close this issue.

What needs to be added in the doc is the usage of the now exposed sql, join, etc that dev can use to create sanitized queries outside the templated method.


Unable to run with LocalDB

I'm using VSTS and the only database available is LocalDB, but SqlClientLibrary apparently can't work with LocalDB on attempt to open connection I get network error:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

The instance is up and running - I'm using it from other applications.
Here is how build.cake looks like:
Task("Create-DB-And-Schema")
.Does(() =>
{
    ExecuteSqlQuery("create database [MyProject-Testing]", new SqlQuerySettings()
    {
        Provider = "MsSql",
        ConnectionString = "Server=(localdb)\v12.0;"
    });
})

Here is a repro:
class Program
{
    static void Main(string[] args)
    {
        System.Data.IDbConnection con = System.Data.SqlClient.SqlClientFactory.Instance.CreateConnection();

        con.ConnectionString = "Server=(localdb)\v12.0;";
        con.Open(); // throws here
    }
}

You problem is with SqlClientLibrary and not the addin itself. You can support multiple databases by implementing a new ISqlQueryRepository and updating the Alias with the new provider
Happy to accept a PR for this when you find a solution :wink:

Yeah.. after enough head banging I found the issue. Two words "String escaping".
The connection string I used in Cake was var connStr = "Server=(localdb)\v12.0;";. But Cake is C#. And in C# backwards slash \ is an escape symbol, so it really should be var connStr = @"Server=(localdb)\v12.0;";
So actually it was not SqlClientLibrary's fault. It was my fault for not putting @ in front of the connection string. Sigh. Simple thing are always the worst to figure out!

Glad you sorted it. Sorry I wasn't much help, I've never had a reason to use LocalDB before.


Can TEA be used to discover new versions of a library

This was raised during our meeting. I think it is doable.


Bad Icons

<Icon name="logo-ionic" /> is bad, here the icon CC will be shown. Latest NPM Release!

<Icon name="ios-list-box" /> is also bad, shows the cash icon instead

is also wrong

Okey so I found out the issue here. Looks like somehow the latest version of vector icons was installed for me (6.5.0). Using 6.1.0 like the one included in the latest native base works.
@Bizarrus
I tried logo-ionic too. The correct icon is shown. Maybe you have the same issue as me. If so this issue should be closed.

Hi @andidev,
Did you install the react-native-vector-icons v6.1.0 in your package.json or did you do other steps?

For me, i had installed the latest version from NPM.

Hi @Bizarrus, you must install latest version of react-native-vector-icons.
Hi @andidev, please use <Icon name="ios-notifications-outline" /> instead of <Icon name="ios-notification-outline" />. Other than these thing, all <Icon {...props} /> works fine.

Hi @Bizarrus ,You must import Icon from 'native-base'.
latest version of Native base has been released.
Native Base 2.13.12


Import broccoli-asset-rev defaults

Instead of hardcoding the defaults we can get them from
broccoli-asset-rev so they are updated in case they ever change.

👏 👏 👏
Thanks for contributing!

Happy to help. Thanks for the great addon.


Force HTTPS on the site

https://blog.github.com/2018-05-01-github-pages-custom-domains-https/

Done :)


⚠ Carbubu has degraded performance

In 537b875, Carbubu (https://carbubu.fr) experienced degraded performance:

HTTP code: 200
Response time: 6256 ms

Resolved: Carbubu performance has improved in 4562606.


#14 Remove check for $refs

Instead of $refs a check is made for actions.length. Because $refs is initialised only after the function.

Hi @BoyWithSilverWings ,
Thanks for this PR. I'll test it out as soon as I get some free time and merge it if everything works fine.

Thanks for you contribution :)


Update images for cert-management to golang 1.23

What this PR does / why we need it:
Update images for cert-management to golang 1.23
/kind enhancement
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

/lgtm
/approve


[Dispatcher] When query parameter is used with commas the relevant parameter is taken as null

Sample code
   @http:GET {}
    @http:POST {}
    @http:Path {value:"/api/v1/magazines.json"}
    resource echoTwoResource (message m, @http:QueryParam {value:"name"} string name, @http:QueryParam {value:"age"} string age) {
        message response = {};
        system:println("Printing age:" + age);
        string payload = "This is a test 4 ..............." + name + ":" + age;
        messages:setStringPayload(response, payload);
        reply response;
    }

Sample URI: http://localhost:9090/test//api/v1/magazines.json?name=jane,age=25,30
Response: This is a test 4 ...............erandi,age=25,30:null
The value of age when printed shows as null.

It looks like this is not in the URI spec and hence we should not support it.
If a person wants to read a string and split it at "," our regex functions should certainly support that.

Not standard; not implementing.


Add navigation link to Enterprise Gateway

Add navigation link to Jupyter Enterprise Gateway project, see sample generated html view below

Hello all, I've been following this thread and I wanted to chime in, sorry for lurking so long, I wanted to gather my thoughts before I ring in directly.
From a design point of view even the existing website has a very serious top-nav issue. The rule of thumb for top nav is it should have ideally 4 and no more than 6 primary links, with drop-downs if necessary. We currently have 8 links up top, and this would make it 9. I know this doesn't seem like  very serious issue, but it really is, we need to re-evaluate the top-nav in a meaningful way. I don't have time to do all that re-design work right now myself, but the work does need to be done. I also want to acknowledge how important including the enterprise gateway is for a host of reasons, including those @willingc mentioned above.

I like the idea of the navbar links being more "meta" pages that point users in the right direction to multiple projects. E.g., we could replace the notebook link with user interfaces and then it could also include links to projects like Jupyter Lab, nteract, RISE, etc.

I think this suggestion is spot on. I don't want to see the nav bar scale up indefinitely, and I think there's a lot of room for Jupyter.org to funnel outwards to the vibrate group of projects that are both core and in it's orbit.
I have many more thoughts on this to continue, I'm still on the fence about whether it's a good idea to increase the size of the top nav at this point, even as a temporary fix. But I do think this draws on an issue that ought to be discussed more thoroughly.
What is the consensus on having that conversation here versus in a separate issue?

I don't see anybody else ringing in here. @lresende @choldgraf is it possible to update this PR to include a 'projects' drop down in the main nav that contains JupyerHub, NBViewer, Widgets, and Enterprise Gateway? That would help pair down the main nav to a reasonable level while also including the Enterprise Gateway.

is it possible to update this PR to include a 'projects' drop down in the main nav that contains JupyerHub, NBViewer, Widgets, and Enterprise Gateway?

I think that folks like Widgets (@SylvainCorlay @jasongrout) may wish to keep their top level nav. I'm not sure that how I feel with JupyterHub moving out of the top level (@choldgraf thoughts?) Do we have any analytics on the popularity of these nav items?

My 2 cents is that I think that:
We should have a strategic conversation about the website structure, which projects get "special highlighting treatment", etc. However I think this will (and should) take some time to get right. In the meantime, I don't think that we should block any additions to the website until that gets resolved. And since we don't have a policy for "what goes on the website, and where", we should default to being open and inclusive of the various major projects in the Jupyter ecosystem (not to say that we shouldn't have such a system, we just don't have one now).
In my opinion, "should the projects go in a drop-down menu or in the navbar" and "should the enterprise gateway be added to the list of projects" are two separable issues. Since this PR tackles the latter, I'm (still) +1 on merging it in, and then opening up a conversation about restructuring the navbar. IMO the structure and style of the website is important, but not as important as the content. The enterprise gateway link could be valuable to the community, and we don't want to prevent the community from discovering this potential resource because we're worried that the website won't look good with too many buttons.
Just to make it clear what we're deciding between, this is the website now (on my 13" laptop screen)

and this is the version in this PR

I don't think that the addition of the extra button is problematic enough that it should prevent the addition of new content.
(again, just to be clear, I don't think this is a good status quo for process around the website, but until we have a better official process, our default should be to accept contributions if they are for Jupyter sub-projects)

@choldgraf I agree. At this point, I think it's less disruptive to just add the enterprise gateway to the navbar. Leaving a larger refactor for later.

Bumping this up in case there are any other requests. Otherwise, my understanding is that there is a consensus in merging this PR and take the website redesign to another thread/pr.

@lresende - I am open to working with you on how we might support your effort to get more visibility for Enterprise Gateway, however, the messaging and the ui/ux design issues that your proposal brings up are significant enough that I'm not in support of it. I don't agree there is consensus in merging this in its current state. If you want to discuss this more or want to share ideas please comment further here or reach out to schedule a quick chat.

@Ruv7 Thanks for your feedback.
The only direct request for change on this PR was related to adding a Projects folder on the website navigation which is really more aligned with the overall website navigation redesign and based on the feedback from @willingc and @choldgraf I thought that we were more towards consensus on adding the Enterprise Gateway link as is, as it is currently not breaking existing website functionality.
IMHO, I agree that there is a greater problem that needs to be solved around website navigation, particularly one that can accommodate the addition of new Jupyter subprojects, but this should be an independent discussion and should include representants from other Jupyter projects and to me, this is better handled on a different PR.
Anyway, I will try to come up with a website design proposal for the overall navigation in a different PR and I guess we can revisit this once that gets consensus.

@lresende in hindsight, I should further explain my comment about how I see a messaging and information architecture problem. The top level navigation bar is a way to visually communicate the most important areas of focus for an organization. To communicate that Enterprise Gateway is one of 4 key initiatives / subprojects for Project Jupyter would not be not accurate. This in no way implies that it is not important or something we do not want to support. The areas of the project that should be given this sort of high level visibility within our messaging have not been defined in the past - this is a broken area of the site and there is no clear and easy solution to moving forward.
At the end of the day, I do think that it's important we move toward fixing this so thank you for bumping this issue.  Since we've talked it at length, I know Tim @tgeorgeux has thought extensively about how we might plan and execute a visual and content redesign of the entire jupyter.org site. I hope this can at least be outlined and shared with the community in a separate issue in the next couple of weeks. Tim - do you have an idea of when you'll be ready to share your proposal?

I would encourage the interested parties to hop on a call and begin to work through a resolution on this. I don't see a fundamental barrier to designing and implementing something that would delight everyone.

I will just remind people that at some point there was some work on a "Ecosystem" page:
https://github.com/jupyter/jupyter.github.io/pull/246
We obviously can't have everything on the top menu bar, and I'm more incline to treat everybody equally and consider Hub/Lab/ipywidgets just another community project.
Regardless of wether I believe this could be merged or not based only on content; it is technically broken on narrow screen:

Instead of having the projects listed in the tab bar, we could have sections in the front-page with minimal information of "top-level" projects, meaning JupyterHub, Notebook, Widgets, etc (not each repository)...
Currently the front page includes a few of these. We could keep these sections very short and provide a link in each to a more detailed section.

Hi @lresende. I'm going to close this PR.


Install extra Vagrant plugins

vagrant-hostsupdater and vagrant-triggers seem to be getting used a lot, might as well have them pre-installed:
vagrant plugin install vagrant-hostsupdater
vagrant plugin install vagrant-triggers

definitely hostsupdater, haven't seen triggers actually in use. This command will update already installed plugins


Shadows not Appearing during Export as PDF

Exactly what the title states. I am using this on google chrome and other colleagues of mine also have the same issue.
The shadows appear in the diagram, but the moment I export as a PDF, they disappear. They do not disappear when exporting as other file types.

This is expected. We cannot convert the shadow to vector so exclude it.

This is expected. We cannot convert the shadow to vector so exclude it.

But, this exact function used to work about a month ago?

Yes. we switched it off for performance problems.

Are there plans to be able to export shadows to vector for a future release?

Thank you for your answer. Could it maybe be included in the desktop version?

it can't because that's chrome.

Clear. Thank you!

I've contacted the Chrome development team through their issue tracker. They would need more information from someone from the draw.io development team to understand what they would need to change to support this. The issue that I reported can be found here (https://issues.chromium.org/issues/365033303) and it would be super nice if someone from the draw.io team could maybe comment there or make a new issue so the Chrome team can work to resolve this. Thanks!

It's this CSS:
filter: drop-shadow(rgb(77, 77, 77) 2px 3px 2px);
HTH


[explorer] IPFS deploy

Following on from #126, which configured the how, this ticket involves getting explorer hosted on IPFS.
Tasks

[ ] Create site on ⚡fleek
[ ] add .fleek.json to token app
[ ] Repoint hostname to ⚡fleek
[ ] Test a deploy, ensure CSS/etc loads properly

@edd @dexturr: Is this still blocked or can we move it to the backlog to be prioritised and refined?
Cc: @pennyandrews


add WPML compatibility for frontend

Hi,
There a few update of the plugin to add the WPML compatibility.
A boolean selector is added in the appereance setting. If true th language is override by the language given by WPML.
Best regards

Everything is done ?

@bjoly-nexurium  - Our conversation is not in the Files Changed tab, looks like it's just on your first commit, but I'm still not clear the language codes that WPML is providing and what happens if that code is not allowed by Lock.

I'm going to close this one for now. I have a backlog task to better integrate the plugin with language settings and would rather align to the core WP language setting (or a custom one that defaults to that) than rely on another plugin's functionality.
I appreciate the contribution here and getting us started down this road @bjoly-nexurium!


Is name unique within a biological_context for an evidence?

When working on OpenBEL/openbel-server#43 (mapping annotations to name/value) there is a real potential for name collisions.
For example if I have three free annotations P-value, P value, and PValue then the names will all normalize to PValue.
Another example that maps to the same name (`Cell Line Ontology) would be:
{
    "uri": "http://next.belframework.org/api/annotations/cell-line-ontology/values/0001045"
},
{
    "name": "Cell Line Ontology",
    "value": "11-<IP_ADDRESS> cell"
}

@nbargnesi @wshayes Should we enforce uniqueness of names or rather collapse common names to an array of values?

It seems like a no-brainer to collapse values by name since we cannot easily enforce this at the schema level.

Not sure I get what you're asking.
I would expect this evidence context:
{
  "evidence": {
    ...
    "biological_context": [
      {
        "name": "foo",
        "value": "bar"
      },
      {
        "name": "foo",
        "value": "baz"
      }
    ],
    ...
}

To be equivalent to:
{
  "evidence": {
    ...
    "biological_context": [
      {
        "name": "foo",
        "value": ["bar", "baz"]
      }
    ]
    ...
}

So unique in terms of the same names being eligible for collapsing? If that's the case, I think collapsing makes sense.

Yes. That is exactly what I meant and your example captures it nicely.
It is also possible for
{
  "uri": "http://..."
}

to map to the foo annotation as well.
Thanks. I will collapse biological context names when processing evidence data.


Fix and actually test test_data/native_dynamic_linking

Fixes https://github.com/dart-lang/native/issues/1521

Thanks for your contribution! Please replace this text with a description of what this PR is changing or adding and why, list any relevant issues, and review the contribution guidelines below.

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.
Most changes should add an entry to the changelog and may need to rev the pubspec package version.
Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

Still red @blaugold, are things being printed out of order?

Still red @blaugold, are things being printed out of order?

Yes, I think that's it.

coverage: 91.034% (+0.02%) from 91.016%
when pulling c0d7ca36e27548ff8b0a7c6822c2e68d9a7ab61a on blaugold:fix-native_dynamic_linking-test_data
into 690ddec3618163ea02b0adb6d1fed59c51622c17 on dart-lang:main.


Add private tangle documentation for IOTA 1.5 Chrysalis

Description
I noticed documentation of how to run a private tangle, using HORNET, was missing for IOTA 1.5. So I took a shot at it.
Type of change

[x] Documentation Fix

How Has This Been Tested?
Thoralf provided a mnemonic to use and update the preconfigured snapshot address. The steps in the tutorial allowed me to run a private tangle and connect cli-wallet successfully.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have made corresponding changes to the documentation
[x] I have tested my code extensively
[x] I have selected the develop branch as the target branch

Thank you very much for this nice tutorial! Really appreciate the work!


ENH: add dot_size arg to beeswarm

Overview
Add argument for dot_size in beeswarm plot
Checklist

[x] All pre-commit checks pass.
[ ] Unit tests added (if fixing a bug or adding a new feature)

Hi @noah-asing , thanks for the interest in contributing to shap! Can you elaborate a little more about your use case (e.g. why is a fixed dot size of 16 not sufficient for you)? If possible, please also provide images of the current beeswarm that you are getting so we can also understand the issue at hand.
With plotting wrappers (like our shap.plots.xxx functions), I understand that there will always be customizations that users will require, but on our end I also wish to control the number of arguments that we expose. Or at least ensure that each new one we add in has a use-case that is well-documented (e.g. as an issue or in PRs like these).

Hi @thatlittleboy, there isn't a specific "need" per se, more of a "nice to have".
I thought it might be nice to have more definition in the beeswarm to try to visually separate NaN clusters, high-feature-value clusters and low-feature-value clusters. Reducing the alpha value resulted in the NaN clusters essentially disappearing completely underneath purple blobs, and I was hoping reducing the dot size might do the trick.
I saw that the scatter plots had a dot_size arg, so I didn't think there'd be a reason not to add dot_size to the beeswarm.
I didn't really think about controlling exposed arguments, so as of now this PR isn't really necessary (feel free to close).

@noah-asing

I thought it might be nice to have more definition in the beeswarm to try to visually separate NaN clusters, high-feature-value clusters and low-feature-value clusters. Reducing the alpha value resulted in the NaN clusters essentially disappearing completely underneath purple blobs and I was hoping reducing the dot size might do the trick.

Did it make it better?

I'm definitely open to adding the customization option, I'll leave this up for a while longer, if anyone else is interested in this functionality feel free to state your use case!
Thanks for the contribution in any case! :)

I shall close this for now as we are thinking of implementing style customisation in a different manner: https://github.com/shap/shap/pull/3377
However, thank you for the PR in any case, as it's helpful to understand what features you need! We'll aim to get a proper customisation API implemented, and any and all contributions are highly appreciated.


Clearing state between request-logger requests

Firstly, let me say thank you for the fantastic work you've done with this project and open sourcing everything, you've done a great job.
I've been running into an issue whereby I have Chrome retaining state between lambda requests. If I run the request-logger endpoint, the same Lambda instance stays warm for ~15min until there is no activity, and therefore the same Chrome instance seems to be retained during this warm period. Therefore, I get an issue with sessions not clearing and cookies being retained between different lambda requests.
I've tried a bunch of different things. Firstly, Network.clearBrowserCache and Network. clearBrowserCookies doesn't seem to do anything, even when Network.canClearBrowserCache and Network.canClearBrowserCookies both return true. I've tried calling these functions before and after the the load event, and neither clear the cookies or cache.
I've also tried to build against the automated releases. However, I find that anything above v1.0.0-33 doesn't work correctly in the new versions of Chrome. For example, v1.0.0-41 built against Chromium 65 only pushes the first request into requestsMade. So where I'd expect several items in the array, there is only ever the request for the base HTML page, and none of the assets. I'm not sure if this is a Chromium bug, but I suspect though.
Next I tried, several examples from @cyrus-and including snippets from issue 92 and 118 and his example on the use of contexts. However, the lambda function exits without notice when I call Target.createTarget, which I can only attribute to the version of Chromium, as Target is only available in the tip-of-tree (albeit,  Target.createBrowserContext() seems to return an ID correctly - so I may be wrong here).
My end goal here is to destroy cookies, or use the Incognito like feature between requests such that session IDs and cookies are not retained for discrete lambda calls from the front end.
I have a feeling that the issues with Target.createTarget may be resolved in later versions of Chromium, but because the requestsMade array only has the one entry and the Network.requestWillBeSent callback seems to be buggy, I've had to fallback to earlier versions.
Have you encountered any of these issues or know what I'm possibly doing wrong here?

I was going over the code and it seems that it intentionally preserves the chrome instance.
means it will also preserve the cookies and such
https://github.com/adieuadieu/serverless-chrome/blob/master/packages/lambda/src/index.js#L19-L23
But also saves startup times when the lambda is hot.
chrome on lambda is running with single process, that's probably breaks stuff like Target.createTarget
How you can solve it:
What i do, i launch chrome myself using the binaries from this package, and killing it before i'm done.
see example here:
https://github.com/adieuadieu/serverless-chrome/issues/129
One more thing you can try (and let me know if you found a way to do it plz :)) find a way to fully clear all the user data of the browser. i couldn't find the relevant debugger protocol command


Update Mac OSX dependencies installation instruction

Thanks for providing great tools!  homebrew/science/ceres-solver is deprecated.

8a4c4e7 should be only in #210, not here too

Thanks for pointing that out. Will fix it.


FIPS Compliance

Description of changes
Close #1672
Test plan
How are these changes tested?

[x] Tests pass locally with pytest for python, yarn test for js

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

Thanks @DueViktor!


WIP Add a test leaking a native peer [ECR-892]:

Overview
The problem with most index constructors is that they first
create a native peer, and then perform some checks, e.g., in
ProofListIndex constructor:
super(nativeCreate(checkIndexName(name),
  view.getViewNativeHandle()), name, view, serializer);

Therefore, the parent receives a native handle, and then checks
some of the other arguments (serializer, in this case). If these checks
fail, we get a leak of a native peer.
A possible solution is to simplify error checking with static factory
methods, that do not have such a restriction as constructors that the first call
in the method must be a call to super. To make it even more reliable, we may
also wrap the code in try/finally, destroying the native peer.

Closing as #244 made this test obsolete.


Zona update

Proposed changes
Refactors the zona_bb_subcortex.smk file. Includes the following:

Defines the zona output directory
Changes for snakefmt
Fix name of files in resources for zona
Added anticipated path for anat segmentation for transformation purposes between different MNI spaces and subject native space

These files are available locally at the moment, but are too big to be added to the git repo (any ideas here @tkkuehn? I think hippunfold and maybe another workflow downloads any large files separately).

Add transformation to rule to define an transform matrix

Types of changes
What types of changes does your code introduce? Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionalitiy)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Other (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you are unsure about any of the choices, don't hesitate to ask!

[ ] Changes have been tested to ensure that fix is effective or that a feature works.
[ ] Changes pass the unit tests
[x] Code has been run through the poe quality task
[x] I have included necessary documentation or comments (as necessary)
[ ] Any dependent changes have been merged and published

Notes
All PRs will undergo the unit testing before being reviewed. You may be requested to explain or make additional changes before the PR is accepted.

Okay, hopefully caught most things here. Should be ready for a review now.

Also have to deal with this too:
* Added anticipated path for anat segmentation for transformation purposes between different MNI spaces and subject native space
  * These files are available locally at the moment, but are too big to be added to the git repo (any ideas here @tkkuehn? I think hippunfold and maybe another workflow downloads any large files separately).

Updated to make use of functools.partial
Also removed the expand in the xfm_zona_rois rule, but need to double check to see if:

it grabs the correct inputs
it runs without error


java.lang.RuntimeException: setParameters failed

Using API 28
android.hardware.Camera.native_setParameters (Camera.java)
android.hardware.Camera.setParameters (Camera.java:2102)
de.charite.balsam.utils.camera.CameraPreLolipop.getParameters (Unknown Source:4)
net.kibotu.heartrateometer.HeartRateOmeter.getPublishSubject (Unknown Source:107)
net.kibotu.heartrateometer.HeartRateOmeter.startPreview (Unknown Source:12)
net.kibotu.heartrateometer.HeartRateOmeter.start (Unknown Source:139)
net.kibotu.heartrateometer.HeartRateOmeter$bpmUpdates$1.accept (Unknown Source:19)
net.kibotu.heartrateometer.HeartRateOmeter$bpmUpdates$1.accept (Unknown Source:2)
io.reactivex.internal.observers.DisposableLambdaObserver.onSubscribe (Unknown Source:2)
io.reactivex.subjects.PublishSubject.create (Unknown Source:5)
io.reactivex.Observable.doOnDispose (Unknown Source:14)
io.reactivex.internal.operators.observable.ObservableDoOnLifecycle.subscribeActual (Unknown Source:11)
io.reactivex.Observable.doOnDispose (Unknown Source:14)
io.reactivex.internal.operators.observable.ObservableDoOnLifecycle.subscribeActual (Unknown Source:11)
io.reactivex.Observable.doOnDispose (Unknown Source:14)
io.reactivex.Observable.doOnDispose (Unknown Source:25)
io.reactivex.Observable.subscribe (Unknown Source:8)

on deviced with no torch this exception happens

I'm not actively maintaining this project, however i'll merge PRs if there are any


dependencies warning control, overriding path heuristic

Describe the problem you are trying to solve
I am working on a project with upstream dependencies, some of which I have had to edit locally.  So (pending an upstream release, and sometimes even pending locally committing the upstream code) I have edited my Cargo.toml to have a path dependency on the upstream.
However, the upstream has a number of warnings from rustc.
When I compile the same crate as a non-path dependency, cargo gets the version from crates.io - which has the same warnings - but the warnings are suppressed.  Evidently cargo treats the use of a path dependency as an indication that I am a developer of the dependency and therefore want to see the warnings.  (I failed to find a discussion of this in the cargo documentation.)
Describe the solution you'd like
This path dependency heuristic is a good rule of thumb.  Usually it will be right.  But it would be good if there were a way to override it.
I suggest an additional entry in the dependency, alongside the path key.  propagate_warnings maybe.  The default would be false for non-path dependencies, and true for path dependencies, but it could be overridden by the depending crate.
Warnings would be shown to the user if all of the dependency links from the toplevel to the relevant place had propagate_warnings.  (I haven't checked but presumably this is what cargo does already, only just checking for path dependencies.)
In my scenario this would mean that I would see the warnings if I ran cargo build in the directory of my dependency, but not in the directory of my own project.  That seems right to me.
Notes
It seems that a git dependency suppresses the warnings.  So I could use a git dependency instead, as a workaround.  In my situation this is less than ideal, because it means I must always be sure to commit all my edits to the dependency.  For another user it might well be useful to enable the warnings.
Another possibility would be some kind of global configuration to specify which crates to print warnings for.  That would be independently useful but it would be less helpful in my specific situation.

Have you tried using the [replace] or [patch] sections instead of a path dep? They may work better for the use case of fixing an upstream bug.

@Eh2406 [patch] with a path dependency will also issue warnings.

How many things can I get wrong in one day? :-P
Just ignore me. Sorry for the noise.

It might be reasonable to simply not warn for [patch] dependencies (or [replace]). Whenever I've used that I've never really wanted warnings and almost always get a lot to deal with anyway.

I'd like to take this on. Any pointers to  how and where cargo decides to suppress warnings when building dependencies?

Yay, thanks for looking at this.  I'm afraid I don't have any tips for navigating the inside of cargo.  But I can say what the behaviour appears to be:
Basically, path dependencies are treated like the toplevel crate and have warnings enabled.  Warnings are suppressed for dependencies specified as git= and for crates.io.  I assume that this is done transitively, so that in principle if there's a git dependency which has path dependencies within the git tree, the warnings are suppressed for those too.  crates.io doesn't allow path dependencies; IDK what happens if you specify a registry that contains things that look like path dependencies.  (I assume cargo must do some laundering here or there might be a security risk.)
IDK what [patch] and [replace] do.
Overall it appears that this "you see warnings" thing is a property of a dependency edge.  Currently, just from the type of the edge.  @alexchriton is suggesting that [patch] and [replace] should be treated differently.  I am suggesting an ability to explicitly control the warnings-propagation-ness of a dependency edge (in the depending package, where the dependency is specified).
I hope this is of some use...

The decision to show warnings is controlled by show_warnings.  However, whether or not something comes from [patch] is lost by the time it is needed, so I think adding that support will be hard.  Unfortunately I don't have the time to look into it in more detail.

I just encountered this and found this behavior surprising. Since I was doing no local patching of the dependency, the suggestions regarding [patch]/[replace] aren't helpful to me.
My naive expectation is that the transition from crates.io dependency -> remote git dependency -> local path dependency should be doable without any change to the warnings that are printed.


misleading documentation surrounding IDE support

The documentation claims IDE support, but there is no information on how this actually work, that I could find. I did however find discussions that editor integrations are still closed-source:
https://github.com/sorbet/sorbet/issues/1013
https://github.com/sorbet/sorbet/pull/4915
Could the sorbet project be more transparent about what it means by "IDE ready" and what the expectations are surrounding that? Does Stripe have an internal vs code extension that is closed-source? is the Sorbet project looking for contributors to create a VS Code extension? As it stands, the documentation is misleading, especially considering this gif on the homepage:

It's somewhat of a tease to show something that doesn't actually exist or is actually closed-source on the project homepage.

While I've read several times that Stripe has their own proprietary VSCode integration and I'll assume that's likely true, the LSP support in Sorbet works relatively well for me in Neovim. Not a byte of proprietary code needed to make it happen.

langserver.org is a good resource for sorting out the language <-> editor matrix for LSP-driven "IDE-like" features. Speaking to VSCode specifically, there appears to be at least one community project to that end at https://github.com/danhuynhdev/sorbet-lsp, though I haven't personally used it (since I don't use VSCode to begin with).

It's available now :) https://sorbet.org/blog/2022/01/06/open-sourcing-sorbet-vscode


Fix release notes item for SEI

Harness Developer Pull Request
Fix release notes item for SEI
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[x] Optional Screenshot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65f1d1f768d5a73e8cf79bf1--harness-developer.netlify.app


how to adjust the size of avatar

It is a little small and want to make it bigger. Could you please help?

Hi,
You may adjust the CSS file to change the layout of this page. For the avatar, you can adjust the parameters in this line:
https://github.com/yaoyao-liu/minimal-light/blob/4883931596f3bb5aa4061bc9b64a318b83be9f16/_sass/minimal-light.scss#L92

Thanks for your reply!
But it doesn't work. I changed the width to 100% and no difference.

thanks! everything looks fine!