Filtered records count taking a long time

Summary of problem or feature request
When calculating the total filtered records in a datatable of ~1M record the count is taking up to 40s whereas the query to display the records is only taking 10ms.
Is there any way to disable the filtered records count?
I know there is a method setTotalRecords() which disables the count of the total number of records but would it be possible to add something similar to prevent the count taking place in the filterRecords() method in DataTableAbstract?
System details

Operating System MacOS Sierra
PHP Version 7.1.6
Laravel Version 5.5
Laravel-Datatables Version ~8.0

Afaik, disabling filtered counts is not yet supported. Will try to dig option this when I got the chance.
On the other hand, have you tried optimizing your queries using indexes and other db optimization tricks?

Great thanks!
Yeah I've tried to optimise as best I can. We have a table with roughly 50M rows which is well indexed and the select queries are fine, it just seems to be the count that takes ages.

I agree this might be a huge improvement, looking forward to set filtered count manually.

Yes, this is a big problem for me as well.

Yes, I am too need setFilteredCount for big tables.
Could you add feature, please

For anyone interested, I've circumvented this issue temporarily. I have a branch on my fork that adds a function setFilteredRecords() for the query builder datatable. This will allow you to manually set that count. My strategy to deal with large (many millions of rows) Innodb tables is to manually query the count and cache it to a unique key derived from the query that was executed. The query will take a long time to execute the first time around but any subsequent requests are instant.

@forgottencreature I just saw your changes and I think it's a good implementation for this issue. Would you mind submitting a PR?
BTW, this line is required and a fix added on v8.5.1.

@yajra Sure thing. I'll submit the PR tomorrow.

PR submitted!

I considered adding support for that in this PR but I wasn't sure what that would look like given you need a count otherwise it won't know how many pages to display.

@forgottencreature You're right.


Front-End: Fetching User details from API

Pulling User details from database and displaying them in react table.


static-adapter expand dynamic routes according to paths set in conig.kit.prerender.entries generating same result as if they were wrote in static way

Describe the problem
Use case:
Imagine that you are writing an SEO-friendly website, where the website has the same structure, the same content, and the only difference is the language. Let's say expected structure of the website is:
/index.html
/ja/index.html
/es/index.html
/blogs/a_blog.html
/ja/blogs/a_blog.html
/en/blogs/a_blog.html
/es/blogs/a_blog.html
It would be nice if I can write once in Svelte with following routes:
[slug]/index
[slug]/blogs
And build with conig.kit.prerender.entries set to:
[
/index.html
/ja/index.html
/es/index.html
/blogs/a_blog.html
/ja/blogs/a_blog.html
/en/blogs/a_blog.html
/es/blogs/a_blog.html
]
And static-adapter can expand the dynamic routes into expected structured website which can be hosted in S3 directly (doesn't have to be hosted behind server).
Note：I know static-adapter can works with dynamic routes as long as a fallback is given. But the generated site have to be hosted behind a node-server(?) or something like that, can't be hosted in S3 directly. Which, I think, is not static.
Describe the proposed solution
It would be nice if static-adapter could expand dynamic routes according to paths set in conig.kit.prerender.entries and generate same result as if they were wrote in static way.
For example:
Given a Svelte project with dynamic routes:
[slug]/index
[slug]/blogs
and conig.kit.prerender.entries set to:
[
/index.html
/ja/index.html
/es/index.html
/blogs/a_blog.html
/ja/blogs/a_blog.html
/en/blogs/a_blog.html
/es/blogs/a_blog.html
]
The result of this project generate by static-adapter should be equivalent to
a Svelte project with static routes:
routes/
--/index
--/ja/index
--/es/index
--/blogs/a_blog
--/ja/blogs/a_blog
--/en/blogs/a_blog
--/es/blogs/a_blog
Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response

I'm confused. Does this not work currently work? You should be able to specify the value of slug to prerender dynamic routes with config.kit.prerender.entries. https://kit.svelte.dev/docs/configuration#prerender

I'm confused. Does this not work currently work? You should be able to specify the value of the slug to prerender dynamic routes with config.kit.prerender.entries. https://kit.svelte.dev/docs/configuration#prerender

I've tried, it works, but not static. The generated site can't be deployed to S3 directly. Dynamic routes with specified value are generated as some js file instead of a html page, so they can't be accessed directly(like: https://host/some_dynamic_route_here.html), they're only accessible through index.html.
As a comparison, static routes will be generated as corresponding HTML pages, and each route can be directly accessed without going through the index page.
In this aspect, I believe there are differences between the two.

You'll need to share a minimal reproduction of how you've setup your dynamic routes. It should produce a html page for each of your specified entries if you have marked your dynamic route to be prerendered.

I guess know where the problem is now. I must place export const prerender = true; outside of the [slug]/ in the +layout.ts file. If I put it inside the [slug]/ in the +page.ts file, Svelte will require me to specify a fallback path, and in this case, dynamic routes will be generated as some JavaScript files

It's mentioned in the docs that you should have export const prerender = true; in the root layout of your routes directory so that all pages are marked as prerendered. This is also mentioned in the error message when building your project.
https://kit.svelte.dev/docs/adapter-static#usage


[pycodestyle] Respect isort settings in blank line rules (E3*)

Summary
This PR changes the E3* rules to respect the isort lines-after-imports and lines-between-types settings. Specifically, the following rules required changing

TooManyBlannkLines : Respects both settings.
BlankLinesTopLevel: Respects lines-after-imports. Doesn't need to respect lines-between-types because it only applies to classes and functions

The downside of this approach is that isort and the blank line rules emit a diagnostic when there are too many blank lines. The fixes aren't identical, the blank line is less opinionated, but blank lines accepts the fix of isort.

Outdated approach
Fixes https://github.com/astral-sh/ruff/issues/10077#issuecomment-1961266981
This PR changes the blank line rules to not enforce the number of blank lines after imports (top-level) if isort is enabled and leave it to isort to enforce the right number of lines (depends on the isort.lines-after-imports and isort.lines-between-types settings).
The reason to give isort precedence over the blank line rules is that they are configurable. Users that always want to blank lines after imports can use isort.lines-after-imports=2 to enforce that (specifically for imports).
This PR does not fix the incompatibility with the formatter in pyi files that only uses 0 to 1 blank lines. I'll address this separately.

Review
The first commit is a small refactor that simplified implementing the fix (and makes it easier to reason about what's mutable and what's not).
Test Plan
I added a new test and verified that it fails with an error that the fix never converges. I verified the snapshot output after implementing the fix.

I don't know that I have better suggestions, but I'll admit that I'm nervous to make the rule contingent on whether another rule is enabled, since it means ruff check --select E and ruff check --select E --select I will show discontinuous diagnostics, which can make for a really confusing debugging experience.

Hmm that's a good point. The alternative is to never touch blank lines after imports and direct users towards isort? Although that's a bit overkill if all you want is 2 blank lines

So the options I see are

Remove the blank line rules
Never enforce blank lines after or between imports (forcing users to use isort)
Disable blank lines when isort is activated (what we do for other incompatible rules)
Use isort.lines_after_imports or isort.lines_between_types after imports or between imports in the blank line rule (A bit weird that it respects options from another rule)

Use isort.lines_after_imports or isort.lines_between_types after imports or between imports in the blank line rule (A bit weird that it respects options from another rule)

I was thinking about that one. As you said it's a bit weird to use options from another rule, but that allows using both rule sets.
Also, this weirdness would likely not be visible to a user (it seems unlikely to me that someone would specify the isort options but not select isort), so it would be a matter of handling the added complexity in the blank rules in a way that is maintainable.

The ecosystem results seem outdated. I ran the checks locally and there are no changes

Just to confirm, this change won't fix the issue in #10077, correct? I'm testing things out with this branch but still see the infinite loop when running on .pyi files.

Just to confirm, this change won't fix the issue in #10077, correct? I'm testing things out with this branch but still see the infinite loop when running on .pyi files.

Nice find. It seems specific to a class coming after imports when using lines-after-imports=1 Let me revisit the tests to see why this case isn't covered.

Just to confirm, this change won't fix the issue in #10077, correct? I'm testing things out with this branch but still see the infinite loop when running on .pyi files.

Okay, the issue is specific to pyi files and is fixed by https://github.com/astral-sh/ruff/pull/10098

@hoel-bagard thank you for your review and fixing the indentation.


mace3D interface and docstring update

This PR contains the updated interface of mace3D function.
It looks like a lot of changes, but the majority of the changes are in the interface & docstring part of mace3D function.
Interface available here: mace.pdf
Specifically, here are the changes to the interface:

Added arguments num_image_rows, num_image_cols, num_image_slices, image_slice_offset to align the mace interface to the recent interface change regarding ROR recon.
Deleted argument ror_radius.
Reordered arguments to align with the interface of recon function.

Tested with demo_mace3D.py and demo_mace3D_fast.py, and it worked fine.
Once this is done, we will make similar changes to mace4D.
After that, we may start working on the interface change regarding delta_det_channel and delta_det_row.

Ok. It looks good to me.

@cabouman A kind reminder on this PR. Once this is merged I'll make similar updates to mace4D interface. After that we may work on the interface change regarding delta_det_row and delta_det_channel (issue #107).


feat(doc): Update maintainer list according to activity and add  steering commitee member…

…ring commitee member

Motivation

Explain here the context, and why you're making that change. What is the problem you're trying to solve.

Some maintainers are not active enough, or there are too many overlapping positions within the maintainers.
A steering committee has been added to better achieve community autonomy governance
Modifications

Describe the modifications you've done.

@bboyCH4 @jadewang198510 transfer to committer

Types of changes

Show in a checkbox-style, the expected types of changes your project is supposed to have:

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

Verifying this change

(Please pick either of the following options.)

[x] Make sure that the change passes the testing checks.

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

This can be verified in development debugging
This can be realized in a mocked environment, like a test cluster consisting in docker

(or)
This change MUST reappear in online clusters, or occur in that specific scenarios.
Does this pull request potentially affect one of the following parts:

Which of the following parts are affected by this change?

[ ] Master
[ ] MetaNode
[ ] DataNode
[ ] ObjectNode
[ ] AuthNode
[ ] LcNode
[ ] Blobstore
[ ] Client
[ ] Cli
[ ] SDK
[ ] Other Tools
[ ] Common Packages
[ ] Dependencies
[x] Anything that affects deployment

Documentation

Is there a chinese and english document modification?

[ ] doc
[ ] doc-required
[ ] doc-not-needed
[x] doc-complete

Review Expection

How long would you like the team to be completed in your contributing?

[x] in-two-days
[ ] weeks
[ ] free-time
[ ] whenever

Matching PR in forked repository

enter the url if has PR in forked repository.

PR in forked repository:

+1

+1

+1

+1

+1

+1


significance of LockAssert

Is your feature request related to a problem? Please describe.
I am raising this issue for one clarification, being a newbie. In the scheduler code mentioned in the example, the first line is as below:
 `LockAssert.assertLocked();`

According to my understanding, the job can be scheduled on any of the given pod at a given time, when the lock is held by the pod itself.
So, the above line will get executed only if the associated POD has the lock. With this logic, I think the LockAssert line is redundant.
Please correct me, if I am wrong. Also, it would be great if you give one small example when things will break if I don't add this line.

https://github.com/lukas-krecan/ShedLock#lock-assert

Hi @lukas-krecan , yeah I saw this. To prevent misconfiguration errors, we can assert that the lock works by using LockAssert.
But I don't quite understand what is meant by misconfiguration error. Is it possible to give one very small example?


meta parameter in all routes

a fastify plugin that implement new meta for all endpoints that return additional metadata information in the results.
For example:

original locations
processing times
CRS for locations
units of values

solution: https://www.fastify.io/docs/latest/Reference/Hooks/#onroute


Always getting prompted to select a python interpreter

Environment data

VS Code version: XXX
Extension version (available under the Extensions sidebar): XXX
OS and version: XXX
Python version (& distribution if applicable, e.g. Anaconda): XXX
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): XXX
Relevant/affected Python packages and their versions: XXX
Relevant/affected Python-related VS Code extensions and their versions: XXX
Value of the python.languageServer setting: XXX

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
Should not get prompted to select an interpreter everytime
Actual behaviour
Getting prompted to Select Python interpreter everytime user loads VS Code.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

