Ability to easily download the init package

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I'm using Zarf as part of an automated workflow. As part of the workflow, I need to download the init package.
Describe the solution you'd like

Given a state
When an action is taken
Then something happens

Given I have Zarf downloaded, but not the init package
When I run zarf tools download-init-package (or some other equivalent command)
Then the correct init package is downloaded in the same way as if I had run zarf init interactively and said "yes" when asked if I want to download the init package.

Describe alternatives you've considered
(optional) A clear and concise description of any alternative solutions or features you've considered.
A gross script that uses curl would do it, but this would be much nicer.
Additional context
Add any other context or screenshots about the feature request here.

Closing as dupe of https://github.com/defenseunicorns/zarf/issues/1654


iOS: Add bottom and top padding to images

Right now there is no padding, so two pictures, one after another look like they are just one picture.

Is there a good test feed/article for this one? Otherwise I'll whip up a sample file for it.

https://blog.thenounproject.com/tutorial-diy-coloring-book-noun-project-f5da884e39a5?source=rss----e1758884c61e---4
This is the third article from the end, dated Dec 9. About halfway through you should see a couple images butted up against each other.

Looks like it might be partly to do with their being wrapped in <figure>s. Adding a margin to those is probably the thing to do.


style: remove useless methods in the example

Codecov Report

Merging #347 (9cc4fb5) into dev (f717257) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #347   +/-   ##
=======================================
  Coverage   96.35%   96.35%
=======================================
  Files         209      209
  Lines        4882     4882
  Branches     1042     1042
=======================================
  Hits         4704     4704
  Misses        178      178

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 f717257...9cc4fb5. Read the comment docs.


Ethereum updates (IOV-Core patch 0.12.3)

Closes #834
Closes #833
Also adds a nonces/ folder for each package to ensure releases are made for every package

updated, +3 commits


Beta Bug: media_folder_relative also setting relative path when uploading images

Describe the bug
I'm referring to a Gatsby issue Issue 4753, where you announced relative image paths in the beta. This works great for loading files from the static folder that already exist, but uploading a new file via the admin also saves them as relative paths to the .md file, making it impossible to find it later when loading (basically ignoring the media_folder setting).
To Reproduce

Install the Beta "^2.9.8-beta.3"
Set the config
media_folder_relative: true media_folder: "static/uploads"
Upload an image via the netlify admin area
Check the .md file image path

Expected behavior
Uploads should be saved as image: /uploads/logo.png, but instead they're saved as ../../../uploads/logo (number of directory changes depending on where the page lives).
Applicable Versions:

Netlify CMS version: "^2.9.8-beta.3"
Git provider: Gitlab
OS: MacOs

CMS configuration
`
backend:
name: gitlab
repo: ********
auth_type: implicit # Required for implicit grant
app_id: *********
api_root: ********
base_url: ********
auth_endpoint: oauth/authorize
media_folder_relative: true
media_folder: "static/uploads"
public_folder: "/uploads"
collections:

name: navbar
label: Navbar
folder: src/markdown/widgets/navbar
create: true
fields:

{label: "Template Key", name: "templateKey", widget: "hidden", default: "navbar-widget"}
{label: "Title", name: "title", widget: "string", hint: "Please choose a unique name for the Navbar. The grey background will just be visible here, the regular navbar will be transparent"}
{label: Logo, name: logo, widget: object, fields: [{label: Image, name: image, widget: image}, {label: "Image Alt", name: imageAlt, widget: image}, {label: Path, name: path, widget: string}, {label: Alt Text, name: altText, widget: string}]}
{label: Tabs, name: tabs, widget: list, fields: [{label: Label, name: label, widget: string}, {label: Path, name: path, widget: string}, {label: Offset, name: offset, widget: string}]}
{label: "Call to Action", name: cta, widget: object, fields: [{label: Text, name: text, widget: string}, {label: Path, name: path, widget: string}]}
`

This is what that functionality is supposed to do, write a relative path to the image from the entry. However, I'm just realizing that it's calculating the relative path based on the entry location in source rather than the entry location on the published site 🤦♂
@s0 this is based on a quick glance, let me know if I'm missing something. If not we may need to revert this puppy.

I haven't tested this, however from briefly reading the issue and your comment, it is supposed to calculate the relative path based on the source location, and not the published site. The idea is that you only use media_folder_relative: true when using a pre-processor such as gatsby. Solving issues such as https://github.com/gatsbyjs/gatsby/issues/4753

If I'm following everyone correctly, it sounds like Netlify CMS needs to be aware of two types of relative paths at once when using this flag. One relative to production to enable display in the admin (sourced from the repo) and one relative to source so Gatsby can do its thing.
To elaborate: Netlify CMS needs the original, unaltered relative path from the entry location of the published site (the one it typically outputs already) to source images from the repo correctly so that it can display images in the admin.
In a Gatsby build, that would be /static/[media folder name here]/, where the root folder is the public folder. However, Gatsby needs the relative path to the image from the markdown file in source to flag the frontmatter field on the node as matching an existing file node, which subsequently adds and populates childImageSharp fields for that frontmatter field in the schema.
If that's correct, it's imperative that anyone who uses this flag with Gatsby chooses the static folder as their media folder in the CMS config to facilitate previews. Regardless, it may not matter, because this still adds additional challenges for previews, because it means the shape of the data used in the previews will never match the shape of the data used in production components.

@s0 ah, right, that's it. As a matter of fact you're all correct lol. This is a complicated issue, which is why we hadn't taken it on just yet, really needs to be thought through on all sides. I'm certain that there are ways to pull this off though. Good breakdown @hu0p, we need both a relative source path and a relative production path. Could be relative to root for the production path as mentioned by @Jan17392.

Ah yes, I forgot that previews don't work for this, and weren't fixed in my original PR, I mention it at the end of the description here: https://github.com/netlify/netlify-cms/pull/2394.
Rather than calculate the published path for an image, I feel it would make more sense to embed the image directly from the backend (e.g. GitHub) like is done with the gallery picker (IIRC), rather than try and resolve the published location for the image.
This is slightly more robust, and allows for e.g. staging environments (master publishes to staging and is checked there before publishing a blog live), where the image may not yet be publicly accessible even if it's in git.

I also have a somewhat alterior motive for doing it this way, which is to get preview images for https://github.com/netlify/netlify-cms/pull/2397 working (where an image used in a post may not even be in the default branch at all yet).

In any case, if calculating the (site-relative) production path is preferable for everyone else, it should be fairly easy to work that out from the existing configuration options. We can work that out fairly easy:

Use the Path of the entry to work out the path of the image in the repo.
Use media_folder to work out the path of the image relative to the media folder (will usually just be the filename, if picked from the gallery)
Use public_folder to work out the production path.

Perhaps this is an over-simplification/misunderstanding, but couldn't the public_folder setting be left as is in frontmatter/markdown in certain scenarios? Particularly when using ~/ in conjunction with webpack. To illustrate the desired effect:
# Settings
media_folder: "assets/img"
public_folder: "~/assets/img"

# Result in yml/json/frontmatter
{ image: "~/assets/img/hello.jpg"}

This can then be happily used in nuxt/gatsby/whatever as a psuedo-relative path, while the admin interface should still be okay finding assets since the paths aren't actually relative.

Sorry to jump in late into this discussion, but there might be another solution.
I'm using this Gatsby plugin to make sure the CMS paths play nice with Gatsby.
I can confirm I'm getting optimized Gatsby images just by adding the plugin, which I believe was the point of the original issue in the Gatsby repo.

Hi, do we have a proper fix for this? :)

As a part of this https://github.com/netlify/netlify-cms/pull/2958/ image previews will always be taken directly from the repo and not the published site.
media_folder and the path of the entry will be used to figure out where to save the image in the repository, while public_folder will be used to populate the yml/json/frontmatter to be used later by site generators.
Will work only for editorial workflow at the moment, but this https://github.com/netlify/netlify-cms/issues/568 is next on our agenda.

Closing as media_folder_relative was removed in favour of https://www.netlifycms.org/docs/beta-features/#folder-collections-media-and-public-folder


Fix ISSUE 798: password printed to STDOUT when running initdb, resetdb, upgradedb

This fixes ISSUE-#798 by printing the sqlalchemy engine.url object rather then the connection string

Thank you sir!


feature: Add a Xamarin.Events.XamEssentials package

Add a events package with just updates for the XamEssentials package.
Fixes #1574

That's what ="x.x.x" means. It's a minimum range

https://docs.microsoft.com/en-us/nuget/reference/package-versioning#version-ranges-and-wildcards


Mahimahi experiment consuming too much time.

Hello, Hongzimao,
I'm trying to reproduce results(Figure 7,8,9,10) in your "Pensieve" paper and I met some problems.
According to my estimate, it will take about 13days assuming that we use one server for mahimahi experiment.

320 seconds run time for each simulation, pensieve/run_exp/run_videos.py
455 trace files from your dropbox/cooked_traces
8 algorithms (BB, RB, FIXED, FESTIVE, BOLA, fast mpc, robust_mpc, rl(pensieve rl))

So total 3204558 sec = 13days
Can you give me advice on how you proceeded experiment in this part to reduce total consumed time.
I thought about proceeding experiment pararelly in single machine. But I'm worried about bandwidth, and have no clue on how many experiments I can hold with single machine.
Thank you

Reply from Hongzimao
We ran experiments over multiple machines. I don’t remember the exact setting, but either of the following—(1) span out the traces, e.g., server 1 runs trace id 1-100 for all schemes; server 2 runs trace id 101-200 for all schemes; etc. (2) span out the schemes, e.g., server 1 runs RL for all traces; server 2 runs MDP for all traces; etc.
Thanks,
Hongzi


Prevent endless rekey and tunnel update cycle

