[SUPPORT]Whether there are some problems when using hudi-trino-bundle of 0.13.0 version to query hudi table of 0.12.2 version

Describe the problem you faced
Now I use trino of 407 version to query hudi table，hudi-trino-bundle version i use 0.13.0 version, and our hudi tables were created by 0.12.2 version. I need some help to confirm whether there are some problems of known by community when using different hudi version. Thanks!

There should not be any problem reading 0.12.2 version with hudi-trino-bundle of 0.13.0. Are you using trino-hive connector to query the Hudi table?

There should not be any problem reading 0.12.2 version with hudi-trino-bundle of 0.13.0. Are you using trino-hive connector to query the Hudi table?

Thanks, Yes, i use trino-hive connector and trino-hudi connector to query the hudi table. In our product scene, we use the two connector.

Got it. So, currently both trino hudi and hive connectors support only querying the COW tables and there is a PR out for MOR snapshot query support - https://github.com/trinodb/trino/pull/14786
I will close this issue. Feel free to reopen if you find any issues.


Ignore CSS properties that are not supported by React Native and turn some properties into numbers

you only have to change the src folder, not the build one.

Thank you for the PR.
https://circleci.com/gh/sabeurthabti/react-native-css/85


Launcher 8.0 path patch

Launcher 8.0 path has changed.
This patch correct it.

I'm not a reviewer or anything but I can confirm that this branch works for me on NixOS 23.05. Thank you :)

confirmed +1

friendly reminder :)

Any chance we can get this merged?

+1 from me as well ... maybe we should look for another maintainer or what's the concensus?


refactor(CategoryTheory/Monoidal): split the naturality condition of monoidal functors

Extracted from #6307. We replace μ_natural with μ_natural_left and μ_natural_right since we prefer to use the whiskerings to the tensor of morphisms in the refactor #6307.

Thanks very much!
bors merge


zwavejs2mqtt beyond 5.9.0 (5.10.0 and above) breaks usbip service

I am sharing my wave controller via usbip on an rPI.
When I use the docker image with tag 5.10.0 or above as soon as the container starts the usbip service fails and the usb device is no longer shared to the target host. I need to do this as I run docker on a VM in my environment and just have the rPI closer to the wave devices I am trying to control.
This worked perfectly since you released zwavejs2mqtt. I tried a bunch of versions from 5.10.0 upwards all the way to the latest tag with no luck.
Let me know if I can get you any more info to assist.

If you're running zjs2mqtt, you need to disable soft reset in the settings or set the environment variable to do so. This is a known issue caused by the new soft reset functionality.

Thank you that resolved my issue


Timeline for returning an item

@nishant-cyro @priyank-gupta I think this extension is incomplete unless we have associated time to return the product. Can we have the time in days associated with the product, so that customer can request return until then. Currently customer has no time limit on returning a product.

@bansalakhil - Thanks for the suggestion, we will include it in our next version.


⚠ Mobitopup has degraded performance

In a679d17, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 25317 ms

Resolved: Mobitopup performance has improved in c762c12.


Edit the cmdHistory entry

Add the possibility to edit the entry in cmdHIstory and searchHistory before execution. Appropriate keybindings, in my opinion, would be Ctrl-e in "Input" mode (like in fzf) and e in "Normal" mode.

Implements for #448 !
Try it if you want.
Usage:

Insert mode: <C-o>
Normal mode: e

I think this issue can be closed.


allow for no source URL (defer download to assemble script)

@bparees PTAL
These are the source-to-image changes needed for build config with no inputs.
They stem from this call in origin failing a source strategy build.
Also, I made this change origin only, and did not add any options to s2i.  The s2 user minimally still should point that command to a local directory with scripts.

BTW - the one travis failure was a hiccup building travis via make install-travis with golang 1.4.

i'll fix travis here: https://github.com/openshift/source-to-image/pull/438

OK ... update pushed.

lgtm.  note that someone still can't actually use the s2i command line w/o providing a source arg, but this will allow us to address the origin requirement anyway.
[merge]


Some tutorials can't open

Describe the bug
Some tutorials can't open
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/beta#
2.Click tutorial "Barrel Dodger"
Actual behavior
Some tutorials (Barrel Dodger, Simple Extensions, Maze, Setting the Scene, Breadcrumb Trail) can't open. It seems that the issue happened in the tutorial that needs tilemap.

Additional context
1.OS: Windows(rs6)
2.arcade version: 1.3.24
3.Microsoft MakeCode version: 6.8.10

@Sheila111 this seems to be fixed. Can you please validate?

@Sheila111 this seems to be fixed. Can you please validate?

@abchatra  These tutorials are fixed except Setting the Scene.

@abchatra  These tutorials are fixed except Setting the Scene.


Implement general state cheatcodes

Part of: https://github.com/runtimeverification/foundry/issues/12

It looks good, we need to wait for https://github.com/runtimeverification/evm-semantics/pull/1332 to fix the failed vs _failed issue.


[master] sync master branch with upstream opendatahub stable branch

sync master branch with upstream opendatahub stable branch
Getting ready for 2.11

Merging this PR, to get all the bits included in RHOAI 2.11


Bundled plugins are not configured during run requiring IDEA download.

It appears that bundled plugins (e.g. 'java') are not configured during a command-line run where a version of IDEA is downloaded.  It is configured correctly on a second run on the same machine when IDEA has already been downloaded previously.  (Meaning that the build works on the second invocation.)  This is a killer for CI builds that start with a clean slate.
Sources for testing are at: https://github.com/HaxeFoundation/intellij-haxe/pull/945
Gradle 5.5.1
gradle-intellij-plugin 0.4.9
IDEA 2019.2
From './gradlew removeIdeaCache; ./gradlew --info clean build verifyPlugin -PtargetVersion=2019.2' (an unsuccessful first run):
> Configure project :
Evaluating root project 'intellij-haxe' using build file '/home/ebishton/sandbox/github/EricBishton/intellij-haxe/build.gradle'.

Compiling build file '/home/ebishton/sandbox/github/EricBishton/intellij-haxe/build.gradle' using SubsetScriptTransformer.
Configuring IntelliJ IDEA gradle plugin
Configuring patch plugin.xml task
Configuring prepare IntelliJ sandbox task
Configuring prepare IntelliJ sandbox task
Configuring plugin verification task
Configuring run IntelliJ task
Configuring build searchable options task
Configuring jar searchable options task
Configuring building IntelliJ IDEA plugin task
Configuring publishing IntelliJ IDEA plugin task
Configuring IntelliJ resources task
Configuring IntelliJ compile tasks
Compiling build file '/home/ebishton/sandbox/github/EricBishton/intellij-haxe/build.gradle' using BuildScriptTransformer.
Target set to IDEA 2019.2
Including java plugin for version >= 2019.2
Configuring IntelliJ IDEA gradle plugin
Configuring patch plugin.xml task
Configuring prepare IntelliJ sandbox task
Configuring prepare IntelliJ sandbox task
Configuring plugin verification task
Configuring run IntelliJ task
Configuring build searchable options task
Configuring jar searchable options task
Configuring building IntelliJ IDEA plugin task
Configuring publishing IntelliJ IDEA plugin task
Configuring IntelliJ resources task
Configuring IntelliJ compile tasks
Including java plugin for version >= 2019.2
Configuring IntelliJ IDEA gradle plugin
Configuring patch plugin.xml task
Configuring prepare IntelliJ sandbox task
Configuring prepare IntelliJ sandbox task
Configuring plugin verification task
Configuring run IntelliJ task
Configuring build searchable options task
Configuring jar searchable options task
Configuring building IntelliJ IDEA plugin task
Configuring publishing IntelliJ IDEA plugin task
Configuring IntelliJ resources task
Configuring IntelliJ compile tasks
Including java plugin for version >= 2019.2
Configuring IntelliJ IDEA gradle plugin
Configuring patch plugin.xml task
Configuring prepare IntelliJ sandbox task
Configuring prepare IntelliJ sandbox task
Configuring plugin verification task
Configuring run IntelliJ task
Configuring build searchable options task
Configuring jar searchable options task
Configuring building IntelliJ IDEA plugin task
Configuring publishing IntelliJ IDEA plugin task
Configuring IntelliJ resources task
Configuring IntelliJ compile tasks
Including java plugin for version >= 2019.2
Configuring IntelliJ IDEA dependency
Using IDE from remote repository
IntelliJ IDEA dependency cache directory: /home/ebishton/sandbox/github/EricBishton/intellij-haxe/idea-IU/ideaIU-2019.2
Adding IntelliJ IDEA sources repository
Configuring IntelliJ IDEA extra dependencies []
IntelliJ IDEA IU-192.5728.98 is used for building
Configuring IntelliJ IDEA plugin dependencies
Configuring IntelliJ plugin java
Looking for builtin java in /home/ebishton/sandbox/github/EricBishton/intellij-haxe/idea-IU/ideaIU-2019.2
Configuring IntelliJ tests tasks

The line "Configuring IntelliJ plugin java" appears in the second run, when the required version of IDEA was already in gradle's cache, showing that the plugin is actually being configured and used.

BTW, this is a linux build, but appears to have the same problem on osx.  CI output is here: travis-ci.org/HaxeFoundation/intellij-haxe/builds/569183150

have you tried to debug it? Are you sure that the condition null != codeline && codeline.toInteger() >= 192 is true on the first run?

Yes.  But I will go verify it again.

I see that the problem is in your build script. You're trying to access to ideaDirectory before it was downloaded. Use ideaVersion variable to check whether java plugin should be installed

Hmm.  OK.  I'll go with that.  Thanks.


Set Cache-Control: max-age for static content (default: 1 day)

Cheers for this. Though in production, static content doesn't go through express at all (though still makes sense to merge)


fix-cleanup

Codecov Report

Merging #235 into master will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #235      +/-   ##
==========================================
+ Coverage    58.9%   58.95%   +0.04%
==========================================
  Files          40       40
  Lines        3244     3243       -1
  Branches      389      389
==========================================
+ Hits         1911     1912       +1
+ Misses       1227     1225       -2
  Partials      106      106

Impacted Files
Coverage Δ

vmmaster/cleanup.py
0% <ø> (ø)
:arrow_up:

core/auth/custom_auth.py
65.21% <0%> (-2.18%)
:arrow_down:

core/utils/network_utils.py
57.89% <0%> (+2.1%)
:arrow_up:

Continue to review full report at Codecov.

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


[x/gamm][Testing]

Story:

As an Osmosis engineer, I want to maximize test coverage so that I can be more confident about the quality of our code

[x] #1408
[x] https://github.com/osmosis-labs/osmosis/issues/1116
[x] #1407

[x] Done for spot price

[x] https://github.com/osmosis-labs/osmosis/issues/1371
[x] https://github.com/osmosis-labs/osmosis/issues/1372
[x] https://github.com/osmosis-labs/osmosis/issues/1448

Closing this issue since testings have diverged from the point this issue was opened, we should open a separate PR if there are more components to be visited for gamm testing


Automated cherry pick of #1877: fix glance list share resource

Cherry pick of #1877 on release/2.11.
#1877: fix glance list share resource

Codecov Report

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

@@              Coverage Diff               @@
##             release/2.11   #1878   +/-   ##
==============================================
  Coverage                ?   7.58%
==============================================
  Files                   ?     412
  Lines                   ?   63635
  Branches                ?       0
==============================================
  Hits                    ?    4825
  Misses                  ?   58399
  Partials                ?     411

Flag
Coverage Δ

#aFlag
7.58% <ø> (?)

Continue to review full report at Codecov.

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

/lgtm
/approve


Adding a fizz buzz generator with dynamic number of terms

My first PR

Thanks for your PR. While it's creative, it isn't really a solution to FizzBuzz. You basically replace a number by a string if one digit in the number matches. FizzBuzz is about numbers that are either divisible by 3, 5 or both.
Thanks anyway!


Manpage: missing sections

I cannot find manpage sections listed in the source code at _construct_manpage_specific_structure() in the generated manpage. Am I missing some configuration by any chance?
The generated manpage has those sections:
NAME
POSITIONAL ARGUMENTS
NAMED ARGUMENTS
AUTHOR
COPYRIGHT

While from the source code and usual best practices in manpage generation I was expecting to have:

a SYNOPSIS section with the synopsis of the command
a DESCRIPTION section with the description taken from the argparse parser
an OPTION section with what is now in the NAMED ARGUMENTS and maybe POSITIONAL ARGUMENTS too? I'm not sure if usually the positional arguments are documented inside the DESCRIPTION section.

I'm not familiar with docutils library, so I'm not sure if those were meant to be subtitles inside the section, but the final results doesn't seems to follow best practices and the docstring in the code.
Versions used:
Sphinx==1.6.4
sphinx-argparse==0.2.1
docutils==0.14
``

Did you add the :manpage: parameter?
I had to add it like so:
ots manpage
===========

.. argparse::
   :module: otsclient.args
   :func: make_common_options_arg_parser
   :prog: ots
   :manpage:

Seems this is missing from the docs.

@hstock, after adding the :manpage: sub directive, My arguments are not documented anymore.

Currently not working on the project that needed this - but I'll get back to this for debian packaging of opentimestamps. (I am not directly involved in sphinx-argparse)

I bumped into this bug while trying to generate tox's manpage using sphinx-argparse. I suspect the culprit is the usage of action groups in combination with a bug in the code. I think in this section of the code:
https://github.com/ribozz/sphinx-argparse/blob/178672cd5c846440ff7ecd695e3708feea13e4b4/sphinxarg/ext.py#L310-L312
…the second line should read if 'options' in action_group instead, no?


discourseAllPlugins: init discourse-checklist, discourse-data-explorer, discourse-migratepassword

Motivation for this change
discourse-checklist: allows rendering interactive checkboxes for TODO style posts

discourse-data-explorer: allows admins to run queries, useful for making it easier to export surveys

discourse-migratepassword: useful when migrating from another forum type while not requiring users to remake their password. For example, phpbb.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@dpausp Thanks for the review! I updated the update.py script to include the missing plugins. I couldn't easily test the updater though because it makes use of the experimental nix CLI and some changes in that latest nix version have broken it.


Id like to make some performance related changes

Hey there,
Im my research I need to generate a lot of GradCAM heat-maps which I then do further processing on. Im using the GradCAM class as I dont need other implementations right now - although I may decide to use some in the future. Ive performance tuned my work to as much as it can be. Using the torch profiler I discovered the greatest cost is due to moving data between the Cuda device and CPU.
Im already batching the GradCAM (and found a batch size of 8 seemed to be the most performant - more has a diminishing return).
Where I think there is improvement is allowing the GradCAM class and maybe others to use the Torch versions of Numpy functions to limit when the data is moved off device. I believe many of the actions could be done before moving the results back which should give a nice speedup. And in my case if I can get back a tensor result on device rather than a numpy result on CPU that would help in my work.
Im happy to investigate implementing this as a optional / configurable change - if thats something more agreeable. So that you have to opt in somehow. I just wanted to know if thats something others would like - before I fork and do it as I dont want to have to maintain a fork that diverges from the base work.
Id have to make changes to the BaseCam and GradCAM classes at a minimum.
My time right now is also very much limited which is why I wanted to ask if there is an appetite for these changes - as I might get a working concept that does what I need but not be able to change all the other CAM implementations too.

Hey,
I'm definitely open to changing everything to be done with pure torch on the device instead of numpy.
But before investing in this large change,
Should we get some data point on how much faster Grad-CAM would be this way ? Could also be in a quick and dirty implementation of this.
To get a motivation for doing this and see if it's worth it.

Cool so I have made a proof of concept. Its quite crude.
Appears to be somewhat faster in my code.
I will continue this later. Its very late where I live so Im calling it a night.
I have tried to add comments / document as I go. My aim in the draft PR is to get just enough to work that I can build some proper benchmarks before and after so we can see if this is worth implementing.
One potential change is around the use of cv2.resize. I have not found a one to one equivalent, and at least for my particular use-case I managed to remove it. When completing the PR this will have to be looked at more closely.

Im thinking of benchmarking a DataSet like Cityscapes on a default Resnet50 or something similar. Ill post the code in the PR when I write it too.
I want it to be as generic as possible and make use of the torchvision stuff. So thats its a fair before and after comparison.

Okay some good and some bad news.
My benchmark shows its faster but only marginally.
Ill do a more extensive benchmark across some more models later.
The reason my own code is noticeably faster is possibly because I use the tensor on the GPU and dont have to convert the Numpy result back into a tensor after computing it - removing all those operations.
Ill create some nice looking markdown tables and maybe some graphs later
I also want to make the benchmark more advanced and try scaling batch size and other bits to see what happens. I luckily have access to a fairly good compute machine (and can schedule get way bigger machines if need be)

Also tests super failing right now 😭 ... but to be expected

Sorry about going quiet. Working full time and needing to write my thesis draft + some papers. And presenting at a conference in two weeks ...
But my experiments are slower than expected ... by days so will be investing more time into this soonish


Dots are laggy

Hi, dots are feels laggy when you slide screens. Anyone know why is that or how to fix it ?
It may cause of development env? I tested on snack.expo it is still same.

Please try in prod env, it should be decently responsive.

Closing for inactivity, feel free to reopen is necesarry.


Fix macOS typo

@microsoft-github-policy-service agree

Thank you for the contribution, closing this as it's bundled into the most recent readme update #80


fix #1959

Fixing the auto-scroll issue, also realized that prep didn't have an editable restriction so showed the delete button all the time (not a biggie cause users couldn't actually delete) so added it.
It works like this:

Coverage decreased (-0.03%) to 91.518% when pulling 4b19b45ec8e181db71cff83d89b1014eb0315348 on antgonza:fix-1959 into 4e380e04488c353a741c0766bf478778aa30ffbc on biocore:master.


Improve TagHelper resolution speeds 2x

When a project gets updated TagHelpers we used to put it on a delay of 3s before publishing any information for it. I changed that logic to fast-path TagHelper resolution (no delay) if we detect that potential TagHelper changes have happened.
Added and updated tests.

Before

After

Fixes dotnet/aspnetcore#35129

Sorry, somehow missed this comment when I initially responded. Feel free to call me out next time 😄

lgtm! Just wondering, are there any negative implications if we directly publish instead of queuing?

SO yes technically. It means we're doing a bit more work to ensure our system stays "accurate". For instance, when a project is initializing it'll go through a few phases:

No TagHelpers: C# workspace is still being put together
TagHelpers in packages: C# workspace has metadata references but the semantic model for active sources is still being determined
All TagHelpers, C# workspace is complete, we have TagHelpers from packages + from the active projects.

With the old model of Enqueuing we'd typically go from step 1 to step 3 in terms of colorization / TagHelper understanding. At least for smaller projects. With the new model we go through each phase so you'll see your project gradually gain capability. Now that being said, it means we've effectively increased the TagHElper resolution work by 33%; however, we've optimized that flow significantly so it shouldn't be the worst.

3 seconds does seem to be an excessive time-frame though, is that long time just a product of when we were starting out and perf was much worse?

Ya 3 seconds is a long time. The intent behind it was that when a project is initializing our project manager is also hammered with document added events (it adds each doucment individually). The 3s back then seemed to be a reasonable timeframe to not re-publish / re-calculate the world N number of times where N was the number of documents.  I didn't want to boil the ocean toooo much so left the number alone for now given it rarely has an impact


warning during AOT compilation

Version info

Angular: 5.0.3
Firebase: 4.6.2
AngularFire: 5.0.0-rc4
Other (e.g. Ionic/Cordova, Node, browser, operating system):
How to reproduce these conditions
Failing test unit, Plunkr, or JSFiddle demonstrating the problem

Steps to set up and reproduce
launch AOT build with: ng build --aot
Expected behavior

no warnings
Actual behavior
activeWarning: Can't resolve all parameters for AngularFirestore in /home/phra/git/bloqmanager/node_modules/angularfire2/firestore/index.d.ts: ([object Object], ?). This will become an error in Angular v6.x
Warning: Can't resolve all parameters for AngularFirestore in /home/phra/git/bloqmanager/node_modules/angularfire2/firestore/index.d.ts: ([object Object], ?). This will become an error in Angular v6.x

Already reported https://github.com/angular/angularfire2/issues/1280 and https://github.com/angular/angularfire2/issues/1206


test: add didcomm test

Description:
Summarize the changes you're submitting in a few sentences, including Jira ticket ATL-xxxx if applicable.
Link to any discussion, related issues and bug reports to give the context to help the reviewer understand the PR.
Alternatives Considered (optional):
Link to existing ADR (Architecture Decision Record), if any. If relevant, describe other approaches explored and the selected approach. Documenting why the methods were not selected will create a knowledge base for future reference, helping prevent others from revisiting less optimal ideas.
Checklist:

[ ] My PR follows the contribution guidelines of this project
[ ] My PR is free of third-party dependencies that don't comply with the Allowlist
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked the PR title to follow the conventional commit specification

coverage: 48.539%. remained the same
when pulling d193c55c076d6a7189c1df565509f24dfa06a656 on tests/didcomm
into 5830a7e17a72abae98faa81594421aa577eaeb24 on main.


[Bug]: Settings stays the same even after changing them

/mv version -p output
https://paste.gg/p/anonymous/606203594924413c909db2ce37b48fce
Server logs
https://paste.gg/p/anonymous/3faba0479ff04ec5a6263eaacc3900fa
Server Version
Server is running Leaves version git-Leaves-"10e2199" (MC: 1.20.1) (Implementing API version 1.20.1-R0.1-SNAPSHOT) (Git: 10e2199)

Bug Description
Changing the settings for Multiverse does not change when I restart the server
Ex: autoload 'true'  >  'false'  doesn't do anything and in the config for MV it is still set to 'true'
Steps to reproduce
1 Start Server
2 Change a setting in the MV World Config
3 Restart Server
4 Check MV Config
5 Still the same
Agreements

[X] I have searched for and ensured there isn't already an open or resolved issue(s) regarding this.
[X] I was able to reproduce my issue on a freshly setup and up-to-date server with the latest version of Multiverse plugins with no other plugins and with no kinds of other server or client mods.

This is known behaviour, you need to change config values while the server is off


[RFE] [OSP16] Environment variable with option for OVN with DVR-HA

Currently, Jetpack deploy osp16 with default ml2-ovn with ovn ha service template, where the controllers are act a gateway chassis.
/usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovn-ha.yaml
For DVR based deployment, Jetpack environment "jetpack/group_vars/all.yml" needs enhancement with ovn_dvr option which can deploy the overcloud with the ovn-dvr-ha service template, if the compute have dedicated external NIC.
/usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovn-dvr-ha.yaml

@pradiptapks Thanks for bringing this up, but can we not use the extra_templates option in group_vars/all.yml to pass the DVR template?

https://github.com/redhat-performance/jetpack/pull/167 should address this


add vast example to infra

Adding Vast as an example for infra

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 68.47%. Comparing base (be65c27) to head (4b6bb6c).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

:exclamation:  There is a different number of reports uploaded between BASE (be65c27) and HEAD (4b6bb6c). Click for more details.
HEAD has 5 uploads less than BASE

Flag
BASE (be65c27)
HEAD (4b6bb6c)

6
1

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #343      +/-   ##
==========================================
- Coverage   77.95%   68.47%   -9.49%
==========================================
  Files          35       35
  Lines        2531     2531
==========================================
- Hits         1973     1733     -240
- Misses        558      798     +240

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Toasts should raise a FAB

Resources:
Before submitting an issue, please consult our troubleshooting guide (http://ionicframework.com/docs/troubleshooting/) and developer resources (http://ionicframework.com/docs/developer-resources/)
Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[X] 3.x
I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
On a page with a FAB, triggering a bottom-positioned toast (mostly) covers the FAB, making it very hard to click the FAB without first having to dismiss the toast (which might not be possible through user interaction).
Expected behavior:
The toast should lift the FAB while it is displayed. This is defined in the Material Design specification.
Steps to reproduce:
Other information:
This issue has been opened before at #12139 and was closed as a feature request moved to the internal list. As suggested in the last comment by @AmitMY, I am reopening this here as a bug report because I agree that this is a bug in an existing feature rather than a feature request.
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
cli packages: (/home/ingo/.npm-global/lib/node_modules)

    @ionic/cli-utils  : 1.9.2
    ionic (Ionic CLI) : 3.9.2

System:

    Node : v8.4.0
    npm  : 5.3.0
    OS   : Linux 4.11

I have implemented a temporary solution. It is an Angular / Ionic 3 directive that allows Ionic toasts to animate the fab buttons and other elements in the fixed-content div of a page accordingly.
All you have to do is to include the directive in your project and then add a corresponding element in your app component template:

Please check out the code here:
https://gist.github.com/maumchaves/d7270b54afd5c8ae120f34b41436a119


[SDK] Sync Transformers version for train API

We should keep Transformers version the same with our Trainer image.
Otherwise, users can see the errors with incompatible arguments for HuggingFace Trainer
/assign @johnugeorge @deepanker13 @tenzen-y

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall first build on fix-version-transformer at 35.374%

Totals

Change from base Build<PHONE_NUMBER>:
35.4%

Covered Lines:
4374

Relevant Lines:
12365

💛  - Coveralls


[5.7] Emit language-specific relationships

Explanation: Display language-specific relationships information for symbols that have different relationships in Swift vs. Objective-C. For example, when subclassing NSObject, the Swift compiler synthesises protocol conformances that are only available in Swift.
Scope: DocC multi-language support
Radar: rdar://91627374
Risk: Medium
Testing: Added automated tests, verified that existing tests pass, and tested manually.
Reviewer: TBD

Testing with SymbolKit passed here: https://github.com/apple/swift/pull/59523


seg fault at start

eovim --version: last git
nvim --version | head -n1: NVIM v0.4.3
edje_cc --version:1.23.3
Installed on debian bullseye after installing
enlightenment libefl-all-dev neovim libmsgpack-dev

I am ready to help fixing that :
GNU gdb (Debian 9.2-1) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from eovim...
(No debugging symbols found in eovim)
(gdb) r
Starting program: /home/nous/eovim/build/eovim
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff456a700 (LWP 73787)]
[New Thread 0x7ffff3d69700 (LWP 73788)]
[New Thread 0x7ffff3568700 (LWP 73789)]
[Thread 0x7ffff3568700 (LWP 73789) exited]
[Detaching after fork from child process 73790]
[New Thread 0x7ffff208d700 (LWP 73791)]
Thread 1 "eovim" received signal SIGSEGV, Segmentation fault.
0x00007ffff74d5128 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) Quit
(gdb)

Thanks for the report. It's something that goes away with EFL dev (at least on EFL commit ca169ec715, which I'm based on). IIRC, there was a bug with text classes in edje files prior 1.24...
I'm working on changes that get rid of them and should resolve this. Hopefully to land this month.
As a local workaround, you can add:
font='the font name' font_size=10

to all the styles in default.edc. It should allow eovim to run, but with limited font support.

Mmm, sorry, I am novice, I see only one default.edc (and I have no idea what it is...).
Should I add the line
font='the font name' font_size=10
as it is, just at the end of this file after :
   #include "cursor.edc"
#include "tab.edc"
}
.....?

And I see styles in it :
   style { name: "cmdline";       base: "color=#bcbcbc wrap=word left_margin=2 right_margin=2 text_class=cmdline";    }   style { name: "cmdline";       base: "color=#bcbcbc wrap=word left_margin=2 right_margin=2 text_class=cmdline";    }

Sorry, I should have been more specific. Yes, that's there.
diff --git a/data/themes/default.edc b/data/themes/default.edc
index 523ea26..d68f5b6 100644
--- a/data/themes/default.edc
+++ b/data/themes/default.edc
@@ -38,10 +38,10 @@ color_classes {
 }

 #define CMDLINE_INFO_STYLE(Color) \
-   "font_weight=Bold text_class=cmdline color="Color" left_margin=8 right_margin=8"
+   "font=Courier font_size=14 font_weight=Bold text_class=cmdline color="Color" left_margin=8 right_margin=8"
 styles {
    style { name: "cmdline";
-      base: "color=#bcbcbc wrap=word left_margin=2 right_margin=2 text_class=cmdline";
+      base: "font=Courier font_size=14 color=#bcbcbc wrap=word left_margin=2 right_margin=2 text_class=cmdline";
    }
    style { name: "cmdline_slash_info";
       base: CMDLINE_INFO_STYLE("#ffffa7");

If you make the changes in the diff above, Eovim should not segfault. Here, I used the Courier font with size 14. However, changing the font after startup will not take effect in some parts... I have to find a proper fix for this to work with EFL 1.23.
Also, I just noticed that there is a weird behavior with Courier, (there is "wave effect when the cursor changes lines) that I do not observe with Fira Code.

Ok, fine after reinstall :
sudo cmake --build . --target install
Thank you very much !

For reference, the font problems in EFL 1.23 (and probably earlier versions) seem to be mentioned in upstream T8477.


Send the entire notification payload to the client

Currently, when receiving a notification, we only send the title and message to the client. Let's copy the entire payload to a data object, so the app has some more flexibility.

It's all copied into a data object. Check the readme for details.

@EddyVerbruggen You legend! You did this sooner than expected. Can now pretty much complete my app!
Cheers bud!


How to aggregate same classes in different screens ?

I have this in my class :
cell-date p {
  @screen xs {
    @apply pl-6;
  }
  @screen sm {
    @apply ml-6;
  }
  @screen xl {
    @apply ml-8;
  }
}

Is there way to aggregate xs and sm and use one class , for example :
@screen xs, sm{
@apply ml-6
}

If your screens are min-width based then @screen xs {…} will already do what you want.
However, this could still be useful in situations where screens have been customized or where the rules have to apply to discontiguous screen sizes (e.g. xs and md but not sm because it already has separate styles applied).
ping @adamwathan If this is something you'd want I've already got the code and tests written for this and can open a PR (the existing setup made it like a 2 minute change ¯\_(ツ)_/¯).

@thecrypticace , yes I've customized my screens using intervals :

screens: {
            'xs': {
                'min': '320px',
                'max': '659px'
            },
            'sm': {
                'min': '640px',
                'max': '767px'
            },
            'md': {
                'min': '768px',
                'max': '1023px'
            },
            'lg': {
                'min': '1024px',
                'max': '1279px'
            },
            'xl': {
                'min': '1280px'
            },
        },

@adamwathan , do you have a suggestion  to ignone code duplication in different screen sizes?

I do see a strong use case for the ability to aggregate multiple @screen sizes in one line of code.


Enable server-side search by default

Hi, I'm not sure if we need to check the account's IMAP Capabilities to verify that is supported.
Closes #5499

The goal of issue #5499 is to get rid of the setting, not just change the default value.


Database files not deleting?

Hello! I have a small issue with file deletions in my application. Basically, it seems that the database only unlinks(?) the entries from the database but the files remain in the computer. Sometimes deleted entries seem to be reindexed randomly on refresh or startup.
Opening db
let LinvoDB = require("linvodb3");
LinvoDB.defaults.store = { db: require("medeadown") };
LinvoDB.dbPath = process.cwd();
let Doc = new LinvoDB("doc", { text: String, time: Date});
let doc = new Doc();

This is the command I use to delete everything:
    Doc.remove({ }, { multi: true }, function (err, numRemoved) {
      console.log("Removed: " + numRemoved);
    });

This is how I delete an entry:
 Doc.remove({ _id: id }, {}, function (err, numRemoved) {
      doc.save(function(err) {
        if (err) {
          console.error("Delete error:" + err);
        }
      });
      console.log("This is the item's ID that will be deleted: " + id);
    });

This is how I add an entry
Doc.update({ _id: id }, { $set: { text: text } }, function (err, numReplaced) {
      doc.save(function(err) { /* saving the document */ });
});
  };

This is how I populate on startup
 Doc.find({}).sort({time: 1})
  .filter(e => (e.text !== undefined))
  .map(res => {populateTable(res.text, moment.unix(res.time).format($("#time").val()), res._id);})
  .exec(function(err, res) {
  });

Sorry if I pasted too much stuff in here. If it's not an actual issue with Linvodb I'd greatly appreciate some support! It's the biggest bug I currently have in my app and can't seem to get the hang of it...
Thank you!

Do the entries actually stay in the database? Or only on the filesystem?
If it's only on the FS, it's pretty normal, as medea won't delete the entries unless you call compact ( can't remember how it was called ).
But if they also stay in the db after .remove is called, then we may have an issue in linvodb

Doing
cat *.medea.data

in the doc.db folder shows the files contents - so I guess I have to use db.compact()? Should I do this after entry deletions and, when there's the case, the whole db deletion?
Sometimes - rarely though, deleted stuff turns up on the database using  Doc.find({}) when I populate the table on startup or refresh.

Can you try with the level-js (https://www.npmjs.com/package/level-js) backend if conditions permit it?
Just so as we can evaluate if the problem is in linvodb or medea.
Also, if it suits you, level-js might be a better option altogether

Sure thing.
Creating an entry worked great.
Deleting a single entry - Doc.remove seems to remove everything except id
{"text":"assets","time":1453640671,"_id":"pzXwX9WX347uvuCV"}"
"{"_id":"pzXwX9WX347uvuCV"}"

Think this could be my fault because the _id is actually the Key so there's no need for _id? I wonder how I'd access the key for deletion. I'll look into it.
Database destroy worked nicely. I guess dbPath is not needed anymore because I'm using indexedDB?

dbPath may still be used I think because it should be passed as a prefix to the indexeddb keys
Use it to avoid conflicts.
Yeah, _id is the key. How does actually the object become to an _id object only? Does that get returned from db lookup? If so, it's a bug

Think I was wrong. It seems that a Key Value pair with an ID and a key get returned on each refresh only if I create an intended new entry before the refresh and it's inconsistent, it does not always happen. I hope I'm explaining well enough.
The results themselves are not returned by the find({}), but they're in Resources > IDBWrapper.


Support hooks to add custom documentation to objects, fields, arguments and enum values

We came up with a documentation technique that works well for us (syncing both development teams and our product documentation team). We're trying to resolve the relevant Markdown documentation for each object, field, argument and enum value.
SchemaGeneratorHooks is an awesome general purpose vehicle for intercepting schema generation. I think it can be very helpful in this case, but it would have to be extended to include hook methods that would allow me to augment builder objects just before calling build(). That way I can call the builders' description method and add my own documentation. Specifically I'm asking for the inclusion of the following hooks:
fun willGenerateGraphQLObject(objectName: String, builder: graphql.schema.GraphQLObjectType.Builder): graphql.schema.GraphQLObjectType.Builder = builder

fun willGenerateGraphQLField(objectName: String, fieldName: String, builder: graphql.schema.GraphQLFieldDefinition.Builder): graphql.schema.GraphQLFieldDefinition.Builder = builder

fun willGenerateGraphQLEnumType(enumName: String, builder: graphql.schema.GraphQLEnumType.Builder): graphql.schema.GraphQLEnumType.Builder = builder

fun willGenerateGraphQLEnumValue(enumName: String, enumValue: String, builder: graphql.schema.GraphQLEnumValueDefinition.Builder): graphql.schema.GraphQLEnumValueDefinition.Builder = builder

fun willGenerateGraphQLArgument(objectName: String, fieldName: String, argumentName: String, builder: graphql.schema.GraphQLArgument.Builder): graphql.schema.GraphQLArgument.Builder = builder

I added the names of the objects/fields/arguments/enums to the hooks' contexts since it's difficult to extract that information from the builders directly.
What do you think?
Thanks a lot for a fantastic library!

You can add custom documentation using `@GraphgQL

You can add custom documentation using @GraphQLDescription annotation that can be added to any type. See https://github.com/ExpediaDotCom/graphql-kotlin/wiki/Fields#documenting-fields for more details.
Is there some additional functionality needed that current annotation doesn't provide?

GraphQL supports Markdown schema documentation. Our technique is pretty basic - we maintain a directory with Markdown files. The documentation can be as rich as Markdown allows (we use paragraphs, links, tables etc). Within those files an h1 (# ...) demarcates a beginning of a type documentation. h2 (## ...) demarcates a beginning of a field documentation. The directory structure doesn't really matter so we can organize these files as we see fit. Several types can be documented in the same file. Our documentation team uses an external tool to author the files (mostly https://typora.io/).
Maintaining documentation by passing an argument to an annotation is disadvantageous because:

it's very limiting. It isn't convenient to read/write anything more than pretty short string values. We don't consider that adequate documentation for our API.
it's maintained as part of the code. While this may be perfectly fine in many case we find it hinders collaboration with our documentation team.
There can be many GraphQL API endpoints implemented using different stacks but we would like the documentation for all of them to be maintained coherently using the same documentation method.

We generate another GraphQL schema for another use case not using graphql-kotlin using the documentation technique I described above successfully and we would like to continue to document all our APIs in similar way.
We would happily contribute the above mentioned documentation technique although it's very simple. It only involves scanning a directory for Markdown files, parsing them using https://github.com/vsch/flexmark-java and providing a resolution method for types and fields.

@liqweed I see why you would want this with your dynamic documentation.
We could add a method for every GraphQLType implementation but would it make more sense if we added a hook at the the same location as didGenerateGraphQLType? This is called right before we add the type to the schema but that is not helpful for you since we don't use the modified value if you were to change it in the hook.
If we added a new hook at the same location as didGenerateGraphQLType, we can have you modify the type by passing it into a builder again and the returning it.
/**
 * Called after using reflection to generate the graphql object type but before returning it to the schema.
 * This allows for modifying the type info, like description or directives
 */
fun willAddGraphQLTypeToSchema(type: KType, generatedType: GraphQLType): GraphQLType = generatedType

Your hooks can check all the possible types
override fun willAddGraphQLTypeToSchema(type: KType, generatedType: GraphQLType): GraphQLType {
    return when (generatedType) {
        is GraphQLScalarType -> GraphQLScalarType.Builder(generatedType).description("My custom description + old one: ${generatedType.description}").build()
        else -> generatedType
    }
}

Actually I noticed that we already have this with the onRewireGraphQLType but it is just not called for all the object types. If I fixed that you could use that hook in the same way as above

To add description for fields I would also need the field's name at that point. The builders don't expose the added fields for inspection or manipulation.
If I understand correctly, according to your suggestion I should traverse all the information in the builder, including its fields, and create a copy based on that - right?

Are there use cases for mutating hooks besides adding markdown, could it be used to implement custom directives? https://github.com/ExpediaDotCom/graphql-kotlin/issues/88#issuecomment-447260683

@liqweed You can access the name of the generatedType since at this point in the hook, it is fully generated. You can also look at the info on the KType but that is not always the most accurate if you are using this like @GraphQLName to override the type name

@rharriso This hook can be used at this point to add any more info to the type, not just documentation. We already have a way to do custom directives, documented here: https://github.com/ExpediaDotCom/graphql-kotlin/wiki/Schema-Directives
The comment you are referring to is a way to expose a config method or setting to provide a list of pre-configured directives instead of using the onRewireGraphQLType. There are slightly different issues.

@smyrick To make sure I follow your comment about modifying fields using this new hook, do you mean like so?
class DocumentationSchemaGeneratorHooks : SchemaGeneratorHooks {
    override fun willAddGraphQLTypeToSchema(type: KType, generatedType: GraphQLType): GraphQLType {
        return when(generatedType) {
            is GraphQLObjectType -> {
                val builder = GraphQLObjectType.Builder(generatedType)
                builder.clearFields()
                generatedType.fieldDefinitions.forEach {
                    builder.field(GraphQLFieldDefinition.Builder(it).description(resolveFieldDocumentation(generatedType.name, it.name)))
                }
                builder.description(resolveTypeDocumentation(generatedType.name)).build()
            }
            else -> generatedType
        }
    }
}

@liqweed Yep that looks correct, I know it's a few lines to parse but with some helper functions you can reuse the code for all the types, not just object types.
If that doesn't work please feel free to create a new issue with this hook

@smyrick Thanks, I think that would do.
Thank you for such a quick handling of the issue!
Looking forward to seeing this in an upcoming release.

This mechanism works well for all GraphQLTypes except for GraphQLInterfaceTypes.
The following code:
    override fun willAddGraphQLTypeToSchema(type: KType, generatedType: GraphQLType): GraphQLType {
        return when (generatedType) {
            is GraphQLInterfaceType -> GraphQLInterfaceType.newInterface(generatedType)
                .description("My resolved description").build()
            else -> generatedType
        }
    }

Produces the following error:
graphql.AssertException: All types within a GraphQL schema must have unique names. No two provided types may have the same name.
No provided type may have a name which conflicts with any built in types (including Scalar and Introspection types).
You have redefined the type 'Result' from being a 'GraphQLInterfaceType' to a 'GraphQLInterfaceType'

	at graphql.schema.GraphQLTypeCollectingVisitor.assertTypeUniqueness(GraphQLTypeCollectingVisitor.java:105)
	at graphql.schema.GraphQLTypeCollectingVisitor.visitGraphQLInterfaceType(GraphQLTypeCollectingVisitor.java:58)
	at graphql.schema.GraphQLInterfaceType.accept(GraphQLInterfaceType.java:152)
	at graphql.schema.TypeTraverser$TraverserDelegateVisitor.enter(TypeTraverser.java:71)
	at graphql.util.Traverser.traverse(Traverser.java:147)
	at graphql.schema.TypeTraverser.doTraverse(TypeTraverser.java:58)
	at graphql.schema.TypeTraverser.depthFirst(TypeTraverser.java:50)
	at graphql.schema.TypeTraverser.depthFirst(TypeTraverser.java:38)
	at graphql.schema.SchemaUtil.allTypes(SchemaUtil.java:42)
	at graphql.schema.GraphQLSchema.<init>(GraphQLSchema.java:102)
	at graphql.schema.GraphQLSchema.<init>(GraphQLSchema.java:37)
	at graphql.schema.GraphQLSchema$Builder.build(GraphQLSchema.java:411)
	at com.expedia.graphql.generator.SchemaGenerator.generate$graphql_kotlin_schema_generator(SchemaGenerator.kt:68)
	at com.expedia.graphql.ToSchemaKt.toSchema(toSchema.kt:24)
	at com.expedia.graphql.ToSchemaKt.toSchema$default(toSchema.kt:21)

@liqweed These seems like a valid error, I have created a new issue which is open for anyone to work on https://github.com/ExpediaDotCom/graphql-kotlin/issues/281


HTML entities are not encoded when using plain text

Using this Markdown code:
```text
<b>test</b>
```

The HTML is not encoded and I end up with a code block that just says "test", in bold. In other words this is the HTML output:

test

It should be this:

<b>test</b>

Using any other language (e.g. js) encodes the entities correctly. As does omitting a language (just using ```) but then you don't get the default highlighting (box colour etc).

Duplicate of https://github.com/11ty/eleventy-plugin-syntaxhighlight/issues/54#issuecomment-1169031169 (some discussion and solutions over there, thank you!)


Can you provide some guidance in Scale UP operation for ASE based App Service?

I was recently in a situation where instead of properly configuring scale out rule, customer tried to scale up their App Services deployed in ASE and the outage lasted for 4 hrs. . So in that case can you provide some guidance or refer me to doc link on best practice on Scaling up App Service deployed in ASE ? E.g. Is there any documentation on guidance or warning, pitfall of doing Scale up operation on production App deployed in ASE without testing/simulating it on Staging/Test environment? And what should they expect in terms of downtime/outage etc.

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

ID: 6ffd3caf-247a-a3ce-f667-a4923189aa44
Version Independent ID: 34673bc0-4ab6-9f62-d032-224e4d937a08
Content: Scale an app in ASE v1 - Azure App Service Environment
Content Source: articles/app-service/environment/app-service-web-scale-a-web-app-in-an-app-service-environment.md
Service: app-service
GitHub Login: @ccompy
Microsoft Alias: ccompy

@Anand-Moghe Thank you for reaching out. We will investigate and update the thread further.

Apologies for the delay! Firstly to highlight on how scaling works - Every App Service app runs in an App Service plan. The container model is environments hold App Service plans, and App Service plans hold apps. When you scale an app, you scale the App Service plan and thus scale all the apps in the same plan.
In ASEv2, when you scale an App Service plan, the needed infrastructure is automatically added. There is a time delay to scale operations while the infrastructure is added. In ASEv1, the needed infrastructure must be added before you can create or scale out your App Service plan.
However, in the multitenant App Service, scaling is usually immediate because a pool of resources is readily available to support it. In an ASE, there is no such buffer, and resources are allocated upon need.
The document that you're referring to, does highlight as a note on scale out scenarios:
"Moving an ASP from one worker pool will cause cold starts of the apps in that ASP. This can cause requests to run slowly as your app is cold started on the new compute resources. The cold start can be avoided by using the application warm up capability in Azure App Service." , kindly let us know if this isn't clear or you wish to see more points on this topic.
Kindly find the docs below which highlights on how scaling works & provides generic scaling guidance:
https://docs.microsoft.com/azure/architecture/best-practices/auto-scaling
https://docs.microsoft.com/azure/app-service/environment/using-an-ase#how-scale-works
Thanks again for your feedback! We will close this out, but if you feel you need more information please just let us know we will continue the discussion.


[Workers] Refactor timingSafeEqual example

Refactored the description to talk a little bit more about why you should use timingSafeEqual and adapted the example to be a proper Worker example.
cc @elithrar (might be of interest to you)

@jasnell, is this something you could help validate?

Thanks for the contribution, @KianNH!


Wrong group name

Hey Moulberry,
I think the group name in build.gradle.kts is not right.
https://github.com/Moulberry/AxiomPaperPlugin/blob/3954a72ce94a35d6af22d2d1291aac723db06468/build.gradle.kts#L10

Fixed


Can't build

I tried to build on windows 10 and Ubuntu 17.04, it installs but won't build. I downloaded the zip from github then extracted it and ran install/build as mentioned on the "Developing" section of the page
For the build I get this on windows and linux respectively:
> postscribe@ build C:\Users\Dan\Desktop\postscribe-master
> gulp build

[17:30:58] Requiring external module babel-register
resolve failed for "babel-runtime": Error: Cannot find module 'babel-runtime'
resolve failed for "webpack-core": Error: Cannot find module 'webpack-core'
resolve failed for "@semantic-release": Error: Cannot find module '@semantic-release'
semantic-release WARN invalid config loglevel="notice"
semantic-release ERR! post Command "build" not recognized. Use either "pre" or "post"

> postscribe@ build /home/dan/Desktop/postscribe-master
> gulp build

[17:33:12] Requiring external module babel-register
resolve failed for "babel-runtime": Error: Cannot find module 'babel-runtime'
resolve failed for "webpack-core": Error: Cannot find module 'webpack-core'
resolve failed for "@semantic-release": Error: Cannot find module '@semantic-release'
semantic-release WARN invalid config loglevel="notice"
semantic-release ERR! post Command "build" not recognized. Use either "pre" or "post"

For the install I get this on windows an linux respectively:
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 1308 packages in 62.94s

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 1308 packages in 173.877s

@danielocdh you could try to replace es2015-loose with es2015 in package.json

From:
  "babel": {
    "presets": [
      "es2015-loose"

To:
  "babel": {
    "presets": [
      "es2015"

That did it, thanks.
The output was a bit different than the CDN files but I think that was all because of different versions of dependencies/compilers, should work the same.


Made SuperBoL Python3 compatible

see below

Thank you @guillochon for taking care of the Python 3 compatibility on the current release!
Cheers,
Jeremy


latcontrol_torque: deprecate yaw-based curvature

Description
The use_steering_angle = False path of the lateral accel torque controller is broken, possibly by #33283. The breakage escaped notice because this path isn't used by any supported cars.
We can either:

Fix it, the most obvious fix being b6166fc6b2ba815e976778f35119f332ee561d73.
Deprecate it since it's unused and has no CI coverage, this PR.

[ ] Requires commaai/opendbc#1214

Verification
CI testing.
Route
Route: 04836f13759962ab/00000097--450580dbd3
Additional Info
I drove on a fixed version earlier today, trying to gain insight into problems with roll compensation. When we need to hold a straight line on variably-banked rural two-lane highway, it actually performs better than the vehicle-module curvature, but it's too noisy to turn smoothly or handle freeway speeds in its current form.
I would be a little sad to deprecate it, but perhaps the core idea can return in a better form someday.
Traceback (most recent call last):
  File "capnp/lib/capnp.pyx", line 1377, in capnp.lib.capnp._DynamicStructBuilder.__setattr__
  File "capnp/lib/capnp.pyx", line 1370, in capnp.lib.capnp._DynamicStructBuilder._set
  File "capnp/lib/capnp.pyx", line 829, in capnp.lib.capnp._setDynamicField
capnp.lib.capnp.KjException: Tried to set field: 'error' with a value of: '-0.14431941964088504' which is an unsupported type: '<class 'numpy.float64'>'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/data/openpilot/openpilot/system/manager/process.py", line 40, in launcher
    mod.main()
  File "/data/openpilot/selfdrive/controls/controlsd.py", line 852, in main
    controls.controlsd_thread()
  File "/data/openpilot/selfdrive/controls/controlsd.py", line 842, in controlsd_thread
    self.step()
  File "/data/openpilot/selfdrive/controls/controlsd.py", line 814, in step
    CC, lac_log = self.state_control(CS)
                  ^^^^^^^^^^^^^^^^^^^^^^
  File "/data/openpilot/selfdrive/controls/controlsd.py", line 587, in state_control
    actuators.steer, actuators.steeringAngleDeg, lac_log = self.LaC.update(CC.latActive, CS, self.VM, lp,
                                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/openpilot/openpilot/selfdrive/controls/lib/latcontrol_torque.py", line 71, in update
    pid_log.error = torque_from_setpoint - torque_from_measurement
    ^^^^^^^^^^^^^
  File "capnp/lib/capnp.pyx", line 1379, in capnp.lib.capnp._DynamicStructBuilder.__setattr__
  File "capnp/lib/capnp.pyx", line 267, in capnp.lib.capnp.KjException._to_python
AttributeError: 'NoneType' object has no attribute 'type'

Turns out RAM_HD was using it, as a positional arg, and we're not currently running CI on dashcam cars.
Choices:

Fix yaw-based curvature, and regain CI coverage by running on dashcam cars again
Check to see if RAM_HD really benefits from this. Yaw-based curvature doesn't seem to work that well, in its current form, but neither does the 1.0 degrees of RAM_HD steering angle deadzone.

Holding in Draft to get opinions.

This PR was closed because of a git history rewrite.
Please read https://github.com/commaai/openpilot/issues/33399 for what to do with your fork and your PRs.


Nested div onclick event

I have a overlay background element and dialog inside. The problem is that onclick event of overlay div is fired event if that div is under dialog. That cause me closing the dialog. Then I tried to solve that by addEventListener via JSInterop and use e.stopPropagation() but it fail another way. It stop all blazor onclick events inside of popup dialog. Blazor use document as the only point to attach event listeners. Should I use other way to stop propagation in blazor ?

There are many different related problems related to your report. When porting an admin theme like https://demo.pixelcave.com/codebase/db_classic.php, blazor will break almost the whole javascript functions. I guess the event Listener behavior should get more focus...


Page.getResourceTree doesn't return stylesheets

| Operating system	  	 	| Windows 10
| Node.js					| 10.16.3
| Chrome                         	|  86.0.4240.75
Is Chrome running in a container? NO
When i run Page.getResourceTree

The returned array of resources does not include stylesheets. Only javascript, images and fonts.
Im trying to get a detailed outline of the website structure, the same you would find when you look at "Sources" in devtools

I cannot reproduce this, if you can tell me a web site where this happens I can take a look.
Make sure that the page is loaded during the debug session, for example:
await Page.navigate({url: 'https://www.ansa.it'});
await Page.loadEventFired();
const tree = await Page.getResourceTree();

Try with this

I cannot reproduce this, if you can tell me a web site where this happens I can take a look.
Make sure that the page is loaded during the debug session, for example:
await Page.navigate({url: 'https://www.ansa.it'});
await Page.loadEventFired();
const tree = await Page.getResourceTree();

Try this one
https://nuruerotic.com

With the following I see style sheets, which is basically my previous suggestion.
(async () => {
    const CDP = require('chrome-remote-interface');
    const client = await CDP();
    const {Network, Page} = client;
    await Page.navigate({url: 'https://nuruerotic.com/'});

    // this page rarely finishes loading so use a timeout instead of await Page.loadEventFired()
    setTimeout(async () => {
        const {frameTree: {resources}} = await Page.getResourceTree();
        console.log(resources.filter((resource) => resource.type === 'Stylesheet'));
        client.close();
    }, 3000);
})();


Dependency update and add eslint

The test passed on windows, not sure if it's ok on linux, please help double-check.


Fix the typo

In the reference of #2753
convert from .tar or .tar.gz or .zip  to .tar or .tar.gz

If you give your branches meaningful names, it'll be easier to keep track of them. For example, this one could be 2753-import-typo or something similar to remind you what issue # it is associated with and what the topic is.
After you create the new branch, you might want to investigate the git cherry-pick command to copy one of your commits to it.

@chetan-v Also, if you are new to Git and still learning all the CLI commands, you might want to use a GUI to help you along as well.
Gitkraken can be used for free with open source, such as our OpenRefine repo.

Oh! I fix it very soon


"Gușoeni" , "Burdălești" , "Dealu Mare" , "Gușoianca" , "Măgureni" , "Spârleni" are listed in the drop-down menu

The villages are listed in the drop-down menu alongside its corresponding county and city, according to the law
Preconditions : the  website is up and runing. After every step delete the text you typed from the search bar.

Step 2
Write in the search bar "Burdălești"

Expected results
The location appears in the drop-down menu as "Sat Burdălești, VÂLCEA (Gușoeni)"

Step 3
Write in the search bar "Dealu Mare"

Expected results
The location appears in the drop-down menu as "Sat Dealu Mare, VÂLCEA (Gușoeni)"

Step 4
Write in the search bar "Gușoianca"

Expected results
The location appears in the drop-down menu as "Sat Gușoianca, VÂLCEA (Gușoeni)"

Step 5
Write in the search bar "Măgureni"

Expected results
The location appears in the drop-down menu as "Sat Măgureni, VÂLCEA (Gușoeni)"

Step 6
Write in the search bar "Spârleni"

Expected results
The location appears in the drop-down menu as "Sat Spârleni, VÂLCEA (Gușoeni)"


Update to youtube oembed endpoint breaks auto advance

Need to add new prep embed for youtube.
Todo to remind myself.

fixed with last commmit


Add new rpc 'subtensor_epoch'

Make an optional Bool argument with default=False called “incentive” in the epoch parameters that, if set to “True”, will return the incentive storage value as Vec<I32F32> instead of the emission tuples
cargo clippy and fmt

short text information


WIP DO NOT MERGE: Set default_api_level=API_HYBRID for protobuf-go v1.36.0

Open questions:

Does a new revision get automatically created for v1.36.0?
Should we delete the protoopaque files by wrapping protoc-gen-go and deleting them from the resulting CodeGeneratorResponse on the fly? I'd argue no, as while the build tag logic isn't our favorite, that's just our opinion, and we should match protoc-gen-go behavior unless there's a strong reason not to.

You could actually argue that we shouldn’t make this the default for remote plugins, but should for generated SDKs, so we may want to close this PR in the. end.

Yes, we'll get a revision bump and subsequent go get ... requests will generate hybrid (opaque+open) code.
I don't think we want to modify the response because there might be some users who explicitly want this. Also, we probably don't want to couple the generator output too closely with the implementation of Generated SDKs.
If we were to go down this route, we'd be better off applying a patch to exclude those files from being generated in the first place. We have some prior art for git-based patches and custom builds.
We're in a predicament of having to pick exactly one sane default. Although I think default_api_level=API_HYBRID is the least-worst option because it satisfies the most amount of use cases, including the new OPAQUE API, which was not previously possible without .proto changes (which we actively discourage).
Unless @pkwarren @stefanvanburen have any objections I think we should roll forward with this.

I wonder if we should also bump grpc/go to depend on the updated protocolbuffers/go version?


Create shared/.userskel folder to be copied to users' home

There will be a new shared/.userskel folder ('user skeleton').
The contents of this will be copied to any user's home folder on spawn of a server (but not overwriting any existing files).
.userskel is admin-writable but only readable by other users.
This PR is a solution, at least for the inspiration behind, #391

If we like this feature it needs some documentation.


Fixes #45, Fixes #46, Fixes #47

Fixes #45.
Fixes #46.
Fixes #47.
Fixes checkstyle configuration, and actually runs checkstyle during the build.

Signed-off-by: sappenin<EMAIL_ADDRESS>

Codecov Report

Merging #49 into master will increase coverage by 0.08%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master      #49      +/-   ##
============================================
+ Coverage     74.55%   74.64%   +0.08%
- Complexity      430      437       +7
============================================
  Files            92       92
  Lines          2771     2780       +9
  Branches        300      301       +1
============================================
+ Hits           2066     2075       +9
  Misses          530      530
  Partials        175      175

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/org/interledger/psk/PskNonceHeader.java
80.95% <ø> (ø)
5 <0> (ø)
:arrow_down:

.../java/org/interledger/psk/PskEncryptionHeader.java
89.18% <ø> (ø)
12 <0> (ø)
:arrow_down:

...n/java/org/interledger/ilp/InterledgerPayment.java
75% <ø> (ø)
1 <0> (ø)
:arrow_down:

...main/java/org/interledger/codecs/CodecContext.java
87.17% <ø> (ø)
21 <0> (ø)
:arrow_down:

.../main/java/org/interledger/InterledgerAddress.java
96.82% <100%> (+0.52%)
20 <7> (+7)
:arrow_up:

Continue to review full report at Codecov.

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


Anna morris

Sprint challenge.

What Looks Great

All MVP accomplished
Excellent semantic HTML markups
CSS naming conventions make sense
Great frequency on your commits

Requested Improvements
I would simply look at applying the CSS stylings to the boxes by referencing them using one class versus by class and id.
Rating: {1-3}
2


Cant connect to steam even client is connected (same network)

Describe the bug
Cant connect to steam even client is connected
I dont see any blocked traffic on the firewall or some sort of.
Additional Details

Platform you are running SteamPrefill on:  Linux (Debian 12)
Region : Germany

Screenshots

NEVERMIND could find the issue now


How to join .NET Platform organization

Is it possible to become a member of  .NET Platform  for guys not from Microsoft?
If yes, are there any requirements for that? I know that I should contribute a lot, but how much? Let's  say I have 20+ commits in different repositories from .NET Platform organization, then should I create some request or wait until someone will notice me?
I know how to become a member of .NET Foundation, but I'm interested in  .NET Platform.
Thank you in advance and sorry if this is not the place to ask such questions.

@terrajobst @richlander do you have an answer for this? Do you know if external people can join the .NET Platform group?

It would be great to know, thanks

In general, we add people working directly on .NET Foundation projects to the dotnet org. In the case of the .NET Core project and associated repos, we only add Microsoft people. We may change that in future, but that's our current approach. Here is our latest updated on that: https://github.com/dotnet/announcements/issues/144.
On topic of committer permissions, we have no plan to offer that to folks outside of the .NET team. We get questions from time to time on our governance strategy for committer access, and most big organizations (commercial and government) appreciate this approach. It isn't the most OSS friendly approach one could imagine, but it works.

@PeterPreter , did @richlander's response answer your question?

yes, thanks


Correct nul character patch

The removal was off by one, i.e. one nul character remained

Checklist

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

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


feat(trie): Add map sum pairs.

Coverage remained the same at 100.0% when pulling 06fcfadc86b3ebc6a27f3e92299ade10e95427a6 on map-sum-pairs into dad591fcdefa07efb547cda236d3903e02e91948 on master.


Update cloudformation_compatibility based on Release 1.4.0

docs/cloudformation_compatibility.rst was out of date based on Release 1.4.0. This PR is to update those docs to include the recent changes.

We need to add all the new API properties to the list. Can you do that?

Ahhh!!! I forgot about those! How did I forget about those!
Will update :)


Getting error: Error: Cannot find module 'react-test-renderer/shallow'

After upgrading to v4.1.0, I am getting the above error. Does anyone know what might be going on here? I am running my tests using mocha-webpack, and it kind of looks as though this error is arising as mocha-webpack tries to build the testing bundles...

I seem to have solved this temporarily by installing the react-test-render explicitly: npm i -D react-test-renderer.

react-test-renderer is now a peerDep of unexpected-react from version 5.


Non-regex nickname entry allows leading/trailing whitespace in username

Checklist

[X] I'm reporting a problem with Chatterino
[X] I've verified that I'm running the most recent nightly build or stable release
[X] I've looked for my problem on the wiki
[X] I've searched the issues and pull requests for similar looking reports

Describe your issue
When editing a nickname, whitespace can be prepended/appended to the username field which is invalid as part of a Twitch/IRC username. This can be confusing to users that paste usernames with trailing spaces as nothing indicates that the whitespace exists outside of the edit mode.
Screenshots
Username with whitespace (nickname does not work):

OS and Chatterino Version
Chatterino 2.3.5 (commit 965b06677) built with Qt 5.15.5 Running on Arch Linux, kernel: 5.18.14-zen1-1-zen

My suggested fix for this is to strip leading/trailing whitespace on settings save. I see no impact implementing this as no username on Twitch/IRC should start or end with a space.

Fixed by #3946


Possibly trivial question(s) about spawning tasks

Is there any particular "cost" to spawning tasks on the fly? As in, should all tasks be spawned ahead-of-time, and then left in an awaiting state on a signal/channel?
Or, is it a valid pattern to spawn-on-demand?
I guess the thing I don't fully understand is whether the task macro + spawner do any sort of embedded "magic" that I need to be on the lookout for - or whether it's just as straight-forward as I think it might be, which is basically just putting a statically allocated task onto the queue of tasks the executor needs to keep an eye out for.
That was the impression the docs give me (https://embassy.dev/book/dev/runtime.html). I read it as #[embassy_executor::main] is just a regular old task that happens to be first + comes with a spawner.
But what I was less clear on was whether it's fair game to use the spawner from the non-main tasks, to spawn new tasks?
For example: I have a BLE scanning task, and when I find a specific device, can I spawn that off into a separate connection task that lives for the duration of the connection - and then ... dies? Gets recycled? Or do I need to ensure that connection task is long-lived so that I can safely re-use it?
Another example, I have an ANT+ scanning task, and then I might have up to 3 ANT+ devices connected at once - so I was going to create a task with pool_size=3, but can I spawn and let them finish, and then re-spawn? Or should I keep a long-lived loop and handle them with a channel?
This ticket makes me think that it's on the side of "just spawn as needed".
https://github.com/embassy-rs/embassy/issues/19

's just as straight-forward as I think it might be, which is basically just putting a statically allocated task onto the queue of tasks the executor needs to keep an eye out for.

yes, it's exactly that.

But what I was less clear on was whether it's fair game to use the spawner from the non-main tasks, to spawn new tasks?

yes, that's totally fine.

For example: I have a BLE scanning task, and when I find a specific device, can I spawn that off into a separate connection task that lives for the duration of the connection - and then ... dies? Gets recycled? Or do I need to ensure that connection task is long-lived so that I can safely re-use it?
Another example, I have an ANT+ scanning task, and then I might have up to 3 ANT+ devices connected at once - so I was going to create a task with pool_size=3, but can I spawn and let them finish, and then re-spawn? Or should I keep a long-lived loop and handle them with a channel?

Yes, that's exactly how I'm handling BLE connections. On receive connection, spawn a task. When the connection dies, just let the task exit. When a task exits, it's marked as free in the pool, so next spawns can reuse it.

Awesome thanks! Great to know it functionally works more or less as I thought it does :)

When a task exits, it's marked as free in the pool, so next spawns can reuse it.

This was the piece I was trying to dig through the code to find. I assumed it must have been how everything worked, but hadn't yet ran into the code that does it.


Propagate fuzzing options to the OSS-Fuzz package, through the creation of the options file.

Is there more that needs to be done here now that #148 has been merged? .options files are not exposed via the *_fuzz_test macros yet, but this also doesn't seem to be needed for C++ fuzz tests since max_len should rather be implemented in the fuzz test directly.

You're right, I think this is now addressed. Thanks!


physical way to keep camera correct distance to bed

from the info determined in #7, design/print physical device to distance camera from the bed.
keep .stl in the public github repository (/hardware directory). make sure to commit as soon as you make changes

decided on physical distance for camera height ... 3inches


Selecting the same value a second time does not fire a select event.

Prerequisites

[ ] I have searched for similar issues in both open and closed tickets and cannot find a duplicate
[ ] The issue still exists against the latest master branch of Select2
[ ] This is not a usage question (Those should be directed to the community)
[ ] I have attempted to find the simplest possible steps to reproduce the issue
[ ] I have included a failing test as a pull request (Optional)

Steps to reproduce the issue

Create a select2 element with something to select
Select something.
Select that same thing again

Expected behavior and actual behavior
The second time I select a value the select event is not being fired.
I was expecting to get an event. I guess that this should be the difference between the change and the select event. the change event should not be fired since nothing changed, but I still selected something so I need an event.
Environment
Browsers

[x] Google Chrome
[x] Mozilla Firefox
[?] Internet Explorer
[?] Safari

Operating System

[?] Windows
[x] Mac OS X
[?] Linux
[x] Mobile (iOS)

Libraries

jQuery version: 1.12
Select2 version: 4.0.3

Isolating the problem

[x] The bug happens consistently across all tested browsers

This appears to be a duplicate of #4934.  Please search the open issues carefully before opening a new issue!


Config.php requires "use Aws\Credentials\CredentialProvider"

Hi,
I have an infrastructure with moodle installed as described in aws-refarcg-moodle.
Since August 4th I have a 500 HTTP server error and I found the following error.
ERROR
#######################################################################
Fatal errorPHP Fatal error:  Uncaught Aws\Exception\CredentialsException: Error retrieving credentials from the instance profile metadata service. (cURL error 6: Could not resolve host: https (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)) in phar:///var/www/moodle/html/lib/aws.phar/Aws/Credentials/InstanceProfileProvider.php:272
Stack trace:
#0 phar:///var/www/moodle/html/lib/aws.phar/Aws/Credentials/InstanceProfileProvider.php(159): Aws\Credentials\InstanceProfileProvider->handleRetryableException(Object(GuzzleHttp\Exception\ConnectException), Array, 'Error retrievin...')
#1 [internal function]: Aws\Credentials\InstanceProfileProvider->Aws\Credentials\{closure}()
#2 phar:///var/www/moodle/html/lib/aws.phar/GuzzleHttp/Promise/Coroutine.php(160): Generator->throw(Object(GuzzleHttp\Exception\ConnectException))
#3 phar:///var/www/moodle/html/lib/aws.phar/GuzzleHttp/Promise/Promise.php(204): GuzzleHttp\Promise\Coroutine->_handleFailure(Object(GuzzleHttp\Exception\ConnectException))
#4 phar:///var/www/moodle/html/lib/aws.phar/Guzzl in phar:///var/www/moodle/html/lib/aws.phar/Aws/Credentials/InstanceProfileProvider.php on line 272
#######################################################################
To resolve it I have to change the initial part of config.php file from:
              require 'lib/aws.phar';
              use Aws\\SecretsManager\\SecretsManagerClient;
              use Aws\\Exception\\AwsException;
              use Aws\\Iam\\IamClient;

              $client = new SecretsManagerClient([
                  'version' => '2017-10-17',
                  'region' => ''
              ]);

to:
              require 'lib/aws.phar';
              use Aws\\SecretsManager\\SecretsManagerClient;
              use Aws\\Exception\\AwsException;
              use Aws\\Iam\\IamClient;
              use Aws\\Credentials\\CredentialProvider;

              $provider = CredentialProvider::defaultProvider();

              $client = new SecretsManagerClient([
                  'version' => '2017-10-17',
                  'region' => '',
                  'credentials' => $provider
              ]);

Basically seems that a breaking change has been introduced in aws.phar.
Please can you help me to understand  how to prevent that from happening?
Is it available an url point for a specific v3 revision ?
What I did is correct ?
You too have the same anomaly as me?
Thanks

Can you confirm that you have an IAM profile assigned to the instance and the metadata service is enabled?  It should look something like this.
% aws ec2 describe-instances
{
    "Reservations": [
        {
            "Groups": [],
            "Instances": [
                {
                    ...
                    "IamInstanceProfile": {
                        "Arn": "arn:aws:iam::XXXXXXXXXXXX:instance-profile/XXXXXX",
                        "Id": "XXXXXXXXXXXXX"
                    },
                    ...
                    "MetadataOptions": {
                        "State": "applied",
                        "HttpTokens": "optional",
                        "HttpPutResponseHopLimit": 1,
                        "HttpEndpoint": "enabled"
                    },
                    ...
                }
            ],
            ...
        }
    ]
}

Yes. I can confirm  it.
IAM profile is assigned to instance and the metadata service is enabled.

Is this issue still valid? If so, please reopen. Thanks!


Overhaul CLI reference

What kind of changes does this PR include?

New or updated content

Description
I noticed https://github.com/withastro/astro/issues/4870 this morning and it triggered me to look through our CLI reference.
I’ve tried to improve it by

adding an introductory section that explains how to use the CLI more generally, including passing flags
correcting some errors (removing mention of --reload which doesn’t seem to exist anymore, moving --drafts up to the astro build section as it only works there)
breaking up “global” flags into “common flags” (to be combined with commands) and “global flags” (standalone, e.g. astro --version)
adding links where relevant
adding a warning not to use dev in production
explaining why --host can be useful

I’ve also deleted an old Spanish translation of the CLI reference as we now have a newer version.

Going to merge on the advice of @Jutanium. We still need to figure out what to do with the --verbose CLI flag, but the rest is an improvement so we can tackle that separately.


Possible release !!

Hi mcollina, My tech stack is using mongodb and I was looking for adding persistence for QoS 2 in aedes. Do you have ny possible release date for this project? Please let me know. Thanks- Vikram

I'm closing this. It's done when it's done, or ask for "how can I help you?", and I can lay out a series of task for you to help me out.


Resize added image

Is your feature request related to a problem? Please describe.
I want to resize the added image, added by the draw button.
I am not sure if there is any other option available to resize it so I am using dev tools to add custom CSS.
Describe the solution you'd like
If there could be any slider for having setting width and height of the image added. 😅
Describe alternatives you've considered
An alternative method is to just add custom CSS and position it properly.
Additional context

Hi Aman, yes there isn't any other option available yet but would definitely love to have a way to do this.
Closing this issue since we have issue open for this in #34.
Thank you for reporting :D


Fix PowerShell version in features.md

Fix PowerShell version.

@alexandair : Thanks for your contribution! The author, @jluk, has been notified to review your proposed change.

#sign-off


Feature request: Pagination

It would be great if there could be a pagination feature while reading a collection.
P.S. I would love to contribute but since I'm a newbie here, help me understand how to contribute to this repo. Thanks!

You can already paginate with limit and offset:
    sdk.items('posts').readMany(query: Query(limit: 5, offset: 10));

You can create PR to add page property to Query class, since it looks like Directus API supports it: docs.
That way we could use
    sdk.items('posts').readMany(query: Query(limit: 5, page: 2));

Query class is located in lib/src/data_classes/query.dart

You can already paginate with limit and offset:

    sdk.items('posts').readMany(query: Query(limit: 5, offset: 10));

You can create PR to add page property to Query class, since it looks like Directus API supports it: docs.
That way we could use

    sdk.items('posts').readMany(query: Query(limit: 5, page: 2));

Query class is located in lib/src/data_classes/query.dart

😍
Thanks!


Evaluation on COCO-test-dev

Hi,
I am trying to test the yolo_nano model with test2017 set. I have already downloaded the test2017 dataset locally. And I tried the exact command mentioned in the readme file, that is
python eval.py -d coco-test \                --cuda \                -m yolov_nano \                --weight path/to/weight \                --img_size 640 \                 --root path/to/dataset/
And the readme file says, this generates the .json file. However, unfortunately I end up with the error FileNotFoundError: [Errno 2] No such file or directory: '/data/COCO/annotations/image_info_test-dev2017.json'. This is understandable because there is no such file.
@yjh0410 Did I miss something here? How do I test the model on test dataset?
Thanks!

@kulkarnikeerti
You can download it from here:
ttps://github.com/yjh0410/PyTorch_YOLO-Family/releases/download/yolo-weight/image_info_test-dev2017.json
https://github.com/yjh0410/PyTorch_YOLO-Family/releases/download/yolo-weight/image_info_test-dev2017.json
You might also need this, if you want to evaluate the model on COCO2017 test(not test-dev):
https://github.com/yjh0410/PyTorch_YOLO-Family/releases/download/yolo-weight/image_info_test2017.json

@kulkarnikeerti
You can download it from here:
https://github.com/yjh0410/PyTorch_YOLO-Family/releases/download/yolo-weight/image_info_test-dev2017.json
You might also need this, if you want to evaluate the model on COCO2017 test(not test-dev):
https://github.com/yjh0410/PyTorch_YOLO-Family/releases/download/yolo-weight/image_info_test2017.json

@yjh0410 Thanks for the links. But I guess they are broken. I don't find anything there. I don't see any releases folder in the repo. Below is the result with the link.

@kulkarnikeerti
Please try to download from here:
github
gitjub

@yjh0410 Thank you very much.
Just one last clarification: the results of YOLO_Nano in the table contains three different rows. YOLO-Nano-320, YOLO-Nano-416, YOLO-Nano-512.
what does these numbers 320, 416, 512 in the name indicate? Are these the input image size?

@kulkarnikeerti
Yes. For example, 320 means that the input image is resized to shape 320x320.

Okay. Thanks a lot again @yjh0410


Added German Translation

I added all missing translations for German. To make it easier to find missing messages and work with machine translation, I used the tooling of inlang by adding the inlang.config.js. I am also participating in this project.
Changes

added inlang.config.js
copied id text in english files
added German translation

Questions
I am interested in why you are using the English translation as id.
If you change the English copy, every other language file must be updated and multiple sentences end up being a big key. Also supporting tools expect a full reference language to support linting or machine translation.
As a contributor I couldn't find much in the documentation about the translation process and were to begin with. Would you like me to help you with that?
There are plenty of missing messages (1.827 of 6.105) and by adding the inlang.config.js developers can use the IDE extension and CLI in code or a web editor to find easily find these and translate them. They just need to be referenced in the documentation or added to the .vscode recommendations.
See: https://inlang.com/editor/github.com/NiklasBuchfink/Ghost

Hi @NiklasBuchfink - this PR has quite a few conflicts because we've had a lot of updates to the German translations on main. Would you be able to rebase? Then I'll open the PR to merge 🙂

Hi @daniellockyer, I know this PR is quite old, but I use it to contact you. I saw you managing a lot of the translation-related issues for Ghost. Is the Ghost community interested in using inlang to make it easier to work with translations in code and manage contributions? I'm working on this project and you can benefit from our tools.


Some links have empty names for assistive technologies and are therefore problematic for accessibility and also search engines

I love Rive and just wanted to make it even better - and especially more accessible. Some links have accessible names but some don't. This is a huge problem for many, especially blind screen-reader users and also search engines.
Example on https://rive.app - first, main call to action button "Get Started" that has the rocket animation on mouse hover.
When I check the generated HTML I get:

<canvas style="vertical-align: top; width: 500px; height: 500px;" width="500" height="500"></canvas>

The semantic part that is important for accessibility tree is the anchor part:

As you can see - it's empty. Therefore link text won't be announced to screen-readers, for example.
And search engines will also have it difficult if not impossible to extract link text from <canvas>.
Solution can be to insert link text and make it visually hidden but available to screen-readers.
This can be achieved with some CSS:

Get Started

with following CSS:
.sr-only {
  border: 0 !important;
  clip: rect(1px, 1px, 1px, 1px) !important;
  -webkit-clip-path: inset(50%) !important;
  clip-path: inset(50%) !important;
  height: 1px !important;
  overflow: hidden !important;
  margin: -1px !important;
  padding: 0 !important;
  position: absolute !important;
  width: 1px !important;
  white-space: nowrap !important;
}

(CSS source: https://kittygiraudel.com/snippets/sr-only-class/)
With this fix link text would be invisible but at the same time available for both assistive technologies and search engines.
This should be fixed not only for React but for all web technologies that generate HTML.
Also - remove the tabindex="0" on
.

@avivian - thanks for labeling, but I think this should be labelled as a bug, not as a feature-request.
We need to fix the missing link text, we don't need a new feature for it...

Hey @BogdanCerovac
Firstly, thanks for raising this issue. The specific issue you raised about link text is an issue with the https://rive.app website, not the react runtime. Any fix we do will, for now, be outside the react runtime.
However I think it would be cool for anyone creating a rive animation to add some text that can be exposed to screen readers. The exact implementation of this we'll need to discuss with the team, but it will likely be a new feature required in our runtimes and perhaps our editor. Hence the tag!


Question: How to add support of new macros

I using this library in following way:
import { parse } from "@unified-latex/unified-latex-util-parse";
import { convertToHtml } from "@unified-latex/unified-latex-to-hast";

const ast = parse(content ?? "");
const html = convertToHtml(ast);

I want to add support for custom implementation for macro:
<<Some text>> % this should be generated like «Some text»
% It looks like this is a common feature and should be added to this library.

\includegraphics{url} % this should be generated like
% It looks like it's a custom implementation, at least for html generation.

How can I add this support? It seems I should add a macro to parse and an html generator to convertToHtml, but the current interface doesn't allow this.

Yes, it seems that convertToHtml doesn't allow custom extensions right now. Here's a possible workaround:
Using htmlLike from unified-latex-util-html-like you can create macros that will be converted to HTML tags. E.g., if you insert the node htmlLike({tag: "div", attributes: {foo: "bar"}}) it will create a valid Ast.Node that when converted to HTML will be

.
Parse the your code. Then use the replaceNode function from unified-latex-util-replace  to replace all includegraphics with the appropriate tags. Then continue converting as normal.
If you need to add your own custom macro parsing, you can pass a list of macros if you create your own unified parser:
import { unified } from "unified";
import { unifiedLatexFromString } from "./plugin-from-string";

const options = {macros: {includegraphics: { signature: "m",  processContent: myCustomFunction}}}
const parser = unified().use([unifiedLatexFromString, options]);

It seems that includegraphics not being processed is a missing feature. A PR to add that conversion to the library would be welcome :-). It would also be nice to add a hook for the html processor itself so custom processing could be added just like custom macros can be specified.

I tried this approach, and this is working as expected:
const parser = unified().use(unifiedLatexFromString, {
    macros: {
        def: { signature: "m m" },
    },
});

type Context = {
    imageBaseUrl?: string;
};

const macros: Record<string, (node: Macro, context: Context) => any> = {
    "def": () => null,
    "includegraphics": (node: Macro, context: Context) => {
        if (!node.args) {
            return null;
        }
        const args = pgfkeysArgToObject(node.args[1]);
        let style = '';
        if (args["width"] && args["width"].length) {
            style += `width:${printRaw(args["width"][0])};`;
        }
        if (args["height"] && args["height"].length) {
            style += `height:${printRaw(args["height"][0])};`;
        }
        const imageName = printRaw(node.args[3].content);
        const imageUrl = (context.imageBaseUrl ?? "") + imageName;
        return htmlLike({ tag: "img", attributes: { src: imageUrl, style: style } });
    },
};

// External values:
//     imageBaseUrl
//     content
const ast = parser.parse(content ?? "");
const context = {
    imageBaseUrl: imageBaseUrl,
};
replaceNode(ast, (node) => {
    if (node.type !== "macro") {
        return undefined;
    }
    const macro = macros[node.content];
    if (!macro) {
        return undefined;
    }
    return macro(node, context);
});
const html = convertToHtml(ast);


Mega Backpack's extra slots aren't working properly

I've noticed that with the A21 version of Mega Backpack, if your vanilla inventory slots are full, you can't quick loot with R (default keybind) or shift click items from storage/loot into your inventory. You have to manually drag items into the new slots.

UPDATE: After closing the game and reopening/loading my save file, all the items that were in the additional inventory slots were gone.

I could never get it to work either and sounds like Im glad I deleted it went with the other with 96 slots lol

I haven't noticed this myself, but thanks for report it... I'll look into it. Are you using any other mods which might modify the UI?

UPDATE: After closing the game and reopening/loading my save file, all the items that were in the additional inventory slots were gone.

if you uninstall the mod, you won't be able to see any items that were in those extra slots, but they're not gone... you just can't see them. Re-installing the mod should recover them. This will be true of any mod the modifies your backpack rows and columns.

I'm sorry, but I'm unable to replicate this issue locally. I've run several tests with only megabackpack installed and with AiO, and everything works as expected.
Please make sure you have the latest version of the mod installed which is, at the time of this writing, v21.0.1


Update ViMbAdmin 3.0.12 to 3.0.15 - security update

update ViMbAdmin 3.0.12 to 3.0.15
https://github.com/opensolutions/ViMbAdmin/releases/tag/3.0.15

We have dropped support for webmail in v4. Sorry.


Open VPN script - trouble with client certs

I used the Open VPN userdata script when building my droplet. Presumably I now need to continue at step 3 of the tutorial at https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-14-04
But when I try to execute the command './build-key client1', it gives me the following error:
Please edit the vars script to reflect your configuration,
then source it with "source ./vars".
Next, to start with a fresh PKI configuration and to delete any
previous certificates and keys, run "./clean-all".
Finally, you can run this tool (pkitool) to build certificates/keys.

Hi!
The script actually takes care of that part too. See:
https://github.com/digitalocean/do_user_scripts/blob/master/Ubuntu-14.04/network/open-vpn.yml#L44
A bundled client profile (client.ovpn) as well as a CA certificate (ca.crt), user certificate (client1.key), and user private key (client1.crt) are all generated and can be found in the /root directory. You should be able to jump right to step 5 of that tutorial.

I tried that. I am getting TLS errors, and I see some of the comments below the article reflect this as well. Is a TLS issue a case of the client cert not matching the server cert?

On line 56 there is an error, it will add the certificate in both text and base64.
It's only the part between -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- (i.e base64 certificate) which should be added to the client.ovpn file.
I guess that's why people gets TLS errors.
My suggestion is to replace cat /etc/openvpn/easy-rsa/keys/client1.crt with openssl x509 -in /etc/openvpn/easy-rsa/keys/client1.crt -outform PEM

Thanks @ao95 I've merged your change. If anyone else is still seeing issues, please feel free to open a new issue.