Error when adding buildModules to nuxt.config with NaiveUI

Hello ! Thanks for the great work. Using your module alone works fine but I am having a hard time integrating it to my project that uses modules (supabase integration).
Environment
Nuxt CLI v3.0.0-27409835.c53c736                                                                             11:57:10
RootDir: /media/workspace/code/nuxt3-naive-ui-starter                                       11:57:11
Nuxt project info:                                                                                11:57:11

------------------------------
- Operating System: `Linux`
- Node Version:     `v17.3.0`
- Nuxt Version:     `3.0.0-27409835.c53c736`
- Package Manager<EMAIL_ADDRESS>- Bundler:          `Vite`
- User Config:      `build`, `vite`, `buildModules`, `supabase`
- Runtime Modules:  `-`
- Build Modules:    `<EMAIL_ADDRESS>------------------------------

Reproduction
https://stackblitz.com/edit/github-9zcuqu?file=app.vue
Describe the bug
When adding supabase module with the following instructions, automatic import of naiveui components don't work anymore. I have to manually import everything.
I wonder if @css-render/vue3-ssr plays well with Nuxt3 ? Do you have an idea what could cause this error ?
Logs
[Vue warn]: Failed to resolve component: n-result
If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.
[Vue warn]: Failed to resolve component: n-button
If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.
[Vue warn]: Failed to resolve component: n-space
If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.
[Vue warn]: Failed to resolve component: n-h2
If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.
[Vue warn]: Failed to resolve component: n-tooltip
[...]
(node:13) UnhandledPromiseRejectionWarning: TypeError: Invalid value used as weak map key
    at WeakMap.set (<anonymous>)
    at normalizePropsOptions (/home/projects/github-9zcuqu/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:3384:11)
    at createComponentInstance (/home/projects/github-9zcuqu/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6851:23)
    at renderComponentVNode (/home/projects/github-9zcuqu/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:197:22)
    at Module.ssrRenderComponent (/home/projects/github-9zcuqu/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:629:12)
    at _sfc_ssrRender (file:///home/projects/github-9zcuqu/.nuxt/dist/server/server.mjs:7330:31)
    at renderComponentSubTree (/home/projects/github-9zcuqu/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:269:13)
    at renderComponentVNode (/home/projects/github-9zcuqu/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:214:16)
    at Module.ssrRenderComponent (/home/projects/github-9zcuqu/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:629:12)
    at default (file:///home/projects/github-9zcuqu/.nuxt/dist/server/server.mjs:7224:35)

I'm not familiar with supabase, and it's used in nuxt3 with very little information, maybe you can give feedback directly to the author's repository to see. naive-ui can be fully automated and introduced on demand thanks to unplugin-vue-components. maybe you can refer to this project to implement it
https://github.com/zulvkr/nuxt3-ts3


Java to Bedrock Conversion Error

Chunker Version
1.1.3-main-ac2a40f
Input World Version
Java 1.21.1
Output World Version
Bedrock 1.21.0
Platform / Operating System
win32-x64-10.0.22631
Issue Description
Error Chunker Displayed: A fatal error occurred during conversion.
Error identifier: a7c9739a-10b2-4be2-8009-2f73113c464f

If you're able to provide the following so we can look further into the issue:

Can you send a copy of your main.log from %APPDATA%/chunker-electron/logs, you'll want to put that path into Explorer / Run dialog (Windows Key + R)
The world if possible or a world that produces the same error, you can also email it to<EMAIL_ADDRESS>

Thanks for sending this, seems to be related to the NBT limits we have in place, we'll increase the limits for the next release which will hopefully allow you to try converting the map.


feat(proxy): Adds NO_PROXY environment variable support

Adds support for loading from the NO_PROXY or no_proxy environment
variables. This should make reqwest support the system proxy settings.
Please note that I brought in one additional dependency in order to
handle CIDR blocks in the no proxy settings.
Closes #705

The one thing I could use help with here is that if I don't use __internal_proxy_sys_no_cache or run my new tests individually, I get test failures, which is causing some of them to fail. I figure this is due to it caching what it loads from the environment, so I am not sure what the right way is to do it

Just added a commit that manually constructs the proxy each time so as to avoid caching. If that is not desired behavior, let me know what else I can do and I'll change it

@seanmonstar, I could definitely use this--can you take a look?

thank you, works like a charm ❤

No problem! Thanks for the review


Replace HTTP with Fetch #55

One last step before Meteor 3 upgrade.

Both options are fine, but I think separate PR would do better, so that we can merge this and do a release.


Installation Instructions

@rikonen
@rdunklau
@aiven-amartin
What can we help you with?
How do I install this?
Where would you expect to find this information?
README

@rikonen pretty please?  I would really like to use this software, but there is no clear docs on how to actually install this (Ubuntu in my case)

I'm not really working on the project anymore. There is currently no support packaging this for Ubuntu specifically unfortunately. In general the expectation is that user mysql is used to run both MyHoard and MySQL server, MySQL server is managed via systemd and the unit name is mysqld, the following is defined in sudoers
mysql   ALL=(ALL) NOPASSWD: /usr/bin/systemctl start mysqld
mysql   ALL=(ALL) NOPASSWD: /usr/bin/systemctl stop mysqld
mysql   ALL=(ALL) NOPASSWD: /usr/bin/systemctl restart mysqld
mysql   ALL=(ALL) NOPASSWD: /usr/bin/myhoard_mysql_env_update -f /etc/systemd/system/mysqld.environment -b false -g false
mysql   ALL=(ALL) NOPASSWD: /usr/bin/myhoard_mysql_env_update -f /etc/systemd/system/mysqld.environment -b false -g true
mysql   ALL=(ALL) NOPASSWD: /usr/bin/myhoard_mysql_env_update -f /etc/systemd/system/mysqld.environment -b true -g false
mysql   ALL=(ALL) NOPASSWD: /usr/bin/myhoard_mysql_env_update -f /etc/systemd/system/mysqld.environment -b true -g true

, /usb/bin/myhoard and /usr/bin/myhoard_mysql_env_update are executable files that run myhoard.py and myhoard_mysql_env_update.py python modules respectively, and the myhoard.json file is updated according to your configuration to contain appropriate parameters. The myhoard.unit file has an example of how to configure systemd service for MyHoard itself.

@rikonen Thank you for the reply.

So, is there no other "install" before any of that is configured for service account or permissions?
Do I need to do a pip install ?

@rikonen I was able to get things workong ( I believe ).
I connected as the mysql user and:

git cloned repo into /tmp directory
copied the myhoard dir into /var/lib/myhoard and gave it mysql user/group permissions
used python3 -m venv  /var/lib/myhoard/venv to create a virtual environment
activated the virtual env with source /var/lib/myhoard/venv/bin/activate
pip install -e . (from within the /tmp/myhoard directory)
updated the service file (with path to virtualenv in ExecStart and some other tweaks)  ( see below )
made changes to myhoard.json config file

[Unit]
Description=MySQL streaming backup service

[Service]
User=mysql
Group=mysql
Type=notify
Restart=always
RestartSec=5s
Type=forking
KillMode=process
TimeoutSec=60s
ExecStart=/bin/bash -c '/var/lib/myhoard/venv/bin/myhoard --config /var/lib/myhoard/myhoard.json & echo "Service started"'
ExecStop=/bin/kill -TERM $MAINPID
ExecReload=/bin/kill -HUP $MAINPID
WorkingDirectory=/var/lib/myhoard
# Percona XtraBackup needs to keep all database tables open simultaneously and it inherits our
# nofile limit. Set to very large number to allow it to operate in large environments
LimitNOFILE=2000000

[Install]
WantedBy=multi-user.target

Now my questions are:

I do not have a /etc/systemd/system/mysqld.environment file and not sure what goes in there or what it's for? My systemd service name for mysql is mysql not mysqld
How can I validate the backup is good without restoring it?
Is it possible to do a restore on the master mysql server?


software crashes when attempting to view results

When launching the software from executable, the software quits when attempting to view scenario results. This does not occur when launching the software from the IDE. This is occurring both on main and on github_issues.

I can view results using the build I put together a week ago, so this happened recently.

it just closed the program, no uncaught exception window

if helpful, it just happened upon attempting to view study properties

I think it will happen on any UI that uses "UserControls".

I'm suspecting this has something to do with the hacky way I was packaging the build before. I'm now using the publish function.  This should be better.

Successfully viewing results using a Published build, rather than just a zipped build folder.

The Workflow file has been updates so that we now publish our builds using dotnet publish when we do CI.


Remove unused verbose flag

If it's all the same with you, I will reimplement the command line option-
I don't recall when it went away.
On Thu, Dec 22, 2016 at 9:53 AM, Don Brower<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/ndlib/bendo/pull/144
Commit Summary

Remove unused verbose flag

File Changes

M cmd/bclient/main.go
https://github.com/ndlib/bendo/pull/144/files#diff-0 (2)
M fileutil/fileutil.go
https://github.com/ndlib/bendo/pull/144/files#diff-1 (8)

Patch Links:

https://github.com/ndlib/bendo/pull/144.patch
https://github.com/ndlib/bendo/pull/144.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ndlib/bendo/pull/144, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADNGTMwdPBkeWE8ErrEcBO5PKuh9nzGgks5rKo7lgaJpZM4LUDXY
.

The command line utility bclient still has a verbose option. This patch removes an unused global in the fileutil package.


Error found during installation

I am using grl_Software_Manual (https://ahundt.github.io/grl/_downloads/grl_Software_Manual.pdf) windows operating system (windows1064bit) and install Cygwin64 Terminal. When i enter this command (git clone https://github.com/ahundt/grl.git) the following error appear.
-bash: git: command not found
On the contrary
When i enter below command
tar xzf /path/to/downloaded/grl-$version.tar.gz
then i got following error
tar (child): /path/to/downloaded/grl-.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
Could you please suggest me what i need to do.
While it work in Linux.

$version is a variable and you haven't set it to anything.
Maybe try the windows subsystem for linux?
https://msdn.microsoft.com/en-us/commandline/wsl/install_guide
However, we don't generally support windows at this time, unfortunately. I'm glad to hear linux works for you!


Ability to select background color

Would it be possible to avoid selecting a background color, instead of an image?
This parameter could reside inside the betterlockscreenrc config file.
What do you think?

Thanks for your request, this will be resolved soon, with the merge of the multi-monitor branch from the multilockscreen-fork :)

Tested with multi-monitor (upcoming v4) and works - but currently we generate images for colors even i3lock-color can do color's without so we should think about if this is really a good idea as the user has to run update for color-changes...

@SebTM The loginbox is rendered onto the images (during update). If we use i3lock's --color, we wouldn't get the loginbox.
We are actually setting --color, but that's to mitigate flickering some users have reported (#241 and mls/#43).
I added this feature to multilockscreen in response #143. I guess these are duplicate issues?

Okay I get it thanks, then it's resolved :)


Fix lastUpdated position closes

What kind of changes does this PR include?

Changes to Starlight code

Description
Closes #417
Before the "Last Edit Date" would be leading-aligned if there was no edit url set. This caused an inconsistency on the wide layouts:

Now it will always be trailing-edge aligned if it's the only child:

There's no change in behaviour for if the editUrl is present.

@delucis I agree with you on that and thought the same when I was writing it. But like you said, it might not be worth that big of a refactor just for this low-hanging fruit and to get it cleaned up.


[stable-4.0] generating ceph.conf fails

Bug Report
What happened
TASK [ceph-config : generate ceph.conf configuration file] ******************************************************************************************************
fatal: [sagittarius]: FAILED! =>
  msg: the inline if-expression on line 1 evaluated to false and no else section was defined.

How to reproduce it (minimal and precise):
stable-4.0 branch, upgrading from stable-3.2 with the below variables
---
# forcing them as it kept changing from debian and container
bootstrap_dirs_owner: "167"
bootstrap_dirs_group: "167"
fsid: <fsid>
generate_fsid: false
monitor_interface: eth0
cephfs_pools:
# about to change to autoscaler
 - { name: "{{ cephfs_data }}", pgs: "64", size: "2", min_size: "{{ osd_pool_default_min_size }}" }
 - { name: "{{ cephfs_metadata }}", pgs: "64", size: "4", min_size: "{{ osd_pool_default_min_size }}" }
public_network: "<IP_ADDRESS>/24"
osd_objectstore: bluestore
radosgw_frontend_type: beast
radosgw_civetweb_port: 7480
radosgw_frontend_port: 8088
radosgw_interface: eth0
common_single_host_mode: true
ceph_conf_overrides: {}
os_tuning_params:
  - { name: fs.file-max, value: 26234859 }
ceph_docker_image_tag: latest-nautilus
containerized_deployment: true
---
ceph_mgr_modules:
  - status
  - balancer
  - dashboard
  - prometheus
  - restful
  - iostat
---
ceph_mon_docker_memory_limit: "{{ (ansible_memtotal_mb / 4) | round | int }}m"
---
dummy:
nfs_file_gw: true
nfs_obj_gw: false
ceph_nfs_disable_caching: true
---
devices:
  - /dev/disk/by-id/ata-HGST_HUH728080ALE600_R5G2DRGV
  - /dev/disk/by-id/ata-HGST_HUH728080ALE600_R6GWWBXY
  - /dev/disk/by-id/ata-HGST_HUH728080ALE600_VLG6K3BY
  - /dev/disk/by-id/ata-HGST_HUH728080ALE600_VLHMNLBY
osd_auto_discovery: false
osd_scenario: lvm

Environment:

OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Docker version if applicable (e.g. docker version):
Ansible version (e.g. ansible-playbook --version):
ceph-ansible version (e.g. git head or tag or stable branch):
Ceph version (e.g. ceph -v):

radosgw_frontend_type: beast

That's a known bug when using beast rgw frontend due to a missing else statement in radosgw_frontend_options variable.
This will be resolve by https://github.com/ceph/ceph-ansible/pull/3637

Thank you, will await the PR.


Add group name uniqueness validation to endpoint-prefix package.

Add group name uniqueness validation to endpoint-prefix package.

Actually - RegExp constructor already does that (thankfully):
/(?<test>first)|(?<test>second)/

produces
Uncaught SyntaxError: Invalid regular expression: /(?<test>first)|(?<test>second)/: Duplicate capture group name


@angular-devkit/build-angular:server emits invalid code at the second and subsequent times when running in the watch mode

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

Command (mark with an x)
- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [x] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

npm: 6.4.0
macOS High Sierra
Angular CLI: 6.1.4
Node: 8.9.0
OS: darwin x64
Angular: 6.1.2
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.7.4
@angular-devkit/build-angular     0.7.4
@angular-devkit/build-optimizer   0.7.4
@angular-devkit/build-webpack     0.7.4
@angular-devkit/core              0.7.4
@angular-devkit/schematics        0.7.4
@angular/cli                      6.1.4
@ngtools/webpack                  6.1.4
@schematics/angular               0.7.4
@schematics/update                0.7.4
rxjs                              6.2.2
typescript                        2.9.2
webpack                           4.9.2

Repro steps

$ git clone git@github.com:angular/universal-starter.git
$ cd universal-starter
$ ng update --all --force
$ yarn add<EMAIL_ADDRESS>$ ng run ng-universal-demo:server
$ wc -l dist/server/main.js
     530 dist/server/main.js
$ npm run compile:server && npm run serve:ssr
# Node Express server starts successfully
# quit with cmd+C
$ ng run ng-universal-demo:server --watch

# in a different tab of the terminal
$ wc -l dist/server/main.js
     530 dist/server/main.js
$ npm run compile:server && npm run serve:ssr
# Node Express server starts successfully
# quit with cmd+C
$ vi src/app/app.component.ts
# remove an empty line inside the AppComponent class and save
# wait for the second build to be completed
$ wc -l dist/server/main.js
     697 dist/server/main.js
$ npm run compile:server && npm run serve:ssr
# "Error: Cannot find module<EMAIL_ADDRESS>$ vi src/app/app.component.ts
# add an empty line inside the AppComponent class and save
# wait for the third build to be completed
$ wc -l dist/server/main.js
     672 dist/server/main.js
$ npm run compile:server && npm run serve:ssr
# "Error: Cannot find module<EMAIL_ADDRESS>
The log given by the failure

Error: Cannot find module<EMAIL_ADDRESS>    at Function.Module._resolveFilename (module.js:536:15)
    at Function.Module._load (module.js:466:25)
    at Module.require (module.js:579:17)
    at require (internal/module.js:11:18)
    at<EMAIL_ADDRESS>(/Users/kenji_imamura/src/universal-starter/dist/server/main.js:646:18)
    at __webpack_require__ (/Users/kenji_imamura/src/universal-starter/dist/server/main.js:20:30)
    at Object../src/app/app.server.module.ngfactory.js (/Users/kenji_imamura/src/universal-starter/dist/server/main.js:200:26)
    at __webpack_require__ (/Users/kenji_imamura/src/universal-starter/dist/server/main.js:20:30)
    at Object../src/main.server.ts (/Users/kenji_imamura/src/universal-starter/dist/server/main.js:507:37)
    at __webpack_require__ (/Users/kenji_imamura/src/universal-starter/dist/server/main.js:20:30)

The cause of the error is the following line, which does not appear at the first time build.
module.exports = require("@angular/router.ngfactory");

Desired functionality

@angular-devkit/build-angular:server should emit valid code in the watch mode.
Mention any other details that might be useful

@zygimantas Thanks.  Yes the underlying issue is indeed the same.


feat: add sendRaw function

Closes #439
Adds a sendRaw function that lets the user manually construct a CDP message. This way, the user has control over parameters like sessionId, unlocking the full capabilities of CDP.

Nice addition, AFAIK this is necessary to support commands like Target.attachToBrowserTarget()

Nice addition, AFAIK this is necessary to support commands like Target.attachToBrowserTarget()

Ah yeah, we should be talking about Target.attachToTarget, not Target.attachToBrowserTarget here. :facepalm:
Is there another way to attach to a per-tab target from the browser target besides calling Target.attachToTarget? After using Target.attachToTarget, the sessionId that is yielded from that command must be sent with every command for the target, which was the motivation for this PR.

No OK, my question was (for @Niek) about Target.attachToBrowserTarget.

Is there another way to attach to a per-tab target from the browser target besides calling Target.attachToTarget? After using Target.attachToTarget, the sessionId that is yielded from that command must be sent with every command for the target, which was the motivation for this PR.

@flotwig the alternative is the deprecated Target.sendMessageToTarget, so yeah this PR makes sense.

BTW, I can't seem to make it work, Chrome simply doesn't reply anything to messages that include a sessionId parameter:
$ wscat -c ws://<IP_ADDRESS>:9222/devtools/browser/322f0530-a2ea-4430-aa1e-70f897a30e4c
> {"id":0,"method":"Target.getTargets","params":{}}
< {"id":0,"result":{"targetInfos":[{"targetId":"153B060BA08BB627A6205846A1799A46","type":"page","title":"about:blank","url":"about:blank","attached":false,"canAccessOpener":false,"browserContextId":"E26C41C6E1F55135ABDDCEBB1BBB071E"}]}}
> {"id":0,"method":"Target.attachToTarget","params":{"targetId":"153B060BA08BB627A6205846A1799A46"}}
< {"method":"Target.attachedToTarget","params":{"sessionId":"AB8DD70A146AD1EEC8363C92E4D5DEEE","targetInfo":{"targetId":"153B060BA08BB627A6205846A1799A46","type":"page","title":"about:blank","url":"about:blank","attached":true,"canAccessOpener":false,"browserContextId":"E26C41C6E1F55135ABDDCEBB1BBB071E"},"waitingForDebugger":false}}
< {"id":0,"result":{"sessionId":"AB8DD70A146AD1EEC8363C92E4D5DEEE"}}
> {"id":0,"method":"Page.navigate","sessionId":"AB8DD70A146AD1EEC8363C92E4D5DEEE","params":{"url":"http://example.com"}}
> # no reply...

Where ws://<IP_ADDRESS>:9222/devtools/browser/322f0530-a2ea-4430-aa1e-70f897a30e4c is the browser WebSocket:
$ curl http://localhost:9222/json/version
{
   "Browser": "HeadlessChrome/91.0.4441.0",
   "Protocol-Version": "1.3",
   "User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/91.0.4441.0 Safari/537.36",
   "V8-Version": "9.1.60",
   "WebKit-Version": "537.36 (@151c9b31e30d132a7a859f41f49bd44d7b008675)",
   "webSocketDebuggerUrl": "ws://localhost:9222/devtools/browser/322f0530-a2ea-4430-aa1e-70f897a30e4c"
}

Chrome simply doesn't reply anything to messages that include a sessionId parameter

With the only exception, funnily enough, of the sessionId returned by the Target.attachToBrowserTarget  method, which is useless IMHO.

In the meanwhile I pushed an alternate implementation in a separate branch that does not require an additional function, now the sessionId is just another optional argument to send() and all the other variants, for example:
await Page.navigate(sessionId, {url: 'https://github.com'});

@cyrus-and Sorry, Target.attachToBrowserTarget was a bad example.
I tested the new branch and it works great:
→ ./bin/client.js inspect
>>> Target.getTargets()
{
  targetInfos: [
    {
      targetId: 'C104A7A2F6C6B29840C1EAFD9E7F4A22',
      type: 'page',
      title: 'about:blank',
      url: 'about:blank',
      attached: true,
      canAccessOpener: false,
      browserContextId: 'C689EBAB4EF2567951424D1C7E0794FA'
    }
  ]
}
>>> Target.attachToTarget({targetId: 'C104A7A2F6C6B29840C1EAFD9E7F4A22'})
{ sessionId: '5B8328334DD51F8EFDBD17C941C42C58' }
>>> Page.navigate({sessionId: '5B8328334DD51F8EFDBD17C941C42C58', url: 'https://github.com'});
{
  frameId: 'C104A7A2F6C6B29840C1EAFD9E7F4A22',
  loaderId: '78B81222D9D6211F918787268E249B9B'
}

Looking forward to see this released!

@Niek uhm, I'm afraid it doesn't work that way, you're just passing sessionId as another parameter and it gets ignored as it is not a parameter of Page.navigate. That example would also work with master version.
In the new branch the correct syntax is:
Page.navigate('5B8328334DD51F8EFDBD17C941C42C58', { url: 'https://github.com'})

But it hangs, as I pointed out in this comment (where I use the browser target, which I think is the only context where the sessionId can be used AFAIK).
I'm not aware of your use case but it looks like you don't really need to use sessionId. But if I'm wrong I'd love to see a minimal examples that successfully manages to use it, even with raw WebSocket messages.

@cyrus-and Oops, I feel silly. This is the way to get it working (you need to flatten the session):
>>> Target.getTargets()
{
  targetInfos: [
    {
      targetId: 'AE5249680D5E2E5FE1AEBC1FE029EC8F',
      type: 'page',
      title: 'about:blank',
      url: 'about:blank',
      attached: true,
      canAccessOpener: false,
      browserContextId: '1FB2FCD4E41A007E3938DED4678A5933'
    }
  ]
}
>>> Target.attachToTarget({targetId: 'AE5249680D5E2E5FE1AEBC1FE029EC8F', flatten: true})
{ sessionId: '8C45BC912828F26DD634268FF23A1570' }
>>> Page.navigate('8C45BC912828F26DD634268FF23A1570', {url: 'https://github.com'});
{
  frameId: 'AE5249680D5E2E5FE1AEBC1FE029EC8F',
  loaderId: '2154A11FF6AE82267E2BE7ABA9C7D7B7'
}

I'm not aware of your use case but it looks like you don't really need to use sessionId. But if I'm wrong I'd love to see a minimal examples that successfully manages to use it, even with raw WebSocket messages.

My 2c on this: for simply navigating a page the sessionId is useless, however there are other cases where it's really useful. See for example this bugreport: https://bugs.chromium.org/p/chromium/issues/detail?id=1070568
Without sessionId it's impossible to attach to all targets in time. In addition, the Chromium developers are moving towards supporting sessionId only. So this is a very important feature to have IMHO.

@Niek

This is the way to get it working (you need to flatten the session):

LOL now I feel silly, I thought it was enabled by default...

My 2c on this: for simply navigating a page the sessionId is useless, however there are other cases where it's really useful. See for example this bugreport: https://bugs.chromium.org/p/chromium/issues/detail?id=1070568

That makes perfectly sense, thank you.

So this is a very important feature to have IMHO.

Yup, let me clean up a few things and I'll merge it in a few hours.

There is one problem though, events should support sessionId too so that it is possible to listen only for those belonging to one particular session.
The event filtering part should be fairly easy to implement, the only problem raises when events are registered via a promise and without any sessionId in that cases (the present case actually) there should be a way to tell from what session an event is coming from. Just adding a parameter will work for callbacks, but promises can only return one value, and changing the API (to return {params, sessionId} instead of just params) would be a breaking change...

I pushed a possible implementation in that branch.

@cyrus-and looks great, thanks!


Apollo Federation and Shield Question

Question about GraphQL Shield
I have a dummy api running Apollo Federation with 1 gateway and 2 subgraphs. Apollo Federation offers a method called __resolveReference that we can use to populate a field from one subgraph in another. I seem to be having issues getting Shield rules to work together with this method. The behavior that I am experiencing is that when I apply rules to a type let's say "User", this method does not get invoked at all.
For example, my subgraphs are User and App. the App type extends the User type at the "owner" field and it's resolved using this __resolveReference method. When I add the permissions to the User's subgraph schema using applyMiddleware this method is not called and owner returns null. If I comment out the permissions from the schema then it starts populating again.
Is this something that you guys are aware of? Is there a special way of setting up Shield to work with Apollo Federation?
Thanks for the help.

We've encountered the same issue as well. It seems that graphql-shield doesn't play well with federated graphs and the __resolveReference subgraph resolvers. There was a workaround for for an older version of Apollo-server that used the buildFederatedSchema method and solved this problem. (Fix here). But the latest version has the buildSubgraphSchema method which does not have the same options to satisfy the previous solution.

Here another one having the same issue. Not being able to access the __resolveReference if the Apollo Server subgraph has a middleware on it (by using applyMiddleware) but somehow, others subgraphs with the same config works properly with the middlewares and __resolveReference... weird though.
P.S: Will share the versions in case it's needed:
"@apollo/subgraph": "^0.4.0"
"apollo-server": "^3.6.7"
"apollo-server-express": "^3.6.7"
"graphql-middleware": "^6.0.9"
"graphql-shield": "^7.5.0"


Add patch for dtc to avoid segmentation fault on Raspberry Pi

Signed-off-by: Anton Gerasimov<EMAIL_ADDRESS>

Seems fine, but can you demonstrate to me what the problem was or otherwise explain it to me?

Passes oe-selftest.


schema validator tool: add recursive PGV checks

PGV checks will now recurse into all sub-messages, including
Any messages, allowing for full verification of the message tree.
Risk Level: Medium. Bump of PGV and PG* which had multiple regressions that needed to be fixed.
Testing: Existing test overage as well as new schema validator tool tests
Docs Changes: N/A
Release Notes: Added
Platform Specific Features: N/A

This is stacked on https://github.com/envoyproxy/envoy/pull/20111 just to test CI. I want to merge the other one first as it doesn't have the PGV bump which is riskier.

Need to work out the ASAN issues which will require another fix to PGV.

Will need https://github.com/envoyproxy/protoc-gen-validate/pull/576 to pass tests.

/rk-ping

I'm going to merge this into the other PR


refactor: Remove VK computation Pg prover flow; improve benchmark to reflect possible optimization

Closes https://github.com/AztecProtocol/barretenberg/issues/833.
Properly separate prover and verifier information in the implemented Protogalaxy protocol according to the paper. The  prover now returns a folded ProverInstance and the verifier a folded VerifierInstance. Previously the structure of the ProverInstance contained also information only relevant for the VerifierInstance (i.e. the verification key).  With this separation, the prover doesn't need to send the previous verifier accumulator through the transcript anymore.  Furthermore, this PR refactors the ClientIVC to work with this change (enabling precomputation of verification keys) as well as the recursive folding and decider verifiers. The latter required creating a stdlib counterpart of VeriferInstance since the previous verifier accumulator (\phi*) is now received from the previous folding iteration.
The PR also implements an optimization that is possible in the application client IVC scheme that was not previously reflected in our benchmarks. Namely, it is possible for the IVC provers first fold to be a function circuit-function circuit fold. This means that we can remove one kernel iteration (including the construction of the kernel's witnesses and the protgalaxy prover execution). Bechmarks follow. Note: looking at just the difference in commitment times, we have observed that the commitment cost was reduced by 4s.
Benchmarks
Before
Benchmarking lock created at ~/BENCHMARK_IN_PROGRESS.
ivc_bench                                                                                100%   16MB  65.3MB/s   00:00
2024-02-23T15:02:49+00:00
Running ./ivc_bench
Run on (16 X 3000 MHz CPU s)
CPU Caches:
  L1 Data 32 KiB (x8)
  L1 Instruction 32 KiB (x8)
  L2 Unified 1024 KiB (x8)
  L3 Unified 36608 KiB (x1)
Load Average: 5.87, 2.74, 1.08
----------------------------------------------------------
Benchmark                Time             CPU   Iterations
----------------------------------------------------------
IvcBench/Full/6      39833 ms        37395 ms            1
Benchmarking lock deleted.

After
ivc_bench                                                                                100%   16MB  61.5MB/s   00:00
2024-02-23T15:00:54+00:00
Running ./ivc_bench
Run on (16 X 3000 MHz CPU s)
CPU Caches:
  L1 Data 32 KiB (x8)
  L1 Instruction 32 KiB (x8)
  L2 Unified 1024 KiB (x8)
  L3 Unified 36608 KiB (x1)
Load Average: 0.17, 0.36, 0.17
----------------------------------------------------------
Benchmark                Time             CPU   Iterations
----------------------------------------------------------
IvcBench/Full/6      32817 ms        31790 ms            1

Benchmark results
Metrics with a significant change:

note_history_trial_decrypting_time_in_ms (5): 162 (+85%)
note_successful_decrypting_time_in_ms (8): 325 (-25%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit e63f0226 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
46,020
181,668
724,260

l1_rollup_calldata_gas
227,148
888,336
3,535,884

l1_rollup_execution_gas
321,334
1,007,784
3,757,285

l2_block_processing_time_in_ms
1,194 (-1%)
4,487
17,806

note_successful_decrypting_time_in_ms
:warning: 325 (-25%)
1,009 (+4%)
3,835 (+6%)

note_trial_decrypting_time_in_ms
39.1 (-7%)
39.9 (-62%)
129 (-27%)

l2_block_building_time_in_ms
18,428 (+1%)
72,801 (+1%)
291,619 (+1%)

l2_block_rollup_simulation_time_in_ms
13,593 (+1%)
53,639 (+1%)
215,810 (+1%)

l2_block_public_tx_process_time_in_ms
4,807 (+3%)
19,083 (+3%)
75,553 (+2%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,167 (-5%)
29,620 (-3%)

note_history_successful_decrypting_time_in_ms
2,605 (+14%)
4,778 (+3%)

note_history_trial_decrypting_time_in_ms
:warning: 162 (+85%)
215 (-13%)

node_database_size_in_bytes
17,285,200
33,181,776

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
329 (+1%)
44,664
25,409

private-kernel-ordering
196
43,729
16,289 (+1%)

base-rollup
1,462 (+1%)
129,870
933

root-rollup
83.0
4,192
825 (+13%)

private-kernel-inner
433
71,051
25,409

public-kernel-private-input
245 (+2%)
33,895 (+1%)
27,041

public-kernel-non-first-iteration
241 (+1%)
33,937 (+1%)
27,041

merge-rollup
7.79 (-1%)
2,712
933

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
16,955 (+1%)
37,661 (+6%)

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
555
1,471 (+2%)

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
0.519 (+2%)
588 (+2%)

Is it possible to extract https://github.com/AztecProtocol/barretenberg/issues/833 as its own PR?

Is it possible to extract AztecProtocol/barretenberg#833 as its own PR?

@codygunton yeah as a predecesor to this PR if you think it's worth it


JS errors in documentation examples

just run any example from docs like http://v4-alpha.getbootstrap.com/examples/navbar-top-fixed/ and open console
Uncaught Error: Bootstrap tooltips require Tether (http://github.hubspot.com/tether/)

Correct me if I'm wrong, but it seems like on actual site version everything is fine with this example and with others too. Examples from repository also do not throw any errors.

@antmatr: Only v4 is broken: http://v4-alpha.getbootstrap.com/examples/navbar-top-fixed/

You can safely ignore that error for any pages that aren't using popovers or tooltips

@wolfy1339
Not when you use gulp to mix all in 1 file

This is fixed by 95d030c.

Closing per previous comment then.


Fix compilation with musl libc

Hi @doughdemon,
Thanks for the contribution.
I remember vaguely that I used pread64 to be compliant with older versions of gcc, so let me check that again.
Possibly we will need to add a compilation time flag to choose the best flavor.
I'm sorry for the delay, and I will try to get to that asap.

Thanks for the contribution.
I remember vaguely that I used pread64 to be compliant with older versions of gcc, so let me check that again.
Possibly we will need to add a compilation time flag to choose the best flavor.

-D_FILE_OFFSET_BITS=64 should ensure that preadv uses the 64 bit
version even on old systems.

Hi @doughdemon,
I didn't have too much time recently to get to this, but I finally did this morning.
I realized that the problem was not older GCC versions, but rather something else.
There was an issue before #7 that helped me refresh my memory.
What happens is this.
When you compile the code with preadv as a 32-bit executable, everything seems to work find, but(!) you can't read the entire memory space of a 64-bit process.
By using preadv64, you are able to do so, because it expects an loff_t, which is 64-bit even for 32-bit executables.
If we use preadv, you are NOT able to do so, because it expects an off_t, which is a 32-bit value.
Unfortunately my current setup makes it difficult for me to run the exact scenario locally, so I need to spawn up a new machine to test it thoroughly. I believe I can do that today or tomorrow, and then I can try to adjust the tests accordingly. Having this test in the CI/CD pipeline could prevent some human errors.
Thanks for your patience.

No worries about the delay.
-D_FILE_OFFSET_BITS=64 should ensure that off_t is 64bit on all systems.

OK, It seems to work fine.
For future readers: As currently running 32-bit executables on a 64-bit machine is not a popular use-case, no reason to invest significantly in it. And it will be handled upon request.


e2e: switch from netshoot image to toolbox image

The test testACNPICMPSupport failed a few times because pulling the netshoot image took in excess of 90s. The toolbox image also has ping tool and is smaller than netshoot (169MB vs. 432MB). The patch switches to the toolbox image for all e2e tests.

The netshoot image can be removed from antrea's dockerhub repo after the patch is backported to all releases in maintenance.

/test-ipv6-only-e2e
/test-e2e
/test-ipv6-e2e

it may be a good opportunity to upgrade the toolbox tag used for the tests from 1.1-0 to 1.2-1
can we get rid of all references to the netshoot image and remove createNetshootPodOnNode, or do we still have e2e tests that require this image specifically?

Sure, all suggestions have been applied. Thanks.

/test-e2e
/test-ipv6-e2e
/test-ipv6-only-e2e
/test-multicast-e2e

/test-e2e
/test-ipv6-e2e
/test-ipv6-only-e2e
/test-multicast-e2e

/test-multicast-e2e

/test-e2e
/test-ipv6-e2e
/test-ipv6-only-e2e
/test-multicast-e2e
/skip-conformance
/skip-networkpolicy

/test-multicast-e2e


Update storage-considerations.md

based on my latest test and my discussion with samuelzhang we do not have such limitations now

@ggailey777
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


v0.299.0

Bumping version to v0.299.0 to build update including BCNL mmol/L changes.
@jebeck - Can I please get a review?

I'm a bit confused. Where's the cherry-picked commit? Already on master but then you didn't tag (as I do all the time 😜). Just making sure everything's straightened out!


adaptive lighting and motion sensors

Version information: 1.0.14
Description:
I have a motion sensor that turns on lights when someone enters the room. With adaptive lighting turned off for that area, the lights fade in gently. If adaptive lighting is turned on, the color and/or brightness seem to jump right away to whatever state adaptive lighting believes they should be.
I have set initial_transition to 45 in the area config.
I've also tried adaptive_lighting.apply before turning on the light with turn_on_lights set to false and transition set to 45.
Any ideas?

Hey @anoblet, @desertblade,
this is now part of the Roadmap for Version 2.
Feel free to vote on the point which will fix this:

https://github.com/basnijholt/adaptive-lighting/discussions/291#discussioncomment-2886261
https://github.com/basnijholt/adaptive-lighting/discussions/291#discussioncomment-2886273


Futurenet

fix deployment scripts
update to new blend-sdk

Note - I can't test this yet against a standalone network. Instead of dealing with things already existing on futurenet, I'm gonna opt to push a "should work" script and do formal testing once new, working standalone containers are deployed.


Support multiline editing

Fixes #3047
Problem:
Editing text with multiple lines doesn't really work as newlines get chomped when exiting text edit mode.
Fix:

Convert the newlines to
 tags
Render the
 tags as newlines
Join the multiple fragments correctly per the two above

Note: I'm trying to test this, but unfortunately it's quite tricky because

execCommand alters the HTML of the element, not really sure why
triggering text input as key presses doesn't seem to work

if anybody has good ideas, please do tell :)

Note: I'm trying to test this, but unfortunately it's quite tricky because

execCommand alters the HTML of the element, not really sure why
triggering text input as key presses doesn't seem to work

if anybody has good ideas, please do tell :)

Yes, I also experienced that key presses doesn't work in tests (that is why I chose to use execCommand)


commander registers apps from other pools with shuttle

In a pool with no apps, commander will still register all the running backends in other pools with shuttle

This is a remnant from expecting all apps to access localhost:port for any galaxy apps, though we now have the app.galaxy internal domain.
Should both remain as valid methods?


Configuring Managed Identity

Type of issue
Missing information
Description
We see option to configure access key for the EventGrid using KeySettingName but how do we configure EventGrid that use Managed Identity based auth.
Page URL
https://learn.microsoft.com/en-us/dotnet/api/microsoft.azure.webjobs.extensions.durabletask.eventgridnotificationoptions?view=azure-dotnet
Content source URL
https://github.com/Azure/azure-docs-sdk-dotnet/blob/master/xml/Microsoft.Azure.WebJobs.Extensions.DurableTask/EventGridNotificationOptions.xml
Document Version Independent Id
ec66102e-568e-9087-b442-6c9399e23ff1
Article author
@azure-sdk
Metadata

ID: e7b049c9-bbe7-d26d-6e98-a026d93a6610
Service: azure-functions

This issue has been transferred to the repository where the Microsoft.Azure.WebJobs.Exentions.DurableTask library is maintained as #2924.


relative url_for with a blueprint mounted two times

Based on blueprint concept, I expected it to handle relative url_for nicely:
from flask import Blueprint, Flask, url_for

bp = Blueprint('foo', __name__)

@bp.route('/')
def func():
    return url_for('.func')

app = Flask(__name__)
app.register_blueprint(bp, url_prefix='/foo')
app.register_blueprint(bp, url_prefix='/bar')

client = app.test_client()
print client.get('/foo/').data
print client.get('/bar/').data

Both prints write the URL to the first blueprint registered (/foo/). Is it possible to mount two times the same blueprint and make relative url_for work? Is this behaviour expected?

Hmm, this is definitely unexpected behavior, but I'm not sure what we can do about it. The problem is that the endpoint become foo.func, and while Werkzeug knows all the rules associated with an endpoint, it only uses the first one to build with.
There's no information about which path to prefer. We'd need to send the url prefix to MapAdapter.build and use that when deciding which rule to use for the endpoint.
There's also no way to know what other prefixes a blueprint was registered under, so we can't know a prefix to strip and replace with the current blueprint.

This is really confusing. The same Register a blueprint multiple times on an application with different URL rules line in the docs let me to expect that utilities like url_for would still work, but they don't.

Hello all :) Still no solution for this?


[bug]: Vaultwarden LAN URL takes you back to Embassy login screen.

Prerequisites

[X] I have searched for existing issues that already report this problem, without success.

EmbassyOS Version
0.3.0
Device
Laptop/Desktop
Device OS
MacOS
Device OS Version
10.14.6
Browser
Firefox
Browser Version
94.0.2
Current Behavior

Expected Behavior
Interface for Vaultwarden should load (works fine using Tor interface)
Steps to Reproduce
0.3.0 -> Installed Vaultwarden -> Launch LAN interface
Anything else?
No response

this is an nginx problem for sure. if it was an mDNS thing it wouldn't resolve at all.

This is an issue in how we handle the port mapping. I need to change how the different aspects of the port mapping are written to the nginx config.

@BitcoinMechanic this should be ready for testing as of b270011131aea8c325c8b2bb9f084eddab11f217

Tested on a normal build (wasn't migrating). It worked as expected. I don't think migrating is necessary to test here.


Set Pinning - Doesn't send the folder name

OS: macOs
Version of IPFS Desktop: 0.24.0

Describe the bug
When pinning a folder to a remote service through the Pinning Service API, the client sometimes does not send the name over.
The payload of the POST request sent contains the cid and origins but no name.
This has been raised by a user on a web3.storage  issue.
To verify it wasn't a problem in web3.storage implementation I tested this against a development instance of the service and logged Add pin payload to confirm no name is provided.
Unfortunately, this happens randomly, it sometimes does and sometimes doesn't, and I couldn't quite figure out a consistent way to reproduce it.
To Reproduce
Steps to reproduce the behavior:

Go to 'settings'
Add web3.storage
Go to the file list
Click on the 3 dots on the right -> set pinning to the newly added service
Navigate to https://web3.storage/account/?table=pinned
See file appearing with "no name"

Expected behavior
It should send the name.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Please be aware that in order to be able to be able to pin on Web3.storage you need to have the PSA enabled, see docs.
In order to see the table you need to have at least a succesful pin.
Example of payload sent:
{
    "cid": "QmeWZGxrwPyR532r4HTHUwWo6zJPZKxzPMnsm3Smbi2TDv",
    "origins": [
        "/ip4/<IP_ADDRESS>/tcp/4001/p2p/12D3KooWF59pZMi2q4qqqz6Mimi5oULWFQABYGXSQjNkR6sKC1kD",
        .. more origins
    ]
}

@flea89 thanks so much for submitting this issue and all the details. I have experienced this issue myself, with a few others reporting it to me as well. I had this on my backlog but didn't have a tracking item for it yet, so we will use this issue.
Unfortunately, we've got a few high priority deadlines that need taken care of before we can look into this. To unblock yourself, can you see if adding the pinning service as a custom service resolves your issue?


Feature flesh out

Added support for DELETE /memberships /webhooks and /rooms.
Added webhooks for membership created/deleted
Added support for personID in the body of a POST to /messages.  This will create a one-on-one space as needed.

Upon further review you are right!  Removed the filter so webhooks are sent to the creator of the message.


Settings

Add screen for Settings, implement settings cards. Add navigation to each. Start prefilling General Settings with CounterValue, lock options.
Start using i18n in common json.
Parts of the app affected
Settings screen

Settings
General Settings

NOICE


Sandbox operations no longer work (`require': cannot load such file -- macho (LoadError))