Task/Issue URL: https://app.asana.com/0/1207603085593419/1207806947583090/f
iOS PR: https://github.com/duckduckgo/iOS/pull/3091
macOS PR: https://github.com/duckduckgo/macos-browser/pull/2987
Description
Prevents the following endless loop of calls updateTunnel > rekey > updateTunnel > rekey.
This adds noise to our metrics and is unnecessary.
Testing
See platform-specific PRs for testing instructions.
Definition of Done:

[ ] Does this PR satisfy our Definition of Done?

Internal references:
Pull Request Review Checklist
Software Engineering Expectations
Technical Design Template
Pull Request Documentation

I'll merge this tomorrow, to allow the internal testing week.


Create A Logo For The Project

Create a logo for the project with the same color scheme as the banner on the README.md
It should say THEMESWITCHER
You can use Canva or whatever you like
Fork and put the logo in the root folder with the filename logo
This is no-code. You shouldn't put the logo in the code.
Have fun!

Hi @omicreativedev  ,
Is it possible to assign this issue to me? I believe I can help in addressing the problem and working towards a solution.
Looking forward to your response.
Best regards,
Ezhill Ragesh

@ezhillragesh You are assigned. Have fun.


Running the Action script locally using nektos/act fails

Hi @julienloizelet,
First, I would like to thank you for creating and sharing the very useful GitHub Action.
I have been trying to test it locally using https://github.com/nektos/act.
The process runs fine until a certain point, and then it fails.
Following is the relevant output.
Do you know what's causing it and how it could be resolved?
Much appreciate it!
Itay
....
| Created a new local CA 💥
| The local CA is now installed in the system trust store! ⚡
|
| Could not connect to a docker provider. Please start or install a docker provider.
| For install help go to: https://ddev.readthedocs.io/en/latest/users/install/
[Coding standards/Static test suite]   ❌  Failure - Main Install DDEV
[Coding standards/Static test suite] exitcode '1': failure
[Coding standards/Static test suite]   ⚙  ::set-output:: m2_url=
[Coding standards/Static test suite]   ❌  Failure - Main Install Magento 2
[Coding standards/Static test suite] exitcode '1': failure
[Coding standards/Static test suite] ⭐ Run Post Install Magento 2
[Coding standards/Static test suite]   🐳  docker cp<EMAIL_ADDRESS><EMAIL_ADDRESS>[Coding standards/Static test suite]   🐳  docker exec cmd=[chown -R 1001:1001<EMAIL_ADDRESS>user=0 workdir=
[Coding standards/Static test suite]   ✅  Success - Post Install Magento 2
[Coding standards/Static test suite] 🏁  Job failed
Error: Job 'Static test suite' failed

...

Hi @itaymesh,
Thanks for your message.
Reading your error message suggests that there is something wrong with Docker.
Did you install Docker on your machine ? (as explained here)
Thanks

Yes, of course.
I am running Docker for Mac with Intel Chip

Ok!
Well, I never tried to test locally with  nektos/act. And I'm using a linux setup.
But I will try it asap to see if I can reproduce the bug.
For my information, are you able to use DDEV locally on your Mac ?
Thanks

Hi @itaymesh,
I tried ACT and got the same error.
I opened an issue in the ACT repo to find out more:  https://github.com/nektos/act/issues/1731
Thanks

Hi @julienloizelet
Thank you for letting me know. I see we have yet to get a response.
What is your preferred why for testing GitHub Actions?

Hi @julienloizelet Thank you for letting me know. I see we have yet to get a response. What would you preferay for testing GitHub Actions?

Hi,
most of the time, I just use a workflow_dispatch workflow to manually trigger an action.
As I am working on Linux, I assume that if it works on my machine, it will work in the GitHub runner :)
For a more advanced debug (when it is not working as expected), I sometimes use this action to enter in the runner with an ssh session.

No response from nektos: https://github.com/nektos/act/issues/1731. I close this one.


Keep reagent dispenser inventory ordered

About the PR
This will keep the dispensable reagents buttons sorted in lexicographical order.
Additionally, if a jug doesn't have a label, we'll try to use the reagents it contains to make the button label.
Why / Balance
Purely QoL.
Technical details
N/A
Media
https://github.com/space-wizards/space-station-14/assets/262623/da99dc00-df38-496d-aea2-d9be14d91f5a

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

gee i sure wish someone would make the bartenders dispensers use the reagent names instead

gee i sure wish someone would make the bartenders dispensers use the reagent names instead

you can fix things yourself, you can make github issues, but please leave the sly begging off of PRs. thank you.

i'm going to just comment that unlabeled containers using the reagent contents instead of the entity name is quite a strong buff and removes a fairly intentional element of sabotage to the system. I get the quality of life perspective, but there's definitely a case to be made for powerful chemistry systems to be more fallible.

I didn't know the reagent names were not displayed intentionally.
How about I take the reagent name displaying out of this PR then? Chem uses labelled jugs most of the time anyway.

Yes, please undo the reagent name display changes. It looks like the sorting boils down to a one-line change on the client, then.

I reverted the reagent name display change. Indeed that's quite a simple change in the end!


feat: begin node schema and ops

#15
#14
#13  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rphmeier and the rest of your teammates on  Graphite

Merge activity

Mar 21, 11:56 AM EDT: @pepyakin started a stack merge that includes this pull request via Graphite.


LayerStack::PopLayer does not delete the Layer object

As long as m_Layers is a std::vector<Layer*> and a std::vector<std::unique_ptr>,  calling erase() in LayerStack::PopLayer will set the pointer to null and not delete the object. Do I miss something?

There are times you want to reinsert layers. Reallocation can be sometimes very time consuming

Or we could pass a boolean to the pop function (with default value)? So you can tell if it has to delete it or not?

Did Cherno mention whether he wants the LayerStack to have ownership of Layers? Seeing as we delete all the layers in the LayerStack's destructor I think LayerStack does take ownership of the layers.

Or we could pass a boolean to the pop function (with default value)? So you can tell if it has to delete it or not?

I like the idea of passing a boolean on whether it should delete it. The default should probably be to delete. The application already has the pointer to the layer just by calling the method so if the application specifies to not delete then we expect it to take ownership of the layer.
We should probably start documenting these things (in the wiki maybe?), but that's another issue.

Did Cherno mention whether he wants the LayerStack to have ownership of Layers? Seeing as we delete all the layers in the LayerStack's destructor I think LayerStack does take ownership of the layers.

Or we could pass a boolean to the pop function (with default value)? So you can tell if it has to delete it or not?

I like the idea of passing a boolean on whether it should delete it. The default should probably be to delete. The application already has the pointer to the layer just by calling the method so if the application specifies to not delete then we expect it to take ownership of the layer.
We should probably start documenting these things (in the wiki maybe?), but that's another issue.

Pop layer could return a reference to the layer if the layer isn't deleted, returning a null when it is deleted maybe? To transfer ownership back? I think these things should be documented, but cherno didn't want to open up the wiki yet...

My suggested solution was going to be returning the pointer to the popped layer, but seeing as the application already has to provide the pointer to the layer as a function parameter in the first place it seem rather pointless (pun not intended).
We should probably make a separate issue about documentation for Hazel.

My suggested solution was going to be returning the pointer to the popped layer, but seeing as the application already has to provide the pointer to the layer as a function parameter in the first place it seem rather pointless (pun not intended).

You require a reference to the layer to pop it, so the caller of popping the layer can delete this as well... So I think we should stick with not deleting the layer when poping and let the caller delete it (or not, so it can be pushed again).
So with this reasoning, I think this can be closed as it is not realy a bug in the LayerStack?

We should probably make a separate issue about documentation for Hazel.

Same response as before: Make a community driven wiki and go from there... I'm hapy to create some github.io page for it and allow anyone to contribute... This should be a seperate PR. But the general answer: cherno didn't open any official wiki/documentation place so far.


Fix BucketFileInterface::internalListObject unit test.

Since delimiterTools are exported in Arsenal in the algorithms.list
export, the test BucketFileInterface::internalListObject is broken.
This test iterates on all the elements of this export, expected them to
be list constructor.
Pull request template
Description
Motivation and context
Why is this change required? What problem does it solve?
Related issues
Please use the following link syntaxes #600 to reference issues in the
current repository
Checklist
Add tests to cover the changes
New tests added or existing tests modified to cover all changes
Code conforms with the style guide
Sign your work
In order to contribute to the project, you must sign your work
https://github.com/scality/Guidelines/blob/master/CONTRIBUTING.md#sign-your-work
Thank you again for contributing! We will try to test and integrate the change
as soon as we can.

as discussed with Lauren, there are two solutions to fix this problem:

either

As discussed with Lauren, I am going to change the DelimiterTools export path in Arsenal rather than add conditional in S3 unit tests.


[WIP] Avoid crashing prepare function of Connection.

Related Pull Request https://github.com/stephencelis/SQLite.swift/pull/785

@touyu @stephencelis any updates about this PR? we're observing crashes on iOS 10 for iPhone5/5s users (https://github.com/stephencelis/SQLite.swift/issues/928)

