Sveltekit / Node > 16: ClientResponseError 404 Every Time

I am on Windows pocketbase version 0.7.9, npm pocketbase version 0.7.4, and the latest sveltekit. I am using the default example for sveltekit in the readme.
When using node > 16, I am getting an error on any request that uses locals.pocketbase. I can get around this by creating a new client, but that gets painful trying to juggle states.
await locals.pocketbase.users.authViaEmail(data.email, data.password)
Error
ClientResponseError 404: Something went wrong while processing your request.
Any help is appreciated, thank you!

@timmyjl12 I cannot reproduce it. I've just installed the latest SvelteKit template with npm create svelte@latest my-app and added the example hook from the readme and it works fine for me (the hook file need to be renamed only to hook.server.js since SvelteKit now seems to support client-side hooks too, but I'll update the documentation later).
Make sure that you are using the correct url address when instantiating the PocketBase client. If the address is correct, then please provide the full ClientResponseError or a repo where it can be reproduced.

Hi @ganigeorgiev, thank you for the quick response. Turns out it is the ipv4 resolution. I changed the address from localhost to <IP_ADDRESS> and all is well. Thank you again.


Exclude namespaces from Datadog

Prior to this change, when enabled, Datadog is configured to ship logs
from all tenant namespace plus a configured number of "extra" namespaces
through the "extra_namespaces" variable in eks_core and aks_core.
Now we also must be able to exclude namespaces from the tenant
namespaces. Instead of adding a "exclude_namespaces" variable, the
module interface is changed by removing the "extra_namespaces" variable
and an new "namespaces" variable is introduced where you configure all
namespaces that Datadog shall ship logs from explicitly. In this way
the module interface will be easier to understand compared to the other
alternative. Also what namespace that are being used will be more
explicit though the configuration of the module.

No comments on the code itself. Could you provide a example what variables to send in to the module when using it?


Add extra instructions to readme to help get setup faster

Contributes to # (add issue number here. i.e. #302)
What did you do?
Added instructions for what to put in the .env file
Added link to video showing how to setup IBM App ID
Added comment about forking before cloning
Why did you do it?
To help make setup a little smoother so people don't encounter issues I did
How have you tested it?
I was able to get the API up and running with the newly modified steps in the readme
Were docs updated if needed?

[ ] No
[ ] Yes
[x] N/A

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new console logs
[ ] Fixes entire issue
[ ] Partial fix for issue

@Holdrick, which libraries are not supported? We should list them and point to their docs for supported platforms.

@Holdrick, which libraries are not supported? We should list them and point to their docs for supported platforms.

The one I came across was uvloop. I'll add some detail for it


'Destination address' field not controlled per chain.

Just a small thing I noticed as an everyman after trying to help someone find out why their transaction went wrong. They were attempting to send LUNA from Terra to Osmosis but they accidentally entered their cosmos address in the destination field. As far as I know, as it stands it is not possible to send (fuunctional) non-native tokens from chain to chain other than to or from their native chain, so this incorrect address should not be possible to even attempt with this tool.

Thanks, fixed by #108


we need to update artifactory url here?

https://github.com/Lior-Asher/JFrog-Artifactory-CLI/blob/98d0edfef3a59b67a503967e56b9577b9309f056/app.py#L29

Only the Artifactory server name you will use here:
self.url = f'https://{self.server}.jfrog.io/artifactory/api/'

Im receiving this error,
from secrets import SERVER

ImportError: cannot import name 'SERVER' from 'secrets'

On Wed, Oct 12, 2022 at 8:44 PM liorasher @.***> wrote:

Only the Artifactory server name you will use here:
self.url = f'https://{self.server}.jfrog.io/artifactory/api/'
—
Reply to this email directly, view it on GitHub
https://github.com/Lior-Asher/JFrog-Artifactory-CLI/issues/5#issuecomment-1276345422,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQETFCPG2UYD5HDC43LD7Z3WC3IUNANCNFSM6AAAAAARDCKIQQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks,
Can you please share me what all values I need to import from secrets.py
file.. after adding servers and username .etc im still receiving few errors:
If you provide a sample example list here, it would be helpful. As I'm new
to python/scripting.
On Thu, Oct 13, 2022 at 12:08 PM liorasher @.***> wrote:

secrets.py is another file, in the same directory as app.py file, where I
keep private data such as server name.
To fix the error add another python file named "secrets.py".
In it add the line: SERVER='your_server_name' (your Artifactory server)
The line is importing a value from another python file.
—
Reply to this email directly, view it on GitHub
https://github.com/Lior-Asher/JFrog-Artifactory-CLI/issues/5#issuecomment-1277101392,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQETFCIYFT2ZXOHKCVTIUALWC6U5DANCNFSM6AAAAAARDCKIQQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

It includes only server name for this project.
What other errors you get?

`usage: test.py [-h] -u USERNAME
test.py: error: the following arguments are required: -u/--username
Process finished with exit code 2`

Okay.
The Ping test is successful
the rest options are failing due to  authentication error, not able to get artifactory version, storage info.. user creation
Error:
Get Storage Info: {'errors': [{'status': 401, 'message': 'Authentication is required'}]}

Have entered all credentials correctly..also given admin permission to that user.

if I remember correctly, ping does not require authentication, so it always works.
other API calls require a token.
_get_token_for_group method retrieves a token for users in group 'administrators'.
my guess is you can't get a token from Artifactory.
add the user to 'administrators' group, see if that helps

Great!!
I changed the group to 'adusers' and provide administrator permission.. and added a local user.. it worked..
Thanks for your help!! buddy


[Request] Add download button for videos

I use Firefox for Windows and the default player doesn't have a dedicated button to download videos. I can rightclick-download just right, I just thought it'd be nice for the UX to be consistent with pictures.
Otherwise this is a great hb, good job!

Hey, thanks! I wonder what do you mean? When opening a video, there's the download button under it right there:

Oh, I never got to that screen. When I click on a video, it automatically plays.

I didn't look for it bit I believe you.


TEIIDTOOLS-764 adding validations to view listing and view definition

also correcting test package names

This has been updated to combine stash / validate and to return the full entity from stash.  As currently implemented it means that if the preview vdb is not available a service unavailable response will be returned rather than saving the entity.

LGTM


Added the content for PR workflow of director

Exact application name that is under test.

Storage engine that is under test

OpenEBS version if required.
Assumptions of this PR

Notes to reviewer.

Anything else we need to know?

Versions:

$ Kubernetes version
$ Kubernetes platform
$ kubectl version

Closing this due to inactivity. Please reopen if required later.


Builds extra layer with contents of src/main/jib.

This might be what we go with for #473 over what was proposed at #455.
This PR just has the changes for the Gradle plugin. Docker context exporting is also not supported yet.

Also would this close this old issue? https://github.com/GoogleContainerTools/jib/issues/213

@TadCordle yea, though I'll close it manually after the Maven one is added too


Language code not recognized

I'm having an issue where a language code isn't recognized and it wont pick it up. It calls the server and gets the language file,  But i get the error
ERROR TypeError: Cannot read property 'toString' of undefined
The language code I'm using is "mi" for "Maori".  All other languages Ive tried works, en for english, de for german etc.  But mi for maori nope.
I thought the code wouldnt really matter and it would basically look for [languagecode].json file, so aslong as that exist it would work, but nope, it appears it needs to be a known set of codes???

Can you provide some example code which you use? Maybe some stackblitz will be helpful here


Help webpack

Hello, I'm trying to use iscrollview with ssr and am getting this error:
iscroll.js:275 Uncaught TypeError: Cannot read property '0' of undefined
at IScroll (iscroll.js:275)
at Function.Vue.use (vue.runtime.esm.js:3866)
at Object.defineProperty.value (iscroll-view.js:4)
at webpack_require (bootstrap a91fff8…:691)
at fn (bootstrap a91fff8…:114)
at Object.defineProperty.value (index.js:92)
at webpack_require (bootstrap a91fff8…:691)
at fn (bootstrap a91fff8…:114)
at Object.options.path (client.js:1)
at webpack_require (bootstrap a91fff8…:691)
Could you help me or do you know why this might be happening?

Here is the line 273 ~ 275 of iscroll.js
function IScroll (el, options) {
	this.wrapper = typeof el == 'string' ? document.querySelector(el) : el;
	this.scroller = this.wrapper.children[0];
	...
}

It seems that the option el never had a children property. Try to print this.wrapper between line 274 & 275 and then show me the log message, it's a lot of help to debug.

@dinho-afsn ping

Is somebody here? @dinho-afsn


The templates/Web_Scraper_Sample.xml refer to a file regions.txt, but not included

/Users/user/Documents/TowersWatson/regions.txt

Did you find the file?

There wasn't much hope so I just created one by taking arbitrary location names from the food and hygiene rating site and placing some names there in regions.txt file.


Update tgenv-list-remote

It would be very helpful to update tgenv-list-remote to return more than 100 versions. This would assist me in a migration from older versions  of terragrunt that do not show due to the limitation of github api having a max of 100 for per_page.

I did not see there is already an open pull request for this same issue the other fix is probably better as I does not have the limitation of page numbers

@NathanTindle unfortunately, you won't get any traction with this PR. See #19

Thank you @sajid-khan-js you are probably right. I will just use my own fork for now. Just need it for a migration so will probably be removed sometime in the future

@NathanTindle Have you tried using git ls-remote --tags https://github.com/gruntwork-io/terragrunt to fetch versions instead?

@jpalomaki I had not seen this thank you for the info. I will take a look

@NathanTindle @weyderfs has forked and is trying to reboot this project over at https://github.com/tgent/tgenv (see https://github.com/cunymatthieu/tgenv/issues/45)
Consider raising your MR over there? Otherwise do you mind If I move this over?

@NathanTindle I've reimplemented this PR incorporating suggestions from the comments over at in https://github.com/tgenv/tgenv/pull/2


USB GET_INTERFACE response always 0, even when an alternate setting is used

Describe the bug
The response to a USB GET_INTERFACE is always 0, see the following excerpt from subsys/usb/usb_device.c.
	case REQ_GET_INTERFACE:
		/* there is only one interface, return n-1 (= 0) */
		data[0] = 0U;
		*len = 1;
		break;

