xdt-vhive module authentication

The xdt-vhive module breaks (1) container builds and (2) go mod download
Logs:
(1) https://github.com/ease-lab/vSwarm/runs/6060750238?check_suite_focus=true#step:5:174
#17 [builder 8/9] RUN go mod tidy
#17 sha256:4f6cb49384556377e5104c8dfab05b6072043e959c6646f5bd61c203be40524d
#17 2.512 go<EMAIL_ADDRESS>invalid version: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /go/pkg/mod/cache/vcs/9a55d04d66b40bef8fcfb41f84ee0a31b34b74f38389df85a9774f7df3d7887b: exit status 128:
#17 2.512 	remote: Invalid username or password.
#17 2.512 	fatal: Authentication failed for '***github.com/ease-lab/vhive-xdt/'
#17 ERROR: executor failed running [/bin/sh -c go mod tidy]: exit code: 1
------
 > [builder 8/9] RUN go mod tidy:
------
executor failed running [/bin/sh -c go mod tidy]: exit code: 1

(2) https://github.com/ease-lab/vSwarm/runs/6180720496?check_suite_focus=true#step:4:29
Running [/home/runner/golangci-lint-1.45.2-linux-amd64/golangci-lint run --out-format=github-actions --path-prefix=./benchmarks/chained-function-serving --timeout 5m] in [/home/runner/work/vSwarm/vSwarm/benchmarks/chained-function-serving] ...
  level=error msg="Running error: context loading failed: failed to load packages: failed to load with go/packages: err: exit status 1: stderr: go<EMAIL_ADDRESS>invalid version: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /home/runner/go/pkg/mod/cache/vcs/9a55d04d66b40bef8fcfb41f84ee0a31b34b74f38389df85a9774f7df3d7887b: exit status 128:\n\tfatal: could not read Username for 'https://github.com/': terminal prompts disabled\n"

This line authenticates to the github for accessing private repo. And this is failing on github runners. Github has changed their authentication scheme. Refer to this for reference.

Harshit can you pleas look into that next week


404 on criteria links

On the home page, under contents, the criteria links go to a 404

The links are going to
https://standard-for-public-code.github.io/criteria/code-in-the-open.html

instead of
https://standard-for-public-code.github.io/standard-for-public-code/criteria/code-in-the-open.html

I checked the liquid and can't quite spot why
* [Criteria](criteria/){% assign sorted = site.pages | sort:"order" %}{% for page in sorted %}{% if page.dir == "/criteria/" %}{% if page.name != "index.md" %}{% if page.title %}
  * [{{page.title}}]({{page.url}}){% endif%}{% endif%}{% endif%}{% endfor %}

also works fine locally :thinking:
so not a jekyll issue, but the github pages build omitting the /repo/ from the url for some reason?

I remember similar issues before. Perhaps a baseurl in _config.yml would help? I think we did that with https://github.com/publiccodenet/publiccodenet-url-check/blob/main/_config.yml

Curious - I tried this locally and it added the baseurl to all the others links, except these criteria listed on the homepage

Could it have anything to do with the
scope:
      path: '/criteria/*'

in_config.yml?

If I'm not mistaken, that should only be saying "for all that have /criteria/* path, show the previous and next"
https://jekyllrb.com/docs/configuration/front-matter-defaults/

With a bit of inspiration from you both @Ainali @clausmullie it should be fixed in the https://github.com/standard-for-public-code/standard-for-public-code/pull/1038


Haxe autocompletion not working for classes in the same project, in ST2

Autocompletion used to work for me for these typical cases:

instance. -> would show public variables and functions
Class. -> would show public static variables and functions

But I noticed it stopped working in the past week or so. I had recently upgraded all Haxe libraries using haxelib upgrade, and some of them were indeed upgraded but I don't remember which ones exactly.
I've tried uninstalling the Haxe bundle via Sublime Text package control, and reinstalling it, but it didn't help. Any ideas on how to get it to work again? Thank you!

To clarify a bit more, ST2 is indeed able to find the classes when I'm instantiating a new instance or calling the class directly, and it knows where they are located. Just the public variables and functions can't be found anymore.

Do you get any error message in the ST console ?
Most people now use ST3, including myself, so ST3 support is much better than ST2. You may want to upgrade too.

I've upgraded to ST3, but I still don't have the autocompletion.
No error messages appear in the ST console. I would expect it to show something when I hit the . for fetching (or failing to fetch) things for autocompletion, but nothing appears at all.

I'm on Mac OS X 10.9.5, in case that helps.

Still no error messages in the ST console, but I noticed in the status bar it says "Class not found : lime.Assets" when I'm typing, including after pressing the .

Then it's very likely a duplicate of #175

Yes, adding the lime dependency allows autocompletion to work again! Thank you :)
I'll close this one and add a comment to that other issue that it was affecting me too.


Error When Using Comparison Operators Between Untyped Objects

When applying comparison operators (e.g., =, <>) between two untyped objects, a check error is returned.

This is intentional.  Ideally, we want to steer away from untyped and towards stronger typing.
Don't say:
U1 < U2
Instead say:
Value(U1) < Value(U2)
We will coerce if one of the args is known.
U1 < N1


Module/raid registering

Description
Adding the back end support for the Raid event registration
Checklist

[ ] Created tests which fail without the change (if possible)
[ ] All tests passing
[ ] Extended the documentation, if necessary

Quick note: please be careful when using get_file_from_data() and save_file_as_data() 😉
Comment says: WARNING: **NEVER** trust user input when calling this function. Always check that parameters are valid.
Currently, your document_id is directly controlled by the user. As it is, it would be a major security flaw.

Yes, this is just a placeholder, the function done are tagged with Tags.raid for now

We need to merge https://github.com/aeecleclair/Hyperion/pull/510 fisrt


Explore serverless separate packaging option in serverless.com

https://www.serverless.com/framework/docs/providers/aws/guide/packaging#packaging-functions-separately

Closed by #273.


Vendr uSync Umbraco V10 support?

Tried to use it on V10 but it didn't work.
I'll try to spend some time to see what's wrong and where but thought it'd be good to keep it as an issue here too :)

Hi @busrasengul There is a new 3.0.0 RC on our unstable feed at https://nuget.outfield.digital/unstable/vendr/v3/index.json if you want to give this a try?


PowerShell alias calling non-existent command returns 0 exit code

Running an alias using the Powershell shell plugin with rez-env doesn't return a failure exit code when attempting to run a non-existent aliased command in-line.
Environment

Windows 10
Rez 2.112.0
Rez python version 3.7.9

To Reproduce

Create a package.py for a test_invalid_alias package with the following definition:

name = "test_invalid_alias"

version = "1.0.0"

build_command = ""

def commands():
    alias('my_alias', 'a_non_existent_executable')

Install the package to your package repository.
Run rez-env -- a_non_existent_executable
Observe the following error message:

& : The term 'a_non_existent_executable' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Users\bryce.gattis\AppData\Local\Temp\rez_context_2bfjto0k\rez-shell.ps1:4 char:3
+ & a_non_existent_executable
+   ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (a_non_existent_executable:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Run rez-env test_invalid_alias -- my_alias
Observe $LASTEXITCODE as being 0 instead of a non-zero exit code.

Use Case
This is currently happening and causing issues on our render farm. With Rez, we are creating aliases for python that map to whatever the DCC's version of python is. For example, the python alias for Houdini maps to hython.
The behavior observed via this issue is problematic when a specific machine doesn't have the correct version of Houdini installed on their machine. Rez will still use the alias (and expect that the corresponding software is installed where the Rez package is looking for it), but will not correctly return a non-zero exit code if the executable is not found.
This causes false positives on our render farm.
Related Issues/PRs

Added failing test in #1801

Expected behavior
A non-zero exit code is returned.
Actual behavior
A 0 exit code is returned.

I had similar problem exposing commands like nuke as an alias for Nuke15.0 etc
The aliases don't seem to propagate any error codes (so even if the command starts, but say it fails mid-render - then farm monitoring software doesn't notice the job failed)
I ended up replacing all aliases with .bat scripts, e.g our nuke.bat contains:
@echo off
"%~dp0\nuke\Nuke15.0.exe" %*

