DASH VOD manifest with large offset at the start can't be played.  Seek doesn't work either.

Have you read the Tutorials?
Yes
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
3.0.8
Please ask your question
the link to Dash MPD is here : https://amsts11mediaarmaccpmxj-ts111.streaming.media.azure-test.net/79d49732-c63e-4506-9d53-c2dac1f5b8e7/test.ism/manifest(format=mpd-time-cmaf,starttime=2021-02-25T18:00:00.000Z,endtime=2021-02-25T18:30:00.000Z).mpd.   This could be MPD authoring issue but would like to clarify.  There is a big gap between the presentationTimeOffset and the first timestamp of first segment in the video (bigger than the duration of the manifest).
I get this weird seek time range:<PHONE_NUMBER>777778 - 1799.988 where end is less than start (since end is clamped to the duration of the manifest while start is the first timestamp - presentation offset.  So the player just stalls after loading manifest. I tried to manually seek around but that doesn't work either.  Wondering if there is a way to play such content without reauthoring the manifest.

That link isn't valid anymore.  Can you post a new URL?

There is a big gap between the presentationTimeOffset and the first timestamp of first segment in the video (bigger than the duration of the manifest).

Is this VOD?  If so, the presentationTimeOffset should be the same as the timestamp of the first segment.  VOD content must start at 0.  This is likely bad content.  You may be able to use a response filter to edit the XML before we get it and fix the presentationTimeOffset value.

Thanks. Yes this can be closed.


[WIP] Bench without changes

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 73.02%. Comparing base (89f48d4) to head (4691fe1).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #639      +/-   ##
==========================================
- Coverage   73.05%   73.02%   -0.03%
==========================================
  Files         252      252
  Lines       36093    36076      -17
==========================================
- Hits        26366    26345      -21
- Misses       9727     9731       +4

Components
Coverage Δ

crashtracker
20.53% <ø> (ø)

datadog-alloc
98.73% <ø> (ø)

data-pipeline
90.12% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
83.08% <ø> (ø)

ddcommon-ffi
69.52% <ø> (ø)

ddtelemetry
59.10% <ø> (ø)

ipc
83.63% <ø> (ø)

profiling
84.26% <ø> (ø)

profiling-ffi
77.42% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
40.12% <ø> (ø)

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
50.36% <ø> (ø)

tinybytes
91.66% <ø> (ø)

trace-mini-agent
72.49% <ø> (ø)

trace-normalization
98.25% <ø> (ø)

trace-obfuscation
95.73% <ø> (ø)

trace-protobuf
77.67% <ø> (ø)

trace-utils
93.30% <ø> (+0.41%)
:arrow_up:


"no match response" button present in qna maker dialog when active learning is disabled

JS tracking issue for repo code-owners
See original issue for details: https://github.com/microsoft/botframework-sdk/issues/6146

Investigated and it appears that this does not show up as a bug in JS.
Closing.


Not building when in release mode on Windows

I just set everything up and it builds normally with cargo 3ds build. I am using all the devkitPro stuff and LLVM on Windows. However, running cargo 3ds build --release gives this error. Not sure if this is a rustflags thing and an issue with cargo-3ds.

Compiling ctru-sys v22.2.0+2.2.2-1 (https://github.com/rust3ds/ctru-rs#4d718c41)
The following warnings were emitted during compilation:
warning<EMAIL_ADDRESS>failed to check libctru version: cannot find binary path
warning<EMAIL_ADDRESS>arm-none-eabi-gcc: error: unrecognized command-line option '-m64'
error: failed to run custom build command for ctru-sys v22.2.0+2.2.2-1 (https://github.com/rust3ds/ctru-rs#4d718c41)
Caused by:
process didn't exit successfully: C:\Users\fek\k-git\first-3ds-rust-project\target\release\build\ctru-sys-d91d501a2927c647\build-script-build (exit code: 1)
--- stdout
cargo:rerun-if-changed=build.rs
cargo:rerun-if-env-changed=DEVKITPRO
cargo:rustc-link-search=native=C:\devkitPro/libctru/lib
cargo:rustc-link-lib=static=ctru
cargo:warning=failed to check libctru version: cannot find binary path
TARGET = Some("x86_64-pc-windows-msvc")
OPT_LEVEL = Some("3")
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("false")
CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
HOST = Some("x86_64-pc-windows-msvc")
cargo:rerun-if-env-changed=CFLAGS_x86_64-pc-windows-msvc
CFLAGS_x86_64-pc-windows-msvc = None
cargo:rerun-if-env-changed=CFLAGS_x86_64_pc_windows_msvc
CFLAGS_x86_64_pc_windows_msvc = None
cargo:rerun-if-env-changed=HOST_CFLAGS
HOST_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = None
running: "C:\devkitPro\devkitARM\bin/arm-none-eabi-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-m64" "-I" "C:\devkitPro\libctru\include" "-Wall" "-Wextra" "-march=armv6k" "-mtune=mpcore" "-mfloat-abi=hard" "-mfpu=vfp" "-mtp=soft" "-Wno-deprecated-declarations" "-o" "C:\Users\fek\k-git\first-3ds-rust-project\target\release\build\ctru-sys-d4aabc400d3d9b70\out\884983ec69cfa99d-libctru_statics_wrapper.o" "-c" "C:\Users\fek\k-git\first-3ds-rust-project\target\release\build\ctru-sys-d4aabc400d3d9b70\out\libctru_statics_wrapper.c"
cargo:warning=arm-none-eabi-gcc: error: unrecognized command-line option '-m64'
exit code: 1
--- stderr
error occurred: Command "C:\devkitPro\devkitARM\bin/arm-none-eabi-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-m64" "-I" "C:\devkitPro\libctru\include" "-Wall" "-Wextra" "-march=armv6k" "-mtune=mpcore" "-mfloat-abi=hard" "-mfpu=vfp" "-mtp=soft" "-Wno-deprecated-declarations" "-o" "C:\Users\fek\k-git\first-3ds-rust-project\target\release\build\ctru-sys-d4aabc400d3d9b70\out\884983ec69cfa99d-libctru_statics_wrapper.o" "-c" "C:\Users\fek\k-git\first-3ds-rust-project\target\release\build\ctru-sys-d4aabc400d3d9b70\out\libctru_statics_wrapper.c" with args "arm-none-eabi-gcc" did not execute successfully (status code exit code: 1).

Facepalming very hard right now. Was using cargo build --release over and over. My apologies. It's 4am

Don't worry, it's fine :sweat_smile:. Happy to see you managed to set everything up.


[CST-4878] [CST-4879] [CST-4884] [CST-4947] Upload files - Edit bitstream (improvements and bug fixes)

References

Fixes #1337
Fixes #1359
Fixes #1399
Fixes #1415
Fixes DSpace/DSpace#7977 (this was actually a dspace-angular issue)

Description
The Edit bitstream form has been moved in a modal. Several bugs in the form, mostly related to the Access condition type, have been fixed.
Instructions for Reviewers
List of changes in this PR:

The Edit bitstream form (section-upload-file-edit.component) is now displayed inside a modal. Saving process is managed within the modal component.
When  Access condition type is changed the PATCH does not fail anymore.

Bug reason: when the previous access condition type had a start date or an end date and the new condition type did not have it the previously saved date was still included in the patch, although the corresponding form field was deactivated

Grant access from/until fields are now correctly deactivated

Bug reason: if no access condition type had a start date or an end date the corresponding field was not deactivated for all the access condition types
With this fix, when no access condition requires start date or end date the corresponding field is not present at all

The description can now be deleted

Checklist

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes TSLint validation using yarn run lint
[x] My PR doesn't introduce circular dependencies
[x] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[x] If my PR includes new, third-party dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.

@tdonohue
I'll check bullet #2 ASAP.
As for bullet #4, the trashcan button (which was already present) removes the whole Description fields, not its content. Assuming that at least one description field is required, this behaviour should be correct. If you add a second field, both buttons are enabled and allow to remove one of the two fields:

@davidenegretti-4science : Thanks for the reminder regarding bullet 4.  If we can simply get the TypeError resolved, then this can move forward as-is.

@tdonohue I fixed the TypeError


dbeaver/dbeaver#19677  SQL format in generate SQL

Hello @Griitaz
Thanks for the contribution.
First of all - you have an extra commit in your files.
And second - please look at the SQLFormatUtils.formatSQL method. Try to implement it instead of non-universal formatting.

What's the point of adding tabs? As for me, compact or non-compant formatting is more about new lines.
I'd rather apply the same formatter that we apply on format command in SQL Editor.

This PR is stale, so I'm closing it. Please, let me know if you'll continue working on this - we can reopen it.


bat: 0.9.0 -> 0.10.0

changelog
Things done

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

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

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

@GrahamcOfBorg build bat
Something wonky happened to the Darwin build.

Change the default configuration directory on macOS to ~/.config/bat, see #442 (@lavifb). If you are on macOS, you need to copy your configuration directory from the previous place (~/Library/Preferences/bat) to the new place (~/.config/bat).

Might be important to notify macOS users somehow?

Might be important to notify macOS users somehow?

I'd like to, but how?

I'm not really sure how, guess it's really minor so we can just ignore that :smile:
However it looks like somethings up with the darwin build. Perhaps someone can see if they can reproduce locally?

Let's try again :)
@GrahamcOfBorg build bat

FWIW I can build it on darwin https://gist.github.com/d241d55fd7b606bff977ee5fbb112d39

Thanks @marsam, I can merge this now :+1:


unexpect result when using re2 syntax regular expression in prometheus

when i query something in prometheus using regex like tihs :
sort_desc(sum by(envoy_cluster_name)sort_desc(sum by(envoy_cluster_name)(increase(envoy_cluster_upstream_rq_total{cluster_name=~"gateway-proxy-1", envoy_cluster_name=~"^[^prometheus-server].*$"}[172800s])))
i want exclude the prometheus-server cluster , and i don't want to use the operator !~
and i found that :
using expression ^[^prometheus-server].*$, it would missing some other envoy_cluster_name
using envoy_cluster_name=~".*"}

using envoy_cluster_name=~"^[^prometheus-server].*$"}

please figure out whether i am wrong  and the solutions
PS:

and RE2 syntax
https://github.com/google/re2/wiki/Syntax

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


Document/video with detailed example of how to classify an object

A document/video is needed that explains in detail how to classify a lightcurve
Feature Summary
A document with multiple examples of how to classify objects. This includes a concise description with all the actions and information used (PS1 cutout, folded lightcurve etc).
Implementation details
google doc with multiple examples; and possibly a video

If we are ready to move back to Fritz, this needs a bump up.

A video is now available at https://www.youtube.com/watch?v=e48OBo8M-p4. Additional documentation would still be helpful as well, perhaps as a new page in the docs?


Thunderbird Uninstall/Reinstall Deletes Default Profile

I don't see how the changes in https://github.com/caskroom/homebrew-cask/pull/29937 would cause this, but I uninstalled Thunderbird then re-installed this morning to get on the new version.  After the install, I noticed Thunderbird was using a brand new default configuration.  I had to use Time Machine to pull my config from the day before.  This has never happened before upon uninstall/reinstall of TB.  Anyone else experience this?

Unless you uninstalled with zap, it’s unlikely the culprit was HBC.

@vitorgalvao Always quick to close issues I notice.
I uninstalled using brew cask uninstall --force thunderbird
I believe that is the same as using zap and I'm sure you'll let me know one way or another.
HOWEVER, this is always how I have upgraded Thunderbird but this is the first time my default profile was outright deleted.  And not on one machine, but others as well.
I'm not saying it HBC... or the script.  Just curious why this particular update deleted the profile and if anyone else has experienced this.
If it's the new norm with the TB updates, then I'd like to be better prepared before upgrading in the future.

@vitorgalvao Always quick to close issues I notice.

I am when they’re unlikely to be related to us, yes. There’s no point in keeping them open, and I frankly don’t comprehend the others projects who just leave unrelated and old issues open indefinitely. They become untenable, maintainers burnout, and the projects are abandoned.
HBC was already close to such a state, being proficient in closing issues as they’re no longer relevant makes sure a project doesn’t stagnate. We’re not tech support. If it isn’t related to us, there’s no obligation to spend resources fixing. That’s even detrimental, I’d say.
Closing does not mean the conversation is over. I can just as easy reopen the issue

I uninstalled using brew cask uninstall --force thunderbird
I believe that is the same as using zap and I'm sure you'll let me know one way or another.

No, it is not the same.

HOWEVER, this is always how I have upgraded Thunderbird but this is the first time my default profile was outright deleted. And not on one machine, but others as well.
I'm not saying it HBC... or the script. Just curious why this particular update deleted the profile

Since the only thing we do is remove the app, that’s a question for the thunderbird team, not us.

and if anyone else has experienced this.

They haven’t. We have no other reports of this.

If it's the new norm with the TB updates, then I'd like to be better prepared before upgrading in the future.

And again, that’s a question for them, not us. We have no control over how they manage their software.


ci(linux): add Ubuntu 24.04 as a runner for some Rust tests

Refs #4883, looks like an issue that Tauri will fix upstream.


Add MIT License

Ground rules:

Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
Pull Requests sent without claiming and referencing the Issue will not be entertained.
Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

I got this one. Pull request incoming.

Merged! Good work @ryanwake . Welcome to the Open-Source community!


libethcore.so when running tokenminer

What OS version is that?

Ubuntu 16.04
On Fri, Mar 23, 2018 at 2:09 PM, Mining Visualizer<EMAIL_ADDRESS>
wrote:

What OS version is that?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mining-visualizer/MVis-tokenminer/issues/5#issuecomment-375555111,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AiMhSvxkS1p2gVRZ3PiIweZgM46LEQpkks5thJGegaJpZM4S4NbF
.

It looks like I need to ship those dependencies with the executable.  I had assumed everything was statically linked at compile time, like it does under Windows.  Should have a new download package shortly.

v2.1.5 is now available, which hopefully will address this issue.  Please try it out and let me know the results.

i still got the same error message not sure why... cant find libethcore.so
and i ran all the commands in INSTALL-LINUX as well
On Sat, Mar 24, 2018 at 7:29 AM, Mining Visualizer<EMAIL_ADDRESS>
wrote:

v2.1.5 is now available, which hopefully will address this issue. Please
try it out and let me know the results.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mining-visualizer/MVis-tokenminer/issues/5#issuecomment-375824442,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AiMhSrJ0sa--g7FngGrahoIpJxE3jwsyks5thYVygaJpZM4S4NbF
.

so and i ran all the commands in INSTALL-LINUX as well

Yeah, that was the idea.  I forgot to mention it.  I assume it worked then?

no sorry, didnt finish my sentence before sending the email lol.
I still get the same exact error complaining libethcore.
On Sat, Mar 24, 2018 at 10:21 AM, Mining Visualizer <
<EMAIL_ADDRESS>wrote:

so and i ran all the commands in INSTALL-LINUX as well
Yeah, that was the idea. I forgot to mention it. I assume it worked then?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mining-visualizer/MVis-tokenminer/issues/5#issuecomment-375839829,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AiMhSrSYh4yjxzoq9YLWeYccBq7eWgeeks5tha2agaJpZM4S4NbF
.

Well, for now I think I'm just going to recommend building from source.  With the instructions you followed in INSTALL-LINUX, you're 80% there already.

i built it from source... you'll want to  update your instructions:
You can then find the executable in the build/tokenminer subfolder
its actually in the ethminer folder
On Sat, Mar 24, 2018 at 1:31 PM, Mining Visualizer<EMAIL_ADDRESS>
wrote:

Well, for now I think I'm just going to recommend building from source.
With the instructions you followed in INSTALL-LINUX, you're 80% there
already.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mining-visualizer/MVis-tokenminer/issues/5#issuecomment-375848496,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AiMhSuEeDRWqzmaFjZcmw64JtwxqpRQcks5thdpGgaJpZM4S4NbF
.

Done.


Added the shares_float and shares_float/all API

Hello Everyone,
I've added the shares-float and shares-float/all
as available endpoints.
Since this is my first contribution to Open-Source please let me know,
if i messed something up :)

I think instead of having two methods, it should be a single method. Make the "all" as an optional boolean attribute that defaults to faults. What do you think?

That would certainly a way to do that while reducing the total amounts of endpoints.
I will get to that in the next couple of days :)