@iprox I can't update it because I can't think of any good solutions.
sorry :(

fixed in a different PR


fix thumbnail issue 3526

Description (required)
Fixes #3526
What changes did you make and why?
Thumbnail images were not being fetched for child classes due to incorrect entity I'd being sent in the request. This was fixed by taking the substring at the right index.
Tests performed (required)
Tested on main variant on Google pixel 3a with API level 10.

Thanks for fixing this bug!


' panicked at 'Could not retrieve core::option::Optionchrono::naive::datetime::NaiveDateTime from Value'

the connectorx version is : 0.2.4

Hi @ztsweet , we might need more information:

What database are you using? (e.g. postgres, mysql)
What return_type do you get? (e.g. pandas, arrow)
Would be better if you could provide a simple example that we could reproduce your error

the code like:
df = pl.read_sql(sql, conn)
the database is mysql
I guess the most likely reason is that the datetime means like '000/00/00 00:00:00'

Hi @ztsweet , sorry for the late reply. It seems like '0000/00/00 00:00:00' is not a valid datetime for mysql.

https://dev.mysql.com/doc/refman/8.0/en/datetime.html#:~:text=MySQL retrieves and displays DATETIME,both date and time parts.

I get a similar error for date values that come back from the database as 0000-00-00.

I had a similar issue, when tried to select datetime columns on MySQL.
In my case, qeurying datetime column to string worked such as
SELECT DATE_FORMAT(date, '%Y-%m-%d') FROM TABLE.

same error, and try catch not work.

I had a similar issue, when tried to select something on MySQL.
pyo3_runtime.PanicException: Could not retrieve chrono::naive::datetime::NaiveDateTime from Value
I use connectorx==0.3.1 ,first demo not work.

I'm having the same issue on connectorx==0.3.2 and a MySQL database.
Error: panicked at 'Could not retrieve core::option::Option<chrono::naive::time::NaiveTime> from Value'
Here's the scheme of the table:

I found that the error happens when getting a negative time column. If I query a view with a column like this timediff(DATE_SUB(NOW(), INTERVAL 5 MINUTE), now()) as time_diff``, I get the error. Here's the view code to reproduce:
CREATE OR REPLACE
VIEW `v_test` AS
select
    timediff(DATE_SUB(NOW(), INTERVAL 5 MINUTE), now()) as `time_diff`


ENH add monitor keyword to the autoencoder

This PR adds the monitor keyword to the autoencoder.
Closes #20

@samcarlos This one is good to go.

@samcarlos This is fixed! Back to you!


Migrate volumes to compose extensions

Part of https://github.com/appvia/kev/issues/443
Figure out the necessary tickets to move Volumes from labels to extensions.
This includes:

Validation.
K8s manifest transformation.

Created follow up tickets:

#486
#489
#488
#487


Goscaleio cleanups

This patch moves the HTTP request logic into a common place, /api/api.go which makes
it easier to log requests and replies.  Logging is now enabled (and works!) with two new env vars:

GOSCALEIO_DEBUG
GOSCALEIO_SHOWHTTP

These changes consolidate all the JSON encoding/decoding logic, all the handling of HTTP headers for Auth and Content-Type.
I've built the latest REX-Ray with this patch, and found it to be backwards compatibility, specially testing create/delete/attach/mount/unmount. Tested with foreground and service mode, and specially triggered a logout via curl to test that token expiry and reauthentication is working. I have not tested with useCerts.  Speaking of certs...
One odd thing in the code is the use of embedded certs/CAs in certs.go, rather than using the system cert pool. I have actually changed that to use the system cert pool, but want feedback on if this is okay to do. If so, I'll delete that file entirely.
Closes #26

I believe the certs was all me a long while back. The idea was to be able to capture std certs in the app and thus make building a container from "scratch" and not have to include any ssl deps to make RR work. I don't think its relevant now considering where we are with our plugins and alpine.

@clintkitson That makes sense.  Thanks for the background. I agree that we can probably move forward w/o them at this point. I think it's better -- some of those certs may have been long revoked.
Thanks for the feedback @akutz. I'll incorporate it next week!

@akutz incorporated all feedback, minus extra code for special handling of redirects. PTAL.


Add support for ChangeHistoryService

This is for issue #7. Currently undoing doesn't work great. It does seem to work fairly consistently but only after a few undos. It also runs into an issue of trying to undo things that were destroyed, such as the Link ObjectValue's and prefab models. This needs further work before it can be merged back into the master.

ee7e441 is such a bad idea since it'll keep everything loaded in memory, but I'm not sure how we could do undo/redo otherwise.
Since the cloned in prefabs aren't important to keep around in any meaningful way, maybe we could prioritize an easy "only undo placeholders" system? I'm not sure how that could work though

Closing this out. We've had a shift to using purely models for everything and no placeholder parts. We'll need a different approach to history in a new pull request.


drivers/note: move the note formatting code from trace_dump into noteram_drivers.c

Summary
This PR moves the note formatting code from trace_dump into noteram and simplifies the noteram code.
Details:
Change 1: move trace_dump to noteram_driver.c
Change 2: replace the spaces in the name in tcb, there cannot be spaces in the thread name in atrace format
Change 3: remove task_context and get_taskname related code, we don't need it anymore
Change 4: simplify the logic of ringbuffer in noteram
Impact
The data returned by reading the /dev/note device is no longer binary data, but a formatted string, and it will only return one note record each time it is read
Testing
self-test + internal CI

Please fix this error in the nuttx-apps:
====================================================================================
Configuration/Tool: esp32-devkitc/watcher
------------------------------------------------------------------------------------
  Cleaning...
  Configuring...
  Building NuttX...
In file included from wdt.c:38:
Error: task_mn.h:74:35: error: 'struct noteram_get_taskname_s' declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
   74 | void task_mn_get_task_name(struct noteram_get_taskname_s *task);
      |                                   ^~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[3]: *** [/github/workspace/sources/apps/Application.mk:171: wdt.c.github.workspace.sources.apps.examples.watcher.o] Error 1
In file included from task_mn.c:37:
Error: task_mn.h:74:35: error: 'struct noteram_get_taskname_s' declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
   74 | void task_mn_get_task_name(struct noteram_get_taskname_s *task);
      |                                   ^~~~~~~~~~~~~~~~~~~~~~
task_mn.c: In function 'task_mn_print_tasks_status':
Error: task_mn.c:65:33: error: storage size of 'task' isn't known
   65 |   struct noteram_get_taskname_s task;
      |                                 ^~~~
Error: task_mn.c:86:25: error: 'NOTERAM_GETTASKNAME' undeclared (first use in this function); did you mean 'NOTERAM_GETMODE'?
   86 |           ioctl(notefd, NOTERAM_GETTASKNAME, (unsigned long)&task);
      |                         ^~~~~~~~~~~~~~~~~~~
      |                         NOTERAM_GETMODE
task_mn.c:86:25: note: each undeclared identifier is reported only once for each function it appears in
Error: task_mn.c:65:33: error: unused variable 'task' [-Werror=unused-variable]
   65 |   struct noteram_get_taskname_s task;
      |                                 ^~~~
task_mn.c: At top level:
Error: task_mn.c:244:35: error: 'struct noteram_get_taskname_s' declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
  244 | void task_mn_get_task_name(struct noteram_get_taskname_s *task)
      |                                   ^~~~~~~~~~~~~~~~~~~~~~
Error: task_mn.c:244:6: error: conflicting types for 'task_mn_get_task_name'; have 'void(struct noteram_get_taskname_s *)'
  244 | void task_mn_get_task_name(struct noteram_get_taskname_s *task)
      |      ^~~~~~~~~~~~~~~~~~~~~
task_mn.h:74:6: note: previous declaration of 'task_mn_get_task_name' with type 'void(struct noteram_get_taskname_s *)'
   74 | void task_mn_get_task_name(struct noteram_get_taskname_s *task);
      |      ^~~~~~~~~~~~~~~~~~~~~
task_mn.c: In function 'task_mn_get_task_name':
Error: task_mn.c:255:17: error: 'NOTERAM_GETTASKNAME' undeclared (first use in this function); did you mean 'NOTERAM_GETMODE'?
  255 |   ioctl(notefd, NOTERAM_GETTASKNAME, (unsigned long)task);
      |                 ^~~~~~~~~~~~~~~~~~~
      |                 NOTERAM_GETMODE
task_mn.c: In function 'task_mn_subscribe':
Error: task_mn.c:261:33: error: storage size of 'task' isn't known
  261 |   struct noteram_get_taskname_s task;
      |                                 ^~~~
Error: task_mn.c:261:33: error: unused variable 'task' [-Werror=unused-variable]
task_mn.c: In function 'task_mn_unsubscribe':
Error: task_mn.c:281:33: error: storage size of 'task' isn't known
  281 |   struct noteram_get_taskname_s task;
      |                                 ^~~~
Error: task_mn.c:281:33: error: unused variable 'task' [-Werror=unused-variable]
cc1: all warnings being treated as errors
make[3]: *** [/github/workspace/sources/apps/Application.mk:171: task_mn.c.github.workspace.sources.apps.examples.watcher.o] Error 1
In file included from watcher_main.c:34:
Error: task_mn.h:74:35: error: 'struct noteram_get_taskname_s' declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
   74 | void task_mn_get_task_name(struct noteram_get_taskname_s *task);
      |                                   ^~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[3]: *** [/github/workspace/sources/apps/Application.mk:231: watcher_main.c.github.workspace.sources.apps.examples.watcher.o] Error 1
make[3]: Target 'all' not remade because of errors.
make[2]: *** [Makefile:53: /github/workspace/sources/apps/examples/watcher_all] Error 2
make[2]: Target '/github/workspace/sources/apps/libapps.a' not remade because of errors.
make[1]: *** [Makefile:47: all] Error 2
make: *** [tools/LibTargets.mk:232: /github/workspace/sources/apps/libapps.a] Error 2
make: Target 'all' not remade because of errors.
/github/workspace/sources/nuttx/tools/testbuild.sh: line 370: /github/workspace/sources/nuttx/../nuttx/nuttx.manifest: No such file or directory
  Normalize esp32-devkitc/watcher

Please fix this error in the nuttx-apps:

I've already fixed the error in the nuttx-apps：https://github.com/apache/nuttx-apps/pull/1942


[Feature] - En Passant

When a pawn advances two units on its first move, if it could have been captured on the first square, then it can be captured

This can only occur when the opportunity presents itself, then it can no longer be done


add deb package info to index_pkg_db for prov_pkg

This PR adds the debian package info to bomsh-index-pkg-db for prov_pkg metadata of debian package build.
It also has some minor fixes.


Simple 1.19.x port

Mod Name
vs-additions
This issue occurs when only Valkyrien Skies, addons, and the mod I have specified are installed and no other mods

[ ] I have tested this issue and it occurs with only Valkyrien Skies, addons, and the mod I have specified

Minecraft Version
1.18.2
Mod Loader
Forge
Issue description
Is it possible to make a simple port for 1.19,x?
Issue reproduction
Or maybe, can I try to make this port?
Logs
No response

Due to the emergence of the Reign of Nether, this (porting to 1.19) might be put on the agenda. 🤔


Added Issue #11

Description
enter here if you have any details
Program Name -
Issue No.- #

Type issue number after hash(#)

Checklist(self check)

[ ] Yes, this task assigned to me.
[ ] My code follows the style guidelines(Clean Code) of this project
[ ] I have performed a self-review of my own code
[ ] My Filename is in camelCase format
[ ] I have added Problem statement, Problem link in file.

@gokulrajanpillai @gourav-j @jayanthj737 @aayushi-droid Could you please review it and merge!

Thanks for making PR and participating..


Rename xit to it in specs in temp directory before running them

Allows the example to be tested against all the specs, including the ones that were marked not to be run right away with xit.
Possible solution to Issue #71
I tested this on my Ubuntu machine. I'd want to see if it worked on Travis and in any other environments that need to be supported before being confident of it.

For what it's worth, here's how I get the pull request downloaded locally:
git fetch origin refs/pull/72/head
git checkout -b drueck/xit-all FETCH_HEAD

Ah, some googling yielded this stack overflow thread about changing files in place using sed on osx. http://stackoverflow.com/questions/7573368/in-place-edits-with-sed-on-os-x
I'll update the PR to account for this. Would you be willing to test it again on your mac, assuming it passes on Travis again? Sorry, I only have linux machines at the moment. Thank you!

Yeah, no problem! Just let me know when the PR is updated.

Oh, it's updated. Sorry. I just amended the commit and force pushed the
update. Thanks!
On Fri, Jan 16, 2015, 5:56 PM Katrina Owen<EMAIL_ADDRESS>wrote:

Yeah, no problem! Just let me know when the PR is updated.
—
Reply to this email directly or view it on GitHub
https://github.com/exercism/xjavascript/pull/72#issuecomment-70349613.

ah, cool. I wasn't sure. Give me a sec.

it works :sparkles: great :sparkles:

Based on the discussion over in #71 I'm going to assume that windows devs will either have cygwin and friends, or they'll push a PR and travis can check.

Awesome, thanks. :)


Splash screen when running from conda shows partially on Windows

It seems that sphinx was not the only factor with the OP. pillow must also be installed for the splash screen to render properly. I don't understand this.
So installing Spyder from the installer, with sphinx < 7.4.0 and pillow included via matplotlib-base, there is no issue.
However, installing Spyder by itself, e.g. conda create -n test python=3.11 spyder=6.0.0.rc2, results in the bad splash screen.
The splash screen renders correctly:

If the environment is activated first, e.g. conda run -n test spyder. Shortcuts do not activate the environment, as doing so creates a flashing cmd window. @jaimergp and I are unable to fix this.
OR if the environment Library\bin is in the PATH environment variable. This is added to PATH when the environment is activated.
OR if pillow is installed and sphinx < 7.4.0.

I suspect that Qt requires something in Library\bin and that the combination of sphinx < 7.4.0 and pillow either obviates the need for whatever is in Library\bin or alters Qt's search paths to include Library\bin.
Continuation of #22370

Duplicate of #22374


decouple top-app-bar-row in an own component

after looking closer at the upstream project mdc-web, it doesn't seem that the row of a top-app-bar is a candidate for multiplicity usage


Website [various pages] add inline notification about Expressive theme sunset

Once the message is written and signed off by team, add that message to website as inline notification on several pages:

Developing
Designing
Resources
The goal is to warn people before they access resources that are about to go away such as expressive theme design kit, and expressive wrapper.

PR created
https://github.com/carbon-design-system/carbon-for-ibm-dotcom-website/pull/1004


about virtual  env install

My environment is:
Python3 --version: python3.7
conda: miniconda
Now I need to manage the python3 virtual environment:

There are more than 500 python packages to be installed, but there are many dependencies in the python packages. As a result, the installation of requirements.txt cannot be successful every time the virtual environment is installed，have a good idea ？ @jezdez

Thanks! Can you provide reproducible steps, input files, and any error messages?

Thanks! Can you provide reproducible steps, input files, and any error messages?

1、create a venv :  conda create --name py379 python=3.7
2、pip install -r requirements.txt
but there are many problems like:

can you import my requirements.txt to creaete a vens ，here is my import file:
requirements.txt


tests: ensure that /etc/pki/product-default exists too

Fixes commit 00ba7f061d9a7132bb7e5aa6f27b37996892689c.

[citest]


tree borrows: consider some retags as writes for the purpose of data races

Turns out not all retags can be freely reordered. Those that cannot should be considered writes for the data race model, to aid with optimizations.
Only the last commit is the actual change; the ones before that are some refactoring I couldn't stop myself from doing.

@bors r+

:pushpin: Commit cef0eb3cbed1cb4cb3e33ac0fbe7f756f27ebd51 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit cef0eb3cbed1cb4cb3e33ac0fbe7f756f27ebd51 with merge 48322c40f221995699284a22c9eed1022e472494...

@bors r- retry

:sunny: Try build successful - checks-actions
Build commit: 48322c40f221995699284a22c9eed1022e472494 (48322c40f221995699284a22c9eed1022e472494)

@bors r+

:pushpin: Commit 7ca3d03f2031cd4e30da60a46c2a9e73354996de has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 7ca3d03f2031cd4e30da60a46c2a9e73354996de with merge 0e9981e1747921d4307cbe9db0be120db91a5202...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 0e9981e1747921d4307cbe9db0be120db91a5202 to master...


pinremoteimage version up 3.0.1

check pinremoteimage version

@DreamingInBinary It's fixed already in 3.0.3.
Also, it got SPM support. How about SPM support in this one too? :-)