and so on, and these get added to $PATH instead of using Rez's alias(...)
Wrapper scripts like this are slightly less convenient to setup, but they seem a lot more robust - e.g even in bash, aliases have some weird properties which makes them a flaky solution for this problem (mainly they don't get inherited into child shells - so if you did rez env mypackagewithanalias -- my_alias would work but rez env mypackagewithanalias -- bash -c 'myalias' would fail)


Raise error on unknown exit code from diff-pdf

What it does: Raises an error if the exit code from diff-pdfwasn't 0 or 1.
Why: This prevents a fail-silent error where it may seem like the pdf's wasn't matching, but there was actually a problem running diff-pdf.
Background: When running in Docker, I was troubleshooting why I had a diff, and no diff file was generated, when I discovered that the libraries required to run diff-pdf were missing which resulted in an exit code of 127.
Implemented solution: Check the exit code, and if it's not 0 or 1, then raise an error.
Other notes: I am now redirecting stdout and stderr to /dev/null, as it's unexpected behavior to get stdout spam directly from diff-pdf (and this actually happens in the test case, which is why I discovered it).
I tried to be helpful by adding changelog and version bump, but please let me know if I should change this.
My first Ruby PR ☺, hope it's useful!
Thanks!

I have released v2.1.0.
https://rubygems.org/gems/pdf_matcher/versions/2.1.0


Logging

The logging branch standardizes how input vs. debug information is displayed to the user. @marcandrew-choi @oliven-n please check out the changes in Vivan's code and see if any of them seem wrong or will break something you wrote

looks good

There is an issue in the log.debugLog function I think (100% my fault) I
can merge this into main tonight. I think someone else needs to click
approve pull request on the github first tho?
On Tue, Jun 25, 2024 at 4:24 PM Marc Andrew Choi @.***>
wrote:

looks good
—
Reply to this email directly, view it on GitHub
https://github.com/Jpickard1/RAG-DEV/pull/1#issuecomment-2189905577, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEDRP66XV5AAWIRPBGD5S7LZJHGZJAVCNFSM6AAAAABJ4GIPZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBZHEYDKNJXG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
University of Michigan
@.***<PHONE_NUMBER>


Add more certificate information into prometheus metrics

Is your feature request related to a problem? Please describe.

Almost all certificates we have are managed by cert-manager and I want to build a Grafana dashboard using the Prometheus data source to list all ingresses that aren't managed by cert-manager.
Describe alternatives you've considered

List all ingresses using the kube_state_metrics kube_ingress_annotations metric that don't have a cert-manager annotation.
Describe the solution you'd like

Since the Certificate CRD resources are managed by cert-manager, I think a good way to provide more useful information for this type of monitoring would be to expose some new data about the Certificate CRD's (dnsNames, issuerRefName, secretName, etc) either by:

Exporting a new metric (something like certmanager_certificate_info) with this data
Adding this data into already existing metrics certmanager_certificate_expiration_timestamp_seconds, certmanager_certificate_renewal_timestamp_seconds, certmanager_certificate_ready_status

Additional context

If I had the secret name of the Certificate CRD into the cert-manager metrics, I could compare the kube_state_metrics kube_ingress_tls metric with the cert-manager metric and find out all the secrets that are referenced by a ingress and are NOT referenced by cert-manager (thus finding out all certificates that aren't managed by cert-manager).
I think exposing this data would be a great addition to the metrics exported by cert-manager and would be very useful to a lot of people.
Environment details (remove if not applicable):

Kubernetes version: v1.27.10
Cloud-provider/provisioner: Bare Metal
cert-manager version: v1.13.3
Install method: e.g. helm/static manifests: idk

/kind feature

Thanks @gbassinello

I want to build a Grafana dashboard using the Prometheus data source to list all ingresses that aren't managed by cert-manager.

Given that problem, I prefer your alternative suggestion, but I'm happy to change my mind if that turns out not to be viable.

List all ingresses using the kube_state_metrics kube_ingress_annotations metric that don't have a cert-manager annotation.

I tried it out locally
EDITOR=vi kubectl edit -n prometheus deployments.apps default-kube-state-metrics

    spec:
      containers:
      - args:
        - --metric-annotations-allowlist=ingresses=[cert-manager.io/issuer,cert-manager.io/cluster-issuer],secrets=[cert-manager.io/certificate-name]

kubectl get --raw /api/v1/namespaces/prometheus/services/default-kube-state-metrics:8080/proxy/metrics | grep annotation_cert_manager_io

kube_ingress_annotations{namespace="default",ingress="example-1",annotation_cert_manager_io_cluster_issuer="issuer-1"} 1
kube_secret_annotations{namespace="default",secret="example-1-tls",annotation_cert_manager_io_certificate_name="example-1-tls"} 1
kube_secret_annotations{namespace="samplewebhook",secret="samplewebhook-example-webhook-webhook-tls",annotation_cert_manager_io_certificate_name="samplewebhook-example-webhook-webhook-tls"} 1
kube_secret_annotations{namespace="samplewebhook",secret="samplewebhook-example-webhook-ca",annotation_cert_manager_io_certificate_name="samplewebhook-example-webhook-ca"} 1

It should be possible to construct the report from those metrics, right?


Resolved ValueError when calling manim cfg write

Percent signs added to parser needed to be re-escaped before writing
back to the parser.
Closes #2334.

The pipeline failure seems unrelated (and actually appears across all currently open and recently modified PRs in the repo).


Removed deprecated partition-file feature

What this PR does:
Remove the partition-file feature as its deprecated after the new track-run feature.
Which issue(s) this PR fixes:
Fixes #273
Checklist:

[x] Automated Tests added/updated
[x] Documentation added/updated
[x] CLA Signed:  DataStax CLA

lgtm, but one question - how do we migrate/validate just a token range with the new approach, if need be. Should we document that as well too?

Support for Migrating a specific token-range will continue unchanged using the partition min/max feature. However if you have to migrate several distinct token-ranges, you may have to manually create a run in the cdm_run tables, which may be not be as convenient as listing those token-ranges in the partition-file as currently supported. Having said that, I have not seen a need for this other then for processing failed partitions. Also the new DB based handling is more spark complaint (single point of reference for distributed compute VMs) than the current output  file based approach.
Do you think we should document the min/max feature in the readme? Overall I like the idea of keeping the readme only for highly used featutes and the rest in the detailed properties.

Catching up with these changes :).  With large migrations/validations, there are scenarios where multiple partition ranges get logged in the partition range file. During the rerun, the job only processes the errored ranges. How will this be handled with the recent changes?

Catching up with these changes :). With large migrations/validations, there are scenarios where multiple partition ranges get logged in the partition range file. During the rerun, the job only processes the errored ranges. How will this be handled with the recent changes?

That will be fully supported & is the whole nature of these changes. All failed (& more) partitions will be tracked in the DB as part of the track-run feature instead of partition-file (deprecated feature). The track-run generates a unique run-id for each run, so if for any reason you need to rerun a job that previous failed or was in-complete, just pass the previous-run-id & the new job will just resume & process only the token-ranges that had failed or not processed.


Fix DefaultExperiment parsing and shift defaults to simulate function

@ThummeTo

Thanks for improving @sharanry. I will merge and register as soon as tests are finished.

@ThummeTo That took a bunch of tries as I didn't have access to my windows machine. 😅
I am not really sure what is causing the added errors when compared to dymola in CS tests.
If this is okay, could you please tag a patch release?


latex2html: 2016 -> 2018

Semi-automatic update. These checks were performed:

built on NixOS
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/texexpand -h got 0 exit code
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/texexpand --help got 0 exit code
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/texexpand --version and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/latex2html -h got 0 exit code
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/latex2html --help got 0 exit code
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/latex2html -V and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/latex2html -v and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/latex2html --version and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/latex2html -h and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/latex2html --help and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/.pstoimg-wrapped -h got 0 exit code
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/.pstoimg-wrapped --help got 0 exit code
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/.pstoimg-wrapped -V and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/.pstoimg-wrapped -v and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/.pstoimg-wrapped --version and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/.pstoimg-wrapped -h and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/.pstoimg-wrapped --help and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/pstoimg -h got 0 exit code
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/pstoimg --help got 0 exit code
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/pstoimg -V and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/pstoimg -v and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/pstoimg --version and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/pstoimg -h and found version 2018
ran /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin/pstoimg --help and found version 2018
found 2018 with grep in /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018
found 2018 in filename of file in /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018

cc "@yurrriq"

If it builds, it looks good to me. I no longer use latex2html very often, but can test by the end of the week, if needed.

@grahamcofborg build latex2html

Success on x86_64-darwin (full log)
Partial log (click to expand)
Info: Installed /nix/store/b4qh9bs5s8n89zllkpq9sk0njxm945da-latex2html-2018/share/texmf/tex/latex/html/htmllist.sty
Info: Installed /nix/store/b4qh9bs5s8n89zllkpq9sk0njxm945da-latex2html-2018/share/texmf/tex/latex/html/justify.sty
Info: Installed /nix/store/b4qh9bs5s8n89zllkpq9sk0njxm945da-latex2html-2018/share/texmf/tex/latex/html/ldump.sty
Info: Installed /nix/store/b4qh9bs5s8n89zllkpq9sk0njxm945da-latex2html-2018/share/texmf/tex/latex/html/techexplHTML.tex
Info: Installed /nix/store/b4qh9bs5s8n89zllkpq9sk0njxm945da-latex2html-2018/share/texmf/tex/latex/html/verbatimfiles.sty
Done. Have a lot of fun with LaTeX2HTML!
post-installation fixup
strip is /nix/store/4sdh09gmvl15cy0zb6i7mbvxh5syz206-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/b4qh9bs5s8n89zllkpq9sk0njxm945da-latex2html-2018/bin
patching script interpreter paths in /nix/store/b4qh9bs5s8n89zllkpq9sk0njxm945da-latex2html-2018

Success on x86_64-linux (full log)
Partial log (click to expand)
Info: Installed /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/share/texmf/tex/latex/html/verbatimfiles.sty
Info: Installed /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/share/texmf/tex/latex/html/heqn.sty
Info: Installed /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/share/texmf/tex/latex/html/html.sty
Done. Have a lot of fun with LaTeX2HTML!
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018/bin
patching script interpreter paths in /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018
checking for references to /tmp/nix-build-latex2html-2018.drv-0 in /nix/store/ca56d1xc80h2kjv0q7kz5bkj6j96kakg-latex2html-2018...

Success on aarch64-linux (full log)
Partial log (click to expand)
these paths will be fetched (0.60 MiB download, 5.18 MiB unpacked):
  /nix/store/vpq9k8g7v42ziry7qnnxhhxf8vzppifm-latex2html-2018
copying path '/nix/store/vpq9k8g7v42ziry7qnnxhhxf8vzppifm-latex2html-2018' from 'https://cache.nixos.org'...
/nix/store/vpq9k8g7v42ziry7qnnxhhxf8vzppifm-latex2html-2018