Customization variables in custom.el are overwritten

The work in #112 introduced a bug that overwrites the customization variables saved to custom.el by the Customizaiton UI. Further,
The rational-load-custom-file function documentation (quoted below),

Load the custom-file after saving customized values. Customized values set during the initialization process are saved, other values set through the Customization UI or via certain workflows are not lost in this process. The custom-file is loaded last.

implies that the variables customized by early-init.el and init.el are saved to custom.el, which does not appear to be the case. The function (customize-save-customized) eventually calls custom-save-delete before reinserting the form into custom.el. As the values are customized outside of custom, they are not saved and are in fact deleted, along with any values set and saved into custom.el by the Customization UI, as this deletion of the saved contents of custom.el occurs every initialization, exactly when we are trying to load previously customized variables.
I haven't understood why, but my incoming refactor does allow the customizations set outside of custom by early-init.el and init.el to persist in custom-file, along with customizations applied with the UI. As far am able to understand, the culprit is custom-save-customized calling custom-save-delete eventually.
I read most of the discussion around customization, and I'm in agreement with most things. One thing, however, is that I don't think we need a dedicated function to load the custom file. In my refactor I inlined the function into a lambda in the load call.
Using Rational has made me learn more about Emacs, mostly Customization UI ironically, even though the project isn't urging people to use it. I ended up using it a decent bit because it was a nice way to explore the Rational customization group without focusing on implementation; it was also how I learned to customize the fringe face, which I protected in code in my config.el until I wrote the refactor and fixed the regression.
🤷🏼 I'm not sure what Rational is going to do going forward, but I'm fairly sure I've fixed this.

