Fix crash when sorting by network address in UI

Fixes: #278

This applies to Aggregate.prefix, Prefix.prefix, and IPAddress.address.

Doesn't look like this can be tested at this point?

Are there similar issues with the IP Address columns (primary_ip, primary_ip4, primary_ip6) in the Devices table?

Are there similar issues with the IP Address columns (primary_ip, primary_ip4, primary_ip6) in the Devices table?

Just checked and they are fine since that column already uses an order_by=("primary_ip6", "primary_ip4") and because those are related fields (not computed fields) it works as expected.

Doesn't look like this can be tested at this point?

Just manual testing for now by clicking the column a couple times for each view.

It bugs me that we're using text-nowrap on one of these three columns but not the other two, but that's not what you're here to fix. :-) Looks good, thanks!

File a bug!


Issue with NaN values in sqrt_beta_pred of the IG model

I’m encountering an issue where the model's prediction is returning NaN values.
After executing the line:
sqrt_beta_pred = self.model(x_noisy)
Upon inspection, the output is:
(Pdb) sqrt_beta_pred
tensor([[nan],
[nan],
[nan],
...
[nan]], device='cuda:0', grad_fn=)
And the input x_noisy looks like:
(Pdb) x_noisy
tensor([[-0.1985,  0.8690,  3.1156,  ...,  2.5546, -0.0584,  0.0749],
[ 0.2889,  0.0399, -1.1737,  ...,  0.3547, -0.0621, -0.9403],
...
[-0.6547,  0.0246, -0.3291,  ..., -0.2791, -0.6015,  0.7493]],
device='cuda:0', grad_fn=)
It appears that x_noisy contains reasonable values, but the model output is NaNs across the board.
What could be causing this behavior?

That is weird, I don't have that issue in my runs. Did you modify anything in the code?

You’re right, it might be an issue in my code. I’ll check it out. Please ignore for now unless I ping here.

I will remove this issue;
A little question - I saw you changed back:
At class DTEInverseGamma(DTE):
from:
def init(self, seed = 0, model_name = "DTE_inverse_gamma", hidden_size = [128, 128], epochs = 400, batch_size = 64, lr = 1e-4, weight_decay = 0, T=300):
super().init(seed, model_name, hidden_size, epochs, batch_size, lr, weight_decay, T, 0)
To:
def init(self, seed = 0, model_name = "DTE_inverse_gamma", hidden_size = [256, 512, 256], epochs = 400, batch_size = 64, lr = 1e-4, weight_decay = 5e-4, T=400, device=None):
super().init(seed, model_name, hidden_size, epochs, batch_size, lr, weight_decay, T, 0, device)
Could you advise which version you think is better?

I think the second one is better (the current version).

Thank you. Since I can’t delete the issue, I’ve closed it. Feel free to delete it.


bpf: Move to-stack trace after host firewall

When host firewall feature is enable, to-stack trace can be generated
even if the packets are rejected by host firewall policies. Generate trace
only when the packets are actually delivered to the stack.
Fixes: #12562
Signed-off-by: Yutaro Hayakawa<EMAIL_ADDRESS>Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Thanks for contributing!

/test

Looks like k8s-1.22-kernel-4.19 (test-1.22-4.19) , k8s-1.23-kernel-net-next (test-1.23-net-next) and runtime (test-runtime) tests are failing. I think this is related to https://github.com/cilium/cilium/pull/18336. I'll rebase after it is merged. Otherwise, I think this PR is ready for review.

Rebased the branch based on the latest master since #18493 is merged now.

/test

Failure in K8sPolicyTest Multi-node policy test validates fromEntities policies Validates fromEntities all policy seems similar to https://github.com/cilium/cilium/pull/18544. I'll rebase.

/test

/test-1.23-net-next

One minor, nit, I would try to create a user-facing release-note in the PR description, something like this should communicate the implications of the change correctly:
```release-note
Fix bug where Hubble flows report that a packet is both forwarded and dropped by host firewall. It will now only report the drop.
```


Conjugate gradient optimizer

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
What are the significant changes in functionality due to this change request?
Added a Conjugate gradient optimizer based on SPSA. Adding one option in Finite Difference Optimizer to alow central difference.
Skip VARMA test
Optimizer

Imported 'minpack2' for a better line search method to determine the step size so that it will find the step that satisfies decrease condition and a curvature condition.
Added 'polakRibierePowellStep' method to update the gradient
Added central difference option for finite difference and conjugate gradience
Unlike SPSA and Finite difference, persistence will not be zeroed after searching the local opt point.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Not ready for review, just want to test it.

Need some writeup for the manual.

@aalfonsi Ready for review

@JiaZhou-PU I talked to @PaulTalbot-INL . It is fine if you address the InputData in another PR.

@alfoa Changes addressed, ready for review again.

@JiaZhou-PU just other 2 comments.
Thanks
Andrea

Closure checklist passed...
PR can be merged and approved


A non-null value as always greater than a null value

SObjectPredicates.isGreater()
comparison of all primitive types and considers a non-null value as always greater than a null value.
Integer num1 = 10;
Integer num2 = null;
Assert.isFalse(num1 < num2);
This goes against the default behavior of Salesforce.

Hi @konradbeck-creditech,
Thank you for bringing this up. You’re absolutely right about the behavior, but this is documented in apex-docs:

Unlike the standard > "greater than" operator, the predicate function supports comparison of all primitive types and considers a non-null value as always greater than a null value.

This design choice is due to the underlying use of Comparers in predicates. One of the key properties of a Comparer, as defined by its contract, is anti-symmetry:

sgn(compare(x, y)) == -sgn(compare(y, x))

Without adhering to this constraint, sorting operations could yield incorrect results.
However, you can handle nullability using functional composition:
IPredicate isRevenueGt10AndNotNull = SObjectPredicates.isGreater('AnnualRevenue', 10)
    .andAlso(SObjectPredicates.isNotEqual('AnnualRevenue', (Object) null));

isRevenueGt10AndNotNull.test(new Account(AnnualRevenue = null)); // false
isRevenueGt10AndNotNull.test(new Account(AnnualRevenue = 0)); // false
isRevenueGt10AndNotNull.test(new Account(AnnualRevenue = 10)); // false
isRevenueGt10AndNotNull.test(new Account(AnnualRevenue = 15)); // true

Additionally, I wanted to share that I’m currently working on a package that enhances the API of our built-in functions, which will include support for predicates based on non-antisymmetric comparers.
Best regards.

Hi @konradbeck-creditech,
I've added a non-antisymmetric Comparer in the latest release. This allows you to emulate the default behavior of Apex comparison operators. However, to achieve the desired behavior, you'll still need to use functional composition:
IPredicate isRevenueGt10AndNotNull = SObjectPredicates.isCompared(
    SObjectFunctions.get('AnnualRevenue'),
    Function.constant(10),
    Comparer.nonAntisymmetricOrder(),
    1
);
// Or
isRevenueGt10AndNotNull.test(new Account(AnnualRevenue = null)); // false
isRevenueGt10AndNotNull.test(new Account(AnnualRevenue = 0)); // false
isRevenueGt10AndNotNull.test(new Account(AnnualRevenue = 10)); // false
isRevenueGt10AndNotNull.test(new Account(AnnualRevenue = 15)); // true

IPredicate isRevenueLt10AndNotNull = SObjectPredicates.isCompared(
    SObjectFunctions.get('AnnualRevenue'),
    Function.constant(10),
    Comparer.nonAntisymmetricOrder(),
    -1
);

isRevenueLt10AndNotNull.test(new Account(AnnualRevenue = null)); // false
isRevenueLt10AndNotNull.test(new Account(AnnualRevenue = 0)); // true
isRevenueLt10AndNotNull.test(new Account(AnnualRevenue = 10)); // false
isRevenueLt10AndNotNull.test(new Account(AnnualRevenue = 15)); // false

It's not as concise as I would like, but I'm currently working on a package that will provide a fluent and flexible API for working with built-in functions.
Best regards.

Hi @berehovskyi ,
Awesome!
Will definitely check it out.


#4112. JVM languages leak threads

cometd thread pool still gives ugly names to his threads (usually starts with pool-1-... example ) but i can't change it

ok i see that some of the threads now have the name ObservableUpdater-X but they still leak and many are still named pool-1-thread-Y.
I just created an empty notebook, added groovy, and then ran a cell with 1+1 several times:

I encountered the thread naming problem in my own project. Java thread pool executor is very convenient tool, but it does not allow to define thread naming policy. Even if one passes a name to a thread using custom thread factory, it soon becomes obsolete due to thread reusing,
One needs to use something like Thread.currentThread().setName(...) to keep thread names up to date with running processes. Also one can keep separate Thread - name mapping.


Feature/doc request: support for changing tables?

This looks pretty cool, but does it support adding or removing or changing columns?  The README is not explicit but seems to hint that it can only generate brand new tables.

Hi @brandondrew, thanks for the request!
Yep, currently it doesn't support any changing columns and I'm now considering adding some features.
So I'll add some epics for the development to projects and fix README.


Add support for get() without key, returning all rows/documents in table/collection

db.get(key) works well when a key is provided, returning a specific row in the table.
db.get() would work wonderfully to return all rows in a table, since no key was provided.

This PR makes it possible. Minor changes to make it happen:

Moved isExpired logic to _checkIsExpired() fn, so it can be re-used per row, if multiple rows are returned.
Added Array handler for _deserializeData() fn.

The only part I wasn't sure about was the name-spacing, should it return all rows in a particular name-space? Or all rows across all name-spaces?
I'll send a separate PR shortly for the mongo module.
Edit: https://github.com/lukechilds/keyv-mongo/pull/31

Thanks for working on this.
This will need to have support in all official storage adapters before it can be merged. It will also need to have tests added in https://github.com/lukechilds/keyv-test-suite which run against all adapters.
Is this something you're willing to work on?

I'll try when I can though I'm not sure yet when I'll find the time. If you or anyone else can help in the meantime, that'd be great of course. I've been using these changes in my implementation for a little while now and it's working well. Hopefully it's valuable to others too.

Completely understand about not having time, I've been meaning to work on this for a while myself (https://github.com/lukechilds/keyv/issues/40) but also haven't had the time.


revert: Remove MESSAGEBUS_TOPICS_SYSTEMEVENTTOPIC workaround