I get this prompt for every session. Once I've selected an interpreter, I don't get it any more. However, if I do select "Developer: Reload Window" then I do get the prompt again.

Original comments from issue https://github.com/microsoft/vscode-python/issues/13809#issuecomment-700237298:
> @davidcieslak
> Do you always get the prompt `No Python interpreter is selected. You need to select a Python interpreter to enable features such as IntelliSense, linting, and debugging.`

yes

> **Questions**
>
> * I.e after reloading VS Code, do you still get this prompt?

I get this prompt for every session. Once I've selected an interpreter, I don't get it any more. However, if I do select "Developer: Reload Window" then I do get the prompt again.

> * Do you have a workspace folder opened?

No

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

User belongs to experiment group 'ShowPlayIcon - start'
User belongs to experiment group 'DebugAdapterFactory - experiment'
User belongs to experiment group 'PtvsdWheels37 - experiment'
User belongs to experiment group 'UseTerminalToGetActivatedEnvVars - control'
User belongs to experiment group 'LocalZMQKernel - experiment'
User belongs to experiment group 'CollectLSRequestTiming - control'
User belongs to experiment group 'CollectNodeLSRequestTiming - experiment'
User belongs to experiment group 'EnableIPyWidgets - experiment'
User belongs to experiment group 'DeprecatePythonPath - experiment'
User belongs to experiment group 'RunByLine - control'
User belongs to experiment group 'CustomEditorSupport - control'
User belongs to experiment group 'pythonaacf'
> conda --version
> pyenv root
> python3.7 ~/.vscode-server/extensions/ms-python.python-2020.9.0/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3.6 ~/.vscode-server/extensions/ms-python.python-2020.9.0/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3 ~/.vscode-server/extensions/ms-python.python-2020.9.0/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python2 ~/.vscode-server/extensions/ms-python.python-2020.9.0/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python ~/.vscode-server/extensions/ms-python.python-2020.9.0/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python ~/.vscode-server/extensions/ms-python.python-2020.9.0/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> ~/miniconda2/bin/conda info --json
> python ~/.vscode-server/extensions/ms-python.python-2020.9.0/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python ~/.vscode-server/extensions/ms-python.python-2020.9.0/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
Error 2020-09-25 23:48:07: Failed to check if file needs to be fixed [EntryNotFound (FileSystemError): Unable to read file 'vscode-remote://wsl+ubuntu/home/dcieslak/.config/Code/User/settings.json' (EntryNotFound (FileSystemError): Error: ENOENT: no such file or directory, open '/home/dcieslak/.config/Code/User/settings.json')
    at _handleError (/home/dcieslak/.vscode-server/bin/e5e9e69aed6e1984f7499b7af85b3d05f9a6883a/out/vs/server/remoteExtensionHostProcess.js:730:74)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
    at async y.readText (/home/dcieslak/.vscode-server/extensions/ms-python.python-2020.9.0/out/client/extension.js:1:498797)
    at async p.doesFileNeedToBeFixed (/home/dcieslak/.vscode-server/extensions/ms-python.python-2020.9.0/out/client/extension.js:56:961676)
    at async /home/dcieslak/.vscode-server/extensions/ms-python.python-2020.9.0/out/client/extension.js:56:960803
    at async Promise.all (index 0)
    at async p.getFilesToBeFixed (/home/dcieslak/.vscode-server/extensions/ms-python.python-2020.9.0/out/client/extension.js:56:960749)
    at async p.updateTestSettings (/home/dcieslak/.vscode-server/extensions/ms-python.python-2020.9.0/out/client/extension.js:56:960376)] {
  code: 'FileNotFound',
  name: 'EntryNotFound (FileSystemError)'
}
> ~/miniconda2/bin/conda env list
> ~/miniconda2/bin/conda env list
Error 2020-09-25 23:48:07: Jupyter Kernel Spec not found for a local connection
Error 2020-09-25 23:48:07: Failed to determine if a notebook is active for the current editor Failed to find a kernelspec to use for ipykernel launch
Error 2020-09-25 23:48:07: Failed to initialize S Failed to find a kernelspec to use for ipykernel launch
Error 2020-09-25 23:48:07: DataScience Error Failed to find a kernelspec to use for ipykernel launch
Error 2020-09-25 23:48:07: Failed to initialize ipywidgetHandler Failed to find a kernelspec to use for ipykernel launch
Starting Jedi Python language engine.
Error 2020-09-25 23:48:07: Diagnostic Code: InvalidPythonInterpreterDiagnostic, Message: No Python interpreter is selected. You need to select a Python interpreter to enable features such as IntelliSense, linting, and debugging.
Diagnostic Code: InvalidPythonInterpreterDiagnostic, Message: No Python interpreter is selected. You need to select a Python interpreter to enable features such as IntelliSense, linting, and debugging.
> ~/miniconda2/envs/py3/bin/python ~/.vscode-server/extensions/ms-python.python-2020.9.0/pythonFiles/pyvsc-run-isolated.py -c "import jupyter"
> ~/miniconda2/envs/py3/bin/python ~/.vscode-server/extensions/ms-python.python-2020.9.0/pythonFiles/pyvsc-run-isolated.py -c "import notebook"
Error 2020-09-25 23:48:09: Jupyter Kernel Spec not found for a local connection
Error 2020-09-25 23:48:09: DataScience Error Failed to find a kernelspec to use for ipykernel launch
> ~/miniconda2/envs/py3/bin/python ~/.vscode-server/extensions/ms-python.python-2020.9.0/pythonFiles/pyvsc-run-isolated.py pip --version
Error 2020-09-25 23:48:37: Jupyter Kernel Spec not found for a local connection
Error 2020-09-25 23:48:37: DataScience Error Failed to find a kernelspec to use for ipykernel launch
Error 2020-09-25 23:48:47: Jupyter Kernel Spec not found for a local connection
Error 2020-09-25 23:48:47: DataScience Error Failed to find a kernelspec to use for ipykernel launch
> ~/miniconda2/envs/py3/bin/python ~/.vscode-server/extensions/ms-python.python-2020.9.0/pythonFiles/pyvsc-run-isolated.py pip --version
Error 2020-09-25 23:50:16: Jupyter Kernel Spec not found for a local connection
Error 2020-09-25 23:50:16: DataScience Error Failed to find a kernelspec to use for ipykernel launch
Error 2020-09-25 23:50:23: Jupyter Kernel Spec not found for a local connection
Error 2020-09-25 23:50:23: DataScience Error Failed to find a kernelspec to use for ipykernel launch
Error 2020-09-25 23:50:31: Jupyter Kernel Spec not found for a local connection
Error 2020-09-25 23:50:31: DataScience Error Failed to find a kernelspec to use for ipykernel launch
Error 2020-09-25 23:50:45: Jupyter Kernel Spec not found for a local connection
Error 2020-09-25 23:50:45: DataScience Error Failed to find a kernelspec to use for ipykernel launch
Error 2020-09-25 23:51:09: Jupyter Kernel Spec not found for a local connection
Error 2020-09-25 23:51:09: DataScience Error Failed to find a kernelspec to use for ipykernel launch

Originally filed here https://github.com/microsoft/vscode-python/issues/13809#issuecomment-700237298
@davidcieslak Please could you fill in the details of the issue:

OS, Python extension version, vscode version

@davidcieslak
Please could you fill in the requested information (OS, Python Extnsion Version, VS Code Version)
As a temporary solution please could you add the following into your user settings.json file:
	"python.experiments.optOutFrom": [
		"DeprecatePythonPath - experiment"
	],

Info:

Edition	Windows 10 Pro Insider Preview
Version	2004
Installed on	8/28/2020
OS build	20201.1000
Experience	Windows Feature Experience Pack 120.21600.0.0

executing Ubuntu 20.04 through WSL.
Python Extensoin Version: 2020.09.111407
VS Code:

Version: 1.49.2 (user setup)
Commit: e5e9e69aed6e1984f7499b7af85b3d05f9a6883a
Date: 2020-09-24T16:29:41.983Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.20201

I reviewed much of the documentation and ended up determining that I need to open VS Code using the statement code . and not code. This seems to correctly utilize the WSL2 based libraries. Thanks for your support.


Error loading asn1js/org/pkijs/common

Getting an error using common: var common = require('asn1js/org/pkijs/common');:
.../node_modules/asn1js/org/pkijs/common.js:66
    var CalculatorMixin = Base => class extends Base
                                  ^^^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode

It looks like some junk code snuck into a commit.

Sorry, was added by accedent. Fixed.


training and inference

@hlei-ziyan thanks for open sourcing the wonderfull work , i had few queries
Q1 have you trained the architecture on the available other dataset like semanttic Kitti and 3D dataset
Q2 If not trained can we follow the same training pipeline , if trained can you please share the pre-trained model
Q3 can we use the currently pre-trained model to test on custom dataset which less number of point cloud density
Thanks in advance

A1: Not yet.
A2: Yes, the new tensorflow modules we introduce is applicable to any point cloud dataset. You just need to prepare your data (block pre-splitting or random block sampling on the fly is the current convention). The training/evaluation will be rather similar to those of S3DIS and ScanNet.
A3: About applying pre-trained models to test with less or more number of point cloud density, short answer is that testing pre-trained model on more points is fine, but the performance drops quickly for less points. Our cvpr2020 paper (should be available after this March) studied this detailedly. If you are interested in using trained-model across different number of points, the fuzzy kernel proposed in the cvpr2020 paper suits your purpose (code now partially available in my github repository 'SegGCN').


Possible factors for constructing synthetic I-V curves

In no particular order, here are some options for synthetic curves:

I-V curves with points equally spaced in voltage vs. points "bunched" up around Isc and Voc or around Pmp.
I-V curves with roughly equal noise in I and V, vs. more noise in I than V (or vice versa). Greater noise in I can occur from solar simulators that "flicker" during the measurement. (This intensity variability is often corrected along with the spectral correction, and such corrections may introduce bias.)
Curves that try to show how a fitting algorithm handles model error, such as fitting a single-diode model to a double-diode model physics. This can be done "cleanly" or with the additional complication of measurement noise.
Single curves vs. IEC 61853-1 sets of curves.

I note that "raw" I-V curves from calibration labs (e.g., using solar simulators) can have different irradiance levels for every point on the I-V curve. (Less often have I seen temperature measurements for each I-V point, but rather pre- and post- temperature measurements to give some idea of heating during the measurement.) These raw curves are often corrected to a single temperature and irradiance, with the likely introduction of some level of correction bias.

This is flexing my memory banks from uncertainty analyses I did at NREL, but I recall a few broad options to consider:
(1) Additive noise
(2) Multiplicative noise
(3) Bias
Additive noise, typically normal and independent and identically distributed (i.i.d.), usually matches the statistical assumptions behind many standard (linear) regression methods (although we generally have a non-linear, error-in-variables model here). For example, "such and such" a method produces the maximum likelihood estimator (MLE) on linear problems under certain noise assumptions.
Multiplicative noise, IIRC, seemed to better match the physics of the voltage measurements that underlie the voltage AND current measurements in I-V curves. The relative magnitude of the noise is constant, but the absolute magnitude of the noise grows with the signal size. Note that these voltage measurements may have bias and noise correlation, say due to temperature fluctuations between I-V curve measurements. It is usually hard to quantify this based solely on manufacturer's specifications, but is often assumed small and/or ignored.
For the current measurement, the conversion from voltage to current (e.g., via a current shunt resistor) adds more uncertainty, which may add more bias than random noise (e.g., an imperfectly known resistance biases all conversions in I = V/R). Furthermore, any spectral- and/or light-level correction in the current also add bias (e.g., from, the spectral-correction using the imperfect factor M) and random noise (e.g., from the flickering of a continuous solar simulator), which is why the "noise" is often larger in the current channel.
I have typically used multiplicative i.i.d. normal noise without bias in my SDM calibration work. After picking a noise model, I would suggest doing all combinations of zero, low, and high noise levels in the I and V channels (via the variance parameter in the normal distribution), e.g., 0, 0.01, and 0.025. (Maybe leave out the highest noise level for voltage?)
I am happy to provide some further implementation examples/details in Python code.


add NIO event loop as an argument for execute

Addresses #78

@weissi what do you think we need to test? that we use event loop we pass in?

@weissi what do you think we need to test? that we use event loop we pass in?

Two things:

that it uses the correct event loop
every API should at least be used by a test case so that there's at least one caller

@ldewailly done

I think in its current state, in case of redirect the provided EventLoop will be ignored.
In general, is this API really a good idea?
I'm thinking about the future connection pooling. What happens if the pooled connection lives on a different event loop? Should the client then not use this connection and create a new one? Or hop to the event loop of the connection and hop back only in the end? What should happen during the delegate callbacks? On which loop will those be executed?
My understanding was: If you want to tightly control on which event loop the client executes, then initialize it witch a single event loop instead of a event loop group. WDYT?

I'm thinking about the future connection pooling. What happens if the pooled connection lives on a different event loop?

The pool could be keyed on the event loop too but that would as you point out mean that we possibly create more connections than necessary to avoid hopping.

My understanding was: If you want to tightly control on which event loop the client executes, then initialize it witch a single event loop instead of a event loop group. WDYT?

Good point. That is achievable today through HTTPClient(eventLoopGroupProvider: .shared(myEventLoop)).execute(...) (because every EventLoop is also an EventLoopGroup where .next() always returns itself)
I think I'm with @t089 and am unsure if we really need this API or if we should just use a new HTTPClient with the EL as the ELG if you want to pin the client to a certain EL. Said that, that also isn't great regarding connection pools because that new HTTPClient would then likely have a new connection pool which gets us back to the initial issue that we might create too many connections... @Lukasa thoughts?

I'm a bit inclined to want to say that the Client should hide this from users.
Creating new clients per event loop seems like an excessive construction. Why not use the event loop as part of the connection key? Users that don't pass an event loop to execute are expressing that they don't care (that is, nil matches everything), but users that do are requesting a pooled connection on a specific loop. If there isn't one, we just manufacture a new connection for them.
This is strictly no less efficient than creating new clients for every loop.

Creating new clients per event loop seems like an excessive construction. Why not use the event loop as part of the connection key? Users that don't pass an event loop to execute are expressing that they don't care (that is, nil matches everything), but users that do are requesting a pooled connection on a specific loop. If there isn't one, we just manufacture a new connection for them.

This sound doable, although I wonder: if we manufacture a new connection for the explicitly requested event loop, should this connection then also become part of the connection pool? Because in that case, the pool would possibly contain connections that live on event loops that are completely out of the control of the Client. Not sure if this would cause a problem?!

Yeah, the connection should be part of the pool. Not sure what you mean by an event loop "out of control of the client" though: can you clarify?

Yeah, the connection should be part of the pool. Not sure what you mean by an event loop "out of control of the client" though: can you clarify?

Yeah, maybe that is also a non-issue. But I was thinking of this scenario:

Let's say you create the client with eventLoopGroupProvider: .createNew.
You fire a request with an EventLoop-#8 from another MTELG.
The client will pool the connection with the EventLoop-#8
You shut down the MTELG.
Somebody else fires a request to the same server as above without specifying an event loop.
Would the client now try to use a connection that lives on an event loop that has been shut down?

Yeah, good call, I think the client should confirm that the event loop for the connection is within its event loop group.

Yeah, good call, I think the client should confirm that the event loop for the connection is within its event loop group.

So, should connections on "external" event loops become part of the pool or not?

The client should refuse to make them, to avoid the question being relevant. 😁

Ahhhh ok, I totally missed that use case: You created the client with a MTELG and you want to make sure that a subsequent request is executed on a specific EL of this ELG. Yeah, that's a very good use case. 👍

is there a way to test if EL is part of our ELG?

Yes, ELGs expose a property that shows you the loops in them.

For the case of a connection pool, I wonder what's the cost of hopping to a different event loop (even repeatedly) versus generating a completely new connection to match the event loop requirement, isn't the former typically much less expensive than the latter since network IO is orders of magnitude slower than memory? In this case, wouldn't it have the risk of causing worse performance when the user actually thinks they are doing an optimisation?
Maybe we could do the following with the eventLoop argument:

It guarantees the futures returned by the client are all hopped to eventLoop.
It is used as a hint for the client / connection pool: if a new connection needs to be created, it will use eventLoop, otherwise, an existing connection will be used no matter its event loop.

What do you think?

In general, yes, for a simple request you probably gain nothing by establishing a new TCP connection on your loop instead of reusing one on a different loop.
However, if you are streaming a very large request or response body, you will need to incur way more coordination overhead, and in those cases it is often worth trying to line up the loops.
I think your idea is good, but we should consider extending the API to allow users who know they want it to demand a connection on a specific loop.

@weissi added a test
@Lukasa > I think your idea is good, but we should consider extending the API to allow users who know they want it to demand a connection on a specific loop.
But still from the clients ELG, right?

@Lukasa  I see, so a finer grained control?
Why not something such as:
enum EventLoopPreference {
    case indifferent
    case prefers(EventLoop)
    case requires(EventLoop)
}

.indifferent is the same as nil in the current PR.
.prefers(EventLoop) guarantees futures callbacks are executed on EventLoop by hopping them, but imposes no further requirement on connection providers implementations, the goal is to enable them to make the right optimizations without over constraining them.
requires(EventLoop) guarantees futures callbacks are executed on EventLoop by ensuring everything is executed on EventLoop.

.prefers(...) would be destined to cases where the user knows using a specific event loop can offer performance benefits, but also knows that forcing the creation of a new connection would probably outweigh the performance gains. On the other hand, requires(...) forces the creation of new connections, better suited for cases such as the long lived streaming @Lukasa describes.
The current implementation would likely treat .prefers(...) and .requires(...) the exact same way, because it creates a new connection each time, but I'm interested to see this already integrated into the API as I'm not sure of how this could be integrated after the 1.0.0 release without being a breaking change?