[x] Confirmed this is a problem with Homebrew/brew and not one or more formulae? If it's a formulae-specific problem please file this issue at https://github.com/Homebrew/homebrew-core/issues/new
[x] Ran brew update and retried your prior step?
[x] Ran brew doctor, fixed as many issues as possible and retried your prior step?
[x] Ran brew config and brew doctor and included their output with your issue?

Hi,
any installation or post-install command involving the sandbox fail since a recent update. This did not happen yesterday, and my system configuration did not change.
This also happens with a clean Homebrew installation.
# oliver @ Windshear in ~ [17:01:15] C:1
$ brew install cmake
==> Downloading https://homebrew.bintray.com/bottles/cmake-3.8.1.sierra.bottle.tar.gz
######################################################################## 100.0%
==> Pouring cmake-3.8.1.sierra.bottle.tar.gz
==> Using the sandbox
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- macho (LoadError)
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/os/mac/mach.rb:1:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/os/mac/pathname.rb:1:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/extend/os/mac/hardware/cpu.rb:1:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/extend/os/hardware.rb:2:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/hardware.rb:123:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/os/mac.rb:1:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/os.rb:15:in `<module:OS>'
	from /Users/oliver/.local/Library/Homebrew/os.rb:1:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/extend/os/emoji.rb:1:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/emoji.rb:14:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/utils.rb:2:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/extend/pathname.rb:4:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/global.rb:3:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/oliver/.local/Library/Homebrew/postinstall.rb:3:in `<main>'
