Scrolling section backgrounds

Another post-positconf enhancement I'd like to work on: assigning a video or image sequence as a full bleed background that animates on scroll.
Example: https://www.apple.com/airpods-pro
This is a pretty common scrollytelling technique - -although it can blow out page size, it means a video team can separately prep the visuals without too much engineering! And it would work well for people using packages like rayrender 🥳

Sounds great! And wow, that examples is intense!

#132 brings up another example of video functionality that would be very helpful and probably fairly easy to implement: a trigger effect that starts a video playing. Seems straightforward through JS .play()?

I think a video that autoplays (and potentially loops) when visible should be pretty straightforward! And maybe a .scale-to-cover class to match .scale-to-fill?
A video that progresses as the user scrolls is more complicated — I've seen a couple of libraries designed to do it, but if I could make it work with just Scrollama I'd love to. Might mean writing a few event handlers and streaming media hooks ourselves. I'll do some reading for that!

The Apple AirPods Pro example above actually demonstrates both techniques:

The AirPods that feature at the top and move on scroll are a PNG sequence:

HTML of the PNG image sequence from the Apple site

  <canvas class="image-sequence image-sequence-hero" data-sequence-img-format-map="{"large": "png", "medium": "png", "small": "jpg"}" data-sequence-basepath="/105/media/us/airpods-pro/2022/d2deeb8e-83eb-48ea-9721-f567cf0fffa8/anim/hero/" data-sequence-img-format="png" data-sequence-load-kf="{"start": "a0t - 200vh", "end": "a0b", "anchors": [".scroll-container-hero"], "disabledWhen": ["no-enhanced", "no-heavy-media", "text-zoom", "mq-large-short"]}" data-sequence-progress-kf="{"start": "a0t - css(--r-localnav-height, a0)", "end": "a0t - css(--r-localnav-height, a0) + (a0h - a1h) - 18vh", "anchors": [".scroll-container-hero", ".sticky-hero"], "disabledWhen": ["no-enhanced", "no-heavy-media", "text-zoom", "mq-large-short"]}" data-component-list="Sequence" style="opacity: 1; transform: matrix(1, 0, 0, 1, 0, 0);" width="1440" height="810">
  </canvas>
  <picture class="hero-fallback-pic" data-lazy="" data-download-area-keyframe="{"disabledWhen": ["enhanced"]}">
    <source data-empty="" srcset="data:image/gif;base64,R0lGODlhAQABAHAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw==" media="(min-width:0px)">
    <source srcset="/105/media/us/airpods-pro/2022/d2deeb8e-83eb-48ea-9721-f567cf0fffa8/anim/hero/small/0000.jpg" media="(max-width:734px)"><source srcset="/105/media/us/airpods-pro/2022/d2deeb8e-83eb-48ea-9721-f567cf0fffa8/anim/hero/medium/0000.png" media="(max-width:1068px)">
    <source srcset="/105/media/us/airpods-pro/2022/d2deeb8e-83eb-48ea-9721-f567cf0fffa8/anim/hero/large/0000.png" media="(min-width:0px)">

  </picture>
  [a stringified version of the picture element]

A video of a person dancing autoplays after you scroll beyond that:

HTML of the looping, autoplay video
 ```

 ```

The video has 100% width and height, and has object-fit: cover, which takes care of cropping it an aspect ratio that fits the available space (in line with the CSS-Tricks link above).

This would be so neat! I'm hoping to apply the image sequence/gif idea to my closeread submission! Do we have an estimate for when this feature might be available? 🙏🏽

It's exciting! You see the work here:
https://github.com/qmd-lab/closeread/pull/139
I'm not sure if new features will be ready before the deadline, but if so, we'll be sure to update the github / docs site and send out a message to those that have submitted.


Very quick and dirty fan support

I don't expect to merge this PR, but maybe someone gets some use from this until there's more complete fan support in this repo.

hi @domstarkey, thanks for creating a PR! I'm actually really close to providing fan support but have been blocked because I don't own an Alexa-connected fan and no one has provided the information I need yet to feel confident it will work. This is the information I need:
please upgrade the plugin to the latest version (2.0.1), enable debug in the plugin settings, and share the following output:
[date time] [HomebridgeAlexaSmartHome] <your device name here> ::: Current state: [
...
]

[date time] [HomebridgeAlexaSmartHome] <your device name here> ::: Range capabilities: [
...
]

Thanks!

@domstarkey thanks so much for creating this PR and fork. I will be adding basic support for fans as you have here in v2.0.8. From what I have discovered so far, various fan models and companies have very different underlying controls which has made it difficult to add full support for fans.


chore(release): 1.14.1

See CHANGELOG.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: d9400bdf61527608e32cdc6a449dfca41f4cad37
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@MergifyIO refresh


[SPARK-45638][SQL][Avro] Improve test coverage of decimal conversion

What changes were proposed in this pull request?

-Improve test coverage of decimal conversion
Why are the changes needed?

Test improvement
Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit test
Was this patch authored or co-authored using generative AI tooling?

No

thanks, merging to master!


Update openthread.io Pre-Built NCP Firmware

