frequency and duty cycle?

by any chance did you record the frequency and duty cycle of the Rif6 Cube remote? I have a Rif6 and I am missing the remote, as I am sure many are. I am working on getting the Flipper Zero to work with the Rif6 Cube.
The parsed hexedecimal codes don't seem to work. with the Flipper Zero. or maybe it is an address issue?
but I can send the raw data. however when I try a frequency of 38740 and duty cycle of 0.330000 nothing happens.
Thanks!

AHH! I got a raw file working using flipper zero.
here is example:
name: Power type: raw frequency: 36045 duty_cycle: 0.330000 data: 9024 4506 570 582 542 582 518 606 518 606 518 606 518 606 518 606 518<PHONE_NUMBER> 548 1698 546 1700 546 1700 546 1698 546 1700 546 1696 548 1702 570 1674 546<PHONE_NUMBER> 546 606 542 582 542<PHONE_NUMBER> 546 610 520<PHONE_NUMBER> 570<PHONE_NUMBER> 546 1698 570 1674 572<PHONE_NUMBER> 546


[Bug] attribute 'lib' missing when attempting to use stylix

I'm using stylix in a nix config, and whenever I try to evaluate my system configuration, it errors out.
The error is:
       error: attribute 'lib' missing

       at /nix/store/lbgfhradyynfljgmv9bywhg9h3p25qyf-modules/chromium/nixos.nix:5:5:

            4|   options.stylix.targets.chromium.enable =
            5|     config.lib.stylix.mkEnableTarget "Chromium, Google Chrome and Brave" true;
             |     ^
            6|

I don't know what is causing this problem, but if you can help, that would be much appreciated. Please let me know if there are any other details you need.

Yes I am. I will push my code changes to my forge and send a link to the relevant files.

Ok, so

The repo is here
The relevant flake.nix lines are here. These pull in the stylix module from inputs and call the configuration file for the host
The stylix config for the host is imported on line 24 of the configuration.nix file listed above. All options are taken directly from the documentation. I hope this helps, please let me know if there is other relevant documentation I can provide.

This has been reported before (#20), although it was never clear what caused it.
I would assume something outside of Stylix is the problem? You have a lot of flake inputs, and the latest commit works fine with a minimal config.
If this is the case, perhaps moving our utils into the config.stylix namespace rather than config.lib would avoid interference? Or injecting them into the real lib, if that is possible. However, these would both be breaking changes.

Well, I don't know what exactly the problem would be, but I would be glad to test any potential changes. I may fork and try to put everything in a config.stylix namespace and see if that works.

Maybe it's due to the fact that config is not computed yet when the options are evaluated (it should be fully lazy and work, but I admit not liking depending on things in config for the structure of options).

So, I ran into a similar problem and I've got some debugging information that may help.
The error I received was:
       error: attribute 'xserver' missing

       at /nix/store/23gl8kb384mgqm0ys6bvcbhdpknfjlrm-modules/gnome/nixos.nix:16:17:

           15|       default = config.stylix.autoEnable
           16|              && config.services.xserver.desktopManager.gnome.enable;
             |                 ^
           17|     };