But according to USB Specification Revision 2.0 (usb_20.pdf from usb.org) section 9.4.4 GET_INTERFACE should return "selected alternate setting for the specified interface."
To Reproduce
There is no (or at least I can't find one that builds for my board) sample that has multiple USB alternate settings; but it is possible to reproduce using a patch to subsys/usb/class/loopback.c and samples/subsys/usb/testusb.

Apply the following patch.

diff --git a/subsys/usb/class/loopback.c b/subsys/usb/class/loopback.c
index 754c2a4906..df35aee390 100644
--- a/subsys/usb/class/loopback.c
+++ b/subsys/usb/class/loopback.c
@@ -30,6 +30,7 @@ struct usb_loopback_config {
        struct usb_if_descriptor if0;
        struct usb_ep_descriptor if0_out_ep;
        struct usb_ep_descriptor if0_in_ep;
+       struct usb_if_descriptor if0_1;
 } __packed;

 USBD_CLASS_DESCR_DEFINE(primary, 0) struct usb_loopback_config loopback_cfg = {
@@ -65,6 +66,19 @@ USBD_CLASS_DESCR_DEFINE(primary, 0) struct usb_loopback_config loopback_cfg = {
                .wMaxPacketSize = sys_cpu_to_le16(CONFIG_LOOPBACK_BULK_EP_MPS),
                .bInterval = 0x00,
        },
+
+       .if0_1 = {
+               .bLength = sizeof(struct usb_if_descriptor),
+               .bDescriptorType = USB_INTERFACE_DESC,
+               .bInterfaceNumber = 0,
+               .bAlternateSetting = 1,
+               .bNumEndpoints = 0,
+               .bInterfaceClass = CUSTOM_CLASS,
+               .bInterfaceSubClass = 0,
+               .bInterfaceProtocol = 0,
+               .iInterface = 0,
+       },
+
 };
 /* usb.rst config structure end */

Build the testusb sample (my example below for the NXP RT1020 EVK).

west build -p auto -b mimxrt1020_evk samples/subsys/usb/testusb

Flash.
Run USB Chapter 9 TEsts (USB 2 Devices) in the compliance tool from usb.org (USB 3 Gen X).

The test will fail in Configured State - TD 9.4 with an error message "A successful GetInterface request must return the alternate setting set by a prior call to SetInterface".
Expected behavior
Compliance tests should pass.
Environment (please complete the following information):

OS: Ubuntu
Toolchain: Zephyr SDK 0.11.2
Zephyr master b74cad5a5d0f35905c4ab3d719bdc6b2794bc940.

First of all, whats the use case to add alternate setting for such device?
In order to make it work i suppose that custom_handler must be implemented but I might be wrong as I took only i brief look into this. I cannot say when I will have time to do it as I am a bit busy right now and I do not see clear use case for that right now.
The current code is indeed incorrect but for all the classes and functionalities we support just right now its sufficient.
Alternate settings are commonly used in audio class. Implementation could be found here #21526.
I think it would be worthwhile to implement it in audio for sure and as an author I will keep that in mind as for now it is missing.

Sorry for being a bit unclear - the example was just the quickest way I could find to create a patch that would fail in the USB compliance test. I'm tinkering with audio stuff and it was in that context that the issue was found.
I can create a PR for a more generic solution; store the alternate setting after a successful USB SET_INTERFACE and returning that in the GET_INTERFACE request.

Ah, okay now I get this. If You want to post a PR it would be great. One question as You said 'generic solution'. Where do You gonna store the info about alternate setting?

Good question. If zephyr only supports one interface would it be out of place to store it in struct usb_dev_priv?

Until now it supported no alternate settings but many interfaces. For example if You configure 2x cdc there will be 4 interfaces in total.
It cant be in usb_dev_priv as on this level You are not possible to guess the total number of interfaces so there is no possibility to create a table or whatsoever to store this information.
I think the only way now is to implement custom_handler as it is called prio the std_interface_req(), but this will get tricky as well because of how the set_interface is handled..

Thanks! I'll look into that.

We can follow up on Slack, feel free to ping me there.

There is no (or at least I can't find one that builds for my board) sample that has multiple USB alternate settings;

CDC ECM has alternate settings for the second interface:
CDC ECM Interface 1 | bAlternateSetting = 0 and CDC ECM Interface 1 | bAlternateSetting = 1

This issue will be addressed during usb device stack rework and shall not remain stalled.


docs bug - does it work with webpack --watch

In the docs it says:

This plugin allows you to run any shell commands before or after webpack builds. This will work for both webpack and webpack-dev-server.

maybe it could specify it works with webpack --watch too?

Old issue I know but may help new users, it seems you have to use onBuildExit see comment


dice_loss and NumPy 1.17.3

Hello!
Loss-function dice_loss works fine with NumPy 1.15.4, but with last version (1.17.3) I'm getting error:

C:\Users\Daemon\AppData\Local\Programs\Python\Python35\python.exe C:/Users/Daemon/PycharmProjects/atDNARelationshipDetector/train.py
C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\h5py_init_.py:36: FutureWarning: Conversion of the second argument of issubdtype from float to np.floating is deprecated. In future, it will be treated as np.float64 == np.dtype(float).type.
from ._conv import register_converters as _register_converters
Using TensorFlow backend.
C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\framework\dtypes.py:523: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\framework\dtypes.py:524: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\framework\dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_qint16 = np.dtype([("qint16", np.int16, 1)])
C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\framework\dtypes.py:526: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_quint16 = np.dtype([("quint16", np.uint16, 1)])
C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\framework\dtypes.py:527: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_qint32 = np.dtype([("qint32", np.int32, 1)])
C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\framework\dtypes.py:532: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
Traceback (most recent call last):
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\segmentation_models_init.py", line 98, in
set_framework(framework)
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\segmentation_models_init.py", line 68, in set_framework
import efficientnet.keras  # init custom objects
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\efficientnet\keras.py", line 4, in
from .preprocessing import center_crop_and_resize
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\efficientnet\preprocessing.py", line 16, in
from skimage.transform import resize
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\skimage_init.py", line 158, in
from .util.dtype import *
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\skimage\util_init.py", line 7, in
from .arraycrop import crop
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\skimage\util\arraycrop.py", line 8, in
from numpy.lib.arraypad import _validate_lengths
ImportError: cannot import name '_validate_lengths'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:/Users/Daemon/PycharmProjects/atDNARelationshipDetector/train.py", line 5, in
from generators import batch_test_generator, batch_train_generator, size_of_batch
File "C:\Users\Daemon\PycharmProjects\atDNARelationshipDetector\generators.py", line 5, in
from mymodel import matrix_width, matrix_height, classes
File "C:\Users\Daemon\PycharmProjects\atDNARelationshipDetector\mymodel.py", line 7, in
from segmentation_models.losses import dice_loss
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\segmentation_models_init_.py", line 101, in
set_framework(other)
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\segmentation_models_init_.py", line 71, in set_framework
import efficientnet.tfkeras  # init custom objects
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\efficientnet\tfkeras.py", line 4, in
from .preprocessing import center_crop_and_resize
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\efficientnet\preprocessing.py", line 16, in
from skimage.transform import resize
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\skimage\transform_init_.py", line 1, in
from .hough_transform import (hough_line, hough_line_peaks,
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\skimage\transform\hough_transform.py", line 3, in
from .. import measure
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\skimage\measure_init_.py", line 2, in
from ._marching_cubes_lewiner import marching_cubes, marching_cubes_lewiner
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\skimage\measure_marching_cubes_lewiner.py", line 17, in
from ..shared.utils import skimage_deprecation, warn
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\skimage_shared\utils.py", line 10, in
from ..util import img_as_float
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\skimage\util_init.py", line 7, in
from .arraycrop import crop
File "C:\Users\Daemon\AppData\Local\Programs\Python\Python35\lib\site-packages\skimage\util\arraycrop.py", line 8, in
from numpy.lib.arraypad import _validate_lengths
ImportError: cannot import name '_validate_lengths'

This error occurs because scikit-image<=0.14.1 depends on the numpy method _validate_lengths(), which was removed from numpy as of v1.16.0. This should be fixed with scikit-image v0.14.2. Check this and this for more details.


Jupyter Notebook + Julia

Issue Type: Bug
Since upgrade of Vscode to version 1.54.1 I cannot use jupyter notebook with Julia. I get the following when including a .jl file.

/extJupyter


Odiglet is emitting too much info logs

Describe the bug
When you setup a fresh install of Odigos and make the full setup of your apps, when the Collector send some trace to save the Odiglet generate a log of this operation.
To Reproduce
Steps to reproduce the behavior:

See the logs on odiglet when has any services receiving traces.

Expected behavior
Any option to control when or which log level we want to use, like the -zap-log-level on instrumentor or scheduler.
Screenshots

Thanks @vitorhugoro1 ,
Indeed its emitting a lot of logs. related issue to apply the fix in the source: https://github.com/open-telemetry/opentelemetry-go-instrumentation/issues/691


added optionals sheet & sheetIndex params to  object

This address issue #6 by adding two optional parameters to options object. Passed as parameter to spawned command.

hi, i don't use this anymore - but this looks good. I can add you as a collaborator/owner and you can merge it your self?

Sure, no problem. You may also add me on npm to keep versions updated.
Sadly, I'll need to work with xlsx for a couple of months. :cry:

@guumaster I feel your pain.
you are now a collaborator + npm owner! have fun!


Publish blog post about "recommended architecture for a simple payment dapp"

Definition of done (Notion)

WIP #699

Merged, will be published Monday (2023-03-06)


[1.12.1] Random crash when placing projectors

So I was just placing projectors around, trying to figure out how they work and then I randomly got a crash:  https://pastebin.com/J9KqM3WQ

Weird. That shouldn't happen or at least i'm not sure why it is. Should be an easy workaround/fix though.

I can not reproduce this at all. Anyway, a workaround is incoming and i'll upload a new build to curse right away.


create role to update submodules

Create a role that updates git submodules.

This might be achieved in this way:

Create a job that runs in a periodic pipeline

Job Updates the Submoduls
Job creates a PR in GitHub
Human can confirm and merge changes

no need at the moment.


Remove extra characters on previous / next button

Remove extra characters on previous / next button on the french translation

Codecov Report

Merging #23 (74411b5) into 2.5 (b44af9b) will decrease coverage by 0.12%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                2.5      #23      +/-   ##
============================================
- Coverage     55.94%   55.81%   -0.13%
  Complexity     1264     1264
============================================
  Files           275      275
  Lines          4803     4803
============================================
- Hits           2687     2681       -6
- Misses         2116     2122       +6

Impacted Files
Coverage Δ
Complexity Δ

app/Presenters/ComponentPresenter.php
84.21% <0.00%> (-15.79%)
10.00% <0.00%> (ø%)

app/Integrations/Core/System.php
84.61% <0.00%> (-5.13%)
13.00% <0.00%> (ø%)

app/Http/Controllers/Dashboard/ApiController.php
50.00% <0.00%> (-2.50%)
9.00% <0.00%> (ø%)

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 b44af9b...74411b5. Read the comment docs.


Adding tslint

This PR adds tslint rules from wtslint-wix-react: https://github.com/wix/tslint-wix-react/blob/master/tslint.js as team agreed.
And also delivers all source and demo, and tests files linted.
During the linting I added some specific rules to test/ folder and turned off some rules in main preset repo.

I've reverted the merge to master, as this pull request contained behavior changes and refactors outside the scope of linting.
I understand adding linting touches almost every file in the project, which makes it imperative that we do not mix other code refactors within the pull request itself.
Please remove changes that are not related and open a new PR.

Alright, after going through most of the changes, I noticed the following:

Most changes are great. They align the code style to be mostly consistent and easier to read.
There are some rules we should discuss. Like changing the regular function to arrow functions in the tests. We'll open issues in https://github.com/wix/tslint-wix-react for continued discussion.
This pull request can easily have less noise by moving the render functions back to their original place. This made it really hard to spot any breaking/out-of-scope changes.
The changes to Tree are not related to linting. Behavioral changes should be reviewed and discussed in a separate PR.


Documentation Updates

Closes #89 .
Points 3 and 4 in https://github.com/yuvipanda/hubploy-template/issues/9 are addressed in this PR.
I'll take a stab at a couple things here: https://github.com/yuvipanda/hubploy/issues/67#issuecomment-650615805
Namely, using custom version of Helm and a contribution guide.

make html succeeded without errors. Only warning was
WARNING: html_static_path entry '_static' does not exist

Formatting is as I expect it.


Update AphlictClientServer to support ws2 or ws3

I'm not sure if endlessm-test is the right branch to target PRs for in our repo.
Summary: This lets us support either ws2 or ws3. Fixes T12755
Test Plan: Update server to version 3, send message, watch debug log. Downgrade to 2.x, send messages, watch debug log. Everything seems OK
Reviewers: epriestley
Reviewed By: epriestley
Subscribers: Korvin
Maniphest Tasks: T12755
Differential Revision: https://secure.phabricator.com/D18411

I used endlessm-test as a place to stage changes for the dev environment. Since this is a minor change, I assume you can test it in place on the dev environment without building a whole new AMI? You might want to just put it straight into endlessm-stable.

I already hacked it into place on stable for https://phabricator.endlessm.com/T19478 :) It seems to work correctly since notifications are working again.

OK, that's reasonable. But do we want endlessm-test to be behind endlessm-stable? Seems like that shouldn't happen.

endlessm-test is just a sort-of staging branch.. It should be branched from the latest endlessm-stable.

Changed the PR to target endlessm-stable. After merging, should endlessm-stable be merged to endlessm-test so that we don't make a dev/test AMI using old code?


Can't proceed past starting screen for Tangent or AFPS on the web

Tangent and AFPS on the web send a reliable network message to the server to set their state (class and name respectively), but this doesn't seem to be processed by the server.
This suggests that

the client is not sending a message to the server correctly
the server is not handling the message from the client correctly
something else is happening

In any case, more investigation is required.

Initial testing from @ten3roberts suggests that the WebTransport layer is working correctly (i.e. you can send unistreams from the client to the server). This suggests it's an issue with Ambient specifically.

This does not happen everytime for tangent, but it does for AFP. For AFPS i can't get past putting in my name.

I can't reproduce this on Tangent with:

native client on local server
web client on local server
web client on remote server
website + web client

@TobiasEnholmX How often are you seeing this happen?

Tangent seems OK but AFPS still gets an error

Now it worked so that's likely


[20.03] ansible: v2.9.2 → v2.9.9, v2.8.11 → v2.8.12, v2.7.17 → v2.7.18, mark v2.6 as insecure

Motivation for this change

Missed backporting a security bump from #86980
Backport  recent minor versions from #88037
Mark Ansible 2.6 as insecure, since it's EOL and the CVEs in #86980 happened

Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

One remaining issue is that the "Known issues" message for ansible_2_6 references the wrong ansible version (v2.9.9).
❯ nix-build -A ansible_2_6
error: Package ‘python3.7-ansible-2.9.9’ in /home/hexa/git/nixos/release-20.03/pkgs/tools/admin/ansible/default.nix:30 is marked as insecure, refusing to evaluate.

Known issues:
 - Ansible 2.6 is End-of-Life since 2019/11/06 and affected by multiple CVEs.

You can install it anyway by whitelisting this package, using the
following methods:

a) for `nixos-rebuild` you can add ‘python3.7-ansible-2.9.9’ to
   `nixpkgs.config.permittedInsecurePackages` in the configuration.nix,
   like so:

     {
       nixpkgs.config.permittedInsecurePackages = [
         "python3.7-ansible-2.9.9"
       ];
     }

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
‘python3.7-ansible-2.9.9’ to `permittedInsecurePackages` in
~/.config/nixpkgs/config.nix, like so:

     {
       permittedInsecurePackages = [
         "python3.7-ansible-2.9.9"
       ];
     }

(use '--show-trace' to show detailed location information)

@flokli Done


The redis-py dependency is very old (<=2.10.6)

This is an almost 4 year old package, any reason the dependency still point to it?
It generates conflicts in newer Python environments.

@swilly22 Do you see a problem with bumping this up? Are there sufficient tests to catch simple redis-py compatibility issues?

I don't see any reason why no to bump redis-py version.

Opened PR #46 and moved discussion there.


Allow entering the container to debug its state

Is your feature request related to a problem? Please describe.
I am trying to debug a crash in a process using this tool. I'd need to run again one of the processes with gdb and interact with it.
Describe the solution you'd like
I'd like to be offered a way to interact with the system as one of the tests fails.
Describe alternatives you've considered
I looked into modifying our ci tooling to call the processes by default with gdb, can't really do that without breaking our current ci as we get the recipes from elsewhere shared.
Additional context
This is the CI in question:
https://invent.kde.org/plasma/kwin/-/blob/Plasma/5.27/.gitlab-ci.yml?ref_type=heads

You need to make a more precise description of what you want here.
How would you like the gitlab-ci-local command to look like?

I can imagine running gitlab-ci-local $job --shell bash or even just gitlab-ci-local $job --devel and after it executes the CI suite you're given a shell with the environment where the system just ran. It would be a good opportunity for running the CI, modifying the code and running again or just generally learning about the execution.


After clicking Add attachment the keyboard toggles back for a split second

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Launch the app
Log in with any account
Open any conversation
Tap on the compose box to make sure the keyboard is open
Click the + button.
Click Add attachment

Expected Result:
Transition is smooth when clicking the Add Attachment button and doesn't toggle back.
Actual Result:
After clicking Add attachment the keyboard toggles back for a split second
Workaround:
Unknown
Platform:

Where is this issue occurring?

iOS
Mobile Web/Chrome (Android)

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): any
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/189416600-4d187b70-5881-48e9-9e24-73d9c1b3ae3b.mp4
https://user-images.githubusercontent.com/93399543/189416602-8512c58f-c0a6-4261-8117-fc8eb0881194.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

It looks like a problem when the virtual keyboard is opened because it toggles back for a split second right?
Adding the External label for this.

@PauloGasparSv - marking the issue as external by design adds the Daily label.
@kbecciv - The issue title says iOS but the Platforms section has all platforms listed. Can you confirm which platforms are impacted, please? Is it limited to iOS (incl. mobile web) or Android as well?

Transition is not smooth when clicking the Add Attachment button.

This description is a bit ambiguous to me. When reproducing this, I think I would more so describe it as a flicker. I agree with Paulo that we could make this clear by updating it to:

After clicking Add attachment the keyboard toggles back to the create menu for a split second

Thoughts on that?

Cool, I'll update that in the OP issue and title, then wait on @kbecciv to confirm the platforms before we proceed.

@trjExpensify Checking with team, update here shortly.

@trjExpensify Updated the impacted platforms.
Adding mWeb/Chrome behavior as well
https://user-images.githubusercontent.com/93399543/190198758-05a11415-a20e-40e6-91b6-71dcc30fd6d5.mp4

Sweet! So just to confirm, we also need to add Android to the platform list right?

Issue is reproduceable iOS app and mWeb (Android/Chrome)

Cool, thanks. On upwork here: https://www.upwork.com/jobs/~01c3f1b04035ef88cf

Waiting for proposals.

Job doubled to $500 on Upwork here: https://www.upwork.com/jobs/~01c3f1b04035ef88cf

Did this get fixed elsewhere? 🤔 I'm unable to reproduce on iOS
https://user-images.githubusercontent.com/16232057/194327643-b810846b-53eb-498c-9f82-d25e1adf20f9.MP4
@mananjadhav @kbecciv can either of you retest on Android before I bump the price on this one?

I don't have an Android for the time being to test this one. @kbecciv Can you please help here?

Unable to reproduce on Android. The keyboard no longer pops up like the original screencasts show. Pixel 6A, Android 13
https://user-images.githubusercontent.com/10736861/194564695-3d4083f9-2b32-424c-a1e0-ce62788689fd.mp4

Checking with team, will update you shortly

QA team is still reproduced this issue with latest build <IP_ADDRESS>
https://user-images.githubusercontent.com/93399543/194598426-014e835d-974f-4876-92a5-8a608711342e.mp4

Hm, is that iOS or Android?

This is IOS app

@kbecciv could you please share the iOS version, and device?

Sure, checking with team

@Julesssss Tester was using iPhone XS Max/IOS 16

Okay. I think we should leave the issue open, but not increase the bounty. Verifying a fix will be tricky, but first, let's see if anyone finds a solution.

I'm a bit wary of leaving this open if both Jules nor I can reproduce it on either Android or iOS. What conditions are we missing, are the steps in the OP accurate? If the tester can consistently reproduce this, we must be missing something.

My assumption is that it's just an inconsistent bug. Perhaps it's occurring on a specific device, but it's also possible for it to require additional steps to reproduce that we're not aware of.
I'm also happy to just ignore it and close the issue, but we should first confirm whether we can reproduce on this device: iPhone XS Max/IOS 16. If yes, it's probably a device-specific (or device with certain hardware) issue. Else, it probably requires some additional step that we're unaware of and closing might be the best use of our time.
I asked here for someone with this specific device to try to reproduce.

Gotcha. The iPhone XS Max came out in 2018, it's pretty old at this point (latest in that product line is the iPhone 14 Max). I'm not surprised we're getting crickets from asking in a few places in Slack.

Else, it probably requires some additional step that we're unaware of and closing might be the best use of our time.

@kbecciv can you confirm the steps, and can you confirm on a couple of other iOS devices. Thanks!

Haha! All good - agree with that next step.

@Julesssss Two testers are unable to reproduce the issue using latest build <IP_ADDRESS>
https://user-images.githubusercontent.com/93399543/196179165-1c6d1bb2-eb39-4b68-b340-5a6712d4cf8a.mp4
https://user-images.githubusercontent.com/93399543/196179172-55aed4f2-1fff-4873-a7d3-a94d70ea27a0.MP4

Hi @kbecciv, can you please include the device model and OS version?

@Julesssss Added above to each video.

Two testers are unable to reproduce the issue using latest build <IP_ADDRESS>

Thank you, seems like we're okay to close this issue for the moment then 👍


Create LICENSE

Coverage remained the same at 83.333% when pulling 9a5ce15708a17b16d16111a0f8ec187eb73c8bb2 on add-license-1 into 6f7f6ddcfece108b963e399882d951e7f591b737 on master.


Dependabot updates

Is this a new chart?
Yes/No
What this PR does / why we need it:
Which issue(s) is this PR associated with:

#Issue_Number

Special notes for your reviewer:
Checklist:
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] Chart Version bumped
[ ] Variables are documented in the chart README.md
[ ] Title of the PR starts with the chart name (e.g. [charts_dir/mychartname]) if applicable

