Update the Alice/Faber OpenAPI (Swagger) demo to show webhooks, remove automation

A good issue for anyone familiar with the /demo examples.  I think the code changes are simple, but happy to discuss.
Update the OpenAPI demo behaviour and script to handle manually all of the connection, issue and prove events via the OpenAPI (Swagger) UI. In conjunction with changing the steps to be done, invoke the demos/run_demo script with two new options:
run_demo --no-auto --events alice
When set the --no-auto parameter would remove all (or perhaps most - as makes sense) of the --auto... options on ACA-Py, so that the controller is forced to respond to and handle each of the protocol events happening in the protocols.
When set the --events parameter would cause the webhook to the controller to be JSON pretty-printed to the console so the user operating the OpenAPI interface would know when an event has occurred and a response is needed.
I think those requirements make sense, but would like to talk with anyone taking this one to make sure we're in sync on what is needed.
I'm happy to do the writing for the update OpenAPI script based on just a bit of guidance on what is needed.

Hi @swcurran I'm happy to take this one on. I'm walking through the code to get an idea of the demo workflow with --auto-accept-invites and --auto-accept-requests off. Is there any other documentation that I should checkout?

Cool. Unfortunately, there is not a lot.  The existing demo is here: https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AriesOpenAPIDemo.md
The idea would be to run either or both agents (e.g - https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AriesOpenAPIDemo.md#running-the-faber-agent) with the new options and then add in the extra steps in the story that have to be done when the --auto... steps have been removed.  I'm hoping that by being able to see the webhook events from the agent, the cutting and pasting can be a bit easier.
Let me know if that makes sense.

@swcurran I have gone through the demo with the --auto-.. flags turned off. There are parts of the issue_credential workflow that are not controlled with those flags.
For example:
When Faber sends a credential offer there is a an auto_issue request body parameter that needs to be set to false, otherwise the credential will automatically be issued to Alice,  who then has to explicitly store the credential in her wallet. Prior to this, the handle_issue_credential method in the Alice Agent responds immediately to Faber's credential offer by issuing a credential request back to Faber. Neither of these are controlled by the --auto-.. flags. If we truly want to turn off all automation steps with a --no-auto option I feel there needs to be some control flow implemented in these spots. Should I proceed and add the relevant condition checks? Or should we review it further?

We need to get @andrewwhitehead or @nrempel involved in this.  I'll try to touch base with Andrew tomorrow to review this and connect with you.
Were you able to make the --events option work and was it useful?  I would think that would be a generally useful, if somewhat noisy capability.  How did it work?
This is awesome!  Thanks!

I haven't implemented that part yet. Was hoping to get the documentation completed first (which I was able to at least for establishing a connection). Based on the issue description for the --events flag, I'm guessing you're looking for something like an event logger that gets enabled which prints out methods/webhooks that we're called? Please, correct me if I'm wrong here.

Yes.  If I am going to write a controller, and I'm using the Swagger API to learn about the endpoints available for me to call, I'm going to want to see the content of the events I receive. Presumably, a lot of the data I need to use in responding is going to be in the event data I receive.
Does that make sense?

Im just wondering since the Agent modules imports a logger package we could just use that to print out relevant information in the Agent/Alice/Faber runner methods? I was thinking along the lines of a sort of debug info level option that is turned on when the --event flag is set. Perhaps I can fill in those methods with calls to the logger. I'd have to take a look at the documentation for that package.

@amanji - I that might work.  Could it have unintended consequences. E.g. if you associate the webhook data to be displayed when the "debug" level is set, and the "--event" is the equivalent of turning on debug, wouldn't you get lots of other "debug" events?  Does logger allow for specified logging type names?

Also, I checked with Andrew on the --auto... stuff above.  He checked and he think it looks right.  Perhaps not all of the auto options were removed?
From Andrew:

If auto_issue is not provided as a parameter then the agent defaults to the setting for --auto-respond-credential-request, which should be off

After reading the Logger documentation there are basically three possible approaches:

Create a custom logging level but for events
Creating a custom filter or handler for event logs
A named Logger instance that strictly handles event logs

The first creates additional log levels that deviate from the established standard levels. The second will require filtering through all logs or creating a handler that can capture event logs and could muddy up existing loggers. The third is more modular and encapsulates event log filters/handlers independently of other Logger instances, This named logger can be activated independently of other existing loggers. I am of the belief that the third option is the best approach here.

Agree that third sounds best.
On Fri, Feb 14, 2020, 7:31 PM Akiff Manji<EMAIL_ADDRESS>wrote:

After reading the Logger documentation there are basically three possible
approaches:

Create a custom logging level but for events
Creating a custom filter or handler for event logs
A named Logger instance that strictly handles event logs

The first creates additional log levels that deviate from the established
standard levels. The second will require filtering through all logs or
creating a handler that can capture event logs and could muddy up existing
loggers. The third is more modular and encapsulates event log
filters/handlers independently of other Logger instances, This named
logger can be activated independently of other existing loggers. I am of
the belief that the third option is the best approach here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hyperledger/aries-cloudagent-python/issues/361?email_source=notifications&email_token=AAHYRQUSBB3VS3I5GNGWOZDRC5OZZA5CNFSM4KQTKEU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL3APNI#issuecomment-586549173,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHYRQUVWGEG2HEE67MPQ3TRC5OZZANCNFSM4KQTKEUQ
.


Can't use custom layout scene

The problem
Describe the bug
I cannot select another custom scene as layout.
To Reproduce
Steps to reproduce the behavior:

Go to "Layout"
Change "Preset Mode" to "Custom Mode"
Select a scence in the "Custom layout scene"
Go to another tab, for example "Glossary"
Go back to "Layout". The custom layout scene is now the default scene.

Expected behavior
The custom layout scene should stay selected.
System

OS: Windows 10
Godot Version: 4.0 stable
Dialogic Version: 2.0-Alpha-6

Should be fixed by #1476


build/create-rpm.sh fails on gpg import

[user@untrusted qubes-video-companion]$ DEBUG=1 ./build/create-rpm.sh
+ set -E
+ trap exit ERR
+ '[' '' == dom0 ']'
+++ readlink -f ./build/create-rpm.sh
++ dirname /tmp/qubes-video-companion/build/create-rpm.sh
+ local_dir=/tmp/qubes-video-companion/build
+ cd /tmp/qubes-video-companion/build
+ gpg --import author.asc
gpg: key F83DD5F2: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg:           w/o user IDs: 1
++ exit

Even if I comment out things related to gpg signature I eventually getting this error:
make[1]: Entering directory '/home/user/rpmbuild/BUILD/qubes-video-companion-1.0.0/doc'
pandoc -s -f rst -t man -o qubes-video-companion.1 qubes-video-companion.rst
gzip -f qubes-video-companion.1
install -d /home/user/rpmbuild/BUILDROOT/qubes-video-companion-1.0.0-1.fc26.x86_64/usr/share/man/man1
install -Dm 644 qubes-video-companion.1.gz /home/user/rpmbuild/BUILDROOT/qubes-video-companion-1.0.0-1.fc26.x86_64/usr/share/man/man1
make[1]: Leaving directory '/home/user/rpmbuild/BUILD/qubes-video-companion-1.0.0/doc'
install -d /home/user/rpmbuild/BUILDROOT/qubes-video-companion-1.0.0-1.fc26.x86_64/usr/share/licenses/qubes-video-companion
install -Dm 644 LICENSE /home/user/rpmbuild/BUILDROOT/qubes-video-companion-1.0.0-1.fc26.x86_64/usr/share/licenses/qubes-video-companion
+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /home/user/rpmbuild/BUILD/qubes-video-companion-1.0.0
+ '[' noarch = noarch ']'
+ case "${QA_CHECK_RPATHS:-}" in
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/brp-compress
+ /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
Compiling /home/user/rpmbuild/BUILDROOT/qubes-video-companion-1.0.0-1.fc26.x86_64/usr/share/qubes-video-companion/ui/user_interface.py ...
  File "/usr/share/qubes-video-companion/ui/user_interface.py", line 33
    print('Video source does not exist:', self.video_source, file=sys.stderr)
                                                                 ^
SyntaxError: invalid syntax

error: Bad exit status from /var/tmp/rpm-tmp.uXVhIu (%install)

RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.uXVhIu (%install)
++ exit

I can see by the fc26 strings in the build log that you're trying to build this on Fedora 26 which is woefully out-of-date.
This means that the reason for the first error is the gpg command using GPG version 1 instead of 2 which is incompatible with newer ECC keys (like mine).
The second error is some incompatibility in the older version of Python on Fedora 26 meaning the package cannot build.
The package must be built on the the same version of Fedora that it will be installed on. So, if your sys-usb VM runs Fedora 33 (the newest version a stable Qubes template currently exists for) then you will have to build the package on Fedora 33 as well.
Similarly, if you want to build for Dom0, well it runs Fedora 25 in Qubes R4.0, so you will have to get a Fedora 25 AppVM from the official Qubes repo (I included instructions on how to do this in the script) and run ./create-rpm.sh dom0 so the script knows to build the RPM using the Fedora 25 spec file (as opposed to the one for building on modern versions of Fedora).
Please let me know if you have any more questions!

Jeez, I had no idea about those dependencies. I hope to try that during the weekend. On Tuesday I would like to show something at conference instead of only my struggle with making it work. Are you available for support on some less asynchronous medium e.g. Wire? It would also be great to have your review of my presentation or even if you could join session on Tuesday.

Sure thing! I've never heard of Wire but it seems like a good modern secure and private communication app for the workplace. I created an account @elliotkillick, let's see if we can connect.

Similarly, if you want to build for Dom0, well it runs Fedora 25 in Qubes R4.0, so you will have to get a Fedora 25 AppVM from the official Qubes repo (I included instructions on how to do this in the script) and run ./create-rpm.sh dom0 so the script knows to build the RPM using the Fedora 25 spec file (as opposed to the one for building on modern versions of Fedora).

That isn’t a good idea.  A much safer approach is to use qubes-builder.  The Fedora 25 DNF and RPM packages are horribly insecure.

That isn’t a good idea. A much safer approach is to use qubes-builder. The Fedora 25 DNF and RPM packages are horribly insecure.

That's a good point! In fact, I think Demi has found a few vulnerabilities in DNF since then.
However, without Qubes Builder "set up" for this project (I've never used qubes-builder; I assume there is some setup) it puts us in a tough spot. I just merged that PR so hopefully we can get rolling with that!

That isn’t a good idea. A much safer approach is to use qubes-builder. The Fedora 25 DNF and RPM packages are horribly insecure.

That's a good point! In fact, I think Demi has found a few vulnerabilities in DNF since then.
However, without Qubes Builder "set up" for this project (I've never used qubes-builder; I assume there is some setup) it puts us in a tough spot. I just merged that PR so hopefully we can get rolling with that!

You need to expose a top-level makefile that has the targets Qubes Builder expects

Using and testing R4.1.
The script can build the .rpm in Fedora-34, but have (seemingly the same) issue with gpg in Fedora-32.
So what is the current state of the project? How to build .rpm for dom0?


build: only esm

Codecov Report
Base: 33.24% // Head: 33.28% // Increases project coverage by +0.04% :tada:

Coverage data is based on head (032f43e) compared to base (279b4eb).
Patch coverage: 32.20% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
+ Coverage   33.24%   33.28%   +0.04%
==========================================
  Files          11       10       -1
  Lines         755      754       -1
  Branches       33       33
==========================================
  Hits          251      251
+ Misses        504      503       -1

Impacted Files
Coverage Δ

packages/dite/src/node/compiler/swc.ts
12.67% <0.00%> (-1.22%)
:arrow_down:

packages/dite/src/node/config/server-mode.ts
100.00% <ø> (ø)

packages/dite/src/shared/logger.ts
59.42% <ø> (ø)

packages/dite/src/node/compiler/index.ts
7.25% <15.21%> (+0.71%)
:arrow_up:

packages/dite/src/cli/commands.ts
26.53% <100.00%> (ø)

packages/dite/src/node/config.ts
100.00% <100.00%> (ø)

packages/dite/src/node/server/index.ts
35.64% <100.00%> (+0.64%)
:arrow_up:

packages/dite/src/shared/constants.ts
100.00% <100.00%> (ø)

packages/dite/src/node/utils.ts

... and 1 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


ci: add job to test staking in srml

add a step to the ci that tests staking in srml
Related #2882

the srml staking test is failing here, is that expected?

no it is not expected to fail, I'll take a look, also maybe cc @Kianenigma


Fix off-by-1 error in pointing key update - [merged]

In GitLab by @wtbarnes on Nov 2, 2021, 06:48
Merges pointing-table-bugs -> master
This fixes a fairly egregious error in how the pointing update works. The pointing table values are the CCD pixel coordinates and are 0-based while FITS WCS is 1-based. Thus, we need to add 1 when updating the CRPIX values with the X0,Y0 keys. See section 2.2 of the JSOC keywords doc: http://jsoc.stanford.edu/~jsoc/keywords/AIA/AIA02840_K_AIA-SDO_FITS_Keyword_Document.pdf
This also fixes an issue where the pointing values in the table were being assigned a unit of arcsec instead of pixel. This had no impact on the pointing update though since the units were stripped in the end anyway.

In GitLab by @wtbarnes on Nov 2, 2021, 06:55
added 1 commit
6f9e4636 - changelog
Compare with previous version

mentioned in commit 2f6f053f4303ef6ed167cea6f5d0f6b36d1372e9

In GitLab by @codecov on Nov 2, 2021, 06:49
Codecov Report

Merging #132 (6f9e463) into master (fdfb681) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #132   +/-   ##
=======================================
  Coverage   97.45%   97.45%
=======================================
  Files          16       16
  Lines         551      551
=======================================
  Hits          537      537
  Misses         14       14

Impacted Files
Coverage Δ

aiapy/calibrate/meta.py
100.00% <100.00%> (ø)

aiapy/calibrate/util.py
100.00% <100.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 fdfb681...6f9e463. Read the comment docs.

approved this merge request

mentioned in commit 8124f002e3ce70aa8259800b2d09b1c157e77968

mentioned in commit 46a5020ed6fe22858e1de0b90d385ac31d391e70

In GitLab by @wtbarnes on Nov 2, 2021, 10:27
picked the changes into the branch cherry-pick-2f6f053f with commit 46a5020ed6fe22858e1de0b90d385ac31d391e70


Instrumentation documentation in README

@mkb - Any chance you could add a quick overview of the instrumentation stuff to the README?

Done.


Add integration tests for the metadata exchange

Please provide a description of this PR:
Add committed here, https://github.com/istio/istio/pull/38702#issuecomment-1116740121, adding integration tests for the metadata exchange.
In this PR, I am planning to cover only the http MX.
tcp I am planning to cover in https://github.com/istio/istio/pull/38495

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
a99f51a3cfcff3e75add1834bdd2d7d879c5031e
link
true
/test release-notes_istio

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

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
a99f51a3cfcff3e75add1834bdd2d7d879c5031e
link
true
/test release-notes_istio

lint_istio
a99f51a3cfcff3e75add1834bdd2d7d879c5031e
link
true
/test lint_istio

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

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
a99f51a3cfcff3e75add1834bdd2d7d879c5031e
link
true
/test release-notes_istio

lint_istio
a99f51a3cfcff3e75add1834bdd2d7d879c5031e
link
true
/test lint_istio

gencheck_istio
a99f51a3cfcff3e75add1834bdd2d7d879c5031e
link
true
/test gencheck_istio

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

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

Test name
Commit
Details
Required
Rerun command

release-notes_istio
a99f51a3cfcff3e75add1834bdd2d7d879c5031e
link
true
/test release-notes_istio

lint_istio
a99f51a3cfcff3e75add1834bdd2d7d879c5031e
link
true
/test lint_istio

gencheck_istio
a99f51a3cfcff3e75add1834bdd2d7d879c5031e
link
true
/test gencheck_istio

integ-telemetry-mc_istio
a99f51a3cfcff3e75add1834bdd2d7d879c5031e
link
true
/test integ-telemetry-mc_istio

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

moved changes to #38495 itself


cross-check with tribe29's new checkmk-agent role

Looks like tribe29 did not abandon their ansible roles: https://github.com/tribe29/ansible-checkmk/commit/ff396444706dfb8a117619442130d240f2b6578c
Checkout functionalities of https://github.com/tribe29/ansible-collection-tribe29.checkmk/blob/main/roles/server/README.md and potentially implement them in same way.
maybe even take a look at their modules and include wrapper functionality for them in this role (e.g. similiar to how my https://github.com/JonasPammer/ansible-role-openssl role is a wrapper of modules)
Related agent issue for this: https://github.com/JonasPammer/ansible-role-checkmk_agent/issues/13

i've rethought this, it doesn't make sense to just copy over things and maintain this (which i neglected for much time because of this anyways). there's an official one now, that's very well done, documented, and cared-for. the only thing i may'll think about doing is a role that hard-depend on the official one that does stuff that it doesnt do. i learned many things, and had fun programming the automation. maybe not the finest piece of code, but it worked, was feature-packed and got me to learn many things.


Normalized enrichment score = negative infinity and results not reproducible across different computers

Many times I see the normalized enrichment score to be infinity or negative infinity. Also in general, i find the results to be not reproducible when I run the same input in different computers. I see the code base makes extensive use of random numbers. Maybe set a seed for all random numbers?

Hi, thank you for the feedback. Can you confirm that this is happening on the latest version of blitzgsea? The latest version is 1.3.47 which did address the inf issue. If this is still something you experience is it possible to share the signature that causes this so I can try to reproduce the error?

Is there a way to check the blitzgsea version ?

You can use the following command line call:
pip3 freeze | grep blitzgsea

if you are using windows:
pip3 freeze | findstr blitzgsea

Yes, I did upgrade the blitzgsea version. It still shows NES=-inf. The most difficult part is its hard to reproduce the results even on the same computer.

I resolved an apparently identical issue by increasing the deep_accuracy argument to .gsea() from 50 (default on my install) to 100.


Non-deterministic map traversal is causing index.html to be different on every test

Btw, still not fixed.


Ignores ns parameter in the URL

When I open DSW for embedding to my application, I'm using URL like this /dsw/index.html#!/d/Dashboard%20with%20Meters.dashboard?ns=ENSDEMO&embed=1&lang=cs. But it fails to open, due to some requests to MDX2JSON asking for SAMPLES namespace, which I don't have.

Still relevant as of 2.1.32 (install via ZPM)


Project service account secrets are null after initial apply

I have a use case where we would like to store the service account secret in a secrets manager. The apply initially to create the secret works fine but subsequent applies fail as the api_key attributes are no longer available against the openai_project_service_account resource.
Should this data be available in the state? I understand that Terraform is still working on how to handle sensitive values https://github.com/hashicorp/terraform/issues/516 but until that lands I think its reasonable to store the secret in the statefile.

I'll look into it.
You definitely have it at creation time. So maybe there is a bug in my "refresh" code.
Give me a couple of days

this should be resolve in v1.7.1


Minor grammar fixes

docs(Contributing.md): correct typos, and improve grammar

common nouns should be in lowercase
improve the wording of some instructions

These changes improve the grammar and presentation of the CONTRIBUTING.MD document.
The instructions are now clearer and less verbose

Note: @kishanrajput23
I just discovered that you instructed that the PR's be made after October 1st.🤦♂
However, you can hold off on merging my PR until then so that it will count.
Thank you

Thank you @slim-codes for your suggestion. That's the better idea. Btw your contribution looks great.


Added new compute quota metrics (quotas for the tenant)

New metrics:
kos_compute_quota_cores
kos_compute_quota_floating_ips
kos_compute_quota_instances
kos_compute_quota_ram_megabytes

The new metrics follows the same pattern as the already existing
kos_cinder_quota_* metrics, i.e they also have a quota_type
dimension.
Signed-off-by: Pontus Nordh<EMAIL_ADDRESS>

@tobiasgiese @seanschneeweiss :)

The build job failed because of an outdated go version. I'll create a PR to fix the job.
https://github.com/mercedes-benz/kosmoo/blob/35af45301375846bc72517d464c84d0de56b52c6/.github/workflows/ci.yml#L30

https://github.com/mercedes-benz/kosmoo/pull/95 was successfully merged. Please rebase against the master branch @pnordh :)

#95 was successfully merged. Please rebase against the master branch @pnordh :)

done :)

@tobiasgiese thanks - can you push a new release tag as well?

@tobiasgiese thanks - can you push a new release tag as well?

Sure, will do a new release the next days


[chore] How about bump version for npm?

I worries is that (aem-spa-page-model-manager)-package has been supported for a long time on a limited version of NPM, how about trying to update it to the up-today one?
This may not be an easy task, but I believe that keeping packages up to date will help improve your product and make it more alive.
I remind you that the current version of npm is limited and has '6.14.14' and for up-today we have '8.12.1'

Sorry, I'm wrong with repo

But any way
we till have concern with right notice about exact version of NPM
I mean in current repo wrote version of NPM

but npm package provided a bit different number version)

Thanks. Sorry again for my creating unneeded issue.
Regards!


Added /constants endpoint

Tests failing? My guess is it's trying and failing to test the new endpoint.

All  builds seem to be failing for some reason during setup


Not getting coords without internet [ Geolocator.getCurrentLocator() ]

🐛 Bug Report

Geolocator.getCurrentLocation()

Not returning data without internet.
Expected behavior
As coords are not dependent on internet connection. So, plugin should return coords.
Reproduction steps
Just try to call the below code without internet

Geolocator.getCurrentLocation()

Configuration
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.0, on macOS 12.6 21G115 darwin-x64, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✗] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
        sudo xcodebuild -runFirstLaunch
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the
        Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To install see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] VS Code (version 1.72.2)
