ability to set boundary color?

I should be able to, with code, set the color of the rectangular or circular border which indicates the area of the crop (the visual indicator of the 'points'). I have browsed the docs and don't see this. I might be able to inspect the dom and add a css style, but this seems like it should be built in.

It's not built in to the api.  You're free to add additional CSS styles to manipulate the look of the croppie element, but as far as styling through the API, that doesn't exist beyond width/heights.
This isn't something that I see as a high use case.  I think creating a custom style in your css should cover most uses.  BUT .... I'm open to PR's on this repo.

I also want to set the border and shadow of the boundary (saved image) - any suggestions? - thanks


MonteCarloMeasurements v1 compatibility

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

12 of 12 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.255%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2834

Relevant Lines:
3404

💛  - Coveralls


Agreement

Is there any reason for the agreement to have such a prominent place in the registration process?
Couldn't it be a simple "terms of service" link in the registration form like in many, many, many services we register almost daily?

This was fixed ages ago by @Ant59 with 03c22b9d1d6be497b40046caa775a60615c9dc7d
So closing it. YAY!


[DO NOT MERGE] WebClient + Sleuth のテスト

@ackintosh Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


Adding colored layers for different zones

I am having troubles adding the different zones as new polygon layers on the map.

I changed the code so all zones are added as coloured polygons on the map.
Still to do :
1/ get the markers to work again
2/ improve the colours :-)

Ok, markers working again.


Missing CONTRIBUTING.md

Hi !
Thank you all for bringing falco to the community.
I opened a PR on the project and saw that the PR template reference a CONTRIBUTING.md that doesn't exit on the repository.
Could it be copied from this : https://github.com/falcosecurity/.github/blob/master/CONTRIBUTING.md ?

That's a fair point, we need to discuss about, the main CONTRIBUTING.md has some parts (C++ guidelines) which are really focused on falco


Fix: [TRI-1444] Only allow logins from whitelisted_emails (for self-hosting)#685

Closes #
✅ Checklist

[x] I have followed every step in the contributing guide
[x] The PR title follows the convention.
[x] I ran and tested the code works

Steps

Setting WHITELISTED_EMAILS in .env.example:

I added the WHITELISTED_EMAILS(which is optional) variable to .env.example under # OPTIONAL VARIABLES with the value matt<EMAIL_ADDRESS>I ensured that the application reads this environment variable correctly.
I have implimented the changes mentioned in the last PR https://github.com/triggerdotdev/trigger.dev/pull/692#issue-1964822193

Testing
I have tested the changes in this pull request as follows:

** Values to check wether the WHITELISTED_EMAILS validation works

<EMAIL_ADDRESS>or<EMAIL_ADDRESS>

Screenshots
https://github.com/triggerdotdev/trigger.dev/assets/106991686/717704f3-5d3f-4fc1-9458-072b0614fe5c
💯

hey @nicktrn  can u review my pr

Thanks for your efforts end those edits @AsbarK! We decided to go with #721 in the end.


Bump nova-operator to v0.1.1

This is needed to pick up a bugfix for EDPM deployment in real network isolation environment.
See https://github.com/openstack-k8s-operators/nova-operator/pull/479

We need to tag v0.1.1 in nova-operator then update this PR to use that tag.

/test all

I built this so it can be tried locally via
OPENSTACK_IMG=quay.io/gibi/openstack-operator-index:v0.0.140 make openstack

I built this so it can be tried locally via
OPENSTACK_IMG=quay.io/gibi/openstack-operator-index:v0.0.140 make openstack

I was able to deploy EDPM compute with this openstack-operator version and the AnsibleEE CRs for nova-compute and libvirt now has NetworkAttachment filled:
NAME                                                  NETWORKATTACHMENTS                              STATUS   MESSAGE
dataplane-deployment-configure-network-edpm-compute   ["ctlplane","internalapi","storage","tenant"]   True     AnsibleExecutionJob complete
dataplane-deployment-configure-os-edpm-compute        ["ctlplane","internalapi","storage","tenant"]   True     AnsibleExecutionJob complete
dataplane-deployment-install-os-edpm-compute          ["ctlplane","internalapi","storage","tenant"]   True     AnsibleExecutionJob complete
dataplane-deployment-repo-setup-edpm-compute          ["ctlplane","internalapi","storage","tenant"]   True     AnsibleExecutionJob complete
dataplane-deployment-run-os-edpm-compute              ["ctlplane","internalapi","storage","tenant"]   True     AnsibleExecutionJob complete
dataplane-deployment-validate-network-edpm-compute    ["ctlplane","internalapi","storage","tenant"]   True     AnsibleExecutionJob complete
nova-edpm-compute-0-deploy-libvirt                    ["ctlplane","internalapi","storage","tenant"]   True     AnsibleExecutionJob complete
nova-edpm-compute-0-deploy-nova                       ["ctlplane","internalapi","storage","tenant"]   True     AnsibleExecutionJob complete
nova-edpm-compute-1-deploy-libvirt                    ["ctlplane","internalapi","storage","tenant"]   True     AnsibleExecutionJob complete
nova-edpm-compute-1-deploy-nova                       ["ctlplane","internalapi","storage","tenant"]   True     AnsibleExecutionJob complete

Just the edpm-baremetal job failed and that is also with a known unrelated issue.
Resource: "admissionregistration.k8s.io/v1, Resource=validatingwebhookconfigurations", GroupVersionKind: "admissionregistration.k8s.io/v1, Kind=ValidatingWebhookConfiguration"
--
231 | Name: "baremetal-operator-validating-webhook-configuration", Namespace: ""
232 | from server for: "STDIN": Get "https://api.crc.testing:6443/apis/admissionregistration.k8s.io/v1/validatingwebhookconfigurations/baremetal-operator-validating-webhook-configuration": dial tcp <IP_ADDRESS>:6443: connect: connection refused
233 | gmake: *** [Makefile:476: crc_bmo_setup] Error 1

So I'm fairly confident that this bump is correct

@gibizer I'm not convinced we need to do this. If we build the new nova-operator tag downstream what does bumping a new tag here matter? There is no golang/struct change in play here really other than upstream does bundle pinning (but we wouldn't use those as a basis for how we tag downstream)

OK. If this is not needed to sync things up for the dev preview then one less PR to merge :)

/test openstack-operator-build-deploy-kuttl

/test openstack-operator-build-deploy-kuttl

recheck

/test openstack-operator-build-deploy-kuttl

recheck

/test openstack-operator-build-deploy-kuttl

recheck


access log: cleanup arguments in gRPC access log

Signed-off-by: Shikugawa<EMAIL_ADDRESS>
Commit Message: access log: cleanup arguments in gRPC access log
Additional Description: This refactor is needed to draw proto config around the various classes in access log.
Risk Level: Low
Testing: N/A
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/retest

@wrowe Could you take a look?

@wrowe @yanavlasov gentle ping


Revert flaky concurrent append and streaming replace ITs

Revert https://github.com/apache/druid/pull/16755 since the test introduced seems to be flaky
This PR has:

[ ] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

@AmatyaAvadhanula , do we know the source of flakiness, i.e. would changing a couple of lines fix up the test or is it completely unusable?

We can add the test back once we have identified the source of flakiness.
Merging this PR for now to unblock development, esp. since the code freeze is coming up.


update CrossVersion.patch and scalaOrganization.value

ref. https://github.com/typelevel/scala/issues/135

👍 thanks @aoiroaoino


Only call timeout if the time is a valid integer

Allows the use of ng-attr-dismiss-on-timeout="{{alert.dismissOnTimeout}}" when alert.dismissOnTimeout isn't defined. This fix will keep the alert on the screen instead of running $timeout(function(){ alertCtrl.close(); }, NaN); which runs instantly.

I think doing
$timeout(..., parseInt(attrs.dismissOnTimeout, 10) || 0)

would be a sufficient fix for this.

Ahh, I was mistaken about the intent here - I'm not sure this is desired - if the user intent is to block closing, one should create the blocking behavior in the close method itself, instead of hacking the timeout.

@wesleycho Your fix is definitely a step in the right direction, but I feel that there should be a way to keep the alert on the screen by passing a blank (invalid) number or -1.
Using -1 would be the best option as IE 8 and lower don't fire the callback setTimeout function if the value is negative.

As we are mainly supporting 1.3+, we are not supporting IE8

As per my comments, I believe this approach should not be handled by the library itself, as this is too much of an edge case that has a legitimate workaround on the developer's side.


Rename index.js.gz to entrypoint.js.gz

Pull Request Description
This is required because index.ts was renamed to entrypoint.ts in order to avoid colliding with the main export of the enso-dashboard module, which is used by gui2 as dashboard.run(). This file was renamed in #8587, causing the issue.
Build script changes also included thanks to @mwu-tow.
Important Notes
This should only affect projects opened against the remote (cloud) backend, meaning that to test this, you should open a project against the cloud backend.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

@somebody1234 please fix ci and you can merge

oh, seems like the CI error is from java artifacts, a merge with develop should fix it. will do asap.


How to configure tool.uv.overrids-dependencies in pyproject.toml, I can't find an example in the documentation.

How to configure tool.uv.overrids-dependencies in pyproject.toml, I can't find an example in the documentation.

There's an example in the reference: https://docs.astral.sh/uv/reference/settings/#override-dependencies


Update Settings page with updated UI

Reference - https://www.figma.com/file/bVPRRw282CqGKMdbz7dciH/HC-Ionic-design-system?node-id=23579%3A83419&t=EwnGrKo71tXMohaa-0