Warning: The post-install step did not complete successfully
You can try again using `brew postinstall cmake`
==> Caveats
Emacs Lisp files have been installed to:
  /Users/oliver/.local/share/emacs/site-lisp/cmake
==> Summary
/Users/oliver/.local/Cellar/cmake/3.8.1: 2,208 files, 29.2MB

# oliver @ Windshear in ~ [17:01:29] C:1
$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: Your Homebrew's prefix is not /usr/local.
You can install Homebrew anywhere you want but some bottles (binary packages)
can only be used with a /usr/local prefix and some formulae (packages)
may not build correctly with a non-/usr/local prefix.

Warning: Broken symlinks were found. Remove them with `brew prune`:
  /Users/oliver/.local/bin/blender
  /Users/oliver/.local/include/openssl
  /Users/oliver/.local/share/postgresql95
  /Users/oliver/.local/share/zsh/site-functions/_brew_services

# oliver @ Windshear in ~ [17:05:35] C:1
$ brew config
HOMEBREW_VERSION: 1.2.0-50-g3e4547f52
ORIGIN: https://github.com/Homebrew/brew.git
HEAD: 3e4547f52e7ebec633f8bfefc8a396d944edf908
Last commit: 2 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 9c4f788f512c3fdb9f83dace59b2194a778c13bd
Core tap last commit: 13 hours ago
HOMEBREW_PREFIX: /Users/oliver/.local
HOMEBREW_REPOSITORY: /Users/oliver/.local
HOMEBREW_CELLAR: /Users/oliver/.local/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://homebrew.bintray.com
CPU: quad-core 64-bit ivybridge
Homebrew Ruby: 2.0.0-p648
Clang: 8.1 build 802
Git: 2.11.0 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Perl: /usr/bin/perl
Python: /usr/bin/python
Ruby: /usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
Java: 1.8.0_111, 1.6.0_65-b14-468
macOS: 10.12.4-x86_64
Xcode: 8.3.2
CLT: <IP_ADDRESS>.1.1492020469
X11: N/A