sorry, wrong repo


adding the new roadmap

@MikeWasson do you think this would be helpful?

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/toc.yml
:white_check_mark:Succeeded
View

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


self-daemonization is depricated

It's news to me that self-demonization is now considered a bad practice.
I think it should be left in for people that want to use it.
Can author elaborate why it is depricated and marked for removal?

It's duplicate behavior implemented better elsewhere. By relying on OS-provided demonization you can use the same management tools and monitoring you use for other services. Does that make sense?

Thanks @rud, that's a great formulation, I'll use it in my own explanation (I find this topic comes up once in a while in other areas as well).

Glad I could help


Limit ride requests search to 5 results

Limit ride requests search to 5 results. Give some method for the user to have the rest outputted.

Is this a query limit or in displaying results?
If it’s just for displaying results note get selection from ride.py:
def get_selection(items: list):
"""
Gets the user to select a item from a list, displaying up to 5 items at a time.
:param items: list of items
:return: selected item from items
"""


Fix for TS-4276

In the event that lookup_done returns a NULL, we'll reschedule the lookup in the future instead of dumping core.
2 fixes:
(1) retry: https://github.com/jacksontj/trafficserver/commit/805c041ba8cb464c82a47d611d93b7e03ca2cd7c
(2) return non-mmaped entry: https://github.com/jacksontj/trafficserver/commit/29043cf5dfaa143f5dc4e0a670d5a0ba760ee306