@adtrevor This might be the right idea. I'm just a little worried that right now we're probably not able to express all the things we want to express in the future and the enum is set once we release 1.0.0. What I would probably recommend (is something like):
public struct EventLoopPreferrence {
    private enum Preferrence {
        case .indifferent
        case .prefers(EventLoop)
        /* this is private, we can extend in the future */
    }
    private var preferrence: Preferrence

    public static let indifferent = EventLoopPreferrence(preferrence: .indifferent)
    public static func prefers(_ eventLoop: EventLoop) = EventLoopPreferrence(preferrence: eventLoop)
}

extension EventLoopPreferrence: NilLiteralConvertible {
   /* make `nil` equal to `.indifferent` */
}

if we do this we support the following on day 1: nil (or .indifferent) and .prefers(myEventLoop) and we don't need to implement .requires(...) yet. We can (in a SemVer minor) add any other thing later such as (bad example) .requiresEitherOr(thisEL, thatEL) without breaking the public API.
Obviously if we think .requires is more useful to start with than .prefers, we can also start with that.

Yeah, I think a finer-grained preference control is good. I like that idea, and think if we go with it we should adopt @weissi's suggestion. I also agree with @artemredkin's reminder that we should only allow users to ask for an event loop from the group the client is using.

@weissi Thank you, I already saw this pattern in NIO and I like it.
I also agree starting with .prefers because .requires may cause noticeable performance losses if used incorrectly with a pool IMO.
I'm a little worried about users not realising .prefers still guarantees the futures are already hopped to the loop they specified? Maybe there could be a better name? The docs might also be enough since EventLoopPreferrence is already a quite "advanced" option one shouldn't use without understanding what it precisely does?

@weissi @adtrevor great idea, added preferrence

I also agree with @artemredkin's reminder that we should only allow users to ask for an event loop from the group the client is using.

This part is still missing, isn't it? Should we add a test for it?

@artemredkin Thanks, that's great!

@t089 good catch, thank you! updated the PR

Note, that redirects will ignore the preference parameter, won't they?
https://github.com/swift-server/async-http-client/blob/8fa354df7ccf7139afe4cb9211f17dbcf2c57ed8/Sources/AsyncHTTPClient/HTTPClient.swift#L218

Also in the current implementation .prefers(EventLoop) does what @adtrevor described as .requires(EventLoop): It creates a connection on the requested EventLoop. So shouldn't this be called .requires(EventLoop), then?

@t089 The issue if we use .requires(...) is that when the lib evolves to include pooling, there might be big performance losses for people who still have .requires(...) option set. That's because it imposes big constraints causing the spin of sometimes useless new connections.

Ah got it, thanks!

Note, that redirects will ignore the preference parameter, won't they?
https://github.com/swift-server/async-http-client/blob/8fa354df7ccf7139afe4cb9211f17dbcf2c57ed8/Sources/AsyncHTTPClient/HTTPClient.swift#L218

Indeed looks like this part is missing?

@t089

Note, that redirects will ignore the preference parameter, won't they?
https://github.com/swift-server/async-http-client/blob/8fa354df7ccf7139afe4cb9211f17dbcf2c57ed8/Sources/AsyncHTTPClient/HTTPClient.swift#L218

Indeed looks like this part is missing?

Sorry, I merged because I didn't see this: Created issue https://github.com/swift-server/async-http-client/issues/88


Additional date formats?

I use a MMMM D, YYYY format for my daily notes "December 23, 2020" for example. Is there a way I can change the date format for the daily note to reflect that format?

I've updated the workflow but haven't released it yet. You can try it out by downloading from it here (from another branch). Let me know if it works for you.

Works perfectly. Thanks!


OSBA Cosmos Class Missing

In the OSBA lab using Cosmos it's using the class azure-cosmos-mongo-db. Doesn't look like that class exists any longer as running apply results in
Error from server (Forbidden): error when creating "heroes-cosmosdb.yaml": serviceinstances.servicecatalog.k8s.io "heroes-cosmosdb-instance" is forbidden: ClusterServiceClass {ClassExternalName:"azure-cosmos-mongo-db"} does not exist, can not figure out the default ClusterServicePlan.
I ran ./svcat get classes and azure-cosmos-mongo-db wasn't listed.

I faced the same problem today.  I do see the service listed in:
https://github.com/Azure/open-service-broker-azure/blob/master/docs/modules/cosmosdb.md#service-azure-cosmosdb-mongo-account
What might account for this problem? Prior steps in the lab completed successfully.

The service class was renamed to azure-cosmosdb-mongo-account but we did update the yaml accordingly. Can you paste the new error message you are seeing?

The error we had today is:
Error from server (Forbidden): error when creating "heroes-cosmosdb.yaml": serviceinstances.servicecatalog.k8s.io "heroes-cosmosdb-instance" is forbidden: ClusterServiceClass {ClassExternalName:"azure-cosmosdb-mongo-account"} does not exist, can not figure out the default ClusterServicePlan.
So, same error with the renamed service class.

Into Azure Shell, the command was copied verbatim from the lab instructions. We'll be mindful of this when testing again. Thanks.

I have sucessfully completed the OSBA lab as per instruction mentioned, only change I made from above comments is service class name azure-cosmosdb-mongo-account .

I have verified that I am able to complete the OSBA lab as per the current instructions.

FYI @chzbrgr71 or @jschluchter , this issue could be now closed since PR #108 has been merged into master.


"Error _BAD_MSG - Local: Bad message format" with sample producer code

Running kafka_2.11-<IP_ADDRESS> on my local machine (mac). Connection is coming from a windows VM.
My Code:
class Program
{
    private string _hostIp = "<IP_ADDRESS>";

    private async void WriteToQueue(string message)
    {
        using (Producer producer = new Producer(_hostIp + ":9092"))
        using (Topic topic = producer.Topic("test"))
        {
            byte[] data = Encoding.UTF8.GetBytes(message);
            DeliveryReport deliveryReport = await topic.Produce(data);
            Console.WriteLine($"Produced to Partition: {deliveryReport.Partition}, Offset: {deliveryReport.Offset}");
        }
    }

    static void Main(string[] args)
    {
        var program = new Program();
        program.WriteToQueue("Hello");
        Thread.Sleep(2000);
    }
}

My mistake. My environment was not clean and a full restart resolved the issue. Apologies.


Go v2 is not available

The v2 is currently not listed on pkg.go.dev
From reading the documentation, it looks like we'd need to keep a branch in sync for that new version
But I have no experience publishing a new major version for go libraries, so I believe we should discuss this before taking any action.

Ouch, cc. @lburgazzoli you might know on top of your head how to fix this ...

I just released 2.0.1 to fix the problem but hit another issue:
https://github.com/std-uritemplate/std-uritemplate/actions/runs/11799703853/job/32868849752#step:4:19
the good part is that we can manually finish the Go release at any point.
I'm not sure what's wrong this time, as the command works for me locally, @baywet would you find a Go expert to help out here?
We need:

any fix required to release pipeline / docs / etc.
the manual commands to release a proper 2.0.1

@jhendrixMSFT might be able to help.

A version won't show up on pkg.go.dev until you (or somebody) go get it. This is documented here.
Also, it's best practice to have the v prefix in your version tags. See https://go.dev/doc/modules/version-numbers for more info.

@jhendrixMSFT thanks a lot for chipping in!
This step in CI is tagging the repository for Go releases:
https://github.com/std-uritemplate/std-uritemplate/blob/ded7c2d083f759c75ff74a8adf83c07eaab9ca17/.github/workflows/release.yml#L103-L104
Unfortunately, this failed during the last release and I'm not sure how to fix it.
Can you, please, review the go.mod files in the go subfolder?
We are already releasing from a subfolder, is this compatible with the release of v2 in a sub-sub-folder?
Should I run manually:
git tag "v2.0.1"
git tag "go/v2.0.1"

to fix the failed release?
In this case, will go mod tidy works next time?
:pray: thanks!

I've not personally tried the major version subdirectory approach for major versions, only branches. What you have looks correct though based on the docs.
I believe that for major versions 2+ the v prefix on the tag is a requirement.
As for the tag itself, I believe it should just be v2.x.y. You only need to add a qualifying path when your repo contains multiple modules that independently version. We do that in the azure-sdk-for-go repo, see some examples.


Improve and fix documentation

Move the service documentation to the service block (workaround for #525)
Use markdown formatting
Use syntax highlight for examples in docs
Add link to the RFC

Updated. I'm not sure what's the current status of this intro doc in other API, because I did this a long time ago and maybe things changed.

@stefan-brus-frequenz maybe you want to approve this too as you are more up to date to how API repos should be?

@stefan-brus-frequenz ping


WIP initial configuration PoC

PoC to try different options to pass initial configuraiton but at the same be ready to handle node agent
Idea:
configs will be mapped to configmaps readable by node-agent in future but currently to be used as fallback config for cri-resmgr statically.
configs can be provided as providerConfig in shoot exension section for specifc shoot or even on "ControllerDeployment" level to override the default that is specified in exentions chart values.yaml (not yet implemented).
configs should be reconciled online but there is no mechanism to restart cri-rm without node-agent - to apply new policy for example - maybe we can call "systemctl restart cri-resource-manager" but how to detected change in policy ?!?!?
Also:

replace uninstall script with a trap
removed unused flags (leader election) and fixed ignore annotation.

Temporaray removed healthcheck.
TODO:

[ ] valiadate uninstallation as trap
[ ] implement "controllerdeployement" chart values be used as default for values in extensions when rendering installation chart
[ ] node-agent used instead of sleep (a lot of work, require CRDs)

superseded by #33


Allow enabling troubleshooting stacktraces on TeamCity

Rationale
We encounter occasional memory leaks on TeamCity. Being able to quickly enable stacktraces would be useful for debugging such failures.
Related Pull Requests

https://github.com/LabKey/testAutomation/pull/493

Changes

New action to enable troubleshooting stacktraces via API

This seems OK, but is a separate approach from what's proposed in https://www.labkey.org/home/Developer/issues/issues-details.view?issueId=41534
I guess this may be slightly better because the stack traces aren't really an "experimental" feature.

This approach is fine with me


ciao-cli: Support specifying CA file in environment or command line

With this change the CA certificate file used for communicating with
keystone and the controller can be specified:
a.) either on the command line with -ca-file,
b.) or with an envionment variable, CIAO_CA_CERT_FILE,
thus avoiding the need to import the certificate into you local store.
This change required switching from openstack.AuthenticatedClient() to
the lower level API in order to override the transport options on the
HTTP client.
Fixes #180
Signed-off-by: Rob Bradford<EMAIL_ADDRESS>