Hey @danielgindi - I actually switched jobs up a bit ago, but @ay8s could probably help with this.

@ay8s Are you available for this?


PCL profile cleanup

Split off from #165
PCL profiles to .NET Standard conversion can be 2.x scheduled. There is about 12 supported PCL profiles (of approximately 80), but they are the most common.
<Import Project="$(MSBuildExtensionsPath32)\Microsoft\Portable\$(TargetFrameworkVersion)\Microsoft.Portable.CSharp.targets" />

The one above can be made autoremoved in 2.x if no PCL profiles are left in TargetFrameworks.

@andrew-boyarshin so this would mean rewriting the profiles mentioned here to the corresponding net standard version?
In the case of a non supported one we should abort, right?

Yeah, that seems like it. Although this page is better in that respect (don't forget to enable showing legacy profiles).


Our website doesn't unfurl well

Website doesn't unfurl well

Whare are you looking for here?

Looks like adding the icon to the text.

Whare are you looking for here?

Probably needs to be more concise.

Cleaned it up a bit.
https://github.com/functionless/functionless/pull/196/#issuecomment-1149159558


Introduce fluent declarables in RabbitMQ Container.

Fixes #1775 Introduce fluent declarables in RabbitMQ Container.
Introduce a new RabbitMQContainer.declare(...) method to declare objects such as exchanges, queues, etc in RabbitMQ.
The objects passed to the declare method are constructed via static factory methods from the DeclareCommands class.  Those objects provide a fluent methods for method chaining.
Example:
public static RabbitMQContainer rabbitmq = new RabbitMQContainer()
    .declare(exchange("myExchange").direct())
    .declare(queue("myQueue"))
    .declare(binding("myExchange", "myQueue"))
    .declare(user("skroob").password("12345"))
    .declare(permission("skroob").read(".*"))
    .declare(vhost("myVhost")
        .declare(exchange("myExchangeInMyVhost").direct())
        .declare(queue("myQueueInMyVhost")
            .autoDelete()
            .maxLength(1_000)
            .messageTtl(1_000L))
    );

Existing with* methods are kept for backwards compatibility.
New functionality provided by the new fluent declarable objects:

Allow objects to be declared inside a vhost.  Previously impossible with old with* methods.
Only need to specify the minimum number of optional args.  Previously had to specify all optional args if only one optional arg was needed.
Better defaults provided in the declarable objects, to minimize args needed to be specified.
Type-safe convenience methods are provided for common usages.  Examples:

exchange("myexchange").direct() instead of withExchange("myexchange", "direct")
queue("myqueue").maxLength(1000).autoDelete() instead of withQueue("myqueue", true, false, Map.of("x-max-length", 1000))

Also added documentation for the RabbitMQ module. (Be sure to check out the preview!)
Any and all feedback is greatly appreciated.  Nitpicks, naming, structure, etc

Hi @philsttr,
Thanks, looks promising !
Just wanted to let you know that we were working on releasing 1.12.1 but now back on track and will take a look at your PR as part of the next (minor) release 👍

Also pinging @martingreber and @twillouer who were working on the RabbitMQ module

Hey @philsttr, thanks for this well thought of PR, I think the API is a very interesting idea (and sorry for not providing further feedback on #1775).
Since I'm not a big RabbitMQ user, I have to invest a bit of time in thinking through the current approach and what would be the best way to move forward with the API.
One thing that's on my mind, it that this would be an API which substantially diverges from the API of our other container implementations. I'm not saying that we should not do this, I just want to make sure that the asymmetry makes sens in this case (or if we should derive a generic API concept from this?).

Thanks for taking a look everybody!
Regarding:

this would be an API which substantially diverges from the API of our other container implementations

I didn't think the configuration API was too different from other containers.  It's basically just passing a parameter object to a container method, and using a fluent style to build the parameter object.
It's pretty similar to the way the BrowserWebDriverContainer.withCapabilities works.
For example:
public BrowserWebDriverContainer firefox = new BrowserWebDriverContainer()
        .withCapabilities(new FirefoxOptions()
            .setBinary("foo")
            .addArguments("arg1")
            .addPreference("key", "value")
            .setAcceptInsecureCerts(true)
        );

The differences in the RabbitMQContainer as implemented are:

A static factory method is used to construct the initial parameter object instead of new (I could get rid of the static factory methods if desired, but I thought they made the config code more readable)
The container method is named declare.  (I could potentially rename this to withDeclared to make it more parallel with the other with* methods)
Shortened method names are used when configuring the parameter object (e.g. direct() instead of withDirectType() or something).  I could rename these if needed, at the expense of increased verbosity.
The declare method can be called multiple times to declare multiple objects.

Having said that, the internal design of the parameter objects is quite a bit different, in that the parameter objects can be "executed", and call back into the RabbitMQContainer when executed.  This shows through a little bit because the parameter objects are called "Commands".  So, yeah, they are a little more than parameter objects.  I could put some more thought around separating the parameter object from the execution logic if needed.  Maybe get rid of "Command" from the class names.
The other thing that I think makes the RabbitMQContainer somewhat different than the other containers is that there are a lot of "things" that can be configured, and each of those things has a lot of configuration options themselves.  Most of the other containers have relatively few things that can be configured, and each of those things have relatively few configuration options.  So, I can see a need for them to differ some.
At an absolute minimum, I need a solution for declaring objects inside a vhost (which is what sent me down this path to begin with).  So, keep that in mind when thinking about alternative solutions.
In any case, I'm happy to discuss and incorporate feedback.  I'm really loving test-containers!

Hey guys, sorry for the late reply.
This is quite a good improvement. Thanks @philsttr.
Just some food for thought:
When I first worked on the RabbitMQ container I had to make a choice between using the RabbitMQ CLI (rabbitmqadmin) or passing in a rabbitmq.conf for configuring RabbitMQ.
The CLI is nice because you only have specify the bare minimum, and it sets sensible defaults for the rest. Using rabbitmq.conf on the other hand requires you to specify everything explicitly.
This was one of the reasons for choosing the CLI.
However, in hindsight it might have been cleaner to create a rabbitmq.conf builder and pass in the built configuration file to RabbitMQ. We wouldn't need all these rabbitmqadmin commands (which also need to be declared in a specific order). We would just need to create a rabbitmq.conf file and mount it.
What do you guys think?

Hi @philsttr, thanks for your PR but after some learnings we think the container class should only have the responsibility about starting the container and offer the right attributes so the client can connect to it. Handling this kind of configuration can be handled via execInContainer already and we encourage to do so. Another reason is that we don't want to couple to the cli specifics of the service. We encourage to you to have a library and release it so others can take advantage of it.


Exception thrown while executing UI block: * -[__NSDictionaryM setObject:forKeyedSubscript:]: key cannot be nil

Bug report

Summary
`Exception thrown while executing UI block: * -[__NSDictionaryM setObject:forKeyedSubscript:]: key cannot be nil
__44-[RCTUIManager flushUIBlocksWithCompletion:]_block_invoke
RCTUIManager.m:1201
__44-[RCTUIManager flushUIBlocksWithCompletion:]_block_invoke.498
__RCTExecuteOnMainQueue_block_invoke
82506F82-C97A-3CF2-BA6C-ACA532D8AA49
82506F82-C97A-3CF2-BA6C-ACA532D8AA49
_dispatch_main_queue_callback_4CF
0E00CA08-C176-30F7-9CF9-445B374C0686
0E00CA08-C176-30F7-9CF9-445B374C0686
CFRunLoopRunSpecific
GSEventRunModal
280B8BEE-0493-3862-B922-9A87C5F46EE8
UIApplicationMain
main
start`
Environment info
"react-native": "0.66.1",
      "react": "17.0.2"
      "react-native-maps": "^0.29.3",

Steps to reproduce
npx react-native run-ios
when return screen have this issue
Reproducible sample code
<MapView
initialRegion={{
latitude: -1.395197,
longitude: -78.423335,
latitudeDelta: 0.009999,
longitudeDelta: 0.009999,
}}
style={{height: 200}}
provider={PROVIDER_GOOGLE}
customMapStyle={mapStandardStyle}
showsUserLocation={true}
>
<Marker
coordinate={{
latitude: latitude,
longitude: longitude,
}}>
<Image
resizeMode="cover"
style={styles.marker}
source={require('../../../../assets/img/map-pin.png')}
/>

Same issue

same issue here

Same here, did anyone find a solution?
I noticed that this does not happen in Debug Mode in simulator. It also doesn't happen when I use the arrays index as a key. If I use another property, like an id, the error appears:
Works:
            {results &&
              results.map((entry, index) => {
                return <PubMapMarker key={index} pub={entry} />;
              })}

Does not work:
            {results &&
              results.map((entry) => {
                return <PubMapMarker key={entry.id} pub={entry} />;
              })}

Using the Apple Maps implementation on iOS solves the problem for me (i.e. dropping the provider={GOOGLE_PROVIDER} prop).

This happens only when the marker has children

Any solution??

This is not an issue regarding this project, instead it's an implementation detail difference between GoogleMaps and apple MapKit on iOS.
mainly Apple MapKit supports UIView object inside markers, it knows how to display them. which means if you create a react element inside the marker  in the above example a UIKit view element is created UIImage and added when AppleMaps is used.
but Google Maps don't support native UIKit Views (I think they even render using openGL). so when react native tries to create a view inside the Marker .. everything breaks.
this project at the end of the day is limited by what is possible via the native maps libraries used, so I would recommend looking here: https://developers.google.com/maps/documentation/ios-sdk/marker and see what's possible when it comes to GoogleMaps on iOS before attempting to use it.

Make sure you do not pass any undefined values to Animated.View (Map).

I'm facing the same issue when trying to cluster markers and if the point is a cluster render circle with the number of points. Is there any workaround to render such a custom marker without crashing?

@salah-ghanim @ingvardm This only started to happen when upgrading react-reanimated to 2.10.0 version. Before it worked fine even with such markers. So its about some interdependency in the animation core it seems.

Using the Apple Maps implementation on iOS solves the problem for me (i.e. dropping the provider={PROVIDER_GOOGLE} prop).

This happens only when the marker has children. For my solution i can use images instead of nested views on iOS, see if you can do the same. Also you can try getting the position of thee marker (onLayout) and use that to place your whatever on top of it.

Above both fix this problem for me.

@salah-ghanim @ingvardm This only started to happen when upgrading react-reanimated to 2.10.0 version. Before it worked fine even with such markers. So its about some interdependency in the animation core it seems.

@pke Can you please tell me with which version you got it to work? I tried downgrading react-native-reanimated to version 2.9.1 and 2.3.3 but I keep getting the same error

but Google Maps don't support native UIKit Views (I think they even render using openGL). so when react native tries to create a view inside the Marker .. everything breaks.

I'm not convinced this is the case since the markers do render the first time no problem. The issue seems to be when a key is dropped. This would explain why some developers are mentioning using indexes as a key rather than ids.

Originally posted this comment on a separate issue thread, but figured I would post here since this thread has a lot of activity.
I have written a blog post if you are interested in reading about my solution a little bit more, but if not, I'll add the TL;DR in this comment.
Here's the blog post
And here is the TL;DR:
If you are getting the error Exception thrown while executing UI block: * -[__NSDictionaryM setObject:forKeyedSubscript:]: key cannot be nil while trying to use custom markers with Google Maps on iOS via react-native-maps, it is possible the root cause is a conflict with react-native-reanimated.
I don't know exactly what the conflict is, however, I have two solutions that may work for you!
Solution 1
If feasible, you can remove react-native-reanimated from your project and that should resolve the issue for you.
If that isn't an option, I would encourage you to rebuild your map in a test project without reanimated, and implement your map so that you are using custom markers (and it should work). Then, reintroduce reanimated into that project, and add your desired functionality in piece wise until you can isolate what method in reanimated is causing the error. In our case, it was our use of FadeInUp and FadeInOut. Your mileage may vary, but you should be able to find alternative animation solutions while preserving your app's behaviour.
Solution 2
Agnostic of any react-native-reanimated conflicts, this error is thrown because the indices from the marker array you're mapping over are bring dropped in the case that the marker array length, n, is changing such that n' < n.
You can create a hook that will always return a constant sized array containing marker objects to your map view, so that it may map your objects to custom markers. For every index in this array, there will exist either a real marker object that renders on the map, or a buffer object that will not render on the map. Either way, the indices being used as keys will always exist, therefore you will not hit this error.

I solved it like below.
    const [isLayout, setLayout] = useState(false);

    const onLayout = () => {
      setLayout(true);
    };
    ...

  <MapStyledView
    onLayout={onLayout}
        ...
    <Marker
      key={'startMarker'}
      coordinate={}}>
      {isLayout && <MarkerItem />}
    </Marker>

I just solved this by upgrading my "react-native-reanimated" to "^3.0.0-rc.10". (was 3.0.0-rc.3).
I checked the change log, and I think this bug was related to entering and exiting props of reanimated.

I just solved this by upgrading my "react-native-reanimated" to "^3.0.0-rc.10". (was 3.0.0-rc.3). I checked the change log, and I think this bug was related to entering and exiting props of reanimated.

That fixed it for me thanks

@jinliming2 - thanks u saved my life

_notifyAboutProgress Getting this after installing  ^3.0.0-rc.10

I am facing this issue after after installing ^3.0.0-rc.10
[!] Unable to find a specification for React-hermes depended upon by RNReanimated

Expo 49 supports reanimated 3.3.0 and resolves the issue for me.

have anyone a better solution? we can't update reanimated because of a bug of the new v3

have anyone a better solution? we can't update reanimated because of a bug of the new v3

same trouble, and I've been looking for a solution for quite a long time

Has anyone tryed something like removing the markers first and then remove the MapView on the next frame?


Add Open Graph image

Description
The Open Graph images are not generated when we share https://docs.localstack.cloud/ over social media.

References

Use https://developers.facebook.com/tools/debug/ to validate results for Facebook.
Use https://www.linkedin.com/post-inspector/ to validate results for LinkedIn.
Use https://cards-dev.twitter.com/validator to validate results for Twitter.

@whummer @thrau

@thrau @whummer

Hi @iamrajiv 👋
Would you like to work on it? I have assigned you the issue, but feel free to issue if there is something else on priority 😄

Taking this up ✨


Apk Error

after executing release command system stucked and didn't gave anything

please check tutorials there ! , fast solution [remove folder apk tools] then open builder again !


Remove hardcoded Kitura and Swift versions from guide

For the moment we're going to remove specific references to:

the 2.6.0 and 2.7.0 Kitura releases from the guides and reference the releases link instead
Swift 4.0, 4.2 and 5.0 from our example package.swift files

Closing issue as it is fixed by the above PRs.


Debugging Live Review

1. Make teacher_portfolio

2. Open login page on browser and console

3. Putting breakpoint in fetch code

4. Trying login with breakpoint, shows pause

1. Make CPT project

2. Run backend

3. Inspect page, open console

4. Putting breakpoint on fetch code

5. Trying to login with breakpoint, pause shown

6. Step over button pressed, shown in console

7. Login works after play button is pressed, user is redirected to home page

1. Breakpoint put in backend, pause shown

2. Step over performed multiple times, highlights in code shown


[Bug]: Some issues encountered and existing solutions while compiling Blobstore.

Backgroud
I encountered some issues while compiling blogstore, and through communication with @pengtianyue025 （thanks a lot!!!), I solved some of the problems in my own way (which may not be the optimal solution). Perhaps this information will be useful to other developers.
The environment