I'm not sure this is the correct fix, in this case where we have no space we probably should just get lookup_done to return a non-persistant version of the record instead of just retrying. In this retry case, lookups will continue to fail until a vacancy shows up in hostdb.

This is a different patch to the same issue. Instead of scheduling it for a retry, we can just return the non-mmaped HostDBInfo we have, so everything else can continue to function in a non-persistant way.

As I'm thinking through this some more, I'm not certain this is a great solution either. The particular case that I reproduced was that hostdb was full when returning rr() records. It seems that the insert into hostdb can't fail (as it will eject things if necessary), so really the core issue here is that we are trying to store some additional information (hostnames, etc.) and we cannot store them because we are out of space. The current patch I have here is just returning the HostDBInfo struct, but it didn't put anything in where the hostnames should be. In the more simple cases (where we are storing the hostname that we looked up) it is probably preferable to return without a hostname at all, but in the reverse DNS case that is the primary intent of the lookup.
Thoughts?

Maybe it needs to evict things more aggressively, such that it always has ~10% head room for these sort of events ?

I don't think we can ever gaurantee that there will always be space available, and since we already evict when we need space, we should just keep doing that IMO.
I think we should basically do 1, but specifically as an atomic insert. Right now we are inserting N (usually 2-3) items into MultiCache. Instead we could allocate all of the space up front, and insert just a single item-- this way we are atomic with our objects in cache.

Not sure I understand. I'm saying, evict before it gets full, so normal eviction happens when there's 10% of less available, before inserting new stuff. That gives a 10% head room for this "overallocation" where you can't (maybe?) easily evict more stuff to make room for the necessary changes ?
But if 1) is easily done, such that you can just evict more when needed, I'm +1 on that.

From what I'm seeing 1) should be completely doable-- I'll take a crack at it :)

@SolidWallOfCode  to review.

I don't want to merge this PR in, its a definite hack. I'm working on a better fix, it'll just take some time.


[sbl-filing: just_metadata_branch  branch] enhancement(Upload): Upload Adjustments

closes #410
Note

Using the all-current-prs new_all_branch just_metadata_branch  branch of sbl-filing

Screenshot (04/24/2024)

Success
File Size Check

File Format Error
Unsupported Media

Upload - No Connection

New Test csv's
Syntactical Errors
Logical Warnings/Errors
not-enough-columns-parsing.csv
How to Test

Make sure SBL_REGTECH_FILING_URL is set properly in your .env
yarn install to get luxon
yarn up -i design-system-react to get the latest design-system-react dependency
Run yarn update, reset all Docker volumes and containers, yarn seed and set the user to have a LEI in Keycloak
Navigate to http://localhost:8899/filing and click on 'Upload' to navigate to the lei's specific Upload page
Upload a .csv file -- can use test .csv files from https://github.com/cfpb/regtech-data-validator/tree/main/tests/data
Notice Upload/Validation icons and content changes; inspect the Network tab to verify API request results
Verify the implemented control flow listed below:

[WIP] Control Flow Testing

[x] if the lei and/or filing period do not exist; or are not associated with the user, the user should be redirected to /filing
[x] If a filing has not been posted, the entire "Select a file to upload" Section should not appear
[x] If a previous upload was completed previously, the upload section's content and button label should change
[x] Validation should occur after an upload
[x] Save and continue button should be enabled after the Upload/Validation succeeds
[x] Upload not-enough-columns-parsing.csv and see the SUBMISSION_UPLOAD_MALFORMED error.
[x] Kill the sbl-filing docker container, and then try to upload -- should see the UPLOAD_FAILS error.

Changes

[x] enhancement(Upload): Allow being able to upload the same named file twice in a row
[x] enhancement(Upload - Longpolling): Retries the get latest submission request upon either VALIDATION_IN_PROGRESS or SUBMISSION_UPLOAD
[x] enhancement(Upload - Status): Created general catch all validation error content for the VALIDATION_ERROR state
[x] enhancement(Upload - File Details): Warnings and Errors use special messages and the yellow icon based on validation results
[x] refactor(SubmissionResponse): Updated the type based on incoming backend schema changes
[x] refactor(InlineStatus): Removed ternary hell
[x] feat(Upload - Error Handling): Checks if a user tries to upload a file over a size limit (e.g. 2GB)
[x] enhancement(Upload - Status): Implemented UPLOAD_FAILED

Next PR

[ ] Overall Accessibility
[ ] Alert handling (On initial page load too?) for aria-live regions -- try polite
[ ] aria live region -- initial load don't use polite on uploadedBefore true

@billhimmelsbach Yes, let's merge this into main for the sake of brevity. I've updated based on all of the data.state cases from the backend and have catch-all 4xx/5xx for both Uploading and Validation results.
Additionally, I've matched everything with the Figma as much as I can. If certain design or content items need to be updated, it would not take a significant amount of effort to make the necessary changes.

Let's have our chat about merging your work and Meissa's in our meeting in a bit, then let's go ahead and put up a PR if you think it's ready for design review by Natalia.


[Meta] New behaviours for LoS and if participants are on there several times

Currently:
A new feature allows that one participant can be on a Los several times. The participant is only allowed to put themselves on the LoS once. Only a person with LoS_canmanage can put a participant on the list several times.
Now the LoS needs (potential) more visible information for the user:

[ ] the user/admin needs a marker to see which contribution was set by themselves use vs a different user

[ ] Question: should the marker (contribution is set by self) determined by the person who sets the contribution or should is be determined whether or not the contribution was added via the 'Add me' button we 'select the speaker box
[ ] The backend probably needs a new field which saves who/where/how/new boolean etc. the contribution was saved

[ ] We need to discuss:

how the marker should look
if the marker should only be visible for contributions which were set by self/others

[ ] Wanted behaviour?: A participant should always be able to put themselves on the list once and to ONLY remove themselves from the list if they put themselves on there

does this need a new setting?

Summary:

add a marker for a contribution (self/other)
design/UI/UX
new setting, and new possibilities for the participant

Note: @emanuelschuetze - I've marked you for discussing purpose. We need to talk about this on a conceptual level, before coding can happen.


(Enhancement) gray 'input box' upon successful completion

(Enhancement) Upon successful completion of the game, make the "input box" grey shaded to indicate that the game is done.

I have completed this enhancement.  It will be included in the next commit/pull request.


Only Git tag prerelease builds rather than publish to NPM

NPM lets people install by Git tag like npm install<EMAIL_ADDRESS>but it has no awareness of a prerelease package. Right now the alpha version will be installed by anyone just running npm install node-sass.
EX: NPM itself only has the latest stable 2.7.1 published https://www.npmjs.com/package/npm but they have tagged prereleases up to 2.7.3 https://github.com/npm/npm/releases/tag/v2.7.3

I missed that one. I thought npm would just figure it out from semver. :)
Thanks for pointing it out. Moving forward, I will only publish the stable release to npm.

I have created a new release v3.0.0-alpha.1. But I am unable to install it as: npm install<EMAIL_ADDRESS>However, explicitly specifying the org worked: npm install sass/node-sass#v3.0.0-alpha.1.
Perhaps without specifying organization in slug is something special for npm itself?
Nonetheless we can live with it. :)

I found a few things last night that I'll try to post here when I'm back home. The main one I came across is that I think you now need to use npm dist-tag https://docs.npmjs.com/cli/dist-tag to manage the tags you want to be able to @tag install.

Moving forward, I will only publish the stable release to npm.