@shashwatbangar
I think there is a UI issue, heading are too close to menu


Do not change visibility when sorting

Hopefully fixes #141 . Updates the SortNodes visitor to preserve visibility of nodes. So, a file that looks like
class MyClass
def zethod2; end
def zethod1; end
private
def c; end
def b; end
end

will get sorted as
class MyClass
def zethod1; end
def zethod2; end
private
def b; end
def c; end
end

rather than as
class MyClass
def b; end
def c; end
private
def zethod1; end
def zethod2; end
end

I think there is a better way to do this by using partition and sorting each of the partitions independently. If we did that, we wouldn't have to do all the manual offset calculations that are present in this PR.

After looking into partition, I realized that my original approach was wrong: visibility modifiers can be repeated, so there can be an arbitrary number of chunks. The helpful partition suggestion from @paracycle got me looking into other ruby array methods I don't know, and I found chunk which I think makes things much clearer.
It does increase allocations, but perhaps that is a good tradeoff here, since this isn't runtime code?
@KaanOzkan the code is now much shorter, so perhaps the helper method is not needed? I am on the fence, but leaned towards keeping it inline so that the flow is clear and matches the existing structure more closely.


Project setup fails using backup.dump file

Describe the bug
The backup.dump file that we are including in our setup instructions is causing the Django migrations to fail. The main reason is that the sequences for some tables are not being exported correctly.
I noticed this when I was trying to run migrations and would get an null constraint error. Checking the django_migrations table I saw the sequence was missing.
To Reproduce
Steps to reproduce the behavior:

Follow the setup steps, it'll fail when trying to run the migrations.

Expected behavior
Migrations should be applied without an error.
Screenshots
Error can be seen here https://github.com/TheIndexingProject/contratospr-api/pull/86#issuecomment-546641444
Additional context
I think the best way to solve this for future contributors / users is to not have the backup.dump and export the data using the manage.py dumpdata command. The resulting file can then be used after all migrations have been made. This way we let the framework do it's job.

This should block PR #86
Once this is resolved we can merge the changes into the add-setup branch and proceed with the PR.

Best to create a new dump from production. That last migration was created after the dump was made. I'll do this.

@froi try this one instead.
https://s3.amazonaws.com/data.contratospr.com/2019-10-27/backup.dump

What options are you using for the dump? I also made a new dump and had the same error.

@froi pg_dump -Fc --no-acl --no-owner -h HOSTNAME -p PORT -U USERNAME contratospr-api > docker/postgres/backup.dump

I’ll import it and make sure that the sequences are there. Thanks!

To clarify, the error was never about the data. It was all about what was included in the export. I think we’re better off letting Django do it’s thing and have some test data that people can import.

The issue was with the volumes and images that docker/docker-compose had already made. Since the images and volumes where already there and the init.sh script for the postgres container/image was being ignored. This would prevent the correct backup.dump file to be imported and would in turn cause the sequences in the DB to never exist and make our migrations fail.
The answer to solve this is to wipe everything related to the docker-compose images and resources. To accomplish this we can just run docker-compose down --rmi all -v --remove-orphans.
This is solved and unblocks #86 .


fix: fix labels in issue templates

Issue number:

#1105

Summary
Fixes the drops dow the issue templates
Changes

Please provide a summary of what's being changed

Update dropdown format to be matching the GitHub docs:

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms

User experience

Please share what the user experience looks like before and after this change

Drop downs now match what the user should be capturing.

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[X] Meet tenets criteria
[x] I have performed a self-review of my this change
[x] Changes are tested
[ ] Changes are documented
[x] PR title follows conventional commit semantics

Is this a breaking change?
RFC issue number:
Checklist:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Codecov Report

Merging #1106 (c5c7f40) into develop (f24332d) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1106   +/-   ##
========================================
  Coverage    99.96%   99.96%
========================================
  Files          119      119
  Lines         5377     5378    +1
  Branches       613      613
========================================
+ Hits          5375     5376    +1
  Partials         2        2

Impacted Files
Coverage Δ

...ws_lambda_powertools/middleware_factory/factory.py
100.00% <0.00%> (ø)

...ws_lambda_powertools/utilities/idempotency/base.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

@heitorlessa for review and testing i cloned the templates here:

https://github.com/michaelbrewer/powertools-issue-template/issues/new/choose

Hi @michaelbrewer - as per the contribution guidelines, please wait until the issue has been trusted before creating a pull redirect.

@sthulb sure. Just wanted to demonstrate the fix. Looking forward to the issue being resolved.

As per #1105, this has been resolved elsewhere


Fixes in VlcMedia

Added Error property which is filled if State == Error
Added Detach of event callbacks in Dispose to fix
"CallbackOnCollectedDelegate" error in some cases
Fixed StateChanged event - for some reasons value in the event args
coming from libvlc internals is strange and does not belong to
MediaState enumeration, so call _getStateFunction explicitly to get
actual state value and provide it to subscribers

Thanks for your contributions


MSID: 95304 Version: 1 DOI: 10.1101/2<IP_ADDRESS>1720

MSID: 95304
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>1720
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=95304
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>1720

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/95304v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>1720
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/95304/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

There are various issues with this one that need fixing, especially in the supplementary info.
Also this ref could be cleaned up:


Wait until nodes have pod-cidrs before start cilium

While checking the logs from https://github.com/cilium/cilium/issues/3993#issuecomment-391520696
I've noticed the pod cidrs of one of the node was not the one given by kubernetes.
Correct node:
2018-05-23T15:21:12.933489014Z level=debug msg="Empty IPv6 health endpoint annotation in node" k8sNodeID=a573e16f-5e98-11e8-a07e-08002740ae4f nodeName=k8s1 subsys=k8s
2018-05-23T15:21:12.933505937Z level=info msg="Retrieved node information from kubernetes" nodeName=k8s1 subsys=k8s
2018-05-23T15:21:12.933521389Z level=info msg="Received own node information from API server" ipAddr.ipv4=<IP_ADDRESS> ipAddr.ipv6="<nil>" nodeName=k8s1 subsys=k8s
2018-05-23T15:21:12.933563624Z level=info msg="Retrieved IPv4 allocation range for node. Using it for ipv4-range" node=k8s1 v4Prefix=<IP_ADDRESS>/16
2018-05-23T15:21:12.933579841Z level=info msg="Automatically retrieved IP for node. Using it for ipv4-node" ipAddr=<IP_ADDRESS> node=k8s1
2018-05-23T15:21:12.933593918Z level=info msg="Initializing node addressing"
2018-05-23T15:21:12.933608387Z level=info msg="Using autogenerated IPv6 allocation range" v6Prefix="f00d::a0a:0:0:0/96"

Incorrect node:
2018-05-23T15:21:10.301661991Z level=debug msg="Empty IPv6 health endpoint annotation in node" k8sNodeID=c406276b-5e9c-11e8-a07e-08002740ae4f nodeName=k8s2 subsys=k8s
2018-05-23T15:21:10.301679173Z level=info msg="Retrieved node information from kubernetes" nodeName=k8s2 subsys=k8s
2018-05-23T15:21:10.30172944Z level=info msg="Received own node information from API server" ipAddr.ipv4=<IP_ADDRESS> ipAddr.ipv6="<nil>" nodeName=k8s2 subsys=k8s
2018-05-23T15:21:10.301751647Z level=info msg="Automatically retrieved IP for node. Using it for ipv4-node" ipAddr=<IP_ADDRESS> node=k8s2
2018-05-23T15:21:10.301767378Z level=info msg="Initializing node addressing"
2018-05-23T15:21:10.301935408Z level=info msg="Using autogenerated IPv4 allocation range" v4Prefix=<IP_ADDRESS>/16
2018-05-23T15:21:10.301976802Z level=info msg="Using autogenerated IPv6 allocation range" v6Prefix="f00d::a0f:0:0:0/96"

If the tests are not being set up with the exact same cilium spec file provided in examples/kubernetes/1.x should wait until all nodes have the pod-cidrs.
If the tests are being set up with the same cilium spec file cilium-agent should wait until the node has a pod cidr assigned. how? maybe getting the list of all other nodes and check if all of them have a pod-cidr assigned.

Should be fixed by https://github.com/cilium/cilium/pull/4219

@aanm I updated the cilium daemonsets in test, but I still see this error on Nightly [0]
The nodes are not sync, and I'm see this error, examples:
k8s1
2018-05-31T09:35:31.812053521Z level=info msg="Connected to k8s api-server" ipAddr="https://<IP_ADDRESS>:443" subsys=k8s
2018-05-31T09:35:31.815684591Z level=info msg="Retrieved node information from kubernetes" nodeName=k8s1 subsys=k8s
2018-05-31T09:35:31.81570096Z level=info msg="Received own node information from API server" ipAddr.ipv4=<IP_ADDRESS> ipAddr.ipv6="<nil>" nodeName=k8s1 subsys=k8s
2018-05-31T09:35:31.815704389Z level=info msg="Retrieved IPv4 allocation range for node. Using it for ipv4-range" node=k8s1 v4Prefix=<IP_ADDRESS>/16
2018-05-31T09:35:31.815715457Z level=info msg="Automatically retrieved IP for node. Using it for ipv4-node" ipAddr=<IP_ADDRESS> node=k8s1
2018-05-31T09:35:31.81571779Z level=info msg="k8s mode: Allowing localhost to reach local endpoints"
2018-05-31T09:35:31.815740189Z level=info msg="Initializing node addressing"
2018-05-31T09:35:31.815881623Z level=info msg="Using autogenerated IPv6 allocation range" v6Prefix="f00d::a0a:0:0:0/96"
2018-05-31T09:35:31.815891256Z level=info msg="Annotating k8s node with CIDR ranges"

