flutter update-packages   stuck

I try more than once, no benefit
I waited more than twenty minutes
flutter update-packages
Waiting for another flutter command to release the startup lock...Running "flutter pub get" in tracing_tests...                       0.6s
Running "flutter pub get" in bots...                                1.3s
Running "flutter pub get" in customer_testing...                    0.5s
Running "flutter pub get" in snippets...                            0.9s
Running "flutter pub get" in platform_interaction...                1.1s
Running "flutter pub get" in flutter_gallery...                     1.5s
Running "flutter pub get" in non_nullable...                        0.6s
Running "flutter pub get" in gradle_deprecated_settings...          0.5s
Running "flutter pub get" in release_smoke_test...                  0.9s
Running "flutter pub get" in channels...                            1.0s
Running "flutter pub get" in android_semantics_testing...           1.0s
Running "flutter pub get" in ios_platform_view_tests...             1.1s
Running "flutter pub get" in flutterapp...                          0.6s
Running "flutter pub get" in flavors...                             1.1s
Running "flutter pub get" in flutter_driver_screenshot_test...         1.0s
Running "flutter pub get" in flutterapp...                          0.6s
Running "flutter pub get" in ui...                                  1.1s
Running "flutter pub get" in external_ui...                         1.1s
Running "flutter pub get" in web_compile_tests...                   0.5s
Running "flutter pub get" in ios_app_with_extensions...             0.6s
Running "flutter pub get" in hybrid_android_views...               88.3s
Running "flutter pub get" in android_views...                       0.9s
Running "flutter pub get" in web...                                 0.4s
Running "flutter pub get" in android_embedding_v2_smoke_test...         0.5s
Running "flutter pub get" in abstract_method_smoke_test...          0.5s
Running "flutter pub get" in splash_screen_kitchen_sink...          1.1s
Running "flutter pub get" in splash_screen_trans_rotate...          1.1s
Running "flutter pub get" in splash_screen_load_rotate...           0.6s
Running "flutter pub get" in image_loading...                       0.9s
Running "flutter pub get" in named_isolates...                      0.5s
Running "flutter pub get" in devicelab...                           1.1s
Running "flutter pub get" in manual_tests...                        0.7s
Running "flutter pub get" in platform_views_layout...               1.0s
Running "flutter pub get" in platform_views_layout_hybrid_composition...        1.1s
Running "flutter pub get" in macrobenchmarks...                   (     It got stuck here    )
(This is taking an unexpectedly long time.)       ⣟

attia@HP-Pavilion:~$ flutter doctor -v
[✓] Flutter (Channel beta, 1.21.0-9.1.pre, on Linux, locale en_US.UTF-8)
• Flutter version 1.21.0-9.1.pre at /home/attia/Porgram/flutter
• Framework revision be9bc8cb39 (3 days ago), 2020-08-18 09:46:08 -0700
• Engine revision 267070c17a
• Dart version 2.10.0 (build 2.10.0-7.2.beta)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at /home/attia/Android/Sdk
• Platform android-29, build-tools 29.0.3
• Java binary at: /home/attia/Porgram/android-studio/jre/bin/java
• Java version OpenJDK Runtime Environment (build
1.8.0_242-release-1644-b3-6222593)
• All Android licenses accepted.
[✓] Chrome - develop for the web
• Chrome at google-chrome
[✓] Android Studio (version 4.0)
• Android Studio at /home/attia/Porgram/android-studio
• Flutter plugin version 48.0.2
• Dart plugin version 193.7361
• Java version OpenJDK Runtime Environment (build
1.8.0_242-release-1644-b3-6222593)
[✓] VS Code (version 1.48.0)
• VS Code at /usr/share/code
• Flutter extension version 3.13.2
[✓] Connected device (2 available)
• Web Server (web) • web-server • web-javascript • Flutter Tools
• Chrome (web)     • chrome     • web-javascript • Google Chrome
84.0.4147.135
• No issues found!

@AttSee why you closed this issue?
I also facing same problem.
are you get any solution?

@Basher7 In case you deleted the flutter files, you need more time
Wait a little longer and the download will finish

one hour later ...
I also facing saave problem

$ flutter update-packages
Running "flutter pub get" in automated_tests...                     4.7s
Running "flutter pub get" in complex_layout...                      6.5s
Running "flutter pub get" in macrobenchmarks...
Git error. Command: git clone --mirror https://github.com/flutter/gallery.git C:\src\flutter\.pub-cache\git\cache\gallery-e81411447eb674bf0aa7b6d3b66e18a667cfbf46
stdout:
stderr: Cloning into bare repository 'C:\src\flutter.pub-cache\git\cache\gallery-e81411447eb674bf0aa7b6d3b66e18a667cfbf46'...
fatal: early EOF
fatal: the remote end hung up unexpectedly
fatal: index-pack failed
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
exit code: 128
pub get failed (server unavailable) -- attempting retry 1 in 1 second...
Running "flutter pub get" in macrobenchmarks...                 (This is taking an unexpectedly long time.)       \


Update customerio-cohort.md

UPdating the doc to let customers know that this integration is available in EU DC.
Amplitude Developer Docs PR
Description
Describe your changes.
Deadline
When do these changes need to be live on the site?
Change type

[ ] Doc bug fix. Fixes #[insert issue number]. Amplitude contributors include Jira issue number.
[ ] Doc update.
[ ] New documentation.
[ ] Non-documentation related fix or update.

PR checklist:

[ ] My documentation follows the style guidelines of this project.
[ ] I previewed my documentation on a local server using mkdocs serve.
[ ] Running mkdocs serve didn't generate any failures.
[ ] I have performed a self-review of my own documentation.

@amplitude-dev-docs
@caseyamp

@Brandoncharleskhoo1 what is "DC" referring to?

@Brandoncharleskhoo1 what is "DC" referring to?

Hi Casey, the "DC" refers to Data Center.
"This integration is available in the EU Data Center region. You will need to specify the EU region during the setup stage in Amplitude."


[Dev support]: Chef Bot

Hi - I have managed to get Chef Bot up and running however I'm encountering issues customising the index. I've used Vectra and created a custom script to create the embeddings and index however Teams-AI is not accepting this when I upload it and send a message. Is there a script that I can use to create an index based on my TXT files?

Hi @PatelN123, have you already followed the Vectra instructions for creating your index? https://github.com/Stevenic/vectra/blob/main/samples/wikipedia/README.md#create-an-empty-index
Is it after this that you are still running into trouble?

Ah yes that's worked, thanks. I did not see the samples folder!


Propose adding another Example

https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/3259

Docs Build status updates of commit bd43c2c:
:clock10: Full build: the average full build time is 11 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit bd43c2c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Grant-CsTeamsMessagingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

I know we were trying to be consistent on whether the "PS C:>"  should be at the front of the command. My preference would be not to have it because if someone does a "Copy Code" from the web rendering then they have to backspace that out in order to run the command. However, I looked and the other examples have that so we should be consistent like you did.
Let's merge it and then circle back with the rest of the PowerShell team so we can get consistency regarding the "PS C:>" prepended to beginning of examples across all PowerShell.


Provide an initializer at the requested access level or fail

Continuing the theme of #7:
@MemberwiseInit has traditionally mirrored Swift's memberwise initializer, adapting to the access levels of struct properties. This adapting behavior is necessary for Swift's initializer, which operates without explicit developer intent.
However, when a developer annotates a struct with @MemberwiseInit(.public), their intention is clear: they expect a public initializer. If the struct includes a private property, MemberwiseInit, as it stands, provides a non-public initializer. This outcome, often discovered later and indirectly, is surprising.
@MemberwiseInit should instead fail immediately in such cases, offering immediate, actionable diagnostics. For example, suggesting the annotation of properties with @Init(.public) or recommending access level adjustments.
With this change:

MemberwiseInit better aligns with the explicit and intentional practices preferred in Swift.
Unburdened from the nuance and complexity of Swift's memberwise initializer, README will become considerably shorter.
Usage will become more obvious and incrementally learnable through experience applying the macro and responding to diagnostics—"reading the manual" becomes much less necessary.
MemberwiseInit is still safe by default.

While residing in a somewhat grey area, I consider this a non-breaking change:

It aligns with the logical use of MemberwiseInit: using @MemberwiseInit(.public) while intending a non-public initializer is unlikely to begin with. Furthermore, were your intent to add an internal or private initializer, you wouldn't have much reason to reach for MemberwiseInit over Swift's memberwise initializer.
Existing code using @MemberwiseInit(.public) but not requiring a public initializer likely indicates a mistake, which this change proactively corrects.

Perfect! I think this is the right design philosophy to adopt 👌


Add JSDoc comments on PIXI.Transform

Description of change
This PR adds JSDoc comments on PIXI.Transform properties and improves the PixiJS type declaration file. I intentionally changed the visibilities of the methods onChange and updateSkew from @private to @protected. I thought it is a good thing to allow developers to override them when needed. But if it isn't, I will revert them.
Pre-Merge Checklist

[x] Documentation is changed or added
[x] Lint process passed (npm run lint)

Codecov Report

Merging #5843 into dev will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##              dev    #5843   +/-   ##
=======================================
  Coverage   70.54%   70.54%
=======================================
  Files         205      205
  Lines       10402    10402
=======================================
  Hits         7338     7338
  Misses       3064     3064

Impacted Files
Coverage Δ

packages/math/src/Transform.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Also I'd like to point out that (cx, sx) is normalized first column of matrix, coordinates of normalized local X axis in parent space. Same about (cy, sy)

Thank you for clarifying. I thought long about their good explanations / technical terms. "X-coordinate value of normalized local X axis" sounds good.

We can put the same desc in both _cx and _cy:

(_cx,_sx) is normalized local X axis, first column of local matrix without scale.

(_cy,_sy) is normalized local Y axis, second column of local matrix without scale.

I leave it to you.

@ivanpopelyshev, why should all the members be protected?

That way i can write functions like this: https://github.com/pixijs/pixi-projection/blob/master/src/base/LinearProjection.ts#L2

Also, those are not global unique ID's , they are  unique only inside the instance. We can say that they are incremented. and _worldID  is read by others , while _parentID points to _worldID of parent that we already used for calculation. I don't know how to spell that.

I revised descriptions as per review comments.


Code Improvements

This PR will:

Code cleanup.
Add helpers.php file:

git_version() function. (Avoid updating the application version)
mkdir_if_not_exist() function. (DRY concept)
windows_os() function. (DRY concept)

Done!
Much better now! That's why I love the code review :heart_eyes:...
With all these changes, do you consider launching a new release? maybe 2.5.


Recurring events

Is there a way to create recurring events in Google Calendar, or will there ever be one?