Now, if I--before I even load stylix--set stylix.autoEnable = false I no longer get the error. So I removed the disabling of autoEnable and started digging a bit. Dropping into the debugger at that point showed me that the nixos modules had yet to load and populate config with their settings/defaults. There were only other pieces of my config in there. I don't have GNOME enabled (nor xserver) so they weren't populated by my config either.
The default of the option for the GNOME theming feels suspect. I don't have any specifics or extensive experience writing nixModules to back that statement up, but using config in the options hash might be tempting the recursive gods to smite you. :stuck_out_tongue_closed_eyes:
If I'm not mistaken, that default needs to evaluate as the module loads which is why the autoEnable = false short-circuited the check. If the GNOME / xserver bits load first or the user sets those values themselves, then there's no problem because it has a value to read (either constant false or the user's preference) rather than an evaluated default.
In an effort to prove this out, I walked stylix back to ba324393e9414f57a2d0ba5a1edee5cd02b8af18 and reevaluated the flake. I ended up with this error:
       error: attribute 'mkEnableTarget' missing

       at /nix/store/prq3jjd62gxlb87nlnppnjc9rxmi8rxy-modules/gnome/nixos.nix:7:5:

            6|   options.stylix.targets.gnome.enable =
            7|     config.lib.stylix.mkEnableTarget "GNOME" config.services.xserver.desktopManager.gnome.enable;
             |     ^
            8|

Different, yes, but still in the GNOME module. I went one further step and walked it back to ce781e1d963311216b2837e014f522c3620f0639.
The evaluation succeeded.
My bone-headed suggestion would be to set a default of true/false everywhere and use lib.mkIf around the actual changes to evaluate later in the cycle to avoid the issue. Something like: lib.mkIf (cfg.autoEnable || cfg.gnome.enable) and see if that doesn't fix the issue. I'm going to fork stylix shortly to try it out for myself and see if it works.

Nope. Didn't work. I do not understand the magic. Hopefully meaning can be found in the above...

Couldn't leave it alone. This seems to be work great:
  options.stylix.targets.gnome.enable =
    lib.mkOption {
      description = lib.mdDoc "Whether to style GNOME";
      type = lib.types.bool;
      default = config.stylix.autoEnable
             && (config.services.xserver.desktopManager.gnome.enable or false);
    };

Gleaned from here: https://nixos.org/manual/nix/unstable/language/operators.html#attribute-selection

Is this still an issue?

Sort of, new problems have arisen that hit before this problem so I'm not 100% sure if it's gone.
The defaults in a lot of places are breaking because recursion is trying to use the default before the definition the default is based upon exists.
The latest instance I get (w/ commit 4da2d793e586f3f45a54fb9755ee9bf39d3cd52e)  is:

       error: attribute 'programs' missing

       at /nix/store/hqjk2q12m84v1aqyr9df7i34w99rraag-modules/nixvim/nixvim.nix:17:50:

           16|   config = lib.mkIf ((config.programs ? nixvim) && config.stylix.targets.nixvim.enable) (
           17|     lib.optionalAttrs (builtins.hasAttr "nixvim" options.programs) {

This problem can be worked around by shimming in a module prior to stylix that just defines an empty options.programs = {} which is enough to make the defaults get passed so that loading can continue. It will eventually evaluate correctly so the fix just tries to break an implicit load-order dependency.
Why commit 4da2d793e586f3f45a54fb9755ee9bf39d3cd52e you ask? Well, the commit AFTER that creates a separate problem:
       error: attribute 'mkEnableTarget' missing

       at /nix/store/pwivl3092cg504g6m06y3mns0h5343v2-modules/nixos-icons/nixos.nix:7:5:

            6|   options.stylix.targets.nixos-icons.enable =
            7|     config.lib.stylix.mkEnableTarget "the NixOS logo" true;
             |     ^
            8|

This one doesn't have a simple work around.

@jboyens I'm also running into the same issue with mkEnableTarget missing. From my testing, modules that set conig.nixpkgs.overlay are causing the breakage. These are the nixos-icons and gnome modules.

I have also encountered this issue. In my case, simply adding documentation.nixos.includeAllModules = true; to the configuration results in this error. Not that I particularly care about enabling that option, but I guess it might be of interest.


Cursor on buttons

Not sure if intended, but should the cursor change to a pointer when hovering over button? If so, I can PR for it, just wanted to see what intended behavior is!

Oh yeah, you're right, oops! I didn't even notice that, you have a good eye for detail. It's not the intended behaviour :)

Awesome, I'll try and submit a PR tomorrow :)

@98mprice I believe it should be good!

@KeevanDance Thank you! Works beautifully :)


Regenerated models from OWL

This commit is automatically generated from REC-OWL.
The translation mechanism has shifted the order of some properties compared with the manually modified DTDL, but the semantic meaning should remain unchanged to the existing version.
With the exception of Luminarie;2 which was removed in favor of in-place-version-update on the original Luminarie.json

Oh, one more difference; as discussed per email, this version of Luminaire uses "mounting" rather than "mountingType", for consistency with some other interfaces in the ontology (ITRack, WirelessAccessPoint).


Add test ReadWhileOverwriting

cc  @mihaimaruseac @vnvo2409 merging https://github.com/tensorflow/tensorflow/issues/42597 into the HDFS modular filesystem implementation


[SC-444] Custom errors

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

20 of 21 (95.24%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.889%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contracts/ERC20Farmable.sol
5
6
83.33%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
135

Relevant Lines:
149

💛  - Coveralls


Component content model continued - third sprint

This work is ongoing across multiple sprints.  Related issues:
Sprint 21-16:  #6772
Sprint 21-17:  #6847
Moving forward, let's continue to pick components from the Top priority list, and clean up the content model for them
[List of components TBD]
Acceptance criteria
Aim to finish 2-4 component content models. Recommend more complex components so we can prepare for any additional complexity that the tables need to accommodate.

Content models drafted: https://ibm.box.com/s/ye8a12p66jrdocx8wyfob5yd74yd1a75
Button group
Callout quote
Callout w/media
Content item horizontal
Filter panel
Horizontal rules
Language Selector
Layout
Lead space
Lead space block
Lead space search
Leaving IBM
Link list
Link list section
Link with icon
Locale modal - region
Locale modal - language
Logo grid
Pictogram item
Quote


Add issues from clinic on 4 June

These were issues encountered during a review of a service on 4 June:

Missing label
Inappropriate legend
Missing h1
Page title too simple
Invalid label
Input prefix

Reviewed together


Datatemplating

In XAML it is quite easy to use datatemplate on items.
In Razor, it does not seem possible to do it without including an external view/component.
It is quite often that I get several foreach on a page, with the same kind of items, and using razor, I have to repeat the same template several times, it is not very handy.
I would see something similar to functions:
@templates {
     EventItemTemplate(string name, DateTime time, string place) {

@name

@time.ToString("g")

@place

     }
}

Coming events and in progress

    @foreach(var e in events.Where(e2=>e2.EndTime > DateTime.UtcNow))
    {
        @EventItemTemplate(e.Name, e.Start, e.Place)
    }

Past events

    @foreach(var e in events.Where(e2=>e2.EndTime < DateTime.UtcNow))
    {
        @EventItemTemplate(e.Name, e.Start, e.Place)
    }

It would highly simplify the display of a structure like this:
building.cs
public class Building
{
    public string Address {get;set;}
    public List<Floor> Floors {get;set;}
}
public class Floor
{
    public string Number {get;set;}
    public List<Premise> Premises {get;set;}
}
public class Premise
{
    public string Door {get;set;}
    public string Owner {get;set;}
    public List<string> Residents {get;set;}
}

building.cshtml
@templates {
     BuildingTemplate(Building b) {

              <div<EMAIL_ADDRESS>

               @foreach(var f in p.Floors)
               {
                  @FloorTemplate(f)
               }

     }
     FloorTemplate(Floor f) {

              <div<EMAIL_ADDRESS>

               @foreach(var p in f.Premises)
               {
                  @PremiseTemplate(p)
               }

     }
     PremiseTemplate(Premise p) {

              <div<EMAIL_ADDRESS>              <div<EMAIL_ADDRESS>

               @foreach(var r in p.Resident)
               {
                     @r
               }

     }
}

    @foreach(var b in Model.BuildingsLeft)
    {
        @BuildingTemplate(b)
    }

    @foreach(var b in Model.BuildingsRight)
    {
        @BuildingTemplate(b)
    }

It may allow recursive templates
@templates {
     CommentItemTemplate(CommentViewModel comment) {

By: @name

@time.ToString("g")

              @if(comment.Comments?.Count>0)
              {

                  @foreach(var c in comment.Comments)
                  {
                          @CommentItemTemplate(c)
                  }

              }

     }
}

Comments

    @foreach(var c in Model.Comments)
    {
        @CommentItemTemplate(c)
    }

In that specific case, component may be a better choice of implementation, but that is just an example.
Globally defined c# variables may be available or not, depending on language constraints. If not available, they can still be passed as parameters anyway.
It seems quite clean to me, does it conflict the current language in any way?

Hey I found this issue searching for the same problem. So to be clear is there currently a way to re-use (or declare in some central location) component templates?

@legistek Component templates are RenderFragments, which you could create centrally and reuse.

Hey @danroth27 I can see how you would do it in C# code by making a lambda/delegate. But I should have specified that I'd like to declare them in the cshtml markup, yet not directly inside the component that's using it. I couldn't see any of the tutorials or examples showing how to do that. Is that possible now?
Basically I want to do the equivalent of a WPF DataTemplate defined as a StaticResource.

@legistek Right, we don't have a fully comparable data template experience to what WPF has. I was simply pointing out what we have available today.

Thanks no worries, the code method is a useful workaround for sure.

I should also point out, it's easy enough to create a component for each "reusable" data template, give it a DataContext parameter of your own, and then declare it as the only element in your actual component template.

@legistek It is not as explicit as in-view DataTemplating, but you may create a partial view in include it using
@await Html.PartialAsync("/MyViewPath/_MyPartialView.cshtml", new {param1 = p1, param2 = p2, param3=p3})

We do now support something very much like this: https://github.com/dotnet/AspNetCore.Docs/blob/1e199f340780f407a685695e6c4d953f173fa891/aspnetcore/blazor/webassembly-performance-best-practices.md#defining-reusable-renderfragments-in-code


[BugFix] persist grant/revoke role and support grant impersonate to role (#10596)

Support GRANT IMPERSONATE ON user TO ROLE role and REVOKE IMPERSONATE ON user FROM ROLE role.
Since the role model will be refactored later, I'm simply restoring impersonate privileges of a role in a simple Set.
Persist the relationship between role and user after GRANT role To user. The previous implementation will lose this metadata.

Fixes #10513
Fixes #10691
manully cherry-picked from 4d7266f883d6606b923a722a12630db0d3b9a1aa

run starrocks_fe_unittest


Fix compilation errors

It looks like there's been some syntax and function signature changes in Roc since the last time this code was worked on. I've upgraded this code now.

True, thank you! These are nice syntax changes, too, I'm happy to see them. 🙂


fetching next pages and removed ads

Rename your file by removing Turkish special letters like ğ, ş, ı, ç, ö, ü.


Update app.yaml to work with latest ruby

Note that without this addon, the tutorial is currently broken.  See b/365178099
Problem
I'm running this tutorial https://cloud.google.com/ruby/rails/using-cloudsql-postgres and it appears unable to run gcloud app deploy. The rrror is:
╔════════════════════════════════════════════════════════════╗
╠═ Uploading 2777 files to Google Cloud Storage             ═╣
╚════════════════════════════════════════════════════════════╝
File upload done.
ERROR: (gcloud.app.deploy) INVALID_ARGUMENT: Error(s) encountered validating runtime. Your runtime version for ruby is past End of Support. Please upgrade to the latest runtime version available..
- '@type': [type.googleapis.com/google.rpc.DebugInfo](http://type.googleapis.com/google.rpc.DebugInfo)
  detail: '[ORIGINAL ERROR] generic::invalid_argument: com.google.net.rpc3.RpcException:
    generic::INVALID_ARGUMENT: Error(s) encountered validating runtime. Your runtime
    version for ruby is past End of Support. Please upgrade to the latest runtime
    version available.. [google.rpc.error_details_ext] { code: 3 message: "Error(s)
    encountered validating runtime. Your runtime version for ruby is past End of Support.
    Please upgrade to the latest runtime version available.." }'

By looking at GAE Flex Rubies, looks like 3.2 and 3.3 need Ubuntu22.
So this patch should solve (and its solving in my test).
Description
Fixes #
Note: It's a good idea to open an issue first for discussion.
Checklist

[ ] Tests pass
[ ] Lint pass: bundle exec rubocop
[ ] Please merge this PR for me once it is approved.

note this addresses https://github.com/GoogleCloudPlatform/ruby-docs-samples/issues/1476


Unify the style of Chinese translations

Most changes are about spaces and punctuation marks.

coverage: 60.014%. remained the same
when pulling 988f56d856fb27326c1060df4dcc0380441bf620 on CookiePieWw:zh-trans
into 8748882adb7250e6b091633bebef3299070a943d on newsboat:master.


Slow detection

Great work! Thanks a lot!
The detection takes around 2 second per image on a mac using only CPU.
It's quite different from the performance of test provided in the paper.
Apart from hardware, is it possible that it's caused by the overhead of Keras?
Also, may I ask is it possible to shrink the network somehow?
Thank you.

The performance of inference phase in this paper is conducted using NVIDIA K40 GPUs, and the input is  a batch of images. You can replace the vgg module with AlexNet, AlexNet is smaller than vgg.

@xindongzhang thanks for your comment, but I believe, that the authors state the following:
We measure the speed with batch size 8 using Titan X and cuDNN v4 with Intel Xeon<EMAIL_ADDRESS>However, it doesn't matter, they report performance on GPU.
@MrXu, I measured forward pass of my PC with Titan and for 5 pictures (like in SSD.ipynb) I got the results that are in the screenshot.

This means that it takes around 50 ms per image to get the prediction. I haven't measured the original caffe code, but I'm sure that my NMS implementation is slower, than the original one. Moreover, some custom layers can also be not very efficient, this is the thing to improve in the future, because I also need real-time performance on GPU for my problem. Any ideas how to speed up the code are welcome! I've also heard that sometimes Keras is slower, than other frameworks, but I can't bear Caffe, so, for me Keras is the best choice.
As for network shrinkage, apart from replacing vgg with AlexNet (after this step you will have to retrain the net), you can think about scales of your detection. For example, if you know, that you won't have big objects on the pictures, you, probably, don't need final layers and can delete them.

@xindongzhang thanks for the suggestion. I may prefer to avoid retrain the model.
@rykov8 , thanks for the clarification. I do read that Keras is slower than other framework like TensorLayer or TFlearn. I am trying to run the prediction on Rpi, seems achieving real-time detection with only CPU is really hard...

@MrXu as for training, I'm working on this part, hope to release the code this week. I also had to change some things in the architecture in order to be able to train the net. However, I will test it only for my problem, but I try to implement training as universal, as possible. Hope, it will be useful.
As for real-time detection, I'm quite sure, that unfortunately, it is nearly impossible nowadays to run deep nets on CPU with real-time performance. If you need real-time on CPU you might consider simpler methods with loss of quality.


parsing error

It looks like the arguments sent to cmake_parse_args are incorrect.
I believe the following code:
  set(oneValueArgs
      NAME
      FORCE
      VERSION
      GIT_TAG
      DOWNLOAD_ONLY
      GITHUB_REPOSITORY
      GITLAB_REPOSITORY
      BITBUCKET_REPOSITORY
      GIT_REPOSITORY
      SOURCE_DIR
      FIND_PACKAGE_ARGUMENTS
      NO_CACHE
      SYSTEM
      GIT_SHALLOW
      EXCLUDE_FROM_ALL
      SOURCE_SUBDIR
  )

  set(multiValueArgs URL OPTIONS DOWNLOAD_COMMAND)

  cmake_parse_arguments(CPM_ARGS "" "${oneValueArgs}" "${multiValueArgs}" "${ARGN}")

could look something more like this:
  set(oneValueArgs
      NAME
      VERSION
      GIT_TAG
      GITHUB_REPOSITORY
      GITLAB_REPOSITORY
      BITBUCKET_REPOSITORY
      GIT_REPOSITORY
      SOURCE_DIR
      FIND_PACKAGE_ARGUMENTS
      SOURCE_SUBDIR
  )

  set(optionArgs SYSTEM NO_CACHE GIT_SHALLOW DOWNLOAD_ONLY FORCE)
  set(multiValueArgs URL OPTIONS DOWNLOAD_COMMAND)

  cmake_parse_arguments(CPM_ARGS "${optionArgs}" "${oneValueArgs}" "${multiValueArgs}" "${ARGN}")

I'm finding this defect with this:
PMAddPackage(
  NAME     glew
  URL      https://github.com/Perlmint/glew-cmake/archive/refs/tags/glew-cmake-2.2.0.tar.gz
  URL_HASH SHA256=cdd82afba80f7cf34548cf5c902240d6721ec5a27ec9e075851b4a3a79ec6907
  SYSTEM
  PATCH_COMMAND
    "${PATCH_EXE}" -p1 < "${CMAKE_CURRENT_LIST_DIR}/glew_install_fix.patch"

  OPTIONS
    "glew-cmake_BUILD_SHARED Off"
    "ONLY_LIBS On"
)

My current workaround is to set "SYSTEM SYS"; however, I'm pretty sure this is broken, too.
EDIT: corrected an assumption with further testing.

That does sound and look reasonable, thanks for the report! I don't have time to look into it atm but am happy to review any PR addressing this.

That does sound and look reasonable, thanks for the report! I don't have time to look into it atm but am happy to review any PR addressing this.

I think it's a super easy fix. If you have a "good first issue" label, this could go there, otherwise I will get to it as soon as I can.

Good point! One potential issue I see however is that this might break backwards compatibility as the previous parameters will now be treated as new arguments, so it could make sense to restrict this to the actually broken arguments like SYSTEM. Also having an integration test would be great to avoid future regressions.

Good point! One potential issue I see however is that this might break backwards compatibility as the previous parameters will now be treated as new arguments, so it could make sense to restrict this to the actually broken arguments like SYSTEM. Also having an integration test would be great to avoid future regressions.

I think it's a real risk that there are projects out there with workarounds that will misbehave once this is fixed. I am one, for example. None the less, I believe fixing this is "The Right thing to do." Furthermore, I hope that anyone building a release has CPM pinned to specific version - which I've done in my own project. This also is the right thing to do.
I listed other optionArgs that looked, at first glance, like they might suffer the same defect as SYSTEM. Whoever updates this should evaluate that.
And OF COURSE we should have regression tests!!! When I was writing this I was thinking about how that might be done. :-)

I might be able to get to this on Friday.

Great, looking forward!

After further investigation and testing, I have concluded that this is working as designed. IF I were to suggest a change here it could be additional documentation and/or, possibly, a sanity check of CPM_ARG_* values.  Neither are strictly necessary, though, and I will close this as works as designed.

Thanks for the update! Just to be sure I understand correctly, the SYSTEM flags etc are actually working correctly, however feel unintuitive as they are one-value arguments here as opposed to the option arguments used by related CMake functions?

@TheLartians Correct. This was a user RTFM error on my part. Sorry.


Use readable-stream to address #593

Per issue #593 this swaps in readable-stream for core stream

Can you delete your second commit with the built file? I'll do that part when I do a release?
Otherwise, looks good to me! Thanks @Zanadar.

@feross Done.

Nice work! Thanks!

@Zanadar Do you have interest in sending PRs to the other repos that webtorrent uses?
You can see which ones need PRs by searching for require('stream') in the webtorrent node_modules folder. :

@feross That's a great idea. I'll get cracking on that.

@Zanadar awesome, thanks! Looking forward to merging those PRs from you! Let me know if you need help, or have questions!


Only include necessary Bevy features

Currently this crate is pulling in all of Bevy, preventing downstream consumers from excluding any of Bevy's default features.
This change trims the feature list to only those that are actually used in this crate.

Great idea, thanks!


Update Influxql Readme

Gets the InfluxQL Readme in sync with the 1.0 docs version of the same doc.

[x] InfluxQL Spec updated

Also see https://github.com/influxdata/docs.influxdata.com/pull/605

LGTM


Fix: category casing in metadata and project file

This PR fixes the issue where category casing is not consistent on developer site. This is due to the case in their respective metadata files are not title case.
The PR changes several places:

In project file: change Utility Network to Utility network
In ContentPlist: change Utility Network to Utility network
In 3 categories, fix all samples' metadata category:

Cloud and portal
Route and directions
Utility network

This seems to be outside of the scope of the README update issue and the readme-updates branch is already very long-lived. If we're happy with the way that branch is, I say we go ahead and merge it and then tackle the category name changes as part of a separate issue. What do you think?

This seems to be outside of the scope of the README update issue and the readme-updates branch is already very long-lived. If we're happy with the way that branch is, I say we go ahead and merge it and then tackle the category name changes as part of a separate issue. What do you think?

Sounds good to me.
One reason I targeted this PR to philium/readme-updates is that these category renaming in metadata would have effect on dev site, and Mary and John indicated these categories should be fixed sooner than later.
I'll temporarily put this PR on hold and wait for Mary's feedback next week. Meanwhile, since the philium/readme-updates branch should already be free of issues, I'll render another preview with it and do a final check, before we merge #869 .
If it is good, can we merge #869 next week? 😳

@maryharvey do you think it is OK to push back this fix a little bit? I assume it would be merged by U9 release, but in case it doesn't, is it acceptable to leave those category names as-is a little longer?

As #869 is successfully merged 🎉 , we can start to review these changes and decide if they are needed.

I think it'd be good to go ahead with these changes since it's a relatively quick and simple fix that would keep our sample names consistent. But I do agree that if we're going to update Utility networks in the project file, we should do the same for Route & directions and Cloud & portal.

Nudge to the thread - how do you think of the change to Route & Directions and Cloud & Portal

Nudge to the thread - how do you think of the change to Route & Directions and Cloud & Portal

Not sure if you saw my comment, but I think it'd be better as "Route & directions" and "Cloud & portal".

Not sure if you saw my comment but I think it'd be better as "Route & directions" and "Cloud & portal".

Yep I saw it. I'm still waiting for inputs from @maryharvey and @philium . Pros and cons for making this change

Pros: now category names are consistent everywhere: contentplist, folder name, metadata
Cons: it might not be good looking

Personally I'm in favor of making this change, so that we won't need to be careful of mapping category names anymore, as now they are all the same everywhere. Besides, it makes sense to keep everything in sentence case, which is our new standard.

I personally would love to see us follow platform conventions inside the app, such as using title case for category and sample names. The names could be sentence case in the metadata files so as to follow the website convention. Same with the ampersand. The platform convention is to use it in titles. For examples, just open the Settings app: Display & Brightness, Home Screen & Clock, etc.

I personally would love to see us follow platform conventions inside the app, such as using title case for category and sample names. The names could be sentence case in the metadata files so as to follow the website convention. Same with the ampersand. The platform convention is to use it in titles. For examples, just open the Settings app: Display & Brightness, Home Screen & Clock, etc.

So do you think instead of making changes this PR, we should make all the category names in content plist to title case? e.g. Edit Data, Display Information, etc.?
Either way, we should settle on a consistent casing. 😁

It is probably something to talk over with the team, but if we could follow iOS conventions inside the app while following Esri conventions on the developer site, that would be great.

@saratchandrakarumuri A bit of context: we want to make the category names casing consistent both for the app and for the developer site.
Not sure if it breaks your tests... please give a try.


docs: Add syntax highlighting for generated documentation.

Hi.
Jose notified me I forgot to modify #447 to add syntax highlighting to generated documentation.
Thus, this commit fixes the previous one.
Best regards.

Thank you for the approval!


[PT Run] Shorten title of empty web search

Description of the new feature / enhancement
The title of the empty web search result is to long and in my opinion a bit to much information.
I think we can shorten it to only "Search the web" or "Open the web search" with the subtitle "In {...}".

This is fixed with 0.561. Please head over to https://aka.ms/installpowertoys


entities API and module Instance API sometimes are not getting called on slower networks. Try with slow 3G

https://www.notion.so/entities-API-and-module-Instance-API-sometimes-are-not-getting-called-on-slower-networks-Try-with-s-0b150436afb244fdb252a0ac8c3e53aa

Not reproducible . Closing for now


[Workaround] Use meta-oe-fixups to solve srecord issue

Note: this commit is cherry-picked from
meta-xt-prod-devel-rcar with all signatures.
Add layer with workaround for incorrect libc
used by srec_cat.
See comments inside meta-oe-fixups for details.
Signed-off-by: Ruslan Shymkevych<EMAIL_ADDRESS>Reviewed-by: Volodymyr Babchuk<EMAIL_ADDRESS>

PR was tested by build of meta-xt-prod-aos-rcar on Ubuntu 20.04.5.
Without PR build fails on u-boot.
With PR product was built successfully.

See https://github.com/xen-troops/meta-xt-rcar/pull/33 for detailed explanation.

PR is not relevant to this project.


Forward the entire service ref type on the RootServiceFactoryOptions instead of forwarding each type argument

For more detail see this to do comment:
https://github.com/backstage/backstage/blob/1780a67bc5fbc6ddad25a612f16d671d145a1b6e/packages/backend-plugin-api/api-report.md?plain=1#L517

https://github.com/backstage/backstage/pull/26220


brief update to readme

since this repo was a fork of model_seg_sci, the README described the SCIseg model. This PR briefly updates the readme to describe the bavaria-quebec project.

Merging it right away so that the correct info is described when someone opens the repository. Future PR will properly update the readme by filling in the TODOs


Can we use Flutter for PWA (Progressive Web App) ?

My Question is can we use Flutter for Mobile Web development ?

https://flutter.io/faq/#does-flutter-run-on-the-web

You can split out any business logic type operations into pure-dart libraries and then use AngularDart for the web side of things, importing the relevant libraries to both flutter and AngularDart.

There was a great talk about this at DartConf: https://youtu.be/PLHln7wHgPE

A native "deploy to web" function would be much appreciated, and would open flutter to the huge community of web developers & users. A must have !

Absolutely. +1

This is not something we are intending to implement any time soon.

We very need a web version of Flutter.

Even some framework or something as simple as a ui library to help with angulardart(for web) + flutter(for mobile) would be a huge step

Pardon my mistake if any, I'm not a dev. But as far as I understand the web and OS's UI architectures, Web (HTML, DOM) and OS's UI (say, QT, GTK, ...) "rendering" systems are totally different paradigms, making it hard, if not impossible, to make a Web AND real OS (Windows, Android, iOS, whatever...) universal framework.
That's why Flutter can't be used to Web. Logic and graphic elements, "widgets", are all-in-one objects while the Web layers view (HTML, CSS) and logic (JS).
Still, Facebook did a great job with React and its virtual DOM, and we can share up to 93% of the code between a ReactJS (Web) and ReactNative (Android, iOS) code... Ok, one of the main discussed difference between React and Flutter is this exact point: where React separate view and logic, Flutter mix them. React is a hybrid framework coming from the Web paradigm, and succeeded to manage native UI elements with ReactNative library... Flutter adopted a totally different way of doing the thing, coming from the OS paradigm, and like Qt or GTK, comes with its full set of UI elements. Right?
Now what? If React succeeded to make Web UI architecture work with native OS components, would it be really impossible to make the other way around, Flutter control a kind of virtual DOM and Web'HTML/CSS??? After React "Native", a Flutter "Web" or "DOM"?
Actually, there's an experimental project trying to do it: https://github.com/yjbanov/butterfly

A Flutter Web UI would no more use HTML/DOM than the iOS version uses UIKit or the Android version the SDK view - they don't. Flutter on WASM would likely bypass HTML and render straight to a Canvas.

Dart to webasm is not a thing. https://groups.google.com/a/dartlang.org/forum/#!topic/misc/szGdXdLrZM8[126-150]
And dart2js would cause performances problem.
This could be fine is somehow browsers integrated a dartVM natively. But chrome team refused, so I doubt others will.

I think overall the best solution is splitting your app into packages that don't depend on the OS. And use AngularDart+Flutter altogether.
You may also want to use dart2js interop for things like VUE or React.

The Skia team have Pathkit ( which is the Flutter Compositor) working on the web now.
The skia WASM code:
https://github.com/google/skia/tree/master/experimental/pathkit
The flutter engine referencing it :)
https://github.com/flutter/engine/blob/master/ci/licenses_golden/licenses_skia#L1602
https://github.com/flutter/engine/tree/master/flow
SO there is a good chance that Flutter for Web rendering to canvas ( not html DOM) will happen ?

React Native Web is doing well in this area (universal code base for web, native apps, VR apps, desktop apps). Would be fantastic for Flutter to be able to 'target' different platforms also. Next step up in developer super powers.

I doubt the flutter team would blow up a project by others to get this working, but Flutter for mobile already has tons of improvements yet to be made, I'm not sure if expanding to the web (which already has a huge amount of options), while certainly possible (albeit obviously a lot of work) is something we should be wishing them to take on right now..

Since Flutter is built based on the Materials Design concepts (MDC), I would think there should be a separate framework decided to building Web app using MDC. I recently looked and it looks like there's already support in Materials Design for web development.

I don't think it will really be "so easy" to port Flutter to the Web. I think it will be better for all users if the team continues to focus primarily on mobile. Porting Flutter to the Web not only requires porting a Dart VM to WebAssembly (or AOT, both of which are gonna be complex). And then add to that the expectation of hot reloading, etc. that people will for sure have.
If the community really wants it, though, then I don't see why not to just try and do it ourselves.
Let me just put this out there - I tried to port to the standalone Dart VM to WebAssembly, using Emscripten, and all I can say is that there are many more moving parts than I had imagined. It won't be easy.

We really don’t need an exact “flutter on the web” what would be really cool though is simple api compatibility between a dart web framework and flutter.

@Gee5ive That's BLoC architecture.

@rrousselGit I mean the actual widget api.

I understand you.
My projects, VM and web, are sharing lots of libs.
Would be insanely nice to share designing libs between flutter and web.
Jonathan Rezende

Em 12 de nov de 2018, à(s) 14:01, G.Becks<EMAIL_ADDRESS>escreveu:
@rrousselGit https://github.com/rrousselGit I mean the actual widget api.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/flutter/flutter/issues/14868#issuecomment-437933876, or mute the thread https://github.com/notifications/unsubscribe-auth/AF6Y3t7JYwfBeRcHU7eGDpPEsWDrqWAEks5uuZtCgaJpZM4SSM6E.

@jodinathan
Yup, I think https://workiva.github.io/over_react/ would be the best starting point for something like this. Would be a huge undertaking and require lots of community effort though. Would be really worth it for the dart ecosystem in the long run though.

It seems that they recently announced Hummingbird, which should enable running Flutter on the web.

This makes me wonder about the architecture of the web itself. Today we create SPAs and trick the system with hashes # in the URL or other tricks like that.  Why can't a server send an executable file which runs in the browser*? Just like with Java Applets. Except now with Web Assembly you don't need to embed a JVM in the browser or other runtime in the browser? Alternatively, the executable that the server sends could be precompiled based on what browser you are using?
*The browser is a nice sandbox for such an executable file to run in, so security is taken care of.

@Hixie Are there any progress or ETA for Hummingbird. The project seems so good but it seems that it never went public.

It's announced at Google I/O 2019 https://flutter.dev/web


OpenJ9 AArch64: Enable a BigInteger test back again

This commit enables the following test, which used to fail with timeouts
on AArch64:

java/math/BigInteger/LargeValueExceptions.java (eclipse/openj9#9082)

Signed-off-by: KONNO Kazuhiro<EMAIL_ADDRESS>

The test was excluded by #1710.  OpenJ9 AArch64 is fast enough for running the test now.

sanity.openjdk on AArch64 went successful after the test was enabled.
https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_sanity.openjdk_aarch64_linux/381/


Add TLS support for MQTT

Feature request to add TLS support for MQTT. I'm using Mosquitto as a server with TLS and the current implementation won't support a data pull without code changes.

I agree that it seems sensible to focus on TLS transport initially with client cert authentication being a nice to have extension later.

Noting that this will be a necessary requirement for interfacing with AWS IOT.

This is a long running issue. My two cents: as a workaround I'm using in order to connect to brokers that expose TLS mode only is running a local broker where nodered is hosted and configuring this for TLS based bridging to the external service.

TLS support for MQTT nodes is coming in 0.14.0. Thank you for waiting. ⌛


FAIL: //tensorflow/core/grappler/clusters:single_machine_test

System Info
  Name:						 Hawaii
  Vendor:					 Advanced Micro Devices, Inc.
  Device OpenCL C version:			 OpenCL C 2.0
  Driver version:				 1912.5 (VM)
  Profile:					 FULL_PROFILE
  Version:					 OpenCL 2.0 AMD-APP (1912.5)
  Extensions:					 cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_khr_gl_depth_images cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_image2d_from_buffer cl_khr_spir cl_khr_subgroups cl_khr_gl_event cl_khr_depth_images cl_khr_mipmap_image cl_khr_mipmap_image_writes

ComputeCpp 0.2.0
To reproduce
bazel test --config=sycl --local_test_jobs=4 -k --test_lang_filters=cc,py --action_env=LD_PRELOAD=/usr/lib/libOpenCL.so.1 --test_timeout 300,750,1200,3600 //tensorflow/core/grappler/clusters:single_machine_test

Error
[ RUN      ] SingleMachineTest.Queue
2017-06-12 15:55:49.124896: I ./tensorflow/core/grappler/clusters/single_machine.cc:269] Starting new session
2017-06-12 15:55:49.138891: I ./tensorflow/core/grappler/clusters/single_machine.cc:257] Cleaning up previous session
2017-06-12 15:55:49.142450: I ./tensorflow/core/grappler/clusters/single_machine.cc:269] Starting new session
2017-06-12 15:55:54.143757: F ./tensorflow/core/grappler/clusters/single_machine_test.cc:90] Non-OK-status: cluster_->Run(item.graph, item.feed, item.fetch, &metadata) status: Deadline exceeded: Failed to run the graph after 5 seconds, aborting
external/bazel_tools/tools/test/test-setup.sh: line 159: 19098 Aborted                 (core dumped) "${TEST_PATH}" "$@"
(END)

For me the failure is in SingleMachineTest.CostModel:
[ RUN      ] SingleMachineTest.CostModel
2017-06-14 10:43:59.108073: I ./tensorflow/core/grappler/clusters/single_machine.cc:257] Cleaning up previous session
2017-06-14 10:43:59.108701: I ./tensorflow/core/grappler/clusters/single_machine.cc:269] Starting new session
./tensorflow/core/grappler/clusters/single_machine_test.cc:72: Failure
Expected: (8) <= (node.output_info(0).size()), actual: 8 vs 0
[  FAILED  ] SingleMachineTest.CostModel (300 ms)