k8s2
2018-05-31T09:35:31.325306551Z level=info msg="Initializing node addressing"
2018-05-31T09:35:31.325424356Z level=info msg="Using autogenerated IPv4 allocation range" v4Prefix=<IP_ADDRESS>/16
2018-05-31T09:35:31.325433911Z level=info msg="Using autogenerated IPv6 allocation range" v6Prefix="f00d::a0f:0:0:0/96"
2018-05-31T09:35:31.325438495Z level=info msg="Annotating k8s node with CIDR ranges"

k8s3
2018-05-31T09:35:35.676476203Z level=info msg="Initializing node addressing"
2018-05-31T09:35:35.676513577Z level=info msg="Using autogenerated IPv4 allocation range" v4Prefix=<IP_ADDRESS>/16
2018-05-31T09:35:35.676517761Z level=info msg="Using autogenerated IPv6 allocation range" v6Prefix="f00d::a0f:0:0:0/96"
2018-05-31T09:35:35.676519786Z level=info msg="Annotating k8s node with CIDR ranges"

k8s4
2018-05-31T09:35:33.660485652Z level=info msg="Initializing node addressing"
2018-05-31T09:35:33.660600561Z level=info msg="Using autogenerated IPv4 allocation range" v4Prefix=<IP_ADDRESS>/16
2018-05-31T09:35:33.660624439Z level=info msg="Using autogenerated IPv6 allocation range" v6Prefix="f00d::a0f:0:0:0/96"
2018-05-31T09:35:33.660628799Z level=info msg="Annotating k8s node with CIDR ranges"

Nightly is suffering because of this, could you point to me what changes I'm missed from the daemonsets?
Thanks.
2811a558_NightlyPolicies_PolicyEnforcement_default_L3_No_Policy_L4_No_Policy_L7_No_Policy_Destination_service(1).zip
[0] https://jenkins.cilium.io/job/Cilium-PR-Nightly-Tests-All/123/testReport/

@eloycoto You are probably not missing anything from the daemonsets, you just need to make sure all nodes have a pod-cidr before starting cilium.
Something like this:https://github.com/cilium/cilium/blob/aa5036402d86533a867f3fda1739cf3719ed0267/contrib/vagrant/start.sh#L336-L343

assigned @tgraf based on the discussion we had offline that cilium needs to be aware of the pod CIDR on the node that is running.

@eloycoto was this fixed by https://github.com/cilium/cilium/commit/f9ba47b3cef1a2ff0b18ea826cdb87bae97aa985 ?

@ianvernon that was a workaround in the installation to not fail. The fix I think that is #4330

#4275 was seen again today on jerking master
https://jenkins.cilium.io/job/cilium-ginkgo/job/cilium/job/master/973/

@manalibhutiyani that build is related to https://github.com/cilium/cilium/issues/4384 the nodes anotation is correct.

We have not seen this since


some errors at backend