People using broccoli-sass are asking for the alpha updates; it'd be nice for them to have the alpha releases on npm too (maybe behind the npm tag thing? - I haven't used it) so that broccoli-sass can update the package.json dependency.
If not, we can just wait it out till 3.0.0 stable of course :)

I have updated the release notes in package.json usage:  https://github.com/sass/node-sass/releases/tag/v3.0.0-alpha.1
Sent from my Windows Phone

From: Jo<EMAIL_ADDRESS>Sent: 3/21/2015 21:46
To<EMAIL_ADDRESS>Cc: Adeel<EMAIL_ADDRESS>Subject: Re: [node-sass] Only Git tag prerelease builds rather than publish to NPM (#772)

Moving forward, I will only publish the stable release to npm.

People using broccoli-sass are asking for the alpha updates; it'd be nice for them to have the alpha releases on npm too (maybe behind the npm tag thing? - I haven't used it) so that broccoli-sass can update the package.json dependency.
If not, we can just wait it out till 3.0.0 stable of course :)

Reply to this email directly or view it on GitHub:
https://github.com/sass/node-sass/issues/772#issuecomment-84444285

Cool. I've bumped the broccoli-sass dependency to git+https://github.com/sass/node-sass#v3.0.0-alpha.1 (apparently HTTPS URLs tend to be more reliable, because firewalls). I worry that some people will still have trouble getting npm to download it from GitHub, but we'll see.

You can publish alpha packages to npm, just tag them so that they're not tagged as latest:
npm publish --tag alpha

The horse has already bolted, not much point closing the stable doors now.
Since the default package npm installs right now is 3.0.0-alpha.0, you may as well keep pushing onwards and learn from this mistake.
It might be useful to mark all of these pre-release packages as deprecated on the registry too so people will have some idea what they're getting into.

Actually, I take it back. I think something like this could work:
npm dist-tag rm<EMAIL_ADDRESS>latest
npm dist-tag add<EMAIL_ADDRESS>alpha
npm dist-tag add<EMAIL_ADDRESS>alpha
npm dist-tag add<EMAIL_ADDRESS>latest

@kudos, thanks! 2.0.1 is set to latest: https://www.npmjs.com/package/node-sass.

@kudos I wouldn't remove the latest tag; also, there's no point in adding the tag alpha twice (and order matters!). Tags point at one version exactly, tagging another version with the same tag moves the tag. Your suggestions sets 3.0.0-pre to alpha whereas 3.0.0-alpha.0 should get it.

@mzgol, I added v2.0.1 to latest and v3.0.0-alpha.1 to alpha.

@mzgol didn't realise tags were unique, thanks for the heads up :)
@am11 glad it's sorted!


Purpose of "Output stream name" setting

Can you please describe the purpose of this setting in the context of the DF sink transformation?
It does not look like the name is used anywhere, because the sink is the final step of the corresponding data stream.

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

ID: b52f7d74-8aac-9e9a-e13e-112eaf2e434b
Version Independent ID: 2e16d8b4-2081-f6d4-9879-5774e9fb1dd1
Content: Sink transformation in mapping data flow - Azure Data Factory
Content Source: articles/data-factory/data-flow-sink.md
Service: data-factory
GitHub Login: @kromerm
Microsoft Alias: makromer

@VitalyMCT Thanks for the feedback! We are currently investigating and will update you shortly.

@VitalyMCT The "Output Stream Name" represents the name/label for your output stream (which consists of a sink dataset).
In the image below, you can see multiple sinks - DayStatsSink, VendorStatsSink, TotalPaymentBy... These streams represent a specific output which can be written to any supported sink dataset (which represents the actual dataset).

Hope this helps.

@VitalyMCT, I will now proceed to close this issue. Feel free to still comment and tag me if you have any queries.
Stay Safe!


Support for hyperparameters with JSON serialized and non serialized keys altogether

Description of changes:

Support for hyperparameters with JSON serialized and non serialized keys altogether
Add new SageMaker hyperparameter _tuning_objective_metric
Add new env variable TRAINING_JOB_NAME

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #73 into r2.0 will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##             r2.0      #73      +/-   ##
==========================================
+ Coverage   97.76%   97.79%   +0.02%
==========================================
  Files          18       18
  Lines         627      635       +8
  Branches       47       47
==========================================
+ Hits          613      621       +8
  Misses          9        9
  Partials        5        5

Impacted Files
Coverage Δ

src/sagemaker_containers/_params.py
100% <100%> (ø)
:arrow_up:

src/sagemaker_containers/_env.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Design Principles of PaddleSpeech pinyin lexicon

g2p.md
So, if you want to use common G2P tools in text frontend such as pypinyin and g2pM, you should pay attention to the following rules:
for c, v in zip(orig_initials, orig_finals):
    if re.match(r'i\d', v):
        if c in ['z', 'c', 's']:
            v = re.sub('i', 'ii', v)
        elif c in ['zh', 'ch', 'sh', 'r']:
            v = re.sub('i', 'iii', v)

https://github.com/PaddlePaddle/PaddleSpeech/blob/0fa3fdb9ee89ca399b0f63ef2117c6370dc1f33d/paddlespeech/t2s/frontend/zh_frontend.py#L118
:)

That's very kind of you. Thanks a lot.


Update patches.jade

I think this will almost work. Can you adding another commit that un-indents the new spans? They should be siblings of the inputs, not children.

Like this?

Yup, this should work.

Nice!


Remove trailing whitespace

Can't help myself
This PR is sponsored by Vicarious

Yep! Fine by me.


enable ec2token in keystone and add ca file into ec2authtoken secion in heat.conf

https://scertc.austin.ibm.com:9443/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/144251

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

I was under the impression that we weren't going to support the ec2 APIs. I need to clarify with some people.

More exactly, it is for OS::Heat::SoftwareDeployment with signal_transport: CFN_SIGNAL.
They are introduced by using OS::Heat::SoftwareDeployment with default value of signal_transport property in some yaml. Singal_transport is to specify what kind of call when sending signal back to heat. The default value is CFN_SIGNAL. With the default value, heat engine will generate ec2 token and VM will use that ec2 token to call back heat for authentication; when heat-api-cfn receives ec2 token, it will call Keystone for authentication. That is the background of problems on comment 2 and comment 3.
Taking env/manager.yaml as example, the following snippet is to define do_manager_init with SoftwareDeployment type.  It doesn't specify signal_transport so it uses default value of signal_transport: CFN_SIGNAL.
do_manager_init:
type: OS::Heat::SoftwareDeployment
properties:
config:
get_resource: manager_init
server:
get_resource: s
input_values:
target: /opt/deploy

The problem was identified during testing logmet (which uses OS::Heat::SoftwareDeployment) in BB environment. The change is to fix that problem.

In Kilo we can specify what the default should be for signal_transport when one isn't provided. Is there a more appropriate signal we can use that doesn't involve dragging in ec2? Choices of CFN_SIGNAL, TEMP_URL_SIGNAL, HEAT_SIGNAL
This is undocumented, but added here: https://review.openstack.org/#/c/182906/3

Yep, we can change default value to HEAT_SIGNAL.
You said that you won't want to involve dragging in ec2. Does it mean that BlueBox would like to retire heat-cfn-api server? If that is the true, there are multiple occurrences to use CFN as signal URL and we have to go through all of them to change them to use Heat. Would you confirm? Thanks.

HI Jesse,
Niraj just talked with me and confirmed that we won't support ec2 in future even if it cfn service is in BB environment now.
I will submit another change to change default value to HEAT_SIGNAL. In addition, I will go through all similar default values for other resource type and make corresponding changes.
Thanks for your quick comments and info.
Perry

Thanks @panxia6679 . I'll close this one.


Expanding RAM to 32KB

According to the ad Apple 1 could be expanded to 32KB RAM on-board using larger chips. Could you not expand the RAM to 32KB? I think it would be fun with more RAM. The iCE40HX8K-EVB has 512KB RAM.

I don't have that board but geel free to send me one so I can implement it :)

Closing issue as this is board specific and unless someone implements it and submits a PR this really isn't an issue. Thanks anyway.


QueryBuilder\NumericFacet fails when searching for values <= N

Less than or equals 10 should render: @num:[-inf 10], it renders @num:[10 +inf]
PR #1  adds the ability to unittest, with phpunit, and fixes the issue.

Thanks a lot !
Nice catch


Initial API draft description in RAML

Coverage remained the same at 65.541% when pulling 9555cfbefc46bf4c8070fee6bfcf5392871b593b on maretskiy:dev into 29e5c3fae04168dfab8266e8824cbd1c7e29cc73 on seecloud:master.

Coverage increased (+26.1%) to 91.667% when pulling 7b8ab994af79fb24a9d2f896087a201a7d603031 on maretskiy:dev into 29e5c3fae04168dfab8266e8824cbd1c7e29cc73 on seecloud:master.

Coverage remained the same at 65.541% when pulling ba428f780f433653aeb2965be8ec6398f21b257a on maretskiy:dev into 29e5c3fae04168dfab8266e8824cbd1c7e29cc73 on seecloud:master.

Coverage remained the same at 89.773% when pulling dca47fc717c8a4bfd8abbf09e72bde1c7b9b03c0 on maretskiy:dev into e0397281e03fa8e27da562c75afa63259bd4b741 on seecloud:master.

Coverage remained the same at 90.0% when pulling 5b7f9bba45222c2f678aee758be99282d77c0a82 on maretskiy:dev into 578ad1512e01e1860239cb6d7a8cf8fefb6c2155 on seecloud:master.


specifying indexable of cells for RegularGrid cell size properties

When loading an existing RegularGrid, resqpy looks for cell length properties to determine the implicit geometry. This change adds the clause of indexable being set to 'cells'.  (Note that the properties have constant values although they can optionally be written fully expanded.)

Codecov Report

Merging #527 (2b3fa57) into master (327edd2) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #527      +/-   ##
==========================================
- Coverage   79.09%   79.08%   -0.01%
==========================================
  Files         176      176
  Lines       29191    29191
==========================================
- Hits        23088    23087       -1
- Misses       6103     6104       +1

Impacted Files
Coverage Δ

resqpy/grid/_regular_grid.py
85.31% <ø> (ø)

resqpy/model/_xml.py
91.13% <0.00%> (-0.28%)
:arrow_down:

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 327edd2...2b3fa57. Read the comment docs.


add deepsqueak annotation format

docs say it exports both .mat and .xlsx files
https://documentation.help/DeepSqueak/documentation.pdf
I think the .xlsx only has onset / offset -- not clear if the bounding box is in the .mat file?