And the SingleMachineTest.Queue test passes. Tried both eigen_mehdi and dev/eigen_mehdi branches.

Yes that's the current issue.

Fixed by #114


[PrivateSend] Start MaxParticipants at 10 and decay with time

This will start the MaxParticipants at 10 (theoretical max of 90 inputs and outputs which should be an okay size), at 20 seconds MaxParticipants will be at 5, and continue to decrease with time until it reaches the minimum, 3. This will allow for stronger mixing rounds (more participants) when there is liquidity in the network while also minimally affecting the speed when there is low liquidity.

Based on the pre https://github.com/dashpay/dash/pull/2937/commits/736eb47caae9dbe15507c5fe8d34f99974bcfba1 setup, the first client to start a PS queue would be able to very certainly guess the number of participants in a mix, this change removes that metadata leak

Not sure I like this idea anymore, I'd probably prefer the current state of things where we have random max participants at the start and then fall back to whatever number of clients were actually active (but still above min threshold). It achieves the same goal but with a simpler algo imo.

I'm still conflicted, but I kindof agree. There's probably a better solution anyhow


Added more specific instructions for nightly

@phil-opp might want to consider putting the -Z pre-linker flags in cargo.toml instead of passing it in manually

Thanks for the PR, @Immortalin! Not everyone wants to use nightly by default :).
bors r+