OS: Ubuntu 22.04 amd64 which installed in multipass vm, the host os is ubuntu 20.04 amd64
gcc -dumpversion: 11
cmake version 3.22.1

1. GCC(marjor 11) regard warnings as errors, so that the compile failed
Bug && To Reproduce

(use gcc 11)
cd cubefs/blobstore
rm .deps/lib/librocksdb.a  # if exists
./run.sh

run.sh will execute build.sh, and there are many warnings when compiling librocksdb.a, and gcc regard them as errors.
screenshots here:

Although the build.sh already has handling for ignoring warnings, it seems insufficient.
https://github.com/cubefs/cubefs/blob/d34dc4010dfb4e55e651c5390ce1badfe2ccf992/blobstore/build.sh#L132
I tried adding a -w option at the end to ignore all warnings, and it worked. (But this is obviously not elegant, so I raised an issue.)
The final code looks like this: FLAGS="-Wno-error=deprecated-copy -Wno-error=pessimizing-move -w"
2. blobstore faild to flock
Bug

** How to Reproduce**
I didn't do anything, just execute sudo ./run.sh --consul at cubefs/blobstore.
I even try to execute chmod 777 -R to whole root cubefs dir. It doesn't work.
Analyze and temp resolution
The errror is from:

I guess blobnode.flock is just a regular file, but cubefs simulates lock operations by creating/reading this file (only successful creation and reading means the lock has been acquired).
So I execute touch blobnode.flockand re-runrun.sh`, it did work.
I even tried modifying the .conf file, changing the default flock name to blobnode2.flock, but I still got the same error, so it's not a problem of another process acquiring the file lock.
Therefore, I still can't understand why the file cannot be created correctly, because run.sh has already automatically created many additional files in this directory, so theoretically, it should have the necessary permissions. (maybe due to 22.04 or multipass?)
This is reponse from ChatGPT:

Maybe we could use os.O_RDWR|os.O_CREATE rather than os.O_CREATE|os.O_RDONLY?

Update: When I change os.O_CREATE|os.O_RDONLY to os.O_RDWR|os.O_CREATE, it could open blobnode.flock successfully.

You can check if the latest version of the master branch has already solved the first issue. And the second issue need @JasonHu520 confirm

Sorry, it doesn't work

you can try again with master branch

you can try again with master branch

Cool!  (cd cubefs && make blobstore)

@aFlyBird0 seem that your blobstore compiling is success, so I close this issue.
plz re-open it if necessary.


XML docs are not showing up in the IDE using the nuget package

I use the nuget package but I cannot see the xml docs (which are in the source code)
Perhaps "GenerateDocumentationFile" was not set while generating the nuget build?
https://stackoverflow.com/questions/5205738/how-do-you-include-xml-docs-for-a-class-library-in-a-nuget-package/5214745
https://docs.microsoft.com/en-us/dotnet/csharp/codedoc

Hey @ektrah, could you check out PR #93 please? It attempts to solve this.
Thanks.


GitLab certification is not free

After visiting the GitLab I see all the certifications are showing priced at $150 and is not free. Was it free earlier and recently changed!

Hey @Abinash04,
I did some digging and at some point years ago the Certified Associate certifications were free during a promotion. So yeah, you were right to assume they were free earlier and have changed.


JRTB-0: create Skeleton Spring boot project

create Skeleton Spring boot project for JRTB
Acceptance criteria:

Spring boot project created.

implemented in merged commit 985a102 into main


bin/brew: unset functions that override builtins

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

Unset functions that override builtins (for those who override Bash builtins).
Enable all Bash builtins (for those who disable Bash builtins).

To address both comments I can make the following change:
builtin enable compgen unset
for cmd in $(builtin compgen -A builtin)
do
    builtin unset -f $cmd
    builtin enable $cmd
done
....

I don't know how to handle the situation when enable is disabled.

Makes sense, thanks @maxim-belkin!

Thanks for merging, Mike!
Thanks for the comments, Markus and Dawid!


fix: bug 1982 can open multiple entity pickers

Old behavior:

New behavior:

:tada: This PR is included in version 0.353.9 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


start  app with ngnix proxy pass, load js first time is very slow

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions.

@angular/cli: 1.4.1
node: 8.4.0
os: win32 x64
@angular/animations: 4.3.6
@angular/common: 4.4.4
@angular/compiler: 4.4.4
@angular/core: 4.4.4
@angular/forms: 4.4.4
@angular/http: 4.4.4
@angular/platform-browser: 4.4.4
@angular/platform-browser-dynamic: 4.4.4
@angular/router: 4.4.4
@angular/cli: 1.4.1
@angular/compiler-cli: 4.4.4
@angular/language-service: 4.4.4
typescript: 2.3.4
Repro steps.

execute command:
npm start
package.json:
"start": "ng serve --port 4201 --base-href /template/",
The log given by the failure.

The time of loading inline.bundle.js, scripts.inline.js and vendors.bundle.js is 1.0 mins. I can't find any reasons. The project is about heroes which  is copied from https://angular.io.  can anyone help me?
Desired functionality.

Mention any other details that might be useful.

nginx.conf snippt of ngnix for windows: 1.12.1
location /template/ {
proxy_pass   http://localhost:4201;
proxy_set_header   Host    $host;
proxy_set_header   X-Real-IP   $remote_addr;
proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
}

I agree that is very slow, but I don't think we can help you much here... this seems like a problem with your serving setup. But I have to tell you that ng serve is ONLY a development server and should NEVER be used for production.
A better place to ask questions about your setup would be Stack Overflow.

I have the same setup Windows + nginx + ng serve.
It's slow because of the dual stack ipv4/ipv6, locahost refer to ipv6 first.
Solution 1: nginx proxy to ipv4 only
location /template/ {
    proxy_pass http://<IP_ADDRESS>:4201;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

or Solution 2: ng serve listen to ipv6
ng serve --host=:: --port 4201 --base-href /template/  --disable-host-check=true --live-reload=false


Features From Intermediate Layers

Hi @dbolya, congrats for the Yolact++. It seems great improvement.
Maybe this is trivial for you but I am a little bit stuck due to a confusion.
I wonder how can I get features from intermediate layers? For example from C5 or P3 or P7 or right before prediction head or right before Protonet?
I will just try all of these if they are meaningful enough to refine the results.
Thanks for your attention. I’m looking forward to your reply.

Hi @dbolya , can you please respond to this issue? How can we generate figures similar to fig 5 in your ICCV 2019 paper? Thanks.

Can't I use
model = FPN.forward(weights, output)
feature_embedding=model.predict(image)

from here directly? https://github.com/dbolya/yolact/blob/1d3f7bb94f48dff6324b22483161374c35567306/yolact.py#L311

@bayraktare I'm not sure what you mean by that?
I guess you're trying to use a torchvision pretrained FPN and pass those features into the YOLACT prediction head? In that case, the way the FPN was trained in YOLACT and the way some pretrained version of it in torch's model zoo are completely different, and the features aren't likely to be compatible. So I don't think that would work.

Hi @dbolya.
No, I am not trying to use another thing. I am just trying to obtain features from intermediate layers of YOLACT. In particular, the features i try to get are at just before the mask prediction. I will use these features for concatenating them with semantics and forming an embedding to feed another shallow model. And i also continue using the outputs of the YOLACT together. So i am trying to get something similar to my above comment that will seem like this;
model = the_model_just_before_mask_prediction()
output_features=model.predict(input_image/video)

Then, i will use this output_features for the operations i wrote above.

@bayraktare Oh I see. Do you want the protonet activation then? Or the activations before protonet?
If you want to stop right after the FPN activations (before protonet / prediction heads), you can just put return outs here: https://github.com/dbolya/yolact/blob/eee5ce36242fa1de808a287a3cfe6055486e42b5/yolact.py#L578
If you want just protonet activations, you can put return proto_out here: https://github.com/dbolya/yolact/blob/eee5ce36242fa1de808a287a3cfe6055486e42b5/yolact.py#L605
In both cases to use this you would go
model = Yolact()
# ...
feats = model(input_image/frame)

In the FPN case feats will be a list of tensors, while in the protonet case it will be a tensor.

@dbolya actually, i wanted to see the performance for both.
So, thanks a lot for this satisfying reply. i will let you know about the results.

Hi @dbolya i could have been tried a few times but unfortunately couldn't overcome the issues.
    classes, scores, boxes, masks = postprocess(preds , w, h, score_threshold=cst)

  File ".../yolact/layers/output_utils.py", line 41, in postprocess
    keep = dets['score'] > score_threshold

IndexError: too many indices for tensor of dimension 3

When i try to get outputs from postprocess which calls output_utils, the tensor shape is failing to to continue as above. I placed return proto_out here as you wrote at the same indent with the above if:
https://github.com/dbolya/yolact/blob/eee5ce36242fa1de808a287a3cfe6055486e42b5/yolact.py#L605
If I put it at the same indent with the above line, it gives (but this is not our case):
  File ".../yolact/yolact.py", line 595, in forward
    _, _, img_h, img_w = x.size()

TypeError: 'int' object is not callable

If I trace the  keep = dets['score'] > score_threshold, it gives the following:
A tensor tensor([[[.....]]..., [[.......]], ....[[........]], [[....]]]])  with the size of ```
dets.size()
torch.Size([138, 138, 32])
and

w = 1920
h = 1080
batch_idx = 0
interpolation_mode = 'bilinear'
visualize_lincomb = False
crop_masks = True
score_threshold = 0.2

@bayraktare
After the changes you should instantiate a yolact object and call it directly. Either that, or you can just save the detections as a numpy array instead of returning it from YOLACT. In your first snippet, you could also just save preds. If you want to use these features for some downstream task, then I'm not sure why you're calling postprocess in the first place?
I guess if you want to use both the masks and the intermediate features, instead of returning outs or returning proto_out, you can just add it to the output dictionary. Here:
https://github.com/dbolya/yolact/blob/eee5ce36242fa1de808a287a3cfe6055486e42b5/yolact.py#L638
you could add:
pred_outs['feats'] = outs

then the prototype activations is already in pred_outs['proto'] so you can just use that. Then to get this to not error out in postprocess, just change:
https://github.com/dbolya/yolact/blob/eee5ce36242fa1de808a287a3cfe6055486e42b5/layers/output_utils.py#L46
to
if k != 'proto' and k != 'feats':

Then when you use this downstream, when you have
classes, scores, boxes, masks = postprocess(preds , w, h, score_threshold=cst)

# You can access feats here
preds['feats'] # Do stuff with prediction head inputs
preds['proto'] # Do stuff with protonet activations

Hi @dbolya, thank you so much.
It is working now. But a simple modification for example preds[0]['proto'] since preds is a list and preds[0] is a dict.

@bayraktare

On the other hand, there is nothing related to preds['feats'] or preds[0]['feats'] due to nothing in preds about ['feats']. It completely gives error.

Oops, you'll also have to add
result['feats'] = predictions['feats']

here:
https://github.com/dbolya/yolact/blob/092554ad707c2749631dfe545c8a953b2b3f4a68/layers/functions/detection.py#L74

Thanks, it runs properly with these modifications.
Really cool! I think this issue can be closed...

Sorry, @dbolya but I have a further question related to this issue.
Can I get object specific protonet features?
For example; there are 5 objects detected in the image. So, I want to get 5 different protonet features (with the dimension 138x138xk) for each object independently, is this possible?
Thanks for your help again.

@bayraktare Each object uses the same k features. The object specific information comes from the mask coefficient branch (I think there should be a 'mask' element in that same dict above? Those are the mask coefficients).


Heap allocate our atomics

We used C atomics but these were allocated as Swift variables. Even thought they were atomic, concurrent accesses to them could violate Swift’s exclusivity laws, raising thread sanitizer errors.
Allocate the C atomics using malloc to fix this problem.
rdar://129170128

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows

@swift-ci Please test

@swift-ci Please test Windows


Fix Firestore build resulting from the rename of auth to credentials in the iOS SDK

Note that this PR will not build until the iOS dependencies are updated to 8.9.0 (currently they are 8.8.0). This PR will not be merged; instead, it will be merged into the branch that updates the iOS dependencies to 8.9.0.
I tested this locally on Mac and Linux desktop and on iOS simulator.

These changes have been merged in #714. This PR is now obsolete.


MeshCoord should support a coordinate system

On general principles, since a MeshCoord is designed to be a "window" on other data, it should probably "have" the coord-system of the underlying coordinates from which it takes its values + metadata.
context in UGRID
At present, there is no agreed way of attaching a coordinate-system (i.e. grid-mapping) to coordinates of a mesh, since in CF that may only occur via a data-variable.
context in Iris
However, Iris considers the coord-system to be part of a Coord.  So, it should make perfectly good sense for a coordinate of a Mesh to have one (though there is currently an apparent bug preventing it).
Likewise, it probably makes sense for the coord-system of a MeshCoord to always follow that of the associated node coordinates, as established for the other metadata.
Desired implementation:
Since a face- or edge-located MeshCoord takes its bounds from the (re-indexed) node_coordinates, and its points from the face_coordinates or edge_coordinates (which however are technically optional), it makes sense that the MeshCoord should inherit a coord_system from either of those -- and if different, that should probably be an error.
For now, the coord_system of a MeshCoord is always None, and must always be so.
Related

https://github.com/SciTools/iris/issues/5557 : means that the node-coords of a mesh can't actually have a coord-system, at present.
the face- or edge-coordinates, though they are technically optional in UGRID, are currently required in Iris

We expect that in many cases UGRID files will be loaded with no coordinate systems, since there is little detail about grid_mapping in relation to UGRID. There is some debate between Iris developers about whether we should assume a standard GeogCS coordinate system in these cases, since that appears to be UGRID's assumption.
However UGRID is flexible enough that coordinates could really be anything - XY / XYZ / spherical coordinates / S2 indices / ... - and we have already made Iris more rigid than it should be in this regard, so I am personally uncomfortable with baking in even more assumptions.
Therefore, in addition to MeshCoord inheriting the underlying coordinate system, I would also advocate for a new method: Mesh.add_default_coord_system(), which would modify all the Mesh's coordinates by adding GeogCS(iris.analysis.cartography.DEFAULT_SPHERICAL_EARTH_RADIUS).


Dependabot offers by way of CVE/critical notifications

User Need
As an Operations Engineering Team
I want to know about CVEs and other high criticality vulnerabilities
so that we can fix those vulnerabilities and keep our code secure.
Value
One of our reasons for managing dependancies is to ensure security vulnerabilities are fixed. We want to check what coverage dependabot currently provides us so that we decide if it meets our needs and whether we need to invest time in looking at alternatives
This is a small spike to determine if dependabot is helping us meet this user need.
Questions

Does dependabot provide CVE/critical notifications?
Do we have features enabled?

Acceptance Criteria:

We understand what coverage dependabot offers us in managing CVEs and critical vulnerabilities.
If this feature is available it should be enabled as part of this story.

Notes:

We found dependabot was helping, but you also needed to enable security scanning on the repo. This did however generate a lot of noise that weirdly, caused more issues as we're presented with every small issue that can be classed as wont fix - A solution like snyk, or trivy at build time is better

Aged out


Merge Dev to Main

Description
Merge current work on Dev to Main.

Codecov Report

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

@@           Coverage Diff           @@
##             main      #11   +/-   ##
=======================================
  Coverage        ?   89.56%
=======================================
  Files           ?       13
  Lines           ?      278
  Branches        ?       46
=======================================
  Hits            ?      249
  Misses          ?       28
  Partials        ?        1

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 1649ac1...a2b11f2. Read the comment docs.


Support debugging and code coverage of jsdoc plugins

I have created a jsdoc plugin for documenting mongoose models, https://github.com/sgilroy/jsdoc-plugin-mongoose but I am finding it challenging to create unit/integration tests because there does not appear to be a way to run jsdoc programmatically in the same process as the test. I believe resolving #938 would be a good way to resolve this, but I am opening this separate issue to ask if there is an alternatives for plugin developers and to share the limited workarounds I have discovered so far.
Have other plugin developers run into this problem, and how have you dealt with it?
I've had some limited success debugging by modifying jsdoc-x to use --inspect. Specifically, I added cmdArgs.unshift('--inspect'); after cmdArgs.unshift(file); in jsdoc-x/src/lib/helper.js.
I am using jest for testing. To get code coverage, I am using nyc (as suggested in https://github.com/facebook/jest/issues/3190#issuecomment-354758036) and have had some limited success there.
Both of these solutions require extra setup and do not have good IDE integration.
I've also done some unit tests that isolate the plugin and do not use jsdoc itself, but the primary difficulty with this is instead of providing JavaScript code with JSDoc comments for the test, I have to manually create mock AST objects. I'm interested in directly using babylon as a parser to get appropriate AST nodes and pass these to the plugin, but I haven't tried this yet.
Input code

Below is an example of a jsdoc plugin test using jsdoc-x.
const jsdocx = require('jsdoc-x');

function parseJsdoc(source) {
  return jsdocx.parse({
    plugins: ['index'],
    undocumented: false,
    source
  });
}

it('should do nothing for code with no mongoose schema', () => {
  return expect(parseJsdoc('const simple = true;')).resolves.toEqual([]);
});

describe('with mongoose.Schema', function() {
  it('should add class documentation', async () => {
    const results = await parseJsdoc(`const mongoose = require('mongoose');

/**
 * Blog post
 */
const BlogSchema = new mongoose.Schema({});`);

    expect(results[0]).toHaveProperty(
      'comment',
      `Blog post
@class Blog
@extends mongoose.Model`
    );
  });

  it('should add member documentation to schema path', async () => {
    const results = await parseJsdoc(`const mongoose = require('mongoose');

const BlogSchema = new mongoose.Schema({
  /**
   * Title of the blog post which will be used as the header.
   */
  title:  String
});`);

    expect(results[1]).toHaveProperty(
      'comment',
      `Title of the blog post which will be used as the header.
@memberof Blog#
@member {String} title`
    );
  });
});

Your environment

Software
Version

JSDoc
3.5.5

Node.js
10.3.0

npm
6.1.0

Operating system
macOS 10.11.6

I came up with another workaround using the parser from jsdoc. My initial attempt to just require jsdoc/lib/jsdoc/src/parser was not successful, but with some initialization and mocking I was able to get this working. See below or https://github.com/sgilroy/jsdoc-plugin-mongoose/blob/master/tests/unit/plugin-with-parser.js#L1-L104
This solution is rather complicated and fragile. Any suggestions for simplifying or improving would be appreciated, and of course changes to jsdoc to allow for simpler unit tests of plugins would be great.
const _ = require('lodash');
const plugin = require('../../index');

/*
jsdoc does not provide an API to use it programmatically. As a workaround, these tests initialize jsdoc and then
with the help of some mocking by jest, use the internal jsdoc parser to build and walk the AST to simulate what
jsdoc does and allow the plugin to be tested.
*/

// Note that in order for these jest.mock and require statements to succeed, we need NODE_PATH=./node_modules/jsdoc/lib
jest.mock('jsdoc/env');
const envMock = require('jsdoc/env');

// require in order to initialize jsdoc
require('jsdoc/jsdoc');

// override the mocked env.conf with the conf initialized in the global env from the above require
/*eslint no-undef: "off"*/
envMock.conf = env.conf;

const jsdocParser = require('jsdoc/lib/jsdoc/src/parser');

const parser = jsdocParser.createParser();
const sourceName = 'fake.js';

/**
 * Exercise the visitNode method of the plugin by treating the program function as if it were a file with JSDoc
 * commented code and then passing the specified node to the plugin's visitNode method.
 *
 * @param {Function} program Function with a body of JSDoc commented code to test
 * @param {String} nodePath Relative path to the AST node that should be visited, specified from the body of the program function
 * @return {Object} Event object that results from the plugin visiting the node
 */
function visitNode(program, nodePath) {
  const source = program.toString();
  const ast = parser._astBuilder.build(source, sourceName);
  let event = {};

  // find any existing jsdoc comment
  parser.on('jsdocCommentFound', _event => {
    event = _event;
  });

  // walk the AST to set the parent of each node
  parser._walkAst(ast, parser._visitor, sourceName);
  const node = _.get(ast, 'program.body[0].expression.body.' + nodePath);

  plugin.astNodeVisitor.visitNode(node, event);

  return event;
}

it('should do nothing for code with no mongoose schema', () => {
  const event = visitNode(() => {
    Math.abs(1);
  }, 'body[0]');
  expect(event).not.toHaveProperty('comment');
});

describe('with mongoose.Schema', function() {
  it('should add class documentation', async () => {
    const event = visitNode(() => {
      const mongoose = require('mongoose');

      /**
       * Blog post
       */
      const BlogSchema = new mongoose.Schema({});
      mongoose.model('Blog', BlogSchema);
    }, 'body[1].declarations[0]');

    expect(event).toHaveProperty(
      'comment',
      `Blog post
@class Blog
@extends mongoose.Model`
    );
  });

  it('should add member documentation to schema path', async () => {
    const event = visitNode(() => {
      const mongoose = require('mongoose');

      const BlogSchema = new mongoose.Schema({
        /**
         * Title of the blog post which will be used as the header.
         */
        title: String
      });
      mongoose.model('Blog', BlogSchema);
    }, 'body[1].declarations[0].init.arguments[0].properties[0]');

    expect(event).toHaveProperty(
      'comment',
      `Title of the blog post which will be used as the header.
@memberof Blog#
@member {String} title`
    );
  });
});

I had a similar issue and opted to use spawn from child_process to call the jsdoc cli via npx jsdoc and passed in the --explain (or -X) param to have JSON returned, and then parsed that.
const {spawn} = require('child_process');
const jsdoc = () => {
  return new Promise((resolve, reject) => {
    // using locally installed jsdoc
    const jsdoc = spawn('npx', [
      'jsdoc',
      // pass jsdoc cli options here
      '-c',
      'conf.json',
      '-X'
    ]);
    let output = '';
    let err = '';
    jsdoc.stdout.on('data', data => { output += data });
    jsdoc.stderr.on('data', data => { err += data });
    jsdoc.on('close', code => { code > 0 ? reject(err) : resolve(output) });
  });
};

I know this is a problem. Unfortunately, I think providing programmatic access to JSDoc is the right way to solve it. (I say "unfortunately" because that's not a quick and easy fix.)
Here's a disgusting hack trick that I've used to test a JSDoc template: Patch require() the same way that JSDoc does, then set up a minimal environment. Still fragile, admittedly.


Setup help.

I am sorry to have to ask for help, but I am new to React Native. React Native project apps do not use an index.html file. I was just wondering where everyone was creating and placing this file in their project folders. I am using Expo.

Run expo customize:web to generate index.html

Hello @cfchacon10 did it work for you in expo?
Because I am also using expo and I haven’t gotten around to making it work

I had to run npx expo customize, select web/index.html, press space, press enter to generate the file.
found this solution here


Parse issue with singleton-sets in hostset

I currently implement the commitment protocol parser by having the receivers be a set of hosts -- however this set can sometimes be a singleton. The parser currently crashes on singleton host sets:
-- PARSE ERROR ------------------------------------------------------------ m.vo

I ran into an issue while parsing this file.

2|     let tmp_4 = receive int from Commitment(receivers = {bob}, sender = alice);
                                                               ^
I was expecting one of these:

    IDENT, COMMA

Instead, I found:

    CLOSE_BRACE

We need to change the parser to allow for this

Addressed in #79


Apple Pay region

How can I set visibility for the regions? For example I don't wanna show it if it is not supported in that region? Thanks a lot

That's something that the userCanPay method can do for you, by returning false if Apple Pay is not available for a given user. Take a look at the advanced integration path, concretely the PayClient.userCanPay method, which lets you take action based on whether the payment provider in question is available or not.
In case you need additional context on how Apple Pay determines payment availability, userCanPay calls canMakePayments on the Apple Pay end.


robot_self_filter: 0.1.30-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository robot_self_filter to 0.1.30-0:

upstream repository: https://github.com/pr2/robot_self_filter.git
release repository: https://github.com/pr2-gbp/robot_self_filter-gbp.git
distro file: kinetic/distribution.yaml
bloom version: 0.5.23
previous version for package: null

robot_self_filter
* Fix typo in CMakeLists.txt: CATKIN-DEPENDS -> CATKIN_DEPENDS
* Add ~max_queue_size parameter for subscription queue size
* Contributors: Devon Ash, Kentaro Wada, Ryohei Ueda

Moved to https://github.com/ros/rosdistro/pull/13635


test_operator: more allowed list for tempests (glance, swift)

Follow the estabilished pattern and add more tests groups
for two additional operators, at least to cover the basic
API testing.

/approve

/cherry-pick 18.0.0-proposed


Enhancement, handle rejectUnauthorized as a parameter.

There will be use cases where the httpsAgent settings needed for a particular dependency check will differ from the bedrock defaults in bedrock-https-agent.  There should be a way to provide options to a custom httpsAgent.

Closing as stale.


calc_rmax: Should we compute the rolling average using absolute values?

@jdha we implemented this:
def rmax(dept):

    rmax_x = np.zeros_like(dept)
    rmax_y = np.zeros_like(dept)

    rmax_x[:,1:-1] = 0.5 * ( np.diff(dept[:,  :-1], axis=1) / (dept[:,  :-2] + dept[:, 1:-1]) +
                             np.diff(dept[:, 1:  ], axis=1) / (dept[:, 1:-1] + dept[:, 2:  ]) )
    rmax_y[1:-1,:] = 0.5 * ( np.diff(dept[ :-1, :], axis=0) / (dept[ :-2, :] + dept[1:-1, :]) +
                             np.diff(dept[1:  , :], axis=0) / (dept[1:-1, :] + dept[2:  , :]) )

    rmax = np.maximum(np.abs(rmax_x), np.abs(rmax_y))

    return rmax

Adjacent slopes on the same direction with opposite sign cancel/smooth each others.
Is that intended, or should we implement this?
def rmax(dept):

    rmax_x = np.zeros_like(dept)
    rmax_y = np.zeros_like(dept)

    rmax_x[:,1:-1] = 0.5 * ( np.abs(np.diff(dept[:,  :-1], axis=1)) / (dept[:,  :-2] + dept[:, 1:-1]) +
                             np.abs(np.diff(dept[:, 1:  ], axis=1)) / (dept[:, 1:-1] + dept[:, 2:  ]) )
    rmax_y[1:-1,:] = 0.5 * ( np.abs(np.diff(dept[ :-1, :], axis=0)) / (dept[ :-2, :] + dept[1:-1, :]) +
                             np.abs(np.diff(dept[1:  , :], axis=0)) / (dept[1:-1, :] + dept[2:  , :]) )

    rmax = np.maximum(rmax_x, rmax_y)

    return rmax

@malmans2 I see your point. The original function I recycled from old code was more for illustration and is technically corrected: if you look at the gradient between 2 neighbouring u points

with slopes on the same direction with opposite sign

the gradient will be zero. In reality rmax is only important on the u/v points, not t-points, so your solution is more practical (i.e. returning the maximum rmax values a particular cell has with any of its four neighbours).