Failed run test example

Hello!
I successfully downloaded training data from the official website, and when I trained the model in accordance with the instructions of the tutorial, such errors occurred:
E:\transtate\nmt>python -m nmt.nmt \ --src=vi --tgt=en \ --vocab_prefix=E:\transtate\temp\nmt_data\vocab \ --train_prefix=E:\transtate\temp\nmt_data\train \ --dev_prefix=E:\transtate\temp\nmt_data\tst2012 \ --test_prefix=E:\transtate\temp\nmt_data\tst2013 \ --out_dir=E:\transtate\temp\nmt_data\nmt_model \ --num_train_steps=12000 \ --steps_per_stats=100 \ --num_layers=2 \ --num_units=128 \ --dropout=0.2 \ --metrics=bleu
……
Traceback (most recent call last):
File "D:\ProgramData\Anaconda3\envs\tensorflow\lib\runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "D:\ProgramData\Anaconda3\envs\tensorflow\lib\runpy.py", line 85, in _run_code
exec(code, run_globals)
File "E:\transtate\nmt\nmt\nmt.py", line 495, in
tf.app.run(main=main, argv=[sys.argv[0]] + unparsed)
File "D:\ProgramData\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\python\platform\app.py", line 48, in run
_sys.exit(main(_sys.argv[:1] + flags_passthrough))
File "E:\transtate\nmt\nmt\nmt.py", line 488, in main
run_main(FLAGS, default_hparams, train_fn, inference_fn)
File "E:\transtate\nmt\nmt\nmt.py", line 481, in run_main
train_fn(hparams, target_session=target_session)
File "E:\transtate\nmt\nmt\train.py", line 329, in train
sample_tgt_data)
File "E:\transtate\nmt\nmt\train.py", line 248, in run_full_eval
sample_src_data, sample_tgt_data)
File "E:\transtate\nmt\nmt\train.py", line 162, in run_sample_decode
infer_model.batch_size_placeholder, summary_writer)
File "E:\transtate\nmt\nmt\train.py", line 529, in _sample_decode
utils.print_out("    src: %s" % src_data[decode_id])
File "E:\transtate\nmt\nmt\utils\misc_utils.py", line 66, in print_out
print(out_s, end="", file=sys.stdout)
UnicodeEncodeError: 'gbk' codec can't encode character '\u1ebf' in position 11: illegal multibyte sequence
Log display coding errors, where do I need to change to avoid such errors？Thanks

Are you running on Windows / CMD, as  I am wondering this is because of your default codec is GBK ?
If so, you can try type "chcp" in CMD and the result of 936 stands for GBK.
You can type "chcp 65001" to switch to utf-8 and then re-run the example to see whether the error disappears.
"chcp 936" can switch back to GBK.
Just my 2 cents.

oh, that's good for your answer. But i have meet another problem. I have successfully run the program, but the display in train_log is messy. How can I open the file "events.out.tfevents.1503486266.DESKTOP-K8L49U4" without messy. @bingq


fix: check if the comment exists or not before creating it.

To prevent several messages to be created if a PR is edited, we search for the crawler Id (which is present in the link url) in the previous comments and we don't create another comment in such case.

Tested on https://github.com/damcou/simple-page/pull/4

Looks good.
Can you try to push a commit to your Test PR to see if my comment triggers the early return?

It didn't with the new user check


Fix downloading all user's ebooks

This pull request fixes downloading all user's ebooks - that functionality has been recently broken due to pagination added to user's ebooks page.
It also removes -dc option as agreed in https://github.com/igbt6/Packt-Publishing-Free-Learning/issues/97.
Please, check if that works for you before merging.

thanks! I will test it and merge during the weekend ; )

Any updates?


Example on importing node_module files directly

Clear and concise description of the problem
In my case, I could not get a specific node_module file to import.  I was trying to import node_modules/bootstrap/dist/js/bootstrap.esm.js.
Bootstrap 5.x has good examples on importing scss and JavaScript for vite. Unfortunately the JavaScript import doesn't work in vite-electron. Fyi, the scss import works fine.
I tried the following individually and they did not work for me.
import * as bootstrap from 'bootstrap'
import * as bootstrap from 'bootstrap/dist/js/bootstrap.esm.js'
import { Collapse } from '../../../../../node_modules/bootstrap/dist/js/bootstrap.esm.js'
import { Collapse } from 'bootstrap'
import {Collapse} from 'bootstrap/dist/js/bootstrap.esm.js'
import * as bootstrap from  'bootstrap/dist/js/bootstrap.esm.ts?asset'
import * as bootstrap from 'bootstrap?asset'

I worked around the issue by copying the bootstrap.esm.js file contents into a bootstrap.ts file in the src folder and imported that right into the  renderer/index.html file.  Not the ideal solution.
  <script type="module">
      import './src/bootstrap.ts'
    </script>

Suggested solution
I do not have a suggested solution.
Alternative
I tried the following individually and they did not work for me.
import * as bootstrap from 'bootstrap'
import * as bootstrap from 'bootstrap/dist/js/bootstrap.esm.js'
import { Collapse } from '../../../../../node_modules/bootstrap/dist/js/bootstrap.esm.js'
import { Collapse } from 'bootstrap'
import {Collapse} from 'bootstrap/dist/js/bootstrap.esm.js'
import * as bootstrap from  'bootstrap/dist/js/bootstrap.esm.ts?asset'
import * as bootstrap from 'bootstrap?asset'

Additional context
No response
Validations

[X] Follow the Code of Conduct.
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.

?asset suffix only work in main process


Add unit tests for Bundesanzeiger.__get_response()

As suggested in #125:

Add unit tests for Bundesanzeiger.__get_response() function

Awesome! Thank you.


Updated Documentation and Save/Load Function

I have updated the docs to include some items related to storing data. I have also added the save and load functions into this build.

Closing this for now since @BearDooks suggested he wanted to make some further changes. Please reopen when you've done so, as it's a very useful set of changes.


Scatter plots with trend lines and no overlay variable seem to have lost their legend

The legend was useful for disabling the point data to see the trend line more clearly.
Maybe this was intentional?  Probably not!

Seems the legend has not beed added in scatter plot when there is smooth line and NO overlay variable.

@aaronwlsong Thank you for your tests. I wonder what study you used for the plot? For example, I have tested qa site with GEMS1 case control but it worked just fine as shown in the below screenshot.

Hi @moontrip, I used ELICIT Randomized Controlled Trial. You are right, after I hard refresh my laptop, it shows up. Thanks a lot for letting me know~~! I am gonna close this ticket~~~:)

@aaronwlsong Thank you for your information and quick tests and confirmation! 👍 Sounds great it worked 😃


[ADF]Add SAP Open Hub Message Server Support

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

You don't have permission to trigger SDK Automation.
Please add yourself to Azure group from opensource portal if you are MSFT employee,
or please ask reviewer to add comment *** /openapibot sdkautomation ***.
Please ask<EMAIL_ADDRESS>(or NullMDR in github) for additional help.

Can one of the admins verify this patch?

/openapi pipeline

/openapi pipeline

Close this PR as it has exceeded 3 months, please create a new one if still needed.


Actions in submenu exit to main menu

Describe the bug
When managing Relay, start/restart/logs, exits to main menu.
To Reproduce
Steps to reproduce the behavior:

Manage Relay
Start Relay
Jumps back to main menu
Manage Relay
See Logs
Goto 3.

Expected behavior
Upon exit from Relay operation, the menu should stay in the Relay section, not exit back to main menu.

I don't think that needs to be changed. I like the workflow that it goes back to main menu because you've finished your "managing" and want to see your node status.

The point; is that I have not finished my "managing" and I want to continue, but I am not allowed and forced to "re-manage" every time.
Makes for poor UX and jumping to conclusions


XCombineJars option leads to incomplete header paths

Greetings @tomball!
J2ObjC is producing incomplete header paths when the XCombineJars option is enabled (and this option is always enabled with Bazel - https://github.com/bazelbuild/bazel/blob/f49c1df24df99df97153e02940d7e97202f7b87e/src/main/java/com/google/devtools/build/lib/rules/objc/J2ObjcConfiguration.java#L44
)
This issue starts in version 2.2, and is introduced by this commit - https://github.com/google/j2objc/commit/08308ec278ae08c18e35dd0efe8c1162c30dc0fe.
The issue can be seen in the attached zip file, which contains 3 java classes.  One of the classes BachUpsertCatalogObjectsRequest.java imports another class CatalogModifier.java.
In version 2.1, when I run j2objc (on java 8) via the command:
./j2objc  com/squareup/protos/connect/v2/merchant_catalog/resources/CatalogModifier.java com/squareup/protos/connect/v2/merchant_catalog/service/BatchUpsertCatalogObjectsRequest.java com/squareup/wiremocks/ProtoAdapter.java -d output -XcombineJars
The generated BachUpsertCatalogObjectsRequest.m file imports CatalogModifier.h with the full path with the line
#include "com/squareup/protos/connect/v2/merchant_catalog/resources/CatalogModifier.h"
In version 2.2, running the same command, produces an include statement that does not have the full path:
#include "CatalogModifier.h"
Interestingly, other imports, such as the import for BachUpsertCatalogObjectsRequest.m.s own header file (BachUpsertCatalogObjectsRequest.h) correctly generate the full path in both versions 2.1 and 2.2.
I believe this issue https://github.com/google/j2objc/issues/1030 may also be related.  Thank you in advance for your time!
j2objc-bug.zip

What's weird is that the full path is defined in CatalogModifier.m, just not in BatchUpsertCatalogObjectsRequest.m. Investigating...

The underlying issue is that JavacParser.packageName() wasn't allowing underscores in the package name.

Thanks for the clear test!


Roundup: [oss-security] CVE-2017-5956 virglrenderer: Virglrenderer: OOB access while in vrend_draw_vbo

Here is a vulnerability from the oss-security mailing list
for Vulnerability Roundup 26.
Instructions:
Identification
Identify if we have the software, in 16.09, 17.03, and unstable.
Then determine if we are vulnerable, and make a comment with
your findings. It can also be helpful to specify if you think there is
a patch, or if it can be fixed via a general update.
Example:
unstable: we are not vulnerable (link to the package)
17.03: we are vulnerable (link to the package)
16.09: we don't have it packaged

IMPORTANT: If you believe there are possibly related issues, bring
them up on the parent issue!
Patching
Start by commenting on this issue saying you're working on a patch.
This way, we don't duplicate work.
If you open a pull request, tag this issue and the master issue
for the roundup.
If you commit the patch directly to a branch, please leave a comment
on this issue with the branch and the commit hash, example:
fixed:

release-16.09: abc123

Upon Completion ...

[ ] Update Graham's database

Info
Triage Indicator:
-needs-triage +roundup26 thread:0000000000003b9a # [oss-security] CVE-2017-5956 virglrenderer: Virglrenderer: OOB access while in vrend_draw_vbo

File Search: https://search.nix.gsc.io/?q=virglrenderer&i=fosho&repos=nixos-nixpkgs
GitHub Search: https://github.com/NixOS/nixpkgs/search?utf8=✓&q=virglrenderer+in%3Apath&type=Code