[✓] VS Code (version 1.72.2)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

! Doctor found issues in 1 category.

Version: 1.x
geolocator: ^9.0.2
Platform:

[ ] :iphone: iOS
[x] :robot: Android

Same problem here ... Did you find a solution ?

Same issue here, these are some devices where I was able to reproduce
• EDA71 G (mobile)  • 21113B1FCB         • android-arm64  • Android 8.1.0 (API 27)
• SM G930F (mobile) • 988674424b56494e49 • android-arm64  • Android 8.0.0 (API 26)
• SM G955F (mobile) • ce021712daadea0f02 • android-arm64  • Android 9 (API 28)

The problem still persists
Any update on this?!

Same here, with the permissions:
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />

And the LocationSettings:
LocationSettings(
    accuracy: LocationAccuracy.best,
    timeLimit: Duration(seconds: 10),
 )

But it's working with LocationAccuracy.high. Is there because, best needs the connectivity to return a better position?

Hi everyone!
This might have been caused by a bug in the Android implementation, where we filtered out locations based off their accuracy. Could you confirm that this issue has been resolved?
You would need to pull in the latest version of the geolocator (10.0.1) and run dart pub upgrade. Please check your pubspec.lock file to see if it mentions geolocator_android version 4.2.3.


The user limit on the total number of inotify watches was reached or the kernel failed to allocate a needed resource.