dup of #129 so closing


remove direct ref codes from overlaping section

Direct reference codes should not be added to the overlapping valueset section.
Pull requests into Bonnie require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[X] JIRA ticket for this PR: https://jira.mitre.org/browse/BONNIE-1183
[ ] JIRA ticket links to this PR
[x] Code diff has been done and been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)
[x] If UI changes have been made, google WAVE plug-in has been executed to ensure no 508 issues were introduced.
[x] Tests are included and test edge cases
[x] Tests have been run locally and pass (remember to update Gemfile when applicable)
[x] Code coverage has not gone down and all code touched or added is covered.

See front-end testing instructions for getting coverage for front-end tests
In rare situations, this may not be possible or applicable to a PR. In those situations:

Note why this could not be done or is not applicable here:
Add TODOs in the code noting that it requires a test
Add a JIRA task to add the test and link it here:

[ ] Automated regression test(s) pass

If JIRA tests were used to supplement or replace automated tests:

[x] JIRA test links:
[x] Justification for using JIRA tests:
[x] JIRA tests have been added to sprint

Reviewer 1: @mayerm94
Name:

[x] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[x] The tests appropriately test the new code, including edge cases
[x] You have tried to break the code

If JIRA tests were used to supplement or replace automated tests:

[x] JIRA tests have been run and pass
[x] You agree with the justification for use of JIRA tests or have provided input on why you disagree

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

If JIRA tests were used to supplement or replace automated tests:

[ ] JIRA tests have been run and pass
[ ] You agree with the justification for use of JIRA tests or have provided input on why you disagree

github not allowing edits to the description or checkbox checks... all reviewers say all checkboxes check and that regression tests pass.

github not allowing edits to the description or checkbox checks... all reviewers say all checkboxes check and that regression tests pass.

github not allowing edits to the description or checkbox checks... all reviewers say all checkboxes check and that regression tests pass.


Progression system

TODO LIST:

[X] Client side toggle for progression
[x] Loadout validation on progression toggled on
[X] Stat callbacks
[x] Kill stats
[x] Assist stats
[x] Map/mode stats
[x] Pilot weapon damage stats
[x] Pilot weapon kill stats
[X] Titan damage stats
[X] Titan weapon damage stats
[x] Titan weapon kill stats
[x] Distance stats
[x] Execution stats
[x] Misc stats

TODO:

weapon/titan challenges tracking (we dont do this in northstar at all)
localisation
drawing attention to the button for the first time (new icon or something?)

Ok so this is now ready for review, it changes:

xp gain being far too generous
stat tracking
toggleable progression for clients

Notes:

If a server has a mod that overrides a file and uses DevEverythingUnlocked then it will probably not respect the player's progression choice (this is bad)
The stat tracking I tried to make readable over efficient, it is a bit of a mess tbh (respawn's one isn't much better)
The loadout validation isn't particularly smart, its similar to how regenning resets things, but more forgiving. It doesn't reset the entire loadout, instead resetting individual parts.

Testing:

Toggle the progression from the lobby, make sure you don't have any items, banners, etc. equipped still that you shouldn't
Have multiple players join the same server (server must be on the PR) with different progression toggles, make sure that their preference is being respected by the server
Try completing various weapon/pilot/titan challenges, make sure the stat for each of them is being tracked as expected
Finish some matches, see if the KD stat makes sense in the stats menu

Playtest

[ ] if you enable progression and then dont have your persistence saved, you can bypass some restrictions (weapon mods?) on the loadouts

[ ] postgame report shows no matter what, even if the data from the match isnt populated, because that stuff is populated at match end

[ ] sometimes shows FD postgame (modded FD players)

[ ] gamemodes played stats tab doesnt work

[ ] doublexp is showing in EOG scoreboard

Just a note for anyone who wants to test this, the thing about doublexp showing is because respawn do the weirdest check ever for showing it. Basically they assume that any xp that was gained that didnt also give a merit was from doublexp, so when it shows incorrectly, that means we were giving out xp too generously. I think I have sorted that out now, but I haven't had the time to test it very thoroughly.

Another note: the "Evac attempts" not showing on the stats screen properly I'm not sure about, I moved the place where the stat is given to be a bit earlier, but tbh I'm rly not sure

I'm going to implement a notification thing to tell users that they can toggle it now, then I'm going to try to get a playtest going later today

This is what the announcement looks like, new announcements can be easily created using the convars in the cfg. Eventually I'd like to fetch this from Atlas, but that can wait.

I just found AddPlayerMovementEventCallback and stuff so I'm going to rework the time and distance tracking to be better.

Other than https://github.com/R2Northstar/NorthstarMods/pull/655/commits/caedf379999e95c79cf459931a396deeaf388a0d the playtest picked up no issues with the PR. With that being said I am going to remove the label and mark as ready to merge.


onDisconnected callback taking more than 10 seconds to identify on disconnect of device in android

onDisconnected callback is getting triggered after 10 seconds in android but works fine in ios which gets triggered as soon as the Bluetooth device gets turned off.
Here is how Im using this callback method
device
.connect()
.then((dev) => {
dev.onDisconnected((error,devs) => {
alert('device disconnected')
});
return dev.discoverAllServicesAndCharacteristics();
})

Same issue here (Android, version 2.0.2). And if the device is back online within 10 seconds, it will never send the onDisconnect, although the device is disconnected

Same issue here (Android, version 2.0.2). And if the device is back online within 10 seconds, it will never send the onDisconnect, although the device is disconnected

Another +1 from me. Because of this issue, we cannot correctly update our UI state on Android anymore on disconnect. Please fix this as soon as possible.

Another +1 from me. Because of this issue, we cannot correctly update our UI state on Android anymore on disconnect. Please fix this as soon as possible.

Same issue we have on Android, newest version of library.


Fixed flavor specs detection

All extra specs of flavor (except 'ram', 'disk' and 'vcpus')
are placed in 'extra_specs' dictionary.
Signed-off-by: Maciej Skrocki<EMAIL_ADDRESS>

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

taf/testlib/virtual_env.py, line 930 at r1 (raw file):

        name = None
        if 'name' in flavor_spec:
            name = flavor_spec.pop('name')

Can we not LBYL?
name = flavor_spec.pop('name', None)

and using the empty string instead of None would be advisable though adding a requirement to create_flavor that requires a non-empty string as the name would do well.

taf/testlib/virtual_env.py, line 935 at r1 (raw file):

        extra_flv_keys = set(flavor_spec.keys()) - standard_flv_keys

        def cmp_spec(f):

I'd like to see this done like:
_not_found = object()
all_flv_keys = set(flavor_spec)
standard_flv_keys = all_flv_keys.intersection({'ram', 'disk', 'vcpus'})
extra_flv_keys = all_flv_keys - standard_flv_keys

def make_iter(keys, data):
    return (value == comp_value for value, comp_value in (flavor_spec[k], data.get(k, _not_found) for k in keys))

def filter_test(comp):
    return all(chain(make_iter(standard_flv_keys, comp), make_iter(extra_flv_keys, comp.get('extra_specs', {}))))

taf/testlib/virtual_env.py, line 946 at r1 (raw file):

        matching_specs = list(filter(cmp_spec, flavors_map.values()))
        if matching_specs:

The rest of this function would better be:
if matching_specs:
    return next((f for f in matching_specs if f['name'] == name), matching_specs[0])
elif not name:
    name = 'generic-flavor'
elif all(f['name'] == name for f in flavors_map.values()):
        raise Exception(...)
return self.create_flavor(name=name, **flavor_spec)

Comments from Reviewable

Review status: all files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

taf/testlib/virtual_env.py, line 930 at r1 (raw file):
Previously, esmacgil (Edward MacGillivray) wrote…
Can we not LBYL?
name = flavor_spec.pop('name', None)

and using the empty string instead of None would be advisable though adding a requirement to create_flavor that requires a non-empty string as the name would do well.

Done.

taf/testlib/virtual_env.py, line 946 at r1 (raw file):
Previously, esmacgil (Edward MacGillivray) wrote…
The rest of this function would better be:
if matching_specs:
    return next((f for f in matching_specs if f['name'] == name), matching_specs[0])
elif not name:
    name = 'generic-flavor'
elif all(f['name'] == name for f in flavors_map.values()):
        raise Exception(...)
return self.create_flavor(name=name, **flavor_spec)

why 'all'? shouldnt that be 'any' or 'not all'?

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

taf/testlib/virtual_env.py, line 935 at r1 (raw file):
Previously, esmacgil (Edward MacGillivray) wrote…
I'd like to see this done like:
_not_found = object()
all_flv_keys = set(flavor_spec)
standard_flv_keys = all_flv_keys.intersection({'ram', 'disk', 'vcpus'})
extra_flv_keys = all_flv_keys - standard_flv_keys

def make_iter(keys, data):
    return (value == comp_value for value, comp_value in (flavor_spec[k], data.get(k, _not_found) for k in keys))

def filter_test(comp):
    return all(chain(make_iter(standard_flv_keys, comp), make_iter(extra_flv_keys, comp.get('extra_specs', {}))))

Done.

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

taf/testlib/virtual_env.py, line 946 at r1 (raw file):
Previously, mskrocki (Maciej Skrocki) wrote…
why 'all'? shouldnt that be 'any' or 'not all'?

Yes, I could be wrong about that.  any is probably what it should be.

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

taf/testlib/virtual_env.py, line 946 at r1 (raw file):
Previously, esmacgil (Edward MacGillivray) wrote…
Yes, I could be wrong about that.  any is probably what it should be.

Done.

Comments from Reviewable

Review scrub: needs review?

Reviewed 1 of 1 files at r4.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

TAF doctring style is changed.
Detailed information you can find by link
http://taf-docs.readthedocs.io/en/latest/development_guide.html#docstring


Domain expired

https://food.felf.io/ shows some placeholder page, not the app at all
The webpage states that the domain expired :(

Until fixed the only working alternative I know is a fork running on https://food.fabian-feichter.at/. 🙂


Add Python 3.10 support. Use quotes for version numbers in YAML.

lgtm

Just FYI, I removed Alex and added myself as reviewer under the assumption that was the intent.  Feel free to revert if it wasn't....didn't merge this one just in case Alex was really supposed to review.


Notify Delegate of value changes

Thanks for contributing!

My pleasure, thanks for making and sharing the view in the first place :)
On Mon, Jun 22, 2015 at 5:18 PM Dan Williams<EMAIL_ADDRESS>wrote:

Thanks for contributing!
—
Reply to this email directly or view it on GitHub
https://github.com/danwilliams64/DJWStarRatingView/pull/9#issuecomment-114264108
.