I tested several ways to make sure that didn't happen ... bummer ! (facepalm!!)
custom-save-delete only deletes the values out of the buffer. It depends on them already being set beforehand. If they aren't, then they disappear, which is not intended (aka "bad"). Ultimately, we don't really need to call customize-save-customized at all, that was an attempt to get the currently customized values set during initialization stored in the custom-set-variables form. Your refactor works because it doesn't save the customized values (which is fine, they are in the "SET but not saved" state), and then we load the values set through the Customize UI, via Org Mode Agenda file manipulation, and/or from  .dir-locals.el settings (ie, pressing the ! to accept and remember the settings (see discussion in #111). In the end, all we need to do is remove the call to customize-save-customized and add your better wording in the README.org.
We don't technically need to load the file in the after-init-hook, but that seemed like a reasonable place to put it so a user could choose to remove that from the hook if they don't want the custom-file loaded at all. The only (minor/nit picky) issue I have with your refactor is the use of lambda in the after-init-hook which makes it difficult to undo later.
Would you mind updating your PR to only remove the call to customized-save-customized? (I've added some review notes)
Thanks very much, great catch!


Fixed code sample for authentication headers

Docs only

Could you modify to use the setContext link? https://www.apollographql.com/docs/link/links/context.html

Sure, wasn’t aware of that one yet. Will update later today.

@stubailo I have updated the code to use apollo-link-context, but as I have not used it before, please double check to make sure this is the correct way to use it.

Thank you!


Thanks, thoughts?

Hi Mark,
Thank you for providing drykup, I enjoy the straight forward implementation.  I was wondering if you have been using it much and if so what is your experience with it?  Did you go back to CoffeeCup for any reason?
Thanks,
Zoz
(I put this as a issue because your github messaging is disabled, i hope you don't mind)

Yes I have been using it every day since I wrote it.  I have an app about
to go into beta that uses only drykup.  I probably have a few thousand
lines of it.
When I wrote it I was worried about the need to declare all the tags, but
that has turned out to be no problem at all.  I declare the needed tags at
the top of each module, and it is surprising how few are needed.
The version I'm using has been patched without the github version being
updated, although there have been no bugs.  I didn't think there was any
interest in drykup so I haven't taken the trouble to maintain the repo
properly.
I'm thinking of doing a new version that doesn't even generate HTML but
adds the tags directly to the dom.  I read a great article about how that
is faster than generating the html text first.
http://blog.fastmail.fm/2012/02/20/building-the-new-ajax-mail-ui-part-2-better-than-templates-building-highly-dynamic-web-pages/
This would be a good fit for me because my pages are loaded mostly empty
and then generate html as it is needed.  I would still need to maintain the
current version because I still generate some html on the server.
And of course I also have a lot of wild feature ideas for the new version.
The wildest one is to include the functionality of knockout.  Knockout
bindings are specified in the dom and there is a great opportunity to do
knockout in a more elegant way.
On Fri, Mar 9, 2012 at 9:42 AM, Zoz <
<EMAIL_ADDRESS>wrote:

Hi Mark,
Thank you for providing drykup, I enjoy the straight forward
implementation.  I was wondering if you have been using it much and if so
what is your experience with it?  Did you go back to CoffeeCup for any
reason?
Thanks,
Zoz
(I put this as a issue because your github messaging is disabled, i hope
you don't mind)

Reply to this email directly or view it on GitHub:
https://github.com/mark-hahn/drykup/issues/1

Awesome, I like it!  Thanks for the quick feedback.  I have been doing a similar approach with a library I wrote.  But now that I found drykup I will use your code instead.
Declaring the tags at top is no problem for me too.  I really like how easy it is to extend drykup:
js = (srcname) ->
  drykup.normalTag 'script', [ type:'text/javascript', src:"#{srcname}", '' ]

If I come up with any cool changes or additions I will let you know.
Thanks!
Zoz


[QUESTION] Interface 'Maatwebsite\Excel\Concerns\FromView' not found

PHP version: 7.0
Laravel version: 5.5.39
Package version: 2.1

I tried exporting data from views to excel but I got the errors Interface 'Maatwebsite\Excel\Concerns\FromView' not found

It seems you're using a version of Laravel Excel which is no longer supported. You're strongly advised to upgrade to the latest version (3.1 at this time).

It seems you're using a version of Laravel Excel which is no longer supported. You're strongly advised to upgrade to the latest version (3.1 at this time).

Saved my life! Thank you!


feat(firebase_analytics, ios): add onDeviceConversionMeasurement

Description
This PR adds the onDeviceConversionMeasurement function for ios which is needed for an increased volume and precision of conversion tracking.
I followed as example @mikehardy's implementation of the feature in React Native and @Lyokone's implementation of Pigeon.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Just dropping by for a moment since I saw my tag here 👋  - wanted to note that there is a phone API as well with firebase-ios-sdk 10.13.0+
https://github.com/invertase/react-native-firebase/pull/7358
Same basic pattern, might make sense to get them both in at once

@Lyokone All your recommendations were implemented and I left a comment on your concern about its functioning.
All things considered we should be good to go, right?
P.S: I'll eventually add the equivalent of this implementation for phone numbers in a separate PR but I can't promise it will be soon, so I would rather go only with this one for now.

P.S: I'll eventually add the equivalent of this implementation for phone numbers in a separate PR but I can't promise it will be soon, so I would rather go only with this one for now.

Sure - did not mean to imply any sort of pressure, just wanted to mention it since whenever this PR makes it through review, using whatever code looks good, the other API should be doing exactly the same thing, so it's potentially a really really quick hit that re-uses all the kind-of-ephemeral wisdom built up on how to do the PR and review it etc.
But no one has endless time of course, I certainly feel that! Cheers

Ohhh I get what you meant now, thanks!!!

@Lyokone Just checking back on this one, is there anything missing for it to be ready? 😄

@lucasuracosta Thanks for your contribution, we ended going another way with the API (initiateOnDeviceConversionMeasurementWithEmailAddress) and it's available in the Analytics plugin now :)


use faster typed arrays for monkeyIndexArray allocation

TypedArrays are anywhere from 10+times faster
Benchmark.
typed array: 16
normal array: 164
ops/s
https://esbench.com/bench/57c1f350db965b9a00965c94

Hey, awesome! You're correct, I completely ignored that option. It is much faster on my tests too. monkeyIndexArray is a hacky mess, I wonder if there is a cheaper way to do it... something like gl_VectorID?
Thank you!


Training on FaceForensics

Hi!
I am currently working on using the code for the FaceForensics dataset. I have been able to train VQGAN, but I encountered an issue while training the TATS-base Transformer. Here is the command I am using for training:
python scripts/train_transformer.py --num_workers 32 --val_check_interval 0.5 --progress_bar_refresh_rate 500 \
                        --gpus 4 --sync_batchnorm --batch_size 2 --unconditional \
                        --vqvae exp_1/lightning_logs/version_78873/checkpoints/latest_checkpoint.ckpt \
                        --data_path data/ffs_processed --default_root_dir exp_1_tats --image_folder \
                        --vocab_size 16384 --block_size 1024 --n_layer 24 --n_head 16 --n_embd 1024  \
                        --resolution 256 --sequence_length 16 --max_steps 2000000

However, I got an error:
Traceback (most recent call last):
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/train_transformer.py", line 77, in
main()
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/train_transformer.py", line 73, in main
trainer.fit(model, data)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 737, in fit
self._call_and_handle_interrupt(
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 682, in _call_and_handle_interrupt
return trainer_fn(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 772, in _fit_impl
self._run(model, ckpt_path=ckpt_path)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1195, in _run
self._dispatch()
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1274, in _dispatch
self.training_type_plugin.start_training(self)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/plugins/training_type/training_type_plugin.py", line 202, in start_training
self._results = trainer.run_stage()
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1284, in run_stage
return self._run_train()
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1306, in _run_train
self._run_sanity_check(self.lightning_module)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1370, in _run_sanity_check
self._evaluation_loop.run()
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/base.py", line 145, in run
self.advance(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/dataloader/evaluation_loop.py", line 109, in advance
dl_outputs = self.epoch_loop.run(dataloader, dataloader_idx, dl_max_batches, self.num_dataloaders)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/base.py", line 145, in run
self.advance(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/epoch/evaluation_epoch_loop.py", line 122, in advance
output = self._evaluation_step(batch, batch_idx, dataloader_idx)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/epoch/evaluation_epoch_loop.py", line 217, in _evaluation_step
output = self.trainer.accelerator.validation_step(step_kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py", line 236, in validation_step
return self.training_type_plugin.validation_step(*step_kwargs.values())
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/plugins/training_type/ddp.py", line 444, in validation_step
return self.model(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/parallel/distributed.py", line 1008, in forward
output = self._run_ddp_forward(*inputs, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/parallel/distributed.py", line 969, in _run_ddp_forward
return module_to_run(*inputs[0], **kwargs[0])
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/overrides/base.py", line 92, in forward
output = self.module.validation_step(*inputs, **kwargs)
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/../tats/tats_transformer.py", line 250, in validation_step
loss, acc1, acc5 = self.shared_step(batch, batch_idx)
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/../tats/tats_transformer.py", line 237, in shared_step
logits, target = self(x, c, cbox)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/../tats/tats_transformer.py", line 126, in forward
logits, _ = self.transformer(cz_indices[:, :-1], cbox=cbox)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/../tats/modules/gpt.py", line 208, in forward
assert t <= self.block_size, "Cannot forward, model block size is exhausted."
AssertionError: Cannot forward, model block size is exhausted.
where t=4096 and self.block_size=1024. When I tried to increase the block_size argument to 4096, I received another error message (even with a batch_size of 1):
Traceback (most recent call last):
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/train_transformer.py", line 77, in
main()
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/train_transformer.py", line 73, in main
trainer.fit(model, data)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 737, in fit
self._call_and_handle_interrupt(
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 682, in _call_and_handle_interrupt
return trainer_fn(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 772, in _fit_impl
self._run(model, ckpt_path=ckpt_path)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1195, in _run
self._dispatch()
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1274, in _dispatch
self.training_type_plugin.start_training(self)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/plugins/training_type/training_type_plugin.py", line 202, in start_training
self._results = trainer.run_stage()
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1284, in run_stage
return self._run_train()
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1314, in _run_train
self.fit_loop.run()
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/base.py", line 145, in run
self.advance(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/fit_loop.py", line 234, in advance
self.epoch_loop.run(data_fetcher)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/base.py", line 145, in run
self.advance(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/epoch/training_epoch_loop.py", line 193, in advance
batch_output = self.batch_loop.run(batch, batch_idx)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/base.py", line 145, in run
self.advance(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/batch/training_batch_loop.py", line 88, in advance
outputs = self.optimizer_loop.run(split_batch, optimizers, batch_idx)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/base.py", line 145, in run
self.advance(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 215, in advance
result = self._run_optimization(
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 266, in _run_optimization
self._optimizer_step(optimizer, opt_idx, batch_idx, closure)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 378, in _optimizer_step
lightning_module.optimizer_step(
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/core/lightning.py", line 1651, in optimizer_step
optimizer.step(closure=optimizer_closure)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/core/optimizer.py", line 164, in step
trainer.accelerator.optimizer_step(self._optimizer, self._optimizer_idx, closure, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py", line 336, in optimizer_step
self.precision_plugin.optimizer_step(model, optimizer, opt_idx, closure, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/plugins/precision/precision_plugin.py", line 163, in optimizer_step
optimizer.step(closure=closure, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/optim/optimizer.py", line 113, in wrapper
return func(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/optim/adamw.py", line 119, in step
loss = closure()
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/plugins/precision/precision_plugin.py", line 148, in _wrap_closure
closure_result = closure()
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 160, in call
self._result = self.closure(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 142, in closure
step_output = self._step_fn()
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/loops/optimization/optimizer_loop.py", line 435, in _training_step
training_step_output = self.trainer.accelerator.training_step(step_kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py", line 216, in training_step
return self.training_type_plugin.training_step(*step_kwargs.values())
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/plugins/training_type/ddp.py", line 439, in training_step
return self.model(*args, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/parallel/distributed.py", line 1008, in forward
output = self._run_ddp_forward(*inputs, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/parallel/distributed.py", line 969, in _run_ddp_forward
return module_to_run(*inputs[0], **kwargs[0])
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/pytorch_lightning/overrides/base.py", line 81, in forward
output = self.module.training_step(*inputs, **kwargs)
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/../tats/tats_transformer.py", line 243, in training_step
loss, acc1, acc5 = self.shared_step(batch, batch_idx)
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/../tats/tats_transformer.py", line 237, in shared_step
logits, target = self(x, c, cbox)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/../tats/tats_transformer.py", line 126, in forward
logits, _ = self.transformer(cz_indices[:, :-1], cbox=cbox)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/../tats/modules/gpt.py", line 218, in forward
x = self.blocks(x)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/modules/container.py", line 139, in forward
input = module(input)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/../tats/modules/gpt.py", line 153, in forward
attn, present = self.attn(self.ln1(x), layer_past=layer_past)
File "/home/pkomor/anaconda3/envs/tats/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/lu/tetyda/home/pkomor/Projects/VidGen/TATS/scripts/../tats/modules/gpt.py", line 121, in forward
att = (q @ k.transpose(-2, -1)) * (1.0 / math.sqrt(k.size(-1)))
RuntimeError: CUDA out of memory. Tried to allocate 1024.00 MiB (GPU 1; 31.74 GiB total capacity; 29.71 GiB already allocated; 45.12 MiB free; 30.61 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
Can you suggest any potential solutions that might work?

If you are using the default hyperparameter to train the VQGAN, then it looks like you trained on 256x256 resolution, which results in a latent size of (4, 32, 32) and block size of 4096. It means the sequence to be modeled by the transformer has a length of 4096 which cannot feed into the memory. You have several options:

Use a smaller resolution of 128x128.
Use a larger compression rate by setting --downsample 4 16 16. This may make the reconstruction quality of VQGAN bad, though.
Use a smaller transformer.

Thank you, it working now! I have another question regarding training. My data is structured in a way where there are 704 folders (videos), each containing some number of images (frames). To train vqgan, I'm using the --image_folder flag. However, I've noticed that the training progress output is a bit strange. For example, when using --batch_size 2, the output shows:
Validating: 100%|██████████| 88/88 [01:13<00:00,  1.19it/s]
Epoch 1: 100%|██████████| 176/176 [07:06<00:00,  2.42s/it, loss=1.11, v_num=78873, train/perceptual_loss_step=1.700, train/recon_loss_step=0.278, train/aeloss_step=0.000, train/commitment_loss_step=0.00433, train/perplexity_step=53.50, train/discloss_step=0.000, val/recon_loss=0.446, val/perceptual_loss=1.690, val/perplexity=53.40, val/commitment_loss=0.0475, train/perceptual_loss_epoch=2.640, train/recon_loss_epoch=0.665, train/aeloss_epoch=0.000, train/commitment_loss_epoch=0.012, train/perplexity_epoch=68.70, train/discloss_epoch=0.000]

However, I expected the training progress to show twice as many iterations (176 -> 352), to cover the entire batch in one epoch. Similarly, when using --batch_size 1, I'm getting
Validating: 100%|██████████| 176/176 [01:27<00:00,  2.01it/s]
Epoch 1: 100%|██████████| 352/352 [10:10<00:00,  1.73s/it, loss=1.26, v_num=79006, train/perceptual_loss_step=1.750, train/recon_loss_step=0.384, train/aeloss_step=0.000, train/commitment_loss_step=0.0054, train/perplexity_step=50.50, train/discloss_step=0.000, val/recon_loss=0.520, val/perceptual_loss=1.950, val/perplexity=40.20, val/commitment_loss=0.253]

I couldn't find the reason for this in the code. Do you have any insights on why this might be happening?

Could it be that you are training on multiple gpus, e.g. 2?


[Load/Store] Very slow

Hi
When i made benchmark on std::like algorithm (see #107 and #115) i felt onto surprising behavior
std::transform algorithm is faster than simd counterpart
WTF i said on my desk
I profiled the code and suspects are generalized load/store functions
I made a dedicated benchmark suite on them
And yes, load/store seems to be slow
On avx2 architecture, Ubuntu 5.4.0-6ubuntu1~16.04.9 g++ 5.4.0
i compare c++ for loop and simd like for loop
`
for (size_t i = 0; i < size; ++i)
{
*ptrout++=*ptrin++;
}
Versus
for (size_t i = 0; i < size; i += simd_size)
{
simd_type_T element = simdpp::load(ptrin);
simdpp::store(ptrout, element);
ptrin += simd_size;
ptrout += simd_size;
}
Results for uint8_t and various size
LoadStoreFixture<uint8_t>/UnaryUNINT8_SIMD_Test/64                   72 ns         72 ns    9921739
LoadStoreFixture<uint8_t>/UnaryUNINT8_SIMD_Test/128                 146 ns        146 ns    4629647
LoadStoreFixture<uint8_t>/UnaryUNINT8_SIMD_Test/256                 288 ns        288 ns    2460696
LoadStoreFixture<uint8_t>/UnaryUNINT8_SIMD_Test/512                 573 ns        573 ns    1200729
LoadStoreFixture<uint8_t>/UnaryUNINT8_SIMD_Test/1024               1116 ns       1116 ns     634524
LoadStoreFixture<uint8_t>/UnaryUNINT8_STD_Test/64                    30 ns         30 ns   23157949
LoadStoreFixture<uint8_t>/UnaryUNINT8_STD_Test/128                   56 ns         56 ns   12685794
LoadStoreFixture<uint8_t>/UnaryUNINT8_STD_Test/256                  104 ns        104 ns    6773528
LoadStoreFixture<uint8_t>/UnaryUNINT8_STD_Test/512                  205 ns        205 ns    3477179
LoadStoreFixture<uint8_t>/UnaryUNINT8_STD_Test/1024                 393 ns        393 ns    1775957
`
As you could see loading/storing through simd is 3 times slower than basic for loop and its peanlize all std::like algorithm
I reproduce this behavior on msvc2017
May i made a mistake on compilation flags ?
How i can go further?
Regards
TR

Hey, thanks for the bug report. Could you share minimal reproduction case? I haven't seen any performance issues on GCC, so it's really interesting why you get poor performance.

Hi
I hope the problem is between my chair and my keyboard
But anyway if you have little time to investigate this with me, i really appreciate
I think the simpler is to use the benchmark i add on my fork
So clone https://github.com/ThomasRetornaz/libsimdpp.git

Enable  the benchmark
(in build directory somewhere)
cmake -DENABLE_BENCH=ON path_to_src
This will download and compile googlebenchmark

Compile one possible target in (build_directory)/bench/insn let say make bench_insn_-x86_avx

You could launch the whole bench_suite or select only load_store test

(build_directory)/bench/insn$ ./bench_insn_-x86_avx --benchmark_filter=.*LoadStore.*

the code involved is here https://github.com/ThomasRetornaz/libsimdpp/blob/dev/bench/insn/load_store.cc

May i make mistake using cmake and compilation flags here

https://github.com/ThomasRetornaz/libsimdpp/blob/dev/bench/insn/CMakeLists.txt#L16
or missuse google benchamrk in any manner

Thanks for your help
Regards
TR


Process killed when running generic_utils.make_batches

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
2.10.0
Custom Code
Yes
OS Platform and Distribution
Ubuntu 22.04
Mobile device
No response
Python version
3.9
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Probably due to very large input argument.

Standalone code to reproduce the issue
import tensorflow as tf
import os
import numpy as np
from tensorflow.python.keras.utils import generic_utils
try:
  arg_0 =<PHONE_NUMBER>51
  arg_1 = 512
  out = generic_utils.make_batches(arg_0,arg_1,)
except Exception as e:
  print("Error:"+str(e))

### Relevant log output

_No response_</details>

Hi @nimashiri !
Thanks for sharing your observation on make_batches from generic_utils.
@SuryanarayanaY  !
Could you look at this issue. Attached gist in 2.10,,  2.11 and nightly for reference.
Thank you!

Hi @nimashiri ,
I have checked the logs and there i couldn't found any Error related to crash.

The crash is probably due to High Memory requirement due to higher input argument.This is due to trying to allocate Higher Memory required for the Input and couldn't find enough leading to crash.Please refer to Developer comment related to an issue with similar behaviour.AFAIK this is expected behaviour.Changing the arg_0 to lower value works fine anyway as per attached gist.
Thankyou!

Hi @nimashiri ,
I have checked the logs and there i couldn't found any Error related to crash.

The crash is probably due to High Memory requirement due to higher input argument.This is due to trying to allocate Higher Memory required for the Input and couldn't find enough leading to crash.Please refer to Developer comment related to an issue with similar behaviour.AFAIK this is expected behaviour.Changing the arg_0 to lower value works fine anyway as per attached gist.
Thankyou!

Thanks for the reply, so in this case, I do not report issues related to killed processes if input arguments are large.

@nimashiri ,
I will let you know on it once we got confirmation from the Developer Team.Till then the issue will remain open. Thanks!


Clean up Native Client specific code

After we finally switch to WebAssembly everywhere, we should delete all legacy NaCl-related code.

We use the https://github.com/GoogleChromeLabs/chromeos_smart_card_connector/blob/main/third_party/pcsc-lite/naclport/js_client/src/api.js in our app, since it is in the naclport folder, will this still work?

We use the https://github.com/GoogleChromeLabs/chromeos_smart_card_connector/blob/main/third_party/pcsc-lite/naclport/js_client/src/api.js in our app, since it is in the naclport folder, will this still work?

Yes - I'm going to rename the folder to avoid confusion.

As a status update, we're doing with deleting the "really" NaCl-specific code: #1206, #1207, #1208, #1209, #1210, #1216.

Copying the description from #1220 here for visibility: the third_party/pcsc-lite/naclport/server_clients_management/src/known_client_apps.json file has been moved to smart_card_connector_app/src/trusted_clients.json. It's a cosmetic change.

The second train of PRs went in, renaming the files/dirs that are still used post-NaCl: #1220, #1224, #1225.

The only remaining thing is to modernize the C++ code in places where we were previously held back by NaCl toolchain level of support (which was an incomplete C++11).

The cleanup finished with these PRs: #1213, #1227, #1228.


chore: bdd-nh-import-1583169770 to 0.0.1

chore: Promote bdd-nh-import-1583169770 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Added Support for subscription Values (parameters)

Quick improvement.
Also fix some curly bracket position.

@ClaudioESSilva,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


no CUDA-capable device is detected

Hi,
I've been looking through the similar question before and did what was suggested and still didn't solve the issue. here are the steps I've followed:

installed torch from scratch:
git clone https://github.com/torch/distro.git /data/mulga/oanuru/torch --recursive
cd torch
./install.sh
source ~/.bashrc

downloaded cuDNN 5.1 for CUDA 7.5 from website
export LD_LIBRARY_PATH=<path_to_cuda>:$LD_LIBRARY_PATH

3)luarocks install cutorch
luarocks install cudnn
luarocks install cunn
I had no error for these, but when I run: luajit -l libcutorch
THCudaCheck FAIL file=/data/whip/oanuru/torch/extra/cutorch/lib/THC/THCGeneral.c line=108 error=38 : no CUDA-capable device is detected
Any idea how to solve this? Thanks!

what's the output of installing cutorch
what's the output of nvidia-smi

luarocks install cutorch gave no error. here is last part of the logs:
cd build
Updating manifest for /data/mulga/oana/torch/install/lib/luarocks/rocks
cutorch scm-1 is now built and installed in /data/mulga/oana/torch/install/ (license: BSD)
I have 7 GPUs I can see with nvidia-smi
+------------------------------------------------------+
| NVIDIA-SMI 361.42     Driver Version: 361.42         |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX TIT...  On   | 0000:04:00.0     Off |                  N/A |
| 22%   39C    P8    16W / 250W |     23MiB / 12287MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX TIT...  On   | 0000:05:00.0     Off |                  N/A |
| 22%   37C    P8    16W / 250W |     23MiB / 12287MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX TIT...  On   | 0000:08:00.0     Off |                  N/A |
| 23%   63C    P2   101W / 250W |  11240MiB / 12287MiB |     64%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX TIT...  On   | 0000:09:00.0     Off |                  N/A |
| 30%   70C    P2    98W / 250W |  12012MiB / 12287MiB |     59%      Default |
+-------------------------------+----------------------+----------------------+
|   4  GeForce GTX TIT...  On   | 0000:85:00.0     Off |                  N/A |
| 28%   67C    P2    98W / 250W |  11240MiB / 12287MiB |     35%      Default |
+-------------------------------+----------------------+----------------------+
|   5  GeForce GTX TIT...  On   | 0000:89:00.0     Off |                  N/A |
| 28%   68C    P2   125W / 250W |  11240MiB / 12287MiB |     70%      Default |
+-------------------------------+----------------------+----------------------+
|   6  GeForce GTX TIT...  On   | 0000:8A:00.0     Off |                  N/A |
| 29%   70C    P2   115W / 250W |  11240MiB / 12287MiB |     36%      Default |
+-------------------------------+----------------------+----------------------+

Sorry, my bad, didn't put the CUDA_VISIBLE_DEVICES ups


for translate into french and korean

I want to translete your projects into french and korean for my new project please

Hi, this is a very old fork and has conflicts.

ok thanks bye


Clear -p command does not remove the attendee from the events

Description
Clear -p command does not remove the attendee from the events
Steps to Reproduce

Clear -p

Expected Behavior
The attendee list in events should be cleared.

User may not want to clear the events, so we should just loop through all events and set the attendee list to a new attendee list


Adds codecov

See report here: https://codecov.io/github/theastropath/turbot/commit/b5f5a02aa9069f4baddf3d3b63b1eabbd0f52a9d

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@894764a). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #66   +/-   ##
=========================================
  Coverage          ?   89.93%
=========================================
  Files             ?        1
  Lines             ?      626
  Branches          ?      115
=========================================
  Hits              ?      563
  Misses            ?       56
  Partials          ?        7

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 894764a...7463e56. Read the comment docs.


Optional Claim Configuration references non-existent menu option

Optional Claim Configuration has a section about adding Optional Claims, however, Management -> Token Configuration is an Azure AD option, not an Azure AD B2C Option, and is not available.
See: https://github.com/MicrosoftDocs/azure-docs/issues/65511

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

ID: bac6db2d-bff9-cbcf-d522-966ed17ea27f
Version Independent ID: 91e3eeb7-8602-9e26-21c3-1fa70d03a354
Content: Set up sign-in for an Azure AD organization - Azure AD B2C
Content Source: articles/active-directory-b2c/identity-provider-azure-ad-single-tenant.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@PhilEmpyrean
Thanks for your feedback! We will investigate and update as appropriate.

@PhilEmpyrean
Thank you for your feedback and patience. Configuring optional claims procedure happens in Azure AD, so you must ensure that you're using the directory that contains your Azure AD (and not Azure AD B2C). We've updated our documentation for clarity. Note that our updates may take some time before they go live. Let us know if you've further questions. We'll proceed to close this issue. #please-close


Runtime: silence some warnings

Silence warnings about deleted defaulted constructors due to the
non-trivial constructor for the atomic type.  Guard a conditionally used
function with the appropriate guard.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @mikeash @gparker42

@swift-ci please test and merge

@swift-ci please test and merge

@swift-ci please test and merge

@swift-ci please test Linux platform

Build failed
Swift Test Linux Platform
Git Sha - 272d570c2a0f6f3b073d2eb907cf9ab72e011345

@swift-ci please clean test Linux platform

Build failed
Swift Test Linux Platform
Git Sha - 1ed7874596e6293bb6c0bd7a5d3052fffc23baf9

Please test with following PR:
https://github.com/apple/swift-corelibs-foundation/pull/1753
https://github.com/apple/swift/pull/20329
@swift-ci please test Linux platform


Bucket size keeps increasing (although it did not rain much), and duration was always 0 for a week now

What happened?
So i am testing this integration for a week now, i can say that i am a bit disappointed. I have configured everything exactly as on “Senbei Tristan’s Smartes Heim” german video (with my own wetter station data), although we did not get a lot of rain recently, my bucket keeps increasing every day, and i haven’t seen any positive duration value till now, it keeps 0s.
Most concrete example, the bucket was calculated yesterday night as 6.4mm, and today we had a partly sunny day, more or less 20 degree Celcius, with in total 0.1mm rainrate, my bucket has just been calculated again as 7.0mm. How can it be?
It does not make sense at all.
I also have a soil moisture sensor, it is working as expected and the soil humidity has been decreased today by 10% for example. But the calculation result of this integration does not work for me, don’t know why.
Thank you for your time in advance!!!
How to reproduce
Here is my diagnostic file:
config_entry-smart_irrigation-3d06ed1bcc695c1880eefeb9b105d4d5-3.json
Here is some of my current data from my weather station:

Daily Rain rate graph for the last 7 days:

Temperatur graph for the last days (mostly sunny and between 20-25 degree C):

General tab of the configuration:

I have 1 zone:

Modules tab of the config:

My Ecowitt sensor group:

Relevant log output
No response
Which version are you running?
v2024.4.3
Diagnostics file

[X] I have attached a diagnostics file

Additional information
No response

Please open you own issue instead of piling on to another.
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Themesl @.>
Sent: Sunday, May 26, 2024 10:29:21 AM
To: jeroenterheerdt/HAsmartirrigation @.>
Cc: Assign @.>; Subscribed @.>
Subject: Re: [jeroenterheerdt/HAsmartirrigation] Bucket size keeps increasing (although it did not rain much), and duration was always 0 for a week now (Issue #381)
I have the same problem.
My bucket keeps increasing every day.
However, I entered a fixed value of 0 in the total precipitation sensor setting because it is a greenhouse.
image.png (view on web)https://github.com/jeroenterheerdt/HAsmartirrigation/assets/153023191/b654d97c-3afd-4ca0-b619-86d66a61bd67
—
Reply to this email directly, view it on GitHubhttps://github.com/jeroenterheerdt/HAsmartirrigation/issues/381#issuecomment-2132293551 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB6PIPUS7MEGE4YK7B22P53ZEILXFBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZDANJTHA4TIMJXG6SG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJSGYZTCNZZGE3TNAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDEMZRG43TKMJZGYYYFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZDANJTHA4TIMJXG6TXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you were assigned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I just wanted to inform that the problem continues and can be also seen from the todays values, it may help for the analyse.
Todays rain rate was 0mm:

Humidity:

It was mostly a sunny day:

without much wind:

Temperature:

And my bucket was 7.0mm yesterday, now 6.5mm. So i strangely still do not have to irrigate:

OK, so multiple things here : you are using a 3 day forecast. So of course you can't then look at a days weather and go why did my bucket respond weirdly? Turn off the forecast for now. Also, there is a bug with don't estimate that I am working on to fix. It basically ignores the value from your solrad sensor. Also increase your auto update frequency.
All of those things (two things you can do and one thing that is a bug) should help you get to grips with how this integration works and get better results.

So today's calculation is doing perfectly. A bucket decrease of this size is in line with what is expected for this type of weather. How the bucket was so high is likely due to what is wrote above.
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: akcasoy @.>
Sent: Sunday, May 26, 2024 2:42:50 PM
To: jeroenterheerdt/HAsmartirrigation @.>
Cc: Comment @.>; Assign @.>; Subscribed @.***>
Subject: Re: [jeroenterheerdt/HAsmartirrigation] Bucket size keeps increasing (although it did not rain much), and duration was always 0 for a week now (Issue #381)
I just wanted to inform that the problem continues and can be also seen from the todays values, it may help for the analyse.
Todays rain rate was 0mm:
Bildschirmfoto.2024-05-26.um.23.37.27.png (view on web)https://github.com/jeroenterheerdt/HAsmartirrigation/assets/12121451/5ac3421e-1b52-4b56-b766-c08a26f1273a
Humidity:
Bildschirmfoto.2024-05-26.um.23.38.36.png (view on web)https://github.com/jeroenterheerdt/HAsmartirrigation/assets/12121451/9c1f5613-f2f9-49fc-a5af-5a9b85e3952e
It was mostly a sunny day:
Bildschirmfoto.2024-05-26.um.23.39.15.png (view on web)https://github.com/jeroenterheerdt/HAsmartirrigation/assets/12121451/42a8b529-0d51-463f-8dc1-756102ca9e81
without much wind:
Bildschirmfoto.2024-05-26.um.23.39.50.png (view on web)https://github.com/jeroenterheerdt/HAsmartirrigation/assets/12121451/570a1925-9446-42ab-9a7b-2e770bf90561
Temperature:
Bildschirmfoto.2024-05-26.um.23.40.36.png (view on web)https://github.com/jeroenterheerdt/HAsmartirrigation/assets/12121451/aa2f7098-17df-4362-a6f7-5c2e73bd434a
And my bucket was 7.0mm yesterday, now 6.5mm. So i strangely still do not have to irrigate:
Bildschirmfoto.2024-05-26.um.23.41.09.png (view on web)https://github.com/jeroenterheerdt/HAsmartirrigation/assets/12121451/3b188b95-969c-4807-bfd0-ff4fa6200b28
—
Reply to this email directly, view it on GitHubhttps://github.com/jeroenterheerdt/HAsmartirrigation/issues/381#issuecomment-2132404835 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB6PIPVVJV5WCXGBQ5ZLJELZEJJNVBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZDANJTHA4TIMJXG6SG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJSGYZTCNZZGE3TNAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDEMZRG43TKMJZGYYYFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZDANJTHA4TIMJXG6TXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you commented on the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

So you mean sth. like this?

And:

Yes, like that. Reset your bucket(a) to 0 now and let it run for a couple of days.

OK thank you.

I thought a bit about this "3 day forecast" and would like to know why you think that the reason can be that part.
Does not the logic work this way?: Let's say the bucket was 0 yesterday, and our calculation ended up calculating 3mm today, because with a 80% of chance it will rain a lot tomorrow. So the bucket is 3mm now.
And tomorrow it did not rain at all.. On the next evening the algorithm should actually remove that part of estimation from yesterdays calculation, and start again from 0, and add to that today's real values from the sensors for example.
So in that way this 3 day forecast should not have those kind of strange effects on bucket.
It seem to me that, the bucket was always increasing maybe because the openweather-api were predicting too much rain, and it did not go as expected..

That last part is likely what is happening. What we do for forecasting is rather simple: when calculating the et value, include the forecast for x days in advance, and just treat is as one of the daily values. So yeah if owm says it's going to rain, then that is going to bump up the average a lot. Happy to take ideas on what to change / improve, but prefer PRs.
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: akcasoy @.>
Sent: Sunday, May 26, 2024 3:20:53 PM
To: jeroenterheerdt/HAsmartirrigation @.>
Cc: Comment @.>; Assign @.>; Subscribed @.***>
Subject: Re: [jeroenterheerdt/HAsmartirrigation] Bucket size keeps increasing (although it did not rain much), and duration was always 0 for a week now (Issue #381)
I thought a bit about this "3 day forecast" and would like to know why you think that the reason can be that part.
Does not the logic work this way?: Let's say the bucket was 0 yesterday, and our calculation ended up calculating 3mm today, because with a 80% of chance it will rain a lot tomorrow. So the bucket is 3mm now.
And tomorrow it did not rain at all.. On the next evening the algorithm should actually remove that part of estimation from yesterdays calculation, and start again from 0, and add to that today's real values from the sensors for example.
So in that way this 3 day forecast should not have those kind of strange effects on bucket.
It seem to me that, the bucket was always increasing maybe because the openweather-api were predicting too much rain, and it did not go as expected..
—
Reply to this email directly, view it on GitHubhttps://github.com/jeroenterheerdt/HAsmartirrigation/issues/381#issuecomment-2132413806 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB6PIPRRXRKR4D4LCRCSZLTZEJN4NBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZDANJTHA4TIMJXG6SG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJSGYZTCNZZGE3TNAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDEMZRG43TKMJZGYYYFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZDANJTHA4TIMJXG6TXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you commented on the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I see that still as a bug. The including weather predictions are one of the main advantages/characteristics of this integration.
But this should work like this:
When the weather prediction calculates, there will be 7mm rain tomorrow. And the evapotranspiration of yesterday was 5mm. The bucket size is calculated as 2mm.
The next day, when we see that it did not rain at all, 7mm should have been removed from the bucket as first, besides all other calculations for refreshing the bucket value.

That's fair, that we can do.


Building XCFramework doesn't properly include framework deps (SwiftyBeaver)

Describe the bug
Generating an XCFramework with the project's build script leaves behind SwiftyBeaver's swiftinterface file necessitating SwiftyBeaver be included in the parent project. Simply changing BUILD_LIBRARY_FOR_DISTRIBUTION to true should fix this.
To Reproduce
Steps to reproduce the behavior:

Build (./build.sh xcframework 0.19.3 1)
Embed in another project
Build pukes on missing SwityBeaver fw (it is present on fs, missing its .swiftinterface file)

Expected behavior
Shouldn't have to include the dep in the parent project.
Additional context
Answer found in this SO post. Simply supplying the flag at the xcodebuild step doesn't work, it must be changed within the project file.

see https://github.com/niochat/MatrixSDK/issues/2 for workaround


TypeError: Unable to parse URL: /

In production I have authentication redirect to back home, which is where the issue arises as apposed to miniflare environment.

Considering there's no stack trace I suppose this is framework specific issue. If you want reproduction I followed auth0 guide published by cloudflare.

If you're doing new URL("/") then this is just invalid & not allowed by JS. You need to include a full URL (including protocol) and/or make use of the second base argument.


decorators in object literals not working

From @pascalopitz on November 19, 2015 11:43
I am getting a parsing error for decorators on object literal properties. My jsconfig.json looks like this:
{
    "compilerOptions": {
        "target": "ES6",
        "module": "commonjs",
        "experimentalDecorators": true
    }
}

This code compiles okay in babel 5.8.12 using the "es7.decorators" extension.
Can I somehow make this work?

Copied from original issue: Microsoft/vscode#201

This is currently not supported. it is only supported on classes. i suspect will add support after the next TC39 meeting, just to have the proposal stabilizes.

Hi there. I am not sure why this has been moved to TS? Is the jsconf also using the TS parser?

Yes - some js services in vscode are based on the typescript language service.

It appears that it is firmly part of the proposal now.  I see that "Decorators for function expressions/arrow functions" are on the roadmap for 2.0 but not this.

The decorator proposal is changing a lot. there are some fundamental changes in how decorators are applied. we will need to stage all these changes and make sure they all land around the same time. I do not think we will be changing anything in the decorator implementation until these changes are finalized.

Hi, team, we've been heavily used ES decorators, especially decorators for object literals in our products, currently any code after blocks decorated by such decorators, could not be parsed correctly by VSCode; it keeps prompting [js] ';' expected. or [js] Declaration or statement expected., which seem annoying.
With some search, we found this issue, however a year has passed since last update of the issue. ES standards are evolving slower than we expected but babel-plugin-transform-decorators-legacy is still popular. Seems a lot of JS open source libs depend on this legacy decorators for object literals.
Is it possible for TS or VSCode to add a special setting to allow the decorators for object literals in JS code (e.g. experimentalDecoratorsForObjectLiterals), regardless the ES standard? It's ok to keep the legacy/non-standard warnings, but for minimal the code after the decorated blocks should be parsed correctly.
Thanks.

Hi, @mhegazy , may I ask whether has this issue even been part of TypeScript 2.1 milestone? Thanks.

This issue is under the Future milestone currently, meaning it is on our list, but we have no ETA at the moment .

Thanks for telling @mhegazy . Btw, what do you think about my previous question?

Is it possible for TS or VSCode to add a special setting to allow the decorators for object literals in JS code (e.g. experimentalDecoratorsForObjectLiterals), regardless the ES standard? It's ok to keep the legacy/non-standard warnings, but for minimal the code after the decorated blocks should be parsed correctly.

VSCode uses TS to power the JS/TS language service. If the feature is supported in TS, it will light up in future VSCode versions.
Keep in mind that decorators are currently a stage 2 proposal TC39, and not a ratified feature. we do plan on revisiting our decorator support soon, and implementing the new proposal. once we do that, we should have a clear resolution for this feature.

Ok so do I understand it correctly that since 2015 you weren't be able to implement this? Should I do it by myself or should I wait another 3 years or more?

@mhegazy can you please provide some approximated time, how long will it take? it would be really helpful for us to consider building upon that, (like if it's another 3 years then we will have to find some workaround)

@Durisvk as Mohamed stated, this is contingent on the Proposal progressing to Stage 3 with TC39.  It is still at Stage 2.  You can get the status and progress of the proposal here where you can participate in the discussion.  It is being discussed actively at every TC39 meeting and has a lot of focus.

@kitsonk I didn't find any mention (in this proposal you've provided) about a decorating object literals. It's again only focused on the classes, class properties, class methods and methods params. No object literal at all. I don't even see a place where I can participate in the discussion (should I create issue on that github page or how to discuss?). I don't know what TC39 means.

@Durisvk TC39 is the technical committee responsible for ECMAScript/ECMA-262 (the standard behind JavaScript).  Their guidelines on contributing are documented in the proposals repo I linked to.  They also provide documentation of the proposal process.

I should not say this, but technically you can manually apply a decorator on literal object property as well as on non-const enum member
import "reflect-metadata";

let dataKey = Symbol('myData');

let setMetaData = (Reflect as any).metadata(dataKey, 'DataDataData');
let getMetadata = (type: any, propertyKey: string) =>
  (Reflect as any).getMetadata(dataKey, type, propertyKey);

class MyClass {
  @setMetaData
  static one = 1;
}
console.log(getMetadata(MyClass, 'one')); // DataDataData

enum MyEnum {
  // @setMetaData // Disallowed
  one = 1
}
// @ts-ignore
__decorate([setMetaData], MyEnum, 'one', void 0); // Manual decoration
console.log(getMetadata(MyEnum, 'one')); // DataDataData

let myLiteral = {
  // @setMetaData // Disallowed
  one: 1
};
// @ts-ignore
__decorate([setMetaData], myLiteral, 'one', void 0); // Manual decoration
console.log(getMetadata(myLiteral, 'one')); // DataDataData

@shlangus Yeah but when you're building a library you don't want the programmers who use it to do this kind of hack

@mhegazy Is this going to be supported eventually?  It'd be nice to not do object <-> class mapping in things like type-graphql library.
Ref: https://github.com/wycats/javascript-decorators#object-literal-accessor-declaration

FYI https://github.com/tc39/proposal-decorators is the current decorator proposal.

This issue still exists. Even when this setting is on:

I get the following errors:

Object literal decorators are being considered as an extension to the decorators proposal: https://github.com/tc39/proposal-decorators/issues/119#issuecomment-710009339


Replace behaviors in PRC

Once the behaviors are extracted, we should remove the duplicate code from primer/react and import them from here

Done in https://github.com/primer/react/pull/1700


Bug remove selected options

hello, my code
<multiselect :value="itens_" v-model="itens_" :options="categorias" :multiple="true" label="nome" :track-by="id" placeholder="" select-label="" deselect-label="" :close-on-select="false" :clear-on-select="true" :searchable="true" :allow-empty="true" :hide-selected="true" @close="onTouch"></multiselect>

When you delete the first selected item, always delete the last one
The options I select do not disappear from the list
thank you

:track-by="id" => track-by="id"
It should be a string.
Also please remove :value if you’re using v-model. That’s redundant.


Realisation of "history" command

https://github.com/artemsmirnov/sesh/commit/6efb4ee79a6e68355b09449fcb2a6ca2edc0b7fd


Do not encrypt message subject if message body is not encrypted

Fixes #4718

Why is PgpMessageBuilder used when sending an unencrypted email?

Why is PgpMessageBuilder used when sending an unencrypted email?

The original issue explains that I am using 'PGP/Sign Only' mode (i.e sign the message but not encrypt the contents). Usual practice in mailing lists :)

Thanks :+1:


inspite of the batch job being scheduled it is not getting executed

Although the Scheduled Jobs page says that the RollupCalculateJob last ran on 5/23 at 3 am, I'm not seeing any record of the job running in the Apex Jobs page:

at the time the batch was suppose to execute, at the scheduled time it was observed that it did not even attempt to run the scheduled job. No error was also seen neither on the debug logs page nor in the apex jobs page.

We submitted a Salesforce.com case:  19115101: Salesforce on their end sees the job immediately failed with the message "Scheduled Apex job not finding its core.async_apex_row: jobId:<PHONE_NUMBER>1Uwr7, orgId: 00D36000000JE79" classId: 01p3600000JQPzC

We have deleted the scheduled jobs and then rescheduled them but the issue persists.

We are seeing this behavior with all of the dlrs rollups we have built that they are not rescheduled again.

@drroundcorner please let me know if you want to discuss further.


sample rate for EN_GB

Firstly, thanks to Karan for such a beautiful demo. I look forward to wading through the code in more detail later!
This isn't Karan's fault, the AWS docs state throughout that 16000Hz is allowed for EN_GB, but I have found that it accepts only 8000Hz for that ISO code.
It's a very small point, and when the transcribe team update the capabilities for EN_GB to match the docs, this will go away, but it might be worth mentioning that for anyone who plans to implement this wonderful tutorial, they should expect an error from the WS if using EN_GB and a sample rate of more than 8000 at this time. However EN_US does an amazing job of recognising EN_GB speech.
function setLanguage() {
    languageCode = $('#language').find(':selected').val();
    if (languageCode == "en-US" || languageCode == "es-US")
        sampleRate = 44100;
    else if(languageCode == "en-GB")
        sampleRate = 8000;
    else
        sampleRate = 16000;
}

Hi @faloupy, glad you are enjoying the demo. I'll pass the bug report over to the Transcribe team, as I believe it should downsample things on the server side.

Closed by #4


Feature: Timed user input for ui mode

Current behavior

The user input is now timed for 5 mins that is, if the user does not give any input for 5 min, the program will close itself. The ui will run again if we hit refresh, but the previous text prompts asked and the answers given will be deleted.
Proposed changes

Updated the requirements.txt file.
Changed the ui.py so that now the last_input_time is tracked using st.session_state. Which helps in comparing it with the timedelta funtion. if datetime.now() - last_input_time > timedelta(minutes=5) the chat input will be closed.

It is better to close the chat_input for ui mode by changing the ui.py rather than terminating the program by changing manager.py. Hence, it is a enhanced solution for issue #93 .

After the program is executed (see the bottom right corner for time).

After 5-6 mins (see the bottom right corner for time).
Checks

[x] All commits in this Pull Request are signed and Verified by Github.

@savyez what about the manager.py? like is there any time input?

@neokd for CLI there already was a timer in manager.py but for ui, I thinking adding a seperate timer to ui.py was a better choice as we can easily find the timer and also ui takes more time to load than CLI

The CLI one stops if LLM takes more than 2minutes to respond. I was thinking to add something like https://pypi.org/project/pytimedinput/#:~:text=timedInput(),if the user goes idle. this into our project for CLI. The UI one looks good ,probably you can add a warning like message at initialisation that bot stops after no interaction received for 5 minutes.

@neokd ig it won't have any conflicts with #104 , we are already importing ui in manager.py. also CLI and ui should have different timings as they both require different set of resources... some of which intersect with each other.... for #104 we can add them similiarly as the persona_list.

Thanks for your contribution @savyez

also, update the documentation demonstrating --ui.


DoneJS support for Debian/Ubuntu

Issue by tracer99 from Wednesday Oct 07, 2015 at 20:14 GMT
Originally opened as https://github.com/donejs/donejs/issues/205

The NodeJS package in Debian/Ubuntu creates a /usr/bin/nodejs executable as node is already taken by an older package.
DoneJS is hardcoded to look for /usr/bin/node which on these systems doesn't exist.
a simple simplink makes it work, but ideally donejs should detect and support the different path.

Comment by daffl from Wednesday Oct 07, 2015 at 20:21 GMT

The binary is looking for #!/usr/bin/env node. So if you environment is set up properly it should work. This is what pretty much every other Node package binary does too.

Comment by matthewp from Wednesday Oct 07, 2015 at 20:25 GMT

It's not really a bug I would say. Lots of code expects a node in the PATH.  Debian installs it as nodejs.  You'll find that most scripts in npm look for node.
The fix it to create a symlink:
sudo ln -s $(which nodejs) /usr/local/bin/node

Comment by tracer99 from Wednesday Oct 07, 2015 at 20:22 GMT

So this is a bug with the nodejs package in debian?
Edit: this was a fresh Install of Debian Stable. node was installed through debians package manager.

Comment by matthewp from Wednesday Oct 07, 2015 at 20:27 GMT

@daffl actually we could probably make this be a normal .js file and get rid of the shebang.  npm will run it as an executable anyways I think.

Comment by daffl from Wednesday Oct 07, 2015 at 20:30 GMT

I think we should do it the way literally every other Node binary does it which is the way it is set up at the moment.

Comment by phillipskevin from Wednesday Oct 07, 2015 at 20:31 GMT

This talks about the issue with Debian and how different package managers install the node binary as nodejs: https://github.com/nodejs/node-v0.x-archive/issues/3911#issuecomment-12798913

Comment by tracer99 from Wednesday Oct 07, 2015 at 20:31 GMT

Maybe add a note in the documentation for debian/ubuntu users then? As without creating that symlink, it will not work.

So yes, after installing nodejs-legacy, everything seems to work fine. So this is less of an issue with Node/DoneJS and more an issue with Debian/Ubuntu. Seeing as these are really popular distros though, I suggest making this a documentation item.

We might want to have Platforms page that goes over the various quirks on different platforms (this, stuff you have to install on Windows, etc).

@tracer99 I'm adding a page that goes over these things, which version of Node do you get when you install nodejs-legacy?  You can find out with node -v.

Nm, going to suggest using a PPA.

@matthewp node-legacy is not a node package. You need nodejs installed, which is v0.10.29
The node-legacy package just sets up the symlink for node -> nodejs

@tracer99 I've added a page on using with Ubuntu/Debian, thanks for your suggestion on this.  http://donejs.com/OperatingSystems.html#section=section_Debian_Ubuntu


boards: dts: Fix broken link in comment

Trivial: Update broken hyperlink in a comment to the current location
Signed-off-by: Eug Krashtan<EMAIL_ADDRESS>

CI will always timeout, going to merge.


add license

Hi! Thanks for creating this library, it's been awesome to use. Is there any chance you could add a license for this package? It would make this package more accessible for people to use and develop with.

Hey @amosyou! I kind of just threw together this library for a task I needed to do for work. Wasn't really expecting it to catch the interest of too many others, and so I didn't have a license to begin with 😅. But thanks for this suggestion. I'll be adding an MIT License to the project.

perfect! appreciate the quick response :))


Misc improvements

Added bar counter on crucible

Added config for different highlight modes

Changed heat left to show decimals (to help planning for natural heat loss)

Added rudimentary heat/cool estimates

Still TODO:

Make 3D overlay texts configurable (and position them so they don't jitter)
Fix heat/cool estimates undershooting medium heat
Try getting heat/cool estimates to go to the optimal place
Will attempt notches as mentioned in #10

I'll be travelling next week and will aim to get this merged in afterwards ✈

I just realized we made very similar changes!
https://github.com/Toofifty/easy-giantsfoundry/pull/34

It seems like the quench prediction is off by 1 or so and tells you to do an extra one than it should

I think most of this has been covered by TheLouisHong already so going to close this.


Is there a plan to support rfc7692?

Is there a plan to support rfc7692 ?
rfc7692

No, there is not.


STMNIST addition to snntorch

Training on ST-MNIST with Tonic + snnTorch Tutorial

Will check over the ipynb notebook shortly. Could you revert the title of Tutorial 6 back to what it was before?
We don't want to change that.

Note: you can just push another commit with the updated changes without making a new pull request. Everything will automatically be updated here.

Note: you can just push another commit with the updated changes without making a new pull request. Everything will automatically be updated here.

Sure I changed Tutorial 6 back, everything should be updated!

Structure & results are really solid.
I've just started making some minor changes mainly to make things more succinct.
Could you update the following:

A few of the title headers aren't loading properly and need a space between ## and the text.
remove the code blocks that are fully commented + unnecessary comments (e.g., s 1.7, and s 3)
The test set accuracy plot isn't needed as there are only 3 sample points; I think you should just print the final value

Really cool stuff though; I'll have to share this with the OG authors of the ST-MNIST paper.

Structure & results are really solid. I've just started making some minor changes mainly to make things more succinct.
Could you update the following:

A few of the title headers aren't loading properly and need a space between ## and the text.
remove the code blocks that are fully commented + unnecessary comments (e.g., s 1.7, and s 3)
The test set accuracy plot isn't needed as there are only 3 sample points; I think you should just print the final value

Really cool stuff though; I'll have to share this with the OG authors of the ST-MNIST paper.

Do you want us to delete the code block in 1.5 which has the option to run the full transform vs short transform? Also there is a link in your tutorials where theres a button that says "open in drive" how do we get that GitHub colab link?

Do you want us to delete the code block in 1.5 which has the option to run the full transform vs short transform?

Yep just go with one of the two transforms.

Also there is a link in your tutorials where theres a button that says "open in drive" how do we get that GitHub colab link?

We need to merge this first and then the ipynb file will have a solid URL.
In the meantime, just copy paste the URL from another tutorial and change the ipynb file name to this one.


Settings: display that a new version is available & include link to release

REF #133

Closed by #159


Cleanup of SafeDB directory and add to repo

------ ENHANCEMENT -------
Current Version
<IP_ADDRESS>
What is the the problem you want to solve?
SafeDB does not need to be its own repo.  SafeDB directory has old unused files in it.
What is your take on the correct solution to the problem?
Add SafeDB directory to safe-networking repo and remove
dbbuild.old
dbbuild.old1

Moved SafeDB to safedb.  Removed all cached directories and submodule references and brought under safe-networking repository.
Removed dbbuild.old and dbbuild.old1
See commit 2457370f3af17faa950b5d722c7b1d71437b8a34 for more information


Update Bower Overrides explanation

Add a clarification regarding the path for the override of a dependency.

I would think that we can do better and perhaps more thoroughly explain it. That almost is more confusing to me, someone who understands the main property.
Specifically, we're overriding individual package's main property as it exists in their individual bower.json. For example, angular has an angular.js in their root directory, so they specify their main as angular.js. But let's say you want to use the index.js in the root directory (it exports angular as a commonjs module) with wiredep (not really sure why you'd want to, but just see this through). Then we'd want to override the main property to be index.js.
It's not so much about "relative path" as we're just overriding the main property in the packages' bower.json files, and it makes sense that the packages don't know about anything outside of them, so it is from the packages' directory...
I don't know. Maybe I'm just rambling on and not making and sense and arguing semantics.

Hi @CWSpear thank you for reply.
I think I understand your point: what I intended with my addition was to clarify the base path of an override, that is the dependency's root directory. Maybe we can improve this?

Thanks @tubia! Please add directly to the readme if it can be improved @CWSpear :)


Page marked as "pending" on move even if unpublished

Create root page "sections"
Create root page "section 1"
Publish both pages
Unpublish "section 1"
Move "section 1" to be a child of "sections"
"section 1" will now be marked as pending

https://drive.google.com/file/d/0B9SwgyV0g1hSc1RSLVoxcVJFNDQ/view
Related to #5107
Verified as a regression of 3.2.
Regression came from https://github.com/divio/django-cms/commit/ec1d6c3c1d666efe3cb6eec5a13f59d81f0fbc42.

[ ] Merge #5142 into develop


(nsw-design-system) update to 3.17.5, update class in footer

Changes

Update nsw-design-system to 3.17.5
Add new class in footer for Acknowledgement of Country

See https://github.com/digitalnsw/nsw-design-system/compare/v3.17.0...v3.17.5
Prior to merge, need to review the change in src/components/filters/filters.js in that diff
..also adding sponsors component using what we currently have.

See<EMAIL_ADDRESS>Prior to merge, need to review the change in src/components/filters/filters.js in that diff
..also adding sponsors component using what we currently have.

See 39e0f763dd92bae75dbba4af5a1703b0a72fbb41 for sponsorship component in separate branch

The filters.js change was a fix for form reset handling. Looks OK.