Can you brew update and try again?

Had the same problem with:
Homebrew 1.2.0-50-g3e4547f52
Homebrew/homebrew-core (git revision 9c4f7; last commit 2017-05-06)
But solved by brew update again.

Thanks, this seems to be resolved in the most recent version.

Would it be possible to prevent brew update from updating to a broken master? E.g. users should not end up with a version of master where the build has failed. I haven't given thought for how to implement this in practice, maybe push via a different branch (develop?) + autopush master when CI is successful.
I suffered this yesterday and ended up setting HOMEBREW_NO_AUTO_UPDATE=1 for my environment (I would prefer not to, but not being able to revert when homebrew breaks is worse).

The vast majority of users are not on master but are on the latest stable tag. Those who are on master have either set HOMEBREW_DEVELOPER=1 in their environment or run one of the developer commands, which will add
[homebrew]
	devcmdrun = true

to $(brew --repo)/.git/config.

users should not end up with a version of master where the build has failed.

They didn't, the build passed.

The vast majority of users are not on master but are on the latest stable tag. Those who are on master have either set HOMEBREW_DEVELOPER=1 in their environment or run one of the developer commands, which will add

Thank for pointing this out, it seems I have devcmdrun = true. However, I was completely unaware of this. Enabling this by simply running a dev command seems very unexpected.