Coverage increased (+0.02%) to 66.413% when pulling c03fd1d09f90520898f7e7814d17035ebac3001c on rbradford:cli-ca-file into 4e2cb0c1924ae08064e55d91e859ebf8874ebddb on 01org:master.

Coverage increased (+0.02%) to 66.413% when pulling c03fd1d09f90520898f7e7814d17035ebac3001c on rbradford:cli-ca-file into 4e2cb0c1924ae08064e55d91e859ebf8874ebddb on 01org:master.

Coverage increased (+0.02%) to 66.413% when pulling 9f03f5e22e78c70dddd30f485a0202530471cf51 on rbradford:cli-ca-file into 4e2cb0c1924ae08064e55d91e859ebf8874ebddb on 01org:master.

Coverage remained the same at 66.395% when pulling 9f03f5e22e78c70dddd30f485a0202530471cf51 on rbradford:cli-ca-file into 4e2cb0c1924ae08064e55d91e859ebf8874ebddb on 01org:master.

This change looks good to me.


consider defining a common subset of widget names

can we have ip-v4 and ip-v6 instead of just ip?
I agree we should drop timer


Update with Transparent UTF-8 support

There's a mostly drop-in windows.h replacement (made by another user) which adds transparent UTF-8 support to ANSI Win32 programs, but as awesome as it is, it currently conflicts with WindowsHModular. Here is the repository in question, for review:

https://github.com/thpatch/win32_utf8

There is also a related repository, which adds dynamic layout functionality for Win32 dialogues, but it is dependent on Win32_utf8:

https://github.com/thpatch/win32_smartdlg

By the way, Microsoft has recently taken notice of both WindowsHModular and Win32_utf8, and they are both currently being reviewed for implementation in WinFile:

https://github.com/microsoft/winfile

Yes, what am I supposed to do about it? win23_utf8 does something completely different. Of course it's going to conflict.

What I meant was to... Like, maybe... Combine it? Add transparent UTF-8 support to the modular thing here?

It's not a goal of this library. However, the idea isn't particularly bad. It would have to be added to win32_utf8, though.


Update cost function parameters

Passed dual variable in condat-vu algorithm to cost function.
Fixed bug in matrix.py docstrings.

Coverage remained the same at 17.463% when pulling ef8385859af056dde1fe4e3d194d4cb24ccabf56 on sfarrens:dual_variable into 842f6d726dc8b211f783e2e5b85786067e31fb02 on CosmoStat:master.


Fix Python wrapper returns SwigPyObject instead of CPACSWalls (Issue #1012)

CCPACSWalls couldn't be processed correctly via swig, due to missing include statements in configuration.i.
Adding those includes fixes the issue.
Description

All required includes in configuration.i were added, which are:

The header files of the C++ classes that need to be included
all header files of classes, that deal with types of "boost-optional" or objects related to "ITiglGeometricComponent" that swig can't process otherwise

The changes fixes #1012 and fixes #986.
How Has This Been Tested?

Running a python script opening the configuration according to Issue  #1012 works as expected, also the geometry is exported successful.

There are some unresolved symbols: https://github.com/DLR-SC/tigl/actions/runs/12032196292/job/33543463973#step:3:7317


Wrong encrypted token generation

I'm using :

Ruby 2.2
Rails 4.2
Devise 3.5.1
Devise_invitable 1.5.2 (same issue with 1.3.5)

Use case
An admin user is sending invitation to an agency user.
I'm using a custom view to display the email with this link:
accept_invitation_url(@resource, invitation_token: @token)
Issue
When I click on email link, I have the error: The invitation token provided is not valid!
I tested in Rails console some things:
Token from the email: 3Drz1qJg8PCn5v2oeC7XuU
AgencyUser.find_by_invitation_token("3Drz1qJg8PCn5v2oeC7XuU", false)
=> #<AgencyUser id: nil, agency_id: nil, first_name: nil, last_name: nil, email: "", encrypted_password: "", reset_password_token: nil, reset_password_sent_at: nil, remember_created_at: nil, sign_in_count: 0, current_sign_in_at: nil, last_sign_in_at: nil, current_sign_in_ip: nil, last_sign_in_ip: nil, created_at: nil, updated_at: nil, invitation_token: "bdd8cec81b8094efb66406e22243d9977de698ee3c935580b0...", invitation_created_at: nil, invitation_sent_at: nil, invitation_accepted_at: nil, invitation_limit: nil, invited_by_id: nil, invited_by_type: nil>
Devise.token_generator.digest(AgencyUser, :invitation_token, "3Drz1qJg8PCn5v2oeC7XuU")
=> "bdd8cec81b8094efb66406e22243d9977de698ee3c935580b04cfcb9ea2a2a9d"
AgencyUser.all
=> #<ActiveRecord::Relation [#<AgencyUser id: 1, agency_id: 1, first_name: "Lorem", last_name: "Ipsum", email<EMAIL_ADDRESS>encrypted_password: "$2a$10$Wb7SkdfEV.CVT2Jh/mDcM.vD6aL.CpqDg3BXno23O/Y...", reset_password_token: nil, reset_password_sent_at: nil, remember_created_at: nil, sign_in_count: 0, current_sign_in_at: nil, last_sign_in_at: nil, current_sign_in_ip: nil, last_sign_in_ip: nil, created_at: "2015-07-24 08:38:57", updated_at: "2015-07-24 08:38:57", invitation_token: "c6f096c81c74c15480f71c4972245bf58fedfb1714fba398af...", invitation_created_at: "2015-07-24 08:38:57", invitation_sent_at: "2015-07-24 08:38:57", invitation_accepted_at: nil, invitation_limit: nil, invited_by_id: nil, invited_by_type: nil>]>
tl;dr
token in db: c6f096c81c74c15480f71c4972245bf58fedfb1714fba398af6b5e447cccddb7
token check generated: bdd8cec81b8094efb66406e22243d9977de698ee3c935580b04cfcb9ea2a2a9d
It looks like the token is not generate in the same way when the AgencyUser is created.

Can you send insert agency user sql?

New test
Token from email: 3DWb9QdUhwjhqqT7aKGJ4s
Token check generated: 74a337e2309ef5e7566ec4251f1947b8018875d106ee1f5490dd2835da7fad8b
Token in db: 063a01cedfb4a13b15f5d9339191b93bd1df165b3f3dd4114009e1e266342b91
INSERT INTO "agency_users" ("email", "first_name", "last_name", "agency_id", "encrypted_password", "invitation_token", "invitation_created_at", "invitation_sent_at", "created_at", "updated_at")
VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10)
RETURNING "id"  [
    ["email"<EMAIL_ADDRESS>
    ["first_name", "John"],
    ["last_name", "Doe"],
    ["agency_id", 1],
    ["encrypted_password", "$2a$10$n7iZJXKS047ryehfVL67hOiYo2ISIDRVEAuX4Zuq56Yhj3xQu81xa"],
    ["invitation_token", "063a01cedfb4a13b15f5d9339191b93bd1df165b3f3dd4114009e1e266342b91"],
    ["invitation_created_at", "2015-07-30 06:27:27.830700"],
    ["invitation_sent_at", "2015-07-30 06:27:27.830700"],
    ["created_at", "2015-07-30 06:27:27.832301"],
    ["updated_at", "2015-07-30 06:27:27.832301"]
]

Is it happenning with other devise tokens, like confirmation token?
Also you can test token generator in console:
raw, enc = Devise.token_generator.generate(AgencyUser, :invitation_token)
puts raw
puts enc
digest = Devise.token_generator.digest(AgencyUser, :invitation_token, raw)
puts digest
enc == digest

I've found my issue, it's due to quoted-printable encoding in the emails. The characters 3D was added after the equal sign (just before the token).
However, it does work with the reset_password_token. The Devise Mailer send the email with this encoding:
Mime-Version: 1.0
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

And the Devise Invitable Mailer send the email with this encoding:
Mime-Version: 1.0
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

How can I set the same Content-Transfer-Encoding to 7-bit for Devise Mailer and Devise Invitable Mailer ?

I don't know, ActionMailer probably is setting different encoding depending on content. DeviseInvitable uses Devise mailer, only adds a method to send new mail with own views. However enconding should not be an issue, it's an html email, so if you view as HTML, you shouldn't view these 3D encoding characters (most probably =3D)

A year and a half later, thank you @Chambeur, for the 3D characters, you saved my day !


Swift4 update and fix compiler warnings

Por flavor? We want to keep using this library but the compiler warnings make crazy. No beer no tv make homer something something.

Can you share more info about these warnings? I updated the Swift demo project to the latest Swift compiler and don't see any important warning


"Golang" interval syntax is not actually compatible with Go durations

Exalate commented:
Billing the 1m2s3ms format as "Golang" compatible isn't precisely correct. It works for simple intervals, like the example given, but not for more complicated intervals. E.g., 39mon is a valid Cockroach/Postgres interval, but not a valid Go duration. Similarly for negative intervals: -5m-5s is a valid Cockroach/Postgres interval, but not a valid Go duration.

Thanks for reporting, @benesch!

We have closed this issue because it is more than 3 years
old. If this issue is still relevant, please add a comment and re-open
the issue. Thank you for your contribution to CockroachDB docs!


Add 'Required' tag to IpFIlterRule fields

Add 'Required' tag to IpFIlterRule fields

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

It looks like you're working at Microsoft (ravokkar). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

 https://github.com/Azure/azure-sdk-for-python/pull/791

 https://github.com/Azure/azure-sdk-for-node/pull/1890

 https://github.com/Azure/azure-sdk-for-ruby/pull/466


Misc fixes

Merging this PR will publish the following release:
7.0.2 (2020-04-05)
Bug Fixes

each plugin's options weren't being passed (ec77e03), closes #83
show library name in semantic-release debug output (77c25d2), closes #86

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Tokens come back on visited tiles with smooth movement

Tokens come back on visited tiles with smooth movement. I've spotted an issue with the array that stores the visited locations. The first stored coordinates are fine but the second are not aligned with the grid anymore. Example :
1500, 1500
1570, 1500
1501.30548, 1500
It's as if the new location was calculated when the movement is not finished yet. And indeed, tokens are not aligned anymore with the grid on the map !
I've seen another issue and I don't know if it's related to this one but it might be.  With smooth movement activated, lights don't move with the moving token  (ex torch).

pushed a fix to fixup the position if they are off grid, it should adjust the positions correctly and fix th issue

The issue is fixed : tokens now snap to the grid and light is moving with tokens. But there is a new issue.  And anyway, it works fine when I don't use smotth movement. Do you want to connect to my game to se how it behaves ?

I mean token can't move through "Patrol" areas but they can move through walls (like standard walls).

https://user-images.githubusercontent.com/87486705/126215132-532033cc-b2ee-4209-b63a-5f0d39c041a0.mp4
https://user-images.githubusercontent.com/87486705/126215137-c2c59324-ce9b-4e7a-930f-1879a905c8d5.mp4

https://user-images.githubusercontent.com/87486705/126215265-e3a6f562-28ed-40bc-97d2-1bde3050febd.mp4
https://user-images.githubusercontent.com/87486705/126215267-efff5d26-834d-441a-885a-f8f98fe6023d.mp4

https://user-images.githubusercontent.com/87486705/126215371-30ca645c-5f3e-423c-9685-703ff0b69a64.mp4
https://user-images.githubusercontent.com/87486705/126215374-9e78f24b-d0b2-46f6-9be4-a229790a5133.mp4

try with the new update

Yesss ! Tokens are now snapped to the grid. They don't cross walls. Light is moving when they move. The only remaining issue is when they start a new cycle (ie. they don't have any valid position left to visit and the history is cleared to make sure they can move again). On their first first move on a new cycle, tokens sometimes come back on their starting position (see first video). Something must go wrong with the first position.