Mon, 13 Feb 2017 10:30:38 +0530 (IST) P J P <ppandit-at-redhat.com>, alpine.LFD.2.20.1702131021590.18948@wniryva
   Hello,

Virgil 3d project, used by Quick Emulator(Qemu) to implement 3D GPU support
for the virtio GPU, is vulnerable to an OOB array access issue. It could occur
when in vrend_draw_vbo.

A guest user/process could use this flaw to crash the Qemu process instance
resulting DoS.

Upstream patch:
---------------
   -> https://cgit.freedesktop.org/virglrenderer/commit/?id=a5ac49940c40ae415eac0cf912eac7070b4ba95d

Reference:
----------
   -> https://bugzilla.redhat.com/show_bug.cgi?id=1421073

This issue was reported by Li Qiang of 360.cn Inc.

'CVE-2017-5956' assigned via -> https://cveform.mitre.org/

Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F

Fri, 24 Feb 2017 11:03:42 +0100 Matthias Gerstner <mgerstner-at-suse.de><EMAIL_ADDRESS>> Upstream patch:
> ---------------
>   -> https://cgit.freedesktop.org/virglrenderer/commit/?id=a5ac49940c40ae415eac0cf912eac7070b4ba95d

Please note that the fix for this issue opens a memory leak, because it
forgets to free the 've' structure from this line:

  ve = calloc(num_elements, sizeof(struct pipe_vertex_element));

A possible follow-up patch is attached.

I've already informed the reporter of this issue but there seems to be
no upstream fix yet.

Regards

Matthias

--
Matthias Gerstner<EMAIL_ADDRESS>Dipl.-Wirtsch.-Inf. (FH), Security Engineer
https://www.suse.com/security

SUSE Linux GmbH
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nuernberg)

signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJYsAT+AAoJEBTEBclxkjVTe9AP/0xe1EuHJdifdk5cQUliPY06
ic9ZQB7P/h8SdCBGmWagOGAldqh+zyAiC3nqJvebIArPARf4i1ayoAPO0xha50bP
YZ5vtQzTvpQ9a3Sle/GoOMtprXGC/0nJvsFT0aaVPxTobU6ffpcC7u/OqW4ngnnO
OvWjK8E6fbelpV+G+/ezCD0xhfHD0Pt4FaGeDycm8F7Xm/01gBJqByZ+4P47W0HA
ZVrmczsmzkt15re8eV9ZLhtfCZ9jcNp1T5qYsgxIM+2QTmDg2ypV13TgWPFZMn5c
nxksfq7tIcbXhgN+N5InXeZdxHQtazM9BkQUIDTJmf4saQ8UAunKZ5skiPXKlP0k
KajL/38WgldHzvnS/5OVlZ4OtM9GGokPgxSFpvlGeyAAosGzoyLmsBVBwWPTTTPO
J5slnAzBZB4j1vpiYekCuQAAJFHjpVarcQG9nJ2Q0temsoJcVvfXj2VZPU8YVcYa
oiyh6Mrxtny4gcP8H6Pu1RodgoqMDVb/2xMli9kl9sURWFNAsVBZpkqDNCRgvA1X
oR5zkwYOvozAdG2kgogpTzrQC2b5L6Q4OcwZ1jnOlvxH4QtUqLA7CoS3je3FTUjv
e+javkUWx0lFSwmSzUAgv4s9ynkRQndq8bPN7WzusaWgahR16VHuExP712+nY1QA
ztItLtLUgK7Ut9nnet3h
=z5+R
-----END PGP SIGNATURE-----

Fri, 24 Feb 2017 13:48:33 +0100 Matthias Gerstner <mgerstner-at-suse.de><EMAIL_ADDRESS>> A possible follow-up patch is attached.

Sorry, forgot the attachment. You can find the patch here:

https://bugzilla.suse.com/attachment.cgi?id=715395

--
Matthias Gerstner<EMAIL_ADDRESS>Dipl.-Wirtsch.-Inf. (FH), Security Engineer
https://www.suse.com/security
Telefon: +49 911 740 53 290

SUSE Linux GmbH
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nuernberg)
On Fri, Feb 24, 2017 at 11:03:42AM +0100, Matthias Gerstner wrote:

signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJYsCuhAAoJEBTEBclxkjVTFykQAMXP29mh6Lotz0/Zwca3crA2
A2X+jzXCgvtH8ZQwGelamMuu8Ae9Jwm7mLgdi8Atipytq0L6azlfQYgv/LkTG/1e
Ldq3LKsm5Mw6NJ/v+s27Se6SGbamDwzSQpLVd/ADdXNkeJyKxRXKIJ65HHPxIYvl
or8Flxa0cc/GDusqW53Y+kYSaduI1nQJNV1YnDRHgwQ/DZwOPfITklspzacs812Y
gdVSC0Zlacr41RGrKuweuc2/NND9rcF6X592MVZ2oaEFqvFCYVJSucRB6MAWLbFH
BN3gSGDpl2Dh7vbAUSNsJ/At4WLInglZOvBp+x5jPJ2NdkV3Rm3NgA6lJfiyM18Q
a1cNCPrKXPjSGmxAhmuMknqVGscBE8lVRMe/j3PwPRW1QDFaQ+kP7gjyOmyjJXdS
nUJElFhefjHFPEPVb3x3YW1o8Nw81ah+I5bWxqSb6By4BWDoc3QH78RlCPpHw2Vw
/fpFboXPcJz6qFF2MFl7shmsiMYU04RGekl6kSrJFEYTBn/08wAKUNS/LIYyt1E7
As21Plaf1MH/+dCIFpbYEDkyVI0/BJGDMmFm3eR3ZuixHjBUqsvYA5oSal4bMnsj
kLG34c/vZidkGZDQMBZtPW8VpBkJPi01VsMlGr4ytKYAMJ+qh76BO7dogsJTwM1w
ua1VJzjEzws/HioWbyfu
=xjWn
-----END PGP SIGNATURE-----

Closing with https://github.com/NixOS/security/issues/24


IGAPP-622: Remove unused libraries

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.

When packages previously were only installed implicitly, they were now added explicitly.

Nice  How did you check which libraries are unused?

depcheck and manual search for those where I wasn't sure


Status of pods can become "OutOfCpu" when many pods are created and completed in a short time on the same node

What happened:
This is a bug introduced with k8s 1.22 which affects EKS images.
What you expected to happen:
Have a patched kubelet to fix the bug.
How to reproduce it (as minimally and precisely as possible):
Issue is explained at length here: Status of pods can become "OutOfCpu" when many pods are created and completed in a short time on the same node
Anything else we need to know?:
A fix is backported for k8s 1.22.9:
https://github.com/kubernetes/kubernetes/pull/108749
Could you please apply it to eks amis ?
Environment:

AWS Region: eu-west-1
Instance Type(s): any
EKS Platform version (use aws eks describe-cluster --name <name> --query cluster.platformVersion): any
Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version): 1.22.6
AMI Version: ami-0808f507c5d46608c
Kernel (e.g. uname -a):
Release information (run cat /etc/eks/release on a node):

Thanks for making us aware of this and providing the details, really appreciate it.
We're working on pulling in several commits on other release lines, so I'll try to get this addressed in that same effort.

team, when it could be fixed?
we are running a lot of jobs each minute, so this cause a lot of pods with such error,
for the EKS version 1.21 we are not facing such issues

As a workaround, we rolled back worker nodes to 1.21 specifying AMI ID in launch template since with 1.22 cluster we can't specify releaseVersion to 1.21 in CreateNodegroup / UpdateNodegroupVersion API .

@mikutas you can specify a release version as it appears in our SSM parameters, e.g. 1.21.6-20220526. More info here: https://docs.aws.amazon.com/systems-manager/latest/userguide/parameter-store-public-parameters-eks.html


Closes #618 (Enable E1121)

I fixed the test failures by just removing the broken example. I propose removing it because:

We shouldn't have duplicated code for the whole cartesian product of different ways of running everything. There's already an MNIST keras tutorial and and MNIST black box tutorial, no need for an MNIST keras black box tutorial.
This was broken (it's a real error, not just a style problem) and no one has noticed, so it's not getting used
It's in the examples directory so there's no obligation to keep supporting it


Prepping for release of Rusoto.

Version bump of the library.
Ran into a gotcha with the mock references: everything including dev deps needs a version specified.

I'm using this as a base for releasing Rusoto right now and will be writing down the process for future use and refinement.

Doh, bumped into https://github.com/rust-lang/cargo/issues/2098 .

Uploading rusoto_marketplacecommerceanalytics v0.25.0 (file:///Users/matthew/Documents/rusoto/rusoto/services/marketplacecommerceanalytics)
error: api errors: invalid upload request: ApplicationError("keywords must contain less than 20 characters")

Gonna yolopublish that one for now. 😄

For future information, publishing the service crates took my laptop about an hour to do.  Yow!

My notes for publishing a new version of Rusoto after crategen:
service_crategen dir: bump version numbers of core and services in services.json.  Example:
"acm": {
    "version": "0.24.0",
    "coreVersion": "0.24.0",
    "protocolVersion": "2015-12-08"
  },

to
"acm": {
    "version": "0.25.0",
    "coreVersion": "0.25.0",
    "protocolVersion": "2015-12-08"
  },

rusoto/core/Cargo.toml: bump version number of Rusoto to new release version.
Root Rusoto Cargo.toml file: bump all version deps (this is for integration tests).
Bump credentials crate version if needed, including the rusoto_core dep in it.
Generate new service implementations: cargo run -- -c ./services.json -o ../rusoto/services in service_crategen dir.
Ensure rusoto_credential will publish: cargo publish --dry-run --allow-dirty in its dir.
Ensure rusoto_core will publish: cargo publish --dry-run --allow-dirty in its dir.
Commit changes.
Publish new versions of rusoto_credential and rusoto_core.
Use the script included in this PR, publish-services.sh, to go into each service crate folder and publish it.
... wow we need to automate more of this. 😄

service_crategen dir: bump version numbers of core and services in services.json.
Should only need to bump versions that actually had changes. For example, the recent flattened list fix could (should) have just been a patch version bump for the affected services.

rusoto/core/Cargo.toml: bump version number of Rusoto to new release version.
Only if there have been changes. Core shouldn't change very often. It doesn't need to keep its version in lockstep with the services. Same with rusoto_credential.


Not Connecting, but no error... ??

hi pulviscriptor,
i have a weird problem....it seems to work normal, but after 'Connecting to (server)' it just do nothing...no error...rly weird - picture of it (waited half an hour):

any ideas to help/fix ? :)

Is it repeating?
Is it working in basic.js?
Do you use proxy/socks?
Can you inspect connections using wireshark / Microsoft Network Monitor to check if there connections made?

@pulviscriptor i do not see any packets from the server (<IP_ADDRESS>:1510) or to the server....but a lot of packets from and to a similiar server ip (annother agar.ioserver ? maybe from the browser ?):

@pulviscriptor edit: the problems is since i changed my server-client communication to class ws (from socket.io)...

@pulviscriptor i think i did it wrong - i get packets from and to the server, but seems to be browser..how can i check if a connection is made ? I use proxies, but high quality ones...even when the proxies would be the problem, i would get an ECONNREFUSED (proxy ip), but not nothing

but seems to be browser..how can i check if a connection is made

Close browser before test?
Since nobody else reported same problem for last 16 hours there is high chance that problem is in your code.
Set client.debug=5; and see what is happens there.

@pulviscriptor it happens nothing...to set the key didn't help:

There is listener for ws.onopen event https://github.com/pulviscriptor/agario-client/blob/master/agario-client.js#L46 which is output message about it https://github.com/pulviscriptor/agario-client/blob/master/agario-client.js#L80
So as i see ws.onopen is never called for some reason.
You need to see it using network analyzer, is there SYN/ACK packet from server or not.
And did you modified ws library?
Also if you use some client.agent it can be reason too.

@pulviscriptor you are right, it is because of the agent, without it works^^....but the agent worked the hole time you have an idea why it doesn't work anymore ??

@pulviscriptor got it fixed, thanks for your help !

@pulviscriptor got it fixed


Updated validations.py python script.

Update validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #1

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Broken links for "Avoiding collisions" in 'Service' and 'Feature Gates' page

This is a Bug Report
Problem:
Links for Avoiding collisions are broken in:

https://kubernetes.io/docs/concepts/services-networking/service/#choosing-your-own-ip-address
https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#feature-gates (at ServiceIPStaticSubrange point)

Proposed Solution:
Update [Avoiding collisions](/docs/concepts/services-networking/service/#avoiding-collisions) in both pages
with [Avoiding collisions](/blog/2022/05/23/service-ip-dynamic-and-static-allocation/)
Other possible solutions:

https://kubernetes.io/docs/reference/networking/virtual-ips/#service-ip-static-sub-range

Page to Update:

https://github.com/kubernetes/website/blob/main/content/en/docs/reference/command-line-tools-reference/feature-gates.md
https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/services-networking/service.md

/language en
/area blog

/retitle Broken links for "Avoiding collisions" in 'Service' and 'Feature Gates' page
/remove-area blog

I think the link became broken during the revision process of the Service concept page. We should make an update to direct it to the correct location, which I believe is https://kubernetes.io/docs/reference/networking/virtual-ips/#avoiding-collisions
/priority backlog
/triage accepted

/assign

/sig docs
PR raised #41847

Similar to #41891


Can't Set Array Value using SQL

Attempting to set the value of an array via SQL does not work.  We are currently using the Document API from Java.
Given the following document:
{
    "someArray": [
        10,
        20,
        30
    ]
}

The following query returns successful, but does nothing
UPDATE model SET someArray[1] = 25

The expected result is:
{
    someArray: [
        10,
        25,
        30
    ]
}

The current work around requires loading the entire array and treading it as a OTrackedList which can then be manipulated and then set back as an entirely new value for "someValue".  This is not practical for large arrays.  The above example was greatly simplified.  The actual use case involves larger arrays that have large objects as their values.
Also, if two users were editing the data such that each was attempting to edit a different value in the array, the approach of getting the whole array, modifying it, and setting it back would create an artificial conflict where none really occurs.
This issue was first discussed in the group here:
https://groups.google.com/forum/#!topic/orient-database/YCSyS7sQKTo

To add more information, we came across another use case that makes this feature more important.  If one has nested arrays, then the amount of data that needs to be loaded is even more, and the efficientcy drops rapidly with the current functionality.
{
    "array": [
        [
           10,
           20,
           30
        ],
        [
           "A",
           "B",
           "C"
        ]
    ]
}

What we would like to do is to update the 20 to be a 25.  If this was just a JSON node I would do the following:
doc[0][1] = 25

Our current workaround for the original use case above was something to the effect of:
String queryString = "SELECT array FROM model";
OSQLSynchQuery<ODocument> query = new OSQLSynchQuery<ODocument>(queryString);
List<ODocument> result = db.command(query).execute(params);

OTrackedList<Object> array = result.get(0).field(FIELD_DATA);
array.set(1, 25);

String updateString = "UPDATE model SET array = :value ";
OCommandSQL updateCommand = new OCommandSQL(updateString);
params.put("value", array);
db.command(updateCommand).execute(params);

This worked.  However, this work around DOES NOT work with nested arrays.  The path to the nested array is "array[0]".  Therefore the code would wind up looking like this:
String queryString = "SELECT array[0] FROM model";
OSQLSynchQuery<ODocument> query = new OSQLSynchQuery<ODocument>(queryString);
List<ODocument> result = db.command(query).execute(params);

OTrackedList<Object> array = result.get(0).field(FIELD_DATA);
array.set(1, 25);

String updateString = "UPDATE model SET array[0] = :value ";
OCommandSQL updateCommand = new OCommandSQL(updateString);
params.put("value", array);
db.command(updateCommand).execute(params);

We are now immediately back to needing to set a value in an array.  So not only do we need to load the entire nested array, modify it an set if back, but now we must also load the entire parent (enclosing array) to set the modified nested array in it.  If one has a data structure composed of nested arrays (which is common when dealing with certain multi-dimensional structures), then one would need to recursively load all the data up to object structure.
A document of three levels of nest arrays, would require loading the entire document to change just one integer value in one of the lowest levels of arrays.
If there is another temporary workaround, that would be great.  Otherwise, just wanted to add some weight to this request.

I am working on a Pull Request for this feature.  Since I have not contributed to this project before, I have signed a CLA and have read the docs on contributing.  I will be starting a PR on the develop branch shortly.

It turns out that that issue is not with the Query Parser or SQL.  The SQL and Query parser handles this just fine.  The issues is actually in the ODocument class, when setting the value of a field.
If you have  a document that looks like this:
{
  "data": {
    "array": [
      1,
      2,
      3
    ]
  }
}

And the rough JAva Code
ODocument doc = new ODocument(...) // From JSON Above.
int valueAtZero = doc.field("data.array[0]");
System.out.println(valueAtZero);

This will print the correct value of 1.  The ODocument.field(String) method correctly parses the fields including the array subscript.  However, the version of field that is used to set (ODocument.field(String, Object)) does not properly parse this.  This rough code does not work.
ODocument doc = new ODocument(...) // From JSON Above.
doc.field("data.array[0]", 5);
int valueAtZero = doc.field("data.array[0]");
System.out.println(valueAtZero);

This will still print 1.  what's more, the document will now look like this.
{
  "data": {
    "array": [
      1,
      2,
      3
    ],
    "array[0]": 5
  }
}

The document now contains a relatively orphaned child element.  The property with the name "array[0]" can't ever be accessed.  Doing doc.field("data.array[0]") will return the value in the array and not this errantly created field.  So there is a disconnect between how the "getter" version of the "field" parses array subscripts and how the "setter" version of the "field" method parses array subscripts.
I have created a gist that demonstrates the issue.
https://gist.github.com/mmacfadden/e0943c5cea2d8a30cf0c
I have a fix for this, that I will be submitting as a pull request.  Once this is fixed, it appears that the UPDATE SQL works as intended.  The relationship is that the updated statement will essentially fetch the ODocument based on the WHERE clause and then set the value of the field using the same "field" method above.  So the entire SQL and UPDATE feature works as it should, and then just gets tripped up by this issue at the last moment.

Updated the pull request, to make keeping up with the upstream sane.

Merged, thanks.


sby: 0.47 -> 0.48

Its tag naming was changed the same as Yosys, so r-ryantm couldn't update it either.
This also gets sby working with Yosys 0.48; I didn't notice it being broken in #368946 because I only ran nixpkgs-review on macOS where sby doesn't build due to broken dependencies anyway. Sorry!

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 369528

x86_64-linux

:fast_forward: 10 packages marked as broken and skipped:

python312Packages.cynthion
python312Packages.cynthion.dist
python312Packages.luna-soc
python312Packages.luna-soc.dist
python312Packages.luna-usb
python312Packages.luna-usb.dist
python313Packages.luna-soc
python313Packages.luna-soc.dist
python313Packages.luna-usb
python313Packages.luna-usb.dist

:x: 2 packages failed to build:

cynthion
cynthion.dist

:white_check_mark: 15 packages built:

glasgow
glasgow.dist
python312Packages.amaranth
python312Packages.amaranth-boards
python312Packages.amaranth-boards.dist
python312Packages.amaranth-soc
python312Packages.amaranth-soc.dist
python312Packages.amaranth.dist
python313Packages.amaranth
python313Packages.amaranth-boards
python313Packages.amaranth-boards.dist
python313Packages.amaranth-soc
python313Packages.amaranth-soc.dist
python313Packages.amaranth.dist
sby

You can additionally put the test programs in the correct input:
diff --git a/pkgs/by-name/sb/sby/package.nix b/pkgs/by-name/sb/sby/package.nix
index ca9687a2e70d..28ee23e1947f 100644
--- a/pkgs/by-name/sb/sby/package.nix
+++ b/pkgs/by-name/sb/sby/package.nix
@@ -19,18 +19,21 @@ in

 stdenv.mkDerivation rec {
   pname = "sby";
-  version = "0.47";
+  version = "0.48";

   src = fetchFromGitHub {
     owner = "YosysHQ";
     repo = "sby";
-    rev = "yosys-${version}";
-    hash = "sha256-Il2pXw2doaoZrVme2p0dSUUa8dCQtJJrmYitn1MkTD4=";
+    rev = "v${version}";
+    hash = "sha256-icOlWutvajHMCi2YUIGU4v5S63YobXw4fYYUvPoSzo4=";
   };

-  nativeBuildInputs = [ bash ];
-  buildInputs = [
+  nativeBuildInputs = [
+    bash
     pythonEnv
+  ];
+
+  nativeCheckInputs = [
     yosys
     boolector
     yices
@@ -40,7 +43,7 @@ stdenv.mkDerivation rec {
   ];

   postPatch = ''
-    patchShebangs docs/source/conf.py \
+    patchShebangs --build docs/source/conf.py \
       docs/source/conf.diff \
       tests/autotune/*.sh \
       tests/keepgoing/*.sh \

The references patched in postPatch will still work.

It would be nice to include the fixes mentioned by @FliegendeWurst but it's not absolutely mandatory. I can wait a bit until merging this to give you a chance to fix it.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 369528

x86_64-linux

:fast_forward: 10 packages marked as broken and skipped:

python312Packages.cynthion
python312Packages.cynthion.dist
python312Packages.luna-soc
python312Packages.luna-soc.dist
python312Packages.luna-usb
python312Packages.luna-usb.dist
python313Packages.luna-soc
python313Packages.luna-soc.dist
python313Packages.luna-usb
python313Packages.luna-usb.dist

:x: 2 packages failed to build:

cynthion
cynthion.dist

:white_check_mark: 15 packages built:

glasgow
glasgow.dist
python312Packages.amaranth
python312Packages.amaranth-boards
python312Packages.amaranth-boards.dist
python312Packages.amaranth-soc
python312Packages.amaranth-soc.dist
python312Packages.amaranth.dist
python313Packages.amaranth
python313Packages.amaranth-boards
python313Packages.amaranth-boards.dist
python313Packages.amaranth-soc
python313Packages.amaranth-soc.dist
python313Packages.amaranth.dist
sby

Seems like nixpkgs-review was working right this time lol


Add multi-stage builds support

This PR adds multi-stage builds support to buildah.
Addresses #440.

@nalind PTAL

Travis CI isn't happy @bertinatto
not ok 13 bud-from-multiple-files-two-froms
# (in test file ./bud.bats, line 51)
#   `cmp $root/Dockerfile1 ${TESTSDIR}/bud/from-multiple-files/Dockerfile1.scratch' failed with status 2

Right, I have a question about this failing test (bud-from-multiple-files-two-froms).
In a multi-stage build, each FROM statement will result in a different stage (i.e., container). I believe this specific test made sense so far, but from now on I'd assume that files added to a stage shouldn't end up in the final stage.
What do you think about this?

I am no expert on this. but isn't multi-stage the equivalent of doing two different Dockerfile, where the second Dockerfile from is from the artifact of the first Dockerfile.  Anything that is in the image created by the first Dockerfile would end up in the second unless it was at some point removed?

@rhatdan Here's an example:
https://github.com/gentoo/gentoo-docker-images/blob/master/portage.Dockerfile
This is all based around the flexibility of needing to use one images utilities to bootstrap the toolchain for another (i.e. - using alpine gpg to validate or busybox to copy/untar).

@rhatdan, AFAIU the idea is that we can selectively copy artifacts from one stage to another, leaving the final image without unnecessary artifacts.
Using the example of #440, the first FROM starts a new stage with the base image golang where the binary grafeas-server is built. The second stage is built using alpine as base image and only the file grafeas-server is copied to it, leaving behind the Go SDK.

Do these workloads work with this patch?

Yup, but unfortunately multi-stage builds support changes the way buildah (and imagebuilder) work with multiple Dockerfiles (i.e.,  multiple FROM statements).

@nalind PTAL

@ipbabble @TomSweeneyRedHat Could you try out a couple of Dockerfiles against this to make sure it works fairly well.
I would like to get this merged along with SHELL Support so we can cut a new version of Buildah.

FWIW, I tested using both of the below Dockerfiles and these worked.  I tried a couple of other more complex Dockerfiles that I found on the net and they had failures, but the same failure happened in Docker too.  I don't believe it was a Buildah issue.  If you've a pointer to other multi-stage Dockerfiles, happy to try them.
FROM ubuntu
RUN whoami
FROM ubuntu
RUN echo hi

and
FROM golang:1.7.3
WORKDIR /go/src/github.com/alexellis/href-counter/
RUN go get -d -v golang.org/x/net/html
COPY app.go .
RUN CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app .

FROM alpine:latest
RUN apk --no-cache add ca-certificates
WORKDIR /root/
COPY --from=0 /go/src/github.com/alexellis/href-counter/app .
CMD ["./app"]

I've been traveling and haven't been able to take a look at this. Sorry.
I've been doing som eof my own testing of complex Dockerfiles.
William Henry
Senior Consulting Software Engineer
Red Hat
Colorado, USA.
On Thu, Apr 5, 2018 at 1:24 AM, Fábio Bertinatto<EMAIL_ADDRESS>wrote:

@nalind https://github.com/nalind, thanks for the review. I'll apply
your suggestions as soon as I have time (probably over the weekend, if
that's not a problem).
@rhatdan https://github.com/rhatdan, will do, thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/projectatomic/buildah/pull/495#issuecomment-378844076,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPpgZe3tN_RcxG5ARGHbCRlQnVwhoAPks5tlcavgaJpZM4SR3Us
.

LGTM pending CI.

I had to close/reopen to retest. All green now.

Thanks!
@rh-atomic-bot r+

Time for a new build?  I think this could be buildah 1.0?  @nalind @TomSweeneyRedHat WDYT

My vote doesn't count, but it would be awesome to have buildah 1.0!

/me being excited! :grinning:


[Enhancement] Codeunit 5005351 Change Parameter in function GetSamePhysInvtOrderLine

Codeunit 5005351 OnRun()
For using own fields in function  GetSamePhysInvtOrderLine
we need to change the parameter.
Instead of calling with explicit fields of record PhysInvtRecordingLine, we need the whole record.

PhsyInvtOrderHeader.GetSamePhysInvtOrderLine(PhysInvtRecordingLine, ErrorText, PhysInvtOrderLine)

Hi there. You can't pass the entire record because the existing parameters are fields coming in different scenarios from different records (e.g. Phys. Invt. Order Line in Codeunit 5886 vs. Phys. Invt. Record Line in Codeunit 5876). There are also scenarios where these parameters are passed from two different records, not just one (e.g. Report 5880).
Could you please provide a bit more detail about why you need the entire record? Is it for filtering on more fields? In case it is, would raising an event to which you could subscribe and perform the filtering be enough? (and not resetting the record in GetSamePhysInvOrderLine method anymore)

Mostly it is for filtering this additional parameter in that functions. Another much better solution would be to add a Directory of type [text, text], that would give us an empty container to inject the additional parameter and we can use it in that described function with a new publisher to set our needed filter in a subscriber on that.
This solution i have written in another issue for "all external functions" as a solution for additional parameter with an example too.
This example could be an easy solution for all parameterproblems we have with standardfunctions.

Please have a look at issue #467

This functionality of part of W1 and therefore I'm closing this request. If something needed, please submit new ask for W1.


Remove Blue Protocol

On AreWeAntiCheatYet, the game Blue Protocol is marked as Broken using EAC with the note "Unreleased, Speculative".
The Japan servers will be closed on 02/18/2025 and the game has been canceled in the West.
So I think we can remove the game from the list.
Proof of mention:
https://www.jeuxonline.info/actualite/64543/blue-protocol-ferme-japon-annule-occident
https://www.jvfrance.com/mmorpg-blue-protocol-annule-et-definitivement-ferme-253321/

Closing this as I've decided we're going to do something with closed/shutdown games. More information here: https://github.com/AreWeAntiCheatYet/AreWeAntiCheatYet/issues/1702#issuecomment-2323512817


[Feature]: Improve error messages when attempting retrieve coords/coord bounds for an axis

Is your feature request related to a problem?
In PR #246, a new method called _get_coord_var() was added, which checks if the supplied axis key can be interpreted using the axis attribute:
https://github.com/xCDAT/xcdat/blob/350ac8b36c8f2e89c63a70b53626cae43cf6b88e/xcdat/axis.py#L327-L355
However, when attempting to retrieve coord bounds, we raise an ambiguous error message if they aren't found:
https://github.com/xCDAT/xcdat/blob/350ac8b36c8f2e89c63a70b53626cae43cf6b88e/xcdat/bounds.py#L179-L183
Describe the solution you'd like
There are several reasons for why coord bounds can't be retrieved (https://github.com/xCDAT/xcdat/pull/164#issuecomment-1150152473):

I plan on opening a separate PR to improve error messages when attempting to fetch coordinate variables or bounds data variables using cf_xarray and CF-compliant  "axis" and/or "standard_name" attributes.
This KeyError is possibly being raised because:

There is no Z coordinate variable
There is a Z coordinate variable, but the "axis" attribute is not set to "Z"
There is a Z coordinate variable and the "axis" attribute is set to "Z", but the "bounds" attribute is not set to the name of the bounds data variable
The bounds data var doesn't exist and need to be added.

We need a clearer error message based on which case is true.
Describe alternatives you've considered
No response
Additional context
No response

@tomvothecoder FYI, the upcoming Python 3.11 release (October 2022) plans to include "Fine-Grained Error Locations in Tracebacks" which looks like a great improvement over 3.10 and earlier. The Exception Groups also looks like a great optimization.
Might be useful to ponder as you're working on this feature
See https://www.python.org/downloads/release/python-3110b3/


Device enrollment stuck

I am trying to enroll an emulator. It starts and then gets stuck and does not complete.
The terminal shows an error complaining it can't find frida_tools. Was I meant to install Frida? I think not... (I do have Frida but in a separate virtual environment).
Reproduce:

Fresh install
Load dexcalibur
Launch an emulator
Go to Device Manager on Dexcalibur, try to enroll

Screenshots

The terminal shows this error:
[INFO] [ADB] /home/axelle/dexcaliburWS/.dxc/bin/platform-tools/adb -s emulator-5554 shell getprop
Traceback (most recent call last):
  File "/home/axelle/.local/bin/frida", line 7, in <module>
    from frida_tools.repl import main
ModuleNotFoundError: No module named 'frida_tools'
Error: Command failed: frida --version
Traceback (most recent call last):
  File "/home/axelle/.local/bin/frida", line 7, in <module>
    from frida_tools.repl import main
ModuleNotFoundError: No module named 'frida_tools'

    at checkExecSyncError (child_process.js:635:11)
    at Object.execSync (child_process.js:671:15)
    at Function.getLocalFridaVersion (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/src/FridaHelper.js:144:22)
    at Function.installServer (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/src/FridaHelper.js:299:27)
    at DeviceManager.enroll (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/src/DeviceManager.js:570:37)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/src/WebServer.js:622:38 {
  status: 1,
  signal: null,
  output: [
    null,
    <Buffer >,
    <Buffer 54 72 61 63 65 62 61 63 6b 20 28 6d 6f 73 74 20 72 65 63 65 6e 74 20 63 61 6c 6c 20 6c 61 73 74 29 3a 0a 20 20 46 69 6c 65 20 22 2f 68 6f 6d 65 2f 61 ... 134 more bytes>
  ],
  pid: 326915,
  stdout: <Buffer >,
  stderr: <Buffer 54 72 61 63 65 62 61 63 6b 20 28 6d 6f 73 74 20 72 65 63 65 6e 74 20 63 61 6c 6c 20 6c 61 73 74 29 3a 0a 20 20 46 69 6c 65 20 22 2f 68 6f 6d 65 2f 61 ... 134 more bytes>
}

Desktop:

OS: Linux Mint 20
Node JS version: 12.20.0
Dexcalibur version (see 'package.json' or output) : 0.7.3

Device information:

Device: Emulator
Android version: Android 8.0 x86
Not rooted

If I install frida, it works.
Except, later when I am trying to hook my APK I get this error (though I saw a log before that where frida-server was being downloaded and installed to the emulator). Not sure if this is a related bug or a different one.
[INFO] [WEBSERVER] Start hooking [app=tuna.obvious.trust, type=spawn-self]
[Error: Unable to connect to remote frida-server: closed]
error: Unable to connect to remote frida-server: closed

Hello,
sorry for this late reply.
First issue happens when host-side frida binaries (frida-ps, frida, ...) cannot executed by Dexcalibur (spawn). During enrollment, Dexcalibur push a compatible frida-server server binary into the device. In this case, Dexcalibur starts by executing "frida --version" on the host to gather the local Frida version,  and to avoid issue with frida-server version.
Second issue occurs because frida-server is not started, cannot be started by dexcalibur, or cannot be reached. With Android emulator, if you successfully enrolled your device, you should be able to enumerate installed through "Select an application" menu. Most of users connect Android emulator over TCP.

Ok -- is that a bug of Dexcalibur, a missing requirement, or am I normally meant to install Frida by hand on the host?

I installed the suspicious app on the emulator, and enumerated  it fine. When I ask to analyze it, I get the following error. FYI, yes, Android emulator  is over TCP.

[INFO] [APK HELPER] APK extracted into : /home/axelle/dexcaliburWS/tuna.obvious.trust/apk
Error: [CONNECTOR] Unknown connector : undefined
    at ConnectorFactory.newConnector (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/src/ConnectorFactory.js:60:19)
    at DexcaliburProject.setConnector (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/src/DexcaliburProject.js:193:57)
    at /home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/src/WebServer.js:419:29
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

On (1) I believe this is just a doc issue : the main page, README.md, does not say to install Frida. But https://frenchyeti.github.io/dexcalibur-doc/Installation-guide says to install frida-tools + apktool. Just need to know which is the most up to date doc :)

Yes, you are right on (1). My documentation is out dated, and not mention version ! Apktool is now "installed" by dexcalibur. Current requirements are only : nodeJs,  frida tools (on host), and java. Other requirements are downloaded by dexcalibur into dexcalibur workspace during first.
Another thing is the latest release on GitHub != NPM. Sorry for that.
In fact, i fully rewrote Dexcalibur and fixed lot of things into new version, however this new version (v1.0) is not yet released. I would like to release it mid-january.
About connectors issue, it's a blocking issue. I will patch it today.

Thanks :)


Fix o2o field clone in related relation

Related o2o fields should also be able cloned, see test cases.

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

In the file model_clone/mixins/clone.py:

Line 322:1: W293 blank line contains whitespace

In the file model_clone/tests/test_clone_mixin.py:

Line 64:101: E501 line too long (101 > 100 characters)
Line 75:1: W293 blank line contains whitespace

In the file sample/migrations/0010_backcover_cover.py:

Line 18:101: E501 line too long (114 > 100 characters)
Line 20:101: E501 line too long (110 > 100 characters)
Line 30:101: E501 line too long (114 > 100 characters)
Line 32:101: E501 line too long (110 > 100 characters)

Thanks @yuekui moved your changes to #267 and fixed the bug can create a new PR to work of the current default branch if there are still issues.

Thanks @yuekui moved your changes to #267 and fixed the bug can create a new PR to work of the current default branch if there are still issues.

Great! Thanks @jackton1


Modrinth version catchup

Is it possible for you to put your latest versions on modrinth? especially since it seems that you have used to

Here they are https://modrinth.com/mod/animal_feeding_trough/versions :D


fix shared_preload_libraries in extension update test

I spent some time cleaning up our CI in #1340 and picked up this change as well. Thanks!


Sets supported JDK range explicitly to 11-17

Before, we were using an implicit version of the JDK when releasing, had the pom.xml limited to a non-LTS version (15), and had the docker images and README tests set to 17.
This consolidates the version range status quo to floor of 11 and ceiling of 17. A later change can extend that ceiling to the latest LTS version 21.
While at it, this corrects CI to use latest versions of tools including updating to the latest ubuntu runner 22.04.

draft until green


fix: make secondaries' network less intrusive

Signed-off-by: Mykhaylo Sul<EMAIL_ADDRESS>

@Raigi It would be great if you verify this PR on RPi within your office's internal network and see if it works (just bitbake Primary and Secondary with a default configuration and check if Primary gets current date/time and update works on Secondary)

@mike-sul With the office network and default configuration

Primary got current date > Mon Feb 10 11:46:05 UTC 2020
Installing an update on both Secondary and Primary was successful

@mike-sul With the office network and default configuration

Primary got current date > Mon Feb 10 11:46:05 UTC 2020
Installing an update on both Secondary and Primary was successful

@Raigi Thank you


InitFromBundle() only get hit once because ViewModels get cached

When using navigation paramaters to load ViewModels/Views the system won't work because it caches the first created ViewModel, so at the second run to the same View it uses the old ViewModel without looking at possibly new navigation parameters at InitFromBundle(IMvxBundle parameters).

What's your exact use case (using the classes that are already in the sample)? This is a full fragging example, so you only have the one activity and everything else is a fragment. MainActivity is meant to be the only activity. Does that make sense? If I am missing something, please write out what you're trying to do and then what is actually happening, step by step

I used your exact example, but then added InitFromBundle() to your ViewModels to check if they get hit.
An example use case could be;

Open the Mailing list page
-> a list of mails is displayed
Open a Mail X by tapping
-> A new Fragment gets loaded, and the Mail ID get passed to this Fragment with normal ViewModel navigation of MVVMCross
The mail gets closed by navigating back
-> again you see the list of mails
Open Mail Y by tapping
-> The first ViewModel is cached and will be recycled, InitFromBundle won't get hit, Mail X gets displayed || but you realy need to see Mail Y

Ahh. Gotchya. Thanks for clearing that up. I have not taken this example that far yet.

I'm working\trying out almost the same example as yours, but then with 4.0.3 support and above.
My main goal is to work with Fragments with tombestoning, navigation etc.
I considering to start a new git repository..... but first I have a question why you choose to support only 5.0 and above? (maybe I'm missing something)

@Toine-db as you can see here this project currently support from Api level 19: https://github.com/steffkelsey/Xamarin_MvvmCross_MaterialDesign/blob/master/MvxMaterial.DroidFullFrag/Properties/AndroidManifest.xml#L3
This could be put down to api lvl15 which is 4.0.3 without any problems. The real problems could come when ChildFragmentManager is going to be used, because that is not supported before Android 4.2.

@Toine-db I'm currently only interested in API level 19 and above. My current large projects are all BLE projects where 19 is our min. Because of that, I am not really interested in supporting below level 19 in any of my other projects/examples/etc. You're more than welcome to fork it or sue whatever you want from this stuff.

@martijn00 thanks, I will try doing that and maybe 4.3 will be the minimum because of security reasons and my projects...
@steffkelsey Thanks for the info, I will try some different scenario's. I will let you know.
And for your ViewModel thing (this issue), I  think I fixed it with renewing the ViewModel when the Fragment is comming from cache...
In your Caching activity: (needs some cleaning, the ViewModel loading can be extracted)
// if we haven't already created a Fragment, do it now
if (fragInfo.CachedFragment == null)
{
fragInfo.CachedFragment = Fragment.Instantiate(this, FragmentJavaName(fragInfo.FragmentType),
bundle);
}
else
{
// renew ViewModel
var mvxFragment = fragInfo.CachedFragment as MvxFragment;
if (mvxFragment != null)
{
IMvxSavedStateConverter savedStateConverter;
//IMvxMultipleViewModelCache viewModelCache;
IMvxViewModelLoader viewModelLoader;
                if (!Mvx.TryResolve(out viewModelLoader))
                {
                    Mvx.Trace("Could not resolve IMvxViewModelLoader, won't be able to load ViewModel for caching");
                    return;
                }

                if (!Mvx.TryResolve(out savedStateConverter))
                {
                    Mvx.Trace("Could not resolve IMvxSavedStateConverter, won't be able to convert saved state");
                    return;
                }

                var mvxBundle = savedStateConverter.Read(bundle);
                mvxFragment.ViewModel = viewModelLoader.LoadViewModel(request, mvxBundle);
            }


Fixed #34565 -- Added support for async checking of user passwords.

Add acheck_password method and its unit tests. This method will call the async setter function to update the password field of the user table when the settings.PASSWORD_HASHERS is changed.

@felixxm Hello, I implemented the acheck_passport document by referring to the document in the ORM section. I previewed the document after making changes and saw a green line appearing in front of some paragraphs. I want to ask if I need to try another way of writing?

@felixxm Hello, I implemented the acheck_passport document by referring to the document in the ORM section.

I'm not sure what acheck_passport() has to do with the ORM :thinking: Please submit doc updates and we will review.

I previewed the document after making changes and saw a green line appearing in front of some paragraphs. I want to ask if I need to try another way of writing? (Sorry, I have some problems here, I will upload pictures as soon as possible.)

There is no need to upload pictures, just submit doc changes and we will review.

In addition, regarding the release document, which version of the document should I write in? 4.2.2 or 5.0?

5.0

@felixxm Hello, I implemented the acheck_passport document by referring to the document in the ORM section.

I'm not sure what acheck_passport() has to do with the ORM 🤔 Please submit doc updates and we will review.

I previewed the document after making changes and saw a green line appearing in front of some paragraphs. I want to ask if I need to try another way of writing? (Sorry, I have some problems here, I will upload pictures as soon as possible.)

There is no need to upload pictures, just submit doc changes and we will review.

In addition, regarding the release document, which version of the document should I write in? 4.2.2 or 5.0?

5.0

Ok, thanks for your patient reply, I will upload the document as soon as possible

@HappyDingning Thanks :+1: Welcome aboard :boat:
I pushed small edits.

@HappyDingning Thanks 👍 Welcome aboard ⛵
I pushed small edits.

Thanks a lot for helping me optimize my code.😊 I will check for checks failure issues as soon as possible

Thanks a lot for helping me optimize my code.blush I will check for checks failure issues as soon as possible

No need, this test is flaky,

Thanks a lot for helping me optimize my code.blush I will check for checks failure issues as soon as possible

No need, this test is flaky,

Thank you very much for your review


nbdev_preview Mermaid doesn't work

I was exited by https://quarto.org/docs/authoring/diagrams.html
Graphviz plot work with NBDev, but not Mermaid plot.
How to reproduce
copy-paste the sample from Quarto in a fresh nbdev v2 project:
'''{mermaid}
flowchart LR
  A[Hard edge] --> B(Round edge)
  B --> C{Decision}
  C --> D[Result one]
  C --> E[Result two]
'''

(replace quote by back-quote)
Run nbdev_preview
Expected result
The page display the plot.
Actual result
The page display the code of the plot.
There is an error in the browser console:
Uncaught ReferenceError: mermaid is not defined
    <anonymous> http://localhost:3000/site_libs/quarto-diagram/mermaid-init.js:21

But I could see the library http://localhost:3000/site_libs/quarto-diagram/mermaid.min.js is loaded.
Versions used
nbdev: 2.1.1
Quarto 1.0.37

Thanks for reporting this.  I've tested this and it works with the current version of Quarto.  Can you try upgrading?


Inline packaging does not work

When I try to use inline package referencing as described here:
https://github.com/filipw/dotnet-script#inline-nuget-packages
it doesn't work.
> usingAutomapper; (1,1): error CS0103: Der Name "usingAutomapper" ist im aktuellen Kontext nicht vorhanden.

@TFTomSun
Could you issue the following command
dotnet script --info

also, why is there no space, and why is the M not capital? it should be using AutoMapper;

ah sorry, i copied the wrong error message. I'll update the post. But the issue is there.

ah yes, it was the M in the using. But when i try to reference the latest package it doesn't work. Its somehow confusing. There seem to be issues. For example this script can't restore the package:

ah yes that was indeed a typo. But there are issues:
here are some bash scripts:
works:
dotnet-script <<- EOF Console.WriteLine("Hello"); Console.WriteLine("World"); #r "nuget: AutoMapper, 7.0.1" using AutoMapper; typeof(MapperConfiguration).Assembly.FullName System.Threading.Thread.Sleep(10000); Environment.Exit(0);    EOF
fails:
dotnet-script <<- EOF Console.WriteLine("Hello"); Console.WriteLine("World"); #r "nuget: AutoMapper, [*, 9999]" using AutoMapper; typeof(MapperConfiguration).Assembly.FullName System.Threading.Thread.Sleep(10000); Environment.Exit(0);    EOF
with:
error CS0246: Der Typ- oder Namespacename "AutoMapper" wurde nicht gefunden (m▒glicherweise fehlt eine using-Direktive oder ein Assemblyverweis).

It works on my machine.
@TFTomSun
could you do a dotnet script --info so that we know what version and environment we are dealing with here ?

Version             : 0.26.1
Install location    : C:\Users\adfrth5.dotnet\tools.store\dotnet-script\0.26.1\dotnet-script\0.26.1\tools\netcoreapp2.1\any
Target framework    : netcoreapp2.1
.NET Core version   : 2.1.4
Platform identifier : win
Runtime identifier  : win10-x64

can you confirm that this script works for you?:

dotnet nuget locals all --clear
dotnet-script <<- EOF
Console.WriteLine("Hello");
Console.WriteLine("World");
#r "nuget: AutoMapper, [*, 9999]"
using AutoMapper;
typeof(MapperConfiguration).Assembly.FullName
System.Threading.Thread.Sleep(10000);
Environment.Exit(0);
EOF


Setting camera bounds to projection.visibleRegion is not identity transformation

Describe the bug
Triggering a camera update which sets the camera bounds to projection.visibleRegion moves the camera up.
To Reproduce
To see the effect, I have added a loop that keeps doing this operation on the most basic map from the sample Android app:
diff --git a/platform/android/MapboxGLAndroidSDKTestApp/src/main/java/org/maplibre/android/testapp/activity/maplayout/SimpleMapActivity.kt b/platform/android/MapboxGLAndroidSDKTestApp/src/main/java/org/maplibre/android/testapp/activity/maplayout/SimpleMapActivity.kt
index 55f4265c6..9c41edc25 100644
--- a/platform/android/MapboxGLAndroidSDKTestApp/src/main/java/org/maplibre/android/testapp/activity/maplayout/SimpleMapActivity.kt
+++ b/platform/android/MapboxGLAndroidSDKTestApp/src/main/java/org/maplibre/android/testapp/activity/maplayout/SimpleMapActivity.kt
@@ -24,6 +26,14 @@ class SimpleMapActivity : AppCompatActivity() {
                     val styleUrl = styles[0].url
                     maplibreMap.setStyle(Style.Builder().fromUri(styleUrl))
                 }
+
+                maplibreMap.addOnCameraIdleListener {
+                    maplibreMap.moveCamera(CameraUpdateFactory.newLatLngBounds(
+                        maplibreMap.projection.visibleRegion.let {
+                            LatLngBounds.fromLatLngs(listOf(it.farLeft!!, it.farRight!!, it.nearLeft!!, it.nearRight!!))
+                        }, 0
+                    ))
+                }
             }
         )
     }

For full diff including imports, see cf8f6db58c46109e48efdcf5d6bfcb416abbd173 from https://github.com/e-foundation/maplibre-gl-native/tree/demo-wrong-transformation.
With this modification:

the camera keeps moving upwards
the camera does wrong transformations if it is pitched or zoomed
possibly additional conditions trigger wrong transformations

Expected behavior
The described transformation should be equivalent to the identity transformation.
Screenshots
https://github.com/maplibre/maplibre-native/assets/16943720/e936f4f2-c8a3-4e21-bd34-068955056cf9
Platform

Android
(other platforms not tested)

Additional context
For some reason, one app using microG is pretty much doing the loop described above and we would like this app to work.

Any idea what causes this? Does it also happen when the map is full screen?

No, I don't know the cause. First I suspected it might have to do with different calculations regarding earth curvature, but this seems to have no influence on these calculations (a polygon would render as a square, and we are just specifying the four corner points anyway, not the entire area). Whether it happens with a full screen map, I have not tried, but I suspect that the renderer is indifferent about this.


Examine why our NUTS sampling works better with blocked parameters

@hriebl and I noted that, sometimes, our NUTS sampling works better with separate kernels working on blocks of parameters. That seems strange to us, because according to our current understanding, NUTS benefits from sampling multiple parameters at once, because their interdependence can be taken into account.
Our current hypothesis is that our warmup scheme may be to blame. In this issue, we will analyse the behavior of our warmup scheme to determine whether there is a problem.

Meeting Notes:

Also relevant (BDA 3, p. 305):

Hi @hriebl, I created two baseline examples in https://github.com/liesel-devs/nuts-tests:

https://github.com/liesel-devs/nuts-tests/blob/main/qmd/001-simple-liesel-model.qmd
https://github.com/liesel-devs/nuts-tests/blob/main/qmd/002-nonlinear-liesel-model.qmd

In both cases, sampling runs slower when one NUTS kernel covers all parameters.
In case 1, I have to say that the estimated parameters seem really weird to me. They do not seem to recover the true model at all.  Maybe I just don't see what is wrong there at the moment...


Bug: Unable to run isotope cli on OSX

Issue: isotope cli throws an exception.
> brew install isotope-rs/homebrew-isotope/isotope
==> Tapping isotope-rs/isotope
...
🍺  /usr/local/Cellar/isotope/0.0.8: 5 files, 7.3MB, built in 24 seconds

> RUST_BACKTRACE=full RUST_BACKTRACE=1 isotope analyze -a s3

██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████ 1/0thread 'tokio-runtime-worker' panicked at src/utils/mod.rs:9:45:
called `Result::unwrap()` on an `Err` value: NotPresent
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread 'main' panicked at src/analyze/mod.rs:121:39:
called `Result::unwrap()` on an `Err` value: RecvError
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

The aws cli is configured properly.
> aws s3 ls
2020-05-07 15:50:27 aws-cloudtrail-logs-XXXXXXXX-XXXXXXXX

The environment variables are configured as per README
> env | grep BEDROCK
BEDROCK_REGION=eu-central-1
BEDROCK_MODEL=anthropic.claude-v2

More details about my local environment:
> aws --version
aws-cli/2.13.26 Python/3.11.6 Darwin/22.5.0 source/x86_64 prompt/off

> uname -a
Darwin memons-MacBook-Pro.local 22.5.0 Darwin Kernel Version 22.5.0: Mon Apr 24 20:51:50 PDT 2023; root:xnu-8796.121.2~5/RELEASE_X86_64 x86_64

> arch
i386

> sw_vers
ProductName:		macOS
ProductVersion:		13.4
BuildVersion:		22F66

Thanks for this, can you please test whether you get the same results when using an individual analyzer?
isotope analyze -a s3

Let me know what that yields please

Yes, the same error with an individual analyzer.

I was going through the code and found the issue, it was failing because AWS_REGION env variable was not set and the code expects it. If not set, could it default to us-east-1? or maybe loop over all regions?
https://github.com/isotope-rs/isotope/blob/635539a230cd4df2e97c9596d187b9f835891526/src/utils/mod.rs#L9
I feel this should be added to the README. It's a fairly small change, let me know if you would be ok with a PR for this :)
Btw, there is another issue now. When I ran the sg analyzer, there was no advice even though it says security group is insecure.
> AWS_REGION=us-east-1 RUST_BACKTRACE=full RUST_BACKTRACE=1 isotope analyze -e -a sg -j

████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████ 1/0Running Security Groups analyzer
{
  "sg": [
    {
      "message": "Insecure security group: sg-xxxxxxxxxxxx",
      "analyzer_name": "sg",
      "advice": ""
    }
  ]
}

I also stumbled upon the same issue with the mission region when was playing with the tool!

Thanks both, I appreciate your helpfulness - This is in the readme, but I think we need to make an explicit check in code
export AWS_REGION="" ( e.g. eu-west-2 //wherever your VPC is )


TST: stats: ReferenceDistribution: use complementary methods when available

Reference issue
gh-18449
gh-18433
What does this implement/fix?

gh-18449 added an _sf override to the TruncExpon reference distribution. It would be nice if calling cdf would use it (and take the complement) rather than integrating the pdf, right? This enhances the ReferenceDistribution infrastructure accordingly.
gh-18449 added an _sf override because "The PDF was not enough". It was not enough because _support needed to be defined. This adds _support to the TruncExpon reference distribution and documents when it needs to be defined.
In gh-18433, I suggested preferring defining multiple test cases in a single vectorized test rather than using parametrization for several little reasons:

The vectorized approach is (ever so slightly) faster.
The vectorized approach is (ever so slightly) less ugly.
(most importantly) The vectorized approach is easier to review.

The last suggestion was not accepted in gh-18433, but I think it's important enough to push for it. To review tests written like this, we just need to add the imports, copy-paste the arrays, and write some simple code like StudentT(df=df).logpdf(x) - logpdf_ref (or copy-paste snippets from the comments). Seeing that the results are zero confirms that the author copy-pasted the reference values faithfully (which cannot be taken for granted). This is easier than the alternatives when the tests are parametrized.
Parametrized tests absolutely have a place, but for the reasons above, I think vectorized tests should be preferred (where possible) when testing distribution accuracy. If there is no strong reason to maintain the status quo, let's use the most appropriate style for the job at hand.

I will be traveling for the rest of the month without laptop, so cannot help much with further reviews until the 1.11 release.

Please take a look when you return @dschmitz89; it's relevant to all the distribution method PRs.


Document support for Externalizable in the configuration cache

Fixes: #28461

The merge queue build has started. Click here to see all failures if any.


Stand in Line

Challenge Stand in Line has an issue.
User Agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

function nextInLine(arr, item) {
  // Your code here
  arr.push(item);
  arr.shift([0]);
  return item;  // Change this line
}

// Test Setup
var testArr = [1,2,3,4,5];

// Display Code
console.log("Before: " + JSON.stringify(testArr));
console.log(nextInLine(testArr, 6)); // Modify this line to test
console.log("After: " + JSON.stringify(testArr));

@dungtran211096 Can you please provide more information regarding this issue

@dungtran211096 your code is incorrect. Please review how to use the .shift() method. If you get stuck with a challenge, please first ask questions to the Help Room. Happy coding!


Improve Kubernetes Manifests

Amazing ingress service! Thanks for the implementation 😊
As a first contribution, some tweaks and fixes in the Kubernetes manifests.
See the list of commits for more details.

Thank you for the improvements! :+1:


Root doc part table is added by default on collection creation

Current coverage is 16.24% (diff: 0.00%)

Merging #141 into devel will decrease coverage by <.01%

@@              devel       #141   diff @@
==========================================
  Files           735        735
  Lines         26344      26360    +16
  Methods           0          0
  Messages          0          0
  Branches       2801       2802     +1
==========================================
  Hits           4283       4283
- Misses        21762      21778    +16
  Partials        299        299

Powered by Codecov. Last update 1733e4d...0c28909


Allow init

I'm trying to create auto generated typehints/ stubs for Parameterized classes.
A part of this is autogenerating the signature of __init__ method.  Lets use the Pipeline of Panel as an example.
A simplified version of this is defined as
class Pipeline(param.Parameter);

    show_header = param.Boolean(default=True)
    next = param.Action(default=lambda x: x.param.trigger('next'))

A simplified stub for this would look like
class Pipeline(param.Parameter);

    show_header: bool=True
    next: Callable=...

    def(show_header: bool=True, next: Callable=...):

The problem here is that we probably don't want next included in __init__. But with param we have no way to indicate and know this.
Solution
Add an argument allow_init. Its True by default on any parameter. But if you set it to False and its provided to __init__ it should raise an error.
Additional Context
constant serves a purpose which is close to allow_init. But you can set a constant parameter in the __init__.

Ahhh readonly is what I have been looking for.
I've never really understood readonly and I gave up on it some time ago. Should look at it again.

Right; readonly is like constant, but can't be changed on an instance even in the constructor.


adding mesoamericana university

followed instructions in order to add Mesoamericana University located in Guatemala.
Reference Link: http://mesoamericana.edu.gt/

@brxyxn First stage of verification passed, official domain is mesoamericana.edu.gt as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@brxyxn Thank you for your patience while waiting for a review and processing your request. Pull request merged.


[Infra] Get testing tag from latest tag merged to main

#no-changelog
Fix #13048

Fixing the NOTICE generation in a robust way looks to be a little more complex. I'll send a simple fix.


Switching formats when switching desktops

First of all, thanks for this extension! This is only a minor issue, but still: when I switch desktops with a key combination, the format switches from parsed to raw, because the combination includes arrow keys. Feature request: check to see if any control keys (Ctrl, Shift, Meta, Alt) are pressed on the arrow key event.

I came here to post this because I started using virtual desktops and their keyboard shortcuts this afternoon and noticed this issue. And as it turns out, you came 8 hours earlier!!! 😮


[BUG] coq-thirdparty is missing acceptKey option and string cases don't match with example

Field
Description

Plugin
coq-thirdparty

Nixpkgs
unstable

Home Manager
unstable

Description
In the example listed under plugins.coq-thirdparty.sources, there are two errors:

acceptKey is not handled by nixvim
shortName is actually short_name

Minimal, Reproducible Example (MRE)

programs.nixvim = {
  plugins.coq-nvim.enable = true;
  plugins.coq-thirdparty = {
    sources = [{
      acceptKey = "<c-f>";
      shortName = "COP";
      src = "copilot";
    }];
  };
}

We are using a freeform type for the sources, so you should be able to add any keys you want like. Though I think we lack some documentation on freeform types, we need to improve in that regard.


Add error callback for showStep (Issue #274)

Calling showStep without a proper step target fails, but the tour error
callback is not invoked. This change fixes that, and sets the current
step number to the step that failed for debugging purposes
I'm getting a different error in my codepen example (used in the issue report) related to the 'bubble_default' template, so I wasn't able to test this. I do have this fix in a client code-base however, and that is working fine.
This may be imperfect, if so I apologize. Just thought I'd try to get this in for the maintenance release if possible.

1 test failed. =(
Lemme take a look and see what it's complaining about...

Gah! Sorry for the bad PR. Can definitely remove that bit, but will be slightly less clear if the callback is returning the failed stepNum. Not a deal-breaker though.
Shall I refactor and resubmit? I'm not sure what the protocol is here. Thanks for taking a look!

Hmm, fair point. So, maybe it would make sense to optimistically set currStepNum, then revert currStepNum back on failure (after calling invokeEventCallbacks()). This behavior is consistent with goToStepWithTarget(), except in that case we keep stepping forward until we find a valid step (which is not intended when we call showStep at present).
You can leave this PR open. Go ahead and push a new commit to the feature branch you have open at present. The commits on a PR branch will get squashed when they're merged to master.

Yep, sorry about that- still getting used to some of this. Am trying to test now, had to install node etc. but now I understand why I was getting the error in my codepen example.

Ok, checked this back in here; all tests passing for me locally, and my codepen example is working correctly. Thanks!

Cool, this PR is looking good to me. Just commented with one minor nitpick... once that's fixed, I'll mark this as Ready to Merge. I'll pull this in tonight or tomorrow. Thanks!

No problem! I should have thought of that; too focused on making sure I built it properly to observe good code style. Thanks for catching that.


allow callback or userCallback in the time scale

Fixes #2494

Coverage increased (+0.01%) to 75.276% when pulling 3e63bb63ae5071e6998f623753649a641d060806 on fix/2494 into c276926c14a0f37e71f29f810e66354d7fca1e62 on master.


[0.9.6] How to create a map with roadrunner in which pedestrians can navigate on roads and pavements?

Hi Carla team!
I am very new to Carla and my project requires pedestrian walking on roads, but the current pedestrians in carla only navigate on pavements. I am not sure how the pedestrians navigation works but I roughly understood from other threads that it's somehow related to the meshes in the  maps, so I was wondering if I can create a new map from roadrunner and allow the functionality for pedestrians to navigate on roads as well as pavements.
Thanks in advance!

Hi @bernatx , could you give me some hints for this problem?

Hi Siqi-Wang47,
current version only has a basic navigation system for pedestrians. The navigation is based on a binary file created from the Recast&Detour library with all the information about where the pedestrians can walk.
You can check this issue where some instructions and experiences are given: https://github.com/carla-simulator/carla/issues/1899
I hope it helps.


Incompatibility with Calico eBPF Mode When Transitioning from kube-proxy + IPVS Mode

Issue Description:
When attempting to switch from kube-proxy + IPVS mode to Calico eBPF mode with Calico version 3.26.4 and Kubernetes version 1.22.0, the host becomes instantly inaccessible. Any attempt to access <IP_ADDRESS> on the host results in the error message "ping: sendmsg: Operation not permitted."
However, switching from kube-proxy + iptables mode to Calico eBPF mode does not exhibit any issues.
Query:
Is the current implementation of Calico eBPF mode incompatible with transitioning from kube-proxy + IPVS mode?
Your prompt attention to this matter would be appreciated.

// Check if current felix ipvs config is correct when felix gets a kube-ipvs0 interface update. // If KubeIPVSInterface is UP and felix ipvs support is disabled (kube-proxy switched from iptables to ipvs mode), // or if KubeIPVSInterface is DOWN and felix ipvs support is enabled (kube-proxy switched from ipvs to iptables mode), // restart felix to pick up correct ipvs support mode. func (d *InternalDataplane) checkIPVSConfigOnStateUpdate(state ifacemonitor.State) { 	ipvsIfacePresent := state != ifacemonitor.StateNotPresent 	ipvsSupportEnabled := d.config.RulesConfig.KubeIPVSSupportEnabled 	if ipvsSupportEnabled != ipvsIfacePresent { 		log.WithFields(log.Fields{ 			"ipvsIfaceState": state, 			"ipvsSupport":    ipvsSupportEnabled, 		}).Info("kube-proxy mode changed. Restart felix.") 		d.config.ConfigChangedRestartCallback() 	} }
When kube-proxy uses ipvs mode, that is, when kube-ipvs0 exists, switching to ebpf mode will cause felix to restart indefinitely.

If I remove the kube-ipvs0 interface, the calico-node pod can be ready

@pf2rich We don't support moving to eBPF mode from IPVS. For now the path forward is to move to kube-proxy iptables mode and then switch to eBPF.


Determine road geometry before path geometry

I think Road and Intersection and the first pass of building and transforming a StreetNetwork should be vehicle centric. Not because cars are more important or because osm2streets should aim to support them better, but because roads and adjacent infrastructure are designed first to influence the behaviour of the bigger, faster road users.
The shape of the roadway is designed to communicate what cars should be doing, with curbs following smooth lines to match the driving lines and stuff like that. When other road users are prioritised in the design, this is achieved by routing the other users around the car infrastructure, or changing the path that the cars take (and thus changing the shape of the road).
If we know where the cars go, we can predict where the curbs are (or should be) and thus where the pedestrians go. This might hold more true in some places (like where I live in Perth) than others, but I think the model is the best way to construct shapes anyway.
Bikes complicate the matter a bit, but I think about it as three tiers: Car, Bikes then Pedestrians. Pedestrian infrastructure often fits around dedicated bike infrastructure in the same way it does around car infrastructure. And bike infrastructure sometimes fit around car infrastructure in the same way. But sometimes bikes are treated as part of vehicle traffic (such as bike lanes), which complicates things a bit.
In fact think about railways: They are a tier higher than cars. That is, the shape of a railway tracks isn't determined by any roads, bike paths or footpaths; trains are gonna train, and everyone else is gonna respect that. Instead, features of the railway are going to be positioned to leave enough room for the other tiers to fit around it, but those railway features will be represented in the railway data. This is the idea I'm seeing with roads vs pedestrians.
Actionable takeaways
The "road width" should be the width of the whole carriageway (or both carriageways plus the median) "curb to curb". The "center" of a road should be the center of that width. This matches up with the OSM definition (as best as I can tell; we'd have to do a survey to confirm that mappers place the way at the center of the road width instead of the dividing line, when those don't coincide).
Road trimming and intersection shapes should be calculated by looking just at vehicle lanes. Paths should then be stuck on the side of road shapes. In the first instance, I think A/B street will just need to adjust where geometry is positioned (with then help of a width() and total_width() probably). Eventually, footpaths around intersections could be calculated with a shift operation.
The intersection kind calculation already looks at only driving traffic. (As a consequence, only driving movements are calculated. Bike movements will need to be calculated at some point, and maybe factored into Kind in some way.)
Thoughts?
Does this tiered approach make sense to you? Or are there implementation details that I'm glossing over that render the idea unhelpful? Does the idea of defining "road width" and "center" relative to the curbs, not the edge of the footpaths sound ok?

Road trimming and intersection shapes should be calculated by looking just at vehicle lanes.

Nitpick: More specifically, it should ignore non-vehicle lanes on the outer sides of the road. Sometimes a cycle lane is in the middle of the regular paved road (like when a turn lane is the outermost lane, and the cycle lane isn't). I feel I've also seen some kind of exotic footpath in the middle of a road before, or at the very least, when we zip parallel roads together, boulevards with center paths on grass medians, we might see this.

Does the idea of defining "road width" and "center" relative to the curbs, not the edge of the footpaths sound ok?

I'm warming up to it after understanding your point in #130. It feels like it adds complexity to the data model and API. It would make lane_specs_ltr less easy to understand geometrically, since some of the outer lanes would be special-cased. I guess nothing stops us from writing curb_to_curb_width(), right_of_way_width(), get_left_curb() -> PolyLine, etc. It would also make non-driveable roads more confusing, because some of these definitions wouldn't make any sense. But that needs to happen already for some cases.
I guess I don't yet see what the advantages to this shift in thinking buy us yet. The intersection geometry routine could also be the one place that handles this special case of only matching up the outermost vehicle lanes for calculating trim.

This matches up with the OSM definition (as best as I can tell; we'd have to do a survey to confirm that mappers place the way at the center of the road width instead of the dividing line, when those don't coincide).

I believe what untrimmed_road_geometry is doing with sidewalks is trying to account for this, based on some examples I checked in OSM (and didn't comment...). We can pick the simplest representation to work with internally, and map whatever's in OSM to that. So, maybe this could make sense

Thanks for your input.

The intersection geometry routine could also be the one place that handles this special case of only matching up the outermost vehicle lanes for calculating trim.

I am definitely convinced now that we should implement helpers to work with the curb-to-curb "roadway" while leaving the actual representation alone. It sounds like you've understood the general thrust of the idea, and incorporating it into the geometry calculation code in isolation sounds like the best way to explore further.
I'm right in the guts of implementing the shifting logic for the placement which is one place curb-to-curb is relevant. The incoming placement PR will let us explore this in context. Here is an introduction to that particular can of worms:
Keeping the untrimmed, unshifted geometry as the source of truth, and reapplying the placement gets more difficult when we have zipped together multiple roads. Maybe we can use the concept of "curb-to-curb roadway" in the early stages of the process (for placement shifting and trim calculations), then switch to treating the trimmed geometry as the source of truth before we do certain transformation like zipping. The zipping transformation would then need to update the trimmed geometry properly, instead of updating the untrimmed geometry.
Maybe we go for a Corridor type that represents a list of adjacent Roads so that we can keep the scope of a single Road smaller (similar to Junction vs Intersection). If we're trying to represent a big boulevards as a single Road then it feels like we need to treat the median area as a special case. But if the median is wide enough, with winding paths, benches etc, it feels like working with two Roads and letting the median be a normal "non-road" area might be easier. Depends how median handling turns out I suppose. I'm worried about being forced to merge Intersections that shouldn't be merged, that sort of thing...

Right, the question of Corridor and Junction goes back to earlier questions about whether we should try to merge the raw/primitive Roads and Intersections together, or add additional structure and abstraction on top. This also feels relevant in the dog-leg PR conversation. I'm still not sure the right approach, and it almost feels early to figure it out... the cycleway snapping transformation barely works.
It sounds like your work with placement will reveal more info about the pain of working with current assumptions. Maybe it'd also be worth trying to group/label corridors and junctions without any attempt to merge or transform them yet. That'll give us more understanding about what raw data the lowest layer should store and about any difficulties maintaining it during more complex operations.


Send coverage reports to codecov.io

Sends coverage reports to codecov.io
Removes run_tests script as it looks like go test ignores vendors directory when Go Modules are used.

Close #1686.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@31321a3). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1701   +/-   ##
=========================================
  Coverage          ?   45.14%
=========================================
  Files             ?      381
  Lines             ?    25760
  Branches          ?        0
=========================================
  Hits              ?    11629
  Misses            ?    12955
  Partials          ?     1176

Continue to review full report at Codecov.

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

Thanks for a comment. I was thinking about some tweaks like removing a notification comment (see above) and including only a set of packages in the report. However, I'm going to merge it in the current form so the team is aware of this. We can update the configuration later.


config file wasnt created when i loaded the plugin

config file wasnt created when i loaded the plugin

Dependency repository issue, user made aware, will be fixed for next release.

Dependency repository issue, user made aware, will be fixed for next release.


match contains throws error if compare arrays with different length()

Hi all,
I'm trying to use match contains to validate 2 objects which consist of arrays but would get error if arrays have different length
Here is sample script:
* def obj1 =
"""
    {
      "attr1": "value1",
      "key2": "value5",
      "array1": [
      {
        "key1": "value1"
        }
      ]
    }
"""

* def obj2 =
"""
    {
      "attr1": "value1",
      "attr2": "value",
      "key1": "value4",
      "key2": "value5",
      "array1": [
      {
        "key1": "value1",
        "key2": "value2"
        }
      ]
    }
"""

* match obj2 contains obj1

Execute this script will throw following error:
path: $.array1[0], actual: {key1=value1, key2=value2}, expected: {key1=value1}, reason: [path: $.array1[0], actual: {key1=value1, key2=value2}, expected: {key1=value1}, reason: actual value has 1 more key(s) than expected: {key2=value2}]

Using karate version 0.9.4

requesting help-wanted, also see #826 where we support nested maps, but probably missed arrays
for those who want hints for a fix please see https://github.com/intuit/karate/commit/0072a909b40d763811a8ec699e540a300b164f31

@limbtz hey wait a minute: are you saying that this should work ?
* def obj1 = [{ "key1": "value1" }]
* def obj2 = [{"key1": "value1", "key2": "value2" }]
* match obj2 contains obj1

I am really not sure about that - so I consider this low priority and will wait for you or anyone else to step up and attempt a fix

I can give it a shot @ptrthomas, @limbtz if you guys don't mind...

@guptaatit94 all yours 👍

@limbtz hey wait a minute: are you saying that this should work ?
* def obj1 = [{ "key1": "value1" }]
* def obj2 = [{"key1": "value1", "key2": "value2" }]
* match obj2 contains obj1

I am really not sure this should be the wanted behavior. I personally would expect this to fail, and I think it would really be counter-intuitive.

agree with @MercierAdrien
@guptaatit94 you have the option to stop working on this unless @limbtz is able to make a strong case. it goes without saying that all existing test-cases should work if anyone attempts a fix for this

@ptrthomas I'll wait for @limbtz to respond before starting to work on it...

Thanks @ptrthomas and @guptaatit94 for the responses.
I guess it's quite similar to #826 where the actual has more keys than the expected, and in this case where I'm validating the response object against the update object, and there are differences within arrays inside the response's object.
Not sure what you guys mean by counter-intuitive when validating keys of 2 arrays with different length, could you guys explain a bit? Thanks.

@limbtz as @MercierAdrien said - I personally feel this is too much of a stretch that maps within arrays that are clearly not-equal will be treated as equal . I'm going to close this given that in 2.5 years this has never been reported as an issue. so @limbtz if you do want to see this happen, please contribute a fix (or convince someone to), all the needed info is above. cheers

re-opening.
@abhi-rao - thanks for the contribs in #1080 - if you see line 331 in this commit:
https://github.com/intuit/karate/commit/dadb40277be5167e71ea851b38cd1d7199c2d0c1#diff-1ff5507f3412188862236b7e9e67e8c3R331
I was wondering if * match original !contains deep compared should work, do have a look when you have time

@ptrthomas I think it should work, and the same probably should go for other extensions of contains to have parity.

0.9.6 released


Automatically install extension when it gets activated by the lsp

when the client lets the server autocomplete one of the hx-ext="{extension}" and the header is specified in the current tree, add the script source to it.
ex. Add
<script src="https://unpkg.com/htmx.org/dist/ext/event-header.js"></script>
to the header when the extension is completed using the lsp:
<button hx-ext="event-header">
   Click Me!
</button>

I like the idea of supporting quasi "auto imports" but don't think that adding a script tag to the head is the answer. Now my personal usage of htmx is purely script tags in <head>, but htmx also supports npm-like imports and I'm sure there are other people who want to lazy load extensions. This behaviour would probably annoy a certain subset of users.
We could support an "informational" code action on the extension usage if we don't see the extension imported in the head, but I also think that would raise a bunch of false positives (once again when other loading strategies are used). I like the idea, but am not sure how to eliminate annoyance.

In that case it doesn't seem like the best way. Maybe a code action (or multiple) when hovering around the hx-ext tag?

Can you have code actions that don't raise 'errors'.


[Temporary fix found] SyntaxError: unqualified exec is not allowed in function '_add_offset_to_slice' ...

When trying to import numba after having installed numba from source (v0.36.1) using pip ( installed using command pip install git+https://github.com/numba/numba.git#egg=numba ) on a virtualenv environment ( created using command virtualenv env in the folder named Numba_venv ), I encountered the following error:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/samir/Numba_venv/env/lib/python2.7/site-packages/numba/__init__.py", line 12, in <module>
from .special import typeof, prange
File "/home/samir/Numba_venv/env/lib/python2.7/site-packages/numba/special.py", line 4, in <module>
from .parfor import prange
File "/home/samir/Numba_venv/env/lib/python2.7/site-packages/numba/parfor.py", line 25, in <module>
from numba import stencilparfor
File "/home/samir/Numba_venv/env/lib/python2.7/site-packages/numba/stencilparfor.py", line 544
exec(f_text, {}, loc)
SyntaxError: unqualified exec is not allowed in function '_add_offset_to_slice' it contains a nested function with free variables
Ignoring this and trying import numba once again produced:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/samir/Numba_venv/env/lib/python2.7/site-packages/numba/__init__.py", line 9, in <module>
from . import config, errors, runtests, types
ImportError: cannot import name config
There doesn't seem to be any circular imports, and so I can't understand the second error. However, the first error seems to be (from what I found) a python version issue (since my python version in the virtualenv is 2.7.8) which i read here.
Finally, installing the earlier version 0.35.0 ( using command pip install<EMAIL_ADDRESS>) fixed the issue.
Would love to know what really caused both errors,
Thank you!
EDIT: My sincere apologies if this issue isn't related to numba, I'll delete/close it myself.

Is this Linux 64-bit?

Looks like it is hitting python issue 21591.   The python bug is fixed in 2.7.9.

Yes @seibert, I run it on a:
64-bit Ubuntu 14.04 (14.04.5 LTS Trusty)
gcc/g++ 4.9.4
clang-5.0.1-svn319952-1~exp1 (branches/release_50)
llvm-5.0.1
pip freeze returns:
enum34==1.1.6
funcsigs==1.0.2
llvmlite==0.21.0
numba==0.36.1
numpy==1.13.3
singledispatch==<IP_ADDRESS>
six==1.11.0


New provider, scanner and cache manager to interact with grype

This PR builds on the refactor in https://github.com/anchore/anchore-engine/pull/1000  and introduces a new vulnerabilities provider for grype-integration. It also introduces

a scanner that can generate a grype sbom from engine artifacts and transform grype output into engine report format
a cache manager to load and retrieve vulnerability reports for images

Commits in this PR are a subset of https://github.com/anchore/anchore-engine/pull/973. Merging this PR into the integration branch without an explicit approval


ani-cli installs mpv even if mpv-git is installed

Bug Report
Package Name: ani-cli
Current Behaviour

installing ani-cli installs mpv but i have mpv-git which is already configured and is available as mpv in PATH
Expected Behaviour

mpv-git gets accepted as a dependency as it is almost identical to mpv
Additional context/output

line 10 in ani-cli.json having mpv as a dependency
Possible Solution

i'm not knowledgeable on scoop packages so i'm not entirely sure if that is possible but basically checking if either mpv or mpv-git and depending on which ever is already available
if that is not possible maybe it can not have mpv as a dependency at all and add a simple note to install mpv (or mpv-git)
System details
Windows version: 10
OS architecture: 64bit
PowerShell version: 7.2.2
Additional software:
Scoop Configuration

{
  "lastupdate": "2022-03-23T06:52:51.5882149+02:00",
  "SCOOP_REPO": "https://github.com/lukesampson/scoop",
  "SCOOP_BRANCH": "master",
  "aria2-warning-enabled": false
}

Please make a PR to make mpv a suggest instead of depends