They didn't, the build passed.

Sorry for my lack of knowledge of the internals, I was looking at this travis status: https://travis-ci.org/Homebrew/brew/builds/229664529 (which failed). Either way, looks like the problem was devcmdrun, which I have not knowingly enabled.
Is there any way I can prevent devcmdrun = true from being enabled in future?

I think arguably we should respect a manually set devcmdrun = false though I don''t think that's currently the case.

Also, setting HOMEBREW_UPDATE_TO_TAG=1 may work, though I haven't tested that.

Thanks @ilovezfs, I've set both for now 😄 .

However, I was completely unaware of this. Enabling this (and thus the master branch) by simply running a dev command seems very unexpected.

It's an intentional segmentation of our users. We need to be able to test the master branch on a subset of our more technical users.

Also, setting HOMEBREW_UPDATE_TO_TAG=1 may work, though I haven't tested that.

Yep, export HOMEBREW_UPDATE_TO_TAG=1 is your best bet to avoid this behaviour.

It's an intentional segmentation of our users. We need to be able to test the master branch on a subset of our more technical users.

It makes sense, but I would have liked to be aware that I had opted into this =/. Not sure if I was ever prompted and I've probably been testing master for a loong time. That way it's less surprising and easier to fix when everything suddenly breaks.

Yep, export HOMEBREW_UPDATE_TO_TAG=1 is your best bet to avoid this behaviour.

👍

It makes sense, but I would have liked to be aware that I had opted into this =/. Not sure if I was ever prompted and I've probably been testing master for a loong time. That way it's less surprising and easier to fix when everything suddenly breaks.

I appreciate that but it's intentional that we don't prompt people for this. We want you to be testing this because it helps us.

I appreciate that but it's intentional that we don't prompt people for this. We want you to be testing this because it helps us.

That's very sneaky, but it's your project, I love Homebrew so can't complain. I guess my point is that I would happily volunteer, however, this behaviour was a betrayal of my trust towards the software and thus I feel reluctant of enabling it again (due to the breakage).

That's very sneaky, but it's your project, I love Homebrew so can't complain. I guess my point is that I would happily volunteer, however, this behaviour was a betrayal of my trust towards the software and thus I feel reluctant of enabling it again (due to the breakage).

It's not "sneaky" and it's not my project. We don't have adequate test coverage to be able to have whatever is on master tagged without more widespread testing on our CI and our more technical users. I've been maintaining this project for 8 years and although I don't expect anyone to defer to my knowledge of software development I'd ask people to do so on my knowledge of maintaining Homebrew: there's literally no-one who has been doing that longer than me.
This model is the best balance for all our users and it allows us to get more features and more fixes out to people far quicker than we did before. The consequence is: sometimes things break and when we do we drop whatever is going on in our lives to try and fix it ASAP. You were personally inconvenienced by your setup being broken for a few hours on a Sunday while I frantically worked through the day to fix the issue and you had a workaround to avoid being blocked. I'd ask that you have either cut the project a little more slack or consider using other projects like MacPorts that may better meet your needs.

Sneaky:

behaving in a secret and usually dishonest manner
done in a secret and dishonest manner

You're right, sneaky was a bad word, I don't consider it dishonest. I totally stand by the first part of the words meaning though!
Also, I'm very sorry, I did not mean to offend, or complain about the project. I simply wanted to provide my (an advanced users) point of view, for you to do with what you please.
I appreciate the work you do, I'll just leave it at that.