By the way, I wanted to tell you that you did a very good job ! Your module is awesome ! Thanks for your help and your dedication !

should be fixed


Bump to version 0.9.1. (Just moves toolkit forward.)

It is not urgent, and I am updating the hash to get that in. :-)

Can we try and get this update into this release as well?
https://github.com/googleapis/protoc-docs-plugin/pull/6

Yeah, I can do that.


HARVESTER: fix project-namespace display

Summary
The cluster type remains the same as before, we will remove rancher-mamage-support from the setting, and the back end will create an external rancher through addon to import the harvester cluster.
PR Checklist
~- Is this a multi-tenancy feature/bug?
- [ ] Yes, the relevant RBAC changes are at:~
~- Do we need to backport changes to the old Rancher UI, such as RKE1?
- [ ] Yes, the relevant PR is at:~
~- Are backend engineers aware of UI changes?
- [ ] Yes, the backend owner is:~
Fixes #

Occurred changes and/or fixed issues

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

@mergify backport release-harvester-v1.2


contexts/namespaces via literal prefixes

investigate the possibility of implementing multiple namespaces/contexts within NARS through an optional literal naming convention involving a prefix code.  the presence of a prefix would automatically imply inheritance, product, and/or intensional set relationship between the prefix's concept and its contents.  subspaces can be defined by appending prefixes.
example, if '.' used to indicate contexts:

namespace.item1
namespace.item2
namespace.subnamespace.item

this could be implemented either internally or through a macro pre-processor step

seems like this is  relevaqnt to post-1.7

Something like namespaces can be realized by using products already, no syntax is needed for this.
(*,namespace,item1)
(*,namespace,item2)
(*,namespace,subnamespace,item)
Example:
<(*,(*,namespace,item1),{2}) --> value>.
<(*,(*,namespace,item2),{3}) --> value>.
<(*,(*,namespace,subnamespace,item),{3}) --> value>.


Update the game over message

Update the game over message so people know how to play again!

Looking good


Implemented FT_78, 82

Implemented test cases FT_78 and FT_82

Can one of the admins verify this patch?

ok to test

lgtm

@AnkitGaurNms, please merge master (& fix conflicts, if any) rebuild & check is passes and then push again. Thanks!

Merged branch 'master' into this branch.


Crash on startup with Unlimited Chisel Works

Hello! I am working on a modpack update and Roots is included in the new version. I deleted all the config files for all my mods to allow them to regenerate, and when starting the game up in order to do this, received this crash: https://paste.dimdev.org/exeqijoyuz.mccrash
The UCW config did not populate (file was created, but empty), so I'm guessing the error occurred around that time.
I then temporarily disabled Roots, and loaded up the game to get the UCW config populated so I could exempt Mossy Cobblestone from its list. However, apparently, vanilla blocks cannot be blacklisted via the config. I then tried restarting the game with the config generated, just in case it worked. It did not.
Minecraft version: 1.12.2
Forge version: forge-1.12.2-<IP_ADDRESS>38-universal
Roots: Roots-1.12.2-3.0.13
UCW: UnlimitedChiselWorks-0.2.4
Thanks for your time!

I- uh, oh. Perhaps I was wrong about UCW, as I disabled it and get the same crash: https://paste.dimdev.org/lapitopeni.mccrash
This time, the "suspected mods" include Deep Mob Learning.

Did you try updating MysticalLib to 1.3.7? (https://www.curseforge.com/minecraft/mc-mods/mysticallib/files/2780930)

Boy is there egg on my face. Yep, that fixed it entirely. I'm very sorry for the trouble, thank you for the help!

So, I've been putting in specific required versions for mods but it looks like this is occurring before Forge gets to that point.


parametrize all occurrences of pause image in load config

What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR allows parametrization of the repository used to pull pause images. It actually does two things:

replaces all occurrences of registry.k8s.io/pause:3.9 with latencyPodImage. Right now some of the objects have hard coded image, some are using latencyPodImage. This change unifies it.
allows to specify only registry that will be concatenated with the current version of pause image. This will allow users to either specify whole image via CL2_LATENCY_POD_IMAGE or specify CL2_LATENCY_POD_REGISTRY if they are for example using pull through cache and they do not want to bump image version on their own

Special notes for your reviewer:
This came post https://github.com/kubernetes/kubernetes/issues/126366. This approach allows to inject registry mirror via CL2 env variables. Compared to https://github.com/kubernetes/kubernetes/pull/126448 this will allow to
To start this only changes load config. Other configs will follow.

/assign @mborsz

/lgtm
/approve


Upgrade docs

https://github.com/rancher/k3s/issues/363

curl -sfL https://get.k3s.io | sh -

@galal-hussein It looks like an online upgrade method.
How to upgrade the offline environment (systemd). Are the following steps correct?

Put the k3s in /usr/local/bin
Put the k3s-airgap-images-amd64.tar in /var/lib/rancher/k3s/agent/images/
systemctl restart k3s.service

That is correct @warmchang, but we also provide support for openrc, so restarting for step 3 could be systemctl or restarting from init.d like /etc/init.d/k3s restart. Perhaps it could be updated to something like:

Download air-gap images if desired
Install new k3s binary (from installer or manual download)
Restart k3s (if not restarted automatically by installer)


[Multi-user] Allow private workspaces for sub-users

Allows for users to be able to create their own workspaces and be isolated from one another, basically a public mode!

So the user can create workspaces, chat with them, add/remove documents, but their workspaces not be visible by others - correct?

Yes!

where do i find the multi user mode, i cant find it in settings. i only get single mode by default.

where do i find the multi user mode, i cant find it in settings. i only get single mode by default.

Multi-user mode is only available on the Docker version of AnythingLLM. In the settings menu for this, there's a security tab where you can enable multi-user mode or regular password protection mode.

So the user can create workspaces, chat with them, add/remove documents, but their workspaces not be visible by others - correct?

I am looking for the same. We can also save on resources too. using one main cloud account for multiple new users. (In a public model)


update zeta environment setup file

Hi, Eric. I've updated the document. Sorry for the delay. If there are some mistakes and suggestion, I'll update again.

@HuaqingTu - please remove the change to alcor submodule as it is not needed for this PR.

@HuaqingTu - please remove the change to alcor submodule as it is not needed for this PR.

@HuaqingTu - please see this new wiki page on how to deal with alcor submodule: https://github.com/futurewei-cloud/alcor-control-agent/wiki/Dealing-with-Alcor-Submodule

I'm sorry for missing your message. I can't get into the laboratory now because of the maintenance of the water pipe which will end on Monday. I'll  remove the change to alcor submodul once  I get back to laboratory. And thanks for your new wiki page to guide me how to deal with alcor submodule.

I'm sorry for missing your message. I can't get into the laboratory now because of the maintenance of the water pipe which will end on Monday. I'll remove the change to alcor submodul once I get back to laboratory. And thanks for your new wiki page to guide me how to deal with alcor submodule.

And the remote login I set up before I left the lab is broken down, so I can't submit a commit right now. Sorry for the delay.


Page not up-to-date

Page is missing Release Notes for 1.0.4739.1000 and 1.0.5100.1100.

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

ID: 3cb10266-d3ca-31b1-31a0-bd4952e6736b
Version Independent ID: 9adcd5ff-db9f-44f9-27f6-7c689839267b
Content: What's new in the Azure Virtual Desktop Agent? - Azure
Content Source: articles/virtual-desktop/whats-new-agent.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@stryqx
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@Heidilohr
Can you please check and add your comments on this doc update request as applicable.

@VikasPullagura-MSFT The documentation currently has information about version 1.0.5100.1100, but not version 1.0.4739.1000.

Sorry for the delay in getting 1.0.4739.1000 listed. This should be visible later today.
#please-close


Basic AsyncClient

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

...

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2328  👈
#2297
main

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

Join @codetheweb and the rest of your teammates on  Graphite


Error when I try to create PipelineRun

I followed the tutorial one by one. When I executed the command
 kubectl create -f pipeline/pipeline-run.yaml

It returned one error,
Error from server (BadRequest): error when creating "pipeline/pipeline-run.yaml": admission webhook "webhook.tekton.dev" denied the request: mutation failed: cannot decode incoming new object: json: unknown field "serviceAccount"

The message is a little weird for me. Could anyone help me with that?
Besides, there are some typos in the tutorial:
In the first step of Execute the pipeline section, there is no such a file named pipelinerun.yaml, so we need to change it to pipeline-run.yaml.
Thanks. I didn't submit any issue before. Any feedback is welcome.

@frank0767 , in the latest version of tekton - serviceAccount keyword has been changed to serviceAccountName. Kindly change into your yaml file and retry. It should work.
Please let me know if all works fine - accordingly I'll upadte repo alongwith typo errors.
Thanks!

@maheshwarishikha Thank you a lot. It works well with that change.


Remove System.Drawing reference from live deployment

Designers shouldn't use attributes, generate descriptions during design time on request.

Based on these:

https://code.msdn.microsoft.com/Windows-Workflow-9e867448
http://stackoverflow.com/questions/15423061/wf4-runtime-attempts-to-load-loosely-coupled-activity-designer
http://blogs.msdn.com/b/tilovell/archive/2011/05/08/iregistermetadata-and-best-practice-associating-workflow-activity-designers.aspx

None of them are working:

When you separate the designers into a separate .Design.dll, there is no way to set icons and descriptions for the toolbox. Only the WF designer uses the IRegisterMetadata interface, the toolbox browses only the .dll where the activity is located.
So, when you use IRegisterMetadata to add design time attributes to activities, you can't separate the ToolboxBitmapAttribute this way, you must add this to the activity, but this way the activity .dll will still have reference on System.Drawing...

Help wanted: maybe somebody knows the solution.


Tutorial can't work - configuration is missing

In this tutorial, two Azure VMs need to be deployed and their respective Public IP addresses should be used for configuring the endpoints.

"Add the IP address of the recursive DNS resolver used by myVMEastUS test VM" - it is not mentioned where to find the IP address of the recursive DNS resolver nor how to enter it into the UI.
Even if I run a command like "nslookup -q=txt o-o.myaddr.l.google.com" to retrieve the IP of the local DNS resolver, for an Azure VM that IP address changes with every request. I would need to add a range of IP-addresses associated with the region to it or add another configuration like a DNS resolver if that would even work.

So, in my opinion this tutorial cannot be tested and should be revised.

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

ID: 9b161852-c1fa-349b-38bb-7e4156c6a270
Version Independent ID: ba04bced-40f4-0e59-16b3-ecdc5ecd07fe
Content: Tutorial: Configure subnet traffic routing with Azure Traffic Manager
Content Source: articles/traffic-manager/tutorial-traffic-manager-subnet-routing.md
Service: traffic-manager
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

@mkennten Thanks for your feedback.
Can you try using the Azure Wireserver IP <IP_ADDRESS>?
Meanwhile, I shall check internally and try to get this configuration verified.

Hi,
while I could try this, how would that help with this specific tutorial, demonstrating the subnet-routing method?

I would only be able to add the IP to one of the endpoints, not both (they cannot be overlapping/identical)
there would be no indication of the respective subnet of each VM - and that is the whole point.

The documentation is not very helpful on what exactly to put in that field "Subnet routing settings": it would make most sense to add the respective subnet CIDR block but that doesn't work in Azure. I think that might be by design since the VMs are using a public IP for outbound. If that's the case, this tutorial needs to come up with a different setup.

From: Kapil Ananth @.>
Sent: 24 May 2023 11:08
To: MicrosoftDocs/azure-docs @.>
Cc: Michael Kenntenich @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Tutorial can't work - configuration is missing (Issue #109953)
@mkenntenhttps://github.com/mkennten Thanks for your feedback.
Can you try using the Azure Wireserver IP <IP_ADDRESS>?
Meanwhile, I shall check internally and try to get this configuration verified.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/109953#issuecomment-1560734598, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI7VAMFLTPTNU3URDVCJPQ3XHXFXVANCNFSM6AAAAAAYNBKSJA.
You are receiving this because you were mentioned.Message ID: @.***>

@mkennten I have edited my comment long back and I believe you are referring to my old comment.
As stated in my comment, I shall check this internally and let you know

This is being tracked as internal content issue: 96320
#please-close


How does Joby handle multi process that take more then 10 minutes to each?

Hello
i have 3 process that should run every minute
i believe Jobby run each process is synchrony way. so it will run process number 1 and then when it will check schedule for the next process the schedule will not match because process 1 take long time..  am i wrong? (sorry about my english)

No, that doesn't sound right. Jobby forks new processes for each job, so the only thing it's really doing every minute is checking schedules. I could see if you had 1000+ jobs then just cron scheduling could exceed a minute, but that's super unlikely. Can you reproduce this reliably?


WIP: Readme revamp

Let's give the README a much-needed refresh. Let's collaborate on this to make img easier to use, and reduce the time for newcomers to get started.
Some of my goals here:

Restructure and organize the text into a more logical flow and hierarchy.
Clarify goals section. Considered non-goals as well, but left it at goals.
Emphasize Docker and Kubernetes usage since that is likely the biggest draw for using img in a containerized environment.
Explain how img can be used for Mac and Windows users.
Organize Linux installation instructions... still feel like this dominates a little too much with all the packages, etc. May want to pull this out into an INSTALLING.md file.
Trim out excess text from the CLI Usage section, for less scrolling.
Added some details for how to build and contribute to img. Could go to a CONTRIBUTING.md file instead.
General editing for grammar, punctuation, style, etc.

Resolves #251 .
Table of Contents
I'm experimenting with a depth of 3 to limit noise on the TOC.
markdown-toc --maxdepth 3 -i README.md

TODO
The following areas I still think are weak. I'm perusing common issues and looking for user gaps that could make adoption of img easier.

[ ] Better introductory level explanation to "why img?"...
[ ] More/better visuals to demonstrate and explain.
[ ] Running in common CI/CD systems: GitLab CI, Jenkins, etc.
[ ] How to include img in Dockerfiles with various bases... alpine, stretch, buster, xenial, etc.
[ ] Put details into separate files: CLI, Internal details, Contributing, etc. These can all be split out to allow the README to focus on getting started and project "orientation".

@kekoav  FYI, I was able to get img working on fedora 31 with cgroupsv2 just by creating a symlink for runc pointing to crun, which I did not expect at all to work. Not sure if it's worth mentioning in README

@kekoav FYI, I was able to get img working on fedora 31 with cgroupsv2 just by creating a symlink for runc pointing to crun, which I did not expect at all to work. Not sure if it's worth mentioning in README

@frezbo That is very nice, does that change the security requirements necessary? Can we run with less privileges?

I was running as a normal user in a fedora 31 VM.

Codecov Report

Merging #287 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #287   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files          16      16
  Lines        1006    1006
======================================
  Misses       1006    1006

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 89fb42e...0b3fd8c. Read the comment docs.

docker run --rm -it --name img --volume "$(pwd):/home/user/src:ro" --workdir /home/user/src --volume "${HOME}/.docker:/root/.docker:ro" --security-opt seccomp=unconfined --security-opt apparmor=unconfined --security-opt systempaths=unconfined --entrypoint sh r.j3ss.co/img
This is exactly how I had to run it to make it work on docker toolbox for windows.. Just dropping it here in case it helps someone. As you can see I added the double quotes for the first --volume

This is exactly how I had to run it to make it work on docker toolbox for windows.. Just dropping it here in case it helps someone. As you can see I added the double quotes for the first --volume

@ChrisTomAlx Updated to add quotes on both.


Airing anime not showing

I have a few anime in progress, some currently airing and some finished.
However in the app I can only see "Finished" anime. The count shown for "watching" is correct but then only the finished entries are present in the list.
Airing titles also aren't present even in the "All" category

@noaccOS Hi, could you provide me with your anilist username?

@noaccOS Hi, could you provide me with your anilist username?

Same as on here, here's a direct link to it https://anilist.co/user/noaccOS/

I think its working fine.

I guess you applied some filter, the filter are saved even when you close the app so can you check if you have applied the filter.

Yeah that was it. I did try logging out and back in but it seems like the filter persisted anyway.
Thank you for your help and sorry for the false issue


Docs: Fix typo

Summary of the changes / Why this improves CrateDB
Fix small typo in array function documentation
Checklist

[ ] Added an entry in CHANGES.txt for user facing changes
[ ] Updated documentation & sql_features table for user facing changes
[ ] Touched code is covered by tests
[ ] CLA is signed
[ ] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Closed in favor of #10871
This PR was created against 4.3 branch but I wanted to create it against master. Just changing the merge target did not work as it would merge all news commits on the 4.3 branch.


Hdfs service should be mandatory for HBase and Hive

If user creates an environment by picking HBase/Hive from an HDP cluster added via ambari then HDFS from same cluster should automatically added by UI to the environment. Reason is HBase has hbase.rootdir that uses hdfs-site.xml core-site.xml to connect to HDFS. Without HDFS being present in environment storm topology fails at runtime throwing an exception from HBaseClient that it cannot connect to hdfs.

@shahsank3t  Can you or someone familiar with UI look in to this?
@HeartSaVioR I see that we are packaing hdfs-site.xml and core-site.xml with the topology jar if we have just HBase sink in the topology. Just curious about the logic used to pick hdfs-site and core-site if we have two hdfs services(both from different service pools) added to the same environment? Will it pick the right one?

@priyank5485
No we can't determine which is the right one, so the services which rely on configuration file like HDFS, HBase, and Hive should be selected only once.
Maybe better to prevent selecting same service multiple time in an environment until we support multi-clusters for all services properly. That may be an unnecesary limitation for other services, but safest way to avoid that issue.
We might also want to force selecting cluster for each component in order to provide corresponding configurations while deploying.
(Maybe also better to change some fields which are dependent on cluster to be read-only.)
cc. @harshach @shahsank3t

Btw I guess this issue is filed to wrong project. :) Did you intend to file this issue to the Streamline project?

@HeartSaVioR you are right. will refile in streamline


Adding an SOS page for EMERGENCY NEEDS

@tushargupta1504 we can create an SOS page for emergency needs so that location of the user is fetched and they can call ambulances hospitals or police

@tushargupta1504 assign this issue to me i can create such a page


Add request form for Organisational Login [Admin]

API Endpoint:
/create_ngo_request
header needs authorization token similar to any other API - E.g. /assign_volunteer API or update_request_info API
name, mob_number, email_id, age, address, geoaddress, request, latitude, longitude, source, status, why, what, financial_assistance, verification_status, created_by, urgent, volunteer_count
request  Category as per first question in public form
status  'received'
verification_status = 'pending'
created_by = user_id
verified_by = user_id
user_id is the user_id of logged in user.
Constraints: User must be logged in

Have made an initial commit to branch 21-new-organisational-form.
Logged In user can see a card to fill up the form in their header.
Component OrganisationalPopUpForm will need changes with fields from both initial request + fields from verification step
Flag for marking such requests in API will also be needed


(Do not merge!) Drop support for React 0.13

We won't do this yet, but React 0.14 makes everything simpler for us.
When it's out, releasing this will be a breaking change.
Changes:

No more support for function inside <Provider>, as we have parent context in 0.14
No more jumping through hoops to support React Native: we can still import React from 'react'
We can put react in peerDependencies now because it will work for React Native, and also won't cause “duplicate React” issues
With React Native 0.10, we can rely on process.env.NODE_ENV polyfill being there

Checklist:

[x] Drop support for React 0.13 in a branch
[ ] Wait for React 0.14
[ ] Wait for React Native 0.10 (will it use 0.14?)
[ ] Update the docs
[ ] Merge and release as a breaking change

What is the impetus from switching for a creator pattern to directly exporting the two components?

What is the impetus from switching for a creator pattern to directly exporting the two components?

The reason a factory was added in the first place is because we either needed React from react or from react-native, depending on what user wanted, and couldn't express this statically. With 0.14 we can just use react because react-native will just be a renderer like react-dom, and won't contain Component, PropTypes, etc.

Updated this.

Still waiting on React Native?

Not really—we'll just ask RN users to stay on previous major. I'll release this soon.


Adjust session duration implementation

I found the the implementation of session duration had some issues.
One of which is that some AWS sso roles have a maximum session duration configured in AWS and cannot be extended. However when launching a browser session, we can specify a longer duration than the duration for the session credentials.
So in this PR I have added
--duration which configures the duration for session credentials in the terminal
--browser-duration which configures the browser session duration

Good pickup on browser session duration being a different value.
AWS specifies a duration_seconds config value which can be added to roles in ~/.aws/config - we should load this if it's provided on the role rather than forcing users to use a --duration argument. I have taken a look through the codebase and it looks like we don't support this.
Separately, I wonder whether we could allow users to add a field to ~/.aws/config to configure the browser role duration, e.g.
[profile test]
role_arn=arn:aws:iam:...
granted_browser_duration_seconds=3600

What do you think of this? My thinking here is that the values are specific for a particular role and won't change that often, so it is more cumbersome for a user to enter a --browser-duration=1h --duration=1h all the time.
Also, for instances where a user does pass an argument rather than us reading ~/.aws/config, could we just use --duration in both cases, rather than --duration and --browser-duration? Is it possible for a user to use assume --browser-duration=2h --duration=1h and for this to actually work? (won't the IAM session itself expire once 1h has elapsed, even if the console has a longer session?)

Good suggestions @chrnorm! The focus for the duration flags fix was highlighted by this issue: #58
I think the multiple flags might get confusing. Should there just be one flag that duration overrides both console session and the browser session?

@meyerjrr  I am running a test on this to verify that the browser session can be longer than the iam credentials.

I realised a made some mistakes and have reverted to a single duration flag.
The console session cannot be longer than the credential session duration.
The default is that the browser session will be as long as the credentials used.


feat(echo): 增加 echov4 otel 插桩代码

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.JellyTony seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for your contribution! You can add some tests for plugin according to https://github.com/alibaba/opentelemetry-go-auto-instrumentation/blob/main/docs/how-to-write-tests-for-plugins.md after you've finished the echov4 plugin~

I cant comment on plugin code because I'm not an expert in that area, but thank you for your contribution.

Thanks for your contribution! You can add some tests for plugin according to https://github.com/alibaba/opentelemetry-go-auto-instrumentation/blob/main/docs/how-to-write-tests-for-plugins.md after you've finished the echov4 plugin~

ok

Thanks for your contribution! You can add some tests for plugin according to https://github.com/alibaba/opentelemetry-go-auto-instrumentation/blob/main/docs/how-to-write-tests-for-plugins.md after you've finished the echov4 plugin~

已添加，怎么单独执行某个库的单元测试？

Thanks for your contribution! You can add some tests for plugin according to https://github.com/alibaba/opentelemetry-go-auto-instrumentation/blob/main/docs/how-to-write-tests-for-plugins.md after you've finished the echov4 plugin~

已添加，怎么单独执行某个库的单元测试？

1、build agent
2、cd test

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
JellyTony seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

这个签署了，状态一直变更不过来

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
JellyTony seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

这个签署了，状态一直变更不过来

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
JellyTony seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

这个签署了，状态一直变更不过来

May be you should click the recheck button after you sign the CLA? cc @D-D-H

@JellyTony
我看了下，应该是你提交的 commit 邮箱不对。
commit 242458da154a7e37a9479a774fa91fc466138354 (HEAD -> feat/echo, origin/feat/echo)
Merge: 3964ba0 ad37a8d
Author: JellyTony<EMAIL_ADDRESS>Date:   Wed Aug 21 10:20:12 2024 +0800

    Merge branch 'alibaba:main' into feat/echo

麻烦修改下邮箱，你可以先把这些 commits 压成一个，然后 amend 修改

@JellyTony 应该是你提交的 commit 邮箱不对：
commit 242458da154a7e37a9479a774fa91fc466138354 (HEAD -> feat/echo, origin/feat/echo)
Merge: 3964ba0 ad37a8d
Author: JellyTony<EMAIL_ADDRESS>Date:   Wed Aug 21 10:20:12 2024 +0800

    Merge branch 'alibaba:main' into feat/echo

麻烦修改下邮箱，你可以先把这些 commits 压成一个，然后通过 amend 修改。

done

Sorry for merging this patch without review, please help review this pull request again @123liuziming

@JellyTony Sorry, would you please submit the same PR again. We accidentally clicked the merge button without review. Thanks!


Update URL in opensearch.xml

OpenSearch is broken at the moment, it seems it doesn't like the redirect.  Update the OpenSearch description to reflect the new URL, should fix search with OpenSearch.

S


make wallace warn you if you start with <10 participants but will eventually go over 10

This issue was moved to Dallinger/Dallinger#90


TFS projects

hey there,
is it planned to support TFS (not git) projects?

We don't have a plan yet. Please consider voting on this user voice item: https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/6785457-tfs-plugin-for-android-studio
Thanks,
Madhuri


[NT-643] Remove 1Password extension

📲 What
As identified in #904 we no longer need the 1Password extension.
Note: This should merge after #904 and is based off that branch.
🤔 Why
This functionality is provided by iOS 12's Password AutoFill feature.
🛠 How
Removed 1Password extension and all references to it.
✅ Acceptance criteria
The impact of this should be minimal as we previously disabled 1Password on iOS 12.

[ ] Test for regressions in the affected views.

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger


[bugfix] Support habitat-lab requirements.txt after split

Motivation and Context
With the baselines/lab split from PR 922, requirements.txt was moved. This PR updates install paths for sim testing and colab install pipelines.
Addresses #1884 and should fix broken lab test.
How Has This Been Tested
Here
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Looks like install is changed now too. Direct install with setup.py seems to no longer work, so trying to use pip setup instead.


[Event Request] codeunit 333 "Req. Wksh.-Make Order" - Event for procedure InsertHeader

Can we get the following events for the "Req. Wksh.-Make Order" Codeunit: OnInsertHeaderOnBeforePurchOrderHeaderValidate
local procedure InsertHeader(var ReqLine2: Record "Requisition Line")
    var
        SalesHeader: Record "Sales Header";
        Vendor: Record Vendor;
        SpecialOrder: Boolean;
        ///-
        IsHandled: Boolean;
    ///-
    begin
        OnBeforeInsertHeader(ReqLine2, PurchOrderHeader, OrderDateReq, PostingDateReq, ReceiveDateReq, ReferenceReq);

        with ReqLine2 do begin
            OrderCounter := OrderCounter + 1;
            if not PlanningResiliency then
                Window.Update(3, OrderCounter);

           [...]

            PurchOrderHeader."Order Date" := OrderDateReq;
            PurchOrderHeader."Expected Receipt Date" := ReceiveDateReq;

            ///
            IsHandled := false; ///NEW
            OnInsertHeaderOnBeforePurchOrderHeaderValidate(IsHandled, PurchOrderHeader, ReqLine2); ///NEW
            if IsHandled then ///NEW
                ///-
                PurchOrderHeader.Validate("Buy-from Vendor No.", "Vendor No.");
            if "Order Address Code" <> '' then
                PurchOrderHeader.Validate("Order Address Code", "Order Address Code");

               [...]

        end;
    end;

    [IntegrationEvent(false, false)]
    local procedure OnInsertHeaderOnBeforePurchOrderHeaderValidate(var IsHandled: Boolean; var PurchOrderHeader: Record "Purchase Header"; var ReqLine2: Record "Requisition Line")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.