Fix #338
Signed-off-by: Cherry Wang<EMAIL_ADDRESS>

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-compose/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

https://github.com/edgexfoundry/edgex-compose/pull/334 missed the make build, so there are some more changes in this PR


chore(Deps) dawidd6/action-download-artifact action to v3

This PR contains the following updates:

Package
Type
Update
Change

dawidd6/action-download-artifact
action
major
v2 -> v3

Release Notes

dawidd6/action-download-artifact (dawidd6/action-download-artifact)
v3
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

🦙 MegaLinter status: ✅ SUCCESS

Descriptor
Linter
Files
Fixed
Errors
Elapsed time

✅ COPYPASTE
jscpd
yes

no
1.18s

✅ CSS
stylelint
1
0
0
1.45s

✅ JAVASCRIPT
standard
1
0
0
1.65s

✅ JSON
eslint-plugin-jsonc
3
0
0
3.56s

✅ JSON
npm-package-json-lint
yes

no
0.67s

✅ JSON
prettier
3
0
0
0.33s

✅ JSON
v8r
3

0
10.11s

✅ MARKDOWN
markdownlint
8
0
0
0.56s

✅ MARKDOWN
markdown-link-check
8

0
1.55s

✅ MARKDOWN
markdown-table-formatter
8
0
0
0.38s

✅ REPOSITORY
gitleaks
yes

no
0.18s

✅ REPOSITORY
git_diff
yes

no
0.01s

✅ REPOSITORY
grype
yes

no
11.63s

✅ REPOSITORY
secretlint
yes

no
1.37s

✅ REPOSITORY
trivy
yes

no
9.65s

✅ REPOSITORY
trivy-sbom
yes

no
2.73s

✅ YAML
prettier
3
1
0
0.83s

✅ YAML
v8r
3

0
5.39s

See detailed report in MegaLinter reports
MegaLinter is graciously provided by

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

Autoclosing Skipped
This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.


[release-1.21] dedup domains for gateways with case sensitivity

This is an automated cherry-pick of #49674

hold until 1.21.0 released.
cc @aryan16

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio_release-1.21
8b6e8fa6b0f4e8dc87049984ba85943adc4ebd6e
link
unknown
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


HTTP Error 503+PermissionError: [WinError 32] +PermissionError: [WinError 5]+RecursionError

here are some error:

HTTP Error 503
PermissionError: [WinError 32]
PermissionError: [WinError 5]
RecursionError

This is the result of executing:
translate_arxiv 2205.15510
The current mathtranslate is latest
Start
engine google
language from en
language to zh-CN

arxiv number: 2205.15510

temporary directory C:\Users\29927\AppData\Local\Temp\tmpyucy8gow
trying to download from https://arxiv.org/e-print/2205.15510
main tex files found:
.\main.tex
.\MOB-ML for dipole\main.tex
Processing .\main
Cache is found
It is a full latex document
  0%|                                                                                | 0/49 [00:00<?, ?it/s]Error found in Parapragh 1
Content
  \date{\today}
  \begin{abstract}
This study extends the accurate and transferable molecular-orbital-based machine learning (MOB-ML) approach to modeling the contribution of electron correlation to dipole moments at the cost of Hartree--Fock computations.
A molecular-orbital-based (MOB) pairwise decomposition of the correlation part of the dipole moment is applied, and these pair dipole moments could be further regressed as a universal function of molecular orbitals (MOs).
The dipole MOB features consist of the energy MOB features and their responses to electric fields.
An interpretable and rotationally equivariant Gaussian process regression (GPR) with derivatives algorithm is introduced to learn the dipole moment more efficiently.
The proposed problem setup, feature design, and ML algorithm are shown to provide highly-accurate models for both dipole moment and energies on water and fourteen small molecules.
To demonstrate the ability of MOB-ML to function as generalized density-matrix functionals for molecular dipole moments and energies of organic molecules, we further apply the proposed MOB-ML approach to train and test the molecules from the QM9 dataset.
The application of local scalable GPR with Gaussian mixture model unsupervised clustering (GMM/GPR) scales up MOB-ML to a large-data regime while retaining the prediction accuracy.
In addition, compared with literature results, MOB-ML provides the best test MAEs of 4.21 mDebye and 0.045 kcal/mol for dipole moment and energy models, respectively, when training on 110000 QM9 molecules. The excellent transferability of the resulting QM9 models is also illustrated by the accurate predictions for four different series of peptides.
\end{abstract}
  2%|█▋                                                                                | 1/49 [00:00<00:27,  1.78it/s]