Apparently there is now a table format although I can't find docs for it
https://github.com/DrCoffey/DeepSqueak/issues/192#issuecomment-1499180882


Parsing variables to publish as topics

The payload field in the Publish Message action doesn't support parsing variables.
This would be a really valuable addition - the ability to push existing data from Companion to the MQTT broker. As the module currently stands, it seems like the only possible payload is manually entered text.
It was suggested in Slack that simply adding variable parsing to the payload in the existing Publish action might be a breaking change, if perhaps someone is pushing actual variable names as payloads rather than the variable values. If that's the case, maybe a new action could be added - Publish Message from Variable

I have the same problem.

it has this feature as of v2.0.2 of the module


Kesaseteli review environments

Description :sparkles:
DevOps review environment
YJDH-658

remove useless azure pipeline files
azure pipeline kesaseteli-review.yml
do not add python virtual environment '.envs' -directory to git (added to .gitignore)
yarn cmd 'browser-test:wsl2win' to run browser tests on wsl2 environment
slack message sender crash test run if any test fails and slack was not configured properly

Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #1973 (42aadbc) into develop (646ac7b) will decrease coverage by 27.12%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop    #1973       +/-   ##
============================================
- Coverage    78.53%   51.42%   -27.12%
============================================
  Files          639       91      -548
  Lines        21331     2003    -19328
  Branches      1304      297     -1007
============================================
- Hits         16752     1030    -15722
+ Misses        4373      889     -3484
+ Partials       206       84      -122

see 548 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

API branch is deployed to platta: https://kesaseteli-pr1973.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

YOUTH branch is deployed to platta: https://youth-pr1973.dev.hel.ninja :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://handler-pr1973.dev.hel.ninja :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-pr1973.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://handler-pr1973.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe employer result is failed for https://kesaseteli-pr1973.dev.hel.ninja :crying_cat_face::anger::boom::boom:

TestCafe youth result is failed for https://youth-pr1973.dev.hel.ninja :crying_cat_face::anger::boom::boom:

TestCafe employer result is failed for https://kesaseteli-pr1973.dev.hel.ninja :crying_cat_face::anger::boom::boom:

TestCafe youth result is failed for https://youth-pr1973.dev.hel.ninja :crying_cat_face::anger::boom::boom:

TestCafe employer result is failed for https://kesaseteli-pr1973.dev.hel.ninja :crying_cat_face::anger::boom::boom:

TestCafe youth result is failed for https://youth-pr1973.dev.hel.ninja :crying_cat_face::anger::boom::boom:

API branch is deployed to platta: https://kesaseteli-pr1973.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

YOUTH branch is deployed to platta: https://youth-pr1973.dev.hel.ninja :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://handler-pr1973.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://handler-pr1973.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://kesaseteli-pr1973.dev.hel.ninja :laughing::tada::tada::tada:

API branch is deployed to platta: https://kesaseteli-pr1973.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://handler-pr1973.dev.hel.ninja :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-pr1973.dev.hel.ninja :rocket::rocket::rocket:

YOUTH branch is deployed to platta: https://youth-pr1973.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://handler-pr1973.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://kesaseteli-pr1973.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe youth result is failed for https://youth-pr1973.dev.hel.ninja :crying_cat_face::anger::boom::boom:

API branch is deployed to platta: https://kesaseteli-pr1973.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-pr1973.dev.hel.ninja :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://handler-pr1973.dev.hel.ninja :rocket::rocket::rocket:

YOUTH branch is deployed to platta: https://youth-pr1973.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://handler-pr1973.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://kesaseteli-pr1973.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe youth result is failed for https://youth-pr1973.dev.hel.ninja :crying_cat_face::anger::boom::boom:

API branch is deployed to platta: https://kesaseteli-pr1973.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-pr1973.dev.hel.ninja :rocket::rocket::rocket:

YOUTH branch is deployed to platta: https://youth-pr1973.dev.hel.ninja :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://handler-pr1973.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://handler-pr1973.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://kesaseteli-pr1973.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://youth-pr1973.dev.hel.ninja :laughing::tada::tada::tada:

HANDLER branch is deployed to platta: https://handler-pr1973.dev.hel.ninja :rocket::rocket::rocket:

API branch is deployed to platta: https://kesaseteli-pr1973.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-pr1973.dev.hel.ninja :rocket::rocket::rocket:

TestCafe handler result is failed for https://handler-pr1973.dev.hel.ninja :crying_cat_face::anger::boom::boom:

TestCafe employer result is failed for https://kesaseteli-pr1973.dev.hel.ninja :crying_cat_face::anger::boom::boom:

TestCafe youth result is failed for https://youth-pr1973.dev.hel.ninja :crying_cat_face::anger::boom::boom:

@terovirtanen There are 12 failing checks:

Node updated to 16 on DevOps pipelines

EMPLOYER branch is deployed to platta: https://kesaseteli-pr1973.dev.hel.ninja :rocket::rocket::rocket:

YOUTH branch is deployed to platta: https://youth-pr1973.dev.hel.ninja :rocket::rocket::rocket:

API branch is deployed to platta: https://kesaseteli-pr1973.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://handler-pr1973.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-pr1973.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://handler-pr1973.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://youth-pr1973.dev.hel.ninja :laughing::tada::tada::tada:


[SAHIL] removing relative import

Removing Relative Import, as due to this we are not able to add it in dep.
Error when we are doing dep ensure - "subpackage github.com/charlesvdv/fuzmatch does not contain usable Go code (*.LocalImportsError).. (Package is required by (root).)"

Can you squash your two commits into one ? :smile:

Hey ,
I squashed 2 commits into 1

Thanks!


Material UI Tooltip position issue in IE11,

Material UI Tooltip should popup on position bottom, it's abnormal in IE11,
It will flash on the left top position of document and then appear on the normal position bottom(default position)
It's so wierd, this issue will be fix by import blue-bird, but in some reason I can't use this library
So what's another solution.
Current Behavior 😯

It will flash on the left top position of document and then appear on the normal position bottom(default position)
Expected Behavior 🤔

Steps to Reproduce 🕹
Steps:

Hold typing like key a in the input box, It's will flash.
Type quickly and continuity in the input box, It's will flash.

Context 🔦
This issue will be fix by import blue-bird, but in some reason I can't use this library. So what's another solution.
Your Environment 🌎

IE11

`npx @material-ui/envinfo`

    System:
    OS: Windows 10 10.0.19041
  Binaries:
    Node: 12.16.2 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Not Found
  npmPackages:
    @material-ui/core: ^4.5.2 => 4.11.4
    @material-ui/icons: ^3.0.1 => 3.0.2
    @material-ui/pickers: ^3.2.8 => 3.3.10
    @material-ui/styles: ^4.4.1 => 4.11.4
    @material-ui/system:  4.11.3
    @material-ui/types:  5.1.0
    @material-ui/utils:  4.11.2
    @types/react:  17.0.11
    react: ^16.12.0 => 16.14.0
    react-dom: ^16.9.0 => 16.14.0

See https://next.material-ui.com/getting-started/supported-platforms/#ie-11


lost <IP_ADDRESS> connection

Ben,
I have been successfully running Irrigator for a while now and it has been performing flawlessly but, I now cannot connect via chrome with <IP_ADDRESS> after a series of power outages, I can successfully log on the RP via SSH. Any thoughts on why this behavior?
Neal Musto

Ben, I have been successfully running Irrigator for a while now and it has been performing flawlessly but, I now cannot connect via chrome with <IP_ADDRESS> after a series of power outages, I can successfully log on the RP via SSH. Any thoughts on why this behavior?

Are you connecting to SSH on the same IP?
What's the error message on chrome when you try to go to the IP address?  Are you getting a response form the server (i.e. Server Timeout, Error Code 500, 404, etc.)?  Or is it just not responding at all?
Try http://<IP_ADDRESS>:9000 to get to the supervisor interface (enter the username and password you used during installation).  If this works, you should be able to see if the web app is running or not.  If it's not running, we can perhaps check the logs (I think located at /usr/local/bin/irrigator/logs.
Let's start with those first.

With both <IP_ADDRESS> and <IP_ADDRESS>.9000 I get "The connection has timed out" or " using Chrome "This site can't be reached"
This is what is in logs:
backuplog-2023-08-01.log
backuplog-2023-09-01.log
backup.sh
webapp.err.log
webapp.out.log
The contents of the 09 backuo only goes to the end of august (08)
neal

Are you connecting to SSH on the same IP?  What I'm getting at here is that unless you've made the IP static on your router, it will sometimes give you a new IP after a reboot of the router (i.e. power outage).
When you are SSH'd into your Pi, let's try to look at the logs to see if we can get a clue of what might be happening.