Preventing "except" parameter from modifying "matches" predicate pattern

The documentation states that "except" parameter: "Defines a regular expression that is stripped out of the request field before matching." But in case of "matches" predicate it also strips out the regular expression from the predicate's pattern.
Current master branch behaviour makes the first test from this PR to test 'cde' against // regex instead of /ab/, and the second - to test '12' against /110/ instead of /^\d{1,10}$/.

Thanks so much. Give me until this weekend to merge; trying to free up some time.

Thanks again!


Precursor Lock Key Requirement Randomization

Seems a natural next step after randomizing the alterra door codes. Might take a bit of logic to ensure that keys are accessible before having to use them.
I briefly looked at this and it didn't seem too bad to swap the key requirements around?

Seems a natural next step after randomizing the alterra door codes. Might take a bit of logic to ensure that keys are accessible before having to use them.
I briefly looked at this and it didn't seem too bad to swap the key requirements around?

I don’t like this, because would involve either carrying multiple keys to the locked facilities or travelling back and forth to go gather resources/craft keys or force the need to carry resources for a fabrication baselet or have a cyclops.

It's definitely interesting. To crack down on the tedium mentioned by Ray, I could see giving the player hints in PDA entries beforehand. I'm not yet sure if there are good vanilla entries to modify or whether a custom entry would make more sense.

It's definitely interesting. To crack down on the tedium mentioned by Ray, I could see giving the player hints in PDA entries beforehand. I'm not yet sure if there are good vanilla entries to modify or whether a custom entry would make more sense.

Will probably have to come from alien terminals. To add to jet082’s suggestions, maybe consider also randomising the colours of the tablets found in the world, obviously with some logic in place to prevent a softlock.


Feat: Add clear formatting button to playground

Closes #2190
https://user-images.githubusercontent.com/64399555/170961978-128faa38-23e9-4cdb-8e03-63e5f64d8f11.mp4
Note: Is it okay to leave the hashtag as is? Because lexical changes the node from text to hashtag whenever a string starts with "#". But due to changing the background color to default, the light blue background of the hashtag is being removed.

Could use an e2e test to confirm it works right?

@trueadm Can you please let me know about handling the hashtag node as discussed above? That would help me in writing e2e for this functionality!

@thegreatercurve shouldn't we leave the nodes which already have some pre-specified text-color (quote node and link node) or background-color (hashtags, mentions) while using the $patchStyleText helper function? Attaching these screenshots for reference:
Before Clearing:

After Clearing:

@thegreatercurve shouldn't we leave the nodes which already have some pre-specified text-color (quote node and link node) or background-color (hashtags, mentions) while using the $patchStyleText helper function? Attaching these screenshots for reference:
Before Clearing:
After Clearing:

@im-adithya Very good point. You're right, in other editors, they essentially reset the non-TextNodes to its original styles.
In that case, I think we can still solve the issue with the existing APIs. There is a setStyle method on TextNode, which we can use to reset things such as font, and highlight or text colors.
So, if you remove $patchStyleText, you can then do something like the below in your loop:
 if ($isTextNode(node) || $isHashTahNode(node) || $isMentionNode(node)) {
    node.setFormat(0);
    node.setStyle('');
 }

Done! Checking for just $textNode worked fine as the other two were extending from it!


New version: vOptGeneric v0.2.1

Registering package: vOptGeneric
Repository: https://github.com/vOptSolver/vOptGeneric.jl
Created by: @gsoleilhac
Version: v0.2.1
Commit: 22f63d79068209bd279026f6f441642b71225fcf
Reviewed by: @gsoleilhac
Reference: https://github.com/vOptSolver/vOptGeneric.jl/commit/22f63d79068209bd279026f6f441642b71225fcf#commitcomment-34031796

I just found out it was possible to upper-bound a dependency on an old version without tagging a new one, should I close this and open a PR instead ?

Sorry, was on autopilot and didn't see your comment.
Yes, you will need to adjust for the old version, since they are still compatible with Jump 0.19


Is it possible (or will be) to use containerd based cluster?

Hi!
This project looks really promising to me as it seems to allow to quickly use cluster resources (e.g. gpu-enabled machines) in development.
I'm using Azure-hosted managed cluster which as it seems using containerd runtime instead of docker.
Am I correct that it's impossible to use such a cluster with this project?
If I'm right the question is - is it possible in theory and has chances to be implemented?

Great question! Most features of kdo continue to work irrespective of the underlying container runtime. However, you will not be able to ask kdo to build an image on-demand in the cluster if using a runtime-only container execution environment like containerd. The specific requirements are covered in the documentation here.
The workaround for now would be to build your image manually and push it to a container registry that is visible to the cluster. Then, you can ask kdo to run that image. Depending on how fancy you want to get, you could configure things such that you are running a standard base image in the cluster, and then use kdo's file synchronization capabilities to push code into that container and receive updates when local files change. When combined with running build commands for your app in the image itself, this could simulate the building of an image in the cluster quite well.
I had previously looked into systems for building images inside of containers, but it has been a while. Just poking around, it looks like there may be another option now through buildx that comes with specific support for Kubernetes. I'll take a look at what it would mean to switch to that.
Hope this helps!

Thanks for great response!
In my case I'm also using M1-based MacBook, so sometimes I'm unable to build image locally and use it in my cluster due to arch difference. I also have cases when the image built is really huge (like 20GB) and it's hard to transfer it registry from my location.
With this in mind kdo could give me superpowers (in comparison) with its single-command builds right in the cluster and then getting straight into shell.
Just wondering -- could it be possible to run docker image inside containerd to build image?

Those are great scenarios. I will look into running buildx in Kubernetes and let you know how feasible that looks.

I finally got around to this - see #69.


find queries with embeddables fail if eager relation loaded with with JOINED strategy

Describe the bug
em.find queries fail if an entity that includes both an embeddable and eager one-to-many relationship used.
Stack trace
TypeError: Cannot read properties of undefined (reading '0')
    at SqliteDriver.mapPropToFieldNames (.../node_modules/@mikro-orm/knex/AbstractSqlDriver.js:496:97)
    at .../node_modules/@mikro-orm/knex/AbstractSqlDriver.js:473:44
    at Array.forEach (<anonymous>)
    at SqliteDriver.getFieldsForJoinedLoad (.../node_modules/@mikro-orm/knex/AbstractSqlDriver.js:473:8)
    at SqliteDriver.buildFields (.../node_modules/@mikro-orm/knex/AbstractSqlDriver.js:612:24)
    at SqliteDriver.find (.../node_modules/@mikro-orm/knex/AbstractSqlDriver.js:27:25)
    at SqlEntityManager.find (.../node_modules/@mikro-orm/core/EntityManager.js:105:43)
    at async main (.../src/index.ts:29:15)

To Reproduce
In models.ts:
import { Collection, Embeddable, Embedded, Entity, IdentifiedReference, ManyToOne, OneToMany, PrimaryKey, Property } from "@mikro-orm/core";

@Entity()
export class Cat {
    @PrimaryKey()
    name!: string;

    @ManyToOne()
    user!: IdentifiedReference<User>;
}

@Embeddable()
export class Profile {
    @Property()
    phoneNumber?: string;
}

@Entity()
export class User {
    @PrimaryKey()
    id!: string;

    @Property()
    name!: string;

    @Embedded({ hidden: true })
    profile?: Profile;

    @OneToMany(() => Cat, c => c.user, { eager: true })
    cats = new Collection<Cat>(this);
}

In index.ts:

import { LoadStrategy, MikroORM } from '@mikro-orm/core';
import { Cat, Profile, User } from './user';
import { TsMorphMetadataProvider } from '@mikro-orm/reflection';

async function main() {
  const orm = await MikroORM.init({
    dbName: ':memory:',
    type: 'sqlite',
    entities: [User, Profile, Cat],
    loadStrategy: LoadStrategy.JOINED,
    metadataProvider: TsMorphMetadataProvider,
  });
  await orm.getSchemaGenerator().execute(await orm.getSchemaGenerator().generate());

  const em = orm.em.fork();

  em.create(
    User,
    {
      id: 'TestPrimary',
      name: 'TestName',
    },
    { persist: true },
  );
  await em.flush();
  em.clear();

  console.log(await em.find(User, {})); // This line fails
}

main();

The find query fails if the above configuration is used.
Expected behavior
We should not see any errors.
Additional context
A reproducible repository can be found here.
Versions

Dependency
Version

node
16.13.1

typescript
4.5.5

mikro-orm
5.0.0

your-driver
sqlite (5.0.0)

I also have this issue (sqlite 5.0.0, mikro-orm 5.0.0). Having an eager 1:m or not doesn't seem to make a difference though.

I also have this issue (sqlite 5.0.0, mikro-orm 5.0.0). Having an eager 1:m or not doesn't seem to make a difference though.


Improved Sign-in UI with Theme Color Options

PR Fixes:

#353
Enhanced UI of the sign-in page.
Colors based on theme.

Resolves #353
Video of the changes made
https://github.com/code100x/daily-code/assets/80579894/5be462db-8ebf-4429-9d90-e800122a9f3c
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I assure you there is no similar/duplicate pull request regarding the same issue

can u get rid of the merge conflicts?

can u get rid of the merge conflicts?

yes


Buggy debug mode in the GUI