You're right, sneaky was a bad word, I don't consider it dishonest. I totally stand by the first part of the words meaning though!
Also, I'm very sorry, I did not mean to offend, or complain about the project. I simply wanted to provide my (an advanced users) point of view, for you to do with what you please.
I appreciate the work you do, I'll just leave it at that.

I genuinlely appreciate the apology and sorry for being a hard-ass earlier ❤. Sounds like we all have an acceptable outcome now.


Removed authentication domains from CredentialRequest

Code changes to implement Proposal from issue #5

Removed authentication domains from the CredentialRequest (Updated protobuff as a non-backwards compatible change to leave a cleaner API.  My rational is that until this API hits v1 breaking changes are okay.)
Update test app and demo providers to conform to new API changes.
Updated specification to reflect API changes.
Fixed Trapdoor demo provider's CredentialQueryReceiver implementation to match it's documentation.

Codecov Report

Merging #11 into master will decrease coverage by -0.21%.
The diff coverage is 63.63%.

@@             Coverage Diff              @@
##             master      #11      +/-   ##
============================================
- Coverage     66.03%   65.83%   -0.21%
+ Complexity      286      285       -1
============================================
  Files            41       41
  Lines          1702     1686      -16
  Branches        204      204
============================================
- Hits           1124     1110      -14
+ Misses          513      510       -3
- Partials         65       66       +1

Impacted Files
Coverage Δ
Complexity Δ

.../org/openyolo/spi/BaseCredentialQueryReceiver.java
63.63% <0%> (-14.15%)
2 <0> (ø)

api/java/org/openyolo/api/RetrieveRequest.java
91.17% <100%> (+8.22%)
10 <2> (ø)
:x:

...pi/java/org/openyolo/api/AuthenticationDomain.java
81.35% <0%> (-5.09%)
20% <0%> (-1%)

Continue to review full report at Codecov.

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


Remove example using the durability API that has been removed.  This …

…will be replaced later with a new example using the new API.
Output of "lein run -m clara.examples":
Shopping examples:
VIP shopping example:
10 % :vip discount???
Summer special and widget promotion example:
20 % :summer-special discount???
Free :lunch for promotion :free-lunch-with-gizmo
Free :widget for promotion :free-widget-month

JavaBean Shopping examples from Clojure:
Promotion: Awesome promotion for our favorite VIP!

JavaBean Shopping examples from Java:
Query result: DESCRIPTION: Awesome promotion for our favorite VIP!

Validation examples:
Failed validation:
Validation issue:  HVAC repairs must include a 27B-6 form.
Validation issue:  Insufficient time prior to due date of the large order.
Validation with appropriate client tier and paperwork.

Sensor examples:
Reducing speed of  #clara.examples.sensors.Device{:id 456, :location :room-1}
Reducing speed of  #clara.examples.sensors.Device{:id 123, :location :room-1}
ALERT: temperature of 130 at :room-1 in sector :sector-5
Increasing speed of  #clara.examples.sensors.Device{:id 123, :location :room-1}
Increasing speed of  #clara.examples.sensors.Device{:id 456, :location :room-1}

Discounts when a customer is both a NewCustomer and a ValuedCustomer:  ({:?order-id 1, :?amount 20} {:?order-id 1, :?amount 5} {:?order-id 1, :?amount 5})
Discounts when the customer is noted as new twice in the session:  ({:?order-id 1, :?amount 5} {:?order-id 1, :?amount 5})
Discounts when there is a CustomerAppreciationDay, but it does not match the CurrentDay:  ()
Discounts when an Order matches both branches of clojure.core/or :  ({:?order-id 3, :?amount 10})

Boolean expression examples:
Discounts when a customer is both a NewCustomer and a ValuedCustomer:  ({:?order-id 1, :?amount 20} {:?order-id 1, :?amount 5} {:?order-id 1, :?amount 5})
Discounts when the customer is noted as new twice in the session:  ({:?order-id 1, :?amount 5} {:?order-id 1, :?amount 5})
Discounts when there is a CustomerAppreciationDay, but it does not match the CurrentDay:  ()
Discounts when an Order matches both branches of clojure.core/or :  ({:?order-id 3, :?amount 10})

Fact type options examples:
Query result with a fact of type :temperature-reading :  ({:?good-weather false})
Query result with a custom ancestors function and a fact with a type that descends from :temperature-reading :  ({:?good-weather false})

Discussed previously on https://github.com/cerner/clara-examples/issues/8


fix: allow artifact gc to delete directory. Fixes #12857

Fixes #12857
Motivation

We see error The specified key does not exist when gc artifact are not compressed and is directory
Modifications

Determine if artifact is dir and delete accordingly (used in artifact gc)

Verification

Test log
time="2024-05-25T03:16:16.108Z" level=info msg="S3 Delete artifactttt: key: fanout/collected-other-datasets/yo-test-zl4wk/"
time="2024-05-25T03:16:16.108Z" level=info msg="Creating minio client using static credentials" endpoint="minio:9000"
time="2024-05-25T03:16:16.112Z" level=info msg="Listing directory from s3" bucket=my-bucket endpoint="minio:9000" key=fanout/collected-other-datasets/yo-test-zl4wk/
time="2024-05-25T03:16:16.113Z" level=info msg="Deleting object from s3" bucket=my-bucket endpoint="minio:9000" key=fanout/collected-other-datasets/yo-test-zl4wk/hello-world.txt
time="2024-05-25T03:16:16.115Z" level=info msg="Deleting object from s3" bucket=my-bucket endpoint="minio:9000" key=fanout/collected-other-datasets/yo-test-zl4wk/hello-world2.txt

@tczhao do you want to re-trigger the CI, and then it sounds like this can be merged?

CI doesn't need to be retrigerred as only the Windows tests are failing which are not required to pass

CI doesn't need to be retrigerred as only the Windows tests are failing which are not required to pass. Can just hit merge

ahh, thanks


Foreground Service closes after app swiped up/closed from multitasking panel

The plugin works fine when the app is focused or in the background. But once, once the app is closed by swiping up from the multitasking area, the notification is removed.
APP in Focus:

App In Background but not closed:

App Closed from muli-tasking view:

Note: The white dot is the notification
Is this normal behavior? Shouldn't it keep the app alive even after swiped up?
Objective of the app: Prevent the app from being killed to ensure timely alarm firing by the android alarm manager
Device: Oneplus 7 - Android 11

This is intentional behavior introduced by #10. As closing the app is an intentional action by the user, this intent has to be respected by apps. The isolate the app runs in should be killed either way, so keeping the foreground notification probably does not achieve the desired effect.
I don't quite understand the reason you need the app running in the background in order for the alarm manager to work.

I see. Thank you for clarification.
The thing is Android probably kills my app process after it has been closed for few days. It is a prayer notification app, so notifying prayer time everyday and calculating the next time should continue happening even if user does not open the app for weeks. But, Alarm manager does not fire alarms on due time. Hence, I wanted to keep a process running to make sure it keeps running. Any help would be appreciated 🤠


Fix missing line comment

There was a missing '#' sign in front of comment, this is causing errors when trying to import the repo.

@googlebot I signed it!

@googlebot I signed it!

@michellelivne Could you please merge this pull request? Wanted to propose the same change. Your package is broken and cannot be imported.

Thank you very much!


Feat precommit hooks

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation
[ ] 🧑💻 Refactor
[ ] ✅ Test
[ ] 🤖 Build or CI
[ ] ❓ Other (please specify)

Related Issue
Example: Fixes #123
Describe this PR
A brief description of how this solves the issue.
Screenshots
Please provide screenshots of the change.
Alternative Approaches Considered
Did you attempt any other approaches that are not documented in code?
Review Guide
Notes for the reviewer. How to test this change?
Checklist before requesting a review

📖 Read the Tasking Manager Contributing Guide: https://github.com/hotosm/tasking-manager/blob/develop/docs/developers/contributing.md
📖 Read the HOT Code of Conduct: https://docs.hotosm.org/code-of-conduct
👷♀ Create small PRs. In most cases, this will be possible.
✅ Provide tests for your changes.
📝 Use descriptive commit messages.
📗 Update any related documentation and include any relevant screenshots.

[optional] What gif best describes this PR or how it makes you feel?

Created for test purpose only


Overzealous zone/domain name compliance checks in Unbound > Query Forwarding

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[X] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
The UI does not allow the configuration of a query forwarding if the zone name starts with an underscore. Unfortunately this is frequently the case with special Microsoft AD integrated zones - wich are in turn prime candidates for query forwarding.
To Reproduce
Navigate to Service > Unbound > Query Forwarding, try to add an entry like in my screen shot.
Expected behavior
The entry should be permitted.
Describe alternatives you considered
There is no alternative ;)
Screenshots

Relevant log files
none
Additional context
The validity of these zone names is frequently the topic of debate. My reading of the relevant RFCs is that underscore in hostnames is not allowed, but perfectly well so in zone names or e.g. SRV records. Also Microsoft does (surprise!) have a history of adhering to standards quite tightly in the infrastructure (DNS, LDAP, Kerberos, ...) areas.
Environment
OPNsense 24.1.7_4

That was quick! Thanks!

@pmhausen it's a (very) small change, let's ask @fichtner to pull it in when he has time :)

Ok how about tomorrow?

While you are at it - I guess Unbound > Overrides > Domain Overrides deserves the same treatment and possibly Host Overrrides, too.

@pmhausen since host and domain are split there and validations underneath differ a bit, better open another ticket for that when needed. rfc2181 removes almost all constraints from the field, which might have other downsides in these cases.

Domain Overrides IMHO has exactly the same constraints as Query Forwarding. I was a little bit puzzled by the former still existing. Wasn't the intention to remove that (legacy) part of the menu in favour of Query Forwarding?
Anyway - Host Overrides should follow the standard for host names. Domain Overrides is just another name for essentially Query Forwarding.
Kind regards,
Patrick

Domain Overrides IMHO has exactly the same constraints as Query Forwarding. I was a little bit puzzled by the former still existing. Wasn't the intention to remove that (legacy) part of the menu in favour of Query Forwarding?