In the logs folder, look at the webapp.err.log and post what it shows.  (we probably should look at webapp.out.log too.
pi@irrigator:~ $ cat webapp.err.log

Have supervisor tell us what is running (hopefully the webapp):

pi@irrigator:~ $ sudo supervisorctl status
webapp                           RUNNING   pid 7609, uptime 51 days, 16:15:41
pi@irrigator:~ $

I suspect that the supervisor is not running because it's not responding.

I am SSHing  to the address capture by an IP scanner for the RPi not <IP_ADDRESS> and no I have  the router  set to a dynamic IP.
 Is this because not having a static IP addrees on the router?

I see, your IP has changed, probably because your router was rebooted during the power-loss.  So yes, the best thing to do would be to make a static IP on your router for this Pi.  Something that is outside of the range of IP's that are designated for your DHCP.
Perhaps something like <IP_ADDRESS> might work well (I'm guessing your DHCP range is <IP_ADDRESS>-199).
This way if you lose power again, you can always know that your Pi is at that particular IP address.

I looked at the recent log and found an anomaly, see below

2023-09-14
04:55:02
***** Control Script Starting *****

2023-09-14
04:55:02
Initializing Relays on Raspberry Pi.

2023-09-14
04:55:02
Current Temperature: 65F Precipitation History: 0.0 inches Precipitation Forecast: 0.0 inches

2023-09-14
04:55:02
Schedule Run Selected with Schedule: BackYard

2023-09-14
04:55:02
BackYard found in JSON file. Running Now.

2023-09-14
04:55:02
Turning on Zone: 1_front_yard for 60 minutes.

2023-09-14
05:45:06
Exception occured when reading irrigator.json.  Creating the file with default settings.

2023-09-14
05:55:03
Turning off Zone: 1_front_yard.

2023-09-14
08:00:02
***** Control Script Starting *****

2023-09-14
08:00:03
Initializing Relays on NONE.  Prototype Mode.

2023-09-14
08:00:03
Current Temperature: 0F Precipitation History: 0.0 inches Precipitation Forecast: 0.0 inches

2023-09-14
08:00:03
Irrigation cancelled due to weather status exceeding limits. (Temperature)

2023-09-14
08:00:03
Exiting with errorcode = 1

2023-09-14
08:00:03
***** Control Script Ended *****

2023-09-14
11:05:02
***** Control Script Starting *****

2023-09-14
11:05:02
Initializing Relays on NONE.  Prototype Mode.

2023-09-14
11:05:02
Current Temperature: 0F Precipitation History: 0.0 inches Precipitation Forecast: 0.0 inches

2023-09-14
11:05:02
Irrigation cancelled due to weather status exceeding limits. (Temperature)

2023-09-14
11:05:02
Exiting with errorcode = 1

2023-09-14
11:05:02
***** Control Script Ended *****

2023-09-14
12:12:27
***** Control Script Starting *****

2023-09-14
12:12:27
Initializing Relays on NONE.  Prototype Mode.

2023-09-14
12:12:27
Current Temperature: 0F Precipitation History: 0.0 inches Precipitation Forecast: 0.0 inches

2023-09-14
12:12:27
Initialize Relays Selected.

2023-09-14
12:12:27
Exiting with errorcode = 0

2023-09-14
12:12:27
***** Control Script Ended *****

Looks like you need to go configure your settings.  The platform should be set to Raspberry Pi.

Also, if you are not using weather settings, then you should make sure these sliders are disabled (opposite of the below picture):

just went in and fixed that.
don't have the tab for trigger settings we did that manually the last time, i will go back to that series of discussions and repeat.
Is it possible to update IE, sudo update XXXX?
On another note i am using this to run a drip system which typically runs for more that 60 minute, the max imposed by the system, Can you direct me to where this is impose so that i can change the limit?

also is there a way to backup the settings

just went in and fixed that. don't have the tab for trigger settings we did that manually the last time, i will go back to that series of discussions and repeat. Is it possible to update IE, sudo update XXXX?

Yeah, the feature for trigger settings is in the latest version so you will need to update to get that.  The best way is a fresh installation.  But if that is too difficult, then you can try to run:
cd /usr/local/bin/irrigator
sudo git pull

Then, you will need to go edit the irrigator.json file:
sudo nano irrigator.json

Then ADD the line for relay trigger to the 'settings' section (make sure you add a comma after the 'zone_gate' line):
  "settings": {
    "target_sys": "RasPi",
    "zone_gate": 29,
    "relay_trigger": 1
  },

Note: It's set to 1 because you have an active high relays if I remember correctly.  If you had active low, it would be set to 0.
Next, reboot and cross your fingers.  If this doesn't work, you may need to wipe your SD Card and re-install.
If you want to backup your settings, simply copy your irrigator.json to another file:
sudo cp irrigator.json irrigator.json.backup

On another note i am using this to run a drip system which typically runs for more that 60 minute, the max imposed by the system, Can you direct me to where this is impose so that i can change the limit?

Pretty simple change here, but you'll need to edit the file /usr/local/bin/irrigator/templates/schedules.html

Just remove the max="60" parameter from line 276 and 464.

Save and then go reload your page and edit.

the git pull doesn't work see below.
nealw@irrigator:/usr/local/bin/irrigator $ sudo git pull
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint:   git config pull.rebase false  # merge (the default strategy)
hint:   git config pull.rebase true   # rebase
hint:   git config pull.ff only       # fast-forward only
hint:
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
remote: Enumerating objects: 29, done.
remote: Counting objects: 100% (29/29), done.
remote: Compressing objects: 100% (14/14), done.
remote: Total 17 (delta 12), reused 8 (delta 3), pack-reused 0
Unpacking objects: 100% (17/17), 4.86 KiB | 41.00 KiB/s, done.
From https://github.com/nebhead/irrigator
f497a86..4bba62d  main       -> origin/main
Updating f497a86..4bba62d
error: Your local changes to the following files would be overwritten by merge:
control.py
platform_raspi.py
Please commit your changes or stash them before you merge.
Aborting
do i do the hints?

No, the hints won't really help you out in this case.
  If that's easiest.

i was thinking that since everything seems to work now and if it all goes south again then I'll wipe and reload..
Thanks for the help, your the man.

i was thinking that since everything seems to work now and if it all goes south again then I'll wipe and reload.. Thanks for the help, your the man.

Good plan!  You're very welcome.  Enjoy!


bam sort output

Seems like the output of samtools sort should be directed into the output folder, not the folder containing the input bam files (which may be read-only).

I can catch that exception and redirect to the output folder.


alhaitham chisel mirrors issues

his mirrors icd has a problem and
he only releases 1 mirror attack WAVE when he has 1 mirror, it supposed to be 2 waves

Please provide a viewer link to an example sim and point out specifically what is wrong.

u should try running this. his chisel mirror doesnt spread frequently as it should be. it doesnt spread until the 7th hit in reality it procs spread every 2 hits
https://gcsim.app/sh/1b1c24e2-36ee-470e-b5eb-d43e95b548c1

His mirror elemental application ICD is correct (12s timer, alternating 1 0 1 0 ... hit rule) and it is correct that when he has 1 Mirror he only releases 1 Mirror attack wave (see his talent description/scaling or gameplay). The reason why you experience such few spreads, is because the other team members constantly react with the quicken aura and the Mirror elemental application happens to line up in such a way that it applies dendro when there is no quicken aura on the enemy (see the Sample tab with only the action, character, damage and element categories turned on). This is due to timings, you can try adding/removing actions to observe if you get more spreads/dps. As far as I can tell, nothing is bugged here.

when he has 1 mirror he deals 1 slash BUT after 1.8s later he deals another slash (aka WAVE) until his mirrors disappear.
3 mirrors 2 wave 3 hits
2 mirrors 2 wave 2 hits
1 mirror 2 wave 1 hit
however the simulator only shows 1 wave

That's not how his mirrors work. If you proc a 1/2/3 Mirror wave, then there are only 1/2/3 hit(s) in a single wave. Please check against ingame/video footage if you don't believe me.

im not talking about hit im talking about waves. all his mirrors send out 2 waves however the simulator only gives him 1 wave when he has 1 mirror

u can try "attack:3,dash" 2 times when he has 1 mirror. u only see 1 wave

Here's a config with the actions you gave me: https://gcsim.app/sh/F9DhJTH9NQz8
As you can see he gets 2x 3 Mirror waves, 2x 2 Mirrow waves, 1x 1 Mirror waves. What you're saying doesn't line up with what I see here and it all seems not bugged to me.

This is because the sim is faster than 99% of humans without adding in waits, so your last N3D ends before the proc cooldown is up. Here's an example where I achieved what you described by adding a wait(40);: https://gcsim.app/sh/DcTzTcmDf7pQ

okay so everything works like intended right? i can be wrong but atleast i figured things out. thank for explaining things to me and sr for wasting ur time. btw "skill[hold=1], high_plunge" make the sim stop working. is this normal?

Yes, everything works as intended. Don't worry about wasting my time, at least we were able to clear it up. Yes, it's normal that high_plunge doesn't work, only low_plunge is legal.


[Feature Request]: SimpleDirectoryReader reading from AWS S3

Feature Description
https://docs.llamaindex.ai/en/stable/core_modules/data_modules/storage/save_load.html#using-a-remote-backend
This demo has SimpleDirectoryReader reading in documents from local storage.  It would be cool if SimpleDirectoryReader could directly integrate with AWS S3 via s3fs.S3FileSystem.
Reason
Not having to store raw corpus on local filesystem.
Value of Feature

Increased flexibility when creating VectorStores
Symmetry with StorageContext's support for fs as an input

We have https://llamahub.ai/l/s3. Is this basically what the suggestion is?

Thanks for sharing that link. A line from https://llamahub.ai/l/s3:

All files are temporarily downloaded locally and subsequently parsed with SimpleDirectoryReader.

To me, this means S3Reader isn't "reading" from S3, it's downloading from S3 and then locally opening the files. I can easily reinvent this with boto3 in my own Python code. This request is about eliminating the local filesystem extra stop.
Ideally, SimpleDirectoryReader (or a true S3Reader) can directly read from AWS S3 into a Python process using something like the abstract filesystem specs.

I support this as I am trying to build my own logic that allows me to use PDF files from a cloud source as well (Google Cloud bucket) but I'm having issues when passing those processed files (Strings) into GPTSimpleVectorIndex. I'm getting the error: Error occurred while constructing index: Invalid document type: <class 'str'>.
Not sure what type the files have to be in order to be accepted? JSON?
Directly supporting this would be awesome and save me some time. The goal is to be able to create a mobile version of my app and the first step is removing the need for locally stored documents to use with queries.

Thanks @jamesbraza! I believe you're referring to using something like s3fs, correct?

Yeah that's correct @nerdai 👌 feel free to ask for other clarifications if needed

@MrGobert thanks for sharing, I agree with you it's useful to avoid the local filesystem entirely, in some use cases.
It sounds like your "Invalid document type: <class 'str'>." thing might be a separate issue, would you mind opening a new issue and providing the full stack trace there?  By GPTSimpleVectorIndex, did you actually mean SimpleVectorStore?

A couple of other reasons this would be useful:

s3 loader downloads files in a temp directory locally and doesn't keep a track of file names. This makes it difficult to track them if you need them later to present sources of your RAG output. I opened an issue here before: https://github.com/run-llama/llama-hub/issues/611

You can't use document refresh() with this s3 loader since file names are generated randomly and refresh() uses filename_as_id flag.

Let me know in case of any questions. Thanks!

I support this as well for all the excellent reasons articulated already.

Does anyone work on this? If not, I would be happy to help.

Does anyone work on this? If not, I would be happy to help, i.e. you can assign that to me if no one has already worked on it.

Thanks @MacOS for taking this on! With our v0.10 release, I am wondering if this should live as it own integration package. Please take a look at our Contributing Guide. I believe this could exist as a new reader integration.

@nerdai Thank you for the pointers!

Hi @MacOS I have a PR here that adds this very feature!
https://github.com/run-llama/llama_index/pull/11303
It adds an optional fs parameter to SimpleDirectoryReader which can be any fsspec file-system object, including s3fs.
Should be merged soon :)

@jamesbraza  @MacOS FYI my PR has been merged and should be available in the next release! feel free to re-open if there are any further concerns.

@sourabhdesai Well, that was fast.
No concerns from my side.

Hi! I'm using this on a project and it works great with .txt and .md files reading from S3. I get an error with .doc and .pdf files however:
Failed to load file s3-bucket-name/media/documents/FILENAME.pdf with error: 'S3File' object has no attribute 'name'. Skipping...
Any ideas on why this is happening only with certain filetypes?

sourabhdesai Thanks a lot for the addition of fsspec 👍
I get the same error
Failed to load file s3bucket/.../.../doc.pdf with error: 'S3File' object has no attribute 'name'. Skipping.
I remember encountering the same error a week ago but resolved it when updating llama-index but that doesn't seem to do the job now.

Same thing happening to me when reading files
with error: 'S3File' object has no attribute 'name'. Skipping.


Cleanup Project Structure To Meet .NET Standards

Proposed changes
This PR does the following:

Deduplicates many resource files
Flattens the projects found within the examples and tests directories per .NET convention
Resolves https://github.com/advisories/GHSA-hh2w-p6rv-4g7w
Updates the .gitignore file
Updates all dependencies to their latest version

Types of changes
What types of changes does your code introduce to the community .NET SDK?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update or tests (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have lint'ed all of my code using repo standards
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

Further comments
This PR is the first of many for updating this repository to meet the standard .NET project layout and practices. The next PR will be cleaning up the example and test code, then using the conventional logging from Microsoft.Extensions.Logging.Abstractions.
https://wakatime.com/@a8e4b5db-b8cc-469a-acce-099a0a2425be/projects/dammoujrda?branches=oolunar%2Fupdate-infra&start=2024-10-30&end=2024-11-05

Some comments:

This is likely to break the release process.
You need to update all the documentation to update all links to these files (ie examples, clients, etc)

@OoLunar
the PR is very large to review for  the team and this approach to refactor the code base isn't what we are looking for at this time.
the unit tests are broken: https://github.com/deepgram/deepgram-dotnet-sdk/actions/runs/11692426812/job/32562168995?pr=352
the build is broken: https://github.com/deepgram/deepgram-dotnet-sdk/actions/runs/11692426812/job/32562168134?pr=352
I am guessing the upload to nuget is also broken.
The docs would need to be fixed in multiple places, which isn't something we want to do right now.
I think it be best to close this out as our main goal should be be to maintain and support the existing SDK, not focus on a large refactor at this time.

the PR is very large to review for the team and this approach to refactor the code base isn't what we are looking for at this time. [...] I think it be best to close this out as our main goal should be be to maintain and support the existing SDK, not focus on a large refactor at this time.

That's entirely okay. I still think we should update the dependencies at minimum to address the STJ vulnerability, however the rest of this work can be done again on a different day. I'll save this branch for later, nothing a bit of rebase magic can't help with.


gateway-api: Filter out unused listeners

Unused listeners should not be used, otherwise users can also access the service through unused listeners.
Fixes: #31122 #31717
gateway-api: Filter out unused listeners

Hi, @timoreimann Do you have time to take a look at this PR?

/test

/ci-gateway-api

Thanks for taking a stab at this, @chaunceyjiang. I'll make sure to give this a try as soon as I can.

@timoreimann Thanks so much for testing this PR. I've also found that it doesn't actually solve the problem.
The right solution should be what you described in #31122.


Change the error when trying to use f-string

Summary or solution description
The previous error was: Expected type 'str', got 'none' instead, now it's a NotSupported error.
How to Reproduce
https://github.com/CityOfZion/neo3-boa/blob/81bf9754420d61b4bd2d317b8c14b19aedd080fe/boa3_test/test_sc/string_test/FormattedStringLiteral.py#L1-L3
Tests
https://github.com/CityOfZion/neo3-boa/blob/81bf9754420d61b4bd2d317b8c14b19aedd080fe/boa3_test/tests/compiler_tests/test_string.py#L1480-L1482
Platform:

OS: Windows 10 x64
Python version: Python 3.7

Task linked: CU-86a0b3mcw Change the error when trying to use f-string


chore: run lints and build in parallel

Testing

Trade-offs

Dependencies

Screenshots

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

v3.0.30
GitHub release

Your semantic-release bot :package::rocket:


Add YAMMBS-specific models

[x] Add a model/file for QM input data that is specific to YAMMBS but does not store results
[ ] Test serialization, round-trips
[ ] Refactor existing scripts, test data to use these file(s)
[ ] Check performance on a large dataset?
[ ] Example creating some sort of QM dataset from non-QCArchive data (i.e. a big SDF file)

Codecov Report
Attention: Patch coverage is 0% with 27 lines in your changes missing coverage. Please review.

Project coverage is 82.27%. Comparing base (09720ba) to head (79af2fd).
Report is 16 commits behind head on main.

Additional details and impacted files

Okay, the ballooning of file size is not going to work ...
$ ls -lahrS yammbs/_tests/data/*/01*json | awk '{print $9, $5}'         15:51:16  ☁  input-models ☂ 𝝙
yammbs/_tests/data/yammbs/01-processed-qm-ch.json 160K
yammbs/_tests/data/qcsubmit/01-processed-qm-ch.json 1.4M
yammbs/_tests/data/qcsubmit/01-processed-qm-cho.json 2.0M
yammbs/_tests/data/yammbs/01-processed-qm-cho.json 4.4M
yammbs/_tests/data/qcsubmit/01-processed-qm.json 31M
yammbs/_tests/data/yammbs/01-processed-qm.json 226M

Nevermind, the difference is that these files actually contain coordinates. I forgot they were not present in the QCSubmit files


First screen after fresh installation and missing links

I've installed the package with composer require binarytorch/larecipe and forget to run php artisan larecipe:install.
The look&feel of mysite/docs give this:

Oups, something is wrong (perhaps you can detect the absence of your template?) and show a nice message "Please don't forget to fire php artisan larecipe:install."
So, I run the artisan command and now the screen looks like better but there are a lot of errors in my console.

Indeed, no fonts and no logo at the top left.
I've tested under a totally new installation (Laravel new larecipe) which is, today, on Laravel 5.7.2.

Hi @cavo789
Thank you very much for your contribution and finding the mentioned bugs and issues.

I really like your idea of showing a small feedback when a user forgets to run the install command and now this enhancement available on dev-master and will be added to the upcoming version. See here

Regarding your installation with Laravel v5.7, I'm not quite sure what's the problem of preventing the assets of showing up. I reproduced the installation with fresh laravel 5.7 installation and here is my output.

However, if you can see in my console the only thing is missing is the app logo which is solved now by showing the default larecipe logo instead of confusing a user with blank image unless the user changes the app logo in the config, see here.
One gatcha I guess what prevents showing the assets in your case is the cache in your browser when hit the /docs for the first time before running the install command, could you please clear your cache and tell me back I'll be happy to help you out.
Thank you again 😍


Pattern Searcher yields incorrect results

On the following example:
use egg::{*, rewrite as rw};

fn main() {
    env_logger::init();
    let rules: &[Rewrite<SymbolLang, ()>] = &[
        rw!("manual_1"; "(+ (move 4 4 (scale 2 ?a)) ?b)" => "whatever"),
        rw!("manual_2"; "(+ (move 4 4 (scale ?a line)) ?b)" => "whatever"),
        rw!("manual_3"; "(+ (move ?a 4 (scale 2 line)) ?b)" => "whatever"),
        rw!("manual_4"; "(+ (move ?a 4 (scale 2 line)) (+ (move 3 2 line) (+ ?c ?d)))" => "whatever"),
        rw!("manual_5"; "(+ (move 4 4 ?a) (+ (move 3 2 ?b) (+ (move 4 3 (scale 9 ?c)) (move 5 2 ?d))))" => "whatever"),
        rw!("manual_6"; "(+ (move 4 4 (scale 2 line)) (+ (move 3 2 line) (+ (move 4 3 (scale 9 circle)) ?d)))" => "whatever"),
        rw!("manual_7"; "(+ (move 4 4 (scale 2 line)) (+ (move 3 2 line) (+ (move 4 3 (scale 9 circle)) (move 5 2 line))))" => "whatever"),
    ];

    let start = r"(let s1 (+ (move 4 4 (scale 2 line)) (+ (move 3 2 line) (+ (move 4 3 (scale 9 circle)) (move 5 2 line))))
  (let s2 (+ (move 4 4 (scale 2 circle)) (+ (move 3 2 circle) (+ (move 4 3 (scale 9 circle)) (move 5 2 circle))))
    (+ s1 s2)))".parse().unwrap();
    Runner::default().with_expr(&start).run(rules);
}

Running this example with egg 0.6.0 with debug logging enabled shows that every rewrite matches and is executed at least once, as is expected:
...
[2021-05-11T01:59:53Z DEBUG egg::run] Applying manual_1 2 times
[2021-05-11T01:59:53Z DEBUG egg::run] Applying manual_2 1 times
[2021-05-11T01:59:53Z DEBUG egg::run] Applying manual_3 1 times
[2021-05-11T01:59:53Z DEBUG egg::run] Applying manual_4 1 times
[2021-05-11T01:59:53Z DEBUG egg::run] Applying manual_5 2 times
[2021-05-11T01:59:53Z DEBUG egg::run] Applying manual_6 1 times
[2021-05-11T01:59:53Z DEBUG egg::run] Applying manual_7 1 times
...

However, running this example using the main branch version of egg yields incorrect results; some rewrites which should match and execute don't:
[2021-05-11T02:00:48Z DEBUG egg::run] Applying manual_1 0 times
[2021-05-11T02:00:48Z DEBUG egg::run] Applying manual_2 0 times
[2021-05-11T02:00:48Z DEBUG egg::run] Applying manual_3 1 times
[2021-05-11T02:00:48Z DEBUG egg::run] Applying manual_4 1 times
[2021-05-11T02:00:48Z DEBUG egg::run] Applying manual_5 0 times
[2021-05-11T02:00:48Z DEBUG egg::run] Applying manual_6 0 times
[2021-05-11T02:00:48Z DEBUG egg::run] Applying manual_7 1 times

Some commit bisecting seems to indicate that this problem was introduced with #74 (commit 3f4c07a).

Good catch! I think I spotted the bug (link). It's because I'm using a different ordering in ground_locs and ground_terms, so wrong ground terms are loaded. I made a fix locally (but not sure what's the best way to get it integrated).

@yihozhang can you just make another PR with the changes? And @dcao can validate on that branch.