http://stackoverflow.com/questions/24303080/the-user-limit-on-the-total-number-of-inotify-watches-was-reached-or-the-kernel

That issue no longer exists on stackoverflow, so we should just close this issue.


Youtube app share doesn't work

I can't get the android youtube share to this app to work. sharing from other sites works.

It works on my phones both on alpha and beta versions of the app.
The expected behaviour should be something like this:

You open Youtube select a video and share youtube Link into metube app
Metube app opens with Open URL dialog with the video URL in it.
You press open and it adds to Metube server for downloading.

Is the open URL dialog appears for you with Youtube URL in it when you share from Youtube app? Is there any error message or something?

its working now i tried a differed video today. my guess is it was a previse downloaded video.


Fix Touch pointCount for web

Adds a reset for the CORE.Input.Touch.pointCount for web, if it was the last EMSCRIPTEN_EVENT_TOUCHEND event.
Fixes https://github.com/raysan5/raylib/issues/3100.

@ubkp thanks for the review!


use /usr/bin/vi instead of /usr/share/dict/words as test input

…ilable to unblock CI work.

@dgrove-oss Can you please create a bug for this test, so we can enable the test in the future?
Thanks!
FAIL: dispatch_io
PASS: dispatch_io_net
PASS: dispatch_select
make[4]: Entering directory `/home/buildnode/disk2/workspace/oss-swift-incremental-RA-libdispatch-linux-ubuntu-14_04/Ninja-ReleaseAssert/libdispatch-linux-x86_64/tests'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/home/buildnode/disk2/workspace/oss-swift-incremental-RA-libdispatch-linux-ubuntu-14_04/Ninja-ReleaseAssert/libdispatch-linux-x86_64/tests'
============================================================================
Testsuite summary for libdispatch 1.3
============================================================================
# TOTAL: 26
# PASS:  25
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

@swift-ci Please test Linux

we just need "a large file" could you instead use a file that is here on any distribution that is large enough? /bin/systemctl is 500K /usr/bin/vi is probably also always here and in the MB range
disabling test is wrong

Sure.  I can write the tests to look for different files instead.   I've got the configure check working, so I will probably keep it and check for different input files.    While we're playing with this, dispatch_io also wants another file (but skips the test without failing if it isn't there):
#if TARGET_OS_EMBEDDED
#define LARGE_FILE "/System/Library/Fonts/Cache/STHeiti-Light.ttc" // 29MB file
#define maxopenfiles 768
#else
#define LARGE_FILE "/System/Library/Speech/Voices/Alex.SpeechVoice/Contents/Resources/PCMWave" // 417MB file
#define maxopenfiles 4096
#endif

Suggestions for a replacement file here that will likely be on a distro?

Can't we just create a file in a temporary directory?

I'm taking Pierre's suggestion and using /usr/bin/vi as the input file instead.  The configure check is probably overkill.  Will push an update in a couple of minutes (testing it locally not).

@swift-ci please test linux

@swift-ci please test linux

Build timed out (after 166 minutes). Marking the build as failed.
Build was aborted

The fail was in the dispatch_pingpong test, so not related to this change.
Below is the output of the test log file:
==================================================
[TEST] Dispatch Ping Pong
[PID] 32399
==================================================

[BEGIN] dispatch_queue_create(ping)
	Actual: 0x1b50c40
	Expected: 0x1b50c40
[PASS] dispatch_queue_create(ping)

[BEGIN] dispatch_queue_create(pong)
	Actual: 0x1b50cf0
	Expected: 0x1b50cf0
[PASS] dispatch_queue_create(pong)

[BEGIN] dispatch_group_create
	Actual: 0x1b50d80
	Expected: 0x1b50d80
[PASS] dispatch_group_create

[BEGIN] Process exited
	Actual: 1
	Expected: 0
[FAIL] Process exited (bsdtestharness.c:132)
	bsdtestharness.c:132
[PERF]	wall time: 0.000100
[PERF]	user time: 0.068000
[PERF]	system time: 0.004000
[PERF]	max resident set size: 17580
[PERF]	page faults: 0
[PERF]	swaps: 0
[PERF]	voluntary context switches: 44
[PERF]	involuntary context switches: 10
FAIL dispatch_pingpong (exit status: 1)

is there something different in the build machines, the steps taken to build/test or the environment for testing pull requests against dispatch vs. the other CI testing that includes building & testing dispatch on Linux?   A couple of the recent dispatch pull requests have failed by hanging while running dispatch_pingpong, but as far as I know we've never seen that hang happen in other CI configurations with dispatch and I can't reproduce it locally.

I've seen the dispatch_pingpong failure maybe twice in the wider libdispatch CI.  The CI env is running with 48 CPUs, which is a little larger than I have locally - that might be part of the issue.

Any update here @seabaylea or @dgrove-oss? We're still blocked on merging URLSession because dispatch tests aren't passing.

I want to see if this fails again in the same way.

@swift-ci test linux

This one should be good - we've got a couple of other failures though. I'm currently looking at those.

I'm going to merge this. We will put up a different PR to disable the pingpong test, so as to make some forward progress here.


Use source generators to register profiles instead of reflection

https://www.jetbrains.com/dotnet/guide/tutorials/dotnet-days-online-2022/lets-build-an-incremental-source-generator-with-roslyn/


[Issue 11036][client] Producer BatcherBuilder configuration property

Fixes #11036
Motivation
See #11036 for background on this PR
Modifications
Added a getter/setter pair for batcherBuilderType on the ProducerConfigurationData class, which manipulate the batcherBuilder attribute, based on an enum. This allows for easy mapping to/from properties and json format.
Verifying this change

[ ] Make sure that the change passes the CI checks.

This change added tests and can be verified as follows:

Extended ConfigurationDataUtilsTest::testLoadProducerConfigurationData

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no: config property added, not actual cli options)
Anything that affects deployment: (no: config property added, but default didn't change)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (docs: client-libraries-java.md)

I added more coverage wrt the batcherBuilderType producer property

@eolivelli could you have another look please?

The pr had no activity for 30 days, mark with Stale label.

Closed as stale and conflict. Please rebase and resubmit the patch if it's still relevant.


Fix syntax errors when creating UDR and route for Azure Firewall

There was an error using the location in the following command (line 367):
az network route-table create -g $RG -$LOC --name $FWROUTE_TABLE_NAME
Additionally, the variable for subscription ID wasn't initialized (line 368). Substituted it with:
az network route-table route create -g $RG --name $FWROUTE_NAME --route-table-name $FWROUTE_TABLE_NAME --address-prefix <IP_ADDRESS>/0 --next-hop-type VirtualAppliance --next-hop-ip-address $FWPRIVATE_IP --subscription $(az account show --query id -otsv)
I chose that way, because that's the only command where subscription ID is needed.

@cdennig : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks for the PR! There's already one in flight that adds the subID and adds the -l argument, that should solve this issue as well
#please-close


Issue/70/window contents inherit bounds

It isn't so much that the values are inherited, it's that they are propagated / cascaded downwards.


⚠ Home 主页 has degraded performance

In 7aba18e, Home 主页 (https://www.fangkehou.eu.org) experienced degraded performance:

HTTP code: 200
Response time: 5705 ms

Resolved: Home 主页 performance has improved in 31b1b6b.


Retrieving a byte vector from BitSlice

Hi,
Sorry if this question is answered somewhere in the documentation, I checked and couldn't find it.
Is there a way to convert a BitSlice to Vec of u8? And if so, how is the padding handled if the number of bits is not multiple of 8?

There is, but it's not a direct path and so doesn't show up in the BitSlice docs.
Clone the BitSlice to a BitVec with .to_owned(), then call .into_vec() on the BitVec to get a plain Vec. Dead bits in the slice edges are left as they are, but I could probably make the library erase them.
In the current master branch and upcoming 0.16 release, BitVecs can have padding on both edges, so you will want to call .force_align() on the BitVec before consuming it.
Also on current master and upcoming 0.16 is the ability to copy a BitSlice directly into an array on the stack. This requires picking a size at compile-time, so it's not suited for dynamic slices, but it does avoid the issue of padding at the front edge. Calling .as_native::() on a BitSlice will copy directly into a stack array.
let bits = some_bitslice();
let mut bv = bits.to_owned();
bv.force_align(); // master and 0.16+ only
bv.into_vec()

Alexander Payne
Software Engineer, Space Dynamics Laboratory

From: Ivan Brko<EMAIL_ADDRESS>Sent: Monday, September 9, 2019 7:59:50 AM
To: myrrlyn/bitvec<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [myrrlyn/bitvec] Retrieving a byte array from BitSlice (#27)
Hi,
Sorry if this question is answered somewhere in the documentation, I checked and couldn't find it.
Is there a way to convert a BitSlice to Vec? And if so, how is the padding handled if the number of bits is not multiple of 8?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmyrrlyn%2Fbitvec%2Fissues%2F27%3Femail_source%3Dnotifications%26email_token%3DABNFSVODNNOZ7OBHDNF6ZEDQIZJFNA5CNFSM4IU3STKKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HKFZ7XA&data=02|01||175a9acf401d4a1c0fa508d7352dfb59|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637036343909715759&sdata=ImfBZrgkXQUB9LDZ8GSW5%2BMhroP%2F4GfmjZEtukkEkWo%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABNFSVLZNUJBPE6AFCWW4M3QIZJFNANCNFSM4IU3STKA&data=02|01||175a9acf401d4a1c0fa508d7352dfb59|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637036343909725764&sdata=U2Q%2F9nODo96VL0YHw0UsuhYfDiaFaFO%2F5RUjnS5Wn6Y%3D&reserved=0.

Wow, that was fast.
Thanks a lot!


Remove map file from public assets

The map files were added because of #46, production builds fail without them. Is there a reason to remove them in general?

I removed them because they were causing my deployments to fail. Removing that line locally enables me to deploy my app to our staging environment. Here's the issue I opened in ember-attacher. https://github.com/kybishop/ember-attacher/issues/87
Perhaps there's another way to resolve the issue that keeps everything working as desired?

Really weird. Yeah this points to something fundamentally wrong here if some production builds will fail with them and some will fail without them 🙃
Can you post your ember-cli setup? Versions of cli and related addons and anything custom you might have with ember-cli-uglify, sourcemaps, and fingerprinting would definitely help

Sure, here are the relevant parts of ember-cli-build.js
/* eslint-env node */
'use strict';

const EmberApp = require('ember-cli/lib/broccoli/ember-app');

function getUrlPrefix(environment) {
  if (environment === 'production') {
    return 'https://assets.company.com/';
  }
  if (environment === 'staging') {
    return 'https://assets-staging.company.com/';
  }
  return '';
}

module.exports = function(defaults) {
  var environment = process.env.EMBER_ENV;

  var isProduction = ['production', 'staging'].indexOf(environment) > -1;

  var options = {
    minifyCSS: {
      enabled: isProduction
    },
    minifyJS: {
      enabled: isProduction
    },
    sourcemaps: {
      enabled: true
    },
    tests: process.env.EMBER_CLI_TEST_COMMAND || !isProduction,
    hinting: process.env.EMBER_CLI_TEST_COMMAND || !isProduction,
    fingerprint: {
      enabled: isProduction,
      prepend: getUrlPrefix(environment),
      extensions: ['js', 'css', 'png', 'jpg', 'gif', 'map', 'svg'],  // Default + svg
    }
  }

  let app = new EmberApp(defaults, options);

  return app.toTree();
};

And here are the relevant parts of config/deploy.js:
    // do not gzip .map or .js files, sentry does not unzip
    ENV.gzip = {
      filePattern: '**/*.{css,json,ico,xml,txt,svg,eot,ttf,woff,woff2}',
    };

    // do not upload .map files to S3, sentry will map the correct .map files post-exception
    // see: https://docs.sentry.io/clients/javascript/sourcemaps/#uploading-source-maps-to-sentry
    ENV.s3 = {
      filePattern: '**/*.{js,css,png,gif,ico,jpg,xml,txt,svg,swf,eot,ttf,woff,woff2,otf}',
    };

    ENV['s3-index'] = {
      allowOverwrite: true,
    };

I'm guessing my issue has something to do with the fact that we don't upload map files to s3 because of an issue with Sentry. Hrm...

And it looks like my deploy config was the source of the problem. Removing .map files from fingerprint.extensions resolves the issue. I'm closing the PR. Thanks!


tcl regression scripts

Just noticed that CI is using tcl regression scripts for all unix-like platforms. Was this intentional or accidental?
Tcl scripts don't report failure when the tests fail so issues during regression go unnoticed.
@hzeller You updated the workflow script recently. Any reasoning?

Ah, I was mostly playing with the new right-aligned numbers there and it also provides the sum of CPU time of all tests ('total user time') which gives a good idea of performance (whereas the Python version just showed the test with the maximum time). Since I needed more accurate process timing information then while working on some things to not introduce performance regressions (until #2802 is using operating system provided process information), it was also useful.
Anyway, ok to change back now (though it would be useful if the regression.py also had right aligned numbers and a sum of user time).

Fixed by #2897


Moved temperature to shared

About the PR

Moved Temperature component, ThermalRegulator component and most of the implementation of temperature, thermal regulation and heater systems to Content.Shared. This will allow shared content to interact with TemperatureComponent without requiring a ServerSide implementation. This does not implement predicted temperature, it only networks the component states.
Why / Balance

No visible changes for players. This was done to make working with temperature in shared systems easier.
Technical details

Simply moved temperature, thermal regulation and heater systems to shared along with their associated components. I also networked the components to make sure that the data is accessible on the client as well. I did not implement prediction since temperature interacts with atmospherics which is a purely server-side system and would make prediction more difficult. Values on temperature related components are calculated on the server and then networked to the clients.
Media

Requirements

[X] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Namespace changes:
ThermalRegulatorComponent: Content.Server.Body.Systems -> Content.Shared.Body.Systems
ChangeTemperatureOnCollideComponent: Content.Server.Temperature -> Content.Shared.Temperature
ContainerTemperatureDamageThresholdsComponent: Content.Server.Temperature -> Content.Shared.Temperature
EntityHeaterComponent: Content.Server.Temperature -> Content.Shared.Temperature
InternalTemperatureComponent: Content.Server.Temperature -> Content.Shared.Temperature
TemperatureComponent: Content.Server.Temperature -> Content.Shared.Temperature
TemperatureProtectionComponent: Content.Server.Temperature -> Content.Shared.Temperature

Obsolete methods (will be removed in the future):
public void ForceChangeTemperature(EntityUid target, float temp, TemperatureComponent? temperature = null)
public float GetHeatCapacity(EntityUid uid, TemperatureComponent? comp = null, PhysicsComponent? physics = null)
public void ChangeHeat(EntityUid uid, float heatAmount, bool ignoreHeatResistance = false, TemperatureComponent? temperature = null)

Changelog

I think this one is a duplicate of #30511
Not sure if it includes all the same files though.

crusher dagger disgustingly op

I think this one is a duplicate of #30511 Not sure if it includes all the same files though.

I totally forgot about that one 😅
That said, this implementation puts less networking load on the server (Temperature components aren't being dirtied every tick only when they actually get changed)

Hey, when will you continue working? Or someone on vacation... Just wondering, nothing more

Я думаю, что это дубликат #30511. Не уверен, что он содержит все те же файлы.

Я совсем забыл об этом 😅 Тем не менее, такая реализация снижает сетевую нагрузку на сервер (компоненты температуры не обновляются каждый тик, а только при фактическом изменении)

If you think about it, how soon can you temperature refactor ?

Due to various reasons I have decided to no longer directly be involved
with the development of wizden, and as such I will be closing this PR.
If someone else wishes to take up/re-open this PR and continue developing it,
they have my permission to do so.
A more in depth explanation can be found here: https://discord.com/channels/310555209753690112/770682801607278632/1321967056446554174.


check that localstorage and card are in sync

comparing roots

replaced by https://github.com/deora-earth/voting-frontend/pull/51


Add chill portion and chill units

Closes #1753
TODO:

[x] Tests for the changes have been added (for bug fixes / features)

[x] (If applicable) Documentation has been added / updated (for bug fixes / features)
[x] Test make_hourly_temperature
[x] Test chill_portions
[x] Test chill_units

[x] CHANGELOG.rst has been updated (with summary of main changes)

[x] Link to issue (:issue:number) and pull request (:pull:number) has been added

[x] Check make_hourly_temperature is working with other calendars than 360_day

What kind of change does this PR introduce?

Adds a chill_portion indicator based on the Dynamic model
Adds a chill_unit indicator based on the Utah model
Adds a helper function to estimate hourly temperatures from daily tasmin and tasmax

I am still trying to figure out what the functions should return. Right now, the chill_portions returns an aggregated value per year but chill_units a value per hour that can be aggregated at will. Ideally, they would work the same but chill_portions are significantly harder to aggregate since an hours value depends on the previous hour's value. This also has implications on computing chill portions for a season. For chill units, you can simply select the range of days or hours afterwards and aggregate but for chill portions you need to select the period before and I could imagine this messing with the ResamplingIndicator class that fills missing data   (@aulemahal ?) so I guess I need to do it inside the function?
As you can see in the current implementation of chill_portions, I am doing a yearly grouping to get the values per year but this would fail if you're interested in a season crossing new years (e.g. Nov-Feb). We do a trick where we shift the day so the season is within a year but that's only easy if you assume a 360_day calendar.

I am also not sure what the IndexingIndicator class exactly is doing?

injects "indexer" kwargs to subset the inputs before computation.
sounds a little like what I am suggesting to do but I couldn't find how exactly it works?

For now, I am keeping the logic to only take certain day ranges outside the functions but I think it should be included. Happy to discuss a mechanism on how to do that if we decide to do so. Tomorrow, I will add the test for chill portions and I think its ready for review

Ready for review @aulemahal

Haha. Its only problematic if you had no idea that something like YS-JUL existed ... Alright, that solves a lot. Will implement  the indexer solution for chill_portions and test it.

also linking @eikeluedeling who formalised the method for chill portions.

Sorry for the delay. I think these translations are good enough. I have asked the opinion of a colleague but we could merge away when the tests pass.

For the record, I have found only one french language document discussing the chill units and portions, and they didn't translate the names : https://archipel.uqam.ca/7003/1/M13555.pdf
My colleague nonetheless thinks we should translate them, which I did in the last commit. Especially in the context of  xclim, the translated attributes never appear by themselves, so there's no ambiguity.
But I'm guessing you don't really care about all that,  and I can understand.  This requirement of french translations makes less and less sense as the number of non-Ouranosinc contributors grows...
Hopefully this last commit also triggers the correct set of CI jobs and we can merge.

coverage: 89.435% (+0.06%) from 89.374%
when pulling 427a3136ad88ad05e2f93ed4e668eb084f173693 on saschahofmann:chilling
into<PHONE_NUMBER>64ddfecf71fb2b81828dcc64987719 on Ouranosinc:main.

Thanks @saschahofmann !

Awesome thank you so much !

Hi, I've been using the Utah chill unit model for my research but my code is a mess and time-consuming so I'm happy to see it implemented in xclim (thanks @saschahofmann for that)! I did some tests with my data today and wanted to inform you about two things I've noticed.
Memory issue
First, it's more a warning than an issue. Because chill_unit uses hourly data, some memory errors can occur using an important dataset while the computation of other indices or indicators with the same dataset (but daily resolution) is fine. This can be handled easily by iterating over the years and it's what I've done. However, I think it could be relevant to add a warning message when using make_hourly_temperature. What do you think about this?
Output bug
The second is make_hourly_temperature adds one more day to compute the hourly temperature but does not remove it after the computation, thus returning an array with a shape different to the inputs. See below for data corresponding to a complete year with a shape (time: 365, lat: 56, lon: 54) as input:
>>> data_yr['tasmin'].shape, data_yr['tasmax'].shape
((365, 56, 54), (365, 56, 54))
>>> make_hourly_temperature(data_yr['tasmin'], data_yr['tasmax']).resample(time='D').mean().shape
(366, 56, 54)

This is particularly annoying if the input data ends on the last day of the year and a resampling YS is done, creating a year at the end considering only one day.
>>> hourly_temp = make_hourly_temperature(data_yr['tasmin'], data_yr['tasmax'])
>>> cu = chill_units(hourly_temp, freq='YS')
>>> print(cu)
<xarray.DataArray (time: 2, lat: 56, lon: 54)> Size: 48kB
dask.array<stack, shape=(2, 56, 54), dtype=float64, chunksize=(1, 56, 54), chunktype=numpy.ndarray>
Coordinates:
  * lat      (lat) float64 448B -47.38 -47.12 -46.88 ... -34.12 -33.88 -33.62
  * lon      (lon) float64 432B 166.1 166.4 166.6 166.9 ... 178.9 179.1 179.4
  * time     (time) datetime64[ns] 16B 2100-01-01 2101-01-01
Attributes:
    units:    1

I hope my explanations are clear enough! Thanks !


Last exported state is Failed when exporting many tables

Hello all,
We export a larger number of tables (currently only with a few data). The export seems to be successful, but for some tables the "Last exported state" is displayed as Failed. However, we could see that the data seems to be successfully transferred to the delta folder in ADLS anyway. When we restart the export, the number of failed tables decreases. After 3-4 times all are successful. The message looks like this:

Has anyone had experience with this?

What is a “large number of tables” exactly..? Can you share some more details? I’ve done a setup with 40 tabels without any issues.


Add myself as a codeowner default

This means that you must review every single PR, even all the dependabot bumps. Are you sure?

I want my approvals to carry the same weight as a code owner. I do not want to hold up every PR though.


Add NCEI metrics

Number of packages archived since x date.
Split by hf radar, glider, ATN (once operational), etc

See:

https://gist.github.com/MathewBiddle/c7ccab625b09897ccf7d37497d302c0b
https://github.com/MathewBiddle/nceipy/blob/main/notebooks/ncei_metadata_collection.ipynb
https://ioos.github.io/ioos_code_lab/content/code_gallery/data_access_notebooks/2017-06-12-NCEI_RA_archive_history.html


Patch/openstack driver

This PR splits out Openstack functionality into its own driver.  Further enhancements after 0.2 will abstract some functionality and likely consolidate Rackspace into the Openstack driver.

This fixes https://github.com/emccode/rexray/issues/111


Updates to enable static weight quantization + Static & Dynamic Activation quantization

Summary
This is are the needed changes to enable this script:
import torch
import copy

import torch.nn as nn
from float8_experimental.float8_linear_utils import swap_linear_with_float8_linear

import torch.nn as nn
import torch.nn.functional as F
from torch._inductor.utils import do_bench_using_profiling

from float8_experimental.float8_dynamic_linear import Float8DynamicLinear

def benchmark_cuda_function_in_microseconds(func: Callable, *args, **kwargs) -> float:
    """Thin wrapper around do_bench_using_profiling"""
    no_args = lambda: func(*args, **kwargs)
    time = do_bench_using_profiling(no_args)
    return time * 1e3

class FeedForward(nn.Module):
    def __init__(self) -> None:
        super().__init__()
        self.w1 = nn.Linear(4096, 14336, bias=False)
        self.w3 = nn.Linear(4096, 14336, bias=False)
        self.w2 = nn.Linear(14336, 4096, bias=False)

    def forward(self, x: torch.Tensor) -> torch.Tensor:
        return self.w2(F.silu(self.w1(x)) * self.w3(x))

if __name__ == "__main__":
    compile_backend = "inductor"
    original_mlp = FeedForward()
    original_mlp = original_mlp.to("cuda").to(torch.bfloat16)
    dynamic_fp8_mlp = copy.deepcopy(original_mlp)
    static_fp8_mlp = copy.deepcopy(original_mlp)

    batch_size = 4
    num_tokens = 1024
    embedding_dim = 4096

    input_tensor = torch.randn(batch_size, num_tokens, embedding_dim, device="cuda", dtype=torch.bfloat16)

    compiled_original_mlp = torch.compile(original_mlp, backend=compile_backend)
    with torch.no_grad():
        for _ in range(10):
            compiled_original_mlp(input_tensor)

        bf16_time = benchmark_cuda_function_in_microseconds(compiled_original_mlp, input_tensor)
        print(f"{bf16_time=}us")

    with torch.no_grad():
        swap_linear_with_float8_linear(
            dynamic_fp8_mlp,
            Float8DynamicLinear,
            from_float_kwargs={"static_quantize_weight": True},
        )
        compiled_dynamic_fp8_mlp = torch.compile(dynamic_fp8_mlp, backend=compile_backend)
        for _ in range(10):
            compiled_dynamic_fp8_mlp(input_tensor)

        fp8_dynamic_activations_time = benchmark_cuda_function_in_microseconds(compiled_dynamic_fp8_mlp, input_tensor)
        print(f"{fp8_dynamic_activations_time=}us")

    with torch.no_grad():
        swap_linear_with_float8_linear(
            static_fp8_mlp,
            Float8DynamicLinear,
            from_float_kwargs={"static_quantize_weight": True, "activation_scale": torch.tensor([1.0], device="cuda", dtype=torch.float32)},
        )
        compiled_static_fp8_mlp = torch.compile(static_fp8_mlp, backend=compile_backend)
        for _ in range(10):
            compiled_static_fp8_mlp(input_tensor)

        fp8_static_activations_time = benchmark_cuda_function_in_microseconds(compiled_static_fp8_mlp, input_tensor)
        print(f"{fp8_static_activations_time=}us")

Performance
In eager this produces:

Metric
Time (us)

bf16_time
2651.3976666666676

fp8_dynamic_activations_time
2476.8851578947388

fp8_static_activations_time
2459.5283846153816

With compile this produces:

Metric
Time (us)

bf16_time
2558.1800000000007

fp8_dynamic_activations_time
1546.1596000000022

fp8_static_activations_time
1411.3195846153856

On simple static weight and activation mlp I am seeing a copy_ error

    swap_linear_with_float8_linear(
            static_fp8_mlp,
            Float8DynamicLinear,
            from_float_kwargs={"static_quantize_weight": True, "activation_scale": torch.tensor([1.0], device="cuda", dtype=torch.float32)},
    )

    print(f"out_static = {static_fp8_mlp(input_tensor)}")
    torch.save(static_fp8_mlp.state_dict(), "/home/drisspg/meta/scripts/fp8/saving/dumm_dict2.pt")

    static_load = torch.load("/home/drisspg/meta/scripts/fp8/saving/dumm_dict2.pt")
    static_fp8_mlp.load_state_dict(static_load)
    print(f"out_static_load = {static_load(input_tensor)}")

RuntimeError: Error(s) in loading state_dict for FeedForward:
       While copying the parameter named "w1.weight", whose dimensions in the model are torch.Size([14336, 4096]) and whose dimensions in the checkpoint are torch.Size([14336, 4096]), an exception occurred : ('attempting to run aten.copy_.default, this is not supported',).
       While copying the parameter named "w3.weight", whose dimensions in the model are torch.Size([14336, 4096]) and whose dimensions in the checkpoint are torch.Size([14336, 4096]), an exception occurred : ('attempting to run aten.copy_.default, this is not supported',).
       While copying the parameter named "w2.weight", whose dimensions in the model are torch.Size([4096, 14336]) and whose dimensions in the checkpoint are torch.Size([4096, 14336]), an exception occurred : ('attempting to run aten.copy_.default, this is not supported',).
       ```