yes, so better to leave it alone for now (https://github.com/opnsense/core/issues/7243)


remove Single-feed mode

As mentioned in https://github.com/umputun/feed-master/issues/70, no-conf (single feed) mode is no longer needed and can be removed.

closing in favour of https://github.com/umputun/feed-master/pull/81


Start setting blockID to support logging human feedback

Add the BlockID to the proto
Instrument the Agent.Generate RPC to lock the blockIDs of any generated blocks
Instrument the Executor.Execute RPC to log the IDS of any blocks executed
Configure OTEL so that trace and spans get set. We will use this to link the log entries
associated with a trace.
Add the ability to send traces to Honeycomb

Related to #7

Since the proto change creates an incompatibility between the frontend and backend we shouldn't release this until we've fixed the issues with pinning assets.

The 0.0.4 is now pinning the commit of the image.
2024-04-12T17:22:43.441-0700	INFO	cmd/version.go:41	binary version	{"version": "0.0.4", "commit": "51a604f692eb0803c7d2dcc00fac7709df1fa822", "date": "2024-04-13T00:11:00Z", "builtBy": "goreleaser"}
2024-04-12T17:22:43.441-0700	INFO	cmd/assets.go:63	Downloading assets	{"tag": "51a604f692eb0803c7d2dcc00fac7709df1fa822"}
2024-04-12T17:22:43.441-0700	INFO	assets/manager.go:81	Downloading assets	{"downloadDir": "/var/folders/pc/wqw4h6c54_x2s33qgmdzf9_w0000gn/T/temporaryAssets947028670"}
2024-04-12T17:22:43.441-0700	INFO	assets/manager.go:116	Asset already exists	{"assetDir": "/Users/jlewi/.foyle/assets/vscode", "name": "vscode", "source": "ghcr.io/jlewi/vscode-web-assets"}
2024-04-12T17:22:43.441-0700	INFO	assets/manager.go:126	Downloading asset	{"name": "foyle", "source": "ghcr.io/jlewi/foyle-vscode-ext", "tarBall": "/var/folders/pc/wqw4h6c54_x2s33qgmdzf9_w0000gn/T/temporaryAssets947028670/foyle.tar.gz"}
2024-04-12T17:22:45.138-0700	INFO	assets/manager.go:149	Unpacking tarball	{"srcTarball": "/var/folders/pc/wqw4h6c54_x2s33qgmdzf9_w0000gn/T/temporaryAssets947028670/foyle.tar.gz", "dest": "/Users/jlewi/.foyle/assets/foyle", "stripPrefix": "foyle"}
2024-04-12T17:22:45.147-0700	INFO	application/app.go:103	Shutting down the application

So this is safe to merge.


Enhancing fallback referrer

Problem
As many apps refer via a referrer parameter in the url called ref but ackee uses source as the parameter this leads to many refs untracked.
Solution:
Create a alias of the source param called ref so if any app referrs via the ref param it will also get tracked.
Ik that there is a fallback referrer but this does not catch all refs.
I see if I have some spare time to create a PR. :)

We already had support for ref, but I've removed it: https://github.com/electerious/Ackee/issues/169#issuecomment-753495016
The problem was that it's overwriting the referrer, but I agree that supporting ref is a good idea. Especially because some browsers are sending an empty referrer. I need to check how the current implementation works. It should still use referrer even available. ref shouldn't be able to overwrite referrer.


Merge of predix_extensions_75.18.1 into rc_75.18.3

Merging predix_extensions_75.18.1 into rc_75.18.3 to deploy into EKS and test it.

Looks good to me, but will let @irinaepshteyn approve,


select2 option to not include search string in results

I would like to remove the search 'term' from appearing in the search result list.

How can I do this? Is there an option for this built in?

Do you mean removing the first term (the exact match)? You can control how search results are matched using the matcher option.
Or removing it from every result (so it only displays the suffix)? That'd require some magic in the results adapter, but could probably be hacked with a custom sorter being passed in.

No, I just simply dont want to include the search string in the results from ajax. That list of results is populated by ajax. When I typed "tes" in the search, it appends "tes" as the first result, I do not want it to do this.
Here is the code for the select2:
    select.select2({
      minimumInputLength: 2,
      tags: [],
      placeholder: "Search for a member",
      ajax: {
          url: "./php/testing/module/contact-drop-module/php/user-name-search.php",
          dataType: 'json',
          type: "POST",
          async: false,
          quietMillis: 50,
          data: function (term) {
              return {
                  'term': term.term //search term
              };
          },
          error: function(data){
            alert("ERROR");
          },
          processResults: function (data) {
              return {
                  results: $.map(data.users, function(index, val) {
                      return {
                          id: index,
                          text: index,
                          name: index,
                          slug: index
                      }
                  })
              };
          }
      }
    });

    $(".search-contact").select2("val", "");

When I typed "tes" in the search, it appends "tes" as the first result

This is because you are using the tags option. It doesn't sound like you actually need it.

Nope that is not the problem... I set tags:"false" and it is still appending the search string to the search results. Do you understand what I am asking?
As I type "tes" (search string), it gets appended to the list as "tes", I do not want it to append the search string, I only want it to display the actual results from ajax....

tags:"false" doesn't actually disable tags, as "false" is truthy in JavaScript.
> var x = "false";
> !x
< false
> !!x
< true

Try setting tags: false (note the missing quotes) or just don't include it in your options. The tags option will, by default, put the string entered as a search term into the results in the first position. If you do not want this, don't use tags.

I just tried this suggestion but it didnt change anything. tags: false,
On Apr 14, 2015 7:08 PM, Kevin Brown<EMAIL_ADDRESS>wrote:tags:"false" doesn't actually disable tags, as "false" is truthy in JavaScript.

var x = "false";
!x
< false
!!x
< true

Try setting tags: false (note the missing quotes) or just don't include it in your options. The tags option will, by default, put the string entered as a search term into the results in the first position. If you do not want this, don't use tags.
—Reply to this email directly or view it on GitHub.

you should remove the tags as option when calling selec2
check the docs
https://select2.github.io/options.html#tags


Update the Wiki with details based on v3.0.0 documentation

We need to do this after tagging the release but prior to publishing it to rubygems.org. That way when people get the new major version and use it they have ready to go documentation to help them.

This has been completed.


Enable tearing out tabs to create new windows

⚠ targets #14901 ⚠
This is the last one 🎉

Map

[ ] #14825
[ ] #14843
[ ] #14851
[ ] #14866
[ ] #14901
[ ] #14935 <---- YOU ARE HERE

Summary
In the final chapter of our tale, we present a PR of great significance. It grants the power to tear tabs from their windows and create a new window where they may be dropped, one not necessarily of the Terminal sort. The dimensions of the original window are transferred to this new abode, and its placement on the screen is determined by the user's placement of the tab.
This is the last main chapter of the tear-out saga, and the dawning of the new age.
Closes #5000
Related to #1256
Detailed description
We're really leaning on the existing RequestNewWindow event that the monarch already had - honestly, most of that was so simple that it could have just been in the parent PRs. We just need to add new support for passing in a content blob of json, and making sure the Terminal always uses that over commandline args. Easy enough.
There's a bit of wackiness here in adjusting the positioning just right so that the new window appears in the right place, but it feels... pretty good all things considered. I'll grab a gif when my machine is less borked.


Better guidance as to what to do after you've installed Datasette

Feedback from Discord:

hello, love the project and came for help and to point out a possible gap in the docs. starting with "getting started" and "installation" every thing looks great, but then there's a giant leap after you have it installed and running. from the user perspective of "i have a csv of set of csvs that i want to turn into a table(s), what do i do next?" --- so something like maybe a page for creating your first project should go after "installation".

This will get a whole lot easier if I implement the ideas in here:

#1163

This tutorial is relevant: https://datasette.io/tutorials/clean-data - maybe for the moment I can link to that from the documentation in more places?


[Accessibility] Loading Info is Not Converyed When Dialog is Open

Description
Loading info of task module should be conveyed by screen reader
Expected Behaviour
Given a user is using screen reader, when user open a task module dialog and it is loading, then the loading info should be converyed
Actual Behaviour
Nothing relevant will be read by screen reader when dialog is loading
Card Json
NA

Thank you for reporting this issue, we will check this issue and update you.

We are also able to repro this issue, we have raised a bug for the same. We will keep you posted on the updates. Thank you.


[publish-artifacts] Only bump version in PR builds

Fixes Azure/typespec-azure#3595

Closing in favor of #2434.  There is no reason to publish from non-PR builds, since commits to main are already published to npmjs.com.


🐛 :: apply korea time

Hello, I'm a user who uses your Hugo service holly. I noticed a problem while using the theme holly. In Korean time, when I wrote a blog and built it, I had a problem that said:date_medium. To solve this problem, instead of the value:date_medium
<time datetime="{{ .Date }}">{{ .Date.Format "2006년 1월 2일" }}</time>
                {{- else if .Lastmod -}}
                <time datetime="{{ .Lastmod }}">{{ .Lastmod.Format "2006년 1월 2일" }}</time>

It needs to be set in Korean like this.
It was different from the Hugo version you defined in vercel and netilfy, which are the vape tools you often use in your second routine. In other words, it wasn't the latest version. I solve this problem.
Thank you for making a simple design blog template holi.

Thank you for your contribution. However, this is not a general use case but an opinionated setup, so the PR will not be accepted.

okay. Have nice a day! You made holy skin for thank you!


chore(deps): upgrade jenkins-x/jx3-pipeline-catalog to version 3.2.276

from: https://github.com/jenkins-x/jx

/close


prop-types should cover props in setState() too

As specified in React docs:

It's also possible to pass a function with the signature function(state, props) => newState.

So when we use something like this.setState((state, props) => {}), that props argument must be covered by rule prop-types too.

I just going to made another useless comment just to point out this is badly needed, as sometimes you need to access to props to set the state or something, and the linter will show this as an error (For your point, I realice that I did not actually use the props to set the state, but for resolve the state value).
However, with #943 this would be necessary.


Added compat for Hospitality: Storefront

Currently waiting for MPAPI to update, as well as Multiplayer to update and implement the new API.
Similarly to Cash Register compat, this was ready and waiting for update. May as well make a PR in case I ever end accidentally up losing those files.

Should be safe to merge. Also, just in case - merged master branch in.


How to use this library

HI @benjgrad How to use this library . I have created a component and i want to show animations on scroll how can i achieve this .   Like what would i have to write in the component?

Hi @zeeshan-algo, you just need to specify the classnames mentioned in the readme, and shown in the demo site. The classnames are added as the user scrolls past the threshold. If you want a specific transition, add the transition to that class.


process.env properties are undefined when used with modes