As soon as the debug log is been set to a different level, also if returned to the initial 0, it stop show any informations, whatever output format is selected, many files get affected by this issue.
I mean that any files open with such non default debug level setting fail to show any informations with many files. Closing it and start with the default minimal debug level setting make it display the informations again.
Tested with version 17.09 and 18.05 on Windows XP.
Sample that doesn't work:
https://github.com/MediaArea/MediaInfoLib/files/2103999/VTS_01_1_RLE.VOB.txt

The debug mode was more or less a proof of concept in order to find sponsors, but nobody is currently interested in spending money in it, so bugs stay as is for the moment.

It looks like the Details have changed meaning to be a trace mode? It used to be that they were just something with more details, in between basic output and Advanced mode. Would it be possible to revert to that and explicitly make new Trace entries for this behavior?

It looks like the Details have changed meaning to be a trace mode?

It is the case for a a long time.

It used to be that they were just something with more details, in between basic output and Advanced mode.

I don't see what "between basic output and Advanced mode" is, I don't remind having that in MediaInfo.

The bug is still there in version 22.06.


Add the CXX flag for only running rev tests with the test_ad

Summary
This adds a CXX flag that can be used in Stan Math tests to not compile and run fwd & mix tests if the tests are using the test_ad utility.
I am primarily trying to add this so we can remove compiling & running fwd & mix tests with Windows and Rtools 3.5 (the tests that run with Github Actions). Particularly our mix tests are on the limit of what g++ 4.9.3 can handle, which is why we sometimes have to split tests files so that 4.9.3 can compile them.
I doubt anyone is using g++ 4.9.3 with fwd and mix. It is still used with Stan, but we only need rev tests to check compatibility there.
There is no Math issue for this PR. I can make one if needed.
Tests
This will decrease our testing with Windows Rtools 3.5 (g++ 4.9.3). Given that we using g++ 4.9.3 outside of the use in Stan is not really recommended, I think this should be fine.
Side Effects
/
Checklist

[x] Copyright holder: Rok Češnovar
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

This is ready for review. It cuts about an hour from the Windows RTools 3.5 mix tests.

Yes, once we bump, this should go away!


Feat: Securing the Atlantis UI

What would you like to be added:
As a maintainer I'd like to have the exposed Services, which are reachable from the web, being more secured.
Currently the Atlantis website is open for everyone, and everyone is able to hit the button to Dis- and enable the 'apply commands' directly from the UI.
Initially, I guess, it's ok to to workaround with NGINX Whitelist Feature.
https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#whitelist-source-range
In the long-run, it could be wise to integrate it more to vault. Like it is currently with ArgoCD, and so on.
PS: This Feature is not fully qualified in its description. One might add more technicial details.
Why is this needed:
Since the overall provisioning of the Cluster is about production-grade readiness, an exposed website should not be accessible without some sort of login features.
At least it brings some good feeling for the end-user and decision makers.

Atlantis recently added a feature that will make it easier to implement this https://www.runatlantis.io/docs/security.html#enable-authentication-on-atlantis-web-server


Make dropdown menu close on $locationChangeSuccess optional

When ui-bootstrap used together with ui-router, we have a menu like to stay open, while a nested sub state reloads  (with url changes) when user click on menu item.
Currently it seems impossible to do this, as dropdown is forced to close upon $locationChangeSuccess
Would be nice to have something like close-on-location-change='false' to make this behavior optional.

Feel free to submit a PR implementing this feature. Although I must say I'm not sure if it will make it into the source since we want to keep the API as simple as possible. Adding very specific settings like this one does not add to that philosophy.

@rvanbaalen I don't want to introduce new API either. Another option would be included it in the new auto-close setting.
It's not very intuitive right now: closing on $locationChangeSuccess  is clearly an action of "automatically close", but it always runs despite user explicitly choose auto-close to be disabled or outsideClick (with document states it only closes when click somewhere else).
I think it would make more sense to disable this behavior when auto-close is set to disabled or outsideClick, gives user total control.

This is an issue not only with the ui-router, but also when using lower level angular APIs such as $location.search to update a get param in the url.
I like the idea of not closing the dropdown on $locationChangeSuccess when auto-close is disabled as well since that seems consistent with the current dropdown API and is more inline with what the docs suggest the behavior would be.
I'd be happy to submit a PR that fixes this since the dropdown is currently broken for our use case.
@rvanbaalen Can you provide some direction as to which interface would be acceptable?

Sounds good, let's add this to auto-close . It's a newly added option (0.13), anyway, so it shouldn't break things for most users.

Great thanks for the feedback! I'll submit a PR with this change for auto-close="disabled" in the next day or so.

Awesome! We always appreciate input from the community :+1:

@rvanbaalen bumping since I'm not sure you guys would have seen a notification come through for the associated PR I submitted awhile back. If you're already aware of it, then nevermind!

Thanks @CloudNiner. Did miss the PR notification indeed. Will take a look at it this week I hope.

Great news, thanks!