@ani300 I imagine you were doing some state_dict loading for Float8Tensors?

On simple static weight and activation mlp I am seeing a copy_ error
    swap_linear_with_float8_linear(
            static_fp8_mlp,
            Float8DynamicLinear,
            from_float_kwargs={"static_quantize_weight": True, "activation_scale": torch.tensor([1.0], device="cuda", dtype=torch.float32)},
    )

    print(f"out_static = {static_fp8_mlp(input_tensor)}")
    torch.save(static_fp8_mlp.state_dict(), "/home/drisspg/meta/scripts/fp8/saving/dumm_dict2.pt")

    static_load = torch.load("/home/drisspg/meta/scripts/fp8/saving/dumm_dict2.pt")
    static_fp8_mlp.load_state_dict(static_load)
    print(f"out_static_load = {static_load(input_tensor)}")

RuntimeError: Error(s) in loading state_dict for FeedForward:
       While copying the parameter named "w1.weight", whose dimensions in the model are torch.Size([14336, 4096]) and whose dimensions in the checkpoint are torch.Size([14336, 4096]), an exception occurred : ('attempting to run aten.copy_.default, this is not supported',).
       While copying the parameter named "w3.weight", whose dimensions in the model are torch.Size([14336, 4096]) and whose dimensions in the checkpoint are torch.Size([14336, 4096]), an exception occurred : ('attempting to run aten.copy_.default, this is not supported',).
       While copying the parameter named "w2.weight", whose dimensions in the model are torch.Size([4096, 14336]) and whose dimensions in the checkpoint are torch.Size([4096, 14336]), an exception occurred : ('attempting to run aten.copy_.default, this is not supported',).