Adding the VUE_CLI_KEEP_TEST_ATTRS to a .env.mode file and loading it with --mode mode does not work. The process.env.VUE_CLI_KEEP_TEST_ATTRS and process.env.NODE_ENV are undefined.
Moving the check into the main function solves this issue but I'm not sure if there are any other consequences from doing that - seems like it should be fine though.
Adding the variable directly (using VUE_CLI_KEEP_TEST_ATTRS=true vue-cli-service build for example) work just fine.

Hey @autumnwoodberry,
only saw this now, apologies.

The process.env.VUE_CLI_KEEP_TEST_ATTRS and process.env.NODE_ENV are undefined.

Where are they undefined?

@LinusBorg
At this point https://github.com/LinusBorg/vue-cli-plugin-test-attrs/blob/develop/index.js#L13-L19 both the process.env.VUE_CLI_KEEP_TEST_ATTRS and process.env.NODE_ENV are undefined.

Right, I have to move those into the plugin function. Thanks!


OLS-157: Proper distribution of endpoints unit tests

Description
Just moving tests around to reflect the main package (unit tests should mirror that).
No code is changed here.
Type of change

[x] Refactor

/lgtm


Develop a plugin interface to add new downloaders

We would like to make data services more accessible, but we don't want earthaccess to be coupled with the APIs of all the different services.
It was suggested by Bri that we add support for asynchronous ordering as an access method. @andypbarrett suggested support for NSIDC subsetter. It was suggested by Joseph that a plugin system would be a good way to decouple this significant complexity from the main earthaccess codebase. I think we have broad agreement that this is a good way forward. Does that sound right?
Next up we need to talk about the interface! We need to be thoughtful about breaking changes here, because those will create work for all plugin projects (and those downstream of the plugins). What does developing a plugin look like? How will earthaccess discover/register installed plugins? What context will earthaccess provide to the plugin (and if that includes credentials, how should we warn users about using only trusted plugins?)? What information will be reported back from the plugin to earthaccess? How do we test that we haven't committed any breaking changes to the interface, and if so, apply the correct version change?
Identified tasks (please edit me!)

[ ] Think about what some likely plugins would look like. List out what has been explicitly requested so far in one place.

Harmony
OPeNDAP
Asynchronous ordering (which systems? @betolink: EGI may be going away soon, use icepyx)
NSIDC subsetter
Other NSIDC customization services
Edit me!

[ ] Specify an interface between earthaccess and its plugins
[ ] Edit me!

:rocket: :heart:
EDIT: cc @briannalind @jhkennedy

So I've been poking at this a little. Harmony and HyP3 both have python clients which allow you to interact with those services, so building an earthaccess plugin with those should be straight forward -- most of the work is just translating the earthaccess search results into the form needed by those services. Just sketching out with pseudo code, this could look like:
# HyP3
results = earthaccess.search(...)
jobs = earthaccess.hyp3.submit_rtc_jobs(results, **kwargs)
jobs.watch()

ds =  earthaccess.smart_open(jobs)  # xarray dataset

# Harmony
results = earthaccess.search(...)
jobs = earthaccess.harmony.mosaic(results, **kwargs)
jobs.watch()

ds = earthaccess.smart_open(jobs)  # xarray dataset

# SBAS -> HyP3
results = earthaccess.search(...)
stacks = earthaccess.asf.sbas(results, **kwargs)
jobs = earthaccess.hyp3.submit_insar_jobs(stacks, **kwargs)
jobs.watch()

ds = earthaccess.smart_open(jobs)  # xarray dataset

Really there's three fundamental interfaces for services:

Submit granules to the service
wait for the services to do it's thing
access the resulting data from the service

Some thoughts on how to do this borrowing from @jhkennedy 's comments above.
Abstract Plugin Interface: PluginInterface

submit_granules(): Submit granules to the service.
wait_for_service(): Wait for the services to do its thing.
get_results(): Access the resulting data from the service.

Plugin Discovery:
Propose we create a 'plugins' directory and follow the "Using namespace packages" section at this documentation.
Earthaccess would then discover and load any plugins located in the 'plugins' directory. This could load a list of available plugins that the earthaccess.results.DataCollection.service method can use to return available plugins when returning a list of associated services for a collection.
Later on we could move towards letting the user install the plugins via a command like this: pip install earthaccess[harmony] which would only install and make a Harmony service plugin available. This way the user only has to install what they need. It looks like this might require the use of entry points.
Steps to implement a plugin:

Create a new directory with the name of your plugin in the 'plugins' directory.
Create a __init__.py file in your plugin directory.
Create a class that inherits from PluginInterface and implement the following methods:
a. submit_granules()
b. wait_for_services()
c. get_results()
Register your plugin by editing the pyproject.toml file. I need to do a little bit more research on this. I found xarray documentation and Python packaging documentation that might be helpful.

I would like to implement the PluginInterface class, test the discovery functionality to see how everything might work, and then regroup for feedback on a hackday!

I feel like plugins should be independent repositories so they can be packaged separately. That way we don't need to maintain optional dependencies within this repo for every plugin, and it gives plugin authors more autonomy. I like xarray's documentation about this! I think they're prescribing that the plugin's pyproject.toml would define metadata needed for xarray to discover it. I need to understand better how that discovery works. I like this model.

That's a great idea. I also am interested in better understanding the plug-in discovery mechanism. So far I have been thinking of the plug-in code as a part of earthaccess. But I will explore what xarray has done to see how it might be possible for plug-ins to be contained in their own repos.

I was hoping to catch some news at the end of today's hack day, sorry I missed you!

@mfisher87 - No worries, I dropped off a little early because I was stuck on failing units tests for the services PR. (Luis offered to take a look at the PR as the units tests for Python 3.10 - 3.12 are failing but Python 3.9 are succeeding.) But we didn't get to talk about the plugin architecture. Maybe we can reserve a little bit of time during the next hackday to discuss!

Sounds like a good plan :)


FIX/TEST: Thought.js needs createdAt formatted with getter method

GIVEN a created Thoughts document
WHEN I look at the createdAt date
THEN it is shows a formatted timestamp.
NOTE: I've created the Thought.js > thoughtSchema.methods.formatDate() function, but need to test by creating a document

This requires seed data or a route

fixed


Evaluate Kata + Podman

I'm confident integration of Kata into podman is feasible, and we should have a "how-to" guide and some level of automated testing available to ensure the 'how-to' guides' functionality.
Futher, it would be good to evaluate this in the context of running kata rootless.  This should be feasible with overlay2, though there would likely be complications wrt devicemapper.

/cc @mcastelino @gabibeyer

Any progress on this front? @gabibeyer can you summarize your findings thus far?

kata seems to work pretty seamlessly with podman as long as selinux is disabled (which already seems to be a reported issue within kata). I have gotten it running in fedora 28, trying ubuntu bionic currently just to see if there are differences.

@gabibeyer can you describe your setup. Also the final goal is to run Kata as rootless with podman.
We need to ensure we do not create files with root uid/gid on the host side when using overlay. Also ensure that the other files like resolv.conf etc do not end up being root when modified.

@mcastelino right, that is not yet rootless,. Should I still describe my setup if it is not yet the rootless implementation?

https://gist.github.com/gabibeyer/ae3f8ee5e7ebc4e1db9d9c26119ca861

Modifications to podman and slirp4netns are in progress for a rootless podman + kata integration

[ ] Configurable paths to be at rootless or default location
[ ] Make usage of cgroups configurable
[ ] Create tap device structure intended for tun/tap devices

Any plans to add tests for podman?

@alicefr - we're hoping to convert https://github.com/kata-containers/documentation/pull/565 into both a document and a test (by "executing" the document commands). However, if you have cycles to help write some more comprehensive tests, that would be great! :smile:

@jodh-intel thx!Nice! There are some tests in the podman repo at https://github.com/containers/libpod/tree/master/test. I'm not sure if they can be extended to be used with kata. I'm trying to check if podman+kata works on s390x. I'll have a look after to their testsuite.


Defer GL for GVRCompressedTexture

Defer GL for GVRCompressedTexture
Remove glthread assertion in texture loading API

Compressed Textures can be constructed outside the GL thread. All loadable textures can now be loaded from outside GL-thread, and thus glthread assertion can be safely removed from texture loading APIs.

Fixes https://github.com/Samsung/GearVRf/issues/429

Looks good to me. Planning to merge this in the afternoon.


Protobuf JSON compatibility

Is your feature request related to a problem? Please describe.
We work primarily with protobufs in our REST API, but for ease of development we also have a JSON REST API that uses the protojson to convert the JSON to protos. The issue we've been seeing is that swag doesn't properly handle a few edge cases (why protojson exists over encoding/json) like one_of fields and bytes fields.
Describe the solution you'd like
If possible would be nice to choose the JSON encoder when generating from models, happy to work on a PR for that if someone pointed me in the right direction too.
Describe alternatives you've considered
Unfortunately it would be pretty hard with our proto toolchain to add struct tags to the generated models, so don't think that option.
Additional context
Bytes fields should be represented as a base64 string rather than an integer array, and a one_of fields should at least be displayed, right now they just are listed as object. This might be hard given that it's an interface definition though.

@code-merc This is an Open Source project. Please feel free to contribute with a PR regarding this feature and we will be more than welcome to review it.

Closing: No activity.


Added sign up page

Fixes #53
Changes: Sign up page added
Screenshots for the change:

@oindrilabhadra78 change the listener position also


Initial project and gems setup

Set up Devise for authentication.
Set up RSpec and Capybara testing libraries.
Set up SASS for styling.
Set up Cancancan for authorization.
Set up bullet gem for N + 1 queries.

STATUS: INVALID REQUEST
Hi @mikemtzp  👋,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project that linters are not passing.
Your Code Review Request will be marked invalid in your Dashboard, so please submit a new one once ready 🙏.
Invalid requests don't count as a review, so don't worry about that 😄!
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me @Gopxfs in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.

Hi, @Gopxfs Thanks for noting the linter errors. I have fixed them properly. The feature is good to go. 👍🏼

🟢 STATUS: APPROVED 🟢
Hello @mikemtzp 👋,
Your project is complete! You followed all the requirements, feel free to merge it! 😄
Congratulations! 🎉

Highlights
✔ Linters are passing.
✔ Added all necessary gems.
✔ Project setup is done. Nice work!
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


[#867] tutorials: send & receive

This commit adds a tutorial about how to setup a consumer and a producer exchanging messages over a deployed broker in a kubernetes environment.

I have just figured-out that this PR added a subfolder in tutorial, have you already checked how that is rendered?
See the build the docs step to render it.