might want to consider putting the -Z pre-linker flags in cargo.toml instead of passing it in manually

I didn't know this was possible. However, we no longer need it in the following posts, so using the command line flag makes more sense to me in this case.

@phil-opp merge and close?

Seems like Travis timed out. Let's try again:
bors r+

Hmm, looks like bors still fails. Merging manually.
Sorry for the delay @Immortalin!


Processing times for crop?

Hi - we're trying to build a fast way to crop an HD video on Android devices. We've built a solution using JavaCV for Android (based on FFMPEG). The resulting processing times are way too slow, 90+ seconds for a cropping a 15-second 1920x1080 video to 1080x1080 square video.
We came across this repo and were wondering what type of crop times you are able to achieve. Our applications are written in Java (Android) and Swift (iOS), so before we go down any React Native path, we just wanted to know what type of processing times this solution offers. If this is similar to what we are getting, then it is probably an FFMPEG related issue (encode/decode times).
Thanks for your help!

Hi @tchandok  and sorry for slow reply.
I never checked it and never heard from someone that cropping is slow when using this project.

Thanks @tchandok !

Im getting the same numbers. 2 mins

Seems to be the same as: https://github.com/WritingMinds/ffmpeg-android-java/issues/54
The recommended solutions seems to be to add -preset ultrafast, which we are already doing.