As @chrisirhc suggested (https://github.com/angular-ui/bootstrap/issues/3683#issuecomment-104955925), it would be good to disable the auto close on location change when auto-close is either disabled or outsideClick.
As it is, to me, it reads:

auto-close="disabled" - never close, being from an outside click or location change (only explicitly via the toggle button, esc key, or another dropdown opened)
auto-close="outsideClick" - only close automatically on outside click, but not on location change (or explicitly, as above)

Imagine the case (our case) when you have a dropdown with a date picker inside:

we want the dropdown to close when user clicks outside
whenever the user selects a date, we add it to the URL for persistency (hence changing the location)

These two requirements are incompatible. Similarly, we also have filters inside dropdowns where we would like the same behaviour (add to URL without closing, but closing on outside click).
Can I suggest changing to:
$scope.$on('$locationChangeSuccess', function() {
  if (scope.getAutoClose() === 'always') {
    scope.isOpen = false;
  }
});

I can make the PR if you agree.
Thanks.

I agree that outsideClick should ignore location changes as well (unless I'm missing something). Is there any reason that wasn't included in the fix that was brought in, @CloudNiner?
I'd be happy to create a PR for this as well. It would be incredibly helpful!

@jasonbriggs, we decided that as a library it's better to have users do this themselves and opt-in for this behavior rather than force it on everyone and have them opt-out.


Multi-store wrong category urls

I have issue with generating categories for store ID 1, because this extension create always store ID 2 category names url names for store ID 1. How fix that this generating right category names for store ID 1?
Example.
Store ID 1. - This is right url!
https://website_url/store_code/alypuhelimen-osat/apple/iphone-6-6plus-6s-6splus/akut/iphone-6-alkuperainen-akku-1810mah-3-82v
Store ID 2. - This is wrong url! - this is wrong category url "alypuhelimen-osat" and "akut"
https://website_url/store_code/alypuhelimen-osat/apple/iphone-6-6plus-6s-6splus/akut/iphone-6-original-battery-1810mah-3-82v
It should create a url -> https://website_url/store_code/smartphone-parts/apple/iphone-6-6plus-6s-6splus/batteries/iphone-6-original-battery-1810mah-3-82v
I am tested commands:
php bin/magento ok:urlrewrites:regenerate
php bin/magento ok:urlrewrites:regenerate --entity-type=product --store-id=1
php bin/magento ok:urlrewrites:regenerate --entity-type=product --store-id=2
php bin/magento ok:urlrewrites:regenerate --entity-type=category --store-id=1
php bin/magento ok:urlrewrites:regenerate --entity-type=category --store-id=2
php bin/magento ok:urlrewrites:regenerate --store-id=1
php bin/magento ok:urlrewrites:regenerate --store-id=2
Also tried remove all product and category url_rewrite:
DELETE FROM url_rewrite WHERE entity_type='product';
DELETE FROM url_rewrite WHERE entity_type='catefory';
Magento 2.3.2, PHP 7.3

Hello @Userr017
Please upgrade to version 1.5.2 and re-test. Should be fixed.
Thank you.
Best regards,
Oleg Koval.

Hello
I got same problem with multisite setup and category url generation.
I uses the wrong main cat name.
Like:
In english
https://www.dom.com/tool/screwdriver.html
In french it does
https://www.dom.com/tool/tournevis.html
instead of
https://www.dom.com/outil/tournevis.html
So unfortunatly I can't use your work but I would love to !
Best regards,
Max

I'm experiencing the same issue as @eBusinessAtlantique is. It seems that for the url_path the store is not taken into account. Because the url_key seems to be correct.

I'm experiencing the same issue


Could not decode operation

Operations中 包含 ManageDataOperation 时 Could not decode operation

例如transactionHash：d9380ae2861219d70ef8ccf3326fded0bf4cc59a3b6c17ab087b4f0f959dfb68

例如transactionHash：d9380ae2861219d70ef8ccf3326fded0bf4cc59a3b6c17ab087b4f0f959dfb68

Thank you @ChangLongYuOne for reporting this. It is fixed in release 1.9.4

Thank you @ChangLongYuOne for reporting this. It is fixed in release 1.9.4


Add ability to open multiple devices from different processes (libtm and t265)

Hi guys,
As a followup to this issue #4163 on which I shared my application (and I believe many other users need) to open up multiple cameras from different processes (f.e. two different docker containers)
I would like to offer my and fellow workers help as contributors to accomplish the needed changes to support this ability with libtm.
https://github.com/IntelRealSense/librealsense/issues/4163#issuecomment-500719991
this comment in specific explains the issue I encountered.
I believe the issue occurs for the library registers a libusb event listener to identify usb attachments, I think somehow it performs system call futex (lock) on the usb bus which prevents other devices to be discovered.
Please guide us through this feature

Hi @orshefi - Librealsense already has some ability to stream with multiple cameras / processes, though with some rules to follow.  I hope the information in the link below will be a useful reference for your project goal.
https://github.com/IntelRealSense/librealsense/blob/master/doc/rs400_support.md#multi-streaming-model

@MartyG-RealSense - Please read carefully.
I want to stream two different t265 devices from two differet processes.
As you can see from the ticket I attached this feature isn't supported in the current version.
I want to add this feature.

I am not certain why the systems described in the documentation do not meet your needs.  It says that it allows you to "Stream from camera A in one process and from camera B in another process".  Can you provide more details please about how this is different from streaming different T265 from two different processes, please.

Hi @orshefi
Appreciate your offer to help. Here is IMHO the source of the problem:
third-party/libtm/libtm/src/Manager.h:152 - libtm, the original T265 "driver", is detecting all T265 devices and preemptively opening libusb handles to all of them and storing these handles in a singleton.
The way this should be solved, is by removing Manager class all together and passing librealsense backend object directly to Device. librealsense already has a mechanism for device discovery, it is thread-safe, lazy and well-tested with depth-cameras. However, based on my gut-feeling it can take developer roughly 1-2 weeks to get this done, and I'm still looking for a time slot for it.
However, it's very likely a work-around can be implemented in less time, without changing the  architecture. My thinking was to replace this code with a "lazy" version of itself. So basically the manager would identify a device, download firmware, but instead of creating actual Device object would create a new DevicePlaceholder object and store it in a map. This DevicePlaceholder object would only create Device and lock the handle upon first access. It's not perfect, and I'm not 100% sure it will work, but we would appreciate any assistance on this, since we also want to enable this use-case as soon as possible.

Hi @dorodnic,
About the second solution (DevicePlaceholder), I could not understand so far where does the locking happen and why does it effects the different processes, does it locks all the devices with the t265 vendor:product ID?
About the first (and right solution from my point of view) solution (removing Manager):

I understand we will have to implemet a class that uses libtm device class and implements an inherent of device abstract class
The next step is to change the create_devices inside context.cpp to handle the new device class we created upon t265 vid:pid detection and register them as devices to the context object.

As long as I port the libtm device class to implement the device abstract methods the architecture should support this new device type and the query mechanism should handle the new camera?
What steps am I missing?

does it locks all the devices with the t265 vendor:product ID

Yes. IMHO libusb_ref_device(m.device); is locking the device. Now it does this for every T265 device, as soon as it is detected, and libuvc does not allow multiple open handles (from same or different processes)

What steps am I missing?

You understand the problem correctly. From my experience with the code base I can still advise that this is a sizable amount of work. Firmware download flow must be handled somewhere, also getting to libusb handle from context can require some hacking. Finally, getting two processes to play nice with each other without getting occasional resource busy errors (let's say when both are doing query_devices), requires extra work. There is refactoring already in progress to address some of these limitations.

Hi @dorodnic
First thing first, I want to start sharing my code changes in order to receive guidance and review from you guys, please send me a reference on how to do so.
Here's what I have so far:

Removed all lines that initialize manager in the code base
Changed pick_tm2_devices to find the USB device info that corresponds to the product id of the t265

Next thing I'd like to do is to change the device creation method, but there is something I can't understand.
What the difference between the TrackingDevice.h and the Device.h, here are my thoughts:

TrackingDevice seems to me as a class that contains callback functions that are called by a listener instance, which means I need to start a listener that usually is initialized by the manager (?)
Also I need to initialize a Device.h instance and somehow connect the listener to it in order to enable the functions that been implemented in the tm-device class to remain usefull, do I need to address the Device.h file directly (now its not part of the project include_directories).

In another matter, I think that firmware update shouldn't be a part of the project build because it sets a constraint that forces the project to be built on an internet-enabled station and on top of that it couples the process of build and fw update which is decoupled by nature (f.e. the process of fw update in D415).
Another issue it imposes is that one cannot easily freeze fw version of the t265 module - a fact that create a difficulty with reproducibility of a system behavior

The issue with persistent update is that Movidius does not store firmware image on-board, and was designed to receive new firmware upon every power-up.
You can open pull-request to share and collaborate on this.
I'm not entirely sure about Device.h. The listener in librealsense is generic, abstracted via device_watcher interface, plugging into the context. From there, the new detected device_info should trigger creation of a tm2_device / sensor that would get libusb handle from info and pass it to the constructor of TrackingDevice

@dorodnic now I understand the complexity involved with the right solution, it is very complicated and demands a deep understanding of the different libraries.
The other solution you suggested seems reasonable so before working my way through it I'd like to clarify some things I may not fully understand:
The way I understood the flow (device_hub, pipeline, sensors, etc..) eventually it all comes down to the create function in tm-info.h before the actual query of the data from the camera.
Hence I believe the locking (in the form of libusb_ref_device() ? ) should be done inside the create function.
If you agree with me there is no use of the DeviceHolder Class, rather implement a locking function inside TrackingDevice.h and use it only in the create function.
Do you agree? Do the libusb_ref_device is the only function that locks the device and blocking the query_device mechanism from discovering the devices from two processes?

As far as I understand, yes, libusb_ref_device is the one that locks, but I'm not expert in this specific API (@matkatz ?)
The problem with locking in TrackingDevice ctor is that the TrackingManager will still preemptively create such devices regardless if they are needed or not. This is why I was thinking to keep Manager's map, but instead of it mapping TrackingDevice* for it to map some other object that only create TrackingDevice upon first access.
In addition, I hope we will be able to get the proper solution of the group soon enough. It's a follow-up of #4267 where @matkatz gave Firmware-Update USB devices very similar treatment.

Thank you for highlighting the issue of not being able to open multiple devices with the T265. We have moved our focus to our next generation of products and consequently, we will not be addressing this issue in the T265.


proxy should mount volumes as 'read only' whenever possible

From https://github.com/weaveworks/weave/issues/1285#issuecomment-130085857
$ docker inspect weaveproxy
...
    "Mounts": [
        {
            "Source": "/var/lib/boot2docker/tls/ca.pem",
            "Destination": "/home/weave/tls/ca.pem",
            "Mode": "",
            "RW": true
        },
        {
            "Source": "/var/lib/boot2docker/tls/server.pem",
            "Destination": "/home/weave/tls/cert.pem",
            "Mode": "",
            "RW": true
        },
        {
            "Source": "/var/lib/boot2docker/tls/serverkey.pem",
            "Destination": "/home/weave/tls/key.pem",
            "Mode": "",
            "RW": true
        },
        {
            "Source": "/mnt/sda1/var/lib/docker/containers",
            "Destination": "/mnt/sda1/var/lib/docker/containers",
            "Mode": "",
            "RW": true
        },
        {
            "Source": "/var/run",
            "Destination": "/var/run",
            "Mode": "",
            "RW": true
        },
        {
            "Source": "/proc",
            "Destination": "/hostproc",
            "Mode": "",
            "RW": true
        },
        {
            "Name": "82e65d68d3c74e71d89f1dee62d76df474e0f727d82483a1179c75dddeb478b4",
            "Source": "/mnt/sda1/var/lib/docker/volumes/82e65d68d3c74e71d89f1dee62d76df474e0f727d82483a1179c75dddeb478b4/_data",
            "Destination": "/w",
            "Driver": "local",
            "Mode": "",
            "RW": true
        }
...

We should be mounting the pem files read-only.

Fixed in 74eef4d


Handling of misformatted JSON

The handling of the incorrectly formatted entries like "null" and "123.45" currently only works partially. Especially the "null" values can't be correctly translated to None, but to zero or NaN instead, without having a second pass over the data.
This issue can't be easily fixed without changes from msgspec. Here is the related issue: https://github.com/jcrist/msgspec/issues/424

Msgspec got updated, release pending. I'll get some patch done, as soon as this is release.


Capitalize french days and months

All days and months are in lower case, i capitalized them.

@googlebot I signed it!

Bumping this. When will it be merged ?


IDE: Internal Server Error

As you can see in the image I get "Internal Server Error" on https://kaluma.io/ide page.
Is it just me or an actual error/bug?
I can use the Upload option to upload codes and I have the agent running. I'm running it on Arch Linux. I cloned the agent repo then installed npm packages then ran npm dist.

Also TYSM for making that awesome project.

@unitythemaker Web IDE supported only MacOS and Windows so far. Now It has been improved to work on Linux as well. If you are using Chrome (or Edge), you may not need to install Kaluma Agent.
We tested on Ubuntu only, so please try on your ArchLinux. Please let me know whether it works on ArchLinux or not.
Thanks.


Wrong permission being checked on Create/POST.

I am having the problem described in #29 however that was closed without a discussion or solution.
class FooDeviceViewSet(viewsets.ModelViewSet):
    """CRUD for Foo Devices.""
    model = FooDevice
    serializer_class = FooDeviceSerializer
    filter_backends = (DomainFilterBackend,)
    permission_classes = (DRYObjectPermissions,)
    queryset = FooDevice.objects.all()

The FooDevice permissions in models.py are:
    def has_object_read_permission(self, request):
        """You can read a FooDevice if you are in the Domain, or superuser."""
        if request.user.is_superuser:
            return True
        else:
            for users in [dom.get_users() for dom in self.domains.all()]:
                if users.filter(id=request.user.id).count() > 0:
                    return True
            return False

    def has_object_write_permission(self, request):
        """Only superusers can create/write devices."""
        return request.user.is_superuser

And here's how I know that I am hitting the intended URL and the wrong thing is happening.
    def test_unauthorised_dali_device_create(self):
        """Create a Foo Device"""
        url = reverse("my_api:foo_device-list")
        dev_data = {"description": "test device", "dev_id": 0xA, "controller": self.controller.id, "domains": [self.domain.id,],}
        response = self.client.post(self.url, dev_data, format='json')
        self.assertTrue(response.status_code == 403, "(HTTP %s) %s" % (response.status_code, response.content.decode()))

Which results in:
AssertionError: False is not true : (HTTP 201) {"id":8,"description":"test device", domains":[1]}

When you call create on a list URL it seems to call "has_object_read_permission" rather than "has_object_write_permission" (according to print statements inserted in has_object_read_permission)
When checking request.method in generics.py it appears as though it is recieving a GET request which would obviously cause the _read_permission to be run... The question is, where is the GET request coming into the stack?

from dry_rest_permissions.generics import authenticated_users, allow_staff_or_superuser

@authenticated_users
@allow_staff_or_superuser
def has_object_read_permission(self, request):
        """You can read a FooDevice if you are in the Domain, or superuser."""
        for users in [dom.get_users() for dom in self.domains.all()]:
            if users.filter(id=request.user.id).count() > 0:
                return True
         return False

    @authenticated_users
    @allow_staff_or_superuser
    def has_object_write_permission(self, request):
        """Only superusers can create/write devices."""
        return False
´´´

How are you handling views? Here's a small example of how I do:

class GymnasiumHasUserViewSet(RetrieveCacheResponseMixin, RetrieveViewSet):
permission_classes = (DRYPermissions,)
queryset = models.GymnasiumHasUser.objects.all()
serializer_class = serializers.GymnasiumHasUserSerializer
@transaction.atomic
@detail_route(methods=['patch'], url_path='disable')
def disable(self, request, pk=None):
    if pk is not None:
        gym_has_user = models.GymnasiumHasUser.objects.filter(
            pk=pk,
            is_active=True,
            gymnasium__is_active=True
        )
        if gym_has_user.exists():
            gym_has_user = gym_has_user.first()
            self.check_object_permissions(request, gym_has_user)
            if gym_has_user.user_profile != request.user.user_profile:
                gym_has_user.is_active = False
                if gym_has_user.is_staff:
                    gym_has_user.user_profile.user_category -= 1
                    gym_has_user.user_profile.save(force_update=True)
                gym_has_user.last_modified_by = request.user.user_profile
                gym_has_user.save()
                serializer = serializers.GymnasiumHasUserSerializer(
                    gym_has_user,
                    context={'request': request}
                )
                return Response(serializer.data, status.HTTP_200_OK)

    return Response({}, status.HTTP_400_BAD_REQUEST)

class UsersByGymnasiumList(ListCacheResponseMixin, ListCreateAPIView):
permission_classes = (DRYPermissions,)
serializer_class = serializers.GymnasiumHasUserSerializer
filter_class = GymnasiumHasUserFilter
def get_queryset(self):
    gymnasium_pk = self.kwargs['pk']
    queryset = models.GymnasiumHasUser.objects.filter(
        gymnasium=gymnasium_pk
    )
    gymnasium = models.Gymnasium.objects.filter(pk=gymnasium_pk)
    user = self.request.user
    if gymnasium.exists():
        is_gym_staff = gymnasium.first().has_staff(user.user_profile)
        if is_gym_staff or user.is_staff or user.is_superuser:
            return queryset
        else:
            return queryset.filter(user_profile__user=user)

    return queryset.none()

Hope it helps.

The issue I am going to chase down today is why a GET request is coming in rather than a POST and hitting has_object_read_permission rather than has_object_write_permission - this may not be a DRY Permissions issue yet because I don't think DRY Permissions does any altering of request.method. I suspect it is an issue with DRF APIClient.
If I were to take your approach there would actually be no point at all using DRY Permissions at all because all the permissions handling would be done in get_queryset() and the views, which is what DRY Permissions is trying to avoid - "Don't Repeat Yourself".

See #18 for what the root of the issue is.
(Essentially, to secure Create you must have a global permission on the model in addition to an object permission for write - and use DRYPermissions rather than just DRYObjectPermissions.)


When a user logs in set the highest current role possible

As a user officer or instrument scientist I want the software to default me not to the user role but the highest possible role I have.
Motivation and Context
Eliminate tedious task of changing role for the user officer
How Has This Been Tested
E2E
Fixes
SWAP-3379
Changes
Changes in frontend and backend in the user mutations, user provider
Depends on
NA
Tests included/Docs Updated?

[x] I have added tests to cover my changes.
[ ] All relevant doc has been updated

Hi Fredrik, I am still looking into getting these tests passing btw. They wouldn't run at all in our local environments to start with, and they're tricky to figure out, but hopefully will get it resolved soon

Hi Fredrik, I am still looking into getting these tests passing btw. They wouldn't run at all in our local environments to start with, and they're tricky to figure out, but hopefully will get it resolved soon

Thanks, I have been looking at it myself but have not succeeded with the mock wsdl setup.  My suspicion is that the mock-uows service is not behaving in the same way as the user-office-development-authorization-server.

It looks like one of the problems is that we're not returning the correct mocked responses for users (for example, cy.login('user1') would in fact return a user officer), and this PR has revealed the problem. More tests are passing now but there's still some issues that I'm continuing to investigate where I have time, so thanks for your patience!

I've created a PR that I hope will fix the issues here once merged: https://github.com/UserOfficeProject/mock-uows/pull/8 🙂


UserUtteranceReverted event incorrectly replays actions

Rasa Core version:
master (5a0f0ea445da8f6cbfe53402aa70b1900fd23f66)
Python version:
3.6.3
Operating system (windows, osx, ...):
OSX 10.13.2
Example
Sample project illustrating the error:
https://github.com/twineai/rasa_core-1/tree/rewind_error/examples/rewindbot

Issue
In the example above, the do_inconsequential_thing action issues a UserUtteranceReverted event. After the event is applied, the bot predicts the next actions to be the actions that were previously ran, whereas I'd expect the bot's state to be simply as if the utterance never occurred at all.
Diagnosis
I believe it's the result of the following:
Prior to utterance
Tracker Event History =
   - ActionExecuted(Listen)
   - UserUttered(do_destructive_thing)
   - ActionExecuted(do_destructive_thing_one)
   - ActionExecuted(do_destructive_thing_two)

At this moment, the bot is in the process of listening
Now the utterance comes in, and the next action runs (the one which yields the UserUtteranceReverted)
Tracker Event History =
   - ActionExecuted(Listen)
   - UserUttered(do_destructive_thing)
   - ActionExecuted(do_destructive_thing_one)
   - ActionExecuted(do_destructive_thing_two)
   - ActionExecuted(listen)
   - UserUttered(do_inconsequential_thing)
   - ActionExecuted(do_inconsequential_thing)

The UserUtteranceReverted then rewinds the second UserUttered, yielding a state like this:
Tracker Event History =
   - ActionExecuted(Listen)
   - UserUttered(do_destructive_thing)
   - ActionExecuted(do_destructive_thing_one)
   - ActionExecuted(do_destructive_thing_two)
   - ActionExecuted(listen)

Then the policy looks at the state and says "what do I do in this situation", the model sees the last completed action (this is important) being the listen, and tries to recommend an action. This queries the last message for the intent (do_destructive_thing in this case), and then runs the associated actions.
I believe the UserUtteranceReverted should also rewind the ActionExecuted(listen) that occurs immediately prior to the user utterance, so that the model always predicts the next action as being listen, thus making the bot behave as if the utterance never occurred (barring side effects from the actions, of course).
Config
Content of domain file:
intents:
  - do_destructive_thing
  - do_inconsequential_thing

actions:
  - actions.ActionDoInconsequentialThing
  - actions.ActionDoDestructiveThingOne
  - actions.ActionDoDestructiveThingTwo

Content of stories:
## greet
* do_destructive_thing
    - action_do_destructive_thing_one
    - action_do_destructive_thing_two

## do thing
* do_inconsequential_thing
    - action_do_inconsequential_thing

Content of actions:
class ActionDoDestructiveThingOne(Action):
    def name(self):
        return 'action_do_destructive_thing_one'

    def run(self, dispatcher, tracker, domain):
        dispatcher.utter_message("Doing destructive thing one")
        return []

class ActionDoDestructiveThingTwo(Action):
    def name(self):
        return 'action_do_destructive_thing_two'

    def run(self, dispatcher, tracker, domain):
        dispatcher.utter_message("Doing destructive thing two")
        return []

class ActionDoInconsequentialThing(Action):
    def name(self):
        return 'action_do_inconsequential_thing'

    def run(self, dispatcher, tracker, domain):
        dispatcher.utter_message("Doing an inconsequential thing that shouldn't be remembered")
        return [UserUtteranceReverted()]

I think we resolved that as part of #194.


getEstimatedReceive throws a cannot be converted to a BigInt because it is not an integer

When building a new swap request, and calling getEstimatedReceive I receive 'The number 0.05 cannot be converted to a BigInt because it is not an integer'
This occurs randomly, and for me was occurring when using the Sundaeswap Dex on the second pool returned.
The pool this errors on has a poolFeePercentage of 0.0005 which is much lower than the others that succeed.
  const buyTokenSwapRequest = dexter.newSwapRequest().forLiquidityPool(pool).withSwapInToken('lovelace').withSwapInAmount(BigInt(amount));       const amountOfTokenToReceive = buyTokenSwapRequest.getEstimatedReceive()
I think this could potentially be because this is the first pool with a poolFeePercentage when * 100 the result is still a decimal.
https://github.com/IndigoProtocol/dexter/blob/9f3ad876a13088a68c0529684514e6e909c9eb45/src/dex/sundaeswap.ts#LL141C13-L141C13

This seems to occur across all pools when the poolFeePercentage < 0.01


logging: Add log initialization to system startup

Log API can be used before user can explicitly initialize the logger.
In order to ensure that logger core is ready to buffer log messages
it must be initialize as early as possible. Initialization does not
include initialization of default backend since driver may not be
ready and backend is needed only when log messages are processed.
PR replaces #8742
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

Codecov Report

Merging #8842 into master will increase coverage by <.01%.
The diff coverage is 88.23%.

@@            Coverage Diff             @@
##           master    #8842      +/-   ##
==========================================
+ Coverage   52.32%   52.33%   +<.01%
==========================================
  Files         195      195
  Lines       24730    24739       +9
  Branches     5140     5140
==========================================
+ Hits        12941    12948       +7
- Misses       9715     9717       +2
  Partials     2074     2074

Impacted Files
Coverage Δ

include/logging/log_msg.h
81.81% <ø> (ø)
:arrow_up:

subsys/logging/log_msg.c
81.95% <100%> (+0.41%)
:arrow_up:

kernel/init.c
57.97% <100%> (+0.61%)
:arrow_up:

subsys/logging/log_core.c
72.34% <84.61%> (-0.46%)
:arrow_down:

Continue to review full report at Codecov.

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


The Mac app is damaged

The release Mac app appears to be damaged.

This works fine now.

Actually, it does not.

The issue is related to: https://github.com/feenkcom/gtoolkit-maestro-rs/blob/824584fc1dbc932a75fc5d4bbe36983f64dab659/src/zipping/zip.rs#L53


Update to 1-based API, update PR to spec, add SSSP

Note that SSSP will only work after the following pull request is merged into GraphMat:
https://github.com/narayanan2004/GraphMat/pull/10

Thanks for your contribution!


General: refactor MGCB Editor Tool detection and installation logic

Currently, MGCB Editor Tool is detected from the frontend side in quite an ineffective and buggy way.
ReSharper 2022.2 SDK comes with NuGetDotnetToolsTracker that could be used on a project-scoped level to detect mgcb-editor tool instance (both local and global ones).
We should also keep in mind that according to #13 MonoGame 3.8.1 has changed the way of installing and using mgcb-editor tool. It will be great if we come to a generic approach that could work on any MonoGame version without branching.

Currently the only workaround that I found is going to the project directory and running dotnet mgcb-editor on the command line.
(An alternate, faster method exists by running dotnet mgcb-editor in the Rider's terminal.)
Though just being able to click a mgcb file and having it run would be nice.

Detection should work now, installation feature was temporarily removed.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.19.199",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4921b1618045ffab71b1050bf0014df3313a2289"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "4921b1618045ffab71b1050bf0014df3313a2289",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "scsi: libfc: Fix array index out of bound exception\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.19.199 by commit 4921b1618045ffab71b1050bf0014df3313a2289. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001363


Update request: fsautocomplete 0.73.2 → 0.75.0

Package name: fsautocomplete
Latest released version: v0.75.0

Current version on the unstable channel: v0.73.2
Current version on the stable/release channel: v0.72.3

[x] Checked the nixpkgs pull requests

Notify maintainers
@mdarocha, @gbtb

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

I'll update the package once it releases next version, cause new release will contain the changes I'm waiting for. It should be released soon.

Fixed by https://github.com/NixOS/nixpkgs/pull/360986


Output chunks change when build stays the same

Bug report
The original issue was reported here https://github.com/vercel/next.js/issues/70754, but I have a strong suspicion that the issue is with webpack and not with nextjs.

What is the current behavior?
when none of the source files change, webpack creates new output chunks for some of the pages.

https://www.diffchecker.com/OidQJCx0/
according to the webpack docs:

The [contenthash] substitution will add a unique hash based on the content of an asset. When the asset's content changes, [contenthash] will also change.

if you compare the changed page-[contenthash].js chunks across builds, you'll notice that the contents are nearly identical, except for the webpack chunk IDs at the top of the file. the contents of the array are the same, it's just that the order can change across builds

https://www.diffchecker.com/Zp1tnr7X/
i.e. because the chunk IDs aren't sorted at the top of the chunk, webpack treats these as "new" chunks, even though the actual code hasn't changed.
If the current behavior is a bug, please provide the steps to reproduce.

https://github.com/chriskrogh/build-manifest-test

clone the repo and run npm i
run the nextjs build (npm run build) and take note of the app-build-manifest.json
run the nextjs build again and compare the app-build-manifest.jsons across the two builds

you may want to sort them by route if they're not in the same order across builds
you may also need to repeat step 3 if you observe identical chunk names. see above for why that is

What is the expected behavior?

chunks should be the same when the build doesn't change

Proposed solution

sort the webpack chunk ID array before writing to the file so that the array stays the same if the contents are the same

I'm willing to open a PR if someone points me to the right place.
Other relevant information:
webpack version:  5.90.0
Node.js version: 20.12.0
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6000
Available memory (MB): 32768
Available CPU cores: 10

Maybe related too https://github.com/webpack/webpack/issues/17757

@alexander-akait I'm pretty sure we just need to add a .sort() to the chunk ids before we write to the chunk. do you know where that logic might live in the codebase? I'm willing to test locally and put up a PR

I'm pretty sure we just need to add a .sort() to the chunk ids before we write to the chunk.

Before making changes we need to understand what and how they are created, I will try to figure it out in the near future

i have same issue, and yes a simple sort() would solve it, i tested it

I found the root of the problem and it is inside nextjs - https://github.com/webpack/webpack/blob/main/lib/optimize/FlagIncludedChunksPlugin.js#L50
compilation.modules is not deterministic and always has a different order of modules and due this moduleBits and hash are always different - https://github.com/webpack/webpack/blob/main/lib/optimize/FlagIncludedChunksPlugin.js#L65 and when comparing hashes - https://github.com/webpack/webpack/blob/main/lib/optimize/FlagIncludedChunksPlugin.js#L109 in some situations this condition is true or false - so the order is random.
This can happen due to changing the order of modules in some async hooks. In pure webpack this does not happen because we do not do such things, but apparently in some nextjs plugin this happens. Unfortunately, debugging in which requires deeper knowledge in nextjs, this takes me much more time, I have already spent about 5-6 hours to find where the problem is and why. Anyway I intend to fix this because we have async hooks before this, which could potentially happen in other unofficial plugins too.

thanks @alexander-akait !!! how can i keep track of the version this change will make it into? also, I'm guessing I need to bump webpack in nextjs to test once this has been released?

@chriskrogh I'm planning to make a release this weekend with this fix


[OIDC] Redesign or remove nonce cookie support

The nonce used during the OIDC login can be stored in a cookie or in a server side cache. The cookie support is buggy and needs to be redesigned or removed.
A simple cookie name cannot be used because it will overwrite the existing cookie if a login flow is in progress in another browser tab. To address this a unique cookie name was used per login.
Now the problem is knowing when to clean up stale cookies since we can't tell if another browser tab is still open and will eventually complete it's login flow.
The most often reported problem is in scenarios with configuration issues where the client gets into a redirect loop and creates additional nonce cookies until they get a 400 from the server saying there are too many headers. In this case the surplus of nonce cookies are a just symptom of a configuration problem and no amount of cleanup effort is likely to make the scenario succeed.
RE: https://github.com/aspnet/Security/issues/179

Regarding one of the issues with Nonce cookie:

IDX10311: RequireNonce is 'true' (default) but validationContext.Nonce is null. A nonce cannot be validated. If you don't need to check the nonce, set OpenIdConnectProtocolValidator.RequireNonce to 'false'.

There is a case where cookie does not get written in the HTTP response at all. And it's easy to reproduce.
In MVC controller's action (ex /account/login), I have 2 lines of code:
httpContext.Session.Abandon(); // Cause of the problem!

context.Authentication.Challenge(
	new AuthenticationProperties(),
	OpenIdConnectAuthenticationDefaults.AuthenticationType);

I first abandon current Session and then call Authentication.Challenge() to redirect user to authorization server.
As a consequence of abandoning the session, ASP.NET pipeline does not output Set-Cookie: OpenIdConnect.nonce... in the redirect response, even though it was previously set by CookieManager.
Browser never receives the cookie. After user gets redirected back from authorization server to the relying party, cookie is not there and nonce validation fails.
If I replace Session.Abandon() with Session.Clear() everything works fine.
Core of the issue seems to be related with handling of Response.Headers in the Microsoft ASP.NET pipeline, which has some known issues.
IMPORTANT - To reproduce issue delete ASP.NET session cookie before hitting the page! When cookie is present, example works.

@nenadvicentic that is only applicable to Asp.Net 4 / MVC 4 / Katana. Session.Abandon() no longer exists in Asp.Net 5. See http://katanaproject.codeplex.com/wikipage?title=System.Web response cookie integration issues&referringTitle=Documentation

Recommendation: Mitigate by setting a default cookie timeout for 15 minutes.

Will this fix be in any of the v.3.* -packages of Microsoft.Owin.Security.OpenIdConnect as well, or what is the plan exactly here..?
We're currently being forced to downgrade to 3.0.0 from 3.0.1 because of this.

@johnkors Given the imminent release of Asp.Net Core there's no plan to backport this change to the Microsoft.Owin packages.

@Tratcher If the bugfixes are not being backported to the Microsoft.Owin packages, what is the roadmap for the OWIN in ASP.NET (not Core)? Is there any replacement for it that is being actively maintained?

Super old blog post but it gets the point across still I think https://blogs.msdn.microsoft.com/webdev/2014/11/14/katana-asp-net-5-and-bridging-the-gap/.

@davidfowl Thanks, so if I got it right, we don't have any 1:1 replacement for the Microsoft.Owin stack and packages being actively maintained for the "classic" .NET, right?


Enhanced the design for fixed header

I have worked on the App.css file to make the change the alignment/order of the elements present in the header.  Now the header looks like the below image

Hope you like this design.  Thank you.

design looks great to me but can you also show me the phone view of the app ?

@yokesh004 Why is that white line coming in the right and also that blue header is not covering the whole screen horizontally ? or is it just the issue of picture ? Kindly confirm and resend the image if this is a picture issue.

This is the original image

@yokesh004 Merged ! Thank You 😄

@yokesh004 Merged ! Thank You

Thank you @DhairyaBahl


Identifiers validation failed for dataset Herbarium of the Université Libre de Bruxelles

Identifier validation failed for the dataset Herbarium of the Université Libre de Bruxelles:

Crawler attempt: 333
Publishing organization: Université Libre de Bruxelles (ULB)
Publishing country: BELGIUM
Installation: Belgian BIF IPT
Number of occurrences indexed for this dataset at the time of the issue: 12542
Cause: GBIF ID problems exceed 50% threshold: 81% duplicates; 16046 total records; 12991 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3929141/step

New IDs sample:

ULB:BRLU:7526.0
ULB:BRLU:302.0
ULB:BRLU:7431.0
ULB:BRLU:8628.0
ULB:BRLU:7442.0
ULB:BRLU:26671.0
ULB:BRLU:8523.0
ULB:BRLU:26668.0
ULB:BRLU:582.0
ULB:BRLU:591.0

Old IDs sample:

ULB:BRLU:67175
ULB:BRLU:60068
ULB:BRLU:56800
ULB:BRLU:35008
ULB:BRLU:35009
ULB:BRLU:35010
ULB:BRLU:35011
ULB:BRLU:35013
ULB:BRLU:35014
ULB:BRLU:35015

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Herbarium of the Université Libre de Bruxelles : https://doi.org/10.15468/yn20mq.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

publisher updated archive to match what as in migrations csv


Enable case-insensitive tab completion for files and folders on case-sensitive filesystem

PR Summary
Leverage new EnumerationOption in .NET Core 2.1 to have case-insensitive enumeration of files and folders.  Allows for case-insensitive tab completion of files and folders on a case-sensitive filesystem.
https://github.com/PowerShell/PowerShell/issues/1273
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[ ] Not Applicable or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

@SteveL-MSFT Should we close #1273?


Doesn't work when running in IDE and requires mouse over window caption?

I am working with the SimpleTargetDemo (in the installation's Demos\TargetDemo folder) and didn't think it was working at all. Come to find out it will not work when running in the IDE.
I also found that when I did finally get it to work (both in the Demo and in my own little test app) outside the IDE/debugger, it would only work if I first roll the cursor over the window caption. Only then would the application accept the files to be dropped from Windows Explorer. I thought it may be a timing issue but doesn't appear to be.
Is this by design or what would be causing this?
I am running Delphi XE7 with the latest subscription update applied (Dec 2015) on a Windows 8.1 machine.
I would like to be able to use this component but having to roll over the caption first is not an acceptable behavior.

Hi,
Sorry for the late reply Delphi developer.  Im actually in the process of
trying to get the drag and drop component suite and I am not having any
success.  I dont see the design time package for Delphi10S.  Is there a
particular Design time package that you think would run with 10S?
On Mon, Jul 25, 2016 at 9:24 AM, anngossard<EMAIL_ADDRESS>wrote:

I am working with the SimpleTargetDemo (in the installation's
Demos\TargetDemo folder) and didn't think it was working at all. Come to
find out it will not work when running in the IDE.
I also found that when I did finally get it to work (both in the Demo and
in my own little test app) outside the IDE/debugger, it would only work if
I first roll the cursor over the window caption. Only then would the
application accept the files to be dropped from Windows Explorer. I thought
it may be a timing issue but doesn't appear to be.
Is this by design or what would be causing this?
I am running Delphi XE7 with the latest subscription update applied (Dec
2015) on a Windows 8.1 machine.
I would like to be able to use this component but having to roll over the
caption first is not an acceptable behavior.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DelphiPraxis/The-Drag-and-Drop-Component-Suite-for-Delphi/issues/16,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKOFBSa8p1eew3ctV1Ltjg47TpKb4oBDks5qZONBgaJpZM4JUTNg
.

--
Ray Mejia
Imagine Systems

Using Delphi XE10s on Windows 10.
Open and run TreeViewTarget demo.
It will not except a drop. Does not work.
But If I run the created exe outside of the IDE, then it works.
Any ideas?

works with current sources


Fix Activity onPause/onResume breaking the permission dialog

Jira issue:
https://glia.atlassian.net/browse/MOB-2171
Additional info:
The issue was caused by the DialogController addCallback() method, which always fired the current dialog state.
CallActivity and ChatActivity always add/remove the callback on Activity onResume/onPause to prevent the same dialog from appearing on both Activities. But as a result, because of this, a duplicate second dialog was being with Activity having no callbacks attached to it.
Ideally, need the full refactoring of the Alert dialogs logic in Widgets SDK. Asked this refactoring request to be added to the Android tech depts.
Screenshots:

!merge


feat: enable allowSyntheticDefaultImports typescript option by default

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
This enables allowSyntheticDefaultImports: true by default.
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

I think it is a nice default. Is there any known issue that this fixes?

It fixes the issue of not having TS/IDE support when importing modules with synthetic default imports into a server route. Someone encountered this on Twitter.


Added useful C++ symbols missing from the tensorflow DLL on windows

On Windows, there is tool for selecting which symbols get exported to the tensorflow DLL.
However, this filter does not include the symbols needed to use SessionOptions and SavedModel. It is also missing symbols for accessing shapes of a given node in the graph and creating a default instance of GraphDef.
This fix adds these symbols manually, thus not an elegant fix, and there are most likely several other symbols that should be included, but these are symbols which I find essential to: load a SavedModel, determine shapes and run inference with specific SessionOptions in C++.

This should be opened against master branch. We only backport changes to releases if they are related to security.


Feature: visualization & Analysis Graph models

Is your feature request related to a problem?
visualization & Analysis Graph model is surrealist
Describe the solution
I think visualization & Analysis graph models for surrealdb is a mondatory feature that must be implement in surrealist.like Graphizer in Apache Age.
Are you willing to contribute this feature
no
Surrealist Environment
v2.1.6 +
Contact Details
No response
Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This is a feature request previously discussed way back in #22 which originally lead to the creation of the Designer view. I fully agree that a proper record and relation visualisation option would be a great addition, and something we will likely tackle in the future


R200 STATUS_ITEM_UNAVAILABLE

Unity5.65 R200
public void StartDevice()     {         if (senseManager.Init() == Status.STATUS_NO_ERROR)         {             Debug.Log(TAG + "Initialization Successful!");             isStart = true;         }         else             throw new System.Exception("Initialization Failed!");     }
senseManager.Init() STATUS_ITEM_UNAVAILABLE
r2 support r200,"Full Hand Tracking and Gesture Recognition SDK" belong to r3

Unity5.65 R200
public void StartDevice() { if (senseManager.Init() == Status.STATUS_NO_ERROR) { Debug.Log(TAG + "Initialization Successful!"); isStart = true; } else throw new System.Exception("Initialization Failed!"); }
senseManager.Init() STATUS_ITEM_UNAVAILABLE

r2 support r200,"Full Hand Tracking and Gesture Recognition SDK" belong to r3

Oh! That's my mistake. I'm sorry about that.
I checked the document Full Hand Tracking and Gesture Recognition SDK is belonged to R3 only.
Thanks for notice.
I will correct README.

I'm corrected the document!
So I'm closing the issue.
Feel free to open it again if you have some question.
Thanks 😄


make run - for local development start up

Description
There currently is no one-click start up for local development.
Solution

Add a run target to the root Makefile that will get the local development environment up and running for a developer.
add a run-docker to target running everything in a docker container locally for manual, smoke testing post UI and server build

container is built
use docker-compose to launch on a docker network
expose the UI via pre-defined Host port
set all required input variables via *.env file (Dockerfile conditional copy)

Implementation
It should perform the following:

start ./ui project (with file watch)
start server (at ./server/build)

#27

closing this issue since Ansible avoids placing run statements in their make file.


Rocketchat to Discord

Fixes #1937

@petermetz The contents of this PR itself looks good to me, but this is duplicated with the PR #1942 .
If we prioritize the pull-request that was posted earlier, we should fix the semantic error in this PR #1942.
How do you think, @petermetz ?

My bad! I did not know there was another active PR  to the same issue. Happy to do a re-commit with the right semantics if needed.

My bad! I did not know there was another active PR  to the same issue. Happy to do a re-commit with the right semantics if needed.

@AbhinavMir Let's see how the other PR turns out. The author of that one said he'd fix its issues today. If that comes to pass then we'll merge that one on account of the first come first served PR acceptance policy and this will have to be closed as a duplicate. On the other hand if the other PR experiences more delays then we might just move ahead with this one to make sure that the change gets in as soon as possible.

There seems to be a delay. Happy to resolve it now.