[T7][T16-B1]

User guide and Developer guide appendixes for V0.0

@bennettgo
Some comments added. Please ack & close the PR after reading comments.
From this PR, it is difficult to gauge who all contributed. I believe you guys worked on this together on some collaborative platform like google docs and ported it here.
Do convey the comments to your team. Please keep up the good job :-)

@okkhoy Thank you so much for taking the time to look through!! Quite a few mistakes so we will get working on it asap! Everyone contributed actively! :-)


[internazionale] Fix extraction of non-available-abroad videos

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections

[x] Searched the bugtracker for similar pull requests

[x] Checked the code with flake8

[x] I am the original author of this code and I am willing to release it under Unlicense

[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

[x] Bug fix

[ ] Improvement

[ ] New extractor

[ ] New feature

Some videos can have a data-video-available_abroad attribute that
can be "0" or "1" depending if the video is available abroad (if
not present it is available abroad).
For not available abroad videos (all the ones with
data-video-available_abroad="1") video-ita.internazionale.it is
used instead of video.internazionale.it.
Adjust Internazionale extractor to reflect that and add a test for
a not available abroad video.

Hello Sergey,
first of all thank you very much for the quick review!
"Sergey M." writes:

dstftw requested changes on this pull request.

   video_base = 'https://video.internazionale.it/%s/%s.' % (video_path, video_id)

   if video_available_abroad:

       video_base = 'https://video.internazionale.it/'

   else:

       video_base = 'https://video-ita.internazionale.it/'

Code duplication.

OK, I have tried to adjusted that and at the same time hopefully it
should not be more confusing! (NFC)

@@ -40,8 +56,15 @@ def _real_extract(self, url):
DATA_RE % 'job-id', webpage, 'video id', group='value')
video_path = self._search_regex(
DATA_RE % 'video-path', webpage, 'video path', group='value')

   video_available_abroad = bool(int(self._search_regex(

Breaks on unexpected data.

Good catch! Now it should be less fragile.
Thanks again!


Conditionally rendered fields break onInput revalidation

Describe the bug and the expected behavior
Conditionally rendered Conform fields seem to lose their onInput revalidation once the condition changes. For example, for two (mutually exclusive) conditionally rendered inputs A and B:

Render InputA
Submit (firing the first validation)
Render InputB instead of InputA
Render InputA instead of InputB
InputA's onInput revalidation is now broken (you can submit again to fix it)

Conform version
v0.9.0
Steps to Reproduce the Bug or Issue
https://stackblitz.com/edit/remix-run-remix-dtzhfe?file=app%2Froutes%2F_index.tsx
Instructions are baked into the reproduction.
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
Screenshots or Videos
No response
Additional context
Note: our real schema is more complicated than this, with nested conditional fields, so things like discriminated unions didn't work as Zod doesn't support nested DUs, etc. so this superRefine approach was what worked best for us. But I doubt the schema format has anything to do with this anyway. To solve the revalidation problem, we had to hide/show fields via the hidden attribute rather than conditionally rendering them. It's a workaround, but probably not very idiomatic with regards to React, so we'd prefer to be able to conditionally render them instead if possible.

If I understand correctly, you are expecting input A to be revalidated when you switch the type back.
The behaviour here is indeed working as per the current design. As the input has been unmounted whenever the type is changed, it is considered a new input that are never validated and follows shouldValidate option (which defaults to onSubmit in your example). This design is mainly inspired by how field list is handled. (i.e. If an item is deleted and then re-inserted, it will be considered a new item so it won't be revalidated right away).
Does this design make sense to you? I find this question interesting as I am working on something that actually have the behaviour you want accidentally and I am now wondering what should be the correct behaviour, or at least the default behaviour here.

Thanks, your explanation makes sense. It sounds like we'll just have to choose between the available behaviors based on the combination of conditional rendering + shouldValidate + shouldRevalidate.
One confusing thing is that the validation error for InputA is still there, even though it's a "new" input after unrendering/rendering it. Is that intended behavior? If so, is there a way to clear the error when reintroducing InputA? If the worst case was the newly rerendered InputA started fresh (no errors, no validation until submit), we might be able to live with that (even though it's not quite the UX we were going for). But because the error is still there (in fields.inputA.errors from useForm), we can't really consider this as an option.
As for whatever you're working on and future behavior, it's hard to say what is more "correct". My colleague and I expected that because we had attempted to submit (thus triggering validation, due to the default value of shouldValidate: 'onSubmit'), all fields (currently shown or not) would start participating in onInput validation (due to our setting of shouldRevalidate: 'onInput'), but we also understand from a technical level, the dynamically shown inputs are "new". In the case of a list, we would have also expected a newly added item to the list would have onInput validation in our scenario, but it wouldn't be validated until input had changed, so it would appear valid until they typed in it or something, right? That seems fine. If it started out invalid, that would be bad, but that doesn't sound like that would be the case. I don't know, complex forms are annoying. :P

One confusing thing is that the validation error for InputA is still there, even though it's a "new" input after unrendering/rendering it.

That sounds like a bug which I believe is a limitation of the current implementation.
For now, I will suggest you to keep using the hidden attributes trick to keep them mounted or trigger a validation on the field manually. You can achieve it using the requestIntent helper with the validate intent.
There will be a new architecture  with the behaviour you wanted. It will probably be the default behaviour but I will need to figure out a way to override it as well. Hopefully you will find an alpha version out before November :)

You can now expect the exact behaviour with v1.0.0.

You can now expect the exact behaviour with v1.0.0.

 Thanks for all your hard work.

You can now expect the exact behaviour with v1.0.0.

So, this almost works in v1.0.1... conditionally rendering native inputs works great, but conditionally rendering a hidden input used for receiving events and forwarding to a custom non-native input (e.g., focus from Conform when it's the first invalid input) blows up.
I haven't been able to identify why/how it blows up exactly, but it has something to do with the controlled value (from useInputControl) changing on its own as soon as the condition to render the hidden input becomes true and the hidden input gets rendered.
Any idea what's going on here? I can try to make another reproduction if needed, but you always seem to already know what the problem is so I'll wait this time. 😅

A repo would be great for this case.
How are you conditionally rendering the custom input? I can think of an issue with the hidden input messed up if you are not unmounting the component that called useInputControl hooked together. As it does pollute the form data and affect validation. Is this what you are doing?
function CustomInput() {
  const control = useInputControl();

  // ...
}

function Example() {
  const [state, setState] = useState()

  return (
    <diV>
       {state === 'abc' ? <CustomInput /> : null}
    </div>
  );

}

I'm not unmounting the component that calls useInputControl as it's the same component as the one that calls useForm. Currently doing this:
function Example() {
  const [form, fields] = useForm({ ... });
  const control = useInputControl({ ... });
  const [cond, setCond] = useState(false);
  const customNonNativeInputRef = useRef(null);

  return (
    <>
      {/* field.otherThing radio input that toggles cond */}

      {cond ? (
        <>
          <CustomNonNativeInput ref={customNonNativeInputRef} />
          <input
            name={fields.thing}
            defaultValue={fields.thing.initialValue}
            className="visually-hidden"
            tabIndex={-1}
            onFocus={() => {
              customNonNativeInputRef.current?.focus();
            }}
          />
        </>
      ) : null}
    </>
  );
}

I'll throw a repro together tomorrow if you don't stop me before then. 🙂

I think the issue is clear to me now. So a repo is not needed. Thanks and sorry for the trouble so far.
So what's going wrong? The useInputControl() hook thought there is no input rendered for fields.thing at first (assume your condition is false initially) and inserted an hidden input for you. Then, when you select the radio button and render the custom input with the hidden input, the DOM has two input for the same fields and the formdata is polluted with it.
We can introduce an option to the useInputControl() for this behaviour. But I start to believe that the idea of having useInputControl() inserting a hidden input for you isn't a reliable solution 🙃 I am very likely looking into introducing a new hook that does what useInputControl() does except this particular behaviour and deprecate it.

Yep, that matches what I'm seeing exactly so I think you've got it. I'll render them unconditionally for now and await the new useControl hook (or whatever you call it). 👍 Thanks, Edmund!


add clusterrole rbac for foundation

Signed-off-by: Zhiwei Yin<EMAIL_ADDRESS>story: https://github.com/open-cluster-management/backlog/issues/14686

@zhiweiyin318 With operator sdk updated to a recent version, multiclusterhub roles are automatically generated via RBAC markers. See the markers in https://github.com/open-cluster-management/multiclusterhub-operator/blob/main/controllers/multiclusterhub_controller.go#L78. After adding the markers the rbac files can be regenerated via make generate make manifests and make bundle

@JakobGray thanks for your comments. please review again.


Mouse

Microsoft PowerToys version
0.71.0
Installation method
Microsoft Store
Running as admin
No
Area(s) with issue?
Mouse Without Borders
Steps to reproduce
Issues handing over mouse-pointer to a second PC on the same network.
I've tried uninstalling the app, rebooting, removing all connected machines - but this latest release is temperamental to say the least.
App is running on two machines both on the same network.
Both machines are listed as connected devices within PowerToys, but it's now either refusing to handover mouse control to the other machine, OR, worse still, it mirrors mouse movement on the second machine whilst your focussed on the first machine - with potentially disastrous results (accidentally deleting files on the machine you're not focussed on - not a good thing)
Mouse handover/control was never perfect, but prior to version 0.71.0 - you were aware it was or wasn't connected to the additional machine and that was the end of it.
Now, I have to disable it and hope for the next release.
✔ Expected Behavior
Mouse control to be handed over to ONE machine.
❌ Actual Behavior
Mouse movement on both machines at the same time.
(I don't need stereo mouse control - that doesn't make sense)
Other Software
No response

Is this issue still relevant in v0.73? /needinfo


No deployment story for Node or Typescript

This document jumps straight into "Publishing from Visual Studio", but is called "Deploy your local bot to Azure". Is Publishing from VS the only way to deploy a local bot? As a Node/TypeScript developer who uses VSCode, this doc fails to let me know how to deploy my local bot.

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

ID: cf112c0a-0400-ede4-ab7c-ce10f86d6f30
Version Independent ID: 5fa92c50-b8d1-460c-aa3c-f3f851c15da9
Content: Deploy your bot to Azure - Bot Service
Content Source: articles/bot-builder-howto-deploy-azure.md
Service: bot-service
Product: bot-framework
GitHub Login: @ivorb
Microsoft Alias: v-ivorb

@ryanvolum - we've had trouble getting it to work in JS. Investigating if the issues have been fixed on JS side...

Update: I got confirmation from the dev that deploying local JS bot to Azure using AZ CLI is not working and will be investigated sometime next week. Will update the content when a fix is available.

Thanks Kamran. If we get a fix for JS and not TS, we may consider creating a specific TS deployment bug to track it separately

Is there a way to deploy local TS bot to Azure using AZ CLI? Or an update on deploying local JS bot?

@Kaiqb There's still no documentation on deploying a JS bot without using the CLI. There's a page showing how to deploy a C# bot using Visual Studio. It'd be great to have something similar for JS (either through Visual Studio Code or through the Azure portal).


Constrain QCElemental

QCElemental is making some changes which might break QCSubmit
It's be nice to patch the repodata as well

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Also agree with patching existing packages, good thinking.


Added a dialog for copying memory from RAM and formatting it into byte strings

Added a dialog which can be found under the View menu for copying segments of memory into formatted byte strings.
These byte string options are:

Byte String
Byte String (No Spaces)
Python Byte String
Python Byte List
C Array

The dialog takes a base address, a count (hex or decimal), and a method for formatting the bytes. Upon clicking 'Apply', the bytes will be shown as a formatted string in the output box. The output only updates when 'Apply' is clicked. If the byte format changes, the old data will be reformatted to the new format.
The boxes are error checked for valid inputs. I created my own error checking functions for valid hex/decimal strings and for hex string->u32 and decimal string -> u32 because I couldn't find a common function for doing so.
This was my first time working with Qt, so let me know if there's a more proper way to work with some of these functions and classes.
I was unsure of the "Moc'ing" that was happening during the build, so I'm not sure if I'm building in a way that conforms to that style. So that may be another thing worth looking at.

@roeming It seems you also added Undo and Scanner Range feature in this PR. If you are willing to rebase, we can use this after I do some tests with it.

Rebased

@roeming failing linux build:
...Dolphin-memory-engine/Source/GUI/MemCopy/DlgCopy.h:7:10: fatal error: ..\GUICommon.h: No such file or directory

In general, the features work well and the code is fine.
Before merging this however, could you please change the window type to not include the (?) button. It doesn't seem to function anyhow.

In general, the features work well and the code is fine. Before merging this however, could you please change the window type to not include the (?) button. It doesn't seem to function anyhow.

Actually, you can disregard this. It seems to be something that is automatically removed once we move to Qt 6.
The other windows have the same (?) button.

I'm just going to merge this and fix it since I saw someone else opened a PR on your fork with the CMake change:
https://github.com/roeming/Dolphin-memory-engine/pull/1/commits/a62feb5bd7c0379027fd4497ff71e4ec0ef13652
Thanks again for your effort.


Problem with proxy autentication

Hi
I have a problem with proxy settings
https://github.com/Appdynamics/AppDynamics.DEXTER/wiki/Proxy-Settings
I add the block of proxy in my net471\AppDynamics.Dexter.exe.config
the original code of this config is:
<?xml version="1.0" encoding="utf-8"?> <configuration>     <startup>          <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.1"/>     </startup> </configuration>
i added the block system.net with the default proxy in the configuration block in my first try
i added the block system.net with the default proxy behind the configuration block in my second try
All time i obtain the same error using a correct job json:
dotnet exec netcoreapp2.0/AppDynamics.Dexter.dll -j jobs/eciJob1.json
Checking input job file /home/jtimon/proyectos/ECI/DEXTER/jobs/eciJob1.json
Checking output folder /home/jtimon/AppD.Dexter.Out
Creating job output folder /home/jtimon/AppD.Dexter.Out/eciJob1
Processing input job file to output job file
Target [1] Controller ControllerApi: ControllerUrl='https://xxxxxxxxx.saas.appdynamics.com', UserName='yyy@xxxxxxxxx' not accessible
Job File Problem: Expanded targets but not a single valid target to work on
This is most likely caused by either incorrect password or incorrectly specified user name.
Only AppDynamics-internal authentication is supported in username@tenant format
If you are using SAML or LDAP account, please change to AppDynamics-internal account
Application execution took 00:00:00.6768887 (676 ms)
Regards

Hello there,
dotnetcore applications in netcoreapp2.0/ folder do not use the .NET Full framework config from net471\AppDynamics.Dexter.exe.config. Those are separate execution modes.
Read https://github.com/Appdynamics/AppDynamics.DEXTER/wiki/Proxy-Settings#net-core-framework-on-windows-on-mac, for workaround on setting system proxy on your mac/Linux machine.
Daniel

The instructions to get proxy on mac are in the docs


fix typos in docs

Description
Corrects grammar mistakes in README.md, CONTRIBUTING.md and docs/doc.go.
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[x] Refactoring

Checklist:

[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I ran make goimports
[x] I ran golangci-lint

@nunnatsa

Thanks @alexandear - great catches. Added one inlune comment

Fixed.
Found other mistakes Constantly -> Consistently.


ImportError: cannot import name 'ugettext' from 'django.utils.translation' and TypeError: Signal.init() got an unexpected keyword argument 'providing_args'

I'm getting
`ImportError: cannot import name 'ugettext' from 'django.utils.translation' (C:\realtime-projects\python-django\.venv\Lib\site-packages\django\utils\translation\__init__.py). Did you mean: 'gettext'?`

To suppress that i've imported below libraries in settings.
import django
from django.utils.translation import gettext, gettext_lazy
django.utils.translation.ugettext = gettext
django.utils.translation.ugettext_lazy = gettext_lazy

Then, I got the same issue, which is
TypeError: Signal.__init__() got an unexpected keyword argument 'providing_args'
This issue is raising, when I'm adding  "graphql_jwt.refresh_token.apps.RefreshTokenConfig" in INSTALLED_APPS of Django project.
More Details:
Libraries Version:
Django==5.0.7
django-filter==24.2
django-graphql-auth==0.3.16
django-graphql-jwt==0.3.0
graphene==2.1.9
graphene-django==2.16.0
graphql-core==2.3.2
graphql-relay==2.0.1
Commands to raise the issue:
Install the above libraries in existing django project and run python manage.py makemigrations
Originally posted by @Av1nag in https://github.com/flavors/django-graphql-jwt/issues/328#issuecomment-2235165166

In case it helps, I think you may have tried to update your requirements.txt or otherwise ended up in a situation where an upgrade left you at a lower version than the latest version. The issue occurred for me when you depend on django-rest-framework-jwt, which is currently unmaintained.
The django-rest-framework-jwt project is still depending on pyjwt<=2.0.0 while django-graphql-jwt is expecting a newer version. In order to remedy this, upgrading packages with pip will keep django-graphql-jwt at a lower version such as 0.2.2 in order to keep dependencies matching properly.
It seems like moving from django-rest-framework-jwt (or whichever old dependency you may have) could remedy the issue.

In case it helps, I think you may have tried to update your requirements.txt or otherwise ended up in a situation where an upgrade left you at a lower version than the latest version. The issue occurred for me when you depend on django-rest-framework-jwt, which is currently unmaintained.
The django-rest-framework-jwt project is still depending on pyjwt<=2.0.0 while django-graphql-jwt is expecting a newer version. In order to remedy this, upgrading packages with pip will keep django-graphql-jwt at a lower version such as 0.2.2 in order to keep dependencies matching properly.
It seems like moving from django-rest-framework-jwt (or whichever old dependency you may have) could remedy the issue.

If you're not using REST implementation in your project, I suggest you to remove django-rest-framework-jwt and upgrade django-graphql-jwt. I'm actually implementing only graphql APIs in my project. So, I've done that now it's working good with new version deps.


Order placement style adjustments

PR is under review of Open Wealth community. Feedback will be provided as soon as the review is completed.


The NetworkName is static and cannot be changed

First thank you for this capi for harvester provider.
As you can see here the NetworkName for new VMs is hardcoded to vlan1 which makes it impossible to use a different NetworkName.
At least this should be mentioned in the README as a requirement. :smiley:
I am currently not really sure if additional networks are used at all, if someone extends that list.

https://github.com/rancher-sandbox/cluster-api-provider-harvester/blob/07d0b61f34a8277c0b8eac620dcd52e757e14b5b/samples/rke2/example.yaml#L120
https://github.com/rancher-sandbox/cluster-api-provider-harvester/blob/07d0b61f34a8277c0b8eac620dcd52e757e14b5b/samples/rke2/example.yaml#L140
https://github.com/rancher-sandbox/cluster-api-provider-harvester/blob/07d0b61f34a8277c0b8eac620dcd52e757e14b5b/samples/kubeadm/example.yaml#L134
https://github.com/rancher-sandbox/cluster-api-provider-harvester/blob/07d0b61f34a8277c0b8eac620dcd52e757e14b5b/samples/kubeadm/example.yaml#L154

@firecyberice Thank you so much for the issues, I will try to take a look at them ASAP (for now, I am the only one working on this on my free time, but hoping to onboard more people if I get some more traction :) )

Fixed by 76a6e88dcdc1fe51be36bee46b7af3765a8639d8


[ERROR] Error: The docs folder does not exist for version "current". A docs folder is expected to be found at docs.

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[ ] I have tried the npm run clear or yarn clear command.
[ ] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[ ] I have read the console error message carefully (if applicable).

Description
npm start =>
[ERROR] Error: The docs folder does not exist for version "current". A docs folder is expected to be found at docs.
on the console
Reproducible demo
No response
Steps to reproduce
1.npm run start
Expected behavior
no error
Actual behavior
[ERROR] Error: The docs folder does not exist for version "current". A docs folder is expected to be found at docs.
Your environment

Public source code:
Public site URL:
Docusaurus version used:
Environment name and version (e.g. Chrome 89, Node.js 16.4):
Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Self-service

[X] I'd be willing to fix this bug myself.

Sorry, without a repro, there's nothing we can help you with. We have continuously stressed in the issue template that PLEASE GIVE A REPRO and PLEASE DON'T USE GITHUB FOR SUPPORT. I'm closing this, and should you have further information to provide, feel free to reach out on Discord.


wht is the float division trick called?

Hi,
this is not an issue:
I was admiring your flyback driver code and I'd just like to know what the trick you used to divide by a float with only integers here is called:
https://github.com/cnlohr/cnixxi/blob/d3db1aef0dade1c4579eeff3b5d0570b02ada58f/firmware/nixitest1/nixitest1.c#L239
Is this something along the lines of continued logartihms?
Are the terms trial and error or is there a trick to finding them?
Sorry if the questions are stupid, I really don't know.

I literally don't know if there's a name for this.  It was something I saw a compiler do a looong time ago in a weird situation and I was like "huh, that's a neat trick."  I don't even recall what compiler it was.

@cnlohr, so I've looked at the code again today, and now it clicked:
You're dividing by just-not-enough to cross the target, and then successively approximating the ratio until you're close enough, subtracting ever smaller fractions of the same number, choosing the subtractor to be just a tiny bit smaller than the remaining difference.
The same is also possible from the other direction: divide by just-a-bit-too-much and then add back ever smaller fractions.
And the divisions are dictated by bit-shifts, chosen by trial and error / log(x,2) and then directional rounding?
Sadly I couldn't find a name for this either but I think it's brilliant!
It seems to be related to division by a constant, but most of the time, wikipedia is difficult for me to understand.
@emeb
I've looked at the CSD article you linked but couldn't make much of it, but later found Horners method, both and their combination explained exceedingly well in a TI App note.
I think it's not exactly the same as horner + CSD allows more "quick" precision by using + and -.
I've exercised them for the 4.44 constant used in cnixxi:
binary *< 1
x / 4.44
= x * (1/ 4.44)
= x * 0.224224
= x * 0b0.0011100110101000

CSD
 0 0 1 1 1 0 0 1 1 0 1 0 1 0 0 0
 0 0 1 1 1 0 1 0-1 0 1 0 1 0 0 0
 0 1 0 0-1 0 1 0-1 0 1 0 1 0 0 0
distances
  2     3   2   2   2   2

horner
xtemp = x >> 2 + x
xtemp = xtemp >> 2 - x
xtemp = xtemp >> 2 + x
xtemp = xtemp >> 2 - x
xtemp = xtemp >> 3 + x
result = xtemp >> 2

Does that look right to you? At least my calculator agrees :D

Going to leave this here:
https://github.com/recallmenot/bitshift_div
There's a calculator in there to determine the bit shifts used by @cnlohr s method.

In the future, may want to consider making it a html+javscript thing, so it could be on a github.io page?
But, that's an interesting trick to use + and -.  I have definitely done it with + and -, myself in the past.

I'm adding this to my "to make a video list" but who knows if that will ever happen.


ansible: add dedicated target, cluster tier

@dak1n1
I think this will be a new required variable in a dedicated cluster: 'osod_cluster_tier: dedicated'
and also will be required in dedicated clusters:
osce_scripts
osce_sylesheets
osce_properties

/lgtm


Not parsing   in HtmlParser

Non-Breaking Space ( ) or ( ) are not parsing correctly
public class Program
{
    public static void Main(string[] args)
    {
        string xmlStringWorking = "<xml>* $    © ¨ </xml>";

        var parser3 = new HtmlParser();

        var document3 = parser3.Parse(xmlStringWorking);

        XmlDocument doc = new XmlDocument();

        doc.LoadXml(document3.DocumentElement.GetElementsByTagName(@"body").First().InnerHtml);
    }
}

What do you expect?
If you look at the fiddle you'll see that the outcome is * $    © ¨ , which is exactly the same outcome in all evergreen browser.
Just to simplify see this snippet which alerts the same string.
HTH!

hi @FlorianRappl ideally   should convert to space what cannot break,

ideally   should be convert in to non-breaking space,   is not the decoded value

That is a render information - see what your browser sees / the specification says. We follow the specification, otherwise we are doomed.

With InnerText you would get a non breaking space but obviously not the tag names.
https://dotnetfiddle.net/Lw7lQL
See also https://github.com/AngleSharp/AngleSharp/issues/708#issuecomment-419704926


add lib/ to .npmignore (to ignore 5mb google closure jar)

I noticed that the idb-wrapper tarball was taking forever to npm install on some slow internet, so I checked it out and noticed that the lib/closure folder has a 5.3mb compiler.jar file that seems to be a devDependency

Yep, Closure Compiler is a dev dependency and doesn't belong in the npm distribution. Dupes #52. Will leave this open as this is a PR.


obs-ndi not working

Issue description
The obs-ndi plugin seems to be broken.
Steps to reproduce
Install obs-studio and obs-ndi from unstable.
"Install" the plugin as described in https://github.com/NixOS/nixpkgs/blob/c95664665d15ccbf4a490c3db7c07b00925788a1/pkgs/applications/video/obs-studio/obs-ndi.nix
nix-env -f "<nixpkgs>" -iA obs-ndi
mkdir -p ~/.config/obs-studio/plugins/bin
ln -s ~/.nix-profile/lib/obs-plugins/obs-ndi.so ~/.config/obs-studio/plugins/bin/

When starting OBS the NDI settings don't show up under "Tools" and also not under Filters.
Technical details

system: "x86_64-linux"
host os: Linux 4.19.103, NixOS, 19.09.git.177bc66 (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.2
channels(root): "nixos-19.09.2229.d7843c8add6, unstable-20.09pre215947.82b54d49066"
channels(sohalt): ""
nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos

The correct location seems to be ~/.config/obs-studio/plugins/obs-ndi/bin/64bit/obs-ndi.so (replace 64bit with 32bit on a 32-bit system).

Just ran into this issue myself, and @yvt's suggested fix worked. I also linked in locale/en-US.ini so that the menu labels showed up correctly.
I'm using home-manager, so here's the code I used instead of a manual ln:
# Managing the OBS-NDI plugin.
#
# Could be extended into an "OBS plugin" set of modules, probably...
home.file.".config/obs-studio/plugins/obs-ndi/bin/64bit/obs-ndi.so".source =
  "${pkgs.obs-ndi}/lib/x86_64-linux-gnu/obs-plugins/obs-ndi.so";
home.file.".config/obs-studio/plugins/obs-ndi/data/locale/en-US.ini".source =
  "${pkgs.obs-ndi}/share/obs/obs-plugins/obs-ndi/locale/en-US.ini";

This should work now, tested with the recent OBS major version bump.


Log new headers

To solve #37412

API change check
API changes are not detected in this pull request.


Export to excel

Hi,
Thanks for creating this useful application.
Would it be possible to view the notes individually and be able to export them to excel, or also to have a feature wherein we can import specific notes/bookmarks?
For example, a table having the below columns can be designed:
Publication | Chapter | Verse/Para | Note | Tags
Thanks

@Leroyjd123 Use the "Details" window to show Notes. You can select all and copy them to the clipboard for transfer to Excel. You can use the same Window to Import Bible notes. Does this cover your request?

@Leroyjd123 Use the "Details" window to show Notes. You can select all and copy them to the clipboard for transfer to Excel. You can use the same Window to Import Bible notes. Does this cover your request?

@AntonyCorbett I have tried doing that, and it works fine, but certain details, such as which scripture was the note created or what tags a particular note has, is not available.
So what I meant was something wherein, I could see the note and the verse to which it was linked.
Thanks for responding so quickly!

@AntonyCorbett I have tried doing that, and it works fine, but certain details, such as which scripture was the note created or what tags a particular note has, is not available.
So what I meant was something wherein, I could see the note and the verse to which it was linked.
Thanks for responding so quickly!

@Leroyjd123 The latest pre-release version (v<IP_ADDRESS>) contains a function to export Bible notes to Excel. Use the Ellipsis button next to the "DETAILS" button. Are you able to test and provide feedback please?

@AntonyCorbett
I have just downloaded the prerelease and tried out the export feature, and it's working really well.
I will try using it more fully this week and will let you know if I get any issues.
Thanks again for this feature!!


Add a debug web view to login for local development

Fixed: https://github.com/NigelBreslaw/guardian-ghost/pull/896


Make argdiff an optional keyword argument to update

It would default to the n-tuple of NoChange() values where n is the number of arguments to the generatiev function. Passing in the tuple of NoChange() values is common when doing operations on the top-level generative function of a model in e.g. MCMC.

I started implementing this here (including making the other arguments excluding the trace itself into keyword arguments): https://github.com/probcomp/Gen/tree/20200410-marcoct-argdiffoptional, but the extra typing for the keyword arguments everywhere that update() is almost makes the change not worth it.

Actually, on second thought, we can keep the GFI interface signature the same (no keyword args), but then just the keyword argument wrapper:
function update(trace;
        args=get_args(trace),
        argdiffs=map((_) -> NoChange(), args),
        constraints=EmptyChoiceMap())
    update(trace, args, argdiffs, constraints)
end

This is indeed what I implemented, so all the extra keyword arguments in calls were unnecessary.

The same defaults for regenerate should be implemented as part of the same PR.


DB.source() should support InputStream

I guess it would be useful to have an api which enables user to pass an InputStream instead of a resourceName in case the resource is not part of the project.
If agreed on project level I can prepare a PR.

Pull Request welcome... ;-)

@vorburger I added a PR some time ago. Maybe you can have a give some feedback on it.

#273 finally reviewed and merged.  Thanks for contributing!
Really so very sorry it took this long to review this PR!
Do please feel free to send more PRs for anything.


Unable to connect zeplin to storybook with authentication (401 Error)

Thank you for the great Zeplin plugins! It's really a pleasure to use them just by following easy steps from documentation.
However one thing that doesn't work for the is a connection to the Storybook.
When I add storybook plugin to my components.json file and run zeplin connect I get following error:
% zeplin connect

Zeplin CLI - v1.0.4

Detected Storybook at https://storybook.MY_COMPANY.io/iframe.html

Connecting components to Zeplin components failed.

    401 - {"type":"Buffer","data":[60,104,116,109,108,62,13,10,60,104,101,97,100,62,60,116,105,116,108,101,62,52,48,49,32,65,117,116,104,111,114,105,122,97,116,105,111,110,32,82,101,113,117,105,114,101,100,60,47,116,105,116,108,101,62,60,47,104,101,97,100,62,13,10,60,98,111,100,121,62,13,10,60,99,101,110,116,101,114,62,60,104,49,62,52,48,49,32,65,117,116,104,111,114,105,122,97,116,105,111,110,32,82,101,113,117,105,114,101,100,60,47,104,49,62,60,47,99,101,110,116,101,114,62,13,10,60,104,114,62,60,99,101,110,116,101,114,62,110,103,105,110,120,47,49,46,49,56,46,48,60,47,99,101,110,116,101,114,62,13,10,60,47,98,111,100,121,62,13,10,60,47,104,116,109,108,62,13,10]}

Please check<EMAIL_ADDRESS>for details.

where cli.log says following:
2020-09-28 10:17:32 - info - Zeplin CLI - v1.0.4
2020-09-28 10:17:32 - debug - connect options: {"configFiles":[".zeplin/components.json"],"devMode":false,"devModePort":9756,"devModeWatch":true,"plugins":[]}
2020-09-28 10:17:32 - debug - .zeplin/components.json content: {"plugins":[{"name":"@zeplin/cli-connect-angular-plugin","config":{"useFullSnippet":true,"useFullDescription":true}},{"name":"@zeplin/cli-connect-storybook-plugin","config":{"url":"https://storybook.MY_COMPANY.io/"}}],"projects":["PROJECT_ID"],"styleguides":[],"components":[{"path":"projects/common/src/lib/components/notification-toast-content/notification-toast-content.component.ts","zeplinNames":["Toast/success"]},{"path":"projects/common/src/lib/components/buttons-and-Indicators/buttons/button/button.component.ts","zeplinNames":["PrimaryButton/default"]}],"gitlab":{"repository":"MY_COMPANY/REPO_NAME","branch":"develop"}}
2020-09-28 10:17:32 - debug - component config files: [{"plugins":[{"name":"@zeplin/cli-connect-angular-plugin","config":{"useFullSnippet":true,"useFullDescription":true}},{"name":"@zeplin/cli-connect-storybook-plugin","config":{"url":"https://storybook.MY_COMPANY.io/"}}],"projects":["PROJECT_ID"],"styleguides":[],"components":[{"path":"projects/common/src/lib/components/notification-toast-content/notification-toast-content.component.ts","zeplinNames":["Toast/success"]},{"path":"projects/common/src/lib/components/buttons-and-Indicators/buttons/button/button.component.ts","zeplinNames":["PrimaryButton/default"]}],"gitlab":{"repository":"MY_COMPANY/REPO_NAME","branch":"develop"}}]
2020-09-28 10:17:35 - debug - Initializing @zeplin/cli-connect-angular-plugin.
2020-09-28 10:17:35 - debug - @zeplin/cli-connect-angular-plugin has init method. Initializing with {"useFullSnippet":true,"useFullDescription":true}
2020-09-28 10:17:35 - debug - Initializing @zeplin/cli-connect-storybook-plugin.
2020-09-28 10:17:35 - debug - @zeplin/cli-connect-storybook-plugin has init method. Initializing with {"url":"https://storybook.MY_COMPANY.io/"}
2020-09-28 10:17:36 - error - Connecting components to Zeplin components failed.    401 - {"type":"Buffer","data":[60,104,116,109,108,62,13,10,60,104,101,97,100,62,60,116,105,116,108,101,62,52,48,49,32,65,117,116,104,111,114,105,122,97,116,105,111,110,32,82,101,113,117,105,114,101,100,60,47,116,105,116,108,101,62,60,47,104,101,97,100,62,13,10,60,98,111,100,121,62,13,10,60,99,101,110,116,101,114,62,60,104,49,62,52,48,49,32,65,117,116,104,111,114,105,122,97,116,105,111,110,32,82,101,113,117,105,114,101,100,60,47,104,49,62,60,47,99,101,110,116,101,114,62,13,10,60,104,114,62,60,99,101,110,116,101,114,62,110,103,105,110,120,47,49,46,49,56,46,48,60,47,99,101,110,116,101,114,62,13,10,60,47,98,111,100,121,62,13,10,60,47,104,116,109,108,62,13,10]}
2020-09-28 10:17:36 - debug - StatusCodeError: Connecting components to Zeplin components failed.    401 - {"type":"Buffer","data":[60,104,116,109,108,62,13,10,60,104,101,97,100,62,60,116,105,116,108,101,62,52,48,49,32,65,117,116,104,111,114,105,122,97,116,105,111,110,32,82,101,113,117,105,114,101,100,60,47,116,105,116,108,101,62,60,47,104,101,97,100,62,13,10,60,98,111,100,121,62,13,10,60,99,101,110,116,101,114,62,60,104,49,62,52,48,49,32,65,117,116,104,111,114,105,122,97,116,105,111,110,32,82,101,113,117,105,114,101,100,60,47,104,49,62,60,47,99,101,110,116,101,114,62,13,10,60,104,114,62,60,99,101,110,116,101,114,62,110,103,105,110,120,47,49,46,49,56,46,48,60,47,99,101,110,116,101,114,62,13,10,60,47,98,111,100,121,62,13,10,60,47,104,116,109,108,62,13,10]}    at new StatusCodeError (/Users/@USERNAME/.config/yarn/global/node_modules/request-promise-core/lib/errors.js:32:15)    at Request.plumbing.callback (/Users/@USERNAME/.config/yarn/global/node_modules/request-promise-core/lib/plumbing.js:104:33)    at Request.RP$callback [as _callback] (/Users/@USERNAME/.config/yarn/global/node_modules/request-promise-core/lib/plumbing.js:46:31)    at Request.self.callback (/Users/@USERNAME/.config/yarn/global/node_modules/request/request.js:185:22)    at Request.emit (events.js:198:13)    at Request.<anonymous> (/Users/@USERNAME/.config/yarn/global/node_modules/request/request.js:1154:10)    at Request.emit (events.js:198:13)    at IncomingMessage.<anonymous> (/Users/@USERNAME/.config/yarn/global/node_modules/request/request.js:1076:12)    at Object.onceWrapper (events.js:286:20)    at IncomingMessage.emit (events.js:203:15)
2020-09-28 10:17:36 - info - Please check<EMAIL_ADDRESS>for details.

My storybook instance is protected with authentication, so may this be a problem? Is there any way to pass credentials to zeplin plugin or have it connected same way as with Gitlab where it just uses the code path?
Here is my configuration.json file.
{
  "plugins": [
    {
      "name": "@zeplin/cli-connect-angular-plugin",
      "config": {
        "useFullSnippet": true,
        "useFullDescription": true
      }
    },
    {
      "name": "@zeplin/cli-connect-storybook-plugin",
      "config": {
        "url": "https://storybook.MY_COMPANY.io/"
      }
    }

  ],
  "projects": [
    "PROJECT_ID"
  ],
  "styleguides": [],
  "components": [
    {
      "path": "projects/common/src/lib/components/notification-toast-content/notification-toast-content.component.ts",
      "zeplinNames": [
        "Toast/success"
      ]
    },
    {
      "path": "projects/common/src/lib/components/buttons-and-Indicators/buttons/button/button.component.ts",
      "zeplinNames": [
        "PrimaryButton/default"
      ]
    }
  ],
  "gitlab": {
    "repository": "MY_COMPANY/REPO_NAME",
    "branch": "develop"
  }
}

Hey,
I think we can add the ability to pass headers to be used for HTTP authentication. I'll be working on it in a short time.
In the meantime, I would suggest you to use startScript or command parameters if you can locally start the Storybook on your project.
I should mention that, as of now, the plugin cannot automatically match stories with Angular components. Check out this section for more info.  We are currently evaluating possible improvements for better support.

@yuqu do you have any progress on this issue? We're using external link feature now, but really looking forward toward this kind of integration. Thanks again for an amazing product!

Hey @nitoloz! Sorry for the delay. Incidentally we've just started to work on a new CLI feature, I think I can arrange sometime to resolve this issue until the next week.

I've just found out that JSDOM does not allow to use custom headers. https://github.com/jsdom/jsdom/issues/2699#issuecomment-681787493
@nitoloz Do you need HTTP Basic authentication? If so, you could set the url as https://<username>:password@https://storybook.MY_COMPANY.io/ to authenticate. I'll add this info into the readme. If you use another type of authentication, the only way would be to use a local Storybook setup for now as I mentioned.


[multiplayer] Pause game when simulator frame is not in view (tabbed away, for example)

when host's simulator iframe is not visible:

pause the simulator
send a "game paused" message to the server
server broadcasts this message to all clients, including host
when message is received, the client shows a modal "Game paused"
the host's modal includes a "resume game" button
when resume game is clicked, host sends a "game resumed" message to the server
when "game resumed" is received, clients hide the pause modal, host will resume the simulator

Fixed via https://github.com/microsoft/pxt/pull/9186


How to document a anonymous function

Is there no way to comment and document anonymous functions?

By anonymous function, do you mean a function declaration assigned to a variable? #998 Or arrow functions in a class? #1003. If neither of these, what does the code look like you are trying to document?

In this case it is an arrow function to declare an entry point in the express router
router.get('/', (req, res) => {

    /**
     * Some description
     * @param req Request object
     * @param res Response object
     */

@ChTosar Since that is an expression and not a function declaration, it can't be documented.
To document that callback you would need to define it separately from the expression where it is registered.

/**
 * Some description
 * @param req Request object
 * @param res Response object
 */
function callbackName (req, res) {
 // ...
}

router.get('/', callbackName);

I know but... that's not cool 😢

I'm a bit confused as to why you would document that function in the first place. It's not exposed anywhere. What purpose would including it in your documentation serve?

Because there is the declaration of a petition and I want to document them.
But maybe i need something like swagger-jsdoc for this purpose

@ChTosar Yeah, TypeDoc is designed more for documenting source code. To document a REST API, something to generate swagger docs would likely be a better solution with more features you would like.


Update ci-test.yml, add init.py to the test folder

Codecov Report
Base: 20.47% // Head: 62.59% // Increases project coverage by +42.11% :tada:

Coverage data is based on head (1e4c601) compared to base (f1f543b).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #44       +/-   ##
===========================================
+ Coverage   20.47%   62.59%   +42.11%
===========================================
  Files          18       14        -4
  Lines        1260      965      -295
===========================================
+ Hits          258      604      +346
+ Misses       1002      361      -641

Flag
Coverage Δ

unittests
62.59% <ø> (+42.11%)
:arrow_up:

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

Impacted Files
Coverage Δ

tests/test_math_core.py

tests/test_haiku_modules.py

tests/test_space_model.py

setup.py

nndt/space/repr_mesh.py
71.38% <0.00%> (+71.38%)
:arrow_up:

nndt/space/abstracts.py
90.69% <0.00%> (+90.69%)
:arrow_up:

nndt/space/vtk_wrappers.py
91.35% <0.00%> (+91.35%)
:arrow_up:

nndt/space/repr_sdt.py
91.42% <0.00%> (+91.42%)
:arrow_up:

nndt/__init__.py
100.00% <0.00%> (+100.00%)
:arrow_up:

nndt/math_core.py
100.00% <0.00%> (+100.00%)
:arrow_up:

... and 6 more

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.


[Request] run ddup without changing atime

Could ddup be enhanced for allowing a restore of last accessed time (atime) on a file after it is read for de-duplication comparison purposes?  We find atime useful for alerting users to unused files to clean-up.  We would also like to use ddup but it changes atime.

That's a good idea, and it's related to the O_NOATIME request in https://github.com/hpc/mpifileutils/pull/534 for reading files in dcp/dsync, which can be used to modifying the atime value.

As a test, can you check whether adding the O_NOATIME flag to the open call in ddup works:
https://github.com/hpc/mpifileutils/blob/47918154ea0f4895623f36ccf8cbfe2df477c3ae/src/ddup/ddup.c#L96
so that this line changes to
mfu_open(fname, O_RDONLY | O_NOATIME)

As noted in https://github.com/hpc/mpifileutils/pull/534, in addition to keeping atime the same, that could also improve read performance.  It cuts out a bunch of atime updates going to the Lustre metadata server.
I like this as a general improvement for ddup, but we I'll need to verify that this doesn't create problems for file systems that might not support the O_NOATIME flag.  If nothing else, we could enable the flag by default and add a  new command line option to drop it.

I got the below error.  Looks like src/dcp1/compare.c has O_NOATIME in some commented out code, maybe it was considered there as well at one time?
/project/selene-admin/mpifileutils_debug/mpifileutils-v0.11.1/mpifileutils/src/ddup/ddup.c:102:41: error: ‘O_NOATIME’ undeclared (first use in this function)
102 |     int fd = mfu_open(fname, O_RDONLY | O_NOATIME);
|                                         ^~~~~~~~~

Oh, we probably also need to add a #define _GNU_SOURCE statement before any includes in order to pick up the definition for O_NOATIME.  Can you try again after adding that to the very top of the ddup.c file?

Ok, great, I got this to compile now, just need to test ...
Does dsync change atime?  This made we think that O_NOATIME would be nice to ddup, dsync, etc. tools as we don't want to change atime or mtime while looking for old files to clean-up or move.  :)

It works nicely.  Atime is not changed and duplicate files are found, see attached snippet of text showing "ls -alu" output for atime.  (I did cut out some of the file list to trim down the snippet size).    Thanks!
snippet.txt

Ok, good.  Thanks for testing.  I'll make that O_NOATMIE change to ddup and start looking at the other tools.

some adventurers in atime:

"cp -p source target" will keep atime/mtime on target, but changes atime on source.  You can restore atime on source with "touch -r target source".
rsync requires --noatime switch to use O_NOATIME on source and preserve it even with -a (archive) option.  But, target gets new atime even with "rsync -a" in my quick test.

Looks like newer versions of rsync can preserve atime on both source and target, which seems ideal for our use case.  I think that would be a nice goal for dsync as well.  :)
https://unix.stackexchange.com/questions/630228/rsync-keep-access-time-atime-how
Since rsync version 3.2.0, there are two flags that affect atimes:
--atimes, -U preserve access (use) times
--open-noatime avoid changing the atime on opened files
The full description of these is:
   --atimes, -U
          This  tells  rsync to set the access (use) times of the destina‐
          tion files to the same value as the source files.

          If repeated, it also sets the --open-noatime option,  which  can
          help you to make the sending and receiving systems have the same
          access times on the transferred files  without  needing  to  run
          rsync an extra time after a file is transferred.

          Note  that  some  older rsync versions (prior to 3.2.0) may have
          been built with a pre-release --atimes patch that does not imply
          --open-noatime when this option is repeated.

   --open-noatime
          This  tells rsync to open files with the O_NOATIME flag (on sys‐
          tems that support it) to avoid changing the access time  of  the
          files  that  are being transferred.  If your OS does not support
          the O_NOATIME flag then rsync will silently ignore this  option.
          Note  also  that  some filesystems are mounted to avoid updating
          the atime on read access even without the O_NOATIME  flag  being
          set.

So my reading of these (which testing has borne out) is that the following will both keep rsync from updating the atime on src, and will copy the atime of src to dest:
rsync -UU

Thanks, @markmoe19 .  I just merged https://github.com/hpc/mpifileutils/pull/561 to add a new --open-noatime option to various tools to enable this.
Since adding O_NOATIME can lead to an error for normal users when reading files they don't own, enabling it via a new option is a good way to go.
With this, dsync --open-noatime should avoid updating atime on source files.  And as before, by default, dsync currently copies atime from source to destination files when it set the destination timestamps, so that the destination atime should match the source.

Great.  I'll close this one out as resolved by https://github.com/hpc/mpifileutils/pull/561


feat: add pr_name config field

Close #1740

@MarcoIeni, ready for review on this one 👀
Short summary:

did a little refactor of building Tera templates in project.rs and tera.rs as there was a little bit of annoying duplication
implemented the PR name behavior and added tests
synchronized the commit message in the release branch with the PR name

Thanks a lot for your support, it was a really awesome experience! I will take a look at some more issues in the following days and come back with some PRs.


Fix race condition in service processor

Fix race condidtion if processDeletingPod interrupts processUpdatedPod

Coverage increased (+0.1%) to 76.443% when pulling f9ba1556dc110c720f87d4870801da046c912527 on rastislavszabo:bugfix into 1da68da2dc640379426e3503c07b2c1ba909f278 on contiv:master.


⚠ Bofrost.at has degraded performance

In bc58a9e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2718 ms

Resolved: Bofrost.at performance has improved in 92b259c.


Deploy failed: cannot handle socket (RuntimeError)

Ubuntu 18.04
RVM
Rails: 5.2.2
Ruby: 2.5.3
 jets deploy
=> Rails app detected: Enabling Jets Afterburner to deploy to AWS Lambda.
Traceback (most recent call last):
	28: from /home/josue/.rvm/gems/ruby-2.5.3/bin/ruby_executable_hooks:24:in `<main>'
	27: from /home/josue/.rvm/gems/ruby-2.5.3/bin/ruby_executable_hooks:24:in `eval'
	26: from /home/josue/.rvm/gems/ruby-2.5.3/bin/jets:23:in `<main>'
	25: from /home/josue/.rvm/gems/ruby-2.5.3/bin/jets:23:in `load'
	24: from /home/josue/.rvm/gems/ruby-2.5.3/gems/jets-1.4.5/exe/jets:14:in `<top (required)>'
	23: from /home/josue/.rvm/gems/ruby-2.5.3/gems/jets-1.4.5/lib/jets/cli.rb:5:in `start'
	22: from /home/josue/.rvm/gems/ruby-2.5.3/gems/jets-1.4.5/lib/jets/cli.rb:20:in `start'
	21: from /home/josue/.rvm/gems/ruby-2.5.3/gems/jets-1.4.5/lib/jets/cli.rb:48:in `boot_jets'
	20: from /home/josue/.rvm/gems/ruby-2.5.3/gems/jets-1.4.5/lib/jets/core.rb:18:in `boot'
	19: from /home/josue/.rvm/gems/ruby-2.5.3/gems/jets-1.4.5/lib/jets/booter.rb:7:in `boot!'
	18: from /home/josue/.rvm/gems/ruby-2.5.3/gems/jets-1.4.5/lib/jets/booter.rb:31:in `turbo_charge'
	17: from /home/josue/.rvm/gems/ruby-2.5.3/gems/jets-1.4.5/lib/jets/turbo.rb:15:in `charge'
	16: from /home/josue/.rvm/gems/ruby-2.5.3/gems/jets-1.4.5/lib/jets/turbo/rail.rb:14:in `setup'
	15: from /home/josue/.rvm/gems/ruby-2.5.3/gems/jets-1.4.5/lib/jets/turbo/rail.rb:93:in `copy_rack_project'
	14: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:392:in `cp_r'
	13: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:1461:in `fu_each_src_dest'
	12: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:1479:in `fu_each_src_dest0'
	11: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:1463:in `block in fu_each_src_dest'
	10: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:393:in `block in cp_r'
	 9: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:415:in `copy_entry'
	 8: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:1392:in `wrap_traverse'
	 7: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:1392:in `each'
	 6: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:1393:in `block in wrap_traverse'
	 5: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:1392:in `wrap_traverse'
	 4: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:1392:in `each'
	 3: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:1393:in `block in wrap_traverse'
	 2: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:1390:in `wrap_traverse'
	 1: from /home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:418:in `block in copy_entry'
/home/josue/.rvm/rubies/ruby-2.5.3/lib/ruby/2.5.0/fileutils.rb:1278:in `copy': cannot handle socket (RuntimeError)

I see, it's having trouble copying socket files. As a workaround, delete the socket files in tmp before running jets deploy. Will dig into this once have time 👍

Released in v1.4.6 CHANGELOG


Support streaming google.api.HttpBody message

This PR introduces support for streaming the google.api.HttpBody message, which allows client to download large-sized payload.

https://github.com/akuityio/akuity-platform/actions/runs/6891361981/job/18746267647
tests are passing now


[OP] Move elemwise sum op to tensor fcompute

@piiswrong
Other changes(fixes) in this PR

Fix ROIPooling and Correlation's CPU backward because they assume out_grad buffer is zeroed @winstywang
Fix the broadcast_to's gradient(previous one won't have correct shape inference because axis parameter is not available in broadcast_to) @piiswrong
Fix the matrix op's gpu registration
Fix warnings in C API ndarray

please wait until checks finish before merge

I merged in master and test_operator.test_scalar_pow hangs in check_numeric_gradient.
Could you look into it?

ok.. please test locall next time before we really do a force push.

https://github.com/dmlc/mxnet/pull/3482


GoodMarket: The rotation buttons aren't work at "Edit image" screen on Goodmarket

Pre-conditions: User have existing eWallet account and login into Goodmarket
Steps to reproduce:

Open the hamburger menu in the upper right corner
Tap the "Add new" button
Upload some images with valid size
Tap the "Edit button" under uploaded image
Tap the "Left" button
Tap the "Right" button
Pay attention at the result

Actual result: The rotation buttons aren't work at "Edit image" screen
Expected result: The rotation buttons work correctly. User can rotate the picture
Note: buttons aren't work both for iOS and Android devices
Used devices:
iPhone XS // iOS 13.1
Xiaomi Redmi 7 // Android 9.0

it is iframe content. we can't change any code on this project. @AnastasiiaOdnoshevna @sirpy


[ALLUXIO-2723]Make StorageTierAssocTest final

https://alluxio.atlassian.net/browse/ALLUXIO-2723

alluxio-bot, check this please

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14233/
Test PASSed.

Merged build finished. Test PASSed.


Handle notifications

Notifications
This PR extends the subscription behavior of actionType to be aware of notifications. The syntax looks like this:
[originating_account]::[action_name]>[notified_account]

For example, given that action 'foo' of account 'originating' notifies account 'notified', a subscription to this notification would look like this:
originating::foo>notified

With this subscription, its corresponding Updater or Effect will only run when account originating notifies notified of the action foo. Since the wildcard operator * works in combination, you can track all notifications from action originating::foo via:
originating::foo>*

Likewise, you can track all notifications to notified via:
*::*>notified

Other PR Changes

Add property isNotification to interface EosPayload
StateHistoryPostgresBlock now records whether an action is a notification or not via isNotification
MassiveEosActionHandler now validates all actionTypes of all Updaters and Effects of all HandlerVersions upon instantiation, and throws an error if there is one or more invalid actionType.

Does the original syntax still work or is this a breaking change for how we subscribe?

Does the original syntax still work or is this a breaking change for how we subscribe?

Nevermind, reading the code helps. Looks like it is backwards compatible.


get members from db and not json

Description
Get the members from the database and not json file

Do not merge until ok from @dpfernandes

Hi!
Fantastic work here. I have few comments:

I guess we will need to throw an ApiError also if the getMembers fails.
A state should be added to check if any member is deleted in Owner Page.

Yes, you're right. It has to be added as a state in the context and not as a property on the api object.
And yes I think its better to let the board throw an ApiError also.
Maybe the context state could house the userId also. So that the subcomponents don't have to both call the useBoard and the useUser each time

Actually, now that I think about it, maybe its better to fetch the members in a container for the modal. No reason to put the members on the context when its only used by the members modal


MINOR Add status check for gradle scan

Add a commit status check so PRs can easily access the build scan.

Example of when the CI workflow does not produce any build scan artifacts:
https://github.com/mumrah/kafka/actions/runs/10777726936
Example of when it does produce artifacts, and publishes:
https://github.com/mumrah/kafka/actions/runs/10777816130
PR

Example of when it does produce artifacts, but fails to publish:
Job: https://github.com/mumrah/kafka/actions/runs/10777898146 (in a real failure, there would be no build scan links here)
PR

@chia7712 I have added an explanation of how this workflow works with the CI here https://github.com/apache/kafka/pull/17140/files#diff-03dbd91a7c60e880a3123759ea4ab422044357e5d1d75450d63bbcbd064cd0d9R26-R36

@mumrah just a discussion: Have you evaluated the runner quota? the GitHub Actions Policy  says:
The average number of minutes a project uses per calendar week MUST NOT exceed the equivalent of 25 full-time runners (250,000 minutes, or 4,200 hours).

If 1 commit needs 4 hours (4 checks + 2 test suits), we can run 1050 commits one week. The Pulse says there are 54 merges/commits one week, so we have about 1000 remaining quota can be used by PRs. Hence, it seems kafka community will NOT burn out GitHub runner. WDYT?

@chia7712

Have you evaluated the runner quota

I've been watching the Infra report here https://infra-reports.apache.org/#ghactions (requires committer sign-in). Right now, the "CI" workflow (both trunk and PRs) has averaged 3 full-time runners over the last week.

Hence, it seems kafka community will NOT burn out GitHub runner. WDYT?

I think this is correct. Even with the addition of all PRs running the full test suite, I think we'll be well under this limit. Part of the reason I wanted to get caching working before turning it on for all PRs was to avoid increasing our usage too much.


Cannot install on Firefox 48/49 because plugin is not signed

I cannot install on Firefox because plugin is not signed. This is the message Firefox give to me.

http://www.ghacks.net/2016/08/14/override-firefox-add-on-signing-requirement/
or use Firefox Aurora (developer preview) / Nightly
or sign addon for yourself.

Never trust disable the protection of Firefox. Thank anyway. I have solved issue with flash for now so continue to use flash for now. Thanks... this is just to inform the component plug in not work with standard Firefox.

I signed the addon for myself, and it's fairly simple to do. Just follow the instructions here. IIRC, the key commands are jpm xpi and jpm sign. Alternatively, you can upload an xpm file here (copy the link, because it won't redirect automatically after signin)

Why this addon not signed or not posted here https://addons.mozilla.org/ first of all, at least as alpha?

I agree with @asd-and-Rizzo it should be on https://addons.mozilla.org somewhere.

Since so many people seem to want it, I've uploaded my signed copy to a gist.

@Efreak is this the absolute latest copy?

I think created it after the most recent change to this repo, so it should be. The xpi file and the AMO email that it passed automated tests are both dated 8/5/16. However, I can't guarantee it, as I no longer have the VM I used to build it. You may be able to verify it by building the addon yourself, then unzipping and comparing the contents of your and my xpi files.

Closing as fixed


Improve documentation on datepickerConfig's init-date

The documentation of DatePicker states "All settings can be provided as attributes in the datepicker or globally configured through the datepickerConfig". It also gives example of overriding options "formatYear" and "startingDay" with simple strings and integers.
I tried doing the same with the initDate option in multiple ways (string, integer, Date, scope attribute name) before digging in the code and seing that it uses "$scope.$parent.$eval(...)" and needs a scope path to the variable. In my case the path is $parent.$parent.initDate because the field is in a form. It's quite difficult to find this solution by accident. Maybe a hint in the documentation could help?
Thank you for your work.

I think problems with initDate should be fixed as a result of 98e2bdfc8b4dd108acdf3fac75a795675889bbc7 .  Let us know if this is not the case and this issue can be reopened.


Improve handling of updating resources together with statuses

In case the workflow you implement requires to update the resource itself and the status sub-resource at the same time it cannot be handled in a single pass of the createOrUpdateResource() method.
To be able to handle it currently you need to:

Disable generationAwareEventProcessing:
@Controller(crdName = "some.awesome.crd.com", generationAwareEventProcessing = false)

Handle update to the resource and finish with return UpdateControl.updateCustomResource(res). A new event will be published and another pass of the createOrUpdateResource() will be triggered.

Handle update to the status sub-resource and finish with return UpdateControl.updateStatusSubResource(res)

Ideally, we should just update the resource itself and the status sub-resource in a single UpdateControl.updateCustomResource(res) call. In other words - if there are status updates, these should be applied as well on the updated resource automatically.

I see there 2 ways of support this:

Sending instant events. Thus for example the TimerEventSource would have an addition, to send an event immediately. This will ensure that after a an update (either status sub-resource or CR) there will be a new controller execution for sure. This is a quick win, quite easy to implement.

Support this in update control with an explicit API (this way the generation processing can be still turned on). Where we will update both the custom resource and the status sub-resource. Note that these are 2 separate calls to kubernetes API, both includes optimistic locking. Thus in theory it can happen that after first call there is an update happening from a different parti, so the second call will fail on conflict. (Bot CR update and Status updates increases resource version in a CR). The best way to cover this is with retry, since the 3. party update is not necessary updates generation either (so there is not necessary an event from that). So in any case a retry config is advised.

@metacosm its related, but currently I don't see how we could avoid doing uptimistic locking on status subresource updates? fabric8 client seems to be doing this all the time. I think there should be an api to avoid that. (Hope K8S supports that).
Note that this is completely fine since only the controller should update status by definition.

The best way to cover this is with retry
What I think could be tricky here is that technically the status itself could be updated with a newer event. so retrying may override the new status with the old one.

I see there 2 ways of support this:
1. Sending instant events. Thus for example the TimerEventSource would have an addition, to send an event immediately. This will ensure that after a an update (either status sub-resource or CR) there will be a new controller execution for sure. This is a quick win, quite easy to implement.

Re-triggering the method for simply a status update doesn't appear very friendly to me, especially because the createOrUpdateResource method might be costly.

2. Support this in update control with an explicit API (this way the generation processing can be still turned on). Where we will update both the custom resource and the status sub-resource. Note that these are 2 separate calls to kubernetes API, both includes optimistic locking. Thus in theory it can happen that after first call there is an update happening from a different parti, so the second call will fail on conflict. (Bot CR update and Status updates increases resource version in a CR). The best way to cover this is with retry, since the 3. party update is not necessary updates generation either (so there is not necessary an event from that). So in any case a retry config is advised.

If you're only updating the status, the generation shouldn't be updated so there shouldn't be a conflict on the status update call.

If you're only updating the status, the generation shouldn't be updated so there shouldn't be a conflict on the status update call.

But the resourceVersion will be updated, right?

If you're only updating the status, the generation shouldn't be updated so there shouldn't be a conflict on the status update call.

@metacosm
But the resourceVersion will be updated, right?

I would say no because you're not changing the spec (if you only update the status sub-resource, that is), hence not changing the resource itself but I have to double-check.

In the go framework I previously implemented for operators, updating the status was a separate operation from the create/update process, where each resource associated with the main resource being reconciled was supposed to compute its own status based on the new state of the cluster after the create/update.

@metacosm the resource version is update if you update the status sub-resource.
Its always a separate method, since its a different API call for K8S.

The best way to cover this is with retry

What I think could be tricky here is that technically the status itself could be updated with a newer event. so retrying may override the new status with the old one.

This should not be the case, since the controller should update the status only. But this is more like a convention, its not enforced. On the other hand this is why it a sub-resource. So you don't override it, when you change the resource. (End the controller eventually updates it after execution of a resource change)

@metacosm the resource version is update if you update the status sub-resource.

Are you sure? It doesn't make sense to me that the resource version would be updated when you update a sub-resource status. You're not changing the resource, just its status…

@metacosm the resource version is update if you update the status sub-resource.

Are you sure? It doesn't make sense to me that the resource version would be updated when you update a sub-resource status. You're not changing the resource, just its status…

Yes, it, does not make sense, but I remember double checking this some time ago.

The best way to cover this is with retry

What I think could be tricky here is that technically the status itself could be updated with a newer event. so retrying may override the new status with the old one.

This should not be the case, since the controller should update the status only. But this is more like a convention, its not enforced. On the other hand this is why it a sub-resource. So you don't override it, when you change the resource. (End the controller eventually updates it after execution of a resource change)

OK, so if we guide the user to update the status subresource via the controller API, then it makes sense to retry on conflicts.


App Freezes when Adding/Removing songs from the Library

OS:
Windows 10 Home, 64 Bit
Issue Descriptions:
Any time I add/remove any music from my library the app temporarily freezes and I am unable to do anything. Not sure if this is a well known issue or not but it causes issues when I attempt to add multiple albums to my library using the desktop player. (The music that had been playing will continue to play though)
Steps to Reproduce:
Go into any album and try to add to the library. There will be a slight pause for a few seconds and you will be unable to use any portion of the app.
debug_info.zip

@mlebeau11 GPM appears to trigger a rapid sequence of redraws in this situation that can freeze the application, this is a GPM issue that hopefully they will pick up and fix on their end 👍


Remove the public-url configuration option

Context
The public-url configuration option is used in this charm for setting the OIDC_PROVIDER value, but #156 is proposing a different approach for setting it, so the config option is not required anymore.
This task requires the removal of the public-url configuration option as it has been considered misleading and should not be used. Please refer to https://github.com/canonical/bundle-kubeflow/issues/608 for more information.
What needs to get done

Remove the public-url configuration option
Remove all traces of it from the charm code
Add/modify tests accordingly

Definition of Done
The option is not there anymore and the OIDC_PROVIDER value is set using relation data as suggested in #156

Fixed by #163 and #168