Have the same issue. For input video with duration 20 sec, processing time is 18-20 sec. -preset ultrafast did not help. My command is:
-y -i input -c:v libx264 -preset ultrafast -vf crop=size:size:0:offset -tune fastdecode -c:a copy -f mp4 saveFile
Maybe here are any updates?


Tests run out of memory

Watch task is basically dead at the moment. Noticed that this issue is happening way more often then it used to. @TheSharpieOne mentioned moving off of karma all together and I am +1000 to that. Keeping this issue open to track the status of it.
also, I had some experiment with enzyme and jest in https://github.com/reactstrap/component-template and was pleasantly surprised by the watch, coverage and just general experience of using it.

I went with Jest and react-scripts test since it is more inline with what the component-template project is doing... and also because it was less work since Jest officially supports jasmine's API (meaning the tests didn't have to change)... but travis is taking it's sweet time running the tests. Each suite seems to be taking forever:

422 tests passed (422 total in 63 test suites, run time 147.024s)
Compare that to mocha in a similar project with coverage 493 passing (1s) Converting to mocha is more effort, but may be desired in the long run.


[Bug]: Untested files are missing when collecting coverage in multi-project configuration

Version
29.7.0
Steps to reproduce

Clone my repo https://github.com/tbossi/jest-bug-coverage-per-project
The repo contains two folders coverage-global and coverage-per-project. They are the same codebase with the exact same code but different Jest configuration.
In each of those folders run npm install then npm run test:coverage.
You can see the files included in coverage report are different depending on which of the two main folder you look at.
Additionally, enter in any of the packages (for example pack1) again in both folders coverage-global and coverage-per-project. Then run npm run test:coverage for that single package.
You can see the files included in these coverage report are different.

Expected behavior
The files without tests (pack1/file-without-test-1.js and pack2/file-without-test-2.js) should always be present in the coverage report if collectCoverageFrom is set on each package (both when running jest from root and from each individual package).
Actual behavior
The files without tests (pack1/file-without-test-1.js and pack2/file-without-test-2.js) are present in the coverage report only if:

coverage is configured globally (folder coverage-global) and jest --coverage is run from the root package.json
coverage is configured per project (folder coverage-per-project) and jest --coverage is run from each individual package of the workspace

Additional context
The project shown in the repo is organized using npm workspaces. There is a global jest configuration file (jest.config.js) that maps workspaces to jest's projects setting.
Individual packages each have their own configuration file, and share a common preset (jest.preset.js).
In this context, I want jest --coverage to also show me files without tests in each package. For this reason I used the collectCoverageFrom setting. However, this setting combined with the projects one seems to have unexpected results.
When setting collectCoverageFrom in the root jest.config.js (as it is in folder coverage-global) the files without tests are visible only when jest is run from the root, and not for a single package. That is kind of expected, since the jest.config.js of a single package has no setting collectCoverageFrom even in the preset.
What is not expected, is the other case (in folder coverage-per-project), where collectCoverageFrom is set in the preset and therefore shared by the jest.config.js of each single package. In this situation, which by the way is my go to configuration when dealing with jest combined with workspaces, if you run jest for a single package then the coverage of that package is correct. But if you run jest from the root then the files without coverage are missing.
Also note that having collectCoverageFrom in a preset is just to simplify the problem, but each individual package could also have its own collectCoverageFrom with different values.
I also did a bit of research on my own to find the root cause, and it seems to boil down to the method _addUntestedFiles of CoverageReporter. In the for loop there is a call to context.hasteFS.matchFilesWithGlob passing the global config, but there is no call to the same function passing the config of the current context under iteration.
Adding that missing piece seems to solve the issue, but I'm not sure if it's the right way to fix it.
Environment
System:
  OS: Windows 11 10.0.22631
  CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