Traceback (most recent call last):
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate_arxiv.py", line 143, in main
    success = translate_dir('.', options)
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate_arxiv.py", line 75, in translate_dir
    translate_single_tex_file(file_path, file_path, options.engine, options.l_from, options.l_to, options.debug)
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate.py", line 255, in translate_single_tex_file
    text_final = latex_translator.translate_full_latex(text_original)
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate.py", line 227, in translate_full_latex
    raise e
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate.py", line 220, in translate_full_latex
    latex_translated_paragraph = self.translate_paragraph_latex(latex_original_paragraph)
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate.py", line 163, in translate_paragraph_latex
    latex_translated_paragraph = self.translate_text_in_paragraph_latex_and_leading_brace(latex_original_paragraph)
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate.py", line 158, in translate_text_in_paragraph_latex_and_leading_brace
    latex_translated_paragraph = self.translate_text_in_paragraph_latex(latex_original_paragraph)
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate.py", line 137, in translate_text_in_paragraph_latex
    result += self._translate_text_in_paragraph_latex(split) + ' ' + sep + ' '
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate.py", line 120, in _translate_text_in_paragraph_latex
    text_translated_paragraph = self.translate_paragraph_text(text_original_paragraph)
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate.py", line 95, in translate_paragraph_text
    parts_translated.append(self.translator.translate(part))
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate.py", line 55, in translate
    raise e
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate.py", line 49, in translate
    result = self.try_translate(text)
  File "C:\Program Files\Python310\lib\site-packages\mathtranslate\translate.py", line 41, in try_translate
    return self.translator.translate(text, self.language_to, self.language_from)
  File "C:\Program Files\Python310\lib\site-packages\mtranslate\core.py", line 80, in translate
    raw_data = urllib.request.urlopen(request).read()
  File "C:\Program Files\Python310\lib\urllib\request.py", line 216, in urlopen
    return opener.open(url, data, timeout)
  File "C:\Program Files\Python310\lib\urllib\request.py", line 525, in open
    response = meth(req, response)
  File "C:\Program Files\Python310\lib\urllib\request.py", line 634, in http_response
    response = self.parent.error(
  File "C:\Program Files\Python310\lib\urllib\request.py", line 563, in error
    return self._call_chain(*args)
  File "C:\Program Files\Python310\lib\urllib\request.py", line 496, in _call_chain
    result = func(*args)
  File "C:\Program Files\Python310\lib\urllib\request.py", line 643, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 503: Service Unavailable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\Python310\lib\shutil.py", line 622, in _rmtree_unsafe
    os.rmdir(path)
PermissionError: [WinError 32] 另一个程序正在使用此文件，进程无法访问。: 'C:\\Users\\29927\\AppData\\Local\\Temp\\tmpyucy8gow'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\Python310\lib\tempfile.py", line 843, in onerror
    _os.unlink(path)
PermissionError: [WinError 5] 拒绝访问。: 'C:\\Users\\29927\\AppData\\Local\\Temp\\tmpyucy8gow'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\Python310\lib\shutil.py", line 622, in _rmtree_unsafe
    os.rmdir(path)
PermissionError: [WinError 32] 另一个程序正在使用此文件，进程无法访问。: 'C:\\Users\\29927\\AppData\\Local\\Temp\\tmpyucy8gow'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\Python310\lib\tempfile.py", line 843, in onerror
    _os.unlink(path)
PermissionError: [WinError 5] 拒绝访问。: 'C:\\Users\\29927\\AppData\\Local\\Temp\\tmpyucy8gow'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\Python310\lib\shutil.py", line 622, in _rmtree_unsafe
    os.rmdir(path)
PermissionError: [WinError 32] 另一个程序正在使用此文件，进程无法访问。: 'C:\\Users\\29927\\AppData\\Local\\Temp\\tmpyucy8gow'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\Python310\lib\tempfile.py", line 843, in onerror
    _os.unlink(path)
PermissionError: [WinError 5] 拒绝访问。: 'C:\\Users\\29927\\AppData\\Local\\Temp\\tmpyucy8gow'

......
.....
......
    onerror(os.rmdir, path, sys.exc_info())
  File "C:\Program Files\Python310\lib\tempfile.py", line 846, in onerror
    cls._rmtree(path, ignore_errors=ignore_errors)
  File "C:\Program Files\Python310\lib\tempfile.py", line 855, in _rmtree
    _shutil.rmtree(name, onerror=onerror)
  File "C:\Program Files\Python310\lib\shutil.py", line 750, in rmtree
    return _rmtree_unsafe(path, onerror)
  File "C:\Program Files\Python310\lib\shutil.py", line 624, in _rmtree_unsafe
    onerror(os.rmdir, path, sys.exc_info())
  File "C:\Program Files\Python310\lib\tempfile.py", line 846, in onerror
    cls._rmtree(path, ignore_errors=ignore_errors)
  File "C:\Program Files\Python310\lib\tempfile.py", line 855, in _rmtree
    _shutil.rmtree(name, onerror=onerror)
  File "C:\Program Files\Python310\lib\shutil.py", line 750, in rmtree
    return _rmtree_unsafe(path, onerror)
  File "C:\Program Files\Python310\lib\shutil.py", line 624, in _rmtree_unsafe
    onerror(os.rmdir, path, sys.exc_info())
  File "C:\Program Files\Python310\lib\tempfile.py", line 846, in onerror
    cls._rmtree(path, ignore_errors=ignore_errors)
  File "C:\Program Files\Python310\lib\tempfile.py", line 855, in _rmtree
    _shutil.rmtree(name, onerror=onerror)
  File "C:\Program Files\Python310\lib\shutil.py", line 750, in rmtree
    return _rmtree_unsafe(path, onerror)
  File "C:\Program Files\Python310\lib\shutil.py", line 624, in _rmtree_unsafe
    onerror(os.rmdir, path, sys.exc_info())
  File "C:\Program Files\Python310\lib\tempfile.py", line 846, in onerror
    cls._rmtree(path, ignore_errors=ignore_errors)
  File "C:\Program Files\Python310\lib\tempfile.py", line 855, in _rmtree
    _shutil.rmtree(name, onerror=onerror)
  File "C:\Program Files\Python310\lib\shutil.py", line 750, in rmtree
    return _rmtree_unsafe(path, onerror)
  File "C:\Program Files\Python310\lib\shutil.py", line 624, in _rmtree_unsafe
    onerror(os.rmdir, path, sys.exc_info())
  File "C:\Program Files\Python310\lib\tempfile.py", line 846, in onerror
    cls._rmtree(path, ignore_errors=ignore_errors)
  File "C:\Program Files\Python310\lib\tempfile.py", line 855, in _rmtree
    _shutil.rmtree(name, onerror=onerror)
  File "C:\Program Files\Python310\lib\shutil.py", line 750, in rmtree
    return _rmtree_unsafe(path, onerror)
  File "C:\Program Files\Python310\lib\shutil.py", line 624, in _rmtree_unsafe
    onerror(os.rmdir, path, sys.exc_info())
  File "C:\Program Files\Python310\lib\tempfile.py", line 840, in onerror
    resetperms(path)
  File "C:\Program Files\Python310\lib\tempfile.py", line 832, in resetperms
    _os.chflags(path, 0)
RecursionError: maximum recursion depth exceeded while calling a Python object

But actually I'm already an administrator

This seems to be a network error. However the super-long error information is not expected and is already solved in the newest version. please pip install --upgrade mathtranslate to avoid long error information in the future.


add doc to code format in Intellij

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/2833/
Test PASSed.


File Icons

Love Brackets, but at the current time, setting Brackets to open a specific file type makes the file's icon turn into the boring white document icon. Perhaps a set of icons for when Brackets is the default opener for a file type...?

In Brackets 1.2 on Windows 7 I have plain document icons for files that are supposed to be opened by Brackets by default.

For the mac.
Make up a doc-icon. The Bracket icon, with a page outline, saved as a png converted to .icns, label it BracketsDoc.icns.
Select the Brackets.app icon, open the package content.
In the content folder, open the Resource folder and put in the icns file.
Open the info.plist file in the content folder.
Select Document types, select a type, example HTML Source.
Below the Document Type Name, add item, select from list, Icon File Name, and in value column type or paste in, BracketsDoc.icns.
Do this for all of the types that you wish.
Given the simplicity, I am surprised this is an issue. But then I am surprised how much it bugs the hell out of me to see the generic doc icon.

@MLCozad thanks for your contribution. Could you please post a screenshot? Im kinda new in web development and i have a difficult to execute what you said.
This is where i got stucked:
"Below the Document Type Name, add item, select from list, Icon File Name, and in value column type or paste in, BracketsDoc.icns."


Proposal: Make ScrollPhysics reactive

Hello there!
Right now a ScrollPhysics is only updated if you change the class type.
https://github.com/flutter/flutter/blob/f82046b150ad9d54962ad8098df2babdad34c596/packages/flutter/lib/src/widgets/scrollable.dart#L458-L463
I think it would be great to follow some other patterns inside the flutter framework to allow this class to be reactive. This would be to add a new method inside the ScrollPhysics like
bool shouldReload (covariant ScrollPhysics old) => false;

Notice by default would return false, so the behaviour for all the current ScrollPhysics would be the same as now.
Then when the Scrollable widget updates we would add
  if (newPhysics?.runtimeType != oldPhysics?.runtimeType ||
      newPhysics?.shouldUpdate(oldPhysics!))
        return true;

This pattern can be seen in LocalizationsDelegate, SliverPersistentHeaderDelegate,  SliverChildDelegate,  ScrollBehavior, and many more. (In the search box from the api website write should to see the rest)
Use case
I am building a ScrollPhysics that allows snapping to different positions if the scrollOffset is too close (Similiar to PageScrollPhysics). This would be very useful for SliverAppBars to accomplish this behaviour, where it only snaps to a expanded/collapsed state, but the scroll can not stop in the middle.
https://user-images.githubusercontent.com/19904063/114042305-99013e80-9885-11eb-876e-1e2966379539.MP4
It works, but right now it is not reactive. People need to do a hot-restart to see the changes made to it.
CustomScrollView(
   physics: SnapScrollView(offset: 64, range: 20),
   slivers: [
      ....
   ]
);

It is important to consider this comment from the Scrollable doc though.
https://github.com/flutter/flutter/blob/f82046b150ad9d54962ad8098df2babdad34c596/packages/flutter/lib/src/widgets/scrollable.dart#L142-L155
I don't understand why it would be needed to create this object for each frame to see if has changed its configuration. Right now the type runtime is compared only when the widget or its dependencies are updated. So I think it would be the same to also check it through a shouldUpdate method if the configuration has changed.
Notice the ScrollPhysics class is immutable so it should not change its configuration after created. And when it changes didDependenciesUpdate or didWidgetUpdate should be triggered if is used in that scrollable.
cc: @Piinks

As you can see I did not get any response about it 😅


FR: Add ability to capture lists using output capturing

Currently can only capture a single text value from data returned from REST, python, templates, etc. Should extend this to allow capture of all items. For example, all interfaces, all zones, all security rule names, etc

Example .meta-cnc.yaml can be found here:
https://raw.githubusercontent.com/nembery/Skillets/experimental/kitchen_sink/rest_show_interfaces/panos/.meta-cnc.yaml

and example json path expression to capture a list from JSON output can be found here:
https://github.com/nembery/Skillets/blob/experimental/kitchen_sink/rest_show_addresses/panos/.meta-cnc.yaml


Add a "Add all regions to current playlist" action

...and fix a leaking RgnPlaylistItem if insertion somehow fails.

:white_check_mark: Build sws 556-master completed (commit https://github.com/reaper-oss/sws/commit/b3ec9dba36 by @cfillion)

Windows 64-bit

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x64.pdb
build/sws-<IP_ADDRESS>-Windows-x64-add-all-regions-to-playlist-action-b3ec9dba.exe

Windows 32-bit

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x86.pdb
build/sws-<IP_ADDRESS>-Windows-x86-add-all-regions-to-playlist-action-b3ec9dba.exe

macOS x86 64-bit

build/sws-<IP_ADDRESS>-Darwin-x86_64-add-all-regions-to-playlist-action-b3ec9dba.dmg

macOS x86 32-bit

build/sws-<IP_ADDRESS>-Darwin-i386-add-all-regions-to-playlist-action-b3ec9dba.dmg

macOS ARM 64-bit

build/sws-<IP_ADDRESS>-Darwin-arm64-add-all-regions-to-playlist-action-b3ec9dba.dmg

Linux x86 64-bit

build/sws-<IP_ADDRESS>-Linux-x86_64-add-all-regions-to-playlist-action-b3ec9dba.tar.xz

Linux x86 32-bit

build/sws-<IP_ADDRESS>-Linux-i686-add-all-regions-to-playlist-action-b3ec9dba.tar.xz

Linux ARM 64-bit

build/sws-<IP_ADDRESS>-Linux-aarch64-add-all-regions-to-playlist-action-b3ec9dba.tar.xz

Linux ARM 32-bit

build/sws-<IP_ADDRESS>-Linux-armv7l-add-all-regions-to-playlist-action-b3ec9dba.tar.xz


Add maesh helm chart

Signed-off-by: Michael<EMAIL_ADDRESS>Description
This PR adds the Maesh helm chart to hub.helm.sh
Maesh helm chart repo: https://github.com/containous/maesh

The Artifact Hub is another place you can list your repos. To do that, you login (or create an account), create an organization, and list your repository. You can link it to a user or organization.


routes working to get to single property view, nothing rendering yet.

please do not merge

Everything on this one is done now.


Features brainstorm for 1.3b

duplicate person detection update(not by name but by phone or email maybe?) (garret)
easy-to-detect flags detection (case-sensitiveness)
output box display update, make formatting better and wrap around to prevent horizontal scrolling.
error handling stardardization(do we want to inform users a command did not change anything? What should we do if there are multiple inputs that cause errors?)
5.Update DG to mention not-in-scopes.

Empty optional fields : "-"


Update ammo.ts

The ammo selection is returning array in the API. I'm doing the change based on how bazaar is set up, since the return in the API looks the same.
btw I have no idea what I'm doing. Sorry in advance.

Nice spot, thanks for fixing it.


Final PR for capstone project

Dear Revewer,
Welcome to our Ruby capstone project! It was done in collaboration with @jfoyarzo, @Dadadon  and @MattGomb. The project application was created in accordance with the requirements of Ruby group capstone - Catalog of my things.
This is the final PR, all functionality was created in the other PRs.
In the App we have all the methods required and described, we created the interface to match the requirements also, and you can find the introductory video here.

@OLIPLICHE Hi! What do you mean by 'verification of the data after quitting the app?' We tried all kinds of combinations, and every piece of data gets saved in the jsons. We can also list them. Please elaborate on this!

Sorry for replying a little bit late, we have a different time zone. Thank you for the screenshot you sent. please submit that for the next reviewer to review.

Dear Second Reviewer! As the below pictures show, the data preservation works perfectly!

I added books, albums, games (just the last one on the screenshot)

These are all the info entered ^
And they all get properly saved in the json files:

And after quitting the app and starting it again, I can list all the information in the same form, and everything is in its place


🐛 [firebase_remote_config] Getting dependency issue with new firebase_core 1.0.0

Bug report
Getting the below dependency issue. Can you please update the firebase_core to version 1.0.0
Because firebase_remote_config >=0.6.0 <0.9.0-dev.0 depends on firebase_core ^0.7.0 and app depends on firebase_core ^1.0.0, firebase_remote_config >=0.6.0 <0.9.0-dev.0 is forbidden.
So, because app depends on firebase_remote_config ^0.6.0, version solving failed.
Steps to reproduce
Steps to reproduce the behavior:

flutter run

Hi @gouthamravella
The null-safety versions of the packages are not compatible with older versions. Please use firebase_remote_config: ^0.9.0-dev.0 if you want to use core 1.0.0
Thank you


Update README.md

Coverage remained the same at 100.0% when pulling 83e870ff27b9e2b1df3ef11922835bc9eaf53ddd on wilsongp-patch-1 into 885153ffe1fa565cdb9c9563266687b51755c3bc on development.


Logo Contribution

Hi @xx45,
I just saw your app and if you need a new logo or widget design i can help you
I am waiting for you reply

That would be nice 😃, thanks. Any idea so far?

Do you have discord account? We can talk about design over there

I tend to have all the discussions here.  So that others could join us easily.

Yes, you are right.
If you have any idea we can talk on it, or i can  make a design so we would talk on it

Up to you. I know nothing about design. 😂

@revilationer , are you working on the design now?

@adamfaliq42, yes i am
I am going to share with you on this issue

Absolutely!

Hi, i have proposed 2 design for you
I wanted to make a simple and eye-catching design
You can choose one of them or i can edit whatever you want
I will serve the design with all the project files to you
I hope you like

@iamkun,  i am waiting for your reply to make a pull request
Thank you

Thanks for your great work! That looks lovely.
Still, we'd like to hear more voice before we make a decision.
Any opinions or suggestions?

@iamkun , maybe set another issue to vote for this? and put a link in the README.md to the issue page

@revilationer @adamfaliq42  Why not just keep using the current logo in README? I think it looks great.

And here, see other website already treated this as Day.js's logo.

@texas5 Why you don't like current logo instead making a brand new logo?

I agree with @zazzaz, the original logo looks great; I don't see a reason to change it, however, if I had to pick one of the above, I'd choose the first. A bit cleaner-looking than the second. :)

Well it's a hard decision. First of all, thanks @revilationer 's amazing designs. All looks perfect to me. Still, the original logo made by @xx45 also looks lovely. Discussions and opinions are all welcome, and we might not gonna to make a choice at a very short time.
Plus, personal opinion, we might could use different logo in readme and our website(maybe we will have one soon)

Ok, you can reply whenever you want the source files

@revilationer It's very nice of you, thanks. Maybe we could use your logo in our website. 😁

@xx45
I will send the link of project files but i need to ask which logo do you want to use so i can prepare the files

You may could send both if it won't bother, or a PR maybe. And thanks for your creation.

Thank you, i have made a PR

Changing logo is a big thing.  It might takes a long time thinking. Thanks your work, and please be patient.


feat: support vant2

求新增vant2的支持，很需要：https://vant-contrib.gitee.io/vant/v2/#/zh-CN/field

I am very happy to receive your issue, but the author has limited energy and cannot support every version of so many component libraries. Currently, only the latest version is supported. If necessary, you can consider raising a PR and refer to the latest version of the file to make a copy. Changes, hope you understand

I am very happy to receive your issue, but the author has limited energy and cannot support every version of so many component libraries. Currently, only the latest version is supported. If necessary, you can consider raising a PR and refer to the latest version of the file to make a copy. Changes, hope you understand

I'd love to know how to maintain the vscode snippets of the corresponding components if there is an update to the component library. Is it obtained by using a script to parse the source code of the corresponding library?

I am very happy to receive your issue, but the author has limited energy and cannot support every version of so many component libraries. Currently, only the latest version is supported. If necessary, you can consider raising a PR and refer to the latest version of the file to make a copy. Changes, hope you understand

I'd love to know how to maintain the vscode snippets of the corresponding components if there is an update to the component library. Is it obtained by using a script to parse the source code of the corresponding library?

Each large version of the component library has a corresponding json file configuration. If it is updated, the corresponding json needs to be updated. We can try to obtain the corresponding component library document through a script, and then convert it into the corresponding json.


WIP: Port CircleCI to v2

Thanks @stefanv. Is the only task of circle CI to build the docs? Does it do any testing?
Did you run the config file through the yaml checker that (I am assuming) they provide?

Apparently there's a problem with the config file.

Hi, Andrew, I'm still working on this, but will let you know once I think
it's ready for review.
On 28 February 2018 18:48:53 Andrew Nelson<EMAIL_ADDRESS>wrote:

Thanks @stefanv. Is the only task of circle CI to build the docs? Does it
do any testing?
Did you run the config file through the yaml checker that (I am assuming)
they provide?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/scipy/scipy/pull/8502#issuecomment-369456925

What are shell and extra_argv? at this point? Could be that it can't
find shell or something in extra_argv.
Once you know what both are you can do which shell, or PWD to see if it's
can't find out if it actually can't find the shell,or if there's something
in extra_argv which it can't find.

@stefanv:
export SHELL=`which bash`
python -u runtests.py ...

or something along those lines.

@andyfaff @pv So far so good; we have a working build up to deployment time.  Not sure how to test that step, though!

No idea either. You might get a clue from looking at the setup/artefacts
from circle v1.

I set up CircleCI for SciPy originally to build the docs so that we could view them to make sure things look okay with each PR (instead of having to build them locally or wait to see errors once docs were built for release).
As the first necessary additional feature are the artifacts, accessible via the "Artifacts" tab. If you go to the CircleCI build page for this PR, sign in (if necessary), and click "Artifacts" (if necessary), you'll be able to browse the documentation tree.
Once that works, the next thing needed is the deployment step for the master branch. This updates the docs on github with each merged PR.
I haven't done any 2.0 migrations for my repos yet, though, so I'm not sure how to set these up for 2.0. Hopefully it's not too bad.

@stefanv: if I read the config correctly, this won't store the artefacts
for PRs, because the deploy step is limited to branch:master?
The limitation to master branch should only apply to the part that
uploads the files to scipy/devdocs. The artefacts should be stored also
for PRs, because then the documentation can be viewed also for PRs.

OK, I moved the artifact storage to the build step.

@pv @andyfaff Can either of you see the artifacts?  That tab does not appear for me, so I wonder if I have the correct permissions.

@stefanv You probably just need to login on the top right corner. It seems to periodically log me out. Permissions should likely be ok as "owner".
Here's a screencap after logging in & clicking the tab for this PR:

Logging out and then in again did the trick; thanks @tylerjereddy!

Thanks, merged. I guess there's no way to test the deploy step before merging.

@pv That's useful to know, thanks; I'll do a PR soon.

Seems to be broken again, I guess aftermath of the circleci outage.
Was the fix to remove the deploy key from the scipy main repository? I guess it got re-added.


Mark trail

Fix bug #39 and fix visual format for Search page and for user profile.

Design decision was made to split up TrailList.tsx into TrailDisplay and TrailList. The decision was made because the Profile.tsx needed to reuse the TrailDisplay functionality, but we could only export either the TrailList or TrailDisplay functionality in the original design. Thus, we decided to split the responsibilities of TrailList component into two subcomponents.


find() is returning one character string instead of boolean

Describe the bug
I have a postgres database and after I insert a record using CI's query builder, I see that the boolean field can_be_sold is indeed inserting as a boolean. However after I perform a find() on this record, it's returning a string as "t" instead of true. My ItemModel looks like this:
<?php namespace Item\Models;

use App\Models\BaseModel as Model;

class Item extends Model
{
    protected $table      = 'items';
    protected $primaryKey = 'id';
    protected $returnType = '\Item\Models\Item';

    protected $allowedFields = ['name', 'description', 'image_path', 'can_be_sold', 'rarity'];

    protected $useSoftDeletes = true;
    protected $useTimestamps  = true;
    protected $skipValidation = true;
}

My BaseModel looks like this:
<?php namespace App\Models;

use CodeIgniter\Model;

class BaseModel extends Model implements \JsonSerializable
{
    /**
     * Fields to hide when being serialized.
     *
     * @var array
     */
    protected $hidden = [];

    /**
     * Populate model with array of data.
     *
     * @param array $data
     * @return Model
     */
    public function populateFromArray(array $data)
    {
        $classSet = \Closure::bind(function ($key, $value) {
            $this->$key = $value;
        }, $this, get_class($this));
        foreach (array_keys($data) as $key)
        {
            $classSet($key, $data[$key]);
        }
        return $this;
    }

    public function toArray()
    {
        return (array) $this;
    }

    /**
     * How object returns when being serialized.
     *
     * @return array|mixed
     */
    public function jsonSerialize()
    {
        foreach ($this->hidden as $field)
        {
            unset($this->$field);
        }

        return $this;
    }
}

CodeIgniter 4 version
"codeigniter4/framework": "4.0.0-beta.2"
Affected module(s)
CodeIgniter\Model
Expected behavior, and steps to reproduce if appropriate
It should return boolean as it is pulled from the database. I am looking at the record and it is boolean datatype and is states true.
Context

OS: Mac
Web server Apache
PHP version 7.2

Unfortunately, it seems to be a postgre issue after digging into the CI code and doing multiple var_dump's everywhere. Would it be bad if I set some sort of mutator on the class to convert it to a boolean? This is unfortunate that postgres returns it as a string... seems strange to have that kind of behavior. Or maybe I should go with a different database driver altogether?

First: pls check on current CI version.
Second : paste entity code .
On Fri, Jul 19, 2019, 22:45 hlohrenz<EMAIL_ADDRESS>wrote:

Unfortunately, it seems to be a postgre issue after digging into the CI
code and doing multiple var_dump's everywhere. Would it be bad if I set
some sort of mutator on the class to convert it to a boolean? This is
unfortunate that postgres returns it as a string... seems strange to have
that kind of behavior. Or maybe I should go with a different database
driver altogether?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeigniter4/CodeIgniter4/issues/2096?email_source=notifications&email_token=ACAGMUQSCBOUZVOCL232ZYDQAHOSLA5CNFSM4IE6SGYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2MAE7A#issuecomment-513278588,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACAGMUVCUGR5GHTM5FIX4LDQAHOSLANCNFSM4IE6SGYA
.

@hlohrenz How did you end up handling this? If Postgres is returning boolean datatypes as "true" and "false" it seems to me that is something that should be converted in the driver to actual PHP `bools.

Since this is a problem with Postgres, it should not be handled by the driver but by Entity class because in the end what is happening is that the returned value is not a boll but text.
If handled by the driver it will create extra processing and may lead to performance issues in large tables.
I think it should be the Entity to cast these fields as it is done for MySql users.

On investigation, this appears to be "normal" postgres behavior, and the recommended approach to get around t is to cast or convert the result yourself. I don't think this should be treated as a fixable bug, and will close the issue.


Bro i use your lib but i have problem with the width

Bro, I use your lib but I have a problem with the width of the dropify container plz fix that.
The dropify container is getting 120% of the parent width
I try this but not working
.dropify-wrapper{
  max-width: 95% !important;
  width: 95% !important;
}

And this not work
<div style="width:100%;">
       <input type="file" id="category_image_update" [(ngModel)]="category_image_update" name="category_image_update" class="dropify"
        data-default-file="" data-height="280" data-width="" data-max-width="200px"
        data-allowed-file-extensions="jpg png jpeg gif bmp" data-max-file-size-preview="2M"/>
</div>

having the same issue...

just work for height not for width


Generate JNI fuction following JNI standards

When java package names contain _, the underscore needs to be escaped
as _1. Without this escaping, Java can not find the native function
This change also proposes a test framework for Java initiated
applications calling into Rust generated functions.
fixes https://github.com/duchess-rs/duchess/issues/166

This branch has conflicts that must be resolved

unfortunately, can't merge yet :/


The future of JMESPath

Dear all,
After many careful thoughts, I would like to re-open the discussion we had with regards to the status of this project.
I would like to present an unofficial fork of this project that I – together with my co-author @jdevillard – can commit to maintain for the foreseeable future provided this is received well amongst the community. I would love nothing more than close this fork and rely on this original project. However, the slow progress of this project makes it impossible to invest in JmesPath enhancements if there is no guarantee that this makes it to the various language libraries.
This is a preliminary clone of the original page that I will update depending upon community requirements:

Align the existing JEP proposals and have the community vote on their status. Some could be including in the still unofficial but current specification. Some could be marked specifically as "extensions" and provisions could be made in the various libraries to clearly delineate standard vs extensions.
Update links to the various official libraries with added references to the more up-to-date but still unofficial ports.

I would like to welcome members to the corresponding GitHub organization so that we could make sure to have a strong community effort.
To be honest, I have never maintained a community open-source project and have frankly no idea to do this. However, I feel there is a need and I would welcome any help in this regards.
Please, do not get me wrong - I would like this project to serve as an umbrella for up-to-date libraries, specifications and a committing to study the status of various pending proposals. My goal is not to shortcircuit the original maintainer. But I feel it is long overdue that some updates happened to the status of this projet.
Please, dear community, if this offends anyone, please feel free to let me know.

@chris-armstrong I just realize that you started the same effort.
Although I have started to cherry-pick various fixes and enhancements to my fork,
should we use your fork instead ?
I'm mainly interested in the spec and proposals.
I see that you have proposals as well.
I was planning to split the spec from the website itself.
Once that's done, I can certainly close my fork.
I'm interested to hear what everyone thinks.

@springcomp can you describe the organisation that is backing you? I believe you are working on this on behalf of an employer
@innovate-invent I will be involved from a personal standpoint and not with any corporate backing. Although this would be on a best effort basis, and cannot make any guarantees, I believe I can certainly dedicate a small amount of time on a continuous basis. Like a few hours every month.
My goal is to foster a community effort and I'm more than willing to share the work. That's why I created an organization instead of hosting this on my private GitHub account.

I believe the goal was to separate the website code base and issues from the core specification. This new repository would need to include all the necessary documentation for contributing to the JMESPath specification, including some guiding principles.

Of course that is the goal. Just wanted to bootstrap the effort with more concrete steps than previously when I participated in the discussion.

Right, are you planning on forking https://github.com/jmespath/jmespath.jep into your organisation? Or did you have a different direction planned?

Right, are you planning on forking https://github.com/jmespath/jmespath.jep into your organisation? Or did you have a different direction planned?

I think one repository for both the spec and its proposals would make sense. This would be separate from the website. That's the direction I'd like to take.
But I cannot alone decide if I like a particular implementation. So there would be at least a community consensus for each proposal. I'm currently prototyping the JEP-11 Lexical Scoping proposal, and that's where you find out about trade-offs.

Would you want to keep the repo as a fork so that the issues remain with the original? I think we would have to break the fork relationship to enable issue moderation on the fork.
JEP-11 is probably the best first item to be integrated.

Would you want to keep the repo as a fork so that the issues remain with the original? I think we would have to break the fork relationship to enable issue moderation on the fork.

@innovate-invent You are right. In the long run, either I will close the site or break the fork relationship.

JEP-11 is probably the best first item to be integrated.

I have instantiated the JEP repository with existing proposals.

Dear community,
@jdevillard and myself have now setup the various forks required for ensuring the future of JMESPath.
A JMESPath Site fork has been setup.
It is clearly marked as being unofficial.
I have merged most of the pending pull requests that made sense to fix various typos.
If you feel you have submitted a pull request that has been left out, please contact us.

As the goal to make sure the JMESPath specification receives ongoing improvements
we decided to fix the initial version of the spec as of 2016-09-05.
More specifically, the version is  2016-09-05-9e8d0e3 in reference to the commit that last updated the spec.
The ABNF specification grammar has been split to make it easy to refer to directly.

The libaries page has also been updated to retrieve the compliance level
of the latest version of the spec. I expect libary implementors will want to
opt in to this declaration. The compliance level is retrieved at publication time
from the original GitHub repositories of each library implementation.

We expect to add various regression tests to the JMESPath compliance test suite.
The test suite has thus been unofficially forked for this purpose as well.
Early days
In the coming weeks, we will probably start adding a CONTRIBUTING GUIDE, various
documentations, and start accepting pull requests. In particular, library authors
may want to report compliance level from their GitHub releases. We will work out
a way to display multiple – past, current and preview – versions of the specification from the website.
Next steps
Specification
The very first step would probably to merge JEP-12 in the specification and, thus, create an updated version. My understanding is that 'Raw String Literals' have been accepted but are not officially part of the specification yet.
The JMESPath proposals site has also been forked unofficially for this purpose.
propsals have been converted to markdown for wider consumption and it will start accepting pull requests as well.
As we have never maintained a sizeable community effort, I’m not sure how to proceed.
But we will probably setup a voting system for accepting proposals. We would like the library authors to have a voice too.
Functions contributions
The proposals site will also be accepting functions suggestions.
As this probably does not require a large consensus, I expect many functions could
be added quickly. For this reason, we came up with the concept of function sets.
A function set is a versioned set of functions that library authors choose to implement. We expect to surface the compliance level of each libraries agains any particular function set in the site. Maybe as a comparison matrix or in any other way that makes sense.
As an early step, we have split the functions specifications to their own files.
This is a rather clumsy step but I’m sure we can improve from there.
What Next
As I said,  @jdevillard and I are both new to this. Please, help us out.
As a critical step to start accepting issues, we will need to break the fork relationship at one point. It is with great regret that I started this initiative.
So please, dear community, make your voice heard. And please, if you can read this @jamesls, this is not too late for me to fold and offer constructive help with my contributions to the original – official – effort you had started in the first place.

Thank you for all of this work!
Would you be interested in listing off specific tasks that you have planned/need done? I and others would be more likely to pick away at them if we knew the best way to help.

I just spotted some very recent activity by @jamesls : https://github.com/jmespath/jmespath.py/issues/268

Would you be interested in listing off specific tasks that you have planned/need done? I and others would be more likely to pick away at them if we knew the best way to help.

@innovate-invent Indeed, I planned to do this using issues, but forks cannot receive issues and I would rather wait for wider feedback before breaking the fork relationship. But maybe by this time, we would already had feedback if our initiative was that interesting…
As I alluded to in my contribution above, we need help on:
Setup up community guidelines

CONTRIBUTING GUIDE.
CODE OF CONDUCT.
Reach out to library authors to gauge interest.
Consider a voting and governance system for proposals acceptance
… ?

Setup issue templates

JMESPath enhancement proposals templates.
New functions suggestion templates.

Website

Display multiple versions of the specification + documentation

Actions
Decide on what to do next.
My personal feelings are:

Implement JEP-11
Re-introduce JEP-12 in the spec
Consider implementing the ES6 style syntax for multi-select-hash.
Consider implementing the ternary operator. Or maybe something like an iff function.
Decide on the status of items(), from_items() and zip() functions.
…

Dear all,
I have made what I think is good progress curating some content and backlog that could be candidate for the next release of a specification.

I have initialized a milestone that we could build with the community. It currently contains the JEP-09 Lexical Scoping proposal only, that I assume will be accepted, but we need to decide what we want to include.
There a reasonably complete set of proposals from requests that I could identify in various projects. Please, do make your voice heard.
I also added some issues to discuss before some of them could be turned into proposals. Please, let me know your feedback.

Hey everyone, I wanted to chime in here with my thoughts.
First, thanks to @springcomp for the interest in the project, and in wanting to move the project forward with improvements to the spec as well as the main site.  I think that's great.
To give some context to the current state of things, the JMESPath spec has been purposefully static for a while, with no new language features being added.  This was originally intended to give the JMESPath library authors a chance to catch up and allow their libraries to stabilize.  That way you could have consistent behavior/semantics regardless of how you were using JMESPath.
I've let too much time pass without enhancing the spec, and there seems to be several consistent themes of features that users are requesting.  I would like to address that now and am open to adding new functionality to JMESPath.
I would like to have a process in place where we define exactly how changes are proposed and added to JMESPath.  I'd like this process to also include community involvement, so that anyone that wants to participate in these dicussions has the opportunity to do so.  This will likely evolve over time as the process is refined.
There's also the more pragmatic day to day concerns.  While I try to check in on several of the JMESPath repos (e.g. jmespath.py), I've not had time to keep up with all of the various repos in the jmespath org, including this jmespath.site repo.  I will spend time this week triaging and getting this repo into a better state, but long term I would love to hand over maintenance of this repo to interested members of the community.
I think the next steps would be:

Flesh out the entire process for proposing new changes to JMESPath.
Start the review process on existing proposals in the jmespath.jep repo.
Triage through the existing issues/prs on this repo.

Feel free to share any thoughts/concerns you have.

@jamesls
Thank you for your feedback.
JMESPath.site Updates

There's also the more pragmatic day to day concerns. While I try to check in on several of the JMESPath repos (e.g. jmespath.py), I've not had time to keep up with all of the various repos in the jmespath org, including this jmespath.site repo. I will spend time this week triaging and getting this repo into a better state, but long term I would love to hand over maintenance of this repo to interested members of the community.

For the record, before we broke the fork relationship, I had already made a batch of changes by merging all currently pending pull requests concerning minor changes to the site like typos and references to implementations. I also updated the embedded version of JMESPath that powers the live samples and tutorials.

I also updated the generation to support up to date libraries, while keeping the Sphinx-based generation. This was also converted to GitHub actions workflow.
Finally, I split the grammar file and also split each functions documentation into their own files for better sharing.
You can find all this in the  master branch of the jmespath-community/jmespath.site repository we initiated.
If you think this work is a reasonable start, I would be happy to contribute this back in this repository. I posit that you going through this tedious work again would be a waste of time.
JMESPath Enhancement Proposals

I would like to have a process in place where we define exactly how changes are proposed and added to JMESPath. I'd like this process to also include community involvement, so that anyone that wants to participate in these dicussions has the opportunity to do so. This will likely evolve over time as the process is refined.

The effort that we had started is completely aligned with those goals. You may have seen the discussions page were we made every effort to outline pre-proposals with the objective that sufficiently fleshed out and thought through discussions would become JEPs that could be voted on and accepted by the community.
Those discussions were arrived at by first combing through all the existing repositories – site, spec, and library implementations; all the pull requests, discussions and issues that were raised; as well as current competing forks. We are confident we made a great job categorizing those requests in a structured way.
Again we would be happy to contribute this back to you.
The workflow we envisioned is currently demonstrated with a pending pull request with the goal to accept the JEP-11 Lexical Scoping proposal (aka the let() function), with a preliminary version published for demonstration purposes.
JEP process and site generation
Please, let me stress that we made extensive changes so that we streamlined everything into only two repositories:
Specification
https://github.com/jmespath-community/jmespath.spec

JEPs have been converted to Markdown for better consumption.
Compliance tests are embedded in the documentation for functions and other grammar constructs.
The specification is updated automatically from pull requests.

Website
https://github.com/jmespath-community/jmespath.site

The website draws its content from the spec repository and generates the samples, specification rendering, etc.
It requires no manual steps as everything is generated automatically.
It includes examples, references to libraries, tutorials and examples from Wikis.
We also pioneered Frequently Used Patterns to serve as a help for newcomers into alternatives to perceived missing features in the spec.

The website also displays every versions (previous, current and on-going preview version being worked on) simultaneously with a dropdown box. It is easy to refer to a previous version of the spec and see what changed.
Again, we would be happy to contribute those changes here.
Final words
As you may have seen, @jdevillard, @innovate-invent  and I would be happy to steward the specification in a more sustainable way. It would be a honor to have your endorsement if you feel we have done a good job.

If you think this work is a reasonable start, I would be happy to contribute this back in this repository. I posit that you going through this tedious work again would be a waste of time.

Yeah this would be great.  I would probably break the contributions down into several categories of changes for jmespath.site, from least controversial to change that may need more discussion:

Typo fixes, rephrasing to make things more clear
Infrastructure related changes, javascript library updates, switching to github actions, sphinx updates, etc.
Proposed new content changes, new pages, etc.
Proposed UI/layout/theme changes.
Implementation/internal changes, making the site data driven from a separated spec repo, etc.

(1), (2) and (3) should be pretty quick, (4) and (5) may take a bit more time.  I'd be happy to accept contributions, otherwise I plan on addressing (1) and (2) in the next day or two.

Those discussions were arrived at by first combing through all the existing repositories – site, spec, and library implementations; all the pull requests, discussions and issues that were raised; as well as current competing forks. We are confident we made a great job categorizing those requests in a https://github.com/jmespath-community/jmespath.spec/discussions/38.

Awesome, thanks for doing that.  I'll spend some time over the next few days familiarizing myself with those proposals.

I put together a draft of what a more formalized jep process could look like:  https://github.com/jmespath/jmespath.jep/pull/14 .  It still needs some details worked out, but I'd like to get a discussion started around it.

Just a quick update, I've merged all of the linked pull requests except for #100 / #101 which will take some time to go through.  I'd like to switch over to github actions, but keep the existing infrastructure in place for now.  I also like the idea of splitting up the spec/grammar, just thinking through if it makes more sense in a repo that's separate from the front-end website.
Thanks for all your work on this!

I would separate the website from the spec repo. That way you don't have commits for formatting and presentation being mixed in with specification changes.

@jamesls how can we best help you moving forward. Please let us know.

Dear all,
While brainstorming ideas, we are making good strides at drafting some proposals.
Please let us know your feedback and feel free to share your ideas as well.

Dear all,
Our vision for what could constitute the next major milestone for JMESPath has been detailed.
It includes the following proposals:

General Behaviour

Documenting provisions for third-party functions.
Enabling string slices.

New Syntax

arithmetic-expression.
Compact syntax for multi-select-hash.

New Functions

Lexical Scoping and the let() function.
Object Manipulation items(), from_items() and zip() functions.
String functions.
Grouping group_by() function.

All those features are demonstrated here

Please, feel free to head over the preview page and provide feedback.

Dear all,
I'm proud to share the new version of the specification for what we call JMESPath Community.
You can even test drive all the changes!
Please, feel free to share your feedback.

After reading this issue, I'm still confused about the direction. There seems to be two variants of the specs. Does that man library developers will have to decide which version of the spec they implement?

After reading this issue, I'm still confused about the direction. There seems to be two variants of the specs. Does that mean library developers will have to decide which version of the spec they implement?

Yes, I’m afraid so 🤷♂
JMESPath Community was started as a community effort to try and bring improvements at a much quicker pace than with this original repository. At the same time, JMESPath Community contributes to discussions and proposes pull requests to this repository and various upstream libraries.
JMESPath Community is designed to be compatible with this spec and will only bring improvements requested from the community but not necessarily approved here by James.

Just want to clarify a few things here to prevent confusion.
There is one official version of the JMESPath specification, which is the
version maintained in this repo here.  Other variants you see
references to are forks of the specification.  While these forks were created
with good intentions, keep in mind that they are not officially maintained
by anyone in the JMESPath org.
If you are a library developer, implementing the official JMESPath
specification gives you the most compatibility with other tools that
use JMESPath, which generally implement the official JMESPath specification.
I realize that I have been fairly lax with people linking to unofficial
forks within the repos in this org. However, now that JMESPath feature
development has picked back up, I want to make sure we minimize confusion for
people visiting these repos.
In the interest of a clear message to new users that come here,
I'm going to ask that we start directing people towards
the official jmespath repos, including the official jmespath enhancement
proposal process.  We encourage
and welcome contributions from everyone.  We are slowly working through our
backlog of existing issues and proposals so it may take time, but we are
making progress.
Hope this helps clarify things, and thanks everyone for your understanding.
I look forward to everyone's contributions, and I'm excited to see JMESPath
evolve!

@jamesls Thanks for clarifying and I personnaly would like to thank you for your work.
If at any time I caused confusion, I would like to apologize. My intentions were always to bring constructive input and I also always tried to contribute back to this organization’s various upstream repositories.
I’m looking forward to contributing again in this repository.


[BUG] Compiler commands are no longer logged in some cases

setuptools version
65.6.0
Python version
Python 3.10
OS
Linux
Additional environment information
No response
Description
From setuptools 65.6.0 on, a python setup.py build_ext --inplace no longer logs the individual compiler commands that are executed when SETUPTOOLS_USE_DISTUTILS=local if distutils.core.setup is used. They were logged in setuptools 65.5.1, however, and are logged if setuptools.setup is used.
Expected behavior
Compiler commands should be logged by default, and setuptools.setup and distutils.core.setup should behave identically when SETUPTOOLS_USE_DISTUTILS=local
How to Reproduce

Create a temp directory to work in: mkdir /tmp/setuptools_compiler_output
cd /tmp/setuptools_compiler_output
Create a sample setup.py and extension module:

$ cat >setup.py <<EOF
from distutils.core import Extension, setup

setup(
    name="foo",
    version="0.0.1",
    ext_modules=[
        Extension(name="foo", sources=["foo.c"]),
    ],
)
EOF

Create a sample extension module:

$ cat >foo.c <<EOF
#define PY_SSIZE_T_CLEAN
#include <Python.h>

static PyMethodDef methods[] = {
    {NULL, NULL, 0, NULL}
};

static struct PyModuleDef module = {
    PyModuleDef_HEAD_INIT,
    "foo",
    NULL,
    -1,
    methods
};

PyMODINIT_FUNC
PyInit_foo(void)
{
    return PyModule_Create(&module);
}
EOF

python3 -m venv venv
. venv/bin/activate
pip install -q setuptools==65.6.0
SETUPTOOLS_USE_DISTUTILS=local python setup.py build_ext --inplace

Observe that no compiler/linker commands are printed.

Clean up after the build: rm -rf build foo*.so
pip install -q setuptools==65.5.1
SETUPTOOLS_USE_DISTUTILS=local python setup.py build_ext --inplace

Observe that the compiler/linker commands are printed.
Output
$ mkdir /tmp/setuptools_compiler_output
$ cd /tmp/setuptools_compiler_output
$ cat >setup.py <<EOF
from distutils.core import Extension, setup

setup(
    name="foo",
    version="0.0.1",
    ext_modules=[
        Extension(name="foo", sources=["foo.c"]),
    ],
)
EOF
$ cat >foo.c <<EOF
#define PY_SSIZE_T_CLEAN
#include <Python.h>

static PyMethodDef methods[] = {
    {NULL, NULL, 0, NULL}
};

static struct PyModuleDef module = {
    PyModuleDef_HEAD_INIT,
    "foo",
    NULL,
    -1,
    methods
};

PyMODINIT_FUNC
PyInit_foo(void)
{
    return PyModule_Create(&module);
}
EOF
$ python3 -m venv venv
$ . venv/bin/activate
(venv) $ pip install -q setuptools==65.6.0
(venv) $ SETUPTOOLS_USE_DISTUTILS=local python setup.py build_ext --inplace
(venv) $ rm -rf build foo*.so
(venv) $ pip install -q setuptools==65.5.1
(venv) $ SETUPTOOLS_USE_DISTUTILS=local python setup.py build_ext --inplace
running build_ext
building 'foo' extension
creating build
creating build/temp.linux-x86_64-cpython-310
gcc <snip> -c foo.c -o build/temp.linux-x86_64-cpython-310/foo.o
creating build/lib.linux-x86_64-cpython-310
gcc <snip> build/temp.linux-x86_64-cpython-310/foo.o -o build/lib.linux-x86_64-cpython-310/foo.cpython-310-x86_64-linux-gnu.so
copying build/lib.linux-x86_64-cpython-310/foo.cpython-310-x86_64-linux-gnu.so ->
(venv) $

The cause of this behavior seems to be trivial: setuptools.setup() delegates to distutils.core.setup() after first calling logging.configure() and _install_setup_requires(attrs). When distutils.core.setup() is called directly, logging that should be shown isn't.

Hi @godlygeek, please note that newer versions of distutils use the default Python logging infrastructure, so if you don't configure any logging handler, it is very likely the logs are only going to display warnings (see https://docs.python.org/3/library/logging.html#logging.lastResort).
Ideally we encourage every use of distutils that have an equivalent in setuptools to be migrated to setuptools. You can try opening an issue with https://github.com/pypa/distutils, but I don't know to which extent the maintainers would be willing to add a logger handler directly there...


OTP Documentation

Could you please add some documentation on how to configure the OTP? Actually I'm not really sure this is what I think it's (some kind of 2FA), but I'm still curious.
Thank you for a great job, this extension made my day!

Here you go: https://github.com/tadfisher/pass-otp
This extension is only providing a UI for already configured OTP with no extra steps needed. pass-otp is definitely supported, maybe there are other ways to configure OTP as well (I'm not sure).


expand postgres discovery rules

These changes improve the smartagent/postgresql discovery rules to not rely on just the default port and also include a partial metric match that will occur if the receiver can reach a pg instance without having the required extension enabled.

Those changes also impact nginx discovery rules to make the regexp a bit more stringent. Changes look good to me.


[20.09] electrum: 4.0.2 -> 4.0.9

Motivation for this change
Fix https://github.com/NixOS/nixpkgs/issues/99982 .
Things done

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

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

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

@GrahamcOfBorg build electrum

@GrahamcOfBorg build electrum


Simplify endpoint encoding

Issue #, if available:
Closes #179
Description of changes:
Encode destination endpoint with base_url instead of base64.
After this PR has been merged, the ETL artifacts will save into a directory that looks like this:
s3://stack-etl-artifact-123456/amc/dataset_name/P1D/sample_endpoint.execute-api.us-east-1.amazonaws.com/
instead of this:
s3://stack-etl-artifact-123456/amc/dataset_name/P1D/aHR0cHM6Ly9zYW1wbGVfZW5kcG9pbnQuZXhlY3V0ZS1hcGkudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vcHJvZC8=/
T

Enable Integ test workflow, to test this change.


fix launch file name for tiago_nav_bringup

Addresses #34

Hi @david-wb,
I see some extra changes in this PR, could you update it only with the renaming?
Probably you will need to rebase your local repository.
Thanks for the PR!

@Noel215 It's updated but you may want to squash these commits.

How can we pull this request in the terminal because I am new to the VCS imports?

Thanks for the PR!

@kavikode now that this is merged you can use vcs pull to get the latest changes.


Update go.mod to 1.19

Update to using the 1.19 toolchain and run go mod tidy

Project has been updated to Go 1.20


Model types do not get generated correctly when referenced via an array

Sorry, I couldn't get this any simpler, but if you generate this you will see that the model types that are referenced in the array type, do not get generated properly.  They do get emitted as types, but they don't have the property inheritance relationship and they have no properties.
openapi: '3.0.0'
info:
  title: Test
  version: '1.0'
paths:
  "/collection":
    get:
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/itemArray"
components:
  schemas:
    itemArray:
      type: object
      oneOf:
        - $ref: "#/components/schemas/catArray"  # cat does not get properties or base type
        - $ref: "#/components/schemas/dogArray" # dog does not get properties or base type
        - $ref: "#/components/schemas/frogArray" # frog does not get properties
        - $ref: "#/components/schemas/squirrel" # squirrel works
    catArray:
      type: array
      items:
        $ref: "#/components/schemas/cat"
    cat:
      allOf:
        - $ref: "#/components/schemas/animal"
        - type: object
          properties:
            meow:
              type: string
    dogArray:
      type: array
      items:
        $ref: "#/components/schemas/dog"
    dog:
      allOf:
        - $ref: "#/components/schemas/animal"
        - type: object
          properties:
            woof:
              type: string
    frog:
      type: object
      properties:
        croak:
          type: string
    frogArray:
      type: array
      items:
        $ref: "#/components/schemas/frog"
    squirrel:
      type: object
      properties:
        chitter:
          type: string
    animal:
      type: object
      properties:
        name:
          type: string

Union and intersection of array types were excluded from the initial composed types implementation. Or at least this is what I took away from our discussions.
Besides projecting the right types, it poses a lot of challenges during deserialization.
So unless we decide to support that initial exclusion with a thorough implementation spec, I think we should consider all of these edge cases to avoid playing whack a mole.

I think the best thing to do at this point is to take the time to write a proper analysis of what additional vocab we need to do in JSON Schema in order to allow developer to properly communicate how types should be projected.  Until we do that, we shouldn't try and piecemeal solve issues in Kiota.  I just wanted to capture this issue because it showed up in the NightScout API.

@darrelmiller can you please try with the latest preview from yesterday and confirm whether you observe the problem? We've made significant improvements to the handling of allof edge scenarios with #4668 and #4381


helm unable to talk to k2 clusters from within k2 container

Using a stock cluster config as generated by k2cli cluster generate, modified to use k8s v1.5.2 instead of v1.4.4, I can get the cluster to come up, but the heapster and kube-dns services aren't deployed.  Did this via k2cli cluster up
First attempt gave me a cluster with kube-apiserver, kube-controller-manager, kube-proxy, kube-scheduler pods.
Second attempt added tiller-deploy, calico-policy, and canal-node pods.
Second attempt errored out with:
TASK [roles/kraken.services : Install charts] **********************************
failed: [localhost] (item={u'name': u'kubedns', u'namespace': u'kube-system', u'chart': u'kubedns', u'repo': u'atlas', u'version': u'0.1.0', u'values': {u'cluster_ip': u'<IP_ADDRESS>', u'dns_domain': u'cluster.local'}}) => {"changed": true, "cmd": ["helm", "install", "atlas/kubedns", "--name", "kubedns", "--version", "0.1.0", "--namespace", "kube-system", "--values", "/Users/spiffxp/.kraken/spiffxp-k2/atlas-kubedns.helmvalues"], "delta": "0:00:20.657976", "end": "2017-01-17 23:35:31.555674", "failed": true, "item": {"chart": "kubedns", "name": "kubedns", "namespace": "kube-system", "repo": "atlas", "values": {"cluster_ip": "<IP_ADDRESS>", "dns_domain": "cluster.local"}, "version": "0.1.0"}, "rc": 1, "start": "2017-01-17 23:35:10.897698", "stderr": "Error: grpc: the connection is unavailable", "stdout": "", "stdout_lines": [], "warnings": []}

Manual repro from my laptop:
spiffxp@kthxbye:k2 (master)$ docker run -v ~/:/root -it --rm=true quay.io/samsung_cnct/k2:latest /bin/bash
bash-4.3# export HELM_HOME=/root/.kraken/spiffxp-k2/.helm/
bash-4.3# export KUBECONFIG=/root/.kraken/spiffxp-k2/admin.kubeconfig
bash-4.3# helm --debug version
Created tunnel using local port: '44220'
SERVER: "localhost:44220"
Client: &version.Version{SemVer:"v2.1.3", GitCommit:"5cbc48fb305ca4bf68c26eb8d2a7eb363227e973", GitTreeState:"clean"}
rpc error: code = 14 desc = grpc: the connection is unavailable
Error: cannot connect to Tiller

Jenkins doesn't run into this.  @coffeepac and I do.  The main difference I have found thus far is that jenkins is running docker 1.11.x, and we're running docker 1.12.x

Was able to spin up an ubuntu VM with an old (1.11.x) version of docker running.  Worked fine.  Stepped through starting with docker version 1.12.3 up to 1.13.0 and 'helm list' worked every time.
This is a problem with docker for mac, not a specific docker version + helm.

installed docker version 1.13.0 for mac and this was successful.  ran 'k2cli cluster up ...' and kubedns pod was started.

@spiffxp can you please upgrade your local docker install to 1.13.0-stable and see if this works for you?

closing due to inactivity.


Implemented SKCanvas.DrawTextOnPath

Description of Change
Google deleted DrawTextOnPath. This code adds a "polyfill" for it, plus additional options to disable glyph path warping.
Bugs Fixed
Calling DrawTextOnPath threw NotImplementedException

Related to issue #1183

API Changes
List all API changes here (or just put None), example:
Added:

public void SKCanvas.DrawTextOnPath (   		ReadOnlySpan<ushort> glyphs,   		SKPath path,   		SKPoint offset,   		SKPaint paint,   		SKFont font)

public void SKCanvas.DrawTextOnPath (   		SKPath path,   		ReadOnlySpan<ushort> glyphs,   		ReadOnlySpan<float> glyphWidths,   		ReadOnlySpan<SKPoint> glyphOffsets,   		SKPaint paint,   		SKFont font)

public static SKPath SKPath.CreateWarpedTextOnPath (   		SKPath path,   		SKFont font,   		ReadOnlySpan<ushort> glyphs,   		ReadOnlySpan<float> glyphWidths,   		ReadOnlySpan<SKPoint> glyphOffsets,   		float alignment)

public SKTextBlob SKPath.CreatePlacedTextOnPath (   			SKPath path,   			SKFont font,   			ReadOnlySpan<ushort> glyphs,   			ReadOnlySpan<float> glyphWidths,   			ReadOnlySpan<SKPoint> glyphOffsets,   			float alignment)

public SKGlyphWarping SKPaint.GlyphWarping { get; set; }

public enum SKGlyphWarping

Changed:

Obsolete SKCanvas.DrawTextOnPath method accepting IntPtr was removed.

Behavioral Changes
Hopefully none, but Google's original C++ code did a lot more, so most likely this will not be 100% compatible.
PR Checklist

[n] Has tests (if omitted, state reason in description)
[n] Rebased on top of master at time of PR
[n] Changes adhere to coding standard
[n] Updated documentation

Didn't add tests for this yet, but did add a sample program.
Didn't adhere to .editorconfig, see #1197
Didn't rebase on master, since that branch is missing some functionality.
Didn't update documation yet, will be done when this large PR is approved 😉

Also with the docs, we can do that in separate PR because I have to generate it "manually"... I don't think I got it going perfect just yet.

You told me to wait a bit with this PR, you had to fix some things with text alignment.
I am not exactly sure how this impacts this PR, but whenever you think I can make progress on this, please ping.

@Ziriax terribly sorry, that was a separate thing that your PR made me notice while reviewing. Go right ahead with this. Sorry for the confusion.

I think I resolved all requests, but I'm not able to run any unit tests, see #1227.
The PR to fix that doesn't seem to work anymore with the latest changes

Awesome, I'll have a look at all this goodness!
Could I ask that you enable commits to your PR from the contributors? This way I don't have to bother you when merging from master or any trivial changes needed to merge.
https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork
Basically, I'll be able to add a commit to the PR without having to do a PR on your branch.

Awesome, I'll have a look at all this goodness!
Could I ask that you enable commits to your PR from the contributors? This way I don't have to bother you when merging from master or any trivial changes needed to merge.
https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork
Basically, I'll be able to add a commit to the PR without having to do a PR on your branch.

Strange, I can't find the checkbox Allow edits from maintainers anywhere...
I just gave you global write access to the fork, hope that helps for now.

@Ziriax I just want to check before I start reviewing and merging that you are happy with the overall features and functionality at this point? ie: are you working on any local changes?

@Ziriax I just want to check before I start reviewing and merging that you are happy with the overall features and functionality at this point? ie: are you working on any local changes?

Yes, I think it is a good starting point. One extra handy parameter could be an otherSide parameter, that picks the other side of the path. But that can be handled by reversing the path itself. So I think we're okay.
I'm almost ready with the first PR for the image resampler. Thanks for the System.Numerics nuget tip. Would be nice if Microsoft also released a stub package for System.Runtime.Intrinsics that just returned false for every possible SIMD architecture, just avoid having to use #ifdef stuff :)

@Ziriax I can't seem to push to your branch or fork, but I created a PR: https://github.com/smartphoto-group/SkiaSharp/pull/1
Also, I merged in from the "develop"  branch, so after you merge this PR, you can also change the base to "develop". This is the new, official v2 branch for releasing.

I quite liked the FromArrayPool helper you added, so I moved it to the Utils class and then went and changed existing code to use it.
I took the two extension methods and moved it into the respective classes. The one that returns a path went into SKFont alongside the GetTextPath as GetTextPathOnPath. The SKTextBlob one moved into that class as CreatePathPositioned.
I renamed a few members from GetPath to GetTextPath and GetGlyphPath, so now things fit nicely together.

Once you merge that PR, CI can run the last tests and we can merge this in!
Thanks for the work! This brings the backwards compat of v2 to 100% (less the 3 missing color types)

Seems to a bug in Github, I am the owner of the fork, but the ``[x] allow edits from maintainers`  is simply missing. Github seems to think I'm not the owner for some reason. I'll check your PR. I gave you read/write access, but maybe that was not enough, I lifted the permissions to "maintainer"

I merged your PR and changed the base to develop. Thanks for the kind words for FromArrayPool 😉 That was just because I often forget to use a finally. Note that in the old days, the mono compiler didn't like a struct that was IDisposable (I noticed that in Unity3D), the struct got boxed, but maybe that is improved now.

Oh, that is a new feature of C# 8.0!
https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-8#disposable-ref-structs

Oh, that is a new feature of C# 8.0!
https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-8#disposable-ref-structs

Oh, amazing, thanks for the tip! I'm going to take a closer look at your code, I can learn from it.
I haven't been doing a lot of C# the last years, mostly C++ and Typescript, so I have catching up to do 😉

I think this is finally ready to merge! Just waiting on CI and then we will be good to go!


Cann't got same output

I repeated your procedure and found that the results were inconsistent with yours. Although the first mutation is consistent, the other rankings and fitness scores are different.

Please check the model and the code version.
The model and strategy combination in the results is (esm2_t48_15B_UR50D, esm1v_5).
And please check the latest code version in master branch.

If there's no more issues, I'll close this issue, feel free to reopen it!


Reorganize File Structure

Briefly describe the feature or bug that this PR addresses.
Reorganizes file structure.
Please link the Airtable ticket associated with this PR.
N/A
If applicable, include screenshots of the feature/bugfix introduced by this PR (Please include both desktop and mobile if there is a significant UI change).
Describe the steps you took to test the feature/bugfix introduced by this PR.
Local smoke testing
Does this PR depend on any recent backend work? If so, please include the PR number from the iit-backend repo and associated Airtable ticket link.
Does this PR require any French translations? Have they been included?
QA checklist: complete all parts relevant to your ticket changes
Explore

Check Desktop and on Mobile
Summary Stats
Map loads in ~8 seconds with loading spinner
Map has pins
Country Modal - check all fields
Pins modal (check each grade) - check all fields
Filter info bubbles
Select each filter and check options
Execute a Filter for Risk of bias, Sex, and Date.
Check the "Database up to date to:" date
Check each footer item (Privacy policy etc.)

Analyse

Check tableau embed loads and is functional
Check for double scrolling (the embed scrolls within the page)

Data

Click each button
Click a FAQ for functionality
References table embed loads

Check that downloads are disabled.

Data download link provides access to a downloadable CSV.

Download the CSV

"terms of use" button

Publications

Cards all load with images
Carousel is clickable
Try 2 random items on the page for functional links

About

Page loads
Scroll to bottom

Check serotracker.com/broken

404 page loads and animation works

Check serotracker.com/Canada

Check tableau embed loads and is functional
Check for double scrolling (the embed scrolls within the page)
Check in French

Cycle through all pages in French for any glaring omissions

taking this down - will redo once a few big PRs are merged


Fix: Shows star to indicate starred messages(#418)

For #418  .
A star is shown next to messages that user has starred. The alignment is proper with neighboring elements both in landscape and portrait.
Preview Portrait

Preview Landscape

Automated message from Dropbox CLA bot
@nashvail, it looks like you've already signed the Dropbox CLA. Thanks!

Not a fan of the fact we are making the messages narrower.
On small phones this is significant.

Can we only make them narrowed in the event that there's actually a star?  I think that'd be a good compromise.

It would look like a bug, though.

You mean the text wrapping a bit earlier in messages that you starred?  I think it might be possible to do it in a way that doesn't look buggy.

I am going to try making only messages with star slimmer, see if it looks buggy.

I wonder, can we show a dim star as a background of the message?

I'm basically happy with the layout where the star takes up space only if present.  Maybe we should go with that for now and move on.

The thing is, there are at least several structural components added to allow the different structure of the messages. And if we want to keep the star touchable, it better have a 44x44 touchable area (larger than right now) etc.

@borisyankov The reason I put star on right of messages is because any other approach e.g. dim star in background would be a departure from web app's UI.
In my head I am thinking the way messages will be starred will be from an action modal that pops up on long press, and will be unstarred in similar way, from the action modal. If that's the case there's no point in making the star icon larger to accommodate touch. Thoughts?

Yeah, we likely do not want it tappable, but following the main UI people will likely expect to be able to press it.
I become more and more a fan of indicating this somehow, without re-layouting the list.
My top ideas: dim star as background, just some background change (light-yellowish?).

Background color change doesn't make sense, I think -- it's too hard to see that as a "star".  I could imagine doing something with a dim star as the background for some part of the message, though I don't see an easy place to put it.
I feel like we've gotten stuck on trying to optimize beyond the level that makes sense for a feature of this level of importance.  I think we should merge showing the stars soon only if present (and modifying the starred state via longpress), and we can consider trying to optimize the look further for later once we've gotten more feedback from users on this aspect of the mobile experience (e.g. how often do people actually interact with starred messages on mobile).
(As a sidenote, if we're worried about people thinking it'll be touchable, we can just make the star itself touchable with a "long-press to unstar messages" warning that appears if you touch it; with that, we woudln't need a large touchable area.)

@nashvail Let's go with what @timabbott suggests.
I'll comment more on the code, I think just a few changes needed.
Then we merge it and work on other more fun things ;)

I did review the code, but let's wait on the 'Long Press' PR because it conflicts with your code (because I want to put the star inside the 'Touchable')
I'll try to have it merged soon.

@nashvail after you do your chilling for few days that you mentioned, we can work on merging this, now that the long press PR is merged. 🏖

@borisyankov updated the PR. Removed constant from actionConstants.js.

Looks good. Going in.


optimize images - save 59.32%

no problem. That https://imgbot.net/ service is neat. :-)  (i'm not affiliated with it - just discovered it today)


Adding load balancer outputs and exposing ACM ARN as a manual override

Tests aren't passing yet, unfortunately.

Tests are passing now.


Make double Au test more reliable.

In my test environment, the double test fails at least 1% of the time.  I changed an Au test ready condition
to polling in a bash while loop.  I ran the changed test 500 times, and there were 0 failures.  I also
eliminated the "done" temp file, which the current version of the test writes in whatever directory
autest was run from (and doesn't delete it at the end of the test).

Nice tweaks...

This doesn't cherry-pick cleanly to either of these branches. If we want this, please make new PRs for the respective branches, with appropriate "git cherry-pick -x".


_group_count= feature improvements

[ ] The "apply filters" form should keep you on the _group_count= page
[ ] Foreign key references should be expand
[ ] Page title should reflect the view you are on

The single biggest challenge here is expanding foreign key references. This is the blocker that prevents _group_count from being useful at the moment.

From a code point of view, the current mechanism for _group_count makes the TableView even more complicated:
https://github.com/simonw/datasette/blob/446d47fdb005b3776bc06ad8d1f44b01fc2e938b/datasette/app.py#L644-L653
Instead, I think if _group_count is detected we should generate the SQL and then defer to self.custom_sql, like we do for canned queries:
https://github.com/simonw/datasette/blob/446d47fdb005b3776bc06ad8d1f44b01fc2e938b/datasette/app.py#L539-L541

Closing this as obsolete since we have facets now.