@ani300 I imagine you were doing some state_dict loading for Float8Tensors?

Hey, we were quantizing bf16 weights on the fly from our checkpoints, but I think we'll do something akin to AutoFP8 (https://github.com/neuralmagic/AutoFP8) to handle the FP8 checkpoints and load into Float8Tensors


Matrix exponentiation never worked

Try it Online! They should be equivalent
This might be a mutability-related bug.
THIS IS WHY WE HAVE TESTS

Nothing to do with mutability.
It was looping one too many times.
Also, it wasn't actually doing matrix multiplication. It was only doing normal multiplication.
And we do have tests btw

It's just that no one caught the misinterpretation of what matrix exponenation meant in #824


RichTextLabel bbcode refers to the wrong unicode for [ul] bullet points

Godot version
4.0.stable.official
System information
Ubuntu 22.04.2
Issue description
When creating an unordered list with RichTextLabel's bbcode, some fonts will display an oversized bullet point, while others appear normal. I'm 99% sure that this is because Godot is referencing the incorrect Unicode for bullet points.
Here are three identical RichTextLabels except for their differing fonts. I used Franklin Gothic Demi Regular, Ubuntu Regular, and Kanit Regular.

The reason I suspect incorrect unicode is that I dug into the TTF files for these three fonts. They all have normal and similar-sized bullet points at the usual unicode: U+2022. But I believe Godot is actually referencing U+25cf ("black circle"). Franklin Gothic Demi, the font that works as expected, has an entry for U+25cf. The other two fonts do not.
I also found this other open issue #69920 that seems to show that Godot is using U+25cf for bullet points.
Steps to reproduce
Download a few different fonts, assign them to different RichTextLabels, enable bbcode and type some list items with the [ul]{ list }[/ul] format.
Minimal reproduction project
N/A (I tried adding one but either Chrome or Linux isn't cooperating, sorry. I'll try again later.)