Binaries:
  Node: 20.13.0 - ~\AppData\Local\nvs\default\node.EXE
  npm: 10.5.2 - ~\AppData\Local\nvs\default\npm.CMD
npmPackages:
  jest: ^29.7.0 => 29.7.0

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

Nope, it's not stale, it needs someone to answer


Unable to create an array containing a single empty array

When trying to create an array containing a single empty array I am left with only a single empty array:
Steps to reproduce
$arr = @(@())
$arr.Count
$arr[0] += "something"
$arr

Expected behavior
1
something

Actual behavior
0
Index was outside the bounds of the array.
At line:1 char:1
+ $arr[0] +=  "something"
+ ~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : OperationStopped: (:) [], IndexOutOfRangeException
+ FullyQualifiedErrorId : System.IndexOutOfRangeException

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.0.1
PSEdition                      Core
GitCommitId                    v6.0.1
OS                             Linux 4.15.6-1-ARCH #1 SMP PREEMPT Sun Feb 25 12:53:23 UTC 2018
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

I've found a work around for this:
$arr = @(,@())

will create an array containing a single empty array.

Just a quick question how can I get an installer of the nightly version of powershell 6.1 I have been looking everywhere on the site cannot seem to locate. I am a 16 year old high school student whom is looking at and wanting to code programs and apps. Please help

@frogamic:
The behavior is as designed: loosely speaking, @(...) means: treat output from the statement(s) within as an array, unless it already is.
Thus, @() outputs an empty array, and applying another @() just passes that empty array through.
An alternative way to achieve what you want would be:
$arr = , @()  # construct a 1-element array whose only element is the empty array.

Similarly, to create an array with 2 empty sub-arrays can be simplified to:
$arr = @(), @()

Hi @frogamic, the @( ... ) operator guarantees that the result produced by the code inside is always an array. This operator semantic was introduced because of the way streaming works. If the pipeline returns a single element, you don't know if it's supposed to be a scalar value or an array of one element. @( ... ) guarantees that you will always get an array even if the pipeline returns 0 or 1 elements. This way you don't have to special-case your code to handle scalar and non-scalar values.

To complement what @BrucePay is saying:
@(...) is not an array constructor (it's an array guarantor, if you will, as Bruce explains).
All you need to construct arrays from explicitly enumerated elements is  the array-construction operator, , -  e.g.:
'one', 'two'  # array "literal" with 2 elements; you do NOT need @('one', 'two')

However, the belief that @(...) is necessary in this scenario is very widespread and probably impossible to dispel at this point (prior to v5.1, use of @(...) even incurred a performance penalty in this scenario).
This is not helped by the fact that @() is indeed the easiest way to create an empty array.


apps/btshell: fix build on 'native' bsp

strl* methods are not always available, let's use snprintf()
for string copy/concat actions in parse_dev_addr, as it allows
us to keep buffer overflow control and NULL termination of string.

Fixed whitespaces


Indicate that RSSVE provides Scatterer sunflare/config

Just like #5733, I'd expect that this one is broken in some way, but unfortunately I'm not familiar enough with CKAN to determine what exactly is wrong...

Merging with thanks!


Use the token type Comment, not Comment.Preproc, for RST comments

While documenting a project that interacts with headers across different file formats, I noticed that RestructuredText comments rendered differently from the others:

For clarity: the difference between RestructuredText comments and other lexers' comments is that all other comments are styled as blue text and italicized, but RestructuredText uses green text and is un-italicized.
The root cause is that RestructuredText comments are given the token type Comment.Preproc, which is styled uniquely by most styles that I reviewed in Pygments.
This PR modifies the token type for RST comments to Comment. This results in rendering that matches my expectations:

Please let me know if anything is amiss here! As always, thanks for your work on Pygments!

Yeah, there's no good reason for this. Thanks!

It's not a preprocessor anyways, so yes, this is the right change.

Too slow this morning. More coffee needed apparently to beat @birkenfeld on the job :(


Separate clause of query from clause of trigger

Move original clause to internal package
Extends internal clause classes for history state querying
Extends internal clause classes for condition of trigger

@shinsuke-nara  can you review this PR

@yongpingchen
I think we should implement trigger clauses and query clauses without extending internal clause classes.
Trigger clauses and query clauses are different data structure. There is no relationship between trigger clauses and query clauses.
What do you think?

@shinsuke-nara query clause and trigger clause are almost the same structure. Only different is the alias.  What I pretend to do is to share the same logic, so I bring the same structure to internal package.

@yongpingchen I will tell you beforehand that this is my preference :)

What I pretend to do is to share the same logic, so I bring the same structure to internal package.

Sharing same logic is important but we should share logic only if codes require same logic.
In this case, trigger clauses and query clauses are similar but not same in my opinion. Although it is hard to distinguish similar and same. One of my criteria is If a specification says they are same, we should share same logic.
Trait rest API specification does not say that trait clauses and query clauses are same. So I prefer to implement trigger clause and query clause independently. I have some concern about using extending as following:

If we change trigger clause specification or query clause specification, using extending may inhibit to change these classes.
Using extending makes understanding the classes more difficult. In other words, Using extending is not simple.

If you prefer to use extending, It is OK for me. Because this is difference of our preference :)
But if we use extending, we should make internal classes abstract. Developers does not need to construct their classes so we prohibit it.

@shinsuke-nara

Trait rest API specification does not say that trait clauses and query clauses are same. So I prefer to implement trigger clause and query clause independently.

Yes, there is not specification mentioned about that.  However, we do exactly use the same structure, except alias. In this point of view, query clause and trigger clause can be considered as inherit from same supper class. Trigger clause compared with query clause, has a additional filed alias.  That is why I think it is better to make internal clause for both of them.

But if we use extending, we should make internal classes abstract. Developers does not need to construct their classes so we prohibit it.

Thanks. I agree with this.

OK


RHOAIENG-1451: Detect deleted pipeline versions on pipeline runs table, disable, show tooltip

Closes: RHOAIENG-1451
Description
For the pipeline runs table, fetch the pipeline version associated with the runs, and if no pipeline version is returned, that version no longer exists, and we show the name as disabled with a tooltip indicating that the version "no longer exists."
How Has This Been Tested?
Only regression tested by simply navigating to the pipeline runs table with runs that have pipeline versions that have been deleted, and seeing that on-hover of any disabled text for pipeline versions that a tooltip is shown stating the version no longer exists.

Test Impact
Tests will be written as a follow-up.
Request review criteria:
Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[x] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

Also, I am wondering if we should disable the duplicate button in the table row dropdown menu and the pipeline run details page header actions for those runs with unavailable versions. Any ideas? @jpuzz0 @yannnz I think it makes no sense for them to duplicate a run using an outdated version because we could not find it at all. (If we don't disable the duplicate button, the result would be only pre-filling the name to Duplicate of run xxx) with not pipeline and version selection, makes it very slightly different from creating a new run.


Where is the bloom filter in bloomrun?

Hi, this is a question about the internal implementation of bloomrun. In the descriptions I read
A js pattern matcher based on bloom filters

Where can I find the implementation of a bloom filter ? What do you mean with based on? Would be nice to clarify that and besides thanks for this great library!

Since version 3 this is not using bloom filters anymore. A reference remained in the package.json. I have just removed it.

And just as hint the repo descriptions contains it too.


The 'reverse' property should be on the 'Scale' object, not on the 'Tick' object

Setting the property "new LinearTicks().setReverse(Boolean.TRUE)" has no effect.
According to the documentation https://www.chartjs.org/docs/latest/axes/cartesian/#common-options-to-all-axes  the 'reverse' property should be on the 'Scale' object and not on the 'Tick' object

Thank you for the issue. Will be fixed in the next release :)


security issue in authentication

Hello,
i find app vulnerability in authentications process. After you type to login window of this app everything, app store this value to shops.shopify_domain column to database (in older versions of package). Also you can simulate it if you type after your app url "/authenticate?shop=attacker.com". Sorry if this security problem is fixed in some past issue. Do you have some idea how to validate shop parameter before its stored to database? You can check what i mean here:
https://ibb.co/nC8M752
Thanks for info.

If the shop doesnt exist in the database when trying to authenticate, it creates the shop. Not sure what I can do for this right now without changing the flow. Open to suggestions.

Hello,
first of all, thank you for your answer and for your great package.
I fix it by adding to AuthControllerTrait class to authenticate method code like:
if (!$request->filled('code') && strpos($shopDomain, Config::get('shopify-app.myshopify_domain')) === false) {
return redirect()->route('login');
}
This will redirect all not myshopify.com urls to login page. Hope i make it correct. I saw, something similar is in sanitize url method. What do you mean about this change?
I am sending you also print screen of authenticate method here: https://ibb.co/ZhDD17V

Hello, this doesn't make it secure. example of bypass /authenticate?shop=myshopify.com.hacker.net

Hello,
you are right, i think this will be better:
if (!$request->filled('code') && strpos($shopDomain, Config::get('shopify-app.myshopify_domain'), (-1 * strlen(Config::get('shopify-app.myshopify_domain')))) === false) {
return redirect()->route('login');
}
What do you mean about this solution?

I'm not sure this still helps anything. Will think on it, but its not a priority internally right now.


The following script creates a Docker container with a cgo-disabled Go binary that resolves a host defined in the /etc/hosts file.
#!/bin/bash
set -e
set -x
cat > Dockerfile <<EOF
FROM alpine:3.6

COPY internal.sh /tmp/internal.sh
COPY go_dns /tmp/go_dns

CMD /tmp/internal.sh
EOF

cat > go_dns.go <<EOF
package main

import (
	"net"
	"fmt"
)

func main() {
	fmt.Println(net.LookupHost("example.com"))
}
EOF

cat > internal.sh <<EOF
set -e
set -x

export GODEBUG=netdns=10

cat /etc/resolv.conf

cat /etc/hosts

/tmp/go_dns

nslookup example.com
EOF

chmod +x internal.sh

go version
GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build -o go_dns go_dns.go
docker build --no-cache -t go_dns .
docker run --rm \
           --add-host example.com:<IP_ADDRESS> \
           -i \
           -t \
           go_dns

What did you expect to see?
Go's DNS resolver resolve the address that is contained in /etc/hosts.
Output:
+ cat
+ cat
+ cat
+ chmod +x internal.sh
+ go version
go version go1.9.2 linux/amd64
+ GOOS=linux
+ GOARCH=amd64
+ CGO_ENABLED=0
+ go build -o go_dns go_dns.go
+ docker build --no-cache -t go_dns .
Sending build context to Docker daemon 2.691 MB
Step 1 : FROM alpine:3.6
 ---> 053cde6e8953
Step 2 : COPY internal.sh /tmp/internal.sh
 ---> 58c4e4eabbd7
Removing intermediate container e915818d62ae
Step 3 : COPY go_dns /tmp/go_dns
 ---> bcf50d520610
Removing intermediate container 85918214a98c
Step 4 : CMD /tmp/internal.sh
 ---> Running in cf4216686f20
 ---> c75e5b4ccec8
Removing intermediate container cf4216686f20
Successfully built c75e5b4ccec8
+ docker run --rm --add-host example.com:<IP_ADDRESS> -i -t go_dns
+ export GODEBUG=netdns=10
+ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
#nameserver <IP_ADDRESS>
+ cat /etc/hosts
<IP_ADDRESS>	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
<IP_ADDRESS>	example.com
<IP_ADDRESS>	b44f6648150b
+ /tmp/go_dns
go package net: built with netgo build tag; using Go's DNS resolver
go package net: hostLookupOrder(example.com) = dns,files
[<IP_ADDRESS> 2606:2800:220:1:248:1893:25c8:1946] <nil>
+ nslookup example.com
nslookup: can't resolve '(null)': Name does not resolve

Name:      example.com
Address 1: <IP_ADDRESS> example.com

What did you see instead?
An external DNS lookup was performed.
(This may be the same issue that was happening here #14170)

Reading the source of net/conf.go, I see the following comment in regards to /etc/nsswitch.conf:
// glibc says the default is "dns [!UNAVAIL=return] files"
// http://www.gnu.org/software/libc/manual/html_node/Notes-on-NSS-Configuration-File.html.

It turns out that file does not exist in the container. If I create it with the following contents:
hosts: files dns

I get the expected result.

Thanks a ton!
https://gitlab.com/gitlab-org/gitlab-runner/issues/2959

Docker container with a cgo-disabled Go binary that needs to resolves a host defined in the /etc/hosts file but wasn't working
@bontibon 's solution to worked for me
inside container run
echo "hosts: files dns" > /etc/nsswitch.conf

As this is a common deployment method with golang and k8s with minimal images, this has very unexpected results. Can we fix this to function as expected in a minimal environment?
@thockin

Ping

@kfox1111 You should just change your base image, golang should always defer to /etc/nsswitch.conf
@Barbery Here is not the place for sysadmin questions (hint: use sudo)

another reason could be the permission ot '/etc/hosts', it should be 644 when user is not root

@panamafrancis it is common to use alpine as a base image as its size is small. it uses a non glibc implementation and does not contain nsswitch.conf. The distro assumes nonglibc behavior as its not glibc based, and behaves well in the absence of nsswitch.conf. golang chose to implement glibc's failback behaviour in the absence of nsswitch.conf, which IMO is a bad default. etc/hosts should be honored by default in the absence of nsswitch.conf. Alpine is not going away any time soon, and convincing folks not to use alpine is going to be a hard sell. I'd suggest golang change its default to a safer one, ie honor etc/hosts first, in light of this. This would be the least surprise option as well as one that hardens security.

Ok... just hit this again when switching to k8s 1.12.


Always show delete action in notifications

First of all, thanks a lot for K-9 mail! I just switched to it from BlueMail and really like it 🙂.
The only thing I am missing is the ability to – besides replying to a message and marking it as read – also delete it right from the notification.

The functionality is already available. You can enable it under Global settings > Notifications > Show 'Delete' button. If you're using the current beta version please note that "global settings" has been renamed to "general settings".
I believe this functionality isn't enabled by default due to historical reasons. At some point we deleted messages without asking for confirmation and didn't support an easy way to undo the deletion. Nowadays we still don't support undo (see #624), but we do ask for confirmation (can be disabled in settings). That removes the main reason for it being an option feature: accidentally deleting a message.
Since this feature request comes up regularly, I'll use this issue as a reminder to change the default to always show the delete action in notifications.

Very cool, thank you :+1:

I'd like to keep the issue open to track the work we still have to do. You should be able to unsubscribe from updates to this issue in the web interface.


chore(docs): Embed docs to DevHub

Description
This PR cleans up this repo for embedding frontends info developer-portal - https://github.com/shopware/developer-portal/pull/128
Type of change
ToDo's

[X] removed @shopware-pwa/typer private package, moved it to @shopware-docs/typer (now public/published)
[X] cleaned up apps/docs folder
[X] added shortcuts to package.json - docs:env, docs:link and docs:preview
[X] added DevHub workflows for previewing and deploying changes
[x] static sidebar
[x] fixed deadlinks, added missing files
[x] kept package.json
[ ] set up DEV_HUB_PERSONAL_ACCESS_TOKEN secret
[ ] deactivate Vercel integration

Screenshots
Additional context

What is missing? Can we somehow support it? Asking for a friend.

What is missing? Can we somehow support it? Asking for a friend.

I'll rebase, sync the typer package, then we can talk about the new docs workflow. You can still use your old (isolated) and new (embedded) workflows, and this branch is already published to prod (though not linked in the menu, it is searchable by Algolia and contents are provided to the Copilot AI).

@BrocksiNet This was rebased, but generated API references are not working on prod because of the new plugin structure. We'll need to adapt that on our end.

@BrocksiNet This was rebased, but generated API references are not working on prod because of the new plugin structure. We'll need to adapt that on our end.

Thx @bojanrajh :raised_hands: Great work.
We discussed updating our docs to the newest Vitepress version (see).
Do you see any problem with that? :grinning:

Technically, you could see changes in theme.json and package.json in this branch. You can also use clean version of config.ts (because config is already in baseConfig (and sidebar.ts). Keep your plugin definition and you should be good with your standalone docs.
This branch already includes the latest version, but there are 2 breaking changes: API reference (though, it should be properly generated in the standalone version, but not in the DevHub context) and local search (replaced with algolia). Along with possible minor CSS changes from past months (I did apply some stuff from this repo into the theme already).

Closing in favour of https://github.com/shopware/frontends/pull/1313, https://github.com/shopware/frontends/pull/1327 and https://github.com/shopware/frontends/pull/1337.


correcting README.md

In the section "Building ubridge" need to change "cd ubridge" to "cd uBridge".

thank you Dmitry!! just changed it. Any other feedback about these components or the documentation is highly appreciated.
Happy new year!
Best,


Not usable on CI

I tried your hack on our CI but container failed with "the input device is not a TTY". I understand it would not be possible to show progress bar but it should be possible to let the container running until stack is deployed with a proper message.

@soumyadipDe ok what's you CI solution?
This is probably a docker cli error because yes - your CI don't provide a tty - can you please try to run this command in place (notice the -it option removed)?
docker run -u root --rm -v /var/run/docker.sock:/var/run/docker.sock karibbu/docker-php:latest stack:converge myStack

I will add some instructions in the troubleshooting section of your README if it fixes your issue.

@soumyadipDe closing this issue, please reopen it if the given solution don't work for you.


[CARBONDATA-4266][Doc][summer-2021] Add TOC and format how-to-contribute-to-apache-carbondata.md

Why is this PR needed?
Fixed the terrible heading level mistake of old version how-to-contribute-to-apache-carbondata.md.
What changes were proposed in this PR?

Fixed heading level mistake.
Add TOC at the beginning.

Does this PR introduce any user interface change?

No

Is any new testcase added?

No

JIRA Issue: https://issues.apache.org/jira/browse/CARBONDATA-4266

Can one of the admins verify this patch?

add to whitelist

@chenliang613  The TOC (table of content) works now.

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5809/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4066/

Build Success with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/214/

LGTM


Add Introduction to Cryptographic Keys

closing, and adding edits in a separate PR.
@adamd for future ref, commits need to be signed, and the commit message needs to follow this format:
https://www.ockam.io/learn/guides/contributions/CONTRIBUTING/#commit-messages

🤦  Thanks @mattgreg — bookmarked for future reference.


startActivity breaks when moving from 0.9 to 0.9.1

I just spent hours trying to determine why all of a sudden I'm getting errors when trying to start an activity, it turns out that in moving from 0.9 to 0.9.1 something changed in Anko that causes the problem. I was not expecting a minor version change to be a breaking change.
When starting an activity with startActivity<T> it results in this error when compiled with 0.9.1
 java.lang.NoSuchMethodError: No virtual method getActivity()Landroid/app/Activity; in class Landroid/support/v4/app/Fragment; or its super classes

When I revert back to 0.9 it work as expected.

Duplicate of #311.


docker events and net-util

Ammended commit. Only changes were bin in .gitignore and removing TODO

LGTM


--use-fs-snapshot for macOS APFS

Output of restic version
restic 0.12.1 compiled with go1.16.13 on darwin/arm64
What should restic do differently? Which functionality do you think we should add?
Manage the creation of a point-in-time snapshot to use as the source of the backup when on macOS.
What are you trying to do? What problem would this solve?
Concurrent writes during backup without snapshots can cause a variety of silent corruptions. I wrote about some of the scenarios here: https://cyounkins.medium.com/correct-backups-require-filesystem-snapshots-23062e2e7a15
Snapshots can be managed using tmutil. Wikipedia says "Since macOS 10.13 High Sierra, all devices with flash storage are automatically converted to APFS. As of macOS 10.14 Mojave, Fusion Drives and hard disk drives are also upgraded on installation"
Cross reference #3557 , which is this for ZFS

Did restic help you today? Did it make you happy in any way?
restic is fantastic and I recommend it to everyone! Thank you.

Duplicate of #3714


S200 is meager

As in the title, S200, right ray topology on $\omega$, is meager (P56).

This is a part of #933.


How to find 's3://my-bucket/xgb-demo/model/0002.model'?

For bugs or installation issues, please provide the following information.
The more information you provide, the more easily we will be able to offer
help and advice.
Environment info
Operating System:
Compiler:
Package used (python/R/jvm/C++):
xgboost version used:
If installing from source, please provide

The commit hash (git rev-parse HEAD)
Logs will be helpful (If logs are large, please upload as attachment).

If you are using jvm package, please

add [jvm-packages] in the title to make it quickly be identified
the gcc version and distribution

If you are using python package, please provide

The python version and distribution
The command to install xgboost if you are not installing from source

If you are using R package, please provide

The R sessionInfo()
The command to install xgboost if you are not installing from source

Steps to reproduce

What have you tried?

I tried plot_model in demo/distributed training.

You should create a S3 bucket by logging into your own AWS account. Then upload your model into the bucket.


Update disease mapping for PheWAS

Asier to fill in details about disease mapping status
This is in progress and needs more work to be finished. Documents related to this can be found here: https://drive.google.com/drive/folders/1eS3MHRZeyjWQCOQXBJP4Lv-icn-Ra6mL

In December we wen't through the 733 diseases whose mapping had changed compared to the 2017 mapping. However, there are still 659 disease-EFO mappings to be checked, which will be progressively looked into in the next months.

We will schedule a mappathon with a few people to get this done for 19.08.

1,360 PheWAS traits have been mapped against EFO. Some traits, which contain multiple medical concepts, have been mapped against multiple EFO IDs; single medical concepts traits have been mapped against a single EFO ID.
Some new EFO terms were added to the ontology from HP and Mondo (86 HP terms and 28 Mondo terms) - see https://github.com/EBISPOT/efo/issues/728.
133 traits are missing from EFO and will be added at a later stage. A separate EFO SPOT github ticket will be raised for this.
@AsierGonzalez will be running the PheWAS pipeline.

The new mappings file has replaced the old one in the mappings repository: https://github.com/opentargets/mappings/blob/master/phewascat.mappings.tsv

Mappings file in the repo above updated with the latest EFO updates, which includes around 30 new requested terms now included in EFO. This completes the mapping of PheWAS Catalog traits to EFO.


Plugin to magically escape zsh meta-characters in git commands

The plugin simply autoloads git-escape-magic which is included here and
copied from https://github.com/knu/zsh-git-escape-magic .
This addresses #1115

Looks convenient. How about taking aliases of git into account, like g ? Could this not serve as a general escape-magic plugin ? For example zcalc also would be handier if * is auto escaped.

Never mind. Just found out at
http://stackoverflow.com/questions/11456403/stop-shell-wildcard-character-expansion/22945024#22945024
about alias g='noglob git'

Any comments on why this has not been merged? This is a convenient plugin for users of zsh and git  that otherwise needs manual fiddling to install.

I thought there wasn't any more interest in this plugin.

I am still interested in this. I have it in the custom plugins folder currently and have used it since this was opened.

Ok, I'll gladly merge this. Can you add a README with instructions on how to use it (for instance, that it doesn't work with git aliases) and update to the latest version of the git-escape-magic file?

Sure, I'll get to be by the end of the week. Thanks!

I'm cleaning house on my old PR's. I just updated this with a README and updated the script. I have also verified that this plugin still works. If there are no other concerns it should be ready for merge now. Thanks for the insane patience on this!

Just pinging on this, I'm still using it myself and I'm sure others would like to have access to it. Anything left to get it merged?

Congratulations on being probably the oldest PR merged (sorry)


Azure Deployment: DoNotDelete for specif folder

Hi,
is possible in Azure Deployment task set "DoNotDelete" for specific folder? When i uploading some image in my app to /wwwroot/img folder and i want not delete it on every deployment. It is possible via some additional arguments?

@jirisykora83
Yes you can skip your image folder from being deleted with every deployment. You just need to skip that folder.
Use following command as value of additional argument
-skip:Directory=wwwroot\\images

@Ajay-MS Thank you very much for your advice 👍


GPT4All Support for langchain.js

As a developer of an TypeScript application, I would like support for a GPT4All model in the javascript version of LangChain.

There's a discussion in this PR concerning this topic https://github.com/hwchase17/langchainjs/pull/1204

Yes this would be awesome! I believe there's a community package linked in that PR, but otherwise it looks like they're starting to put some resources into it and it may be available soon :)
https://github.com/nomic-ai/gpt4all/tree/main/gpt4all-bindings/typescript


Allow people to delete their account

This now works.
Accounts will be marked as inactive, the username will be reset to "Closed Account n", the bio will be cleared, the photo deleted, and social accounts and email addresses removed.
All content created will remain.


How to retrieve in the GPX file the content of the name tag of a WayPoint

Hi,
GPX plugin for Leaflet How to retrieve in the GPX file the content of the name tag of a WayPoint to display it in the popup sue cli of the marker?
get_name (): returns the name of the GPX track and not the content of the tag
  Col de Saint Ignace (64)
Best regard

Wpt_Name = String(feature.properties.name);


[QUESTION]How to config for using laravel-excel in Lumen 5.6.0

Versions
PHP version: 7.1.9
Laravel version: Lumen 5.6.0
Package version: 3.1.2
Description
In a fresh Lumen 5.6.0, i always got the following error:
(1/1) BindingResolutionException
Unresolvable dependency resolving [Parameter #0 [  $app ]] in class Illuminate\Filesystem\FilesystemManager
composer.json:
"require": {
"php": ">=7.1.3",
"laravel/lumen-framework": "5.6.*",
"vlucas/phpdotenv": "~2.2",
"maatwebsite/excel": "^3.0",
"illuminate/routing": "^5.6",
"league/flysystem": "^1.0.8"
},
bootstrap/app.conf, added:
$app->configure('filesystems');
$app->register(Illuminate\Filesystem\FilesystemServiceProvider::class);
maatwebsite/excel version in vendor/composer/installed.json is 3.1.2
Steps to Reproduce
Expected behavior:
Actual behavior:
Additional Information
Did I missed some config?

I have the same question, but my Lumen version is 5.5.2.

We currently don't "officially" support installing this into Lumen. I've just fixed some things that should improve Lumen support, but haven't done a full test-round on it yet.

Closing as https://github.com/Maatwebsite/Laravel-Excel/releases/tag/3.1.3 improves Lumen support