Great work， and some error when I post at backend:
推送微信失败 : cURL error 52: Empty reply from server (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
Alex

Also, it always caused 502, so whether it support Wordpress MU sites?
Thanks.
Alex

sorry for miss this issue, cURL error 52 maybe is network error. Tell me your php and wordpress version, i will build a demo site to reappears it.

Thanks for reply.
PHP version: 5.6.14
Wordpress: 4.5
LNMP
I just guess Visual Composer caused cURL error 52.
As to 502 Error and Wordpress MU, please check at https://codex.wordpress.org/Glossary#Multisite
Thanks again.
Alex

Hello,
it caused an error message when I push a event post with the plugin of "The Events Calendar"(https://wordpress.org/plugins/the-events-calendar/) :
media data missing hint: [aQjKMa0144e547]
does it support other custom post?  Thanks a lot.
Alex


[WIP][CONNECT] Scala client collection functions

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Adding test cases


[README] Issue165 readme figures

Added figures and updated README.rst
Fixes, in devel, Issue #165

Codecov Report

Merging #168 into devel will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            devel     #168   +/-   ##
=======================================
  Coverage   45.17%   45.17%
=======================================
  Files          70       70
  Lines       20612    20612
=======================================
  Hits         9311     9311
  Misses      11301    11301

Impacted Files
Coverage Δ

tofu/version.py
100% <ø> (ø)
:arrow_up:

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 c6aee52...6190317. Read the comment docs.


Videos on Iphone/Ipad

Hi,
in the config it is possible to encode videos as mp4 instead of webm. This would allow to see this videos also on Safari-devices. However, there some issues: (using the galleria theme)

Obviously, the mime-type is always: type='video/webm'

But the html tags cause also some problems. What I found on the Internet, the html should look like here: http://www.justinwhall.com/html5-video-playing-ios-devices
I tried to play around with the index.html a bit, but I think the theme makes it more complicated...

For the galleria theme the mime type is hard-coded, this is easy to fix:
https://github.com/saimn/sigal/blob/master/sigal/themes/colorbox/templates/index.html#L87
https://github.com/saimn/sigal/blob/master/sigal/themes/galleria/templates/index.html#L150
But I don't understand your second point, the HTML in your link is similar to the one used in the templates, so ?

What I mean is, it seems the Safari browser expects a syntax like:
<video controls> 	<source src="movie.mp4" type='video/mp4'> </video>
But in https://github.com/saimn/sigal/blob/master/sigal/themes/galleria/templates/index.html#L147 - 149 is also the filename referenced and this might confuse the browser ?
At least only changing the mime type don't fix the issue. But after trying around, one time the video was played, when I was heavily scrolling between the pictures/videos. I'm not an expert, but I guess it might be related with the additional file references ?

I fixed the mime-type, but I don't understand the filename issue: <source src='{{ media.filename }}' ... will generate the same line as the one from your example, there is no "additional file references".

The <video.....> sequence is within the data-layer tag. I think Safari has difficulties to interpret this.

The sequence is within the data-layer tag

Sorry but I don't understand ?

Just released version 1.1.0, please check and reopen if the issue is still there.

Works, thanks a lot!


New version: Microsoft.Teams.Exploration version <IP_ADDRESS>880

ARP entries are correct.
Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 650
Microsoft Reviewers: Open in CodeFlow

This is CD build (50-99). 32880
Exploration usually has 00-49 at the end of the of the build number.

It seems that the issue is because I am using the same variables in both scripts.


Facing issue in firefox

Hi,
i use demo but i got error in alert box when i open demo in firefox in chrome working fine.
This is the error :- "Webcam.js Error: Could not access webcam"
if i use userMedia: true then working on chrome but not in firefox.
if i use userMedia: false then working on firefox but not in chrome.
so please tell me what is this option and what i have to do?
Please help on this ASAP.
Thanks,

Hey,
Got it i just remove navigator.mozGetUserMedia and window.mozURL from init: function() and set userMedia: true now i can open it in mozila firefox and chrome.
Now please tell me this is right or it make some issue on live?
Thanks,

Sounds like you have a webcam that only works in Flash.  Try setting "force_flash" parameter to true.
http://pixlcore.com/demos/webcamjs/demos/flash.html

Hi,
Thanks for your reply, please help on one more thing.
i set force_flash: true,
Your given link is work on some of my system but not on all system, i remove all cache but same thing happen with my demo.
Thanks.

Video is not supported, sorry.  If you want to capture video, please check out WebRTC:
http://www.webrtc.org/
I am sorry the library doesn't work on all your systems.  Please try jQuery Webcam -- you might have better luck with that library:
http://www.xarg.org/project/jquery-webcam-plugin/
Good luck to you.

NAVER - http://www.naver.com/
<EMAIL_ADDRESS>님께 보내신 메일 <Re: [webcamjs] Facing issue in firefox (#71)> 이 다음과 같은 이유로 전송 실패했습니다.

받는 사람이 회원님의 메일을 수신차단 하였습니다.


MediaController addListener receives a Player.Listener which has a onSkipSilenceEnabledChanged, but it doesn't get called

Version
Media3 1.2.1
More version details
Not applicable
Devices that reproduce the issue
Not applicable
Devices that do not reproduce the issue
Not applicable
Reproducible in the demo app?
Not applicable
Reproduction steps
If you call exoPlayer.addListener(...) and your listener implements onSkipSilenceEnabledChanged, then that will be called whenever you change the value of exoPlayer.skipSilenceEnabled.
However, if you have a media controller, which you obtain as follows: private val controllerFuture = MediaController.Builder(         context,         SessionToken(context, ComponentName(context, PlaybackService::class.java))     ).buildAsync()
And you implement onSkipSilenceEnabledChanged in controller.addListener(listener), the method will never be called.
Expected result
The method is called.
Actual result
The method is not called.
Media
Not applicable
Bug Report

[ ] You will email the zip file produced by adb bugreport to<EMAIL_ADDRESS>after filing this issue.

Hi @Digipom,
As you rightly pointed out, https://github.com/androidx/media/issues/1027 is a related issue and, in fact, they are completely dependent. So I will close this issue as a duplicate and leave the other one as an enhancement tracker.
To give you more context:
When a setter is called on Exoplayer, the new value is passed to all the listeners as listener.onSkipSilenceEnabledChanged
https://github.com/androidx/media/blob/b930b40a16c06318e43c81771fa2b1024bdb3f29/libraries/exoplayer/src/main/java/androidx/media3/exoplayer/ExoPlayerImpl.java#L1549-L1560
Similarly, if Player interface had its own setSkipSilenceEnabled method (i.e. what you wanted in https://github.com/androidx/media/issues/1027), it would be overriden-implemented by MediaController (or specifically in MediaControllerImplBase) in a similar way to ExoPlayer above. You can take a look at that class to see how other setters have code like
listeners.queueEvent(
          /* eventFlag= */ Player.EVENT_SOMETHING_CHANGED,
          listener -> listener.onSOMETHINGChanged(SOMETHING));

Even though the Player.Listener interface currently has a onSkipSilenceEnabledChanged method, it will not be triggered inside MediaController until MediaController.setSkipSilenceEnabled exists and for that we need Player interface to get its own setSkipSilenceEnabled method.

Thanks, for now I worked around using media session extras. It seems the API is halfway to being fully implemented, so having it fully connected will be nice. :)

@Digipom can you please provide an example or how to send "setSilence" command from UI to MediaSession Service?

Certainly.

Service:

        session =
            MediaSession.Builder(this, player)
                .setCallback(CustomMediaSessionCallback(player))
                .build()

companion object {
        const val ENABLE_SKIP_SILENCE = "ENABLE_SKIP_SILENCE"
        const val DISABLE_SKIP_SILENCE = "DISABLE_SKIP_SILENCE"
        const val EXTRA_IS_SKIP_SILENCE_ENABLED = "EXTRA_IS_SKIP_SILENCE_ENABLED"
    }

Callback:

@androidx.media3.common.util.UnstableApi
private class CustomMediaSessionCallback(private var exoPlayer: ExoPlayer) : MediaSession.Callback {
    override fun onConnect(
        session: MediaSession,
        controller: MediaSession.ControllerInfo
    ): MediaSession.ConnectionResult {
        val sessionCommands = MediaSession.ConnectionResult.DEFAULT_SESSION_COMMANDS.buildUpon()
            .add(SessionCommand(ENABLE_SKIP_SILENCE, Bundle.EMPTY))
            .add(SessionCommand(DISABLE_SKIP_SILENCE, Bundle.EMPTY))
            .build()

        return MediaSession.ConnectionResult.AcceptedResultBuilder(session)
            .setAvailableSessionCommands(sessionCommands)
            .setSessionExtras(Bundle().apply {
                putBoolean(EXTRA_IS_SKIP_SILENCE_ENABLED, exoPlayer.skipSilenceEnabled)
            })
            .build()
    }

    override fun onCustomCommand(
        session: MediaSession,
        controller: MediaSession.ControllerInfo,
        customCommand: SessionCommand,
        args: Bundle
    ): ListenableFuture<SessionResult> {
        return when (customCommand.customAction) {
            ENABLE_SKIP_SILENCE -> {
                exoPlayer.skipSilenceEnabled = true
                Futures.immediateFuture(SessionResult(SessionResult.RESULT_SUCCESS))
            }

            DISABLE_SKIP_SILENCE -> {
                exoPlayer.skipSilenceEnabled = false
                Futures.immediateFuture(SessionResult(SessionResult.RESULT_SUCCESS))
            }

            else -> {
                super.onCustomCommand(session, controller, customCommand, args)
            }
        }
    }
}

Controller:

private val mediaControllerListener = MediaControllerListener(
        onSkipSilenceUpdate = { skipSilenceEnabled ->
            if (DEBUG_LOGGING_ON) {
                Logger.d("Updating is skip silence enabled to $skipSilenceEnabled")
            }
            _skipSilenceEnabled.update { skipSilenceEnabled }
        }
    )

private val controllerFuture = MediaController.Builder(
        context,
        SessionToken(context, ComponentName(context, PlaybackService::class.java))
    ).setListener(mediaControllerListener)
        .buildAsync()

private val _skipSilenceEnabled = MutableStateFlow(false)
val skipSilenceEnabled = _skipSilenceEnabled.asStateFlow()

suspend fun setSkipSilenceEnabled(skipSilenceEnabled: Boolean) {
        if (DEBUG_LOGGING_ON) {
            Logger.v("setSkipSilenceEnabled($skipSilenceEnabled)")
        }
        obtainController()?.apply {
            sendCustomCommand(
                SessionCommand(
                    when (skipSilenceEnabled) {
                        true -> PlaybackService.ENABLE_SKIP_SILENCE
                        false -> PlaybackService.DISABLE_SKIP_SILENCE
                    }, Bundle.EMPTY
                ), Bundle.EMPTY
            )
        }
    }


Enhances intuitiveness of RawMagnifier's example

Demo

Before
After

Related issue
Fixes https://github.com/flutter/flutter/issues/150307
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Hi @justinmc, could you help to review this PR? :)


SwitchBot API v1.1 with SecretToken not implemented

I wanna use the Adapter for my Air conditioner IR, but can't.
So Ive taken a look and seen, that  SwitchBot Api is switch to v1.1 and also uses the secret Token.
https://github.com/OpenWonderLabs/SwitchBotAPI
Is it possible to implemented it?

check this
https://github.com/arteck/ioBroker.switchbot-hub


Error:Execution failed for task ':app:ndkBuild'. > A problem occurred starting process 'command 'ndk-build.cmd''

what your OS ? i got an error like you (in windows), i have resolved with Add the ndk path (your ndk path) to the path variable's value in the environment variable(System variable) which left my "path" variable like this
Settings --> System --> Advenced System Settings --> System Variables,
after that, you have to restart your IDE or CMD


Optimize compareTo in Router to guarantee consistent behaviour.

fix issue https://github.com/apache/incubator-dubbo/issues/3302
remove useless implement and the duplicate compareTo logic,use getPriotity instead.

changes are as below:

remove the duplicate interface Comparable since Router extends.
replace the compare logic from compareTo to getPriority. Router subclass should define its own priotity to decide its order on the chian.

Codecov Report

Merging #3566 into master will increase coverage by 0.24%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #3566      +/-   ##
============================================
+ Coverage      64.2%   64.45%   +0.24%
  Complexity       71       71
============================================
  Files           664      664
  Lines         28629    29096     +467
  Branches       4771     4922     +151
============================================
+ Hits          18382    18753     +371
- Misses         8025     8090      +65
- Partials       2222     2253      +31

Impacted Files
Coverage Δ
Complexity Δ

...ster/router/condition/config/ListenableRouter.java
33.33% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../rpc/cluster/router/condition/ConditionRouter.java
68.05% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../rpc/cluster/router/mock/MockInvokersSelector.java
94.44% <100%> (+0.15%)
0 <0> (ø)
:arrow_down:

...cluster/router/condition/config/ServiceRouter.java
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

.../dubbo/rpc/cluster/router/script/ScriptRouter.java
68.18% <100%> (+5.68%)
0 <0> (ø)
:arrow_down:

...pache/dubbo/rpc/cluster/router/AbstractRouter.java
45% <100%> (+2.89%)
0 <0> (ø)
:arrow_down:

...main/java/org/apache/dubbo/rpc/cluster/Router.java
50% <100%> (+10%)
0 <0> (ø)
:arrow_down:

...rpc/cluster/router/condition/config/AppRouter.java
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

...apache/dubbo/rpc/cluster/router/tag/TagRouter.java
39.5% <100%> (ø)
0 <0> (ø)
:arrow_down:

...ache/dubbo/remoting/p2p/support/AbstractGroup.java
45.45% <0%> (-11.37%)
0% <0%> (ø)

... and 19 more

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 05a98f3...34e4a69. Read the comment docs.

LGTM.


linux-54 lost external connection phone device.

Is there an existing issue for this?

[X] I have searched the existing infra issues

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
linux-54 lost external connection phone device.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

External connection has been restored by rebooting phone device.


Data editor doesn't enclose pre-existing filters in parentheses when adding new conditions, messing precedence

System information:

Operating system (distribution) and version: Windows 10 Pro 21H1
DBeaver version: 21.3.1
Additional extensions: Office support, git support, SSHJ, Debug and SVG

Connection specification:

Database name and version: Postgresql 14.1
Driver name: PostgreSQL JDBC Driver
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
If I use the filter bar of the data editor to manually enter a condition that contains an OR, then click on the filter icon of a column to filter by selected values of that column, the resulting filter fails to enclose the initial OR condition in parentheses, which might return an unexpected result set.
For example, if my initial filter is a > 50 OR b > 50, I click on the filter icon of column c and select only value 10, the resulting predicate in the filter bar becomes something like c IN (10) AND a > 50 OR b > 50, which evaluates the AND before the OR. The expected filter would be c IN (10) AND (a > 50 OR b > 50).
Steps to reproduce, if exist:

Create testing set:

CREATE TABLE test (
	a integer,
	b integer,
	c integer
);

INSERT INTO test
	SELECT
		random() * 100,
		random() * 100,
		random() * 100
	FROM generate_series(1, 1000) as n;

With table test open in data editor, manually enter a > 50 OR b > 50 into the filter bar and press Enter

Now click on the funnel icon of column c and select any value(s) to filter by.

Check the filter bar to confirm the resulting filter is now wrong (or rather different than one would expect).

Include any warning/errors/backtraces from the logs

No erros raised, just a logical bug.

@ivanlonel Thank you for the report. We will fix it.

Verified


Docker image updates

Pull Request Type

[ ] ✨ feat
[ ] 🐛 fix
[ ] ♻ refactor
[ ] 💄 style
[x] 🔨 chore
[ ] 📝 docs

Relevant Issues

resolves #xxx
What is in this change?

Improves Docker Scout Rating (E->B)
Adds SBOM and Attestations for Docker Repo
Bumps patch for mysql pkg due to reported CVE
Bumps Base image to latest jammy

Additional Information
Tested the stuff that would likely be impacted by this. No breaking changes.
TODO:

Bump jsonwebtoken (breaking)
Bump express-ws (no longer maintained, need to fork?)

Developer Validations

[x] I ran yarn lint from the root of the repo & committed changes
[x] Relevant documentation has been updated
[x] I have tested my code functionality
[x] Docker build succeeds locally

G2g


keys in Glyphs userData{UFO.lib{}} should be exported to root of lib.plist

When importing a UFO, Glyphs dumps any lib.plist keys it doesn't recognize into userData{UFO.lib{}}. On manual export it then moves those back out of that subkey in to the root of lib.plist. I've confirmed that this is intentional on Glyphs's part. Examples of such keys:

public.postscriptNames
any custom keys (such as org.sil.altLineMetrics, org.sil.lcg.transforms)

write_ufo should follow Glyphs's export behaviour and restore these keys to the root of lib.plist instead of leaving them in a UFO.lib key.
This will also help to avoid the problem where a font ends up with two public.postscriptNames keys, a complete one in UFO.lib and a strangely minimal one in the root.

write_ufo should follow Glyphs's export behaviour and restore these keys to the root of lib.plist instead of leaving them in a UFO.lib key.

@jvgaultney It makes sense. I had never seen that UFO.lib inside userData, as I haven't used much Glyphs.app's native UFO import/export.
So basically, we need to move all the data that's inside this "UFO.lib" dictionary from the userData, back to the UFO lib.plist.

This should be fixed now

is this still an issue in glyphsLib? (I guess it is)

and what happens when one uses glyphsLib to import a UFO to .glyphs and the UFO contains some custom user-defined data in the lib.plist? Shouldn't glyphsLib also store it in userData, like Glyphs.app does?
I don't think it does that, does it?

what happens when one uses glyphsLib to import a UFO to .glyphs and the UFO contains some custom user-defined data in the lib.plist?

This is already working as intended. The data is imported in the GSFontMaster.userData (it will be under font.masters[0].userData for the first master, etc.)


Automatic Python scraping

Opening this issue as a (self-)reminder.
I have sketched this flowchart as a discussion starter:

It does not look very complex, GitHub already has examples running Python: https://github.com/actions/starter-workflows/blob/ffb4bccd2d52e308ec66fa63f218d93db6dd94a1/ci/python-app.yml
And there are other promising examples out there.

Note that we can run all together in the same GitHub Action, i.e. we can integrate the scrapper in the action that we already have.
Also we can adapt the trigger (now it is in every commit/PR, but we can schedule it via cron or set a manual trigger.

I have created an integrated action with the scraper and the map creation altogether, I suggest working on this direction adding your own improvements on dev branch.
https://github.com/dieghernan/RKI-Corona-Atlas/blob/master/.github/workflows/corona-atlas.yml

I have finished the action integration, the next running time should be 19h CET.
Please note on.push.paths and the like:
https://github.com/dieghernan/RKI-Corona-Atlas/blob/09ef69d9d79797bac9d986a6c179ba7135a98eb9/.github/workflows/corona-atlas.yml#L3-L19
If I understood it correctly, map pages are built from the database and the sources in _R so I made that step conditional to avoid periodic unnecessary rebuilds and commits. Review it and change it if needed, please.


Implementation of multiprocessing for the fit generator

Implementation of multiprocessing for the fit generator (cf. #2730)

All tests are failing.

Interesting, most of the tests failing here passed on my build (which is the latest master). I'll track all issues and update the PR.

Threading behavior may be different on Travis than it is on your local
machine. It seems like the tests never finish, which implies that a process
is started that never gets terminated.
On 20 June 2016 at 16:17, Thibault de Boissière<EMAIL_ADDRESS>wrote:

Interesting, most of the tests failing here passed on my build (which is
the latest master). I'll track all issues and update the PR.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/pull/3028#issuecomment-227298014, or mute
the thread
https://github.com/notifications/unsubscribe/AArWb5u_nc6tfNIBm3fqloEJcii7VHMGks5qNx9ygaJpZM4I5omj
.


should use an identifiable UserAgent so admins can identify in logging

working on this alongside #12

addressed this on #17 (and released it on version 1.0.28). This now uses GetMoarFediverse as its user agent.


Incompatible with latest flowbite-svelte version due to semver functioning

In package.json, a devDependency is stated as flowbite-svelte ^0.34.1. Since the latest flowbite-svelte version is 0.36.X, this causes a conflict because "in semver when you use 0.2.x, 2 isn't a major version. That's why docs.npmjs.com used the specific words: the left-most non-zero digit".
I propose using instead >= to ensure that this package does not always have to be updated whenever "minor" versions of flowbite-svelte are changed.

Can you run pnpm i -D flowbite-svelte@latest?

Can you run pnpm i -D flowbite-svelte@latest?

Don't usually use pnpm, but in any case:
 WARN  Issues with peer dependencies found
.
└─┬ flowbite-svelte-blocks 0.3.6
  └── ✕ unmet peer<EMAIL_ADDRESS>found 0.36.2

The installation works, but there's the same warning.

Can you try this and let me know:
// for npm
rm ./package-lock.json
rm -rf ./node_modules
npm i

Can you try this and let me know:
// for npm
rm ./package-lock.json
rm -rf ./node_modules
npm i

Still getting the same issue.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/flowbite-svelte
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/flowbite-svelte-blocks
npm ERR!   flowbite-svelte-blocks@"latest" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/redacted/.npm/_logs/2023-05-20T09_04_08_584Z-eresolve-report.txt

npm ERR!      /Users/redacted/.npm/_logs/2023-05-20T09_04_08_584Z-debug-0.log

Can you share your repo?

Can you share your repo?

The repo is private, so I'll just provide the package.json. I've tested creating a fresh project with this JSON file and confirmed that the issue persists like that (with npm).
{
  "name": "client",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "dev": "vite dev",
    "build": "vite build",
    "preview": "vite preview",
    "lint": "eslint ."
  },
  "devDependencies": {
    "@popperjs/core": "^2.11.6",
    "@sveltejs/adapter-auto": "^1.0.0-next.91",
    "@sveltejs/kit": "^1.18.0",
    "@tailwindcss/typography": "^0.5.9",
    "@tsconfig/svelte": "^3.0.0",
    "@typescript-eslint/eslint-plugin": "^5.51.0",
    "@typescript-eslint/parser": "^5.51.0",
    "autoprefixer": "^10.4.7",
    "classnames": "^2.3.2",
    "devalue": "^4.3.1",
    "eslint": "^8.34.0",
    "eslint-plugin-svelte3": "^4.0.0",
    "flowbite": "^1.6.3",
    "flowbite-svelte": "^0.36.2",
    "postcss": "^8.4.14",
    "postcss-load-config": "^4.0.1",
    "svelte-check": "^3.0.3",
    "svelte-preprocess": "^4.10.7",
    "tailwindcss": "^3.1.8",
    "typescript": "^4.9.5",
    "vite": "^4.0.0"
  },
  "type": "module",
  "dependencies": {
    "@n8body/tiptap-spoiler": "^1.0.4",
    "@tailwindcss/forms": "^0.5.3",
    "@tiptap/core": "^2.0.0-beta.220",
    "@tiptap/extension-character-count": "^2.0.0-beta.220",
    "@tiptap/extension-highlight": "^2.0.0-beta.220",
    "@tiptap/extension-mention": "^2.0.3",
    "@tiptap/extension-placeholder": "^2.0.3",
    "@tiptap/extension-typography": "^2.0.0-beta.220",
    "@tiptap/pm": "^2.0.0-beta.220",
    "@tiptap/starter-kit": "^2.0.0-beta.220",
    "@tiptap/suggestion": "^2.0.3",
    "axios": "^1.1.3",
    "flowbite-svelte-blocks": "latest",
    "svelte": "^3.55.1",
    "svelte-heros": "^2.6.0",
    "tippy.js": "^6.3.7"
  }
}

Can you run npm i flowbite-svelte-blocks@latest and let me know.

Can you run npm i flowbite-svelte-blocks@latest and let me know.

npm install works now, thank you for the fix!


[Snyk] Upgrade core-js from 3.22.8 to 3.26.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade core-js from 3.22.8 to 3.26.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 15 versions ahead of your current version.
The recommended version was released 22 days ago, on 2022-10-23.

Release notes

Package name: core-js

3.26.0 - 2022-10-23
Array.fromAsync proposal:

Moved to Stage 3, September TC39 meeting
Avoid observable side effects of %Array.prototype.values% usage in array-like branch, proposal-array-from-async/30

Added well-formed unicode strings stage 2 proposal:

String.prototype.isWellFormed
String.prototype.toWellFormed

Recent updates of the iterator helpers proposal:

Added a counter parameter to helpers, proposal-iterator-helpers/211
Don't await non-objects returned from functions passed to AsyncIterator helpers, proposal-iterator-helpers/239
{ Iterator, AsyncIterator }.prototype.flatMap supports returning both - iterables and iterators, proposal-iterator-helpers/233
Early exit on broken .next in missed cases of { Iterator, AsyncIterator }.from, proposal-iterator-helpers/232

Added self polyfill as a part of The Minimum Common Web Platform API, specification, #1118
Added inverse option to core-js-compat, #1119
Added format option to core-js-builder, #1120
Added NodeJS 19.0 compat data
Added Deno 1.26 and 1.27 compat data
Added Opera Android 72 compat data mapping
Updated Electron 22 compat data mapping

3.25.5 - 2022-10-03
Fixed regression with an error on reuse of some built-in methods from another realm, #1133

3.25.4 - 2022-10-02
Added a workaround of a Nashorn bug with Function.prototype.{ call, apply, bind } on string methods, #1128
Updated lists of [Serializable] and [Transferable] objects in the structuredClone polyfill. Mainly, for better error messages if polyfilling of cloning such types is impossible
Array.prototype.{ group, groupToMap } marked as supported from V8 ~ Chromium 108
Added Electron 22 compat data mapping

3.25.3 - 2022-09-25
Forced polyfilling of Array.prototype.groupToMap in the pure version for returning wrapped Map instances
Fixed existence of Array.prototype.{ findLast, findLastIndex } in /stage/4 entry
Added Opera Android 71 compat data mapping
Some stylistic changes

3.25.2 - 2022-09-18
Considering document.all as a callable in some missed cases
Added Safari 16.0 compat data
Added iOS Safari 16.0 compat data mapping
Fixed some ancient iOS Safari versions compat data mapping

3.25.1 - 2022-09-07
Added some fixes and workarounds of FF30- typed arrays bug that does not properly convert objects to numbers
Added sideEffects field to core-js-pure package.json for better tree shaking, #1117
Dropped semver dependency from core-js-compat

semver package (ironically) added a breaking change and dropped NodeJS 8 support in the minor 7.1 version, after that semver in core-js-compat was pinned to 7.0 since for avoiding breaking changes it should support NodeJS 8. However, since core-js-compat is usually used with other packages that use semver dependency, it causes multiple duplications of semver in dependencies. So I decided to remove semver dependency and replace it with a couple of simple helpers.

Added Bun 0.1.6-0.1.11 compat data
Added Deno 1.25 compat data mapping
Updated Electron 21 compat data mapping
Some stylistic changes, minor fixes, and improvements

3.25.0 - 2022-08-24
Added Object.prototype.__proto__ polyfill

It's optional, legacy, and in some cases (mainly because of developers' mistakes) can cause problems, but some libraries depend on it, and most code can't work without the proper libraries' ecosystem
Only for modern engines where this feature is missed (like Deno), it's not installed in IE10- since here we have no proper way setting of the prototype
Without fixes of early implementations where it's not an accessor since those fixes are impossible
Only for the global version

Considering document.all as an object in some missed cases, see ECMAScript Annex B 3.6
Avoiding unnecessary promise creation and validation result in %WrapForValid(Async)IteratorPrototype%.return, proposal-iterator-helpers/215
Fixed omitting the result of proxing .return in %IteratorHelperPrototype%.return, #1116
Fixed the order creation of properties of iteration result object of some iterators (value should be created before done)
Fixed some cases of Safari < 13 bug - silent on non-writable array .length setting
Fixed ArrayBuffer.length in V8 ~ Chrome 27-
Relaxed condition of re-usage native WeakMap for internal states with multiple core-js copies
Availability cloning of FileList in the structuredClone polyfill extended to some more old engines versions
Some stylistic changes and minor fixes
Throwing a TypeError in core-js-compat / core-js-builder in case of passing invalid module names / filters for avoiding unexpected result, related to #1115
Added missed NodeJS 13.2 to esmodules core-js-compat / core-js-builder target
Added Electron 21 compat data mapping
Added Oculus Browser 23.0 compat data mapping

3.24.1 - 2022-07-29
NodeJS is ignored in IS_BROWSER detection to avoid a false positive with jsdom, #1110
Fixed detection of @@ species support in Promise in some old engines
{ Array, %TypedArray% }.prototype.{ findLast, findLastIndex } marked as shipped in FF104
Added iOS Safari 15.6 compat data mapping
Fixed Opera 15 compat data mapping

3.24.0 - 2022-07-25
Recent updates of the iterator helpers proposal, #1101:

.asIndexedPairs renamed to .indexed, proposal-iterator-helpers/183:

Iterator.prototype.asIndexedPairs -> Iterator.prototype.indexed
AsyncIterator.prototype.asIndexedPairs -> AsyncIterator.prototype.indexed

Avoid exposing spec fiction %AsyncFromSyncIteratorPrototype% in AsyncIterator.from and Iterator.prototype.toAsync, proposal-iterator-helpers/182, proposal-iterator-helpers/202
Avoid unnecessary promise creation in %WrapForValidAsyncIteratorPrototype%.next, proposal-iterator-helpers/197
Do not validate value in %WrapForValid(Async)IteratorPrototype%.next, proposal-iterator-helpers/197 and proposal-iterator-helpers/205
Do not forward the parameter of .next / .return to an underlying iterator by the extended iterator protocol, a part of proposal-iterator-helpers/194
.throw methods removed from all wrappers / helpers prototypes, a part of proposal-iterator-helpers/194
Close inner iterators of { Iterator, AsyncIterator }.prototype.flatMap proxy iterators on .return, proposal-iterator-helpers/195
Throw RangeError on NaN in { Iterator, AsyncIterator }.prototype.{ drop, take }, proposal-iterator-helpers/181
Many other updates and fixes of this proposal

%TypedArray%.prototype.toSpliced method removed from the change array by copy proposal and marked as obsolete in core-js, proposal-change-array-by-copy/88
Polyfill Promise with unhandledrejection event support (browser style) in Deno < 1.24
Available new targets in core-js-compat / core-js-builder and added compat data for them:

Bun (bun), compat data for 0.1.1-0.1.5, #1103
Hermes (hermes), compat data for 0.1-0.11, #1099
Oculus Browser (oculus), compat data mapping for 3.0-22.0, #1098

Added Samsung Internet 18.0 compat data mapping

3.23.5 - 2022-07-17
Fixed a typo in the structuredClone feature detection, #1106
Added Opera Android 70 compat data mapping

3.23.4 - 2022-07-09

3.23.3 - 2022-06-25

3.23.2 - 2022-06-20

3.23.1 - 2022-06-14

3.23.0 - 2022-06-13

3.22.8 - 2022-06-01

    from core-js GitHub release notes

Commit messages

Package name: core-js

3b13f58 3.26.0
451645d Merge pull request #1118 from zloirock/self
fc27265 update docs
7e85def update the changelog
036575a add `self`
4604f5b stylistic change
e583927 update dependencies
aa9b0c2 update `SECURITY.md`
503109a add Opera Android 72 compat data mapping
35806ac add Deno 1.26 and 1.27 compat data mapping
7d17fcc update signatures
08fd215 simplify args passing
f5f7df5 `{ Iterator, AsyncIterator }.prototype.flatMap` supports returning both - iterables and iterators
43cfb4e update dependencies
8e58a6d don't await non-objects returned from functions passed to `AsyncIterator` helpers
98edc05 update the changelog
6ff2637 update docs
f17389a add counter argument to async iterator helpers
c8d22f6 add counter argument to iterator helpers
3e18cd0 use NodeJS 19 in `lint` and `karma` CI jobs
edb6b05 update dependencies
8faf133 add NodeJS 19 to CI
84a113c update dependencies
e29fa7c change the order of imports

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Looks good to me.


Missing crcStatus in JSON Uplink Frames

Is this a bug or a feature request?
Potential bug or a change in the design that does not appear to have been articulated in the documentation.
What did you expect?
We are in the procress of building parallel support for V2 JSON (currently in use) and the newer JSON structure.  In the V2 JSON gateway bridge uplink frames included the crcStatus field to indicate whether the frame passed CRC (1), failed (-1) or no CRC check was performed (0).  Various different LoRa gateways support sending this CRC information and this is often configurable in the packet forwarder.
What happened?
In the new JSON structure we are no seeing the crcStatus field and thus are wondering if this is bug or the bridge software is filtering out failures hence removing the need for the crcStatus.
What version are your using?
This is being tested with lora server 2.3.0, lora-app-server 2.3.0, gateway bridge 2.6.0 and geo server 2.0.0.  Are initial test was performed using a Tektelic Pico gateway that only forwards CRC successes but we will be testing with MultiTech conduit and Tektelic Macro gateways too that can forward CRC failures.
How can your issue be reproduced?
Easily, first configure the gateway bridge to send V2 JSON messages and not the crcStatus is present in uplink frames from the gateway.  Then change the bridge setting to JSON and note the incoming json frames no longer include the crcStatus field.
Could you share your log output?
We can if needed but the lora sever documentation online also shows the crcStatus is missing for JSON uplink frames (https://www.loraserver.io/lora-gateway-bridge/integrate/payload-types/json/) versus V2 JSON uplink frames (https://www.loraserver.io/lora-gateway-bridge/integrate/payload-types/v2-json/).  We are just seeking clarification why the crcstatus is now omitted.

The setting was there, but was indeed not enforced in the latest version. The above commit fixes this.


Error when install with laravel-datatables-oracle v9.4.0

Summary of problem
When try install, I received an error message: " Your requirements could not be resolved to an installable set of packages."

Error message:
Problem 1
- Can only install one of: yajra/laravel-datatables-oracle[8.0.x-dev, v9.4.0].
- Can only install one of: yajra/laravel-datatables-oracle[v9.4.0, 8.0.x-dev].
- Can only install one of: yajra/laravel-datatables-oracle[8.0.x-dev, v9.4.0].
- yajra/laravel-datatables-buttons v3.0.0 requires yajra/laravel-datatables-oracle 8.* -> satisfiable by yajra/laravel-datatables-oracle[8.0.x-dev].
- Installation request for yajra/laravel-datatables-buttons 3.0 -> satisfiable by yajra/laravel-datatables-buttons[v3.0.0].
- Installation request for yajra/laravel-datatables-oracle ~9.4 -> satisfiable by yajra/laravel-datatables-oracle[v9.4.0].

System details

Operating System: Nginx
PHP Version: 7.2
Laravel Version: 5.8
Laravel-DataTables Version: 9.4.0

yes it is a problem!!! same problem:
Operating System: Windows 10
PHP Version: 7.2
Laravel Version: 5.8
Laravel-DataTables Version: 9.4.1

You might be using yajra/laravel-datatables-buttons v3.0.0 somewhere? Use v4.0 instead. Or use the  all in one installer composer require yajra/laravel-datatables:^1.5.

See #94 for a solution too. Thanks!


Upgrade NodeJs version from 12 to 16 in all reportstream workflow using gradle/wrapper-validation-action

There is a warning to change the nodejs version in gradle/wrapper-validation-action. I'll create another ticker for
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: gradle/wrapper-validation-action
For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

Issue resolved with PR https://github.com/CDCgov/prime-reportstream/pull/7002


Support for K8S Probes

This issue is about supporting Kubernetes Probes from the framework.
The main question is how to map probes to operators in general:

Liveness  - is operator started? (So start method called?)  Is there any other meaningful way?.
Should be this bound to sync timeout: https://github.com/java-operator-sdk/java-operator-sdk/issues/1318 ?  So if out of sync it is basically not alive?

Readyness  (or Startup?) - probes is naturally can be bidden to event source sync, so the operator is ready when event sources are already synced.

The API:
Operator operator = new Operator()
...
operator.start()

// from this point the methods
boolean ready = operator.isReady()
boolean alive = operator.isAlive()

User later can call those methods from a servlet container or whatever integration chooses with K8S for the probes.

An other thing we should check in the probes if the informers are watching:
https://github.com/fabric8io/kubernetes-client/issues/4340#issuecomment-1222394149
So probably the operator is not ready if the informers are not watching.
But this is related also with the issue: https://github.com/java-operator-sdk/java-operator-sdk/issues/1405
Where we want to start informers, and if there is not permission  for the informer (and not watching) that is fine.
This however this probably requires explicit checking of permission.


Provide a method to extract state variables from mod file

Hi Michael @nrnhines
I'm trying to extract the extract the state variables and their derivatives from the c-generated mod file.
Take as an example the following code extracted from KdShu2007.cpp:
[...]
#define ek _p[1*_STRIDE]
#define ik _p[2*_STRIDE]
#define m _p[3*_STRIDE]
#define h _p[4*_STRIDE]
#define Dm _p[5*_STRIDE]
#define Dh _p[6*_STRIDE]
#define _v_unused _p[7*_STRIDE]
#define _g_unused _p[8*_STRIDE]
[...]

So far there exists a method to extract only the ode count. Ideally I'd also need a method that extracts the offsets of the m, h, dm and dh.  Here is a suggestion of how to extract the count and offsets of each variable:
 void _nrn_ode_state_offsets__KdShu2007(short * count, short** var_offsets, short ** dv_offsets)
 {
     *count = 2;
     (*var_offsets) = (short*) malloc(sizeof(short)* *count);
     (*dv_offsets) = (short*) malloc(sizeof(short)* *count);
     (*var_offsets)[0] = 3;
     (*var_offsets)[1] = 4;
     (*dv_offsets)[0] = 5;
     (*dv_offsets)[1] = 6;
 }

or if it's guaranteed that state and d-vars are always sequentially placed in the _p array, simply provide the offsets of the first element:
 void _nrn_ode_state_offsets__KdShu2007(short * count, short* var_offsets, short * dv_offsets)
 {
     *count = 2;
     *var_offsets = 3;
     *dv_offsets = 5;
 }

This would be useful for CVODE(S) -based computation. So far I'm writing these functions by hand on each c-generated mod file. However, this is not a good solution at long term.
Thank you

Hi Bruno,
I'm looking at the hh.c generated by mod2c and see that a some of the cvode
stuff is still there (_ode_spec1 for y'=f(y) and _ode_matsol for approxiate
jacobian) but a lot get #if 0 away in mod2c so that things relevant to
hoc_register_cvode(_mechtype, _ode_count, _ode_map, _ode_spec, _ode_matsol);
hoc_register_tolerance(_mechtype, _hoc_state_tol, &_atollist);
are missing.
Anyway, the information you are looking for is part of the
int* _slist1;
int* _dlist1;
that are filled in the static void _initlists(){
and give the offsets for state and dstate.
In the classical NEURON world, this information was also encoded in
static const char *_mechanism[] = {
which defined the layout of the _p array in terms of PARAMETER, ASSIGNED,
STATE
Cheers,
Michael

Thank you Michael @nrnhines , I will have a look ASAP and close the ticket if that solves it.
Cheers, Bruno

Hi Michael @nrnhines
I double-checked the code.
Indeed _slist and _dlist provide the offsets for state vars and D-state vars. Populated when _<mech-name>_reg() functions calls _initlists().
I believe this solves the issue.
Thank you vm

Hi Michael @nrnhines .
After checking thoroughly, the _slist1 and _dlist1 are private in the context of the mod file. Also, no variable is available to express how many state vars exist, i.e. the length of the 2 arrays.
To make those changes, I implemented the following on each mechanism:
void nrn_ode_state_vars(int * var_count, int ** var_offsets, int ** dv_offsets) {
  *var_count = _cvode_neq;
  *var_offsets = _slist1;
  *dv_offsets = _dlist1;
}

and added a new variable _cvode_neq.
The diff of the implementation is the following, and I'll leave it here for future implementation if possible.
It's the commit 5dbd3c483dfa0029a37c4c39a4557f86ba73cf57 in the branch brunos_use_case, if you need to git cherrypick.
--- a/src/mod2c_core/deriv.c
+++ b/src/mod2c_core/deriv.c
@@ -635,11 +635,13 @@ if (s->subtype & ARRAY) { int dim = s->araydim;

          "\n#define _slist%d _slist%d%s\n"
          "int* _slist%d;\n"
+         "#define _cvode_neq _cvode_neq_%s\n"
+         "int _cvode_neq;\n"
          "#pragma acc declare create(_slist%d)\n"
          "\n#define _dlist%d _dlist%d%s\n"
          "int* _dlist%d;\n"
          "#pragma acc declare create(_dlist%d)\n"
-         , numlist, numlist, suffix, numlist, numlist
+         , numlist, numlist, suffix, numlist, suffix, numlist
          , numlist, numlist, suffix, numlist, numlist
          );
                Linsertstr(procfunc, buf);
@@ -687,6 +689,14 @@ if (s->subtype & ARRAY) { int dim = s->araydim;
        vectorize_scan_for_func(qq, procfunc);
   }

+        Lappendstr(procfunc,
+                       "\n\
+void nrn_ode_state_vars(int * var_count, int ** var_offsets, int ** dv_offsets) {\n\
+  *var_count = _cvode_neq;\n\
+  *var_offsets = _slist1;\n\
+  *dv_offsets = _dlist1;\n\
+}\n");
+
        Lappendstr(procfunc, "/*END CVODE*/\n");

and
--- a/src/mod2c_core/nocpout.c
+++ b/src/mod2c_core/nocpout.c
@@ -445,12 +445,14 @@ fprintf(stderr, "Notice: ARTIFICIAL_CELL models that would require thread specif
 #define nrn_state _nrn_state_%s\n\
 #define initmodel initmodel_%s\n\
 #define _net_receive _net_receive_%s\n\
+#define _net_receive2 _net_receive2_%s\n\
 #define nrn_state_launcher nrn_state%s_launcher\n\
 #define nrn_cur_launcher nrn_cur%s_launcher\n\
 #define nrn_jacob_launcher nrn_jacob%s_launcher\n\
 #define _ode_matsol1 _nrn_ode_matsol1_%s\n\
 #define _ode_spec1 _nrn_ode_spec1_%s\n\
-", suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix);
+#define nrn_ode_state_vars _nrn_ode_state_vars_%s\n\
+", suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix, suffix);
        Lappendstr(defs_list, buf);

        if (net_receive_buffering_) {
@@ -2777,11 +2779,12 @@ static void _ode_map(int _ieq, double** _pv, double** _pvdot, double* _pp, Datum
                sprintf(buf, "\
        int _i; _p = _pp; _ppvar = _ppd;\n\
        _cvode_ieq = _ieq;\n\
+       _cvode_neq = %d;\n\
        for (_i=0; _i < %d; ++_i) {\n\
                _pv[_i] = _pp + _slist%d[_i];  _pvdot[_i] = _pp + _dlist%d[_i];\n\
                _cvode_abstol(_atollist, _atol, _i);\n\
        }\n",
-                       cvode_neq_, cvode_num_, cvode_num_);
+                       cvode_neq_, cvode_neq_, cvode_num_, cvode_num_);
                Lappendstr(procfunc, buf);
 /* need to take care of case where a state is an ion concentration. Replace
 the _pp pointer with a pointer to the actual ion model's concentration */
@@ -3031,6 +3034,8 @@ sprintf(buf, "\
        }

        sprintf(buf, "\
+\nvoid _net_receive2 (NrnThread * _nt, Memb_list* _ml, int _iml, int _weight_index, double _lflag, double _nrb_t);\
+\n\
 \nstatic void _net_receive (Point_process* _pnt, int _weight_index, double _lflag) {\

I'll reopen the ticket and leave it up to you to decide whether this is an intended feature or not, and close the ticket accordingly.
Thank you

This is ok but I would prefer not introducing the variable cvode_neq.  or indeed, changing deriv.c at all.
All the information needed to generate nrn_ode_state_vars%s is available in nocpout.c. eg.see the
cvode_emit_interface() function.  Notice how there is never an explicit slist1 emitted but slist%d. The
relevant nocpout.c variables are cvode_neq and cvode_num. Also it is not clear to me why
_net_receive is changed to _net_receive2. Is there perhaps a more mnemonic name to distinquish it
from _net_receive

net_receive2 is an artefact of some side development for another ticket (I now changed that comment to remove those line)
Yes, your suggestions is good and I am ok with the variables and notations you mentioned being as you propose, as long as there's a method (similar to the void nrn_ode_state_vars(int * var_count, int ** var_offsets, int ** dv_offsets)) to extract them. I can merge my changes to the master branch or let you implement it and I'll adapt my code accordingly.
Thank you very much for your support.

Please make the changes and I will review.

I just double checked: it will take a while to merge because the changes are spread across several commits that add also other functionalities. I'll handle it asap.

Not relevant anymore, all new development happens in https://github.com/BlueBrain/nmodl


refactor directory structure

It looks like there is a practice followed my mac admins to separate their scripts by folders within their repo.
Wanted to start the discussion of possibly refactoring the script and documentation to depend on this structure.

@BadStreff what do you think about closing this issue out now that the scripts will be in folders?


Use HostedZone ID instead of HostedZone Name

For this part of cluster.yaml when using AWS
# The name of the hosted zone to add the externalDNSName to,
# E.g: "google.com".  This needs to already exist, kube-aws will not create
# it for you.
hostedZone:

I have a public and private hosted zone with the same name, so providing the name causes the creation to ultimately fail because of it. If we instead provided Hosted Zone ID, I don't think that would be a problem

I went with name due to ease of use, but I didn't consider the potential ambiguity.  I'd prefer not to drop support for using the name, but we could support both by adding another field "hostedZoneID".
It looks like hostedzone id's don't have dots in them, and generally look like "Z23ABC4XYZL05B", but I can't find any docs saying we can rely on that.  If we can, we could also consider allowing you to put both ids and names into hostedZone and we could determine which it is.
Any thoughts @colhom?

I think attempting to regex the hostedZone field to figure out if it's an ID or name is dangerous in the long term. Let's either go with an option that doesn't require making that decision. I think hostedZoneID, which would be mutually exclusive with specifying hostedZone, is the best option.


Add GetDirectionsFlightGroups_test

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8052992). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master      #18   +/-   ##
=========================================
  Coverage          ?   43.83%
=========================================
  Files             ?       23
  Lines             ?      762
  Branches          ?        0
=========================================
  Hits              ?      334
  Misses            ?      380
  Partials          ?       48

Impacted Files
Coverage Δ

structs/pricing.response.types.go
5.46% <0%> (ø)

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 8052992...e9bab64. Read the comment docs.


Code action fails with 'prerel1' (a boolean value)

Ubuntu 20, nvim 0.10-dev (build from source), fresh telecope-ui-select.vim using Lazy.

NVIM v0.10.0-dev-508+gd3b9feccb
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3

Directly ":lua vim.lsp.buf.code_action()" or if I use the lsp-zero  code action (which is the same thing).  It fails with the following.
Error executing vim.schedule lua callback: /usr/share/nvim/runtime/lua/vim/version.lua:78: attempt to index local 'prerel1' (a boolean value)
stack traceback:
        /usr/share/nvim/runtime/lua/vim/version.lua:78: in function 'cmp_prerel'
        /usr/share/nvim/runtime/lua/vim/version.lua:120: in function '__eq'
        /usr/share/nvim/runtime/lua/vim/version.lua:372: in function 'cmp'
        ...e-ui-select.nvim/lua/telescope/_extensions/ui-select.lua:32: in function <...e-ui-select.nvim/lua/telescope/_extensions/ui-select.lua:23>
        ...e-ui-select.nvim/lua/telescope/_extensions/ui-select.lua:106: in function 'select'
        /usr/share/nvim/runtime/lua/vim/lsp/buf.lua:713: in function 'on_code_action_results'
        /usr/share/nvim/runtime/lua/vim/lsp/buf.lua:731: in function 'callback'
        /usr/share/nvim/runtime/lua/vim/lsp.lua:2155: in function 'handler'
        /usr/share/nvim/runtime/lua/vim/lsp.lua:1517: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

Not sure what's going on.

Problem solved.  A tangential problem said their fix was not to use 0.10.  I switched to 0.9.5. Now things work.


Notebook Add Advanced Controls

Category

Features

Overview

Add more controls and functions to the notebook:

Image embedding with sizing/resizing (Image is sized with width and will maintain original image ratio)
Text alignments
Text coloring
Colored Highlighting
Task list with checkboxes and option to tick boxes in read only mode
Table with cell color control and resizable columns
Cancel edit button

Issue Number

Closes #1413

Screenshot

Editor with all new features used

Image embed modal

Table insert modal

Highlight, Text, and table cell color picker modal

Did you fix the edit-reload issue ? If not can you create an issue about it and pin it?

No it's out of scope for this PR, I'll make an issue.
No idea where it comes from.
I mentioned on discord that for testing it's better to deploy on docker rather than de environment.


Fails to load DTB

Everything appears to have been built successfully and at first I created extlinux.conf but later found out you can use the created boot.scr instead as-is.  Using either approach I keep running into problems loading the DTB.  The files in /boot/dtb-nouveau appear to be DTB files according to the file command so I'm not sure what is wrong with them.  Maybe something has changed in the kernel that makes these DTB files incomplete?  See the errors below.
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
706 bytes read in 105 ms (5.9 KiB/s)
## Executing script at 90000000
12576256 bytes read in 612 ms (19.6 MiB/s)
51116 bytes read in 109 ms (457 KiB/s)
## Flattened Device Tree blob at 82000000
   Booting using the fdt blob at 0x82000000
   Using Device Tree in place at<PHONE_NUMBER>000000, end<PHONE_NUMBER>00f7ab
Can't create DT prop nvidia,emc-shadow-regs-rdwr-train to copy
Can't create DT prop nvidia,current_dram_clktree_c0d0u0 to copy
Can't create DT node emc-table@204000 to copy
ERROR: board-specific fdt fixup failed: FDT_ERR_NOTFOUND
 - must RESET the board to recover.

FDT creation failed! hanging...### ERROR ### Please RESET the board ###

Ah, this is an issue with the L4T bootloader. I think I have a fix for this, let me try it and come back to this...

Ok, the fix to this should have hit the repo - please repo sync and run the build-linux script again. You should see the message saying "Writing U-boot script in /boot/boot-nouveau.scr...".
Check on the target filesystem that this file now contains the following line:
set fdt_copy_node_names

The L4T bootloader needs to propagate a few nodes from the bootloader's DT to the kernel DT. The nodes to copy are controlled by this variable, and if the targets are not found the BL will complain and abort as you see. Resetting this variable skips the copy phase, and Linux should then boot without any issue.
Closing this issue - please reopen if needed!

Yep that worked!  I actually just looked at the diff, changed the boot script, and manually rebuilt the boot.scr file.  Thanks for the quick response.  I'm at the login prompt now so need to continue on to see if the driver is working, but step 1 is boot the kernel :+1:

Excellent, thanks for confirming! At this point if you can see /dev/dri/renderD128 this means that Nouveau is most probably working properly.


Fix Snapshots

As mentioned in the title, we need to fix the snapshots else the jest tests will continue to fail for Travis

Pull Request Test Coverage Report for Build 4872

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 37.134%

Totals

Change from base Build 4867:
0.0%

Covered Lines:
2898

Relevant Lines:
6977

💛  - Coveralls


Add support for pip install dask[jobqueue]

It might be worthwhile to add support for doing pip install dask[jobqueue] by adding the dependency to [project.optional-dependencies] in pyproject.toml. Additionally, it could be nice to have this tested in some integration CI run.

There are many different dask extensions that could be added this way and so far we chose not to do this. So far, the optional dependencies are only covering things that are related to dask core functionality and doesn't include any deployment specific optionals.
I'm inclined to not go down that route of adding all possible projects as there are too many.

Regarding testing, I see the benefits of having fully integrated CI runs but I'm concerned about the cost (mostly time and developer productivity).
Most of the test suite is actually not setup to run with a distributed cluster but are only using the trivial schedulers. To enable an integration test we'd have to migrate the entire test suite to a setup that is using a LocalCluster variant (which could then be replaced by dask-jobqueue et al with their respective clusters). This is a lot of work and would likely slow down CI considerably even without accounting for the additional test runs against jobqueue, kubernetes, gateway, mpi, ...

cc @jacobtomlinson who is heavily involved in development and maintenance of the various OSS deployment tools

I think the amount of complexity in the CI of the deployment projects is enough to put me off doing something like this. Historically we've kept projects separate in Dask in order to give agency to the maintainers of each subproject.
I'm not especially +1/-1 on adding some more extras to the dask package. But it doesn't feel like it gives that much value over using package names directly. It would also mean we end up with a circular dependency as most subprojects depend on dask which I could imagine would cause a maintenance headache from time to time.
I'm always keen to discuss ideas like this. Anything we can do to make the user experience of Dask better is worth talking about. But I dont see any compelling reasoning in this particular case to motivate making a change like this. Given @fjetter is also not positive on the idea I'm going to close this out. But thanks for starting the discussion @Andrew-S-Rosen!