cc @bruvzg
I've noticed this too and would prefer having a smaller bullet point.

I think it’s literally an error. When I googled it, every site lists 2202 as the Unicode for bullet points.

By the way, this might just be an issue on Linux. The bullet points look fine on Windows. Haven't tested Mac.

Indeed, it's using 25CF (I believe it was selected to display color of the color constants in the docs, and then copy-basted to the rest of docs and RTL). Probably should be customizable.

On the plus side, I think it should be pretty easy to just copy the character in 2022 to the 25CF spot using FontForge, as a temporary workaround. But yeah, customizable would be amazing.


README

Thanks for awesome work.
Please add in description that you need to have http php module installed (http://pecl.php.net/package/pecl_http) to use \Zend\Uri, I spent some time to understand WTF it does not work!

Done


Sometimes difficult to read action (/me) message which tags the user

Describe the bug
If another user sends an "action" (message starting with "/me") that tags me, it's difficult to see the tag if the foreground and background colors are very similar.  See screen-shot.
To Reproduce
Have someone set their name color to red and then send a message beginning with "/me" that includes your user name.
Expected behavior
I would expect the foreground color inside the tag to be white, rather than red, so it has contrast vs. the red tag background.
Screenshots

Environment

Software
Version

YaTA
1.13.3

Browser
Firefox 74.0

Operating System
Windows NT 10.0

Thanks for the detailed report as usual. This will be fixed in the next version.
Before:

After:


[MM-38695] Fixed minimize to tray setting on Linux

Summary
This PR fixes the 'minimize to tray' setting on Linux, as it was not changeable. This enables a user to uncheck the setting if they don't have a system tray to work with, thus allowing the window to minimize to the GNOME app bar if needed.
Ticket Link
https://mattermost.atlassian.net/browse/MM-38695
Release Note
NONE

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/desktop/13776
https://circleci.com/gh/mattermost/desktop/13775
https://circleci.com/gh/mattermost/desktop/13774

disabling the checkbox as in the screenshot brings back the old behavior which at least helps with not having to manually kill the mattermost app process so this is definitely a win for now.

Cherry pick is scheduled.


Evaluator Review: FACINGS NFT Collection Manager Stage 2 - Milestone 2 delivery

Review, approve, or deny https://github.com/eosnetworkfoundation/grant-milestones/pull/106#event-9812846883

Closed per approval comments in https://github.com/eosnetworkfoundation/grant-milestones/pull/106#event-9812846883.


Note about Keywords field

@markjjo - The Keywords field can include any of the fields listed in the Searchable field name using KQL, this is similar to how workload search works, except in AeD there are lots more conditions so people don't use this approach often.  Feel free to re-word or give me a shout if you have any questions.

@mahage-msft PR editing and merged


JUnit format show stdout/stderr

Will be great to see actual stdout/stderr in JUnit formatter from "command" check if we testing stdout/stderr pattern
goss.yaml:
command:
    check-package.py:
        exit-status: 0
        stdout:
        - "Missing: []"
        - "Conflicts: []"

here is current result (v0.2.4)
<testcase name="Command check-package.py exit-status" time="0.421">
<system-err>
Command: check-package.py: exit-status: doesn't match, expect: [0] found: [1]
</system-err>
<failure>
Command: check-package.py: exit-status: doesn't match, expect: [0] found: [1]
</failure>
</testcase>
<testcase name="Command check-package.py stdout" time="0.000">
<system-err>
Command: check-package.py: stdout: patterns not found: [Missing: [], Conflicts: []]
</system-err>
<failure>
Command: check-package.py: stdout: patterns not found: [Missing: [], Conflicts: []]
</failure>
</testcase>

and command run result
$ check-package.py
Satisfied: []
Conflicts: ['argparse<=1.3.1,>=1.2.0']
Missing: []

for exit-status goss returns actual exit-code - "found: [1]", but stdout not.

I was just going to file an issue for this.
✗ build/bin/goss --version
goss version v0.3.6

goss_example.yaml
command:
  echo 'hello world:
    exit-status: 0
    stdout:
      - 'Hello World'

Using all of the formats, I was unable to get an output report that captured the stdout/stderr of a failed test.

Being tracked here: https://github.com/aelsabbahy/goss/issues/483


Close icon in sticky navigation borken for mobile phones

The ‘'close’' icon of sticky navigation on mobile devices is not rendered or broken. Happens on android and iOS.

@justintemps I think we were not able to reproduce this issue. Can you provide an example of where this is broken?

This was fixed with #834


Windows binary executable is not working

In the CI, it errors with "line too long error". On desktop, it exits silently after extracting atom without any messages.

This is resolved with 1.8.0


New version "v1.7.0" does not export "splitCookiesString" function

Environment
Node 18.16
Reproduction
import { splitCookiesString } from 'h3';
Describe the bug
After update from v1.6.6 -> v1.7.0 build fails because my code fails to import:
import { splitCookiesString } from 'h3';
Additional context
No response
Logs
No response

Hi. Thanks for reporting however checking published package, it seems splitCookiesString export is there (check last line in<EMAIL_ADDRESS>Would be nice if you can share a reproduction if still having some issues would be happy to help 🙏🏼


chore(Topology/{Compactness/Compact}, Irreducible}): rename type variables

X, Y, Z are standard mathematical names for topological spaces.
As discussed on zulip, let us rename them.
As a drive-by commit, re-use the declared variables $\iota$, $s$ and $t$ (more) when stating theorems.

I'm following by checklist here.

X, Y, Z are standard mathematical names for topological spaces.

I'm not sure if this is true in mathlib; I've seen greek letters in lots of places too. There is only one mention of topology in the style guide, and it uses [DiscreteTopology α]!

X, Y, Z are standard mathematical names for topological spaces.

I'm not sure if this is true in mathlib; I've seen greek letters in lots of places too. There is only one mention of topology in the style guide, and it uses [DiscreteTopology α]!

I agree that Greek letters are persive in topology files. In math textbooks, I've always seen X, Y, Z etc., though. Hence, my guess was that general topology files, being old enough, were written when Greek letter prevailed. (It's possible I'm wrong, though!)

I've asked on zulip.

awaiting-author

I'm sorry we haven't been quick enough to merge that one. Could you please try to fix the conflicts?

@PatrickMassot Updated; as soon as this passes CI, it should be ready to review.
The merge meant I had to basically re-do these changes; it might be easier to just review/skim all commits since the merge separately. (They're logically independent.)

awaiting-review

Thanks for the quick reviews, this time!


 Multi distro support: available. WSL path support: enabled
[2022-05-06 14:14:45.227] No shell environment set or found for current distro.
[2022-05-06 14:14:45.438] WSL daemon log file:
[2022-05-06 14:14:45.440] Probing if server is already installed: C:\WINDOWS\System32\wsl.exe -d Ubuntu-20.04 -e sh -c "[ -d ~/.vscode-server/bin/57fd6d0195bb9b9d1b49f6da5db789060795de47 ] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2022-05-06 14:14:45.584] Probing result: found
[2022-05-06 14:14:45.584] Server install found in WSL
[2022-05-06 14:14:45.585] Launching C:\WINDOWS\System32\wsl.exe -d Ubuntu-20.04 sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" 57fd6d0195bb9b9d1b49f6da5db789060795de47 stable code-server .vscode-server --host=<IP_ADDRESS> --port=0 --connection-token=161348915-4122562144 --use-host-proxy --without-browser-env-var --disable-websocket-compression --accept-server-license-terms --telemetry-level=all'
[2022-05-06 14:14:45.745] Setting up server environment: Looking for /home/manoj/.vscode-server/server-env-setup. Not found.
[2022-05-06 14:14:45.745] WSL version: <IP_ADDRESS>-microsoft-standard-WSL2 Ubuntu-20.04
[2022-05-06 14:14:45.745] WSL-shell-PID: 237
[2022-05-06 14:14:45.745] Node executable: /home/manoj/.vscode-server/bin/57fd6d0195bb9b9d1b49f6da5db789060795de47/node
[2022-05-06 14:14:45.745] Starting server: /home/manoj/.vscode-server/bin/57fd6d0195bb9b9d1b49f6da5db789060795de47/bin/code-server --host=<IP_ADDRESS> --port=0 --connection-token=161348915-4122562144 --use-host-proxy --without-browser-env-var --disable-websocket-compression --accept-server-license-terms --telemetry-level=all
[2022-05-06 14:14:45.751] VS Code Server for WSL closed unexpectedly.
[2022-05-06 14:14:45.751] For help with startup problems, go to
[2022-05-06 14:14:45.751] https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips
[2022-05-06 14:14:45.755] C:\WINDOWS\System32\wsl.exe -d Ubuntu-20.04 -e kill 237

Looks like the server did not properly start. Can you close all VS Code windows and try this:

in a WSL teminal run  rm -r /home/manoj/.vscode-server/bin and try again
if that doesn't help, manually run /home/manoj/.vscode-server/bin/57fd6d0195bb9b9d1b49f6da5db789060795de47/bin/code-server --host=<IP_ADDRESS> --port=0 --connection-token=161348915-4122562144 --use-host-proxy --without-browser-env-var --disable-websocket-compression --accept-server-license-terms --telemetry-level=all and see if there is more helpful error output
restaty WSL with wsl --shutdown in a Windows terminal

point 1 did help....thanks a lot...
I only have one question? why happened in two computers at the same time?

That's a good question. Something is special about build 57fd6d0195bb9b9d1b49f6da5db789060795de47 that causes it to be installed corrupted. I've had similar other reports.
We make a checksum test after unpacking the server so this shouldn't happen, but...

Well... Regardless, thanks a lot for the good support... Greatly appreciated

Hey @aeschli, this issue might need further attention.
@manoj-arkenea, you can help us out by closing this issue if the problem no longer exists, or adding more information.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Model.to_networkx()'s implementation is compiler-dependant

We need to re-implement and add more tests.
It should also return a nx.MultiDiGraph.

Also the current note (as of July 10, 2024)

is incorrect. It should say that it doesn't work on anything except linux.


Revert "enable basic python linting"

Reverts G-Research/NuPerfMonitor#23
@ljubon running pylint in benchmarks workflow is not a good idea.
Benchmarks workflow runs only on the main branch and we don't want that workflow to fail because of formatting issues. We need a new workflow with pylint that runs on the main branch and also on PRs.

Actually, benchmarks workflow does run on all branches. But still we should move the pylint job to separate workflow.


Ctrl + Click is not working when I am using es6 import function in node

file1.js:
import moment from 'moment'

function getNumber() {
    return 2
}
exports.getNumber = getNumber

file2.js:
import { getNumber } from './file1.js'

My CTRL + CLICK is not working for getNumber function in file2.js.
Note: I observed click functionality is working fine in two cases.

When I remove the import function in file1.js
By replacing import function with const moment = require('moment')

If you enable semantic checks in your js files by adding // @ts-check at the top, do you see any errors?

After adding semantic checks, it is showing error Module '"./file1"' has no exported member 'getNumber'.ts(2305)

I don't believe we support mixing import statements with an commonjs style export object. Try using either one style or modules or the other: all commonjs or all import and export statements


test pr

Issue #, if available:
Description of changes:
Testing done:
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[ ] I have read the CONTRIBUTING doc
[ ] I used the commit message format described in CONTRIBUTING
[ ] I have passed the region in to all S3 and STS clients that I've initialized as part of this change.
[ ] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have checked that my tests are not configured for a specific region or account (if appropriate)
[ ] I have used unique_name_from_base to create resource names in integ tests (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-notebook-tests
Commit ID: e3c4a597cf617dbcd412878ff6487a0986154b97
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-local-mode-tests
Commit ID: e3c4a597cf617dbcd412878ff6487a0986154b97
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-slow-tests
Commit ID: e3c4a597cf617dbcd412878ff6487a0986154b97
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-unit-tests
Commit ID: e3c4a597cf617dbcd412878ff6487a0986154b97
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: navinsoni-sagemaker-python-sdk-pr
Commit ID: e3c4a597cf617dbcd412878ff6487a0986154b97
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-notebook-tests
Commit ID: 57556a73511fd200b457e56e5a606d01214ffbda
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-slow-tests
Commit ID: 57556a73511fd200b457e56e5a606d01214ffbda
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-local-mode-tests
Commit ID: 57556a73511fd200b457e56e5a606d01214ffbda
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-unit-tests
Commit ID: 57556a73511fd200b457e56e5a606d01214ffbda
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: navinsoni-sagemaker-python-sdk-pr
Commit ID: 57556a73511fd200b457e56e5a606d01214ffbda
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-notebook-tests
Commit ID: da17b29a9e654c8273bb53338ced63b2284e31c9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-slow-tests
Commit ID: da17b29a9e654c8273bb53338ced63b2284e31c9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-local-mode-tests
Commit ID: da17b29a9e654c8273bb53338ced63b2284e31c9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-unit-tests
Commit ID: da17b29a9e654c8273bb53338ced63b2284e31c9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: navinsoni-sagemaker-python-sdk-pr
Commit ID: da17b29a9e654c8273bb53338ced63b2284e31c9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-notebook-tests
Commit ID: 6a782d959050449afe9508710286a2fa117da06d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-slow-tests
Commit ID: da17b29a9e654c8273bb53338ced63b2284e31c9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-unit-tests
Commit ID: 6a782d959050449afe9508710286a2fa117da06d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-local-mode-tests
Commit ID: da17b29a9e654c8273bb53338ced63b2284e31c9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-local-mode-tests
Commit ID: 6a782d959050449afe9508710286a2fa117da06d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: navinsoni-sagemaker-python-sdk-pr
Commit ID: 6a782d959050449afe9508710286a2fa117da06d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: sagemaker-python-sdk-slow-tests
Commit ID: 6a782d959050449afe9508710286a2fa117da06d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Add the notion of scopes in assignments + implement string interpolation

fix #11

This is a great idea, @MasseGuillaume! And I definitely need that Group/Artifact extractor refactor 😄 Thanks so much for doing this!
A couple thoughts:

I don't think this will currently successfully work in DependencyUpdaterSpec. Would the intention be to fully replace the interpolated string with the newly selected version, or to update just the val foo = "1.23.0" part? In the latter case, we'd need to track where the value was interpolated, so we could pull just the changed part of the new version. Of course, the new version could also have a completely different shape, so maybe fully replacing the original interpolation makes more sense.
Currently, this only supports s"s"v4-rev516-${V.foo}" and not s"v4-rev516-${fooVersion}" (or other potential combinations.

In the current version, I tried to interpret only the simplest of String expressions, just to limit the complexity. Obviously, there'd be edge cases (like this one) that wouldn't get handled, but I'd guess they're less common.
Definitely open to this feature, but just want to make sure all of the edge-cases and design choices are fully explored. Let me know what you think! 😄
The current "solution" I've merged is to ignore such a version expression without blowing up. But obviously that's not ideal.
Thanks again for all this work!

Yeah I realized the complexity when working on the implementation. At work, we have a really really fancy way of composing dependencies with trait mixing, etc etc. Feel free to reuse the GroupArtifact refactor, I will close this PR, I don't think it's a good way to go.

Thanks, Guillaume! Definitely something to keep in mind for a future extension as well :) A fun challenge to anyone who wants it.


Fix use of deprecated hmset command when running the data loader.

The data loader for this project uses the deprecated hmset command.  Fix this to use hset appropriately and remove deprecated hmset:
python load_stations.py
/Users/simonprickett/source/github/introducing-the-geosearch-command/load_stations.py:39: DeprecationWarning: Pipeline.hmset() is deprecated. Use Pipeline.hset() instead.
  pipeline.hmset(station_key, station_data)
Loaded 52 stations.

Use the dict mapping with hset: https://redis-py.readthedocs.io/en/stable/commands.html?highlight=hset#redis.commands.core.CoreCommands.hset
This is part of our participation in Hacktoberfest 2022. Learn how to complete this issue here: https://redis.io/community/hacktoberfest/
Need help or want to talk to us? Join us on Discord where we have a dedicated Hacktoberfest channel: https://discord.gg/ueQwKUh5Z3
If you're interested in taking this issue on, please mention @simonprickett and @SuzeShardlow in the comments and ask to be assigned.

This issue is available and up for grabs.  If you would like to work on it, please reply and tag me and @simonprickett :)

Can you assign it to me? @SuzeShardlow @simonprickett

Hi @meirdev, I've assigned this to you, looking forward to seeing your PR in the next couple of days. Have fun and please check out our guidelines:
https://redis.io/community/hacktoberfest/

#23

Closed by #23.


Implementing aarch64 image build capabilities

In this PR I introduce the ability to use an aarch64 system with EIB, that allows the user to generate either RAW or ISO images with the same architecture, i.e. it's not possible to cross-build with these patches (e.g. x86_64 image on aarch64, or vice versa) as it's a) not possible to currently use the target architecture for the type of images that we cache, nor the hauler/nmc binary architectures, and b) not possible to currently spin up guestfish with a different qemu architecture to be able to run the image modification tools, but I think this is a good step forward to enabling customers to build aarch64 images at this time.
Note that we will need to rebase on leap:15.6 for ISO images, as the aarch64 ISO's need a newer version of xorriso to be able to repack the aarch64 ISO. I've tested these changes on both aarch64 and x86_64 based systems for both raw and iso (albeit with the previous comment in mind, I tested that pathway on 15.6).
Credit for this largely goes to @dbw7 and @diconico07 for their prior investigation and inputs.
Fixes: #193

Not sure whether this should be covered by this PR, but have we tested whether the RPM resolution logic works with the suggested implementation?
I did a quick test on a aarch64 Tumbleweed with your changes + an EIB image using leap:15.6 as base and the RPM resolution logic failed with a libguestfs error. Could be doing something wrong though 🤷

Not sure whether this should be covered by this PR, but have we tested whether the RPM resolution logic works with the suggested implementation?

Tested RPM resolution logic on an arm system using arm SLE Micro. Image was built successful.

Resolved in https://github.com/suse-edge/edge-image-builder/pull/490.


Proposal to Enable Plates Asset Extension

Proposal to refactor PlatesRendererFactory to enable asset extension.
use League\Plates\Extension as PlatesExtension;

// Create the engine instance:
$engine = new PlatesEngine();

// Enable asset extension
$engine->loadExtension(new PlatesExtension\Asset($config['paths']['assets']));

This will allow plates-layout.phtml in zend-expressive-skeleton to reference assets similar to:
<img src="<?=$this->asset('zf-logo.png')?>" alt="Zend Expressive" />

Where the assets path is configured in templates.global as:
    'templates' => [
        'extension' => 'phtml',
        'paths' => [
            'assets' => 'public',
            'app'    => ['templates/app'],
            'layout' => ['templates/layout'],
            'error'  => ['templates/error'],

I'm not certain that this is really the place to put it, it's certainly already possible by using a container and the manual instantiation vs. the factory instantiation.  The problem you will start to run into is where does that stop for hooking everything?
Basically the factories should be mostly interchangeable and adding implementation logic on each one can lead to highly customized factories that ultimately do several things that are just simply proxying methods.
On one hand, it makes configurability via configuration far quicker but on the other hand, it makes for more of a maintainability nightmare - especially for future versions.  I would say customized handling such as this should be done manually.  But feel free to disagree :)

i think the problem is that right now there is no way to configure the PlatesEngine because it's not accessible anywhere, and the renderer factory always instantiate a new one rather than pulling one from the container.
so as it stands, the implementation is quite closed, and to customize the engine one would need to replace the whole renderer factory, which is odd.

I would say customized handling such as this should be done manually.

I understand, I was hoping it would have been good to have it enabled for the skeleton by default.

While I get the objections that @mwillbanks raises, the fact is that
"asset" helpers are already enabled by default in both the twig and
zend-view implementations. As such, we likely should enable them for
plates.
I see two ways to do so:

add functionality to the factory for registering them; we have this in
both the other implementations already (extensions in twig, helpers for
zend-view).
allow pulling the base plates engine instance via a factory (which would
allow configuring it in an application-specific factory)

Anybody want to start a pull request?
On Dec 12, 2015 10:09 PM, "Alexander R Torrijos"<EMAIL_ADDRESS>wrote:

I would say customized handling such as this should be done manually.
I understand, I was hoping it would have been good to have it enabled for
the skeleton by default.
—
Reply to this email directly or view it on GitHub
https://github.com/zendframework/zend-expressive-platesrenderer/issues/3#issuecomment-164220908
.


CXX_STANDARD requires CMake 3.1+

The CXX_STANDARD property is set if C++11 example building is enabled, but that first appeared in CMake 3.1 and this project only require CMake 2.6.

I guess this could be related with issue #19 ...


[3.x] DatePicker stored data not showing in form field

Description
DatePicker stored data not showing in the form field after saving.
It was successfully stored in the database and shown on actual pages.
However, it always shows nothing but placeholder in the form field.

Steps to reproduce

Create DatePicker Field
Update the DatePicker field and saving
Reload the page

Expected result

Saved Date

Actual result

Only Placeholder

Versions
Twill version:  3.0.0-rc1
Laravel version: 9.40.1

hey @KeithPun13 have you added dates casts?

Oh, sorry. Yes, I was missing casts of the fields.
Thank you for your answer and patient.

Hi, may I learn more about a case similar to this?
Is there any way I can cast the data type in block/repeater?

@haringsrob May I ask more about this question?
What if the date_picker fields are a repeater,
Is there any possible way to add casts for a block or repeater?
Or, is there other ways to handle it?

hey @KeithPun13, can you try to do a php artisan twill:build and see if the issue is still there?

@haringsrob Thanks so much! php artisan twill:build does help in this case.

The stranger thing is that it should already be part of the build. Maybe you did not do "php artisan twill:update" after the latest update?

@haringsrob Just having a quick test, I try to :
Downgrade to 3.0-bata2 > run php artisan twill:update

Issue happend, then :
Upgrade to 3.0-cr1 > run php artisan twill:update

Still got this issue, then :
run php artisan twill:build

Issue solved, then I try to run updated again:
run php artisan twill:update

Issue happening again.

Update:
Just remove all vendor files and re-install, then cannot reproduce the issue anymore...
I don't think I have any changes to any of those, so weird...
Anyways, thanks for your time.

hmm.. Not sure. I will pay extra attention to it next release.


Vue 3 upgrade - skill selector will select an item on tab

When using the skill selector component with the keyboard, scrolling through results but then tabbing out of the component will cause the highlighted value to be selected

Closing as this was an intentional decision for the Autocomplete component.


Added Traccar tracker support

Description:
Adds support for a new device tracker based on Traccar GPS Tracking Platform (https://www.traccar.org/).
Traccar supports person presence detection based on GPS device.
This tracker uses the Traccar API to determine the device location.
Example entry for configuration.yaml:
device_tracker:
  - platform: traccar
    url: <http://server:port>
    username: <username>
    password: <password>

Hi @ToRvaLDz,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Added docs-missing, since I cannot find a matching PR on the documentation repo.

Docs PR has been opened, removing the docs-missing label.

@ToRvaLDz You might wanna check the code you've actually committed this PR.
There are all kinds of files in here, that should not have been in this PR.
For example:

https://github.com/home-assistant/home-assistant/pull/15160/files#diff-830968569b50f87c82e22a0042a7f760
https://github.com/home-assistant/home-assistant/pull/15160/files#diff-d9ae695c8119e58c2ec435b6deae2d53

Any updates? Cannot wait anymore 🙈

What's the progress? It's really interesting!


Create garrett.json

I attempted to set up a .json file modeled after the Allegany.json file. Ours is based on our County's "Address Points" point file and the fields are different.

Sorry, the values for district and region have to match the case in the source (COUNTY and STATE).  Otherwise it looks great!

I think I have this done as requested. Let me know if there is anything else that wasn't correct.

Ok I changed the case of COUNTY and STATE. I guess I didn't realize they were pointing to the source.

Oh, I see!  Yeah, the attribute values should be taken directly from the ESRI source verbatim.

Looks great, thanks again for the contribution!
If you're willing to help out on more sources, you can look for holes in the coverage at any level (city, county, state, or country) or check out Lost sources for sources that used to work but don't anymore!


Wont create file

Once the whole process after compile file is done it opens the dist folder and nothing is there

also nothing works with the file i created before this issue
is pysilon down or smth?

same here

it says "TypeError: expected string or bytes-like object, got 'NoneType'"

i have this issue too.

is pysilon down or smth?

LMAO of course a roblox beamer would ask that

bro same fuck, no fix?

Hey, just use the ModdedPysilon version, it covers every bug and it make sure your discord account never get banned.
Leave me a star if you like my project ;)


syntastic enabled for second file in diff mode (vimdiff)

When opening two files in diff mode (vimdiff) syntastic is enabled for the second file though it should be disabled (according to #125):
Example:
$ printf '#!/bin/sh\nexit 0' > /tmp/a.sh
$ printf '#!/bin/sh\nUNUSED=\nexit 0' > /tmp/b.sh
$ vimdiff /tmp/a.sh /tmp/b.sh
$ vimdiff /tmp/b.sh /tmp/a.sh

With shellcheck installed the first call of vimdiff shows the shellcheck warning while the second call is clean.

Yes, syntastic + active mode + check_on_open + opening files in multiple windows = trouble.  To the best of my knowledge this can't be solved without crippling useful functionality (see #1184 and #400 for related fun).  You can avoid the problem by turning off check_on_open, or by making the relevant filetypes passive.  But between the quirks of Vim startup sequence and the limitations of Vim's API, this can't be solved in a robust way.  There are many other corner cases that fail for similar reasons.  Syntastic is just a best effort approach, most of the time it works by accident rather than by design. shrug

Hopefully fixed by f527cb1.

Yes, the issue is fixed. Many thanks.


⚠ Bofrost.fr has degraded performance

In 105ba7b, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1555 ms

Resolved: Bofrost.fr performance has improved in 8987a6e after 13 minutes.


Mass activation: re-check DDIC objs in transport

I am not sure this is correct. I am going to deploy abapGit with this patch applied in our infrastructure and monitor problems for a while.
However, if any skilled SAP user and ABAP developer believes it is OK, feel free to merge the PR.

yeah, lets merge it tomorrow


Deploy npm

Could you publish the last merge in your npm package? https://www.npmjs.com/package/react-countdown-timer

+1 This would be super handy!

Sorry for the delay. Done.


Confusion due to chainguard-images/actions and chainguard-dev/actions

I know it might be hard to move things now they might be used, but I got really confused by chainguard-images AND chainguard-dev both having a actions repository:

https://github.com/chainguard-images/actions
https://github.com/chainguard-dev/actions

Maybe those could be merged? Or is there a specific reason for some of them being in chainguard-images (and others being duplicated, like apko-build)?
Kind Regards,
Johannes

Yes, I felt that I had to update an old issue regarding this.
https://github.com/chainguard-dev/apko/issues/428


README: change semaphore CI status badge

We just reset Semaphore CI, and badge URL is changed.

CI is not happy

@xiang90 Just fixed the dependency script in Semaphore CI. https://semaphoreci.com/coreos/etcd/branches/master/builds/1

Now works. And travis failures are fixed by https://github.com/coreos/etcd/pull/5016. PTAL.


Vi mode (#94)

Still missing:

cursor at end of line for command mode,
move to the first non-blank character of line

Sorry was on holiday, I'm taking a look at this now.

There is one commit that I cannot add to this PR because it needs the unicode feature:
https://doc.rust-lang.org/nightly/std/primitive.str.html#method.is_alphanumeric

sautrating_mul(), even better!