GUI in headless mode shows local folders, not remote ones

Hi,
Whenever using the GUI on headless mode (a client in my laptop connecting to a headless server running 24/7), whenever I'm trying to add a plot, the GUI will show the local paths I can see in the laptop, not the remote ones the server sees. So I'm pretty sure if I attempt to create a plot in a local path that is not literally mapped exactly the same on the server, it will fail. The GUI should in this case show remote paths contents. Or, at the very least, allow to just manually type the path (at this moment, clicking on the path ALSO launches the file picker window).

I confirm this issue


Extract v gui

Convert the original extract_V notebook into a script file, so that it can be compiled into an standalone exe and run without any dependencies on virtual environment.

That's totally beyond my capability. Great work, Teris!


can you introduce your code ?

can you introduce your code more detail?

In progress. If you can't wait, I suggest you read the code.


Use babili instead of UglifyJS

https://github.com/babel/babili
I have no idea how UglifyJS or babili works under the hood, so I'm posting this to get responses from everyone. Shall we do it now? Or wait until it's more mature.

I believed that we kind of need to support older browser, as babili actually only minify es6 code without transpiling to es5.

transpilation to es5 is also handled by babel, so not sure this is an issue.

Going to be fixed with #925 (moving to user-land)

@MoOx how about https://github.com/babel/babel-preset-env
??

@marcelorl preser env is unrelated to this thread

@marcelorl we are already using this thing, and indeed, nothing to do with compression.

Closing as I won't to rely on something without having to think about it.


Gifting

this is mostly done in #421 but need to rebase that PR and then test / make sure it lines up with what we want to accomplish
Purpose
As a kind, benevolent individual I want to onboard my friends to mutiny via a gift.
Should just be available to mutiny+ users.
Frontend

[x] create gift
[x] redeem gift
[x] rebase
[x] show gifting link on send screen
[x] if not on mutiny+, explain that you need mutiny+
[x] update mutiny+ features list
[x] warn them if it's lower than 50k
[x] can delete a gift
[x] add qr scan link to main navbar

Backend

[x] functionality

Testing

[ ] not enough funds on sender
[ ] too small amount for receiver (if it's a fresh wallet)
[ ] trying to redeem twice
[ ] loading from url
[ ] loading from scanner

Do you think It's worth adding the qr-scanner to the AmountEditable Page as opposed to the homepage?

There's a lot of things a QR code scanner can do that are not related to creating an invoice, which is how you get to that amounts editable screen. LNURL pay/withdraw/auth being some of them.

Tested on firefox mobile web

Not enough funds on sender error only happens on the receiver side
below 50k sats shows a warning on sender and an error on receiver
scanner and url both work as expected

Nice work!


Accordion header closes  keybord when editing  TextInput

I have a TextInput on Accordion's header and can't continue typing on the keyboard, the keyboard closes immediately.
expo snack

@ramisalem I am also facing this issue but I have TextInput in the renderContent, every time I type the textInput its keyboard is dismissing
did you found any solution for this?

if you use a dynamic value as a key for mapping the collapsible component, React treats the new key as a new node, making the keyboard collapse.


Feature request: lock fields in Collecting Event editor

It would be helpful to control which fields are persisted and which ones aren't when cloning new CEs.
The ones that are currently hardcoded to copy are:

collector roles
georeferences
start + end date/time
elevation
all verbatim data

Exposing these as optional locks would be helpful as a starting point without changing functionality.

Additionally, data attributes and trip code namespace are not cloned, and the trip code identifier increment checkbox does not work.


Change vim_clear() to macro and rename to VIM_CLEAR()

And I completed the following TODO.

Use vim_clear() in more places, instead of vim_free() and assigning NULL.

Related comment in vim_dev ML.
https://groups.google.com/d/msg/vim_dev/JyOaLFF_zOo/MDYhz3DmAwAJ

Codecov Report

Merging #2629 into master will increase coverage by 0.01%.
The diff coverage is 67.81%.

@@            Coverage Diff             @@
##           master    #2629      +/-   ##
==========================================
+ Coverage   74.63%   74.65%   +0.01%
==========================================
  Files          92       92
  Lines      133133   132966     -167
==========================================
- Hits        99369    99263     -106
+ Misses      33764    33703      -61

Impacted Files
Coverage Δ

src/misc2.c
80.24% <ø> (-0.05%)
:arrow_down:

src/ex_cmds2.c
80.27% <ø> (-0.1%)
:arrow_down:

src/option.c
84.55% <0%> (+0.02%)
:arrow_up:

src/hardcopy.c
65.77% <0%> (+0.09%)
:arrow_up:

src/crypt.c
76.78% <0%> (+0.45%)
:arrow_up:

src/if_cscope.c
74.97% <0%> (+0.38%)
:arrow_up:

src/os_unix.c
54.52% <0%> (+0.14%)
:arrow_up:

src/ui.c
46.42% <0%> (+0.07%)
:arrow_up:

src/main.c
55.64% <0%> (+0.03%)
:arrow_up:

src/popupmnu.c
71.89% <0%> (+0.15%)
:arrow_up:

... and 45 more

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 7254067...2162fec. Read the comment docs.

I had already included the version with VIM_CLEAR().  Why did you go back to the function?

I had a misunderstanding. Sorry.


Cargo hangs at "Resolving dependency graph..."

Problem
Building the following project, the build process hangs at Resolving dependency graph...
Steps

Clone https://github.com/corepaper/morum/tree/f70f328621513dae95a4c8833878332be9211a4e
Run build, and it should work.
Uncomment line matrix-sdk = { version = "0.6", default-features = false, features = ["e2e-encryption", "sled", "rustls-tls"] } in Cargo.toml to add the dependency.
Cargo hangs at Resolving dependency graph...

Possible Solution(s)
No response
Notes
No response
Version
Tried both stable and nightly releases:
cargo 1.65.0 (4bc8f24d3 2022-10-20)
cargo 1.67.0-nightly (f6e737b1e 2022-12-02)

I suppose this is #4066 more or less. The resolver is running into conflicts, backing up and trying a different version, and then repeatedly failing. It could take hours or more for it to try all permutations.
@Eh2406 Is there anything to learn from this issue? Should it be closed in favor of #4066 (or #5284)?

Yes, my best guess is that the resolver is trying an extraordinary number of permutations without generalizing to see what the real problem is. Real-world examples are always interesting. When will I have time to follow up on this example, to see what properties make it slow? I don't know that I will make time for it, sorry.


Improved message for "Can't find merlin"; need message if bsc is not available

A couple suggestions:

The dialog should say the message is from the ReasonML plugin
There should be another message if bucklescript is not available
How about including a link that goes to instructions on how to install ocamlmerlin and bucklescript, (which could just be a file in github)?  (I suppose they need to be in the search path and nothing more, but nice to explain this a little more--less guessing.)

I have modified the github page today.

added
this message was present in older releases, but then it would appear in every projects, even prjoects that are not using reason or ocaml files. What I do now is that I display this message only if I find a bsconfig.json in the project and if bsb is not found (remember this is a reason plugin).
added a link to this github site

also I removed messages regarding Merlin.

For #2, how about making it depend on whether there are .ml files in the project?
I discovered the plugin because IntelliJ told me that there was a plugin for .ml files.  If the message doesn't appear without bsconfig.json, I might not know there was additional functionality that requires bucklescript.
From what I read, bucklescript installs an OCaml toolchain (which I already have).  Installing bucklescript requires npm.  You get npm by installing Node.js.  A lot of stuff just to get an IntelliJ plugin to work.  But not your doinq!
  From: Hervé Giraud<EMAIL_ADDRESS>
To: reasonml-editor/reasonml-idea-plugin<EMAIL_ADDRESS>Cc: Jim Fehrle<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Sent: Wednesday, December 20, 2017 3:17 PM
Subject: Re: [reasonml-editor/reasonml-idea-plugin] Improved message for "Can't find merlin"; need message if bsc is not available (#20)
I have modified the github page today.

added
this message was present in older releases, but then it would appear in every projects, even prjoects that are not using reason or ocaml files. What I do now is that I display this message only if I find a bsconfig.json in the project and if bsb is not found (remember this is a reason plugin).
added a link to this github site
also I removed messages regarding Merlin.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


scmi: Prepare v0.3.0 release

Update CHANGELOG.md and Cargo.toml for v0.3.0 release. This release adds SCMI notification support.
Summary of the PR
Let's make with a new release of vhost-device-scmi, with SCMI notification support.
Requirements
Before submitting your PR, please make sure you addressed the following
requirements:

[ x] All commits in this PR have Signed-Off-By trailers (with
git commit -s), and the commit message has max 60 characters for the
summary and max 75 characters for each description line.
[ x] All added/changed functionality has a corresponding unit/integration
test.
[ x] All added/changed public-facing functionality has entries in the "Upcoming
Release" section of CHANGELOG.md (if no such section exists, please create one).
[ x] Any newly added unsafe code is properly documented.

I can do the release when we will receive a second approval ;-)

crate published: https://crates.io/crates/vhost-device-scmi/0.3.0

Thanks!


Add T.one aqua air in FRIENDLY_NAMES

Fix issue display on HA, Add "TONE_AQUA_AIR" in const.py FRIENDLY_NAMES
Error while setting up aldes platform for binary_sensor Traceback (most recent call last):   File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 352, in _async_setup_platform     await asyncio.gather(*pending)   File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 533, in async_add_entities     await asyncio.gather(*tasks)   File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 640, in _async_add_entity     if self.config_entry and (device_info := entity.device_info):                                              ^^^^^^^^^^^^^^^^^^   File "/config/custom_components/aldes/binary_sensor.py", line 45, in device_info     name=f"{FRIENDLY_NAMES[self.reference]} {self.product_serial_number}",             ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^ KeyError: 'TONE_AQUA_AIR'

Thanks and sorry for the delay, I didn't get any notification.
Could you test v2.0.0 and confirm it's working for you?


Support more input types other than the Elasticsearch DSL queries

 Issue by dbbaughe
Friday May 03, 2019 at 16:24 GMT
Originally opened as https://github.com/opendistro-for-elasticsearch/alerting/issues/47

Our initial release supports just the Elasticsearch DSL queries.
We have started getting more requests for other input types or enhancements.
Cluster Health API: https://discuss.opendistrocommunity.dev/t/cluster-health-alert-monitors/606
Input Chaining: https://github.com/opendistro-for-elasticsearch/alerting/issues/43

 Comment by ShahNewazKhan
Friday May 03, 2019 at 17:17 GMT

Other use-cases also include indices api such as stats / segments / recovery / shard stores etc.


Dynamically loaded components do not get displayed

Components loaded with DynamicComponentLoader.loadNextToLocation are currently not getting included into batarangle.
Great work otherwise!

@amb-it-ion dynamically loaded components, with the exception for loadAsRoot components, should work fine with batarangle now with the latest update.

@amb-it-ion Do you think that this issue has been addressed?

This was fixed a long time ago

@clbond are you sure ?
For instance, I can't see dialogs created through @angular/material in the Augury inspector

This is not working again, due to Angular deprecating the DynamicComponentLoader. They now use the ComponentFactoryResolver.

This does not work anymore. Angular doesn't use DynamicComponentLoader anymore either, they use the ComponentFactoryResolver.

Hello lads. Sorry to disappoint you but Augury does not show MdDialogs. In the screenshot below I have an MdDialog with SessionsForm component. Wanted to debug it (displays incorrectly) but nope, not happening.

I am also experiencing this.


india map hotness weighted by area

Is your feature request related to a problem? Please describe.
Currently the indian map we show , is only colored on basis of total number of case in that area. a smaller area with more cases is more alarming than the other
Describe the solution you'd like
the indian map should be coloured statewise with respect to the area, of the state. you can normalise the color with respect to area of state and that may seem mode appropriate. also this can be added as an option to view.

I disagree on this request. The user is expecting to see the hotness based on the number of cases. However, we can add another country map in which the hotness can be weighted by area or by population or by population density.

I think this is an inherent limitation with Choropleth maps. We can normalize the colours based on a number of factors, but that won't solve it completely. I'm hoping that the recently added Hotspots view addresses this


A source repo should have a tag matching cookbook version

:+1:

the actual implementation may need to account for some common tag names that differ from the version numbers.  For example a tag of v0.3.3 should match a version of 0.3.3.
This implementation detail can be resolved when implementing this rule.
Otherwise, :+1:


Add a configurable peer limit

We should have a limit at which we stop adding new peers we see around. Kad bootstrap and dialing us should still work (latter except browsers), the limit should be soft.

This can be done very easily with connection_limits.


[Bug]: Create Failed - Instances failed to join the kubernetes cluster on both Managed Ondemand & System Node Groups

Installation method
Own AWS account
What happened?
Setup of the environment in own AWS Account times out with Create Failed - Instances failed to join the kubernetes cluster on both Managed Ondemand & System Node Groups
What did you expect to happen?
Setup was supposed launch required infra for the completing the workshop
How can we reproduce it?
Use cloud9 with terraform version Terraform v1.3.9 installed , I am role with administrator privilege attached to cloud9  and cloud9 setup as per the old EKS workshop. Once done run setup steps from new EKS Workshop.
Anything else we need to know?
Have used the EKS workshop supported regions
EKS version
1.23

Thanks for the report of this. So far I have not come across it happening and will need to investigate more to try to reproduce it.

This issue should no longer be applicable with the rearchitecture earlier this year, closing.


HTTPError: 403 Client Error: Forbidden for url

I followed steps in guide and when I ran src/examples/voice/assistant_library_demo.py it opened up browser for permission, it initialised credentials in cach directory and threw this exception.
Traceback (most recent call last):
  File "src/examples/voice/assistant_library_demo.py", line 73, in <module>
    main()
  File "src/examples/voice/assistant_library_demo.py", line 67, in main
    with Assistant(credentials) as assistant:
  File "/opt/aiy/projects-python/src/aiy/assistant/library.py", line 32, in __init__
    self._model_id = device_helpers.register_model_id(credentials)
  File "/opt/aiy/projects-python/src/aiy/assistant/device_helpers.py", line 93, in register_model_id
    r.raise_for_status()
  File "/home/pi/.local/lib/python3.5/site-packages/requests/models.py", line 928, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://embeddedassistant.googleapis.com/v1alpha2/projects/jarvis-133713/deviceModels/jarvis-133713-voice-kit

Workaround: Re-enable the Assistant API in the Cloud Console.

Did you use the same Google account to create the cloud project and to log in from the Raspberry Pi?
If not, you'll need to use the same account, or to make the account running on the Pi a project editor, so that it can register itself. You can add the editor rights here: https://console.cloud.google.com/iam-admin/iam.

Yes, I used the same account. I removed .cache directory and tried again. I got same error (as above) after following log line.
[2018-03-30 15:05:23,065] INFO:root:OAuth credentials initialized: /home/pi/.cache/voice-recognizer/assistant_credentials.json

I am getting the same error. In my case, I already set up voice recognition app in one google account and I want to change the account with another. I guess the problem is the consent step. It thinks it already have consent from previous account and send request but it has never consented.
My question is where is stores this consent. I guess it's my google account and I totally changed assistant.json.
Help me~~

@proppy Any idea what could be causing this?

can you confirm that account used to register the device is a viewer of the project where the device model was created?

@proppy, I asked "Did you use the same Google account to create the cloud project and to log in from the Raspberry Pi?" and @nickdex responded that they did. Presumably that would guarantee that the account is a project owner, right?

@drigz I would double check in the developer console for project jarvis-133713 just to be sure

Also it seems that the failure is on register_model_id, in order to be able to register a new model, you need to be a Owner or Editor of the project.

Same issue here. Same account to create & log in. Additionally cleared the cache & re-downloaded the credentials to no avail.

I've run into the same issue - same symptoms - but the problem was that, somehow the APIs and services got disabled - I'd swear I didn't do it, but with all the going back and forth, who knows? After I went through “Enable APIS and Services” again, it started to work. The only tweak I would do on the client side is to delete the credentials .cache directory.
I hope this helps.

@mihilie thank you for your input - seems I had the exact same issue. I'm not sure when or how the assistant API got disabled after I set it up, but it all works fine for me now. Didn't even need to clear the credentials. Hopefully this is the root of the problem for others in this thread.

Hi, have the same problem. switched accounts, checked if API is enabled and it is. but i don't seem to find how to delete the credentials cache .. i tried the command: # sync; echo 2 > /proc/sys/vm/drop_caches but doesn't seem to do anything. anyone any idea what to do ? i work as a freelancer on this project. the setup at my home was working, today i try to set everything up with the company credentials but won't work

Please make sure you can run this command using sudo. All credentials should be copied to the /root folder.

Hi Dmitri. Yes, my current command in rc.local looks like this:
sudo -H -u pi python3 assistant_library_with_local_commands_demo2.py &
I've tried to run it without -H and -user but get the same results.
What do you mean when you say "all credentials"? I've created a client ID through Google Cloud Platform and placed it in assistant.json at /root, is there another credential-file I'm missing?
I've even copied my working assistant.json from my user-folder to /root without success.

@Nojahhh Did you try to run your application manually on terminal on rootlevel? Did it work ?
Can you share what happens when you perform below steps:

sudo su
cp /home/pi/assistant.json /root
cp /home/pi/AIY-projects-python/src/examples/voice/assistant_library_with_local_commands_demo.py /root
cd /root
./assistant_library_with_local_commands_demo.py

I was able to run demo with above steps. Haven't tried it with rc.local yet.

@manoj7410 I tried your exact steps above to no avail. Any other suggestions? Thanks.


MDN annotations have ended up in scraped data

git grep -l ✔MDN in reffy-reports shows that a number of specs have MDN annotations in the scraped data. For example, ed/css/css-align.json looks like this:
{
  "spec": {
    "title": "CSS Box Alignment Module Level 3",
    "url": "https://drafts.csswg.org/css-align/"
  },
  "properties": {
    "✔MDN align-content In all current engines. Firefox28+Safari9+Chrome29+ Opera12.1+Edge79+ Edge (Legacy)12+IE11 Firefox for Android28+iOS Safari9+Chrome for Android29+Android WebView4.4+Samsung Internet2.0+Opera Mobile12.1+ align-content In all current engines. Firefox52+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android52+iOS Safari10.3+Chrome for Android52+Android WebView57+Samsung Internet6.2+Opera Mobile43+ align-content": {
      "name": "✔MDN align-content In all current engines. Firefox28+Safari9+Chrome29+ Opera12.1+Edge79+ Edge (Legacy)12+IE11 Firefox for Android28+iOS Safari9+Chrome for Android29+Android WebView4.4+Samsung Internet2.0+Opera Mobile12.1+ align-content In all current engines. Firefox52+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android52+iOS Safari10.3+Chrome for Android52+Android WebView57+Samsung Internet6.2+Opera Mobile43+ align-content",
      "value": "normal | <baseline-position> | <content-distribution> | <overflow-position>? <content-position>",
      "initial": "normal",
      "appliesTo": "block containers, multicol containers, flex containers, and grid containers",
      "inherited": "no",
      "percentages": "n/a",
      "computedValue": "specified keyword(s)",
      "canonicalOrder": "per grammar",
      "animationType": "discrete"
    },
    "✔MDN justify-content In all current engines. Firefox20+Safari9+Chrome52+ Opera12.1+Edge79+ Edge (Legacy)12+IE11 Firefox for Android20+iOS Safari9+Chrome for Android52+Android WebView52+Samsung Internet6.0+Opera Mobile12.1+ justify-content In all current engines. Firefox52+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android52+iOS Safari10.3+Chrome for Android52+Android WebView57+Samsung Internet6.2+Opera Mobile43+ justify-content": {
      "name": "✔MDN justify-content In all current engines. Firefox20+Safari9+Chrome52+ Opera12.1+Edge79+ Edge (Legacy)12+IE11 Firefox for Android20+iOS Safari9+Chrome for Android52+Android WebView52+Samsung Internet6.0+Opera Mobile12.1+ justify-content In all current engines. Firefox52+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android52+iOS Safari10.3+Chrome for Android52+Android WebView57+Samsung Internet6.2+Opera Mobile43+ justify-content",
      "value": "normal | <content-distribution> | <overflow-position>? [ <content-position> | left | right ]",
      "initial": "normal",
      "appliesTo": "multicol containers, flex containers, and grid containers",
      "inherited": "no",
      "percentages": "n/a",
      "computedValue": "specified keyword(s)",
      "canonicalOrder": "per grammar",
      "animationType": "discrete"
    },
    "✔MDN place-content In all current engines. Firefox45+Safari9+Chrome59+ Opera46+Edge79+ Edge (Legacy)NoneIENone Firefox for Android45+iOS Safari9+Chrome for Android59+Android WebView59+Samsung Internet7.0+Opera Mobile43+ place-content In all current engines. Firefox53+Safari11+Chrome59+ Opera46+Edge79+ Edge (Legacy)NoneIENone Firefox for Android53+iOS Safari11+Chrome for Android59+Android WebView59+Samsung Internet7.0+Opera Mobile43+ place-content": {
      "name": "✔MDN place-content In all current engines. Firefox45+Safari9+Chrome59+ Opera46+Edge79+ Edge (Legacy)NoneIENone Firefox for Android45+iOS Safari9+Chrome for Android59+Android WebView59+Samsung Internet7.0+Opera Mobile43+ place-content In all current engines. Firefox53+Safari11+Chrome59+ Opera46+Edge79+ Edge (Legacy)NoneIENone Firefox for Android53+iOS Safari11+Chrome for Android59+Android WebView59+Samsung Internet7.0+Opera Mobile43+ place-content",
      "value": "<'align-content'> <'justify-content'>?",
      "initial": "normal",
      "appliesTo": "block containers, flex containers, and grid containers",
      "inherited": "no",
      "percentages": "n/a",
      "computedValue": "see individual properties",
      "canonicalOrder": "per grammar",
      "animationType": "discrete"
    },
    "✔MDN justify-self In all current engines. Firefox45+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android45+iOS Safari10.3+Chrome for Android57+Android WebView57+Samsung Internet6.0+Opera Mobile43+ justify-self In all current engines. Firefox45+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android45+iOS Safari10.3+Chrome for Android57+Android WebView57+Samsung Internet6.0+Opera Mobile43+ justify-self": {
      "name": "✔MDN justify-self In all current engines. Firefox45+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android45+iOS Safari10.3+Chrome for Android57+Android WebView57+Samsung Internet6.0+Opera Mobile43+ justify-self In all current engines. Firefox45+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android45+iOS Safari10.3+Chrome for Android57+Android WebView57+Samsung Internet6.0+Opera Mobile43+ justify-self",
      "value": "auto | normal | stretch | <baseline-position> | <overflow-position>? [ <self-position> | left | right ]",
      "initial": "auto",
      "appliesTo": "block-level boxes, absolutely-positioned boxes, and grid items",
      "inherited": "no",
      "percentages": "n/a",
      "computedValue": "specified keyword(s)",
      "canonicalOrder": "per grammar",
      "animationType": "discrete"
    },
    "✔MDN align-self In all current engines. Firefox20+Safari9+Chrome36+ Opera12.1+Edge79+ Edge (Legacy)12+IE11 Firefox for Android20+iOS Safari9+Chrome for Android36+Android WebView37+Samsung Internet3.0+Opera Mobile12.1+ align-self In all current engines. Firefox52+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android52+iOS Safari10.3+Chrome for Android52+Android WebView57+Samsung Internet6.2+Opera Mobile43+ align-self": {
      "name": "✔MDN align-self In all current engines. Firefox20+Safari9+Chrome36+ Opera12.1+Edge79+ Edge (Legacy)12+IE11 Firefox for Android20+iOS Safari9+Chrome for Android36+Android WebView37+Samsung Internet3.0+Opera Mobile12.1+ align-self In all current engines. Firefox52+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android52+iOS Safari10.3+Chrome for Android52+Android WebView57+Samsung Internet6.2+Opera Mobile43+ align-self",
      "value": "auto | normal | stretch | <baseline-position> | <overflow-position>? <self-position>",
      "initial": "auto",
      "appliesTo": "flex items, grid items, and absolutely-positioned boxes",
      "inherited": "no",
      "percentages": "n/a",
      "computedValue": "specified keyword(s)",
      "canonicalOrder": "per grammar",
      "animationType": "discrete"
    },
    "place-self": {
      "name": "place-self",
      "value": "<'align-self'> <'justify-self'>?",
      "initial": "auto",
      "appliesTo": "block-level boxes, absolutely-positioned boxes, and grid items",
      "inherited": "no",
      "percentages": "n/a",
      "computedValue": "see individual properties",
      "canonicalOrder": "per grammar",
      "animationType": "discrete"
    },
    "✔MDN justify-items In all current engines. Firefox20+Safari9+Chrome52+ Opera12.1+Edge79+ Edge (Legacy)12+IE11 Firefox for Android20+iOS Safari9+Chrome for Android52+Android WebView52+Samsung Internet6.0+Opera Mobile12.1+ justify-items In all current engines. Firefox45+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android45+iOS Safari10.3+Chrome for Android57+Android WebView57+Samsung Internet6.0+Opera Mobile43+ justify-items": {
      "name": "✔MDN justify-items In all current engines. Firefox20+Safari9+Chrome52+ Opera12.1+Edge79+ Edge (Legacy)12+IE11 Firefox for Android20+iOS Safari9+Chrome for Android52+Android WebView52+Samsung Internet6.0+Opera Mobile12.1+ justify-items In all current engines. Firefox45+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android45+iOS Safari10.3+Chrome for Android57+Android WebView57+Samsung Internet6.0+Opera Mobile43+ justify-items",
      "value": "normal | stretch | <baseline-position> | <overflow-position>? [ <self-position> | left | right ] | legacy | legacy && [ left | right | center ]",
      "initial": "legacy",
      "appliesTo": "all elements",
      "inherited": "no",
      "percentages": "n/a",
      "computedValue": "specified keyword(s), except for legacy (see prose)",
      "canonicalOrder": "per grammar",
      "animationType": "discrete"
    },
    "✔MDN align-items In all current engines. Firefox20+Safari9+Chrome52+ Opera12.1+Edge79+ Edge (Legacy)12+IE11 Firefox for Android20+iOS Safari9+Chrome for Android52+Android WebView52+Samsung Internet6.0+Opera Mobile12.1+ align-items In all current engines. Firefox52+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android52+iOS Safari10.3+Chrome for Android52+Android WebView57+Samsung Internet6.2+Opera Mobile43+ align-items": {
      "name": "✔MDN align-items In all current engines. Firefox20+Safari9+Chrome52+ Opera12.1+Edge79+ Edge (Legacy)12+IE11 Firefox for Android20+iOS Safari9+Chrome for Android52+Android WebView52+Samsung Internet6.0+Opera Mobile12.1+ align-items In all current engines. Firefox52+Safari10.1+Chrome57+ Opera44+Edge79+ Edge (Legacy)16+IENone Firefox for Android52+iOS Safari10.3+Chrome for Android52+Android WebView57+Samsung Internet6.2+Opera Mobile43+ align-items",
      "value": "normal | stretch | <baseline-position> | [ <overflow-position>? <self-position> ]",
      "initial": "normal",
      "appliesTo": "all elements",
      "inherited": "no",
      "percentages": "n/a",
      "computedValue": "specified keyword(s)",
      "canonicalOrder": "per grammar",
      "animationType": "discrete"
    },
    "place-items": {
      "name": "place-items",
      "value": "<'align-items'> <'justify-items'>?",
      "initial": "see individual properties",
      "appliesTo": "all elements",
      "inherited": "no",
      "percentages": "n/a",
      "computedValue": "see individual properties",
      "canonicalOrder": "per grammar",
      "animationType": "discrete"
    },
    "⚠MDN row-gap In only one current engine. Firefox63+SafariNoneChromeNone OperaNoneEdgeNone Edge (Legacy)NoneIENone Firefox for Android63+iOS SafariNoneChrome for AndroidNoneAndroid WebViewNoneSamsung InternetNoneOpera MobileNone row-gap Firefox61+SafariNoneChrome66+ Opera53+Edge79+ Edge (Legacy)16+IENone Firefox for Android61+iOS SafariNoneChrome for Android66+Android WebView66+Samsung Internet9.0+Opera Mobile47+ row-gap": {
      "name": "⚠MDN row-gap In only one current engine. Firefox63+SafariNoneChromeNone OperaNoneEdgeNone Edge (Legacy)NoneIENone Firefox for Android63+iOS SafariNoneChrome for AndroidNoneAndroid WebViewNoneSamsung InternetNoneOpera MobileNone row-gap Firefox61+SafariNoneChrome66+ Opera53+Edge79+ Edge (Legacy)16+IENone Firefox for Android61+iOS SafariNoneChrome for Android66+Android WebView66+Samsung Internet9.0+Opera Mobile47+ row-gap",
      "value": "normal | <length-percentage>",
      "initial": "normal",
      "appliesTo": "multi-column containers, flex containers, grid containers",
      "inherited": "no",
      "percentages": "see § 8.3 Percentages In gap Properties",
      "computedValue": "specified keyword, else a computed <length-percentage> value",
      "canonicalOrder": "per grammar",
      "animationType": "by computed value type"
    },
    "column-gap": {
      "name": "column-gap",
      "value": "normal | <length-percentage>",
      "initial": "normal",
      "appliesTo": "multi-column containers, flex containers, grid containers",
      "inherited": "no",
      "percentages": "see § 8.3 Percentages In gap Properties",
      "computedValue": "specified keyword, else a computed <length-percentage> value",
      "canonicalOrder": "per grammar",
      "animationType": "by computed value type"
    },
    "⚠MDN gap In only one current engine. Firefox63+SafariNoneChromeNone OperaNoneEdgeNone Edge (Legacy)NoneIENone Firefox for Android63+iOS SafariNoneChrome for AndroidNoneAndroid WebViewNoneSamsung InternetNoneOpera MobileNone gap In all current engines. Firefox61+Safari12+Chrome66+ Opera53+Edge79+ Edge (Legacy)16+IENone Firefox for Android61+iOS Safari12+Chrome for Android66+Android WebView66+Samsung Internet9.0+Opera Mobile47+ gap Firefox61+SafariNoneChrome66+ Opera53+Edge79+ Edge (Legacy)16+IENone Firefox for Android61+iOS SafariNoneChrome for Android66+Android WebView66+Samsung Internet9.0+Opera Mobile47+ gap": {
      "name": "⚠MDN gap In only one current engine. Firefox63+SafariNoneChromeNone OperaNoneEdgeNone Edge (Legacy)NoneIENone Firefox for Android63+iOS SafariNoneChrome for AndroidNoneAndroid WebViewNoneSamsung InternetNoneOpera MobileNone gap In all current engines. Firefox61+Safari12+Chrome66+ Opera53+Edge79+ Edge (Legacy)16+IENone Firefox for Android61+iOS Safari12+Chrome for Android66+Android WebView66+Samsung Internet9.0+Opera Mobile47+ gap Firefox61+SafariNoneChrome66+ Opera53+Edge79+ Edge (Legacy)16+IENone Firefox for Android61+iOS SafariNoneChrome for Android66+Android WebView66+Samsung Internet9.0+Opera Mobile47+ gap",
      "value": "<'row-gap'> <'column-gap'>?",
      "initial": "see individual properties",
      "appliesTo": "multi-column containers, flex containers, grid containers",
      "inherited": "no",
      "percentages": "refer to corresponding dimension of the content area",
      "computedValue": "see individual properties",
      "canonicalOrder": "per grammar",
      "animationType": "by computed value type"
    }
  },
  "descriptors": {},
  "valuespaces": {
    "<self-position>": {
      "value": "center | start | end | self-start | self-end | flex-start | flex-end"
    },
    "<content-position>": {
      "value": "center | start | end | flex-start | flex-end"
    },
    "<baseline-position>": {
      "value": "[ first | last ]? baseline"
    },
    "<content-distribution>": {
      "value": "space-between | space-around | space-evenly | stretch"
    },
    "<overflow-position>": {
      "value": "unsafe | safe"
    }
  }
}

It looks like the <aside class="mdn-anno wrapped"> in https://drafts.csswg.org/css-align/ will have to be removed to solve this.
@dontcallmedom @tidoust @tabatkins

Looks like this was a recent regression, the first of these came in https://github.com/tidoust/reffy-reports/commit/4cd3ad967b7d9a167a3cdd8370ec896ce4fb9aec on Jun 26, and it wasn't because of a change in Reffy.

This issue doesn't appear to have been resolved.  Parsing https://drafts.csswg.org/css-transforms-2/ still include MDN annotations in the extracted CSS definitions.
This is due to the fact that the annotations are not contained in aside elements.  This may have changed since #355 landed.  The following line should likely be changed to match the mdn-anno class.
const annotations = cleanedLine.querySelectorAll(".mdn-anno");

https://github.com/tidoust/reffy/blob/master/src/browserlib/extract-cssdfn.js#L52-L61

@pyoor I can't reproduce the problem - I'm assuming you're using the CLI script in src/cli/extract-cssdfn.js on https://drafts.csswg.org/css-transforms-2/ (since the automatically extracted data on webref only deals with transforms-1 at the moment) - when I do that, I don't see any MDN annotations in the extracted definitions:
{
  "properties": {
    "translate": {
      "name": "translate",
      "value": "none | <length-percentage> [ <length-percentage> <length>? ]?",
      "initial": "none",
      "appliesTo": "transformable elements",
      "inherited": "no",
      "percentages": "relative to the width of the containing block (for the first value) or the height (for the second value)",
      "computedValue": "the keyword none or a pair of computed <length-percentage> values and optionally an absolute length",
      "canonicalOrder": "per grammar",
      "animationType": "by computed value, adding a third 0 value if needed to match components, but see below for none"
    },
    "rotate": {
      "name": "rotate",
      "value": "none | <angle> | [ x | y | z | <number>{3} ] && <angle>",
      "initial": "none",
      "appliesTo": "transformable elements",
      "inherited": "no",
      "percentages": "n/a",
      "computedValue": "the keyword none, or an <angle> with an optional axis consisting of a list of three <number>s",
      "canonicalOrder": "per grammar",
      "animationType": "as SLERP, but see below for none"
    },
    "scale": {
      "name": "scale",
      "value": "none | <number>{1,3}",
      "initial": "none",
      "appliesTo": "transformable elements",
      "inherited": "no",
      "percentages": "n/a",
      "computedValue": "the keyword none, or a list of 2 or 3 <number>s",
      "canonicalOrder": "per grammar",
      "animationType": "by computed value, but see below for none"
    },
    "transform-style": {
      "name": "transform-style",
      "value": "auto | flat | preserve-3d",
      "initial": "auto",
      "appliesTo": "transformable elements",
      "inherited": "no",
      "percentages": "N/A",
      "computedValue": "specified keyword",
      "canonicalOrder": "per grammar",
      "animationType": "discrete"
    },
    "perspective": {
      "name": "perspective",
      "value": "none | <length>",
      "initial": "none",
      "appliesTo": "transformable elements",
      "inherited": "no",
      "percentages": "N/A",
      "computedValue": "the keyword none or an absolute length",
      "canonicalOrder": "per grammar",
      "animationType": "by computed value"
    },
    "perspective-origin": {
      "name": "perspective-origin",
      "value": "<position>",
      "initial": "50% 50%",
      "appliesTo": "transformable elements",
      "inherited": "no",
      "percentages": "refer to the size of the reference box",
      "computedValue": "see background-position",
      "canonicalOrder": "per grammar",
      "animationType": "by computed value"
    },
    "backface-visibility": {
      "name": "backface-visibility",
      "value": "visible | hidden",
      "initial": "visible",
      "appliesTo": "transformable elements",
      "inherited": "no",
      "percentages": "N/A",
      "computedValue": "specified keyword",
      "canonicalOrder": "per grammar",
      "animationType": "discrete"
    }
  },
  "descriptors": {},
  "valuespaces": {
    "<matrix3d()>": {
      "value": "matrix3d( <number> [, <number> ]{15,15} )"
    },
    "<translate3d()>": {
      "value": "translate3d( <length-percentage> , <length-percentage> , <length> )"
    },
    "<translateZ()>": {
      "value": "translateZ( <length> )"
    },
    "<scale3d()>": {
      "value": "scale3d( <number> , <number>, <number> )"
    },
    "<scaleZ()>": {
      "value": "scaleZ( <number> )"
    },
    "<rotate3d()>": {
      "value": "rotate3d( <number> , <number> , <number> , [ <angle> | <zero> ] )"
    },
    "<rotateX()>": {
      "value": "rotateX( [ <angle> | <zero> ] )"
    },
    "<rotateY()>": {
      "value": "rotateY( [ <angle> | <zero> ] )"
    },
    "<rotateZ()>": {
      "value": "rotateZ( [ <angle> | <zero> ] )"
    },
    "<perspective()>": {
      "value": "perspective( <length> )"
    }
  }
}

Behavior may be transient in that these annotations are probably generated asynchronously, and thus may or may not be present when the extraction runs. I get the problem on one of the properties of CSS Transforms 2 when I run things locally. Also, it appears in other spesc as well, such as in the CSS extract for CSS Text Module Level 3

Reopening as git grep -l ✔MDN still finds the annotations in some files:
ed/crawl.json
ed/css/css-align.json
ed/css/css-flexbox.json
ed/css/css-fonts.json
ed/css/css-lists.json
ed/css/css-logical.json
ed/css/css-overflow.json
ed/css/css-position.json
ed/css/css-text.json
ed/css/mediaqueries.json


Make links and #streams clickable in messages.

Fix:#638

Thanks for catching and fixing the bug that I introduced in the render refactoring.


Plans to incorporate the WASI spec?

Do you have any plans on building a version to target wasm32-wasi? There is some interest in the Twitter WebAssembly community in running PHP in Spin or other server-side platforms

Can you provide some more info on WASI?

Hey @seanmorris sorry to necrobump this (a new issue/discussion is also fine!) but some more info on WASI, just in case you need it :)
WASI main page
The Component Model book which does more explaining at a high level (works with but not required for WASI support)
WebAssembly Interface Types
WASI repo
WASI Preview 2 interfaces (Example wasi:filesystem/types#descriptor.read reading from a file descriptor)
As a sort of quick explanation, WASI serves as an embedding for standardized system functionality that works outside the browser (and *inside* it too).


ModuleNotFoundError while importing MarketplaceApp

from marketplace.app import MarketPlaceApp
Error message:
ModuleNotFoundError: No module named 'utils' ```

**correction hint:** check  `from utils import camel_to_snake` inside marketplace/app/__init__.py

Thanks for reporting, looking into it now.

@drvgautam The bug should now be fixed in version 0.3.1: https://pypi.org/project/marketplace-sdk/0.3.1/

@csadorf  thanks for fixing the issue.


Multi-Acc-Support.

Need multi-account-support.

Hi we usually charge for custom feature requests and we fix the issues with the current free features of the software that we provide. We do accept some new feature suggestions (ones from discord server), and this is the one of the things that will be added in the future update. Soon we will update all of the projects to newer versions adding some new features (in this particular project that feature) and more exciting things to other projects including one new project release, if you like our work and want to support it leave star on this repository so other people find it more easily !


Using mem with many-keys-map

Hello @fregante, I noticed that you are a maintainer of mem and also the owner of many-keys-map. Is there an easy way to create a memoized version of a function with multiple arguments by internally using your many-keys-map as a cache keeper? Thanks!

Yes, I think you need this:
mem(fn, {
  cache: new ManyKeysMap(),
  cacheKey: args => args
});

Thanks for the fast response, I will try it out later, and if I have trouble I will post here.

@fregante If it works, this would be a good tip for the readme.

Done in https://github.com/sindresorhus/mem/pull/55


Remove nginx from builder

Because we split building image to separated tag, how about to remove parts not needed there? Nginx is the first.

I'll consider over the next few days it but unless there proof it has an impact on performance it's probably gonna stand at a hard no because it provides more benefit there than it does on it's own tag.

I actually read this ticket wrong.  I thought it said all images but I re-read it.

It seems something rely on nginx:
$ docker run -it jekyll/jekyll:builder /bin/sh
/srv/jekyll # ./run: exec: line 11: nginx: not found
./run: exec: line 11: nginx: not found
./run: exec: line 11: nginx: not found
./run: exec: line 11: nginx: not found
./run: exec: line 11: nginx: not found


Add the ability to only show merge commits

If you use a pull request workflow its useful to create a changelog with only merge commits.

Thank you for the contribution! :+1:
What do you think the behavior should be if someone specifies include_merges: false and only_merges: true?

@mfurtak  Could we introduce a merge_behaviour property ?

merge_behaviour: :merges_only
merge_behaviour: :ignore_merges
merge_behaviour: :include_merges

If people set the old property to true we could make it set the merge behavior to include_merges until we remove it.

I think that's a great idea @jcampbell05 :+1: I'd love to see a new option with three possible values:

merge_commit_filtering: :include_merges [default]
merge_commit_filtering: :exclude_merges
merge_commit_filtering: :only_include_merges

Setting include_merges: false should mean merge_commit_filtering: :exclude_merges
Would that work for you, @tabuchid?

Works for me. I think thats clearer then multiple options.
FYI I just tried this with git git log --merges --no-merges and it is a noop.

Cool. Would you like to adapt this in that way, @tabuchid?

@mfurtak How does that look? Forgive my ruby, I haven't worked much in it.

@tabuchid I think that's pretty good! :+1: I added onto it a bit with #1152. Please let me know if that still works for your needs and we can get it in!


fix(automerge): Fix storage adaptor

Motivation / Background

This Pull Request ...
Details

Additional information

Current dependencies on/for this PR:

main

PR #5369   👈

This stack of pull requests is managed by Graphite.


ThrottlingException when calling the DescribeExecution operation

If multiple files are written to a MESH outbound bucket in quick succession, we see these errors in in mesh_check_send_parameters, specifically from where it calls sfn.describe_execution(executionArn=execution_arn)):
{
  "errorMessage": "An error occurred (ThrottlingException) when calling the DescribeExecution operation (reached max retries: 4): Rate exceeded",
  "errorType": "ClientError",
  "requestId": "62ed8b47-518d-4db5-8b45-82e1b9670d9c",
  "stackTrace": [
    "  File \"/var/task/mesh_check_send_parameters_application.py\", line 116, in lambda_handler\n    return app.main(event, context)\n",
    "  File \"/opt/python/spine_aws_common/lambda_application.py\", line 74, in main\n    raise e\n",
    "  File \"/opt/python/spine_aws_common/lambda_application.py\", line 57, in main\n    self.start()\n",
    "  File \"/var/task/mesh_check_send_parameters_application.py\", line 58, in start\n    singleton_check(\n",
    "  File \"/var/task/shared/common.py\", line 67, in singleton_check\n    ex_response = sfn.describe_execution(executionArn=execution_arn)\n",
    "  File \"/opt/python/botocore/client.py\", line 553, in _api_call\n    return self._make_api_call(operation_name, kwargs)\n",
    "  File \"/opt/python/botocore/client.py\", line 1009, in _make_api_call\n    raise error_class(parsed_response, operation_name)\n"
  ]
}

This is _presumably because multiple EventBridge rules fired at the same time and trigger multiple concurrent Step Function invocations.
Suggestion from @matt-mercer that this should maybe handled tactically with a backoff/retry but strategically by replacing the API call with a lookup to a lock table in Dynamo DB (apologies if I'm misrepresenting what you said Matt :-D).

Picking up this ticket


relabel: move tests to separate package

Move relabel package tests to a separate package relabel_test. Also rename the tests to clearly indicate what they are testing and benchmarking

please review @machine424

The renaming seems to make sense.
But what's the motivation for moving the tests into a separate package? I know the pattern exists, and some advocate it because it forces tests to only use exported parts of the package to test. But it also adds some friction, so I think there should be some motivation beyond "just follow the pattern". AFAIK we don't regularly use the pattern in the Prometheus codebase. Cases that come to mind have to do with avoiding circular package dependencies.
@machine424 maybe you have discussed this with @tesla59 in advance?

@beorn7 The motivation comes for this PR https://github.com/prometheus/prometheus/pull/13999
Because promql is following the _test I thought it can be extended to other part as well

#13999 introduced the promql_test package to avoid a circular dependency between packages. We should not take it as a reason to now move all tests to their separate ..._test package.
I mean, maybe we want that, but then it should be an informed decision taken by the team. For now, I would assume the current state is the desired one and not change it.

Thank you for your initiatives and efforts, @tesla59.
I agree with @beorn7, I don’t think moving the tests into promql_test is necessary here.
Regarding the renaming, unless it’s really needed (the test was changed dramatically), I lean towards not changing the names to avoid losing the test’s history. If the test becomes flaky or something, we can look in the issues to check if we had that before, we can easily find threads related to it in Slack, etc. The same goes for benchmarks, we can still compare the results with the previous runs, etc.
Also, you can always start discussions on Stack or here to test the waters before opening a PR. We can also have discussions on the PRs themselves though, as you like. ;)

@machine424 made a good point about not renaming tests unless there is a very compelling reason.
So let's close this PR. @tesla59, this is of course not meant to discourage you from further contributions.


Cannot attach to process when using gdb local debugger

I am trying to use the debugger to analyze a binary. I am getting strange behavior.
First of all, when I try to target localhost:12345, remote debugging appears to start up fine. However, I get the following message:
"Can't determine the current process's PID: you must name one."
I then try to attach to the process. When I do this, I get the following error:
"Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
Warning: process <###> is a zombie - the process has already terminated
ptrace: operation not permitted
I have changed the ptrace_scope file appropriately. However, it still does not work. Additionally, when I try to attach, it terminates the process so I can no longer debug.
The other strange behavior I am seeing is dealing with inconsistent behavior. When I try to debug (without attaching to the process), sometimes the threads/register windows will populate and other times they do not.
Essentially gdb provides no useful information. If I step through, it steps, but I can't see the instruction that was executed. It just tells me the address I'm currently at as I step.  It doesn't do the normal gdb thing and tell me what instruction it is at or highlight the line in the listing window.
Any ideas? Have you observed this behavior?

I'm having trouble discerning how much of this deals with getting GDB to connect to your target vs getting Ghidra to talk to GDB. It might help if you share the commands you're typing (I presume into the GDB Interpreter window presented by Ghdira), and also how you're launching the target to which you're trying to attach. Are you using gdbserver?
As far as the threads/registers windows populating. The reasons could vary. In order for those windows to populate, you have to "Record" the target into a Ghidra trace file. ATM, Ghidra can only record x86 and ARM targets. Sometimes, due to a timing issue we've been working out, the recording is not automatically started. Navigate to "Inferiors[1]" in the "Objects" window and try selecting "Record" from its toolbar drop-down menu. If the "Threads" window populates, but not the "Registers," try selecting a thread.
For disassembly listings, ensure the "Dynamic Listing" window is visible ("Debugger" menu). The usual (static) "Listing" window is only populated when Ghidra recognizes the target's modules from the set of currently opened/imported program images. You can try navigating to "Inferiors[1].Modules..." in the "Objects" window to see if GDB is able to list your target's modules. Or type maint info sections ALLOBJ into the Interpreter. Those should be populated into the "Modules" window, allowing Ghidra to recognize and map them to your open/imported programs. Having that module mapping produces the best user experience.

I wonder if it is because I have a PPC target.
Currently, I am doing the following commands:

qemu-ppc -g 12345 <bin_name>
Launch up the binary in the debugger in Ghidra.
Go to connect the debugger using IN-VM GNU gdb local debugger
In the gdb interpreter in Ghidra: Set the architecture and endianness.
In the gdb interpret: target remote localhost:12345

After this step, I see the message that the current process's PID cannot be determined. I then try to attach to the qemu-ppc process and everything dies.

Hi Morgan,
Sound like you are doing the right things, but, yes, ppc will stop the debugger in its tracks right now.  I've added a new file that should help you out - GdbPowerPCDebuggerMappingOpinion - probably take a day or two before it makes it into the repo.  Once it's there, however, we would love to have you test it out!   Will keep you posted.
Best,
D

Thanks, that sounds great!

GdbPowerPCDebuggerMappingOpinion added.


Update generateCSVString

Update generateCSVString function to create a csv containing subject-level data returned from the API.

Blocked by https://github.com/neurobagel/api/issues/102


Fix #110 - issue with beSupersetOf when compare mutable and immutable co...

[subset isKindOfClass:[actual class]] method doesn't work in cases of when we compare mutable and immutable collection, e.g. NSMutableArray and NSArray.
NSMutableArray is implemented in its subclass __NSArrayM and NSArray is implemented in its subclass __NSArrayI.
In this case isKindOfClass will return NO, because __NSArrayM is subclass of NSArray but not of __NSArrayI.

Thanks a lot @chipp - Any chance we can get a unit test added to prove that it works? :dancers:

It's looks like someone excluded EXPMatchers_beSupersetOfTest.m from test targets, I've added it back and added tests for mutable and immutable collections comparison.

nice! Thanks


How to add a new body to a chain !??

The chain function is for construction only, so you'll need to handle that in your own way by adding a new constraint to the chain composite. Check out the source for Composites.chain which should give you an idea on how.


[5.7] allow use of warnings-as-errors while dependencies have supressed warnings

5.7 cherry pick of #5612

@swift-ci smoke test


What's the meaning of the following sentence of GettingStarted

Please do not submit this issue.
I don't know the meaning of Babel will not verify the types.
I think it's enough to transpile typescript to es5 for jest.
What's the advantage of using ts-jest over babel-jest?
Thank you!
While babel-jest by default will transpile TypeScript files, Babel will not verify the types. If you want that you can use ts-jest.
https://jestjs.io/docs/next/code-transformation#writing-custom-transformers:~:text=While babel-jest by default will transpile TypeScript files%2C Babel will not verify the types. If you want that you can use ts-jest.

[X] I understand

ts-jest is passing the TS files though tsc programmatically. Just like tsc it will show type errors.
babel-jest does not use the TS Compiler API, hence it "will not verify the types" or show anytime errors. This means some performance gain, but tests will not be type checked. In the same document you can find a suggestion to run tsc separately.

@mrazauskas Thanks for your reply!
I really appreciate it.


Reduce container size

Some dependencies are massive, e.g. FreeSurfer / FSL, yet only a fraction of their functionality are requisite for the operation of this specific tool.
Stripping away all unused data / functionalities from these softwares within the container recipes could drastically reduce the size of the final container files.

Use similar process to that of MRtrix3/containers:#2.

This may need to be prioritised not only for the sake of reducing container size, but also because CI is no longer able to complete due to MRtrix3 compilation taking too long.


tests: drivers: can: timing: test that calculated timings can be set

This patch set adds the following CAN timing test cases:

tests: drivers: can: timing: test that calculated timings can be set
tests: drivers: can: timing: test min/max timing can be set

The addition of these test cases revealed a few bugs, for which fixes are included:

drivers: can: mcan: allow sjw == CAN_SJW_NO_CHANGE (Fixes: #44482)
drivers: can: mcan: fix bounds check for data phase prescaler (Fixes: #44483)
drivers: can: mcp2515: correct min/max timing values (Fixes: #44484)

Furthermore, the handler for can_set_timing() is changes to validate all parameters and copy them before calling the implementation.
The tested sample point locations for bitrates >= 800kbit/s have been modified to match those uses in the Linux kernel CAN layer as these seem to be much more likely to be met with 100% accuracy by a wide range of CAN controllers. I will follow up with a PR for changing the default sample point locations used by can_set_bitrate().

Thanks for catching those mcp2515 off by one (bit) errors....

Welcome.

Was this marked draft by purpose? Looks small and self contained enough to be good enough as is?

Yes, it was converted to draft on purpose. I needed to get a minor change in. It is ready for review now.

Rebased to fix an issue with passing non-NULL timing_data_copy even if user passed NULL timing_data.

@karstenkoenig Please re-review.


[4.0] Treat irrefutable casts as irrefutable patterns.

Explanation: Treat irrefutable casts as irrefutable patterns
Scope: Limited.  Silences what were spurious warnings.
Radar/SR: Reported
Risk: Low
Testing: Regression tests included in patch
This is a cherry-pick of #9449 and #9464.

@swift-ci test

@jrose-apple mind one more review for 4.0?

Looks good to me, but at this point a manager should probably look at it too.

@swift-ci test source compatibility

Unexpected pass by Sourcery?

@swift-ci test source compatibility

I'm reviewing the expected failures.

@swift-ci test source compatibility

There we go.
Over to you @tkremenek


Fix exception when an int32 value comes from the json

Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[ ] C++ Guidelines
[ ] Doxygen docs
[ ] Unit tests
[ ] No unwanted commits/changes
[ ] Descriptive title/description

[ ] PR is single purpose
[ ] Related issue listed

[ ] Comments in source
[ ] No typos
[ ] Update changelog
[ ] Not work-in-progress
[ ] External references or docs updated
[x] Self review of PR done
[ ] Any breaking changes?

@ahsonkhan This is to address the issue

If macoslatest CI pipeline for your PR is broken due to abseil package, please merge the latest main into your branch, it was fixed in 22f5135d4c4b6110079863c610d38a9a1e2b6c5b.

@0xar1

Can you please reply to the contributor license comment so we can merge the change ? I added some more unit tests including one to cover the new code.
Thank you,
George Arama

@microsoft-github-policy-service agree

@0xar1

Can you please reply to the contributor license comment so we can merge the change ? I added some more unit tests including one to cover the new code.
Thank you, George Arama

You can merge now..
Thanks,
Arwell

/azp run checkenforcer

/azp run cpp - tables

@0xar1 Thank you for your contribution, the change has been merged and will be part of the next release of the package.


Follow up ticket for v3 release

This issue is meant to keep track of V3 alpha release issues
CC @fzipi @piyushroshan @anuraaga @bxlxx @jcchavezs
Tasks

[x] Variable engine rework (90%)

pending key case fix by @piyushroshan

[ ] API refactor (90%)

Pending moving a few functions to internal and validating if we keep tx context
Moving tx metadata to types

[ ] Response body processor (50%)

Pieces are programmed, but there are some pending tests and connections

[ ] Persistence (20%)

might be pushed to v3.1.0

[ ] Refactor core interfaces for plugins (90%)

Some other types must be moved to types

[x] 100% CRS compatibility
[ ] Implement custom dynamic variables (TIME, ENV, etc): 0%
[x] Tinygo and WASM compatibility
[x] Remove zap and create logging interface
[x] Performance optimization
[ ] Create benchmarks between v2 and v3
[ ] Rework the rule error log mechanism
[x] Expose Directive plugins api
[ ] Update documentation for coraza.io (30%)
[ ] Add more tests for rule exceptions (example: Wordpress exceptions for CRS)

High-Level breaking changes

waf.NewTransaction now receives a Context
seclang.NewParser will stop returning an error
tx.Collections now returns Collection objects. Raw data is not available anymore. Variables can be retrieved from tx.Variables.RemoteAddr

Milestone dates (Expected)

09/09/2022: Tag v3.0.0-alpha.1
09/09/2022: Add repository rules to v3/dev: 1 approver
09/09/2022: Replace v2/master with v3/dev as the default branch
14/10/2022: Tag v3.0.0-rc.1
14/10/2022: Add repository rules to v3/dev: 2 approvers
14/10/2022: Rename the v3/dev branch to v3/main and v2/master to v2/main
18/11/2022: v3.0.0 stable release

If we go with current API, I think the proposed schedule makes sense. But if decide to go with #371, it will be a big change, and we may lump in other similar API changes at this chance. So if going with it, I believe we need 1 extra month, but no more. That would push back e.g., v3.0.0-alpha.1 to 07/10/2002.  If not, let's stick to simple renames and the proposed schedule.

Preparing a Changelog for v3 https://github.com/corazawaf/coraza/pull/538

Do we know what is needed for the body processors mentioned here?

This issue is linked on the very top of the website. This does not look good. Please reopen and give a status update or stop linking to this.

Closed as v3 is out.


[modify] schedule: show resource error

Coverage: 82.912% (-0.02%) from 82.932% when pulling eb670e9f747bbe35c5c4206d0c5997269f4b38c3 on pr-schedule-onerror into b4200b11083c056c0fd12d305dacf133765e24b1 on master.


Fixed flag checking for lexical borrow scopes.

Previously the following pairs were prohibited incorrectly:

-enable-lexical-borrow-scopes=true, -enable-experimental-move-only
-enable-lexical-lifetimes=true, -enable-experimental-move-only
and the following pairs were allowed incorrectly:
-enable-lexical-borrow-scopes=false, -enable-experimental-move-only
-enable-lexical-lifetimes=false, -enable-experimental-move-only
Here, that's fixed.  The first two pairs are allowed and the second two pairs prohibited.

@swift-ci please smoke test and merge


3.8.2 An error occurred in the console after upgrading

Environment
nuxt 3.8.2
Reproduction

Describe the bug
3.8.1 Error after upgrading to 3.8.2
Additional context
No response
Logs
No response

did you use
npx nuxi upgrade --force

to upgrade?

Yes, I used it again

Is it because of this?
I don't know how to modify this

Wait, I just used npx nuxi upgrade --force
Reopen VScode and restart the project. The error seems to have disappeared.

I will close issues first and continue to observe


License and support for ngx-formly

Hi,
We are planning to develop new software and we are in the process of evaluating the ngx-formly to use in .   If we use ngx-formly in my project, does ngx-formly team provide any documentation and support if required in future?

of course, you can contact me in private or if you're looking for better consulting/teaching you may check with @juristr!


add delegated auth handler

This is the 2.x version of https://github.com/apache/couchdb/pull/366
Goes with:

https://github.com/apache/couchdb-couch/pull/132
https://github.com/apache/couchdb/pull/373


Proposal: Rename cuda-cccl-impl to cccl.

Background
Recently, CCCL has migrated to a new unified repo (https://github.com/NVIDIA/cccl). This is now the official home for Thrust/CUB/libcudacxx, and those libraries will be packaged/shipped as a single entity ("CCCL") from CCCL version 2.2.0 onwards. The first release (2.2.0) and compatibility policies for CCCL are being formalized by @jrhemstad right now. From recent conversations around the CCCL 2.2.0 release, it is likely that most users will want to refer to CCCL by its versions (e.g. 2.1.0) rather than by the CUDA Toolkit (CTK) versions (e.g. 12.0.90) that shipped that CCCL version (i.e. cuda-cccl-impl versions, not cuda-cccl versions, in the present naming scheme). There is interest from CCCL maintainers/developers and users (including myself) to make this package, currently named cuda-cccl-impl, into the official conda-forge package for users to find and install CCCL. However, the current name cuda-cccl-impl is unclear and implies that this package is an "implementation" or otherwise contains internals and isn't meant to be the front door for CCCL users.
Proposal
Proposal: rename cuda-cccl-impl (this feedstock/package) to cccl.
Going forward, this package is intended to be a user-friendly way to install and use CCCL in a conda environment. The current name doesn't make it sound that way, and renaming to cccl would help.
The existing double-versioning scheme where cuda-cccl (versioned like the CTK) depends on cuda-cccl-impl (versioned like CCCL) is still useful per the original design (previously discussed with most of those cc'd below), and cuda-cccl would need to be updated to depend on the new name cccl. Currently this should be easy to do, since only one version of cuda-cccl and cuda-cccl-impl exist on conda-forge.
Additionally, this proposal would not introduce any conflicts with the nvidia channel CTK packages. No packages named cccl exist on any channel today. https://anaconda.org/search?q=cccl
Releases
I also propose a clarification of the versioning policies / release schedules that would be used by this package, which corresponds to the new monorepo and drafts about release policies for that repo. The cccl package would be tied to the releases at https://github.com/NVIDIA/cccl. New tags of that repo would result in new releases of cccl, even if that CCCL version has not been incorporated into a CTK release yet. This is aligned with the current practice of pulling cuda-cccl-impl files from the Thrust/CUB/libcudacxx repos, while the "target platform" packages (see below) are made from the CUDA Toolkit package tarballs.
The key results for users would be:

Users desiring the latest CCCL should install cccl

This is aligned with the CCCL guidance to "live at head", i.e. use the latest versions available

Users desiring a specific CCCL version X.Y.Z should install cccl=X.Y.Z
Users desiring a CCCL that was released with CUDA Toolkit version X.Y should install cuda-cccl=X.Y.*

CUDA >= 12.0 only, no backports are planned at this time

Alternatives
Alternative 1: cuda-cccl-impl could be just a metapackage that depends on cccl, and cccl would ship the actual CCCL contents.
Alternative 2: cccl could be just a metapackage that depends on cuda-cccl-impl, and cuda-cccl-impl would ship the actual CCCL contents.
I don't think Alternative 1 or 2 provide much real utility over Proposal 1 above, but they could be evaluated if others feel differently.
Additional Context / "target platform" packages
The cuda-cccl-impl package ships its contents in include/{cub,cuda,nv,thrust}/ and aims to serve users building their packages with a CCCL that may be newer than the CCCL that ships as an internal component of the user's installed CTK (see also CCCL / CTK compatibility policy, draft in https://github.com/NVIDIA/cccl/pull/291 at the time of writing).
There are also "target platform" packages like cuda-cccl_linux-64 which exist to serve the CUDA Toolkit's internal uses of CCCL, specifically packages required for cuda-cudart-dev_linux-64, which is in turn a dependency of cuda-nvcc_linux-64. The "target platform" packages are not affected by this proposal. Those "target platform" packages ship their contents in paths like targets/x86_64-linux/include/{cub,cuda,nv,thrust} and do not conflict with this package.
cc: @jakirkham @wmaxey @jrhemstad @manopapad @kkraus14 @robertmaynard

cc @adibbley

cc @vyasr

I'm happy with any of the directions proposed. Thanks everyone for pushing this forward!

I agree with proposal 1 and don't see the value in the alternatives given how recent cuda-cccl-impl is and how much more involved the reasoning would be with the alternative proposals.

I concur, I don't see much benefit in adding extra metapackage layers of indirection.

All y'all are smarter than me, so I'll defer to you. My only goal is to make it as easy for people to use CCCL from whatever their preferred source is.

@jakirkham It looks like renaming this requires a new staged recipe. https://conda-forge.org/docs/orga/guidelines.html#renaming-packages
Is filing a new feedstock and archiving this one the right process for moving forward?

Yeah that sounds like a good plan. Please link that PR here for reference

Staged recipe PR created: https://github.com/conda-forge/staged-recipes/pull/23722

Thanks Bradley! 🙏

cc @adibbley

Also think we want to add this to cuda-cccl-impl to prevent clobbering (as is being done to cccl)
requirements:
  run_constrained:
    # Prevent clobbering with cccl
    - cccl <0a0

@jakirkham I think you only need run_constrained in one direction, right? I'd prefer to fix (and repodata patch) cuda-cccl-impl and not hold that code in the new cccl, if that's viable. I tentatively accepted your change to the cccl recipe but would like to switch it to a fix/repodata patch for cuda-cccl-impl.

^ That would more similar to how we handled thrust when it was a standalone feedstock. https://github.com/conda-forge/thrust-feedstock/issues/19

Sure let's give that a try

@jakirkham I opened #3 for now, and I'll open a repodata patch PR after the cccl staged recipe and #3 are merged.

The cccl feedstock is now live: https://github.com/conda-forge/cccl-feedstock


initialize vault in workflow

#84
results in:

Hmm. Left some extra stuff in the pr. Will fix in a bit.

@trriplejay rebase required

i think we should remove the cleanup file and add it as a command in installer. something like
./admiral.sh clean
this should ask for prompt and remove containers, folders and any configs


Issue-551 Add server-side encryption for sns topic

Adds support for SNS server-side encryption by passing encryption option in config.
Follows a similar approach to #363
(#551)

Hey, thanks for the approvals! Could you please retry the tests to re check? The failing is a previous one and I've only changed to use structured logging for the last run.

Hey @martincostello could you please trigger the test again as per the above? Seems it still only has the first run and I don't think my change in the logging would cause the failure.
Also, do you have an idea when this could get merged, once the tests are passing?
Thanks

@martalexandra I've re-triggered the build. In terms of merging, I'd have thought we can merge it as soon as the statuses are all green.


Unexpected method 'destination_path', undefined method `join'

The following warning and error are happened. Are they well-known?
$ brew cask install parallels9

Warning: Unexpected method 'destination_path' called during postflight on Cask parallels9.

  Most likely, this means you have an outdated version of homebrew-cask. Please run:

      brew update && brew upgrade brew-cask && brew cleanup && brew cask cleanup

  If this doesn’t fix the problem, please report this bug:

      https://github.com/caskroom/homebrew-cask/issues

Error: undefined method `join' for nil:NilClass

  Most likely, this means you have an outdated version of homebrew-cask. Please run:

      brew update && brew upgrade brew-cask && brew cleanup && brew cask cleanup

  If this doesn’t fix the problem, please report this bug:

      https://github.com/caskroom/homebrew-cask/issues

<main>:12:in `block in <class:KlassPrefixParallels9>'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/artifact/postflight_block.rb:9:in `instance_eval'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/artifact/postflight_block.rb:9:in `block in install_phase'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/set.rb:232:in `each_key'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/set.rb:232:in `each'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/artifact/postflight_block.rb:8:in `install_phase'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/installer.rb:119:in `block in install_artifacts'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/installer.rb:117:in `each'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/installer.rb:117:in `install_artifacts'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/installer.rb:66:in `install'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/cli/install.rb:20:in `block in install_casks'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/cli/install.rb:17:in `each'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/cli/install.rb:17:in `install_casks'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/cli/install.rb:6:in `run'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/cli.rb:79:in `run_command'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/hbc/cli.rb:119:in `process'
/usr/local/Cellar/brew-cask/0.54.0/rubylib/brew-cask-cmd.rb:18:in `<main>

Should be fixed. Please brew upgrade and try again.

brew update
brew upgrade --all

then fixed. Thanks, vitorgalvao!!


Simplify the resender initialize logic

What changed?
Simply the resender initialize logic

Why?
simplify code

How did you test it?
unit test

Potential risks

Coverage decreased (-0.07%) to 68.616% when pulling 703f342d415ba71ba731d74e467c8e5bfe914753 on simplify into 8d51151ba98bb7f7da93b2ab6196fe273c2f300d on master.


Add link to Azure AD authentication documentation

@stewartadam,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/UCWA/AuthenticationInUCWA.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


WIP Delete node and client ALCs on --purge option

Delete node and client ALCs on knife ec backup when --purge option is given (currently this does not happen).
Addresses:
https://github.com/chef/chef-server/issues/2842
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] All commits have been signed-off for the Developer Certificate of Origin.


rewards_staking: fix the issue of exceeding u64 value of transaction fee

First of all, congratulations for taking PR #100 :smiley:. Could you briefly elaborate on the issue? Did the node reject the test due to u64 overflow or does the node need to be fixed to handle this? Coin/token amounts are usually represented as u128 so it seems a bit weird.

The difference between inputs and outputs, which is the reward for miners/stakers, calculated in substrate by default with a u64 type. So, if the difference is too high, I decided to make it fail because that'll cause burning coins


Use just as Router in AWS Lambda

Is it possible to use javalin as Router in AWS Lambda to dispatch incoming request to different controller/handler classes within a lambda itself?

I think it's possible. I know some people have done something similar, but I couldn't find any repo.

https://github.com/richarddd/aws-lambda-api-gateway-servlet

Someone just posted this in the gitter chat.

n1 thx


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: AdamAwada sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


fix: Repair problem in package.json where require/import was swapped. Add in export of package.json

What does this PR introduce?
🐛 Bug: The package.json had the require and import sections
Add package.json into the export sections, which was missing.

PR Checklist

[x] Wrote Tests
[ ] Wrote & Generated Documentation (readme/natspec/dodoc)
[x] Ran npm run lint && npm run lint:solidity (solhint)
[x] Ran npm run format (prettier)
[x] Ran npm run build
[x] Ran npm run test

Switched this to draft, it turns out when you actually try to access INTERFACE_IDS node does more checking and fails with various errors during the typescript import.

It turns out the tsc solution was randomly working and not working. Neither node or ts-node properly support ESMs and when actually accessing the imported values random errors would occur. The best approach was to use esbuild with the --bundle flag to get a properly configured esm and run that.


regular_expression: Support ES2025 proposal-duplicate-named-capturing-groups

https://github.com/tc39/proposal-duplicate-named-capturing-groups

Spec text is not updated yet, ongoing PR may be helpful. 👉🏻 https://github.com/tc39/ecma262/pull/2721
For now, /(?<a>.)(?<a>.)/ is invalid syntax, name a is duplicated.
With this change, we can use the same name if they are splitted by | and in the same Disjunction like /(?<a>.)|(?<a>.)/.
But it still not allowed in some cases like /(?<n>|(?<n>))/, /(?<n>(?<n>)|)/, /((?<n>)|(?<n>))(?<n>)/, etc...
You need to track nesting level and | to mange scope.
TODOs

[ ] Update count capturing parens logic to allow duplicates in certain cases

https://github.com/oxc-project/oxc/blob/aa7718ab7bf0544b21564658a919307022f8824a/crates/oxc_regular_expression/src/body_parser/state.rs#L51
No need to change parser main logic

[ ] Update README

https://github.com/oxc-project/oxc/blob/aa7718ab7bf0544b21564658a919307022f8824a/crates/oxc_regular_expression/README.md

[ ] Update local tests

https://github.com/oxc-project/oxc/blob/aa7718ab7bf0544b21564658a919307022f8824a/crates/oxc_regular_expression/src/body_parser/mod.rs

[ ] Enable conformance tests

https://github.com/oxc-project/oxc/blob/aa7718ab7bf0544b21564658a919307022f8824a/tasks/coverage/src/test262/mod.rs#L103-L104

I'd like to take a stab at this!

@preyneyv You may continue with https://github.com/oxc-project/oxc/pull/6847


RAG

Project Suggestion Title
A simple RAG system using Python and Gemini SDK
Description
RAG System including Gemini and ChromaDB
Would like it be a Hactoberfest Contribution

Hi @TejasGupta-27 ,
Assigned to you with hacktoberfest label.


What's with the line width based on scale?

    _paint.setStrokeWidth(scale/9.0f);

If you don't set a stroke width in android the lines end up being 1 pixel wide regardless how much you zoom. If the coord system is 1 px = 1/10 mm then typically your thread is going to be 3 wide (though there are different threads of different diameters than 30 pt). Apparently since the end of the DST parsing divides the X and Y by 10, we'd be 1 px = 1/100 mm. So at a 1/1 zoom factor we'd be looking at a stroke width of 1/900 ?

I fixed the scale, now you can really see how weird it is.
https://youtu.be/pFOGzsmKJFY

Yeah you are correct, that does look crazy. I set the stroke width to 0.1 for now. Seems to function much better. It is no longer based on scale.


fix linux config path

hey, the config path for configuration on linux systems is wrong.
the correct path is not in init.d directory

This is absolutely correct. Thank you!


Should shelljs be a dev dependency?

In the generated build.js for production there is a require('shelljs/global'). However in the generated package.json shelljs is listed a dev dependency only.
Is this correct? I ask because I'm getting errors when trying ti deploy to Heroku.
Thanks!
UPDATE:
Actually this applies to a bunch of dependencies in build.js like ora and webpack etc.

This is correct. build.js is a script that's used to build the production site, but its dependencies are not included in the static files generated in the dist folder. What errors exactly are you getting on Heroku? And what is your setup? Do you have a backend that you've integrated this into, or are you trying to deploy a static site?

@chrisvfritz hey dude, thanks for the reply.
Basically I'm using this article to deploy the app on Heroku:
<EMAIL_ADDRESS>My set up is the same as the article EXCEPT in the build property in the webpack file I've left it as it is in the webpack template, which is to use build.js.
I think the issue is... build.js references dependencies that aren't loaded in production.
When the code is pushed to Heroku, Heroku run build.js with the env set to Production and it then throws an error saying it can't find any module that's only defined in the devDependencies.
Does that make sense?

@chrisvfritz (FYI I'm totally new to Webpack, node, ES6, express and all that so excuse the ignorance)

@chrisvfritz sorry, some extra info. This is from the Heroku build logs:
-----> Node.js app detected
-----> Creating runtime environment

       NPM_CONFIG_LOGLEVEL=error
       NPM_CONFIG_PRODUCTION=true
       NODE_ENV=production
       NODE_MODULES_CACHE=true
-----> Installing binaries
       engines.node (package.json):  unspecified
       engines.npm (package.json):   unspecified (use default)

       Resolving node version (latest stable) via semver.io...
       Downloading and installing node 5.10.1...
       Using default npm version: 3.8.3
-----> Restoring cache
       Skipping cache restore (new runtime signature)
-----> Building dependencies
       Pruning any extraneous modules
       Installing node modules (package.json)

       ><EMAIL_ADDRESS>postinstall /tmp/build_17d3fe9944e0b6e4f078f45187434413/thatandyrose-the-100-mile-client-5dd0787c0434e15666cb0590f3e9c7301e673a41
       > npm run build

       ><EMAIL_ADDRESS>build /tmp/build_17d3fe9944e0b6e4f078f45187434413/thatandyrose-the-100-mile-client-5dd0787c0434e15666cb0590f3e9c7301e673a41
       > node build/build.js

       module.js:341
       throw err;
       ^

       Error: Cannot find module 'shelljs/global'
       at Function.Module._resolveFilename (module.js:339:15)
       at Function.Module._load (module.js:290:25)
       at Module.require (module.js:367:17)
       at require (internal/module.js:16:19)
etc etc etc.

If you are executing the build step, then you need to install full dev dependencies.

@yyx990803 thanks Evan! (Also thanks for Vue!!!). Could you point me to best practices for deploying vue apps.... it's not very clear for newcomers to this js-only world! Thanks so much.

@thatandyrose Heroku is great for dynamic sites that include a backend server, but for this template (which produces a purely static site), I'd actually recommend using static site hosting such as Surge or Netlify.
What's probably the simplest possible deployment process would look like this:
First, add the surge package to the dev dependencies in your package.json and install it with:
npm install --save-dev surge

Then you can add these two lines to the scripts section of package.json
"predeploy": "npm run build",
"deploy": "surge --project dist --domain whatever-subdomain-you-want.surge.sh"

And... now you're done. 😄  Whenever you run npm run deploy, your site with deploy to Surge, for free. The first time, it'll prompt you to create an account with an email and password and on subsequent runs, it'll just deploy.
Let me know if that works for you!

@chrisvfritz wow awesome! Thanks so much Chris! I'll try that out. THANK YOU!

I ran into the same issue.  Here's how I fixed it.
(Copied below in case the link ever breaks)

devDependencies
We set NPM_CONFIG_PRODUCTION to true by default to install production dependencies only. If you would like to install devDependencies, you can disable production mode:
$ heroku config:set NPM_CONFIG_PRODUCTION=false
However, since you usually don’t want all development dependencies in your production builds, it’s preferable to move only the dependencies you actually need for production builds (bower, grunt, gulp, etc) into dependencies.


Feedback: Fix Docker Container Download

Implemented feedback by updating the docker file and creating a docker-compse.yml file to ease reproducibility.


Snapshots sorted alphabetically instead of the order generated in the test

Do you want to request a feature or report a bug?
Feature
What is the current behavior?
Snapshots are listed in the .snap file alphabetically.
What is the expected behavior?
Snapshots are listed in the .snap file the same order they are created in the test, so it easy to line them up when tests have many snapshots. Maybe the sorting method could be defined as a config option.

Agreed - see comment https://github.com/facebook/jest/issues/3581#issuecomment-311970615

We won't be changing this. You can pass a name to toMatchSnapshot to label snapshots the way you want to.

@cpojer Why would you not consider changing this? Even if we pass in a label, we'll have to duplicate all of the strings in the describe blocks and then prepend every label with 001, 002, etc. just to get it to sort properly.

@cpojer The issue isn't the labels of the snapshots, I actually like the labels being the same as the describe/it blocks.

We aren't going to make this breaking change at this point and we won't be making this configurable. Sorting the snapshots alphabetically makes them stable, for example when tests are disabled. There is an escape hatch to provide the name of the snapshot and you can build your own matcher on top of this to make handling it easier.

@cpojer I'm sorry but I don't understand how this would be a breaking change to make it configurable (since it could just default to its current behavior). I also am not sure what you mean when you say alphabetical sorting makes the snapshots stable.
Regardless of that, can you please provide more info on this escape hatch and how one could go about handling what we're asking for?

@cpojer By disabled tests, do you mean ones resulting obsolete snapshots? Could those just be sorted to the bottom in this case?


Issue when importing @aptabase/web on server

Loving Aptabase so far, but running into an annoyance with using this SDK with SSR frameworks (specifically SvelteKit). I want to exclusively run events clientside, so I make sure to run init and trackEvent only on the client. However, functions like getBrowserLocale are called on import to create defaultLocale (https://github.com/aptabase/aptabase-js/blob/main/packages/shared.ts#L1), which causes an error since navigator.languages does not exist (TypeError: Cannot read properties of undefined (reading 'length'))
Would you accept a PR to either:

Make sure navigator.languages exists before checking length

or

defaultLocale is a "singleton" that is first created when it is requested (which seems to only be in sendEvent()

I'd be happy to do the work, just want to chat about how it should be done (if at all)

Thanks for using Aptabase and for reporting this!
This definitely needs a fix, and it probably makes more sense to read the locale value as late as possible - so like you mentioned in option 2, on sendEvent.
That way when sendEvent is called and is executed on client side navigator.languages should be available.
Adding an extra check with navigator.languages?.length also helps, but it doesn't result in the correct language being loaded, so would go with reading it on sendEvent primarily


Display inline pickers

Is there a way to use it with as an inline picker ? We need to always let the pickers visibles and not in absolute position.

We've implemented that functionnality on our fork, again we don't have time to do a PR but if anyone wants to have a go at it, here's our updated file.
Just look for the openMode prop in the code.

Hey @abclive
Any plans on merging this?
We are super interested in this openMode.
Thank you.

Hey @PascalAOMS sorry just noticing your message now. We curently have no plans of merging this fork as it contains a lot of hacks for our specifics needs and is now far behind the master branch.
However our repo is open and anyone who wants to implement this can use our implementation as a base for a PR.

Hi, I be working on this.

Hi, I am a little swamp right now, so it could take a while.

Done in v4


Add a Gitter chat badge to README.md

PowerShell/Polaris now has a Chat Room on Gitter
@TylerLeonhardt has just created a chat room. You can visit it here: https://gitter.im/PowerShell/Polaris.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: gitter-badger sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

now this is actually a part of the PowerShell gitter group


feat: Join NextGen data with Rails data in resolver

Pull Request
JIRA Ticket
The queries are synchronous because workflowRuns doesn't give us railsSampleIds.
Tests
Being flag

This looks good, but to clarify your PR note, these calls need to be made synchronosly because we need the railsSampleId from nextGen to make the right call to the Rails API, right?

Yep


fix: use absolute links for pypi

The README is used to generate pypi landing page and in this context, your relative links are not pointing anywhere.
With this very little change, you ensure that the readme page remains valid in other contexts than the GitHub display.

I filled the CLA you should be able to relaunch the checks.


Delete action for aws_vpc doesnt work

I run this, to create the VPC:
with_data_center 'us-west-2' do
aws_vpc "provisioning-vpc" do
cidr_block "<IP_ADDRESS>/24"
end
Followed by a second recipe, to delete it:
aws_vpc "provisioning-vpc" do
action :delete
end
The delete recipe just deletes the data bag, not the VPC.

Closing this issue as I can't reproduce it. I think somehow I got the data bag out of sync with what was on Amazon.


selected python version 3.10

why are you selecting for us?

@AhmedCode99 because you had 6 checks failing and one reason was that you selected 3 versions of Python instead of 1.
You used: python-version: ["3.8", "3.9", "3.10"]. Once you remove the two "extra" versions, you will only have 4 fails. It seems you have now removed the "extra" versions after closing this merge request.


Permissions Boundary Not Included in ListUsers Operation

I am calling the ListUsers operation to list out the IAM Users in my account. Among the elements in the response, I was looking for PermissionsBoundary. Per my reading of the documentation, it seems like it should be present in the response data:

https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/iam.html#IAM.Client.list_users
https://botocore.amazonaws.com/v1/documentation/api/latest/reference/services/iam.html#IAM.Paginator.ListUsers

When I call ListUsers, with or without pagination, the response did not include PermissionsBoundary for the IAM User I set it for. I do see the element when I call GetUser for that same user.
This is with version 1.13.27 installed via pip, Python 3.5, Ubuntu 16.04.

I think this is because the IAM API isn't including the data in the response, contrary to the documentation. Here's what I used to reproduce:
import botocore
import botocore.session
import botocore.hooks

def postcall(*args, **kwargs):
   print(kwargs['http_response'].text)

h = botocore.hooks.HierarchicalEmitter()
h.register(event_name='after-call.*', handler=postcall)

session = botocore.session.Session(profile='...', event_hooks=h)

iamclient = session.create_client('iam')
response = iamclient.list_users()

After calling list_users(), the raw XML response from IAM was dumped to stdout due to the hook. Looking for my user with boundaries, the boundary element is not included.

its sort of related to how all the sdks get constructed from the service team descriptions and models. the model thats being provided for user is the same across those two api calls, however the list api call doesn't include the full representation. the service team could have used a separate model that would have been included in the list operation, but in this case they reused same model across both, however its only on the get user operation that the full model response is included. obviously this can cause some confusion around the docs, but afaics its really on the service team to include in their api metadata a correct model for a given operation, the sdks just consume and expose that metadata for a given language implementation.

Okay, then the solution seems to be to pivot to using iam:GetUser for each IAM User I want this data on.

@ncc-erik-steringer - Thank you for your post. I can confirm that list_users operation does not return PermissionsBoundary. @kapilt thank you for such a detailed description. I will contact the service team about the issue and see what we can do to remove this confusion.

To add to this, the botocore documentation also says a list of Tags is returned by the API docs don't reflect that.


[feature] Support "TODO - message" format

This seems like a fairly common pattern
% TODO - message

https://github.com/search?q="TODO+-"&type=code

hyphens and slash separators are already supported


app_identifier  can't change

build.sh
#!/bin/sh
versionNumber=$1 # 1.0.0
buildNumber=$2 # 2000
rm -rf build
basicLanes="InHouse"
for laneName in $basicLanes
do
fastlane $laneName version:$versionNumber build:$buildNumber
done
appfile.h
app_identifier "org.test.the1111111111"
apple_id<EMAIL_ADDRESS>team_id "Q2CBPJ58CA"
# 1.inhouse
for_lane :InHouse do
app_identifier "org.test.apple"
apple_id<EMAIL_ADDRESS>end
I want a to be equal to app_identifier "org.test.apple"
Post execution  app_identifier "org.test.the1111111111"
why？

help help help?

Hi @goodcyg! Great to hear from you. Can you post the full output as well as any error messages you are getting? I'm not quite sure I understand what issue you are hitting, but I'd love to help. Thanks! 👍

appfile
app_identifier "org.test.the1111111111"
apple_id<EMAIL_ADDRESS>team_id "Q2CBPJ58CA"
#1.inhouse
for_lane :InHouse do
app_identifier "org.test.apple"
apple_id<EMAIL_ADDRESS>end
fastfile
def update_app_bundle_id(app_id)
update_info_plist(
    xcodeproj:PROJECT_FILE_PATH ,
    app_identifier:app_id,
    plist_path:"#{PLIST_FILE_PATH}"
)
 update_app_identifier(
    xcodeproj:PROJECT_FILE_PATH ,
    app_identifier:app_id,
    plist_path:"#{PLIST_FILE_PATH}"
)

update_info_plist(
    xcodeproj:PROJECT_FILE_PATH ,
    app_identifier:app_id,
    plist_path:"#{UNITTEST_PLIST_FILE_PATH}"
)

 update_app_identifier(
    xcodeproj:PROJECT_FILE_PATH ,
    app_identifier:app_id,
    plist_path:"#{UNITTEST_PLIST_FILE_PATH}"
)

end
After executing this code，info.plist  File in CFBundleIdentifier="org.test.the1111111111"
And I want  that info.plist  File in CFBundleIdentifier="org.test.apple"，app_identifier can't change？

Hi @goodcyg! Thanks for working with me on this. You should be able to set up your app with multiple targets using env. Check out the help on this page for more info, https://github.com/fastlane/fastlane/blob/9c0494ef5e7d71afc51c73fe0b141b02e8991d9c/fastlane/docs/FAQs.md.
Thanks!

For some reason the link was to a version from a specific commit, here's the latest one from master: FAQs.md


Scarb artifact name change

https://github.com/software-mansion/protostar/issues/2175
In new scarb version the artifact name will change. Right now it is:
[package name].starknet_artifacts.json
and it will change to
[target name].starknet_artifacts.json
In most cases target name is the same as package name, but it could be different. This value can be taken out of metadata.
https://docs.rs/scarb-metadata/latest/scarb_metadata/struct.TargetMetadata.html#structfield.name

Wasn't it resolved in #188?

@bartekryba issue you linked looks like a PR for forge, this issue is for cast

@cptartur Not sure about it, my understanding was that the change is pretty straightforward, but perhaps I'm wrong. Isn't it just about getting metadata from scarb, getting all targets and then trying to figure out which one of them should be used? (we have an information about contract name so perhaps it is enough)

I've looked at #188 again and it looks simple enough


Visibility option on main button versus just sub-buttons

Standard HA visibility option only works for sub buttons and not main button?  Is this by design or am I missing something?
`
      visibility:
        - condition: state
          -  entity: '[[media_player]]'
          -  state: media_player.android_tv_192_168_1_60

`
This works on a sub-button but not on main button

Hi! What do you mean by main button? If it's about the whole card, there is a Visibility tab at the top of the editor.

All is fine for me....?

type: custom:bubble-card
card_type: button
entity: input_boolean.help_house_testboolean3
sub_button:
  - entity: input_boolean.help_house_testboolean3
    icon: mdi:numeric-3
    visibility:
      - condition: state
        entity: input_boolean.help_house_testboolean2
        state: "on"
    name: Only Show when 2=on
    show_name: true
icon: mdi:numeric-3
name: Only show when 1=on
visibility:
  - condition: state
    entity: input_boolean.help_house_testboolean
    state: "on"

I am sorry, it actualy reverse, works on main button but not sub buttons!
And I notice on UI editor it shows 2.3.0 which as far as I can tell from changelogs does not support visibility option on sub buttons.
I have updated to 2.3.3 in HACS

So we can close this?


Document that the automatic center of mass mode uses the individuals shape origins

This clarifies how the automatic mode for center of mass works in RigidBody: it won't calculate the center for individual shapes. It only averages the origins.
I was not expecting this from an automatic mode, so I hope this clarification can help others too.

Thanks!