With recent change merged (PR #4976), the new posix host driver requires to use the new RCP image. Otherwise, user will encounter Spinel parsing error (like the one here: https://groups.google.com/g/openthread-users/c/RtolmaADSc4).
This issue is opened to track the updates to the prebuilt firmware in openthread.io for both nrf52840 and cc2538.

Thanks Yakun (@bukepo) for pointing this issue out.

The nrf52840 NCP image was built with
BORDER_AGENT=1 BORDER_ROUTER=1 COMMISSIONER=1 UDP_FORWARD=1 USB=1 LINK_RAW=1
And the cc2538 NCP image was built with
BORDER_AGENT=1 BORDER_ROUTER=1 COMMISSIONER=1 UDP_FORWARD=1 LINK_RAW=1
Should I use the same flags for the RCP versions?

Hi Jeff. Looks like we only put NCP image on openthread.io (https://openthread.io/platforms/co-processor/firmware). Then I think it is fine to just update the NCP image and use the same flags. No need to put RCP image on openthread.io. Thank you!

The nrf52840 NCP image was built with
BORDER_AGENT=1 BORDER_ROUTER=1 COMMISSIONER=1 UDP_FORWARD=1 USB=1 LINK_RAW=1
And the cc2538 NCP image was built with
BORDER_AGENT=1 BORDER_ROUTER=1 COMMISSIONER=1 UDP_FORWARD=1 LINK_RAW=1
Should I use the same flags for the RCP versions?

Those flags will not affect RCP build, it's OK to use the same flags.

Oh I thought you meant to replace the NCP images with RCP.  I'll just update the NCP ones then.

I've updated the nRF52840 NCP firmware on openthread.io.
CC2538 has been removed (along with all the instructions) as the platform is EOL and downloads of the firmware are extremely low.


Updated example of extending an existing schema

The README gives an example of how to validate an extended schema, but it looks like the code is out of date. This fixes it.

:+1:

Closing this, as I already merged the same change in #335


Creating socket failed during dataload

All 6 gpfdist logs show this message:
[2017-01-10 11:50:45] [WRN /tmp/build/78017950/hdb_apache/src/bin/gpfdist/src/gpfdist/gpfdist.c:2068] Creating the socket failed
Serving HTTP on port 9006, directory /opt/gpadmin/segmentdd/pivotalguru_6
[2017-01-10 11:54:14] [WRN /tmp/build/78017950/hdb_apache/src/bin/gpfdist/src/gpfdist/gpfdist.c:2187] signal 15 received. gpfdist exits
Is this error critical? The data seem to loaded fine.
Thanks.

signal 15 is the process getting killed after it is complete.  Not critical.
The large fact tables are compressed so you will see less than 100GB of
data stored in hdfs.
On Tue, Jan 10, 2017 at 10:59 AM, dimon777<EMAIL_ADDRESS>wrote:

All 6 gpfdist logs show this message:
[2017-01-10 11:50:45] [WRN /tmp/build/78017950/hdb_
apache/src/bin/gpfdist/src/gpfdist/gpfdist.c:2068] Creating the socket
failed
Serving HTTP on port 9006, directory /opt/gpadmin/segmentdd/pivotalguru_6
[2017-01-10 11:54:14] [WRN /tmp/build/78017950/hdb_
apache/src/bin/gpfdist/src/gpfdist/gpfdist.c:2187] signal 15 received.
gpfdist exits
Is this error critical?
I also see the amount of data on HDFS was x2 less in 100GB dataset:
$ hdfs dfs -du /hawq_default
53796875480<PHONE_NUMBER>12 /hawq_default/16385
Is this also correct?
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pivotalguru/TPC-DS/issues/11, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFObRAEwU58UKNxzC07Mw_cpiJrQpIqJks5rQ7jYgaJpZM4Lfpi6
.

Thank you.


Accessory only shows current state but can't control it

When trying to change the state it does not respond (From Homebridge or HomeKit).
Only shows the current state of the switch (Switcher Mini).

Same here
@nitaybz I have the same issue as I opened new ticket but its similar case I guess

From the switcher app settings change to local and turn on and off from there... after a little while I should work again in HomeKit and you can cancel the local mode

Also, need to request from switcher support to upgrade FW version.
Afterwards the "local" configuration fix the problem.
Thanks!


Sometimes 0s min reported

Not sure if time.Duration -> string formatting or something else.

Test wasn't using Safe mode.


Introduce Larastan

Static analysis worth 100 pair of 👀

Should I add vendor/bin/phpstan analyze to CI steps?

Hmm, I'm not sure if I want static analysis for this project. I appreciate the help, but this seems like more of a burden than a useful thing, given that the project is a single PHP file.

I see :) You are right.
But I'm afraid of PHP without the shield of 3 "basic" tests.


SEO information not displayed

[ ] This is a question about using the theme.
[x] I believe this to be a bug with the theme --- not Jekyll, GitHub Pages or one of the bundled plugins.
[ ] This is a feature request.
[x] I have updated all gems with bundle update.
[x] I have tested locally with bundle exec jekyll build.

Environment informations

Minimal Mistakes version: current master as of 2016-09-27
github-pages or jekyll gem version: jekyll (3.2.1)
Operating system: Mac OS

Expected behavior

Display SEO information as implied by the _includes/seo.html in the HTML source
Steps to reproduce the behavior

If you view the HTML source for https://mmistakes.github.io/minimal-mistakes/docs/configuration/ you can see there is a large amount of empty space between the SEO comment and the title.  Something is wrong with the logic in the /_includes/seo.html file so this information is not being populated.
see screenshot: http://cl.rummel.co/0R3c1J1l0o1H

@justinrummel doesn't look like anything is missing to me. All of the relevant open-graph meta, Twitter cards data, etc. are there.
I get why you'd think something is missing from all of the white-space, but that is due to Liquid. For example that chunk of white-space before the <title> tag are all Liquid assign tags that don't actually output anything, but when read by Jekyll output as blank lines.
{% if site.url %}
  {% assign seo_url = site.url | append: site.baseurl %}
{% endif %}
{% assign seo_url = seo_url | default: site.github.url %}

{% if page.title %}
  {% assign seo_title = page.title | append: " " | append: site.title_separator | append: " " | append: site.title %}
{% endif %}

{% if seo_title %}
  {% assign seo_title = seo_title | markdownify | strip_html | strip_newlines | escape_once %}
{% endif %}

{% if site.url %}
  {% assign canonical_url = page.url | replace: "index.html", "" | prepend: site.url %}
{% endif %}

That's the case for a lot of the white-space and is completely normal... messy sure... but that's a Liquid issue and not the theme. HTML minification cleans that right up if you enable it.

OK, but I would have still expected a generic meta items be displayed somewhere in the head
<meta name="description" content="{{ seo_description }}">
<meta name="keywords" content="{{ post.tags}}">
<meta name="author" content="{{ site.name }}">

Oh, and thanks for the note about the _layouts/compress.html!  The documentation at http://jch.penibelst.de is perfect.

@justinrummel  <meta name="description" content="{{ seo_description }}"> is an omission and should be there. Happy to look at a PR to add it in.
keywords is useless and potentially harmful as it's been abused in the past by spammers. It's a general best practice not to use it.
What is the value of adding meta name="author"? I haven't seen it used in many places. Most of the SEO include is lifted from the Jekyll SEO plugin which doesn't use it either.

@justinrummel I originally had compress enabled with the theme but it caused several issues so I turned it off. In most causes it should work fine.

@mmistakes the suggestion for keywords and author are not requirements.  Just was trying to expand beyond the one item description to see if there were other default meta tags that may be missing based on http://smo.knowem.com
I'll work on a PR for the description tag.


add intake catalog and readme

This pull request transfers over the contents of https://github.com/USGS-python/hytest-catalogs.

I updated the README.md to delete the disclaimer at the end, and added a few sentences to give context at the beginning.
I made no changes to the intake catalog
I did not transfer the ioos_intake_catalog.yml or the LICENSE (because we have a license for the whole repo in another pull request).

Once we merge this pull request, I will make sure the notebooks in other repos on USGS-python get updated to read from this catalog (as I transfer them over to this new repo). Then I will make the hytest-catalogs repository private.

Looks like the sample code in the readme is still pointing to the catalog file on USGS-python.
Should that be changed to
https://raw.githubusercontent.com/hytest-org/hytest/main/dataset_catalog/hytest_intake_catalog.yml

??

Thanks for catching that! I'll update now @gzt5142


include option to generate only names with ".com" domain availability

please do the following:

add an option to the name-generator.tsx form to allow the user to select whether they want to optimize name results for names with a ".com" domain available. make sure to add this field to the react hook form and add a checkmark or switch to the form to let the user indicate if they want to optimize for .com
change the name generation logic to first do the whoxy lookup to determine if the ".com" is available for a generated name
only display results that have a ".com" domain available

closing because i implemented this


winapifamily.h fix

For some reason this file is being force-included into windows builds and causes plenty of '"winapifamily.h"': No such file or directory errors while building. Commenting the line seems to solve the issue for me(Visual studio 2017 Enterprise).
Though with my shallow understanding of how Windows SDKs are organized, I think you meant to do this:
if (MSVC)
  if (CMAKE_SYSTEM_VERSION MATCHES "10\\.0.*")
    list(APPEND CRYPTOPP_COMPILE_DEFINITIONS "_WIN32_WINNT=0x0A00")
  else ()
    list(APPEND CRYPTOPP_COMPILE_OPTIONS "/FI\"winapifamily.h\"")
  endif ()
endif ()

As the newer Windows 10 SDKs don't have winapifamily.h, but the older Windows 8-and-below sdks have winapifamily.h in their shared directory. I think SDL ran into a similar issue with the newer SDKs.

Thanks @Wunkolo,
Forgive my ignorance... Would it be possible to have CMake test for the availability of winapifamily.h and include the header if found? Something like:
if (EXISTS winapifamily.h)
    list(APPEND CRYPTOPP_COMPILE_OPTIONS "/FI\"winapifamily.h\"")
endif ()

The tricky part seems to be CMake must use the dev environment [include?] paths, and not just cwd.
Ping @jcfr, @abdes, @MarcelRaad

My Windows 10 SDK does have winapifamily.h. It's in C:\Program Files (x86)\Windows Kits\10\Include\10.0.17134.0\shared.

OK, so I tried to test the CHECK_INCLUDE_FILE_CXX change as described above in a VS 2015 x86 Developer Prompt. It looks like something went sideways. CMakeLists.txt:36 sets the Crypto++ version number via project(cryptopp VERSION 7.0.0).
Maybe someone more experienced with CMake on Windows can test it.
C:\Users\Test\Desktop\cryptopp\cmake_build>"c:\Program Files (x86)\CMake\bin\cma
ke.exe" ..
-- Building for: Visual Studio 15 2017
-- *************************************************************************
The Crypto++ library does not officially support CMake. CMake support is a
community effort, and the library works with the folks using CMake to help
improve it. If you find an issue then please fix it or report it at
https://github.com/noloader/cryptopp-cmake.
-- *************************************************************************
-- Selecting Windows SDK version 10.0.16299.0 to target Windows 6.3.9600.
CMake Error at CMakeLists.txt:36 (project):
  Failed to run MSBuild command:

    C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/MSBuild/15.0/
Bin/MSBuild.exe

  to get the value of VCTargetsPath:

    Microsoft (R) Build Engine version <IP_ADDRESS>198 for .NET Framework
    Copyright (C) Microsoft Corporation. All rights reserved.

    Build started 10/29/2018 5:46:37 AM.
    Project "C:\Users\Test\Desktop\cryptopp\cmake_build\CMakeFiles\3.12.3\VCTarg
etsPath.vcxproj" on node 1 (default targets).
    C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v140\Microsoft.Cpp.Platfor
m.targets(57,5): error MSB8020: The build tools for v141 (Platform Toolset = 'v1
41') cannot be found. To build using the v141 build tools, please install v141 b
uild tools.  Alternatively, you may upgrade to the current Visual Studio tools b
y selecting the Project menu or right-click the solution, and then selecting "Re
target solution". [C:\Users\Test\Desktop\cryptopp\cmake_build\CMakeFiles\3.12.3\
VCTargetsPath.vcxproj]
    Done Building Project "C:\Users\Test\Desktop\cryptopp\cmake_build\CMakeFiles
\3.12.3\VCTargetsPath.vcxproj" (default targets) -- FAILED.

    Build FAILED.

    "C:\Users\Test\Desktop\cryptopp\cmake_build\CMakeFiles\3.12.3\VCTargetsPath.
vcxproj" (default target) (1) ->
    (PlatformPrepareForBuild target) ->
      C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v140\Microsoft.Cpp.Platf
orm.targets(57,5): error MSB8020: The build tools for v141 (Platform Toolset = '
v141') cannot be found. To build using the v141 build tools, please install v141
 build tools.  Alternatively, you may upgrade to the current Visual Studio tools
 by selecting the Project menu or right-click the solution, and then selecting "
Retarget solution". [C:\Users\Test\Desktop\cryptopp\cmake_build\CMakeFiles\3.12.
3\VCTargetsPath.vcxproj]

        0 Warning(s)
        1 Error(s)

    Time Elapsed 00:00:07.60

  Exit code: 1

-- Configuring incomplete, errors occurred!
See also "C:/Users/Test/Desktop/cryptopp/cmake_build/CMakeFiles/CMakeOutput.log"
.

The above solution doesn't work for me...
But I found another solution:
According to the answer here: https://stackoverflow.com/questions/40577415/detect-availablility-of-sdkddkver-h-and-winapifamily-h-from-developer-comman
The CMakeList.txt can be modified like this:

if (MSVC)
  if (CMAKE_SYSTEM_VERSION MATCHES "10\\.0.*")
    list(APPEND CRYPTOPP_COMPILE_DEFINITIONS "_WIN32_WINNT=0x0A00")
  endif ()
  if (WINDOWSPHONEKITDIR OR UNIVERSALCRTSDKDIR OR UCRTVERSION)
    list(APPEND CRYPTOPP_COMPILE_OPTIONS "/FI\"winapifamily.h\"")
  endif ()
endif ()


Detach WatchableStatus from Status and Remove LogLevel Literal

Pending https://github.com/bluesky/bluesky/pull/1585
Required because of an issue with the backwards-compatible way in which Bluesky imports protocols.
LogLevel literal was removed and replaced with a string because pydantic has issues with Literal because it is actually a function, not a class.

For reference https://github.com/pydantic/pydantic/issues/5821

Do we want an issue to revert this once the above is fixed?

In favour of #226


Add executable examples

Currently tests are used as examples - while useful, tests are meant to be rather dense, and - as such - hard to read for a newcomer. Add a set of examples which would be commented properly and executed in the test suite to guarantee their validity.

First, simple example available from 9ce9a9e

Another one available from 88f9a458f613d5eaba6b79f68c40a90ae288ff13


Failed to allocate 16384: Attempt to access invalid address. (os error 487).

++++++++++++++++++ I [00:00:00:00:952]:0x0000000000002090:kernel\src\syscalls\mod.rs:69
Syscall called: 477
++++++++++++++++++ I [00:00:00:00:952]:0x0000000000002090:kernel\src\syscalls\mod.rs:522
Guard page has been requested for main stack.
++++++++++++++++++ I [00:00:00:00:952]:0x0000000000002090:kernel\src\syscalls\mod.rs:69
Syscall called: 466
++++++++++++++++++ I [00:00:00:00:952]:0x0000000000002090:kernel\src\syscalls\mod.rs:69
Syscall called: 477
++++++++++++++++++ P [00:00:00:00:952]:0x0000000000002090:kernel\src\memory\mod.rs:322
Failed to allocate 16384: Attempt to access invalid address. (os error 487).

Can you provide a full log?

loggyboy.txt


Add support for profiler API hipification

This PR has changes to support profiler API hipification in cupy. The build passed with these changes and unit tests also passed as attached.
profiler_tests.log

@pnunna93 Could you please create this PR on hipify-cupy branch?

Sure @lcskrishna , changed the base branch.

This is moved to stage 3 and will be reviewed with Profiler team. Closing this PR.


[Error] Downloading stash for Hardcore

[Error] Downloading stash for Hardcore, details logged to DebugInfo.log, please open a ticket at https://github.com/Stickymaddness/Procurement/issues
[03-10-2015 18:58] System.Exception: Downloading stash for Hardcore, details logged to DebugInfo.log, please open a ticket at https://github.com/Stickymaddness/Procurement/issues
в POEApi.Model.POEModel.GetStash(String league, String accountName)
в Procurement.ViewModel.LoginWindowViewModel.LoadStashItems(Character character)
в Procurement.ViewModel.LoginWindowViewModel.d__6.MoveNext()
в System.Collections.Generic.List1..ctor(IEnumerable1 collection)
в System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
в Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass2.b__1()
в System.Threading.Tasks.Task.Execute()

The new version of Procurement is out, which fixes this issue: https://github.com/Stickymaddness/Procurement/releases/tag/1.9.6
Unfortunately until GGG decide to support the dev community, these type of issues will continue to happen as it is out of our hands. http://i.imgur.com/yrPtajM.jpg


Any traffic transmitted should be encrypted with a temp auth key

Using an ephemeral temp auth key for all traffic instead of the permanent auth key means that traffic can't be captured and decrypted after the fact if the auth key is later leaked or stolen. This is a very common mitigation used in modern TLS suites. (TLS 1.3 only supports ephemeral key exchange groups.)

I'm personally not interested in this and I'd like to prune issues, so I'll be preemptively closing this. But still happy to merge such a PR.

dang i opened this four years ago? aight i'll work on it sometime soon since i'm actually using the library now as of like last week.

We can of course still talk about it and I'm happy to help / guide through the library, perhaps in the gramme_rs group in Telegram, if you prefer.


windows don't save size when turn off

Hi!
After resizing as desired but when closing the application and restarting, the window size is back to the same.
I need save size windows when turn off
My OS: Ubuntu Desktop 20.04
thanks

I'll include this in the next version!


Include ssh gateway public key in UpdateTunnelEndpoint

Send additional parameter to include ssh gateway public key when calling UpdateTunnelEndpoint api if there is atleast one ssh port

An alternative approach could be to add a TunnelRequestOptions.AdditionalQueryParameters, similar to AdditionalHeaders.

Why is the option only on update operation and not get operation? Can you explain the scenario where this is used?

There is no get for endpoints api.
The tunnel CLI uses this update api while hosting a tunnel and uses the output to show relay url/ssh command.

There is no get for endpoints api.

The get-tunnel response includes endpoints.

The get-tunnel implementation has port information to determine if there is an ssh port and hence does not require this query parameter. (Only exception is if we call get-tunnel with a non-ssh port number and there are other ports which are ssh.. but in that scenario, we can skip sending the key)


Info.plist Key Issues in AndroidAutoUKey2Wrapper with XCode 15.x

Hello,
We're using the AndroidAutoUKey2Wrapper framework in our project with XCode 14. After updating to XCode 15.0, we're unable to upload build archives to TestFlight due to missing CFBundleVersion and CFBundleShortVersionString keys in the framework's Info.plist.

Manually adding these keys resolves the issue. Could you please update the framework to include them?
Thanks for your support.

Thanks for the feedback. We'll make the changes and get the change into an upcoming release. Thanks.

I pushed a fix to the hotfix branch for evaluation. Can you let me know whether that fixes the issue? Thanks.

Thank you for your quick reply and support.
The hotfix branch fixes the issue !

Great! Thanks for checking. I appreciate it. I've committed these changes internally, and they should be included in the release later this spring. It won't be included in the February release because that one has already passed QA so it's too late to make any changes in it.


Gulp Cover seems to be failing

Hey,
Firstly thanks for starting this amazing skeleton app and having integration with code coverage tool 'isparta'  . But for some reason this does not seem to be performing well for me.
I tried running this task locally :

https://github.com/aurelia/skeleton-navigation/blob/master/build/tasks/test.js#L26-L49

Seems like this is failing . Any suggestions ?
probably @Gheoan ?

closing this seems to be working now. apologies for the confusion.


Yield table columns get overwritten

When producing yield tables with at least two regions that have at least two bins each, some columns are overwritten accidentally. This happens since the column headers are not unique.

In the example, bin 2 of region 2 will have a header \nbin 2 and be written into the second column instead. This can be fixed by making the headers unique. One way to do this is to keep the region name in all headers.

An alternative solution would be to use some other structure than a dict, which is possible with tabulate. The dict may be a better solution in the longer term as it is easier to parse.

Implementing a solution to keep the best of both options: unique keys in the dict, but a custom header for visualization that removes superfluous region names.


Warning: Batch of prepared statements exceeding threshold

Hello Martin,
I see these warnings in cassandra logs when trying this out-
Batch of prepared statements for [akka.messages] is of size 5331, exceeding specified threshold of 5120 by 211.
This looks more of a concern from cassandra side than this plugin itself. But, wanted to check anyway.
Thanks in advance.

thanks..good job.


Recursion error in transformer module with NeMo Stable Diffusion

🐛 Bug
NeMo's Stable Diffusion uses CLIPTextModel from HuggingFace transformers. Using thunder.jit with the CLIPTextModel is causing a RecursionError.
To Reproduce
Steps to reproduce the behavior:

Add the following lines to transformers/models/clip/modeling_clip.py here in the location where transformers is installed in your container

        ## thunder.jit
        self.embeddings = thunder.jit(self.embeddings)
        self.encoder = thunder.jit(self.encoder)
        self.final_layer_norm = thunder.jit(self.final_layer_norm)

Run NeMo Stable Diffusion with the command below:

python examples/multimodal/text_to_image/stable_diffusion/sd_train.py trainer.precision=16 trainer.num_nodes=1 trainer.devices=1 ++exp_manager.max_time_per_run=00:00:03:00 trainer.max_steps=20 model.micro_batch_size=1 model.global_batch_size=1 model.data.synthetic_data=True exp_manager.exp_dir=/workspace/TestData/multimodal/stable_diffusion_train model.inductor=False model.cond_stage_config._target_=nemo.collections.multimodal.modules.stable_diffusion.encoders.modules.FrozenCLIPEmbedder ++model.cond_stage_config.version=openai/clip-vit-large-patch14 ++model.cond_stage_config.max_length=77 ~model.cond_stage_config.restore_from_path ~model.cond_stage_config.freeze ~model.cond_stage_config.layer model.unet_config.from_pretrained=null model.first_stage_config.from_pretrained=null model.unet_config.use_flash_attention=False model.unet_config.attention_resolutions=\[1\] model.unet_config.channel_mult=\[1\]

Partial stack trace below:
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
    return forward_call(*args, **kwargs)
  File "/workspace/software/lightning-thunder/thunder/core/module.py", line 49, in forward
    res = self._forward_fn(*args, **kwargs)
  File "/workspace/software/lightning-thunder/thunder/__init__.py", line 617, in fn_
    cache_entry, inps, pro_to_epi = get_computation_and_inputs(*args, **kwargs)
  File "/workspace/software/lightning-thunder/thunder/__init__.py", line 202, in cache_info_wrapper
    res = fn(*args, **kwargs)
  File "/workspace/software/lightning-thunder/thunder/__init__.py", line 540, in get_computation_and_inputs
    autocast(computation_trc.python_callable(), dtype=autocast_thunder_dtype), *inps
  File "/workspace/software/lightning-thunder/thunder/core/trace.py", line 437, in python_callable
    python_str = self.python(**kwargs)
  File "/workspace/software/lightning-thunder/thunder/core/trace.py", line 318, in python
    import_ctx, call_ctx, object_ctx = self._gather_ctxs()
  File "/workspace/software/lightning-thunder/thunder/core/trace.py", line 281, in _gather_ctxs
    bsym_import_ctx, bsym_call_ctx, bsym_object_ctx = bsym.gather_ctxs()
  File "/workspace/software/lightning-thunder/thunder/core/symbol.py", line 580, in gather_ctxs
    return self.import_ctx(), self._get_call_ctx(), self.object_ctx()
  File "/workspace/software/lightning-thunder/thunder/core/symbol.py", line 520, in import_ctx
    self._out_printables, self._arg_printables, self._kwarg_printables  # type: ignore
  File "/workspace/software/lightning-thunder/thunder/core/symbol.py", line 472, in _out_printables
    return codeutils.to_printable(trace, self.output, import_ctx=self._import_ctx, object_ctx=self._object_ctx)
  File "/workspace/software/lightning-thunder/thunder/core/codeutils.py", line 128, in to_printable
    printables.append(to_printable(trace, f, import_ctx=import_ctx, object_ctx=object_ctx))
  File "/workspace/software/lightning-thunder/thunder/core/codeutils.py", line 128, in to_printable
    printables.append(to_printable(trace, f, import_ctx=import_ctx, object_ctx=object_ctx))
  File "/workspace/software/lightning-thunder/thunder/core/codeutils.py", line 128, in to_printable
    printables.append(to_printable(trace, f, import_ctx=import_ctx, object_ctx=object_ctx))
  [Previous line repeated 2899 more times]
  File "/workspace/software/lightning-thunder/thunder/core/codeutils.py", line 123, in to_printable
    if is_collection(x):
  File "/workspace/software/lightning-thunder/thunder/core/baseutils.py", line 153, in is_collection
    return isinstance(x, collections.abc.Collection) and not isinstance(x, (str, torch.Tensor, np.ndarray))
  File "/usr/lib/python3.10/abc.py", line 117, in __instancecheck__
    def __instancecheck__(cls, instance):
  File "/root/.vscode-server/extensions/ms-python.debugpy-2024.6.0-linux-x64/bundled/libs/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_trace_dispatch_regular.py", line 469, in __call__
    return None if event == 'call' else NO_FTRACE
RecursionError: maximum recursion depth exceeded in comparison

CC: @tfogal
cc @tfogal

FYI just figured that self.encoder consisted of a nn.ModuleList with a for loop (shown below) which probably caused the recursion error.
self.layers = nn.ModuleList([CLIPEncoderLayer(config) for _ in range(config.num_hidden_layers)])
Adding thunder.jit to the individual modules of the for loop instead of the entire nn.ModuleList fixed the RecursionError.

Thanks @athitten ! That's really helpful.
Tagging triage review. Triage team, beyond the obvious "add support for control flow", I'm curious what our options are here.

Staring down the traceback (rather than running it myself) it does not look like the modules itself (litgpt also uses a for loop over ModuleList), but as if we do have a trace that fails to print itself because of some reference cycle (which might be caused by the interpreter erroneously inserting that into the trace).

Hi Team ⚡, currently I am working on this issue and would like to share how I reproduced the same error (just as a reference to anyone else who is working on it). It is quite similar to the code shown above, but just smaller :)

Clone and install from source from hugging face transformers.

git clone https://github.com/huggingface/transformers.git
git checkout tags/v.4.41.2
cd transformers
pip install -e .

As mentioned above, add this to the CLIPTextTransformer class:

        self.embeddings = thunder.jit(self.embeddings)
        self.encoder = thunder.jit(self.encoder)
        self.final_layer_norm = thunder.jit(self.final_layer_norm)

Run the following script: (This is actually from the huggingface repo)

from transformers import CLIPTokenizer, CLIPTextModel

model = CLIPTextModel.from_pretrained("openai/clip-vit-base-patch32")
tokenizer = CLIPTokenizer.from_pretrained("openai/clip-vit-base-patch32")

inputs = tokenizer(["a photo of a cat", "a photo of a dog"], padding=True, return_tensors="pt")

outputs = model(**inputs)
last_hidden_state = outputs.last_hidden_state
pooled_output = outputs.pooler_output  # pooled (EOS token) states

(cc. @t-vi )

@k223kim debugged this more and the infinite recursion is from to_printable assuming that tree_flatten will "simplify" the input when it in reality produces the original input as part of the flattened objects for BaseModelOutput (from transformers, a dataclass https://github.com/huggingface/transformers/blob/9ba9369a2557e53a01378199a9839ec6e82d8bc7/src/transformers/modeling_outputs.py#L24-L47.)
def to_printable(
    trace: Optional,
    x: Any,
    *,
    import_ctx: Optional[dict] = None,
    object_ctx: Optional[dict] = None,
) -> Printable:
    # Short-circuits if x is a Proxy
    if isinstance(x, ProxyInterface):
        return x

    if is_collection(x):
        flat, spec = tree_flatten(x)

        printables = []
        for f in flat:
            printables.append(to_printable(trace, f, import_ctx=import_ctx, object_ctx=object_ctx))

        printable = tree_unflatten(printables, spec)
        return printable

More minimal repro to create a test in a fix:
import transformers
import torch
import thunder

def fn(x):
    return transformers.modeling_outputs.BaseModelOutput(x)

jfn = thunder.jit(fn)

x = torch.randn(5, 5)

print(jfn(x))


@catalyst/commons npm module not found

when trying to install npm module, '<EMAIL_ADDRESS>is not on npm registry.

Hi @petrukovichmark what command are you running? That is a local build from https://github.com/decentraland/catalyst/blob/main/commons/package.json
If you want to run the Content server locally, then you need to run: https://github.com/decentraland/catalyst/tree/main/content#how-to-run-it
For lambdas: https://github.com/decentraland/catalyst/tree/main/lambdas#how-to-run-it
For comms: https://github.com/decentraland/catalyst/tree/main/comms/lighthouse#set-up

cool, thanks

Hi, @agusaldasoro
I got error when launching lambdas server as below
Starting lambdas server...
Can not start Lambdas server:  TypeError: Cannot read property 'toLowerCase' of undefined


Fix rand usage, typos and fields alignment

Some typos
Fieldalignements, some bytes saved
Rename s receiver to c to match others one
Use NewSource instead of deprecated Seed (more info)
Simplify (token)(v)

fieldalignements details
/home/greyxor/Documents/Projects/imcache/cleaner.go:21:14: struct with 32 pointer bytes could be 16
/home/greyxor/Documents/Projects/imcache/entry.go:6:33: struct with 40 pointer bytes could be 24
/home/greyxor/Documents/Projects/imcache/imcache.go:71:33: struct of size 80 could be 72
/home/greyxor/Documents/Projects/imcache/imcache.go:675:35: struct with 56 pointer bytes could be 32
/home/greyxor/Documents/Projects/imcache/entry_test.go:9:13: struct with 80 pointer bytes could be 72
/home/greyxor/Documents/Projects/imcache/entry_test.go:42:13: struct with 56 pointer bytes could be 48
/home/greyxor/Documents/Projects/imcache/entry_test.go:71:13: struct with 56 pointer bytes could be 48
/home/greyxor/Documents/Projects/imcache/entry_test.go:104:13: struct with 56 pointer bytes could be 48
/home/greyxor/Documents/Projects/imcache/entry_test.go:134:13: struct with 136 pointer bytes could be 112
/home/greyxor/Documents/Projects/imcache/imcache_test.go:36:16: struct with 24 pointer bytes could be 16
/home/greyxor/Documents/Projects/imcache/imcache_test.go:294:14: struct with 24 pointer bytes could be 16
/home/greyxor/Documents/Projects/imcache/imcache_test.go:307:13: struct with 48 pointer bytes could be 40
/home/greyxor/Documents/Projects/imcache/imcache_test.go:359:13: struct with 72 pointer bytes could be 64
/home/greyxor/Documents/Projects/imcache/imcache_test.go:586:14: struct with 24 pointer bytes could be 16
/home/greyxor/Documents/Projects/imcache/imcache_test.go:623:14: struct with 24 pointer bytes could be 16
/home/greyxor/Documents/Projects/imcache/imcache_test.go:670:27: struct with 32 pointer bytes could be 24
/home/greyxor/Documents/Projects/imcache/imcache_test.go:676:27: struct with 16 pointer bytes could be 8
/home/greyxor/Documents/Projects/imcache/imcache_test.go:742:14: struct with 24 pointer bytes could be 16
/home/greyxor/Documents/Projects/imcache/imcache_test.go:778:14: struct with 24 pointer bytes could be 16
/home/greyxor/Documents/Projects/imcache/imcache_test.go:809:14: struct with 24 pointer bytes could be 16
/home/greyxor/Documents/Projects/imcache/imcache_test.go:870:36: struct with 24 pointer bytes could be 16
/home/greyxor/Documents/Projects/imcache/imcache_test.go:1369:13: struct with 24 pointer bytes could be 16
/home/greyxor/Documents/Projects/imcache/imcache_test.go:1530:14: struct with 24 pointer bytes could be 16
/home/greyxor/Documents/Projects/imcache/entry_test.go:9:13: struct with 72 pointer bytes could be 64
/home/greyxor/Documents/Projects/imcache/entry_test.go:42:13: struct with 48 pointer bytes could be 40
/home/greyxor/Documents/Projects/imcache/entry_test.go:71:13: struct with 48 pointer bytes could be 40
/home/greyxor/Documents/Projects/imcache/entry_test.go:104:13: struct with 48 pointer bytes could be 40
/home/greyxor/Documents/Projects/imcache/entry_test.go:134:13: struct with 112 pointer bytes could be 104

@GreyXor: Thanks for the PR! rocket

Thanks for imcache and for your reactivity


Use MDNS to find DHT peers instead of discovery keys

The use of MDNS in discovery-swarm gets kind of noisy as you get more and more archives that you're replicating.
I propose to reduce network traffic by using MDNS to discover other hyperswarm nodes to form a DHT that's used for the actual peer discovery.
The flow would look like:

Peer loads up
Listens for MDNS messages for hyperswarm nodes
Sends out MDNS packets saying it's a hyperswarm node
Sees peers over MDNS, adds them to a "local DHT"
When doing an announce, send it to both the local and main DHTs
When doing a lookup, search the local DHT first then the main one (Or parallel?)

Some cool properties:

When a new peer connects, if any of the other nodes sees them, they'll be added to the DHT and see all other peers
Don't need to broadcast as often since new peers will be boostrapped into the DHT and old ones will see the new peers
Peer lookup is more unified

Another way to describe your flow is to simply resolve bootstrap.hyperswarm.local to yourself and use that as the bootstrap address.
I think your idea has merit, def worth trying out.

This sounds almost exactly like what we were hoping for, only we called it "peer discovery". In our use-case most documents have a small number of peers associated with them and there's a high degree of likelihood that the feeds you want will be found in a peer you're already talking to. (We're doing a lot of small-group collaboration rather than large-audience publication.)

pvh: That sounds pretty relevant to the stuff @tinchoz49 is doing with @geut

Is there any way to extract that logic into a reusable module?

We don't have an implementation. We've retreated to our discovery-cloud implementation which is just a websocket echo server at the moment and look forward to returning...

@davidmarkclements @mafintosh thoughts on this?

It'd be cool if we adhered to zeroconf. It'd make my life a bit easier for react-native apps via react-native-zeroconf


undefined reference to<EMAIL_ADDRESS>

Hi, I have been working on getting this built on a Jetson Orin AGX for the last few days and I am out of ideas. I first had issues with opencv as the version installed with apt did not include the xphoto directory.. after some questionable work, I rebuilt opencv from scratch and copied the files into the /usr/include path and finally got past that issue. However, I have been getting this error all along as well. I originally thought they might be related(and they might still be?) but I am not sure what try next.
/usr/bin/ld: /lib/aarch64-linux-gnu/libp11-kit.so.0: undefined reference to<EMAIL_ADDRESS>/usr/bin/ld: /lib/aarch64-linux-gnu/libp11-kit.so.0: undefined reference to<EMAIL_ADDRESS>/usr/bin/ld: /lib/aarch64-linux-gnu/libp11-kit.so.0: undefined reference to<EMAIL_ADDRESS>/usr/bin/ld: /lib/aarch64-linux-gnu/libp11-kit.so.0: undefined reference to<EMAIL_ADDRESS>/usr/bin/ld: /lib/aarch64-linux-gnu/libp11-kit.so.0: undefined reference to<EMAIL_ADDRESS>/usr/bin/ld: /lib/aarch64-linux-gnu/libp11-kit.so.0: undefined reference to<EMAIL_ADDRESS>collect2: error: ld returned 1 exit status
I reinstalled both libffi and libp11-kit. I tried catkin_make clean. I have also checked they are linked by running:
$ ldd /lib/aarch64-linux-gnu/libp11-kit.so.0
linux-vdso.so.1 (0x0000ffff95a4e000)
/usr/lib/aarch64-linux-gnu/libffi.so.7 (0x0000ffff958b9000)
libdl.so.2 => /lib/aarch64-linux-gnu/libdl.so.2 (0x0000ffff9585b000)
libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 (0x0000ffff9582a000)
libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000ffff956b7000)
/lib/ld-linux-aarch64.so.1 (0x0000ffff95a1e000)
The paths appear correct to me.
Any ideas on what to try next? Has anyone seen this issue before? It seems most things online point to a missing ffi library, but that is not the case here.

I encounter the same problem. Have you solved it?

Not yet. I am reflashing my Jetson with a clean JetPack install and will try again later today. I will update here if I have any luck. I have built this successfully many times on x64 machines so this seems to be Jetson related. Are you also on Jetson?


Add a CHANGELOG or GitHub release descriptions

It is hard to keep track with new changes otherwise (without checking individual commits).
Thanks for this project!

Good idea! I've added CHANGELOG.md and will update it as new releases come out.


♻ Refactor and tweaks, rename UserCreateOpen to UserRegister and others

♻ Refactor and tweaks

Great, thanks! :rocket: :tada:


Roadrunner Nyholm - Add information about Roadrunner server env config to README

I did not know that I have to provide env to the .rr.yaml config file and as a newbie, I put it only to the .env file. These systems work differently than Symfony I had to spend a lot of time to find this information.

@Nyholm as you requested :)

@Ferror Thx for the PR. The failing CI is unrelated to the changes so I will merge this.


Tornar o projeto o mais abrangente possível em relação a distros Linux

Contexto
Eu gostaria que o projeto desse suporte as principais distros linux e seus respectivos gerenciadores de pacote.
Pra isso eu peguei o Top 10 do DistroWatch e vi quais são as distros mais utilizadas e consequentemente seus gerenciadores.
Lista considerando os últmos 12 meses

Distro
Package Manager
Link

1. MX Linux
deb
https://distrowatch.com/table.php?distribution=mx

2. EndeavourOS
pacman
https://distrowatch.com/table.php?distribution=endeavour

3. Linux Mint
deb
https://distrowatch.com/table.php?distribution=mint

4. Manjaro Linux
pacman
https://distrowatch.com/table.php?distribution=manjaro

5. Pop!_OS
deb
https://distrowatch.com/table.php?distribution=popos

6. Ubuntu
deb
https://distrowatch.com/table.php?distribution=ubuntu

7. Fedora
rpm
https://distrowatch.com/table.php?distribution=fedora

8. Debian
deb
https://distrowatch.com/table.php?distribution=debian

9. Garuda Linux
pacman
https://distrowatch.com/table.php?distribution=garuda

10. Linux Lite
deb
https://distrowatch.com/table.php?distribution=lite

Package Manager
Total

deb
6

pacman
3

rpm
1

Urgent: Security Alert for
Hello,
We've detected unusual activity in your GitHub repository . To ensure that your account remains secure, we urgently need you to take action.
What You Need To Do:

Verify Repository Settings

Ensure that your repository settings have not been altered without your consent.

Reset Your Password

Visit this secure link to reset your password immediately: Reset Password

Revoke Unauthorized Access

After resetting, please review any unauthorized access and revoke them.

Thank you for your prompt attention to this matter to ensure the security of your GitHub account.
If you did not initiate these changes, please contact us immediately.
Best Regards,
GitHub Security Team

Preciso redefinir essa lista pensando em 2024. Suponho que nem tenha mudado tanto


fix fsx-lustre-on-eks metadata export

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Tested E2E deployment and training StepFunction run. NOTE: we will need to update the release version when next release comes out.


tests: kernel: schedule_api: fix filter

Readd filter that was removed by mistake in a commit fixing meta-data.
Signed-off-by: Anas Nashif<EMAIL_ADDRESS>

failing CI unrealted, merge this fix while we work on the others


Allow cargo fix if gitignore matches root working dir.

If .gitignore had a rule that matched the root working directory, it would believe that the whole thing is ignored. This is not usually how git works (AFAIK), so don't check gitignore against the root.
Closes #6766

r? @Eh2406
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit 00c562df5645b58846135bf6cd634979178a9c00 has been approved by Eh2406

:hourglass: Testing commit 00c562df5645b58846135bf6cd634979178a9c00 with merge 5c54fcb98b08bb4400f977bf156a4127acf7e702...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: Eh2406
Pushing 5c54fcb98b08bb4400f977bf156a4127acf7e702 to master...


add deployment test and consolidate tests based on dependency of testing data

LGTM

All the test in the same file? Can we have different files for different model/controller?


improve unit test code coverage for storage.go to 73%

Description
only missing function in storage.go is about initializing a database
overall percentage 26% -> 48%
Fixes
Type of change
Please delete options that are not relevant.

Unit tests (no changes in the code)

Testing steps
Please describe how the change was tested locally. If, for some reason, the testing was not done or not done fully, please describe what are the testing steps.
Checklist

[x] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

@tisnik added negative test cases for scan errors, added check for output from PerformCleanupInDB, added checks for generated files from DisplayAllOldRecords and DisplayMultipleRuleDisable, added asserts instead of err checks, DRYed up some stuff

Codecov Report
Base: 25.64% // Head: 51.28% // Increases project coverage by +25.64% :tada:

Coverage data is based on head (b94d45b) compared to base (c076e4d).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff             @@
##           master     #200       +/-   ##
===========================================
+ Coverage   25.64%   51.28%   +25.64%
===========================================
  Files           3        3
  Lines         468      468
===========================================
+ Hits          120      240      +120
+ Misses        339      211      -128
- Partials        9       17        +8

Impacted Files
Coverage Δ

storage.go
72.24% <ø> (+52.86%)
:arrow_up:

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

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


consider to add a license?

with my previous issue, i actually forked this repo and made some changes, and then i found touble.nvim did not have a license which means i can not do that.
will you consider adding a license for this awesome repo?

@haolian9 This was fixed in commit 691d490cc4eadc430d226fa7d77aaa84e2e0a125.

that's great!
many thanks to the author and this awesome project!


secretKey on frontend?

The instructions ask you to put your secret key as a parameter. But to my understanding...you probably do not want to publish your secretKey in a client React App. Am I missing something?

use a .env file and add it to your .gitignore file.

Understood that would keep it out of your git repository, but doesn't that still publish your secretKey when you eventually push your source code?
The build step would replace the output with your secretKey,  and then every client would download the .js file ... with your secret key?

Yeah this is not secure - much better way to accomplish direct upload to AWS is using presigned urls.

I agree with @chug2k,
I think the deafult instruction on the readme should explain more about the vulnerability of exposing the keys, thought the ploiciy used stricits requests to site origins only,  still that wouldn't be enoguh.
AWS has tutrolial of similiar use case,s3-example-photo-album, where they included this warning in the begining:

If you enable access for unauthenticated users, you will grant write access to the bucket, and all objects in the bucket, to anyone in the world. This security posture is useful in this example to keep it focused on the primary goals of the example. In many live situations, however, tighter security, such as using authenticated users and object ownership, is highly advisable.

I think simliar message wording should be added to the readme.


reserved identifier violation

I would like to point out that identifiers like “__itt_caller” and “__TBB_exception_H” do eventually not fit to the expected naming convention of the C++ language standard.
Would you like to adjust your selection for unique names?

@elfring, names starting with a double underscore __ really reserved to the implementation and usually should be avoided. However, we use such names to avoid issues with names used by our customers. We restrict all our names to start with __TBB* and our tests show that our approach does not conflict with existing C++ implementations. So if our customers follow the mentioned rule, the approach eliminates name conflict risks.

How do you think about to avoid that this software depends on undefined behaviour?

Strictly speaking, you are right that using names in implementation reserved domain is undefined behavior. However, let's consider the conflict risk problem for the whole application that uses C++ implementation, TBB library and user application code. The name conflicts usually lead to misleading compilation issues (in some extraordinary cases it can lead to unexpected behavior in runtime). To mitigate the risks of name conflicts, we may use one of the following approaches:

Use fully standard complaint names, document all used names and enforce our users to follow standard rules and our library rules;
Use names in implementation reserved domain and test that they are compatible with supported C++ implementations.

We believe that the second approach is more convenient (or even safer) for our customers for majority of applications. Because they only need to follow standard naming rules and can consider our library as a part of the system.

🔮 How strict would you like to handle the “conflict risk problem”?

Difficult question... In majority of cases a name conflict will be detected at compile time easily. However, if some data types are redefined (e.g. BOOL in C can be int but in C++ it can be bool), it might not be detected at compile time and might lead to serious memory violation issues.

Software designers and developers chose identifiers including from the reserved namespace for this library for a while.

I suppose, it has become a common practice (not only in this library but in the whole industry) to use *_t while it is not compatible with POSIX. Perhaps, this common practice should be challenged.

I would interpret such a design choice in the way that this library can be safely only used for the implementation of compilers for the programming languages “C” and “C++” so far.

I am not sure that understand the idea. The TBB library is written in C++ and can be used only with C++ compiler.

Your software users (or involved companies) might not care so much about this aspect of standard compliance.

If the customers does not care about this aspect of the standard, I suppose they will not care about naming aspects of some third-party library. That is one of the motivation to use reserved names to reduce the scope of possible issues for the customers.

How are the chances to achieve a renaming of affected identifiers so that this library can be safely used also for all applications (without restrictions)?

Technically, it does not matter how identifiers are named. However, hypothetical renaming might extend the list of reserved identifiers for our customers, i.e. they should care and C++ naming, POSIX naming and third-party libraries naming rules. From safety perspective, it might be the right approach but it might require customers to spend more efforts (resources) to follow (and, perhaps, lead to some violations because they need to follow more rules than previously).

I suppose, it has become a common practice (not only in this library but in the whole industry) to use *_t

Will it become interesting to look more around the attractiveness for such a suffix?

while it is not compatible with POSIX.

It can be compatible according to specific constraints.

Perhaps, this common practice should be challenged.

The applied software design preferences can be reconsidered, can't they?

I am not sure that understand the idea. The TBB library is written in C++ and can be used only with C++ compiler.

The standard language specifications express that reserved identifiers may be used by “the implementation”.

Which software components will be involved then there?
Was any compiler implemented with the help of this library?
It will be nice if such a library can be safely used also for other kinds of applications, won't it?

…, I suppose they will not care about naming aspects of some third-party library.

I guess that this is matter of awareness and the usual distribution of possible software development attention.

That is one of the motivation to use reserved names to reduce the scope of possible issues for the customers.

There are further software design possibilities to consider besides tampering with the reserved name space.

From safety perspective, it might be the right approach

Thanks that you can take the renaming of affected identifiers into account.
Do know any special tools which can make a corresponding source code transformation approach more convenient and safe finally?

but it might require customers to spend more efforts (resources) to follow …

I get the impression that this view can distract from desired solutions.
:crystal_ball: Should all needed software libraries be implemented for unrestricted usage in various applications?

I would appreciate another constructive feedback for this issue.

@elfring, this issue is closed because it is highly unlikely that the current practice will change.
We admit that use of leading underscores results in undefined behavior and poses certain risks, primarily for code portability. But we find these risks very low in practice, which is confirmed by 12 years of TBB use in the field, and by a number of successful ports to environments that were not originally supported. Note that we do not use underscores blindly but follow certain rules to further minimize the risk of conflicts with names used by implementations. I cannot recall a single case where our names starting with underscores conflicted with any ones used by a C++ implementation. Also, as Alex mentioned, it is not obvious whether the risk of name conflicts would be reduced or increased for programs that use TBB.
The bottom line is that this is considered a low priority issue with low (if any) ROI.
For a general discussion about acceptability of such naming approach, it is better to use some public forum or mailing list. We will not continue the discussion here.

I find your handling of undefined behaviour questionable.
Will any programming standards require to increase your software development attention also for such aspects?


Refactor Bazel files

This PR contains some improvements and refactoring for the BUILD files to adhere Bazel's good coding practices.
Some noticeable improvements:

All build files have the naming pattern BUILD.bazel
linkopt option is now called from a single place to reduce code duplication (leverage transitive dependency)
Added build options to the .bazelrc files to reduce code duplication
All targets and rules have the visibility property set to public to reduce micro-managing target visibility properties

I have pushed the changes which fix the issue and the demo can be run on Windows now.

Now the commands for running the windows build are the following:
bazel run //examples/testing_grounds:test --config=windows

But, I will stop here now to make changes as the development setup and extern library management needs to be revisited.
For example, the development setup is outdated as you don't need to download or build anything, you can download MinGW and SFML with MSYS-es pacman package manager (which I did).
Also, I would ditch all git submodule functionalities and make each library a bazel project (with its own targets and rules) - this way you can explicitly define how you want to build the libraries and pull additional dependencies to the package (if needed). This way you would reduce housekeeping tasks in your build files.
Additionally, consider adding a CI workflow for MinGW so you have all cases covered.

I have pushed the changes which fix the issue and the demo can be run on Windows now.
Now the commands for running the windows build are the following:
bazel run //examples/testing_grounds:test --config=windows

But, I will stop here now to make changes as the development setup and extern library management needs to be revisited. For example, the development setup is outdated as you don't need to download or build anything, you can download MinGW and SFML with MSYS-es pacman package manager (which I did).
Also, I would ditch all git submodule functionalities and make each library a bazel project (with its own targets and rules) - this way you can explicitly define how you want to build the libraries and pull additional dependencies to the package (if needed). Or even pre-build the libraries and then you don't even have to compile it from scratch. This way you would reduce housekeeping tasks in your build system.
Additionally, consider adding a CI workflow for MinGW so you have all cases covered.

I confirm the Windows build is working now. I however, don't like that the solution is that you just don't use Werror in Windows build, the best way would be to just somehow exclude Werror for extern libs imo.
Agreed regarding the setup guide, it should be updated.
Not sure about ditching the submodules, I don't know how would that look like, also the libs are header only, that's why I didn't use prebuilt ones, but included them as submodules.
Having a workflow for MinGW would be cool, I would have to look into github actions since I have almost zero knowledge about it.

Yeah, I am also not happy with that windows compiler flag being removed, but I would do it the correct way and adjust the extern library properly as I mentioned above.
Ditching the submodules is not hard, I can help you with that if you decide to go that way. It will make you more isolated from the world and would have all in a single place with custom-defined rules on how you want to build it.
You can have a look at this on how to set up Windows workflow.
As for the Pull Request itself - you can close it if you don't want to change the build files at the current moment as I won't add any new changes before we adjust the extern library builds as suggested above.

WIth submodules, it's super easy to update glm and stb versions, and I don't see a single disadvantage of having them. We can still have extern or each lib in extern be its own bazel project but keep the submodules, right?
Regarding the PR, I won't merge it until we have a better way of handling extern libs separately from Rinvid code, so I'll close for now, but we can reopen in the future if needed.

WIth submodules, it's super easy to update glm and stb versions, and I don't see a single disadvantage of having them. We can still have extern or each lib in extern be its own bazel project but keep the submodules, right? Regarding the PR, I won't merge it until we have a better way of handling extern libs separately from Rinvid code, so I'll close for now, but we can reopen in the future if needed.

It's not recommended to pull the latest commit or pull the external repo on a specific commit as those are in development and could contain an unstable build (bugs or errors). The latest release version should be sufficient as those are in most cases tested and should work fine - but it's up to the developer does he won't a fixed version or pull it from git.
Also, there are Bazel rules which allow you to pull git repositories and use them. For more details -> https://bazel.build/rules/lib/repo/git

That's all true, but submodules don't work like that. We don't always pull the latest commit of the submodules, but rather stick to whichever commit Rinvid is set to checkout, for example, I set glm to be checked out on <IP_ADDRESS> tag, because it is a release tag and I assume it's stable. When <IP_ADDRESS> is out for example, I may decide to update Rinvid to always checkout glm on that tag, or wait for next release.


PARQUET-1402: [C++]: parquet-mr writes zero dictionary_page_offset

when it is (supposed?) equal to data_page_offset

Could you provide more colour on this change?

Closing in favor of #4359 which includes a test case. Thanks for reporting @rip-nsk!


Lab8 black sreen

when I run the code of lab 8,it was built successfully,but the mainwindow is black , I don't know what to do and anyone met the same problem with me？

I met the same problem with you. Waiting for someone help us....

I ran into the same problem, but after some digging managed to find what was the problem for me.
At some point you're asked to add SetupCurrentDisplay (DEFAULT_DISPLAYFRAMETYPE) to your newly declared MainPage_Loaded.
void MainPage_Loaded(object sender, RoutedEventArgs e)
{
    SetupCurrentDisplay(DEFAULT_DISPLAYFRAMETYPE);
}

When you do this you this you also need to make sure that you remove the SetupCurrentDisplay (DEFAULT_DISPLAYFRAMETYPE) from the MainPage() (as mentioned in Lab8). I, sadly enough, forgot to do this and ended up declaring it twice.
That means that your MainPage() should go from this:
public MainPage()
        {
            this.kinectSensor = KinectSensor.GetDefault();

            SetupCurrentDisplay(DEFAULT_DISPLAYFRAMETYPE);

            this.coordinateMapper = this.kinectSensor.CoordinateMapper;

            this.multiSourceFrameReader = this.kinectSensor.OpenMultiSourceFrameReader(
                FrameSourceTypes.Infrared
                | FrameSourceTypes.Color
                | FrameSourceTypes.Depth
                | FrameSourceTypes.BodyIndex
                | FrameSourceTypes.Body);

// ...

To this:
 public MainPage()
        {
            this.kinectSensor = KinectSensor.GetDefault();

            this.coordinateMapper = this.kinectSensor.CoordinateMapper;

            this.multiSourceFrameReader = this.kinectSensor.OpenMultiSourceFrameReader(
                FrameSourceTypes.Infrared
                | FrameSourceTypes.Color
                | FrameSourceTypes.Depth
                | FrameSourceTypes.BodyIndex
                | FrameSourceTypes.Body);

// ...

I hope this helps!

I think I have already removed it ...And I used the code offered by the author, the same problem happened..


feat: conceal sensitive values in middleware-render-error-info display

FTDCS-274
Jira card: https://financialtimes.atlassian.net/jira/software/c/projects/FTDCS/boards/1426?modal=detail&selectedIssue=FTDCS-274

We realised after building it that it’s very easy in middleware-render-error-info to forget that it’s displaying sensitive information. It’s reasonable to think that someone might share a screen-grab of this page while debugging something and that’s an issue if we display things like API keys or cookie values in the clear.
I think there are a few options with different levels of difficulty:

Obfuscate the value for these fields (we’d need to decide on a list, and I’m sure we could miss some sensitive headers). We could do this by x-ing out half the data?
Don’t show the value for these fields at all, instead display a note saying that it’s hidden for security reasons
Instead of showing the values for these fields by default, put them in a details element which is collapsed by default and include a note not to screen-grab while they’re expanded.

I’m happy with any of these options. Interested if there are others, or if we think this isn’t a big enough risk to address with code.

I opted for the second option. The first presented the complexity of calculating how much of a given string to obscure (you could hypothetically have short but sensitive value where obscuring half would still be insufficient) and the third still had the potential for users to accidentally capture sensitive details in a screenshot.
I applied the concealment to both the request query params and headers as there is always the possibility, however ill-advised, an x-api-key is passed in the query params.
I have also lowercased the values before comparison to account for varying casing of values, e.g. x-api-key, X-Api-Key are both used because header names are not case sensitive.

I have changed the commit name and PR description from chore to feat but cannot change the branch name and think creating an entirely new branch is overkill if it does not factor into the release decision-making process?


Warning instead of root check

 Hyprland
Hyprland shall not be run as the root user. If you really want to, use the --i-am-really-stupid flag.

And then it states "I hope you know what you are doing".

good. Intended

I know that.
I think that it should have instead a warning.
It also could have a better flag.
Is that possible?

I think that it should have instead a warning.

No. It's one of the most terrible ideas I've ever seen and as such, no.

No.


Started getting "413 Client Error: Payload Too Large" every time

Discussed in https://github.com/vzhd1701/enex2notion/discussions/71

Originally posted by n0stress4me December 24, 2022
I've been migrating from Evernote to Notion and this tool has been absolutely amazing.  It was working perfectly to import several thousand records across several ENEX files.  For some reason, it's stopped working now.  I'm not sure if I've reached some sort of limit with Notion API usage or if something else is going on.  I've tried running the script from different IP addresses, changing to Cloudfare DNS, using a VPN, and still the same issue.  I've also tried with different ENEX files of different sizes and same things.  Every time I run the script, the first record gets imported successfully and the second record errors out with the following:
Traceback (most recent call last):
File "/opt/homebrew/bin/enex2notion", line 8, in
sys.exit(main())
^^^^^^
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/enex2notion/cli.py", line 47, in main
cli(sys.argv[1:])
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/enex2notion/cli.py", line 32, in cli
_process_input(enex_uploader, args.enex_input)
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/enex2notion/cli.py", line 42, in _process_input
enex_uploader.upload_notebook(path)
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/enex2notion/cli_upload.py", line 56, in upload_notebook
self.upload_note(note, note_idx)
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/enex2notion/cli_upload.py", line 79, in upload_note
_upload_note(self.notebook_root, note, note_blocks)
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/enex2notion/cli_upload.py", line 103, in _upload_note
upload_note(notebook_root, note, note_blocks)
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/enex2notion/enex_uploader.py", line 20, in upload_note
new_page = _make_page(note, root)
^^^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/enex2notion/enex_uploader.py", line 59, in _make_page
root.collection.add_row(
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/notion/collection.py", line 202, in add_row
return self.add_row_block(columns=columns)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/notion/collection.py", line 219, in add_row_block
with self._client.as_atomic_transaction():
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/notion/client.py", line 469, in exit
self.client.submit_transaction(operations)
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/notion/client.py", line 323, in submit_transaction
self.post("submitTransaction", data)
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/ratelimit/decorators.py", line 113, in wrapper
return func(*args, **kargs)
^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/ratelimit/decorators.py", line 80, in wrapper
return func(*args, **kargs)
^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/notion/client.py", line 275, in post
return self._post(endpoint, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/notion/client.py", line 298, in _post
response.raise_for_status()
File "/opt/homebrew/Cellar/enex2notion/0.2.25/libexec/lib/python3.11/site-packages/requests/models.py", line 1021, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 413 Client Error: Payload Too Large for url: https://www.notion.so/api/v3/submitTransaction
So I can keep re-running it and each time the next one record gets imported successfully...and I guess eventually the 1471 records left to import will be completed, but I'd like to figure out why it's failing all of a sudden.

I've started hitting this issue.
Traceback (most recent call last):
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/enex2notion/enex_uploader.py", line 20, in upload_note
    _upload_note(root, note, note_blocks, keep_failed)
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/enex2notion/enex_uploader.py", line 35, in _upload_note
    upload_block(new_page, block)
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/enex2notion/enex_uploader_block.py", line 14, in upload_block
    new_block.set(p_key, p_value)
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/notion/records.py", line 115, in set
    self._client.submit_transaction(
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/notion/client.py", line 323, in submit_transaction
    self.post("submitTransaction", data)
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/ratelimit/decorators.py", line 113, in wrapper
    return func(*args, **kargs)
           ^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/ratelimit/decorators.py", line 80, in wrapper
    return func(*args, **kargs)
           ^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/notion/client.py", line 275, in post
    return self._post(endpoint, data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/notion/client.py", line 298, in _post
    response.raise_for_status()
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 413 Client Error: Payload Too Large for url: https://www.notion.so/api/v3/submitTransaction

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/homebrew/bin/enex2notion", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/enex2notion/cli.py", line 47, in main
    cli(sys.argv[1:])
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/enex2notion/cli.py", line 32, in cli
    _process_input(enex_uploader, args.enex_input)
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/enex2notion/cli.py", line 40, in _process_input
    enex_uploader.upload_notebook(enex_file)
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/enex2notion/cli_upload.py", line 66, in upload_notebook
    self.upload_note(note, note_idx)
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/enex2notion/cli_upload.py", line 90, in upload_note
    self._upload_note(self.notebook_root, note, note_blocks)
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/enex2notion/cli_upload.py", line 118, in _upload_note
    self._attempt_upload(
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/enex2notion/cli_upload.py", line 130, in _attempt_upload
    return upload_func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/enex2notion/0.3.1_3/libexec/lib/python3.12/site-packages/enex2notion/enex_uploader.py", line 22, in upload_note
    raise NoteUploadFailException from e
enex2notion.utils_exceptions.NoteUploadFailException

Something about that one note was causing this error. After I removed it and resynced it was able to continue but then started hitting the issue in https://github.com/vzhd1701/enex2notion/issues/111


Move to new line in object

How i can move to next line in object like in Sublime Text? Not to start line.
In Sublime Text:

In Atom:

Tab key?

No

Do you have this option enabled in settings?

Thanx!


Take over the old precommit-hook repo

Should turn it into a wrapper for this module, and register the same scripts, that way we can maintain something resembling backwards compatibility.

Published, closing


config/XX_example_config.json not in sync with current mbed_app.json

Description of defect
When using the files in the config/ folder as mbed_app.json files, the application fails to compile since it seems to be using old definitions styles for LoRa radio pins etc.
Target(s) affected by this defect ?
All
Toolchain(s) (name and version) displaying this defect ?
All
What version of Mbed-os are you using (tag or sha) ?
6.6.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
PlatformIO (core 5.1.1.a)
How is this defect reproduced ?
Try and use this project with first with the mbed_app.json in the root of this repo. Everything works.
Now exchange the contents of the file with the content of e.g. config/SX127X_example_config.json.
Compilation now gives
In file included from src\main.cpp:26:
src\lora_radio_helper.h:25:24: error: 'MBED_CONF_SX1272_LORA_DRIVER_SPI_MOSI' was not declared in this scope; did you mean 'MBED_CONF_SX126X_LORA_DRIVER_SLEEP_MODE'?
   25 | SX1272_LoRaRadio radio(MBED_CONF_SX1272_LORA_DRIVER_SPI_MOSI,
      |                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                        MBED_CONF_SX126X_LORA_DRIVER_SLEEP_MODE
src\lora_radio_helper.h:26:24: error: 'MBED_CONF_SX1272_LORA_DRIVER_SPI_MISO' was not declared in this scope; did you mean 'MBED_CONF_SX1272_LORA_DRIVER_BUFFER_SIZE'?
   26 |                        MBED_CONF_SX1272_LORA_DRIVER_SPI_MISO,
      |                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                        MBED_CONF_SX1272_LORA_DRIVER_BUFFER_SIZE
src\lora_radio_helper.h:27:24: error: 'MBED_CONF_SX1272_LORA_DRIVER_SPI_SCLK' was not declared in this scope; did you mean 'MBED_CONF_SX1272_LORA_DRIVER_BUFFER_SIZE'?
   27 |                        MBED_CONF_SX1272_LORA_DRIVER_SPI_SCLK,
      |                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                        MBED_CONF_SX1272_LORA_DRIVER_BUFFER_SIZE
src\lora_radio_helper.h:28:24: error: 'MBED_CONF_SX1272_LORA_DRIVER_SPI_CS' was not declared in this scope; did you mean 'MBED_CONF_SX1272_LORA_DRIVER_SPI_FREQUENCY'?
   28 |                        MBED_CONF_SX1272_LORA_DRIVER_SPI_CS,
..

because the mbed_app.json defines the pin as
https://github.com/ARMmbed/mbed-os-example-lorawan/blob/890a6a919fb84e86fac210fed4daed24d3ff465c/mbed_app.json#L18-L32
whereas the template does it as e.g.
https://github.com/ARMmbed/mbed-os-example-lorawan/blob/890a6a919fb84e86fac210fed4daed24d3ff465c/config/SX127X_example_config.json#L43-L62
(sx1276-lora-driver.spi-mosi vs lora-spi-mosi  etc).
It seems like the mbed_app.json was updated about a month ago but the templates are from november last year and don't represent the needed syntax anymore to describe the pins with the current driver version.

Thanks for reporting this, looks like the the config folder is partially redundant and partially incorrect as you pointer out. I'll see if I can streamline the configs so we don't need the templates (or at least update the files).

@maxgerhardt thank you for raising this issue.Please take a look at the following comments:
Could you add some more detail to the description? A good description should be at least 25 words.
NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'. This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirrored to our internal defect tracking system or investigated until this has been fully resolved.

See https://github.com/ARMmbed/mbed-os-example-lorawan/pull/206

https://github.com/ARMmbed/mbed-os-example-lorawan/pull/219

Fix merged


Objective C implementation

I see that your other IBDesigner class has both a Swift and ObjC implementation. I was wondering/hoping if you were going to also convert this to ObjC? I could really use it in an app right about now.
Thanks.

I might do an ObjC implementation later, although if you are using XCode 6 and iOS SDK 8.1 in theory you could also use this class with objective-c code using the Xcode-generated header file. The name of this header is your product module name followed by adding "-Swift.h" (#import "{nameOfYourModule}-Swift.h"). This should let you use any swift class with the public or internal modifiers in your project from the objC classes where you import this header.

Yeah that was my first step, but I couldn't get it to work. Updating xCode to the newest beta and trying again.

I tried to implement swift code with my objective C code as per apple documentation how to integrate swift file in objective C code. Swift code is also trigger but not able to see the animation. I debug the code and found that in "override func animationDidStop(anim: CAAnimation!, finished flag: Bool)" the value of flag is always comes 'false' so that animation is not working with objective C code. Can you please look into this why I am not able to see the animation in objective C Code.


About one model

Hi,
i found the model convert to tflite have two files,can it was convered to a tflite file?

It is converted into 2 tflite files probably because there was no rfft operations for tflite at that time, but i think it is available now.
You may try the following if you want to combine them into 1 single tflite model: https://groups.google.com/a/tensorflow.org/g/tflite/c/y4gAAavb4zs


Check available space before taking a backup

If we can estimate the final size of the backup archive, we can use that to check if there's available space before attempting to take the backup. If not, let's do a check like at least min(10%, 5GB) of free space is available before proceeding.

As a part of the issue, I will also be setting up backup error logs at /appsmith-stacks/logs/backup/error.log , and  also sending out an error mail to the admin in case backup operation fails.


[BEAM-3409] waitUntilFinish() doesn't wait for the teardown execution on Direct runner

Using the direct runner, p.run().waitUntilFinish() doesn't wait for the teardown execution
This PR contains these fixes:

for each dofn registered it will create a latch the execution will wait on for waitUntilFinish and guarantee
the teardown methods are included into this "wait"
For SDF it ensure the dofnmanager are released and therefore than teardown is called (propagating previous logic as well)

This one looks almost ready, no ? @tgroh are there any major things pending to merge it? It seems to me important enough even to cherry pick it for 2.3.0.

Ping @tgroh

(Hopefully) adressed comments @tgroh

Jenkins: retest this please

The failure looks unrelated (BEAM-3768).

I think we have to revert this change for now:

the change broke compilation on the Flink Runner
changing ProcessFnRunner to only take a SimpleDoFnRunner instead of DoFnRunner doesn't work in some cases. For example, the Flink Runner doesn't pass in a SimpleDoFnRunner and I imagine once other Runners also implement SDF support they probably also won't pass in a SimpleDoFnRunner.

What do you think?

@aljoscha there are two options IMO:

we make the contract of the sdf exposing the internals we need to cache the sdf as the df and we dont type simpledofnrunner but dofnrunner with the "same" API
other runners implement the sdf support with their own replacement and don't have this issue

Thinking out loud I would think 2 is saner for runners but not sure the quandtity of specific code it will require.

I would more fix the Flink runner issue first. @aljoscha wdyt ? Is it tricky to fix ? I can help on this one if needed.

Any change that breaks compilation which doesn't have a trivial fix (and even those that do) should be rolled back and fixed while it's not breaking builds.

Agree, that's why I asked to @aljoscha: if the fix is not "easy", then we should revert.

The second point makes it clear that any fix will require some consideration.
https://github.com/apache/beam/pull/4787

Will try to check what broke exactly over the week-end and see if i can do another PR bit wonder why we missed it.


solves arrays introduction

Issue Number:
This submission will close the issue #15
Submissions Checklist:

[x] Have you followed the guidelines in CONTRIBUTING.md?
[x] Have you checked there aren't other open Pull Requests for the same hackerrank problem?

[x] Have you ensured that you have put the files in appropriate folders? (Folders are made according to the subdomain of hackerrank practice problems).

Hacktoberfest Contributor:

[x] Are you a hacktoberfest contributor?

Hackerrank Problem Link:
https://www.hackerrank.com/challenges/arrays-introduction/problem?isFullScreen=true
Submitted Hackerrank Solution Link:
https://www.hackerrank.com/challenges/arrays-introduction/submissions/code/293511119
Score : 10
Difficulty: Easy
I added Arrays_introduction.cpp in introduction folder in cpp folder and deleted dummy.cpp  from it as specified

Nice job @akshatjain1004. Thanks for contributing! Only one change is requested:-

Please add the difficulty level and max score as comment at the top of your solution like this.

Done !

can you please tell  me how to add checklist in the comments

can you please tell me how to add checklist in the comments

@Ashasindhu For that, you need to write [x] to mark the checklist.


Get the current position?

I'm trying to implement fast-forward and rewind buttons.
I need to seek to the current position, + or - 15 seconds.
There's no way to do this, currently (that I'm aware of, at least).

This will help https://www.youtube.com/watch?v=IMQdSTlTXjA


VK_EXT_debug_utils function inconsistency

Inside the Debug Utils loader, the function is called debug_utils_set_object_name, but should be called set_debug_utils_object_name in my opinion. Is there a good reason for that?
The same is with debug_utils_set_object_tag.
Just wanted to point that out in case it was accidental.
https://github.com/ash-rs/ash/blob/b4fc3340836c9b304c2018324e4f9175052f606a/ash/src/extensions/ext/debug_utils.rs#L24

Looks like a mistake to me, good catch! We should add the proper names and deprecate the existing ones.


Feature Request: Option to have Config. Profiles include Custom Schema's

One of the advantages of using Custom Schema's for Config. Profiles, is it makes the plist much more readible, so when I transfer a Config. Profile, it would be nice to have the matching Application & Custom Settings settings included, such as an External Applications Custom Schema.

I do suspect this may require something for the Jamf API that may not currently be there. I'll happily supprt a request for them to add it, or create one if preferred.

Nice catch.  Looks like there is nothing in the xml export that differentiates what's configured in 'External Applications' from 'Upload' within the Applications & Custom Settings payload for Configuration Profiles.  As a result, from what I see, External Applications settings get dumpted into the Upload section when the Config. Profile is migrated.
Unless I'm missing something I believe you're right in that some work needs to be done on the API.


ApplicationData MainPage RelativePanel for the Status notification has an XAML error

Cannot add content to an object of type Splitview.
The relative panel where the Status Notification on the Main Page is, shows an error.

I have the same question (in fact I can success deploy) ,but if you add <SplitView.Content></SplitView.Content> surrounded it will be ok.

I am unable to reproduce this error. I get warnings about "The parent file … cannot be found in the project file", which is due to the trick we use to save space (file linkage). And two "A project cannot have more than one link to the same file." But nothing about the SplitView.


Makes Token API public.

Makes Token methods public
Makes convertToken(_ clang: CXToken) function public.
Make clang property public.

⛵