Fails to start under VMWare Fusion

I'd love to start playing with Kubernetes & CoreOS under Vagrant, but I cannot get it to work.
As far as I can see, I've narrowed it down to this:
core@master ~ $ systemctl status -n 100 setup-network-environment
● setup-network-environment.service - Setup Network Environment
   Loaded: loaded (/etc/systemd/system/setup-network-environment.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2015-04-10 06:14:22 UTC; 1min 58s ago
     Docs: https://github.com/kelseyhightower/setup-network-environment
  Process: 1024 ExecStartPre=/usr/bin/wget -N -P /opt/bin https://storage.googleapis.com/k8s/setup-network-environment (code=exited, status=4)
  Process: 1023 ExecStartPre=/usr/bin/mkdir -p /opt/bin (code=exited, status=0/SUCCESS)

Apr 10 06:14:22 master systemd[1]: Starting Setup Network Environment...
Apr 10 06:14:22 master wget[1024]: --2015-04-10 06:14:22--  https://storage.googleapis.com/k8s/setup-network-environment
Apr 10 06:14:22 master wget[1024]: Resolving storage.googleapis.com... failed: Temporary failure in name resolution.
Apr 10 06:14:22 master wget[1024]: wget: unable to resolve host address 'storage.googleapis.com'
Apr 10 06:14:22 master systemd[1]: setup-network-environment.service: control process exited, code=exited status=4
Apr 10 06:14:22 master systemd[1]: Failed to start Setup Network Environment.
Apr 10 06:14:22 master systemd[1]: Unit setup-network-environment.service entered failed state.
Apr 10 06:14:22 master systemd[1]: setup-network-environment.service failed.

Is there something wrong with my network setup?

Apr 10 06:14:22 master wget[1024]: wget: unable to resolve host address 'storage.googleapis.com'

So, no internet access on that VM?

It does have it. If I ssh into it and restart setup-network-environment.service, it runs wget properly.

core@master ~ $ systemctl status network-online.target
● network-online.target - Network is Online
   Loaded: loaded (/usr/lib64/systemd/system/network-online.target; static; vendor preset: disabled)
   Active: active since Fri 2015-04-10 13:21:38 UTC; 14s ago
     Docs: man:systemd.special(7)
           http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget

Apr 10 13:21:38 master systemd[1]: Reached target Network is Online.
Apr 10 13:21:38 master systemd[1]: Starting Network is Online.
core@master ~ $ systemctl status setup-network-environment.service
● setup-network-environment.service - Setup Network Environment
   Loaded: loaded (/etc/systemd/system/setup-network-environment.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2015-04-10 13:21:38 UTC; 24s ago
     Docs: https://github.com/kelseyhightower/setup-network-environment
  Process: 1018 ExecStartPre=/usr/bin/wget -N -P /opt/bin https://storage.googleapis.com/k8s/setup-network-environment (code=exited, status=4)
  Process: 1016 ExecStartPre=/usr/bin/mkdir -p /opt/bin (code=exited, status=0/SUCCESS)

Apr 10 13:21:38 master systemd[1]: Starting Setup Network Environment...
Apr 10 13:21:38 master wget[1018]: --2015-04-10 13:21:38--  https://storage.googleapis.com/k8s/setup-network-environment
Apr 10 13:21:38 master wget[1018]: Resolving storage.googleapis.com... failed: Temporary failure in name resolution.
Apr 10 13:21:38 master wget[1018]: wget: unable to resolve host address 'storage.googleapis.com'
Apr 10 13:21:38 master systemd[1]: setup-network-environment.service: control process exited, code=exited status=4
Apr 10 13:21:38 master systemd[1]: Failed to start Setup Network Environment.
Apr 10 13:21:38 master systemd[1]: Unit setup-network-environment.service entered failed state.
Apr 10 13:21:38 master systemd[1]: setup-network-environment.service failed.
core@master ~ $ ping google.be
PING google.be (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from cache.google.com (<IP_ADDRESS>): icmp_seq=1 ttl=128 time=9.15 ms
64 bytes from cache.google.com (<IP_ADDRESS>): icmp_seq=2 ttl=128 time=11.0 ms
^C
--- google.be ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 9.158/10.099/11.041/0.946 ms

Perhaps network-online.target is not a strong-enough guarantee that the web is reachable?

core@master ~ $ sudo systemctl restart setup-network-environment
core@master ~ $ systemctl status setup-network-environment.service
● setup-network-environment.service - Setup Network Environment
   Loaded: loaded (/etc/systemd/system/setup-network-environment.service; static; vendor preset: disabled)
   Active: active (exited) since Fri 2015-04-10 13:25:12 UTC; 1s ago
     Docs: https://github.com/kelseyhightower/setup-network-environment
  Process: 1325 ExecStart=/opt/bin/setup-network-environment (code=exited, status=0/SUCCESS)
  Process: 1324 ExecStartPre=/usr/bin/chmod +x /opt/bin/setup-network-environment (code=exited, status=0/SUCCESS)
  Process: 1322 ExecStartPre=/usr/bin/wget -N -P /opt/bin https://storage.googleapis.com/k8s/setup-network-environment (code=exited, status=0/SUCCESS)
  Process: 1319 ExecStartPre=/usr/bin/mkdir -p /opt/bin (code=exited, status=0/SUCCESS)
 Main PID: 1325 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/setup-network-environment.service

Apr 10 13:25:12 master wget[1322]: 2200K .......... .......... .......... .......... .......... 87% 14.3M 0s
Apr 10 13:25:12 master wget[1322]: 2250K .......... .......... .......... .......... .......... 89% 5.96M 0s
Apr 10 13:25:12 master wget[1322]: 2300K .......... .......... .......... .......... .......... 91% 4.82M 0s
Apr 10 13:25:12 master wget[1322]: 2350K .......... .......... .......... .......... .......... 93% 6.97M 0s
Apr 10 13:25:12 master wget[1322]: 2400K .......... .......... .......... .......... .......... 95% 3.70M 0s
Apr 10 13:25:12 master wget[1322]: 2450K .......... .......... .......... .......... .......... 97% 5.58M 0s
Apr 10 13:25:12 master wget[1322]: 2500K .......... .......... .......... .......... .......... 99% 7.41M 0s
Apr 10 13:25:12 master wget[1322]: 2550K ........                                              100%  131M=0.6s
Apr 10 13:25:12 master wget[1322]: 2015-04-10 13:25:12 (4.44 MB/s) - '/opt/bin/setup-network-environment' saved [2620224/2620224]
Apr 10 13:25:12 master systemd[1]: Started Setup Network Environment.
core@master ~ $

Sadly, I have no idea how to trigger the remaining bootup after pushing it through manually.

setup-network-environment is not related to VM networkingconfiguration, but rather some CoreOS environment stuff - otherwise, how could you download /opt/bin https://storage.googleapis.com/k8s/setup-network-environment? This must be something with VMware provisioning.

@AntonioMeireles care to join the discussion?

humm... (please do note that i have a way to reproduce this, so bellow just shots in the dark)
at sight it seems that for some reason setup-network-environement.service is just run too soon.
@rubenv can you post please here the contents of /etc/network-environment both when things go wrong and after the manual restart of setup-network-environement.service that induces the expected behaviour ?

Upon initial boot, there is no /etc/network-environment. After restarting the service:
LO_IPV4=<IP_ADDRESS>
ENS33_IPV4=<IP_ADDRESS>
DEFAULT_IPV4=<IP_ADDRESS>
ENS34_IPV4=<IP_ADDRESS>

@rubenv by parts ...
a) destroy existing VMs (vagrant destroy -f)
b) recreate everything
c) vssh master
wait for things to fail.
systemctl status setup-network-environement<< paste results.
journalctl -u setup-network-environement --no-pager --lines=500 << paste results
systemctl list-units << paste ...
cat /etc/network-environment << paste results (may or not be empty depends on above)
d) systemctl restart setup-network-environement
and after all the output again of the command above in c) (by same sequence)

Here you go:
Initially: https://gist.githubusercontent.com/rubenv/caade42ba89e9f64945a/raw/b89844e5f604665530bb13adc91c13b1db05b18e/gistfile1.txt
Boot it: https://gist.githubusercontent.com/rubenv/96759eedca6cfe48f2c1/raw/8bbd664ab8e3c3e786c1b6c37e043cedc4221fe6/gistfile1.txt
Status: https://gist.githubusercontent.com/rubenv/a6e798e5d8ca518439a3/raw/d91609b7c36a721e7177d561bfa44f011c0e48bf/gistfile1.txt
Note the failed unit at login.
For reference, ip a: https://gist.githubusercontent.com/rubenv/335c2ad3cc11a6c185ea/raw/4a35485ed317af5292c98022e3002feeff75a12a/gistfile1.txt
Journal: https://gist.githubusercontent.com/rubenv/ff65f88dc3f650e47461/raw/0edb00a479a91a112e3c16a7661d8d9478dff904/gistfile1.txt
Units: https://gist.githubusercontent.com/rubenv/d7eb37804cd5a70cfc08/raw/5a50cd685a8549d405a5ef1d670fdb4fbe0b9029/gistfile1.txt
At this point:
core@master ~ $ cat /etc/network-environment
cat: /etc/network-environment: No such file or directory

Restarting: sudo systemctl restart setup-network-environment
Status: https://gist.githubusercontent.com/rubenv/0363b84abe66ec782d8e/raw/e8c642468c16fc74203fe168c6efabf23569d44c/gistfile1.txt
Journal: https://gist.githubusercontent.com/rubenv/5ab29049b99729b8acbf/raw/170755f6608b9c21436f2c681c453a0e10162d15/gistfile1.txt
Units: https://gist.githubusercontent.com/rubenv/d26acb1d83fd0b284d5e/raw/b2450d9f5f3475b3812f5b089f2640d11af9d1af/gistfile1.txt
At this point we get:
core@master ~ $ cat /etc/network-environment
LO_IPV4=<IP_ADDRESS>
ENS33_IPV4=<IP_ADDRESS>
DEFAULT_IPV4=<IP_ADDRESS>
ENS34_IPV4=<IP_ADDRESS>

And for completeness, the full Journal: https://gist.githubusercontent.com/rubenv/ddde2f962556b0868243/raw/5a9c5793c877d700968ab3035341f62d539d30f0/gistfile1.txt
And the output of dmesg: https://gist.githubusercontent.com/rubenv/ced75057ae46fc61d358/raw/e316baeb67d90a75abd2e59ea1158932c291e8eb/gistfile1.txt
Phew :-). Hope this is of any help!

ah, for some reason the system is taking too long to get dns setup. dunno yet why.

Can we just force DNS set-up? Something like echo <IP_ADDRESS> > /etc/resolv.conf?

@rubenv care to try latest master? I think #80 may have fixed this.

I'm sorry, I haven't had the time yet to test this. Sadly my VMWare Fusion + Vagrant is also acting up (Hashicorp is looking into it). Will have a look at it, at some point.


5695 add keycloak authentication

This change includes Dave's initial commit.
To just view my changes you can view the individual commit:
https://github.com/bcgov/moh-ldap-account-transfer/pull/6/commits/9d863381487f02a9253d792c0c17740bc67b9cbe


Move away from specific FQDN TLS cert-generation

I'm getting rate-limited by Lets Encrypt due to the amount of ingress resources that need certs (or more likely i'm doing something else behaviorally incorrect). In order to circumvent this I should move to creating a default wildcard cert for my cluster that all of my ingress resources can use.
Ref:

https://github.com/zacheryph/k8s-gitops/blob/main/cluster/system/ingress/wildcard-certificate.yaml
https://github.com/zacheryph/k8s-gitops/blob/main/cluster/system/ingress/ingress-nginx.yaml#L19

thanks to @zacheryph for the help!

fixed in https://github.com/crutonjohn/gitops/commit/4d1179563275f640dda6f0bc74ab18e92f1ca277


Update to Scala.js 0.6.6 and undo workaround for 0.6.5 bug

Fixes #113 now that Scala.js 0.6.6 is out. Verified locally with validateJS.

Current coverage is 77.48%

Merging #174 into master will decrease coverage by -0.02% as of 43374fb

Powered by Codecov. Updated on successful CI builds.


downgrade @nuxt/content from version 2 to 1.15

name: Pull request
about: Contribute your changes to the project
title: '[pull-request]'
labels: ''
assignees: ''
Description
Downgrade @nuxt/contents version back to 1.15. Version 2 did break our webpage.
Reference
Issues #234
Checklist

[ ] Acceptance criteria are met
[ ] Pipeline has been run successfully
[ ] JUnit tests have been run successfully
[ ] Changelog is adjusted
[ ] Documentations are completed
[ ] Frontend is tested
[ ] Created sub-branches are deleted
[ ] Boards are updated ( Digitalisierung , Support , Zenhub )
[ ] feature process is created or extended
[ ] git-ops is customized
[ ] Openshift environments are prepared (Secrets, etc.)

Sorry @lmoesle I pressed merge - the power of the usual ;)


feature not documented

just donated 5$ I was looking for something like this for YEARS!
The documentation on the website https://www.mowglii.com/itsycal/datetime.html is not covering a feature in the time for the seconds, however it's possible to display seconds.
I'm successfully using this time format:
E d MMM - H:mm:ss
Will be great to update the documentation accordingly.

@exenza I'm glad you got seconds to work. The table on that page is just for the most common format specifiers. There is a link at the bottom of that page to the full spec which does include seconds.
I left seconds out on purpose because if I had included it, people would use it and then complain to me that Itsycal was using more CPU than they liked. Well, that's because it is updating the UI every second. It's not a problem on computers today, but people will complain to me anyway.
I'm going to to leave the page as it is and enterprising people who read to the bottom and find the link to the full spec can figure out how to use seconds and all the other format specifiers.


Include in documentation how to achieve same results with functionality that doesn't exist any longer in Microsoft.Azure.NotificationHubs versions to 3.0.0+

Several developers when migrating from old Microsoft.Azure.NotificationHubs versions to 3.0.0+ have issues when trying to migrate code and understanding that Hub management functionality has been removed from the data plane SDK (Microsoft.Azure.NotificationHubs) and is now available via ARM SDK (Microsoft.Azure.Management.NotificationHubs or Microsoft.Azure.Management.NotificationHubs.Fluent).
Please include samples in public documentation of how to use the management SDKs when migrating from old SDK versions to 3.0.0+ to perform the same operations as of the functionality stated here: https://azure.microsoft.com/en-us/blog/push-notification-hub-telemetry-expiry-update/
Thank you!

Management functionality was ported back into this SDK and is currently available in 4.0.0-preview version - https://www.nuget.org/packages/Microsoft.Azure.NotificationHubs/4.0.0-preview2

Closing as per releasing of the 4.0 SDK


WhatSie chrashes repeatedly after Fedora KDE upgrade from 40 to 41

Repeated crashes, mainly after restarting the OS or when WhatSie is running in the background.

This also sounds like a duplicate of #207, which has potentially a temporary solution

The issue was caused due to Custom notification popup widget life-cycle. It is fixed in dde6e02


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
14 seconds
deprecated-base-image-check

✅ Succeeded
17 seconds
sanity-inspect-image

✅ Succeeded
18 seconds
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
15 seconds
sbom-json-check

✅ Succeeded
12 seconds
sanity-optional-label-check

✅ Succeeded
12 seconds
sanity-label-check

✅ Succeeded
4 seconds
show-summary


Problem on getting auth token

Problem:
Facebook have added cookie window which have to be accepted which results to the following error
400 Bad Request: The browser (or proxy) sent a request that this server could not understand.
Solution:
Add this code on line 16 here https://github.com/fbessez/Tinder/blob/master/fb_auth_token.py
f = s.get_form()
s.submit_form(f)
Or the whole function looks like this
def get_fb_access_token(email, password):
    s = robobrowser.RoboBrowser(user_agent=MOBILE_USER_AGENT, parser="lxml")
    s.open(FB_AUTH)
    f = s.get_form()
    s.submit_form(f)
    f = s.get_form()
    f["pass"] = password
    f["email"] = email
    s.submit_form(f)
    f = s.get_form()
    try:
        s.submit_form(f, submit=f.submit_fields['__CONFIRM__'])
        access_token = re.search(
            r"access_token=([\w\d]+)", s.response.content.decode()).groups()[0]
        return access_token
    except requests.exceptions.InvalidSchema as browserAddress:
        access_token = re.search(
            r"access_token=([\w\d]+)",str(browserAddress)).groups()[0]
        return access_token
    except Exception as ex:
        print("access token could not be retrieved. Check your username and password.")
        print("Official error: %s" % ex)
        return {"error": "access token could not be retrieved. Check your username and password."}

Change MOBILE_USER_AGENT variable to Mozilla/5.0 (Linux; U; Android 4.4.2; en-us; SCH-I535 Build/KOT49H) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30. The old one seems to be outdated for facebook and it shows error message instead of the login form.

Is there anything I can try?


fix(remix-dev/vite): instantiate plugins independently for child vite compiler

Closes: https://github.com/remix-run/remix/issues/7989
The same issue is already indicated in https://github.com/remix-run/remix/pull/7911#issue-1977584283 but this time, @vanilla-extract/vite-plugin is affected by the issue since it makes use of config.command = "server" or "build" to switch plugin behavior.
Specifically, the plugin uses this pattern:
export function vanillaExtractPlugin({
  ...
}: Options = {}): Plugin {
  let config: ResolvedConfig;
  ...

  return {
    name: 'vanilla-extract',
    ...
    async configResolved(resolvedConfig) {
      config = resolvedConfig;
      ...
    }

   // ... in later hooks (e.g. transform), it uses `config.command === 'build'` check to switch behavior ...

During vite build, child compiler calls configResolved 2nd time with config.command: "serve", so it forces parent compiler to also behave in the same way.
This PR fixes this issue by loading user vite config file independently for child compiler (via loadConfigFromFile), which will ensure that plugin states won't be mixed between parent and child even though they still have different confg.command.
One issue with this approach is that it also "doubles" remix's own plugin as well, which might cause some issues (or at least negative perf impact). For example, the child compiler is going to have independent resolvePluginConfig cache etc... since it's used for "remix-remove-server-exports" plugin.
Testing Strategy
This PR is tested on reproduction repository https://github.com/mrm007/remix-vite-vanilla-repro/pull/1.
I'll also add a playwright test here.

Thanks for the PR! Just a heads up that I've updated your PR since I've migrated to the Vite 5 beta, along with a couple of small tweaks.

This change makes a lot of sense to me. I can see that our approach to passing plugins to the child compiler is likely to cause issues with random plugins, and those issues will surface in different ways that make it hard to diagnose or even fix.
The tradeoff here is that the Remix plugin won't be usable if it's passed via inline config to the Vite JS API, but I think that's okay for now. I've added an explicit error message to communicate this limitation. Even if there's a way around this limitation, I'd rather ship your PR now as it leaves us in a better state overall.
I'm happy to merge this PR as-is as long as the current test suite is passing, but feel free to add a Playwright test as a follow-up PR.

Thanks for the review!

The tradeoff here is that the Remix plugin won't be usable if it's passed via inline config to the Vite JS API

Good point, I haven't thought about that. It might be cool if that works, but as you say, I assume making that work is not an immediate concern. I'll think about if this can be also mitigated later.

feel free to add a Playwright test as a follow-up PR.

Sounds good. I'll put this PR ready for review and will create a separate PR to add test cases with vanilla extract plugin.


Add service annotations for prometheus-consul-exporter

What this PR does / why we need it:
These were defined in values overrides but not applied to the service.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped

/assign @davidkarlsen

/ok-to-test
/lgtm


feat: include tooltip

Closes https://github.com/scylladb/sphinx-scylladb-theme/issues/873
How to test

Build the docs.
Access http://<IP_ADDRESS>:5500/examples/tooltips/

Ready for review cc/ @annastuchlik


A problem about openblas threads?

I use openblas and in the demo, the code that:
caffeMobile.setNumThreads(4);
and in the jni:
openblas_set_num_threads(num_threads);
I seems that this change the number of cores that we use. However, when I change the number in setNumThreads(), from 1-6. It changes nothing. For example, it cost me 5s to run a image when the number is 1, and 5s as the number is 4(or others).
My arm has 6 cores.
So, would you tell me something about the function setNumThreads()?
Thank you!

For OpenBLAS with libs on armeabi-v7a, I had tested that the number of threads do effect the performance.

I try it again just a moment ago. But it still seems nothing changed.
what I do:
export USE_OPENBLAS=1
export ANDROID_ABI="armeabi-v7a-hard-softfp with NEON"
./build.sh <path/to/ndk>

Did you try the prebuilt libs in this repo before? I'm pretty sure that it works with openmp support.

what is "the prebuilt libs "? and where can I find it?

https://github.com/sh1r0/caffe-android-demo/tree/master/app/src/main/jniLibs

Yes, I always do it, but find ineffective.
I run this demo in TK1, but find that it always run the program in one cpu core(and in other devices like rk3288 or xiaomi box3, it is ineffective when changed the number of openblas threads, too). I make a test in TK1 of Matrix multiplication. I find that even I make sure that I have 4 threads, the time it cost is the same as 1 thread. It seems that TK1 has only a core to calculate the floating point(I guess).
So, would you tell me, what device you use when it do effect the performance ?

Sorry, I found that I made a mistake and thus caffe libs would be built with eigen by build.sh even USE_OPENBLAS=1 is set. Therefore, the prebuilt libs were all built with eigen instead of openblas. I fixed the bug in the dev branch of caffe-android-lib. As it is time-consuming to rebuild the libs for all abi, please build caffe-android-lib on your own. Sorry again for the inconvenience.

Could tell me the mistake so I can build the lib by myself? I am not familiar with shell so I cannot find it.
Thank you!

I find it. I delete build_eigen.sh in build.sh. And just use build_Openblas.sh. It works.
Thank you!


Add "Duplicate file" command in file explorer right click menu

VSCode Version: 1.2.1
OS Version: MacOS

A native "duplicate file" command next to "copy", "rename" and "delete" is much needed.

For now you can Copy & Paste to get the same behavious.

Hey, can I try to add this feature

Should be done as extension (using new menu API).


CBAPI-4622: Add data collection to the CBC SDK

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Tests have been added that prove the fix is effective or that the feature works.
[x] New and existing tests pass locally with the changes.
[x] Code follows the style guidelines of this project (PEP8, clean code, linter).
[x] A self-review of the code has been done.

What is the ticket or issue number?

https://jira.carbonblack.local/browse/CBAPI-4622
Pull Request Description

Add the DataCollectionRuleConfig object and associated extensions to the SDK, handling data collection rule configurations on policies.
Does this introduce a breaking change?

[ ] Yes
[x] No

How Has This Been Tested?

Unit tests have been added to cover new functionality; coverage stands at 96%. Manual test against Prod02 run, logfile for the test is here: data_collection_log.txt

And I provided that log file attached to the PR just for you. :)


cleanup: handle Python site-packages directories

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Inside a given site-packages directory, *.pyc files live in
__pycache__ directories. These are created by the Python interpreter
when a module is imported in order to speed up future access to the
imported module.
These can be left behind when formulae are uninstalled, which results in
erroneous success in importing the modules they were originally compiled
for.
Let's fix that by cleaning these up. In the top-level __pycache__
directory, we use the Pathname#prune? extension in order to determine
whether a *.pyc file is old enough to clean up. In other directories,
we clean them up when they are all that remains in a given module's
tree.
Removing these *.pyc files will make python3 regenerate them when
required, so deleting them is relatively safe. The worst consequence is
slightly slower module import times.
Closes #13701.

Review period will end on 2022-08-19 at 13:18:18 UTC.

Review period ended.

I was thinking about why we need something like this now and not previously. I suspect it might be related to changes in Python that result in packages writing directly to the site-packages directory in HOMEBREW_PREFIX unless configured otherwise.
Is there a way to get formulae to write their *.pyc files into the relevant formula prefix, instead of the site-packages directory in HOMEBREW_PREFIX?
CC @Bo98 @cho-m for thoughts here.


Lots of ios-*-outline icons are removed on newest React Native Vector Icons

I have gone through these following points

[x]   Check latest documentation: https://docs.nativebase.io/
[x]   Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[x]   Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[x]   Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
[x]   For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
[x]   For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description

node, npm, react-native, react and native-base version, expo version if used
  React Native Environment Info:
    System:
      OS: macOS 10.14
      CPU: x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
      Memory: 296.78 MB / 16.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 10.11.0 - /usr/local/bin/node
      npm: 6.4.1 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
    IDEs:
      Android Studio: 3.2 AI-181.55<IP_ADDRESS>14246
      Xcode: 10.0/10A255 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.5.0 => 16.5.0
      react-native: 0.57.1 => 0.57.1
    npmGlobalPackages:
      create-react-native-app: 1.0.0
      react-native-cli: 2.0.1

Expected behaviour
Showing correct icons.
Actual behaviour
Because lots of ios-*-outline icons are removed, it shows question mark now.
Steps to reproduce

npm install native-base
npm install react-native-vector-icons
use home or calendar icon

Is the bug present in both iOS and Android or in any one of them?
Only iOS
Any other additional info which would help us debug the issue quicker.
When I was checking the latest doc of RN vector icons, it only contains these ios-*-outline icons:

Lots of icons here were removed.
So it's better to update the json file and update RN vector icons to the latest version

Fixed with commit https://github.com/GeekyAnts/NativeBase/commit/f841390a7b4c9c88f9c8000689599783d5cfcf09 and https://github.com/GeekyAnts/NativeBase/commit/e678edbf19765421af50a1cdfc8ecd923976656b
Also available on master

@SupriyaKalghatgi
It seems that this file was not updated. The ios-*-outline icons should be reviewed, I think.

I agree with  @kigawas , there is some work left on this issue...

Hey folks,
You are right @kigawas I got this bug reported on #2461 and fixed on #2462 by reviewing this file that @alexkyse1 suggested!
Can you take a look  👀 in this PR @SupriyaKalghatgi ?
Thank you all Folks ❤

Hey @jonathangreco I would love to see #2462 merged too, but unfortunately, I have not write access, so we need to wait until they merge it, while we don't get this release, we are maintaining a fork with this fix and you can temporally point to this fork while they don't release a new patch.
You can do this by changing your package.json import to     "native-base": "git+https://github.com/CESARBR/NativeBase.git#b81cc6d43d88388e112600153b4ad0b39e9beba2",

You can contribute with a thumbs up in this pr #2462

ios-funnel-outline is not available on "react-native-elements 1.1.0"

@alainib This is not the appropriate place to point out about react native elements


Miscellaneous cross compilation fixes

This is a collection of fixes to the cross compilation infrastructures that I have collected. Mostly just stuff that I don't want to forget to merge. Summary:

fix isCompatible identity
add handling for musl when building aws-sdk-cpp
fix the ARM isCompatible definitions
use isCompatible as a backup for finding bootstrap tools
fix spidermonkey compilation
expose crossOverlays to Nix command line args

I can split these up into separate PRs if requested.
/cc @illegalprime

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

@grahamcofborg eval

@matthewbauer thanks for the spidermonkey fix!


Creating a PR (no merge) cause the application to be re-deployed

@gecock commented on Wed Oct 16 2019
@mtamboli found the following issue:
The problem is that when a PR is created for an application update in Git repository, it just starts the pipeline run and redeploys on top of the the working application. So basically, this PR was not even reviewed and merged by anyone but it still replaces the existing running application which may cause unwanted changed to be redeployed. It there was a separate deployment for testing this PR, this was fine.
With lack of eventing, there is not much control. But this behavior should be changed to only redeploy when the PR is merged. No action when PR is created.
There is a pull request to fix this here -- https://github.com/kabanero-io/kabanero-pipelines/pull/73, but it is blocked on this -- https://github.com/kabanero-io/kabanero-foundation/issues/93 and this https://github.com/kabanero-io/kabanero-foundation/issues/94

@gecock commented on Wed Oct 16 2019
@vtereso can you confirm for us that your PR (https://github.com/kabanero-io/kabanero-pipelines/pull/73) will address this situation? If so can you also confirm we cannot merge it until https://github.com/kabanero-io/kabanero-foundation/issues/93 is completed?

@anneqm commented on Wed Oct 16 2019
@gecock I believe PR#73 is is also dependent on #94

@vtereso commented on Wed Oct 16 2019
As per the release page, conditions have been available since 0.6, which was the same release the $() interpolation syntax was introduced. Within the next release, the ${} release was deprecated. There were changes to the experimental code to pass new parameters into the pipeline, which are used by the conditional within my PR. So, Tekton 0.6 and 0.7 are both satisfactory, but ultimately the updated experimental code is necessary to pass in the event type. In Tekton 0.5, we would conditionally return before deployment within this task.

@marikaj123 commented on Wed Oct 16 2019
Tekton 0.7 is not for the 0.2 release.

@kvijai82 commented on Wed Oct 16 2019
I am planning to experiment with tekton 0.7 next week and can try to see if we can address this issue then but can't get this into 0.2 kab release.  Too many dependency issues to sort out.

@gecock commented on Wed Oct 16 2019
Thanks all. Appreciate the info. We will revisit this to verify once all these other issues are resolved.

@marikaj123 commented on Wed Oct 16 2019
@gecock - I am removing the label release-0.2 as you seem to be in agreement with Vijai's comment.

@kvijai82 commented on Fri Nov 01 2019
The long term fix is in the new set of pipelines we are delivering in this release to work with the eventing framework.  We have a pipeline that will only do a build based on PRs and another that will build & push once a PR is merged.  Both of these will not deploy.  Idea here is there will be very specific pipelines for specific triggers.
Having said that, will see what we can do to fix the issue in the existing build-deploy pipeline.  As of now don't have the conditional path working.

Actions:

Experimental pipelines are provided as a temp solution until the eventing will complete.
For release 0.3.0 can use the temp solution.

@kvijai82 - Please let us know when the tem solution is provided.  Thank you.

@marikaj123 We have the solution working in our test env.  @aadeshpa is doing final tests and should have a PR ready by tomorrow.

@marikaj123 Experimental pipelines are in the 0.3.0 collections.  Don't have the bandwidth to implement the short term conditional logic in the pipeline.  Going to close this out.


How to use startActivityForResult with OnNeverAskAgain

Overview
This is what I need to do:
If the user marks the NEVER ASK AGAIN, I'd like to open the App settings to let the user activate it from there, and then catch result of the settings permissions activity. See the bellow details and say if I'm missing something, please.
How I'm trying to do:
    @OnNeverAskAgain(Manifest.permission.ACCESS_FINE_LOCATION, Manifest.permission.ACCESS_COARSE_LOCATION)
    fun openSettings(){
        val myAppSettings = Intent(Settings.ACTION_APPLICATION_DETAILS_SETTINGS, Uri.parse("package:" + packageName))
        myAppSettings.addCategory(Intent.CATEGORY_DEFAULT)
        myAppSettings.flags = Intent.FLAG_ACTIVITY_NEW_TASK
        startActivityForResult(myAppSettings, REQUEST_APP_SETTINGS)
    }

    override fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent?) {
        onActivityResult(requestCode, resultCode, data)
        if(requestCode == REQUEST_APP_SETTINGS && resultCode == Activity.RESULT_OK){
            if(hasPermissions(Manifest.permission.ACCESS_FINE_LOCATION, Manifest.permission.ACCESS_COARSE_LOCATION)){
                toast("permissions granted!")
            } else {
                toast("permissions not granted!")
            }
        }
    }

Expected
The onActivityResult method to be called.
Actual
Method onActivityResult not being called.
Environment

Which library version are you using?
3.0.1
On which devices do you observe the issue?
Nexus 5x - Android 8.0 (AVD)

You probably want to avoid the infinite loop in onActivityResult by changing its first line to call super.onActivityResult instead. Other than that, based from the code you've shared, this looks OK.
Two follow-ups: Do you delegate the handling of onRequestPermissionsResult to the method generated by the library as well? Do you use withPermissionCheck to call the permission-protected resource in the first place?

@mannodermaus thanks for the advice. But even removing the onActivityResult call and including the super call, didn't work.
About your second question, yes:
    @SuppressLint("NeedOnRequestPermissionsResult")
    override fun onRequestPermissionsResult(requestCode: Int, permissions: Array<out String>, grantResults: IntArray) {
        super.onRequestPermissionsResult(requestCode, permissions, grantResults)
        onRequestPermissionsResult(requestCode, grantResults)
    }

        findMeButton.setOnClickListener {
            closeActivityWithPermissionCheck()
        }

It's weird, because I can debug the method NeedsPermission but not the one with OnNeverAskAgain the execution doesn't stop on breakpoint.

I made a few tests here and looks like an activity issue. This code doens't call the activityResult:
val myAppSettings = Intent(Settings.ACTION_APPLICATION_DETAILS_SETTINGS, Uri.parse("package:" + packageName))
        myAppSettings.addCategory(Intent.CATEGORY_DEFAULT)
        myAppSettings.flags = Intent.FLAG_ACTIVITY_NEW_TASK
        startActivityForResult(myAppSettings, REQUEST_APP_SETTINGS)


Dashboard does not work with latest flask (3.0.0)

----> 1 from mpire.dashboard.dashboard import connect_to_dashboard, start_dashboard

~/Projects/mpire/mpire/dashboard/dashboard.py in <module>
      9 from typing import Dict, Optional, Sequence, Union
     10
---> 11 from flask import escape, Flask, jsonify, render_template, request
     12 from werkzeug.serving import make_server
     13

ImportError: cannot import name 'escape' from 'flask' (~/Projects/mpire/venv/lib64/python3.11/site-packages/flask/__init__.py)

Apparently importing escape from flask was deprecated, and has now been removed. Importing it from markupsafe fixes it, and should be compatible with earlier versions as well.

i have solved this problem by importing if from markupsafe , really thank you


Add Bech32 addresses support

In case Segwit gets activated (or even if not, may be useful if someone wants to fork rieMiner for another coin).

Commit c1885467cdc56f605f3094dd1db9258e150e414b brings a first implementation to support Bech32 P2PWKH addresses. Better implementation and support of P2WSH may be done later for 0.92 or even 0.99, but for now it is enough to close this issue.


Adding Laravel 5.6 support

What the title says.
If I missed anything please let me know!

In 2 weeks, I am upgrading all of my packages to only support 5.5 and 5.6 and PHP 7.1.3+. In the meanwhile I will not be accepting any PRs.

@GrahamCampbell Im upgrading to laravel 5.6 can u plz upgrade this package

V5.0 has now been released.


Hides stdin input on Linux

When running with multiprocessing on Linux, stdin won't show. Stdout and stderr still show up, but anything typed in the command line (in urxvt) doesn't show up.

Seems to be related to the multi-processing aspect of it


fix: some incorrect usage of await, added a few explicit hideDialogs

Description
Report from user on stuck payment link modal.
Reproducible on dev while trying to accept a payment link transfer.
Caused by the update of async modals, and some awaits were not applied correctly / maybe some explicit hideDialogs were needed as well
About # (link your issue here)
#4115
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist:

[ ] PR title matches follow: (Feature|Bug|Chore) Task Name
[ ] My code follows the style guidelines of this project
[ ] I have followed all the instructions described in the initial task (check Definitions of Done)
[ ] I have performed a self-review of my own code
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have added reference to a related issue in the repository
[ ] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
[ ] I have added screenshots related to my pull request (for frontend tasks)
[ ] I have pasted a gif showing the feature.
[ ] @mentions of the person or team responsible for reviewing proposed changes

@L03TJ3 ALL added await should be reverted except for where it was needed


1.3.8 error unhashable type 'dict' error on configuration that works in 1.3.7

Description :
In version 1.3.8 I get an error with the same config that works in 1.3.7
❗ ERROR: Hook 'load_terraform_data' from /usr/local/lib/python3.7/site-packages/terraform_compliance/steps/terrain.py:8 raised: 'TypeError: unhashable type: 'dict''

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/radish/hookregistry.py", line 132, in call
    func(model, *args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/terraform_compliance/steps/terrain.py", line 10, in load_terraform_data
    world.config.terraform = TerraformParser(world.config.user_data['plan_file'])
  File "/usr/local/lib/python3.7/site-packages/terraform_compliance/extensions/terraform.py", line 44, in __init__
    self.parse()
  File "/usr/local/lib/python3.7/site-packages/terraform_compliance/extensions/terraform.py", line 403, in parse
    self._mount_references()
  File "/usr/local/lib/python3.7/site-packages/terraform_compliance/extensions/terraform.py", line 359, in _mount_references
    ref_type=ref_type)
  File "/usr/local/lib/python3.7/site-packages/terraform_compliance/extensions/terraform.py", line 257, in _mount_resources
    if ref_type not in self.resources[target_resource]['values']:
TypeError: unhashable type: 'dict'

To Reproduce
Plan/Code cannot be shared, but is a valid plan and can be terraform applied fine
Running as python package
Feature: EC2 instances configuration
    As an engineer
    I want to have a consistent configuration for EC2 instances

    Scenario: Ensure instances don't have public IPs
        Given I have aws_launch_template defined
        When it has network_interfaces
        Then it must contain associate_public_ip_address
        And its value must be false

Tested versions :

terraform-compliance 1.3.7 works, 1.3.8 shows error above
terraform 0.12.29
python 3.7

trying to reproduce this problem.

I wasn't able to reproduce this problem. Could you share an anonymized version of the plan or terraform code?
(This is a parsing bug and is independent from features.)

Thanks for looking, I will try to get an anonymized version of the plan after the holidays.

Happened to me too, we were usign terraform compliance 1.3.8, worked when downgrading to 1.3.7.

Happened to me too, we were usign terraform compliance 1.3.8, worked when downgrading to 1.3.7.

If is useful to you, my repo is open to public and you can get it here and the issue was on this module: https://github.com/luis-calvo-mackenna/lcm-sayu-infra/blob/master/modules/vpc/main.tf

Happened to me too, we were usign terraform compliance 1.3.8, worked when downgrading to 1.3.7.

If is useful to you, my repo is open to public and you can get it here and the issue was on this module: https://github.com/luis-calvo-mackenna/lcm-sayu-infra/blob/master/modules/vpc/main.tf

Perfect! Thanks @luis-calvo-mackenna !

Perfect! Thanks @luis-calvo-mackenna !

Just released 1.3.9 having this fix. Could you please have a try ?
Thanks 🎉

Just released 1.3.9 having this fix. Could you please have a try ?
Thanks 🎉


Get back to specific alert with updated info about seen/unseen

I am here, let's say:

I want to return to my alert 7, https://alert.riparias.be/alert/7. How to do it?
The only option we have up to now is to use the back arrow of my browser, but in this way the information about seen/unseen is not updated as it is cached.
I see two solutions:

do not allow caching so that each time the user wants to go back updated info about See/Unseen is loaded, but I wonder if this is really possible
a button, "Back to Alert" so that uesr knows how to return to the specific alert page with updated info without using the browser back arrow.

I discussed it with @niconoe last week, I think. @niconoe: I couldn't find an open issue related to this, sorry. If you can, just delete this or point to the open one.

Indeed. I plan to implement your suggestion number 2, and I think it's pretty urgent because the current situation is quite impractical for users.
On the longer term, I'm thinking more and more to replace the "occurrence details" page by an occurrence details popup or panel that would open without leaving the alert page (or the main dashboard page). That would solve a lot of similar issues and make the interface better, I think. It's a larger change, so it's not for now. A simple button as you suggest in 2) would already help a lot, I think.

It's probably a bad UX, but how would the application react if the occurrence details were opened in a new tab? Would the application be aware of the change in seen/unseen on the originating page?

@peterdesmet: no.
There are two interleaved issues, I think:

The user cannot easily come back to the previous page (especially if you avoid using the back button in modern web apps like I do - but maybe it's just me) => opening in a new tab would help
The data (read/unread status) is not updated between pages: no easy solution for that

The more I think of it, the more I think we'll really need a single page application for a given data view (either a specific alert or the dashboard at large) if we want a great UI. (all the rest: static pages, alert creation form, login forms, ... can continue as a standard, server-generated HTML pages)

"Go back button" (either to the alert or tot he website root, according to what lead the user there) is now implemented.
We also need that the "mark the observation as unseen" works the same way.

@damianooldoni / @peterdesmet : back button implemented and visible on the dev website.
Will now work to make the "mark observation as unseen" follows the same logic.

Back button tested. Nice.

Also updated the "mark observation as unseen" redirect logic.
Will deploy everything into prod very soon (before my long weekend), if no objections!


Creating Lecture Post Type - Error  Invalid Twig syntax found or missing value

When trying to create another content type such as the example used with lectures I am receiving an error during compiling.
/statie.yaml

parameters:
    google_analytics_tracking_id: 'ABC123'

    generators:
        posts:
            layout: '_layouts/post.twig'
        lectures:
            variable: 'lecture'
            variable_global: 'lectures'
            path: '_lectures'
            layout: '_layouts/lecture.twig'
            route_prefix: 'learn'

/_layouts/lectures.twig

{{ lecture.title }}

                {{ lecture.perex }}

{{ lecture.content | raw }}

            Read more posts

Here is the error message I am receiving.
In TwigRenderer.php line 54:

  Invalid Twig syntax found or missing value in "statie/source/_lectures/my-new-lecture.md" file: Neither the property "title
  " nor one of the methods "title()", "gettitle()"/"istitle()"/"hastitle()" o
  r "__call()" exist and have public access in class "Symplify\Statie\Generat
  or\Renderable\File\GeneratorFile" in "_layouts/lecture.twig" at line 9.

In CoreExtension.php line 1683:

  Neither the property "title" nor one of the methods "title()", "gettitle()"
  /"istitle()"/"hastitle()" or "__call()" exist and have public access in cla
  ss "Symplify\Statie\Generator\Renderable\File\GeneratorFile" in "_layouts/l
  ecture.twig" at line 9.

Do you have title there?  Here is why!"
---

## Why Do We Fail?

We don't fail, we learn.

Enjoy your fails in 2019!

Symplify\Statie\Generator\Renderable\File\GeneratorFile" in "_layouts/l
ecture.twig" at line 9.

How does code look there?

@TomasLudvik the second file is exactly what the code is.
Do I have to create a custom object in order for it to work?
If you have it working any chance of recording a quick screencast of what you did to create a new content type?

I see. You're trying to get "title" on generic object, that has no getTitle() method. There is no magic array acccess (very troublesome) as in Sculpin.
This is the docs:
How to fix that?
Your have to add your own object with getTitle() method:
# statie.yml
parameters:
    generators:
        lectures:
            ...
            object: 'MyWebsite\Statie\LectureFile'

final class LectureFile extends AbstractFile
{
    public function getTitle(): ?string
    {
        return $this->configuration['title'] ?? null;
    }
}

More here: https://www.statie.org/ in the Custom Object - object headline

@TomasVotruba okay. The way the documentation read was it was optional. So if you are creating a new content type then its required.
As a non-php developer it would be extremely helpful if you provided an example of the full object file for the lecture that has multiple fields and where it should be saved.

As a non-php developer it would be extremely helpful if you provided an example of the full object file for the lecture that has multiple fields, on that same page.

Agreed!

I can help write some documentation if need be, once I get it working.

:+1: That would be the best. I don't use Statie much lately, apart adding new markdown files to my blog, so I have no idea how to write it for new users. So your fresh approach would be the best for the rest IMO.
There is the repo (on Statie ;)): https://github.com/crazko/statie-web

Btw, do you have online open-source repository where you use Statie this way? I could help you there, if you add Travis so I can see the fails.
Also check my website, that uses Statie fully: https://github.com/tomasVotruba/tomasvotruba.cz/


Package GeoidHeightsDotNet 1.0.1 is not compatible with monoandroid10.0

I'm trying to use GeoidHeightsDotNet in a Xamarin cross-platform project. When building the Android app, I get the following error:
Package GeoidHeightsDotNet 1.0.1 is not compatible with monoandroid10.0 (MonoAndroid,Version=v10.0).
Package GeoidHeightsDotNet 1.0.1 supports: net (.NETFramework,Version=v0.0)

When using GeoidHeightsDotNet in a portable class library (PCL) based on .NET Standard 2.1, I get this warning:
Warning NU1701: Package 'GeoidHeightsDotNet 1.0.1' was restored using
'.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8'
instead of the project target framework '.NETStandard,Version=v2.1'.
This package may not be fully compatible with your project. (NU1701)

From what I found on the web, this might possibly be due to a bug in older nuget versions. Maybe one could try to re-generate the nuget package with current tools?
Alternatively, converting the project to .NET standard or .NET core might help or improve cross-platform compatibility?

Alternatively, converting the project to .NET standard or .NET core might help to improve cross-platform compatibility?

I tried this approach. Luckily it was not very hard:
https://github.com/janusw/GeoidHeightsDotNet/commits/net_core_port
The best part is that indeed it fixes my compatibility problems.
@MatejFranceskin Would you be interested in integrating these changes in your repository? (If yes, I'll open a pull request.) Apart from improving compatibility and portability, this also simplifies nuget package generation.

Yes, please create a PR. Thank you very much!

This is fixed by PR #2.


I think the set function of the use_state object affects the other mutex usage.

Problem
In certain logic "main loop" and "event action" access shared data via mutex.
Originally there was no problem, but as soon as I used the set of use_state the problem started. What is done writing in "main loop" is not visible in "event action".
If I removed use_statue.set, it worked as expected again.
The link below is my code where the problem occurred.
If you run it, it should be reproducible.
https://github.com/myyrakle/rustetris/blob/8e7e5389a5cfaa3113ee7606fc79090ad5822f5c/src/components/gamebox.rs#L24
Steps To Reproduce
Steps to reproduce the behavior:

Execute the above code as it is.
Press the start button and the tetris game will start.
Press the left and right arrow keys to move.
Uncomment the set function and run it again.
It will not move even if you press the left and right arrow keys. (The error is due to the mutex sync failure issue mentioned above.)

Expected behavior
Screenshots

Environment:

Yew version: 0.19
Rust version: 1.64 stable
Target, if relevant: wasm32-unknown-unknown
Build tool, if relevant: trank
OS, if relevant: windows 11
Browser and version, if relevant: not relevant

Questionnaire

[ ] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

use_state.set re-renders the component, which means the component function is called again. You create GameManager in the function body (not in any hook) so it gets re-created every time set is called


Removes AwaitsFix annotation from MetadataRegressionIT tests

Signed-off-by: Robert Downs<EMAIL_ADDRESS>Issue #, if available:
https://github.com/opensearch-project/index-management/issues/176
Description of changes:
Removes AwaitsFix annotation from MetadataRegressionIT tests as the upstream bug causing these failures was fixed.
CheckList:

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #193 (b21c650) into main (5b48f51) will increase coverage by 0.96%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #193      +/-   ##
============================================
+ Coverage     74.65%   75.61%   +0.96%
- Complexity     1897     1922      +25
============================================
  Files           260      260
  Lines         11094    11094
  Branches       1746     1746
============================================
+ Hits           8282     8389     +107
+ Misses         1876     1760     -116
- Partials        936      945       +9

Impacted Files
Coverage Δ

...nt/indexstatemanagement/model/destination/Chime.kt
40.90% <0.00%> (-13.64%)
:arrow_down:

...anagement/indexstatemanagement/model/Transition.kt
63.07% <0.00%> (-4.62%)
:arrow_down:

...earch/indexmanagement/transform/model/Transform.kt
86.00% <0.00%> (-1.00%)
:arrow_down:

.../opensearch/indexmanagement/rollup/model/Rollup.kt
83.96% <0.00%> (-0.48%)
:arrow_down:

...nsform/action/stop/TransportStopTransformAction.kt
72.15% <0.00%> (ø)

...indexstatemanagement/model/ManagedIndexMetaData.kt
91.19% <0.00%> (+0.51%)
:arrow_up:

...agement/indexstatemanagement/ManagedIndexRunner.kt
54.93% <0.00%> (+0.53%)
:arrow_up:

...nt/indexstatemanagement/ManagedIndexCoordinator.kt
71.77% <0.00%> (+0.69%)
:arrow_up:

...transport/action/explain/TransportExplainAction.kt
73.41% <0.00%> (+1.15%)
:arrow_up:

...ndexstatemanagement/IndexStateManagementHistory.kt
80.14% <0.00%> (+1.47%)
:arrow_up:

... and 8 more

Continue to review full report at Codecov.

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


[TwigComponent] Remove undefined var $name in ComponentExtension

Q
A

Bug fix?
yes

New feature?
no

Tickets
Fix #1115

License
MIT

Implement the solution suggested by @kbond  here:  https://github.com/symfony/ux/issues/1115#issuecomment-1719726445

Thanks Simon!


WIP: Node upgrade test

First PR to address #7914. When complete, will also fix TODOs 2 and 3 on this comment in #8081
This is a WIP because node upgrades have been failing for me; the nodes are fine, but the apiserver is not able to talk to the nodes after the nodes are upgraded. I wanted to start getting feedback while investigating this problem.
This makes a few changes to allow code reuse from service.go and resize_nodes.go:

WebserverTest (services.go) nows uses RCs instead of pods. This means we now test RCs, and the pods survive node upgrades.
upgrade.sh now has a -P option to only prepare a node upgrade
renames and generalizes some stuff in resize_nodes.go

+cc @mikedanese @davidopp @zmerlynn

well on the master /var/log/kube-apiserver.log has thousands of pages of errors that look like:
I0617 23:53:09.666597       6 handlers.go:135] GET /api/v1/pods?fieldSelector=spec.host%3De2e-test-maxforbes-minion-6nwe: (76.558µs) 401
goroutine 8180 [running]:
github.com/GoogleCloudPlatform/kubernetes/pkg/httplog.(*respLogger).WriteHeader(0xc209a43080, 0x191)
	/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/httplog/log.go:188 +0x9a
net/http.Error(0x7fa5bf40a530, 0xc209a43080, 0x1144cb0, 0xc, 0x191)
	/usr/src/go/src/net/http/server.go:1274 +0x9a
github.com/GoogleCloudPlatform/kubernetes/pkg/auth/handlers.unauthorizedBasicAuth(0x7fa5bf40a530, 0xc209a43080, 0xc2089576c0)
	/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/auth/handlers/handlers.go:62 +0x99
net/http.HandlerFunc.ServeHTTP(0x14124c0, 0x7fa5bf40a530, 0xc209a43080, 0xc2089576c0)
	/usr/src/go/src/net/http/server.go:1265 +0x41
github.com/GoogleCloudPlatform/kubernetes/pkg/auth/handlers.func·001(0x7fa5bf40a530, 0xc209a43080, 0xc2089576c0)
	/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/auth/handlers/handlers.go:39 +0x2f7
net/http.HandlerFunc.ServeHTTP(0xc20879eb40, 0x7fa5bf40a530, 0xc209a43080, 0xc2089576c0)
	/usr/src/go/src/net/http/server.go:1265 +0x41
github.com/GoogleCloudPlatform/kubernetes/pkg/api.func·019(0x7fa5bf40a530, 0xc209a43080, 0xc2089576c0)
	/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/api/requestcontext.go:101 +0xe1
net/http.HandlerFunc.ServeHTTP(0xc20873fd80, 0x7fa5bf40a530, 0xc209a43080, 0xc2089576c0)
	/usr/src/go/src/net/http/server.go:1265 +0x41
github.com/GoogleCloudPlatform/kubernetes/pkg/api.func·019(0x7fa5bf40a530, 0xc209a43080, 0xc2089576c0)
	/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/api/requestcontext.go:101 +0xe1
net/http.HandlerFunc.ServeHTTP(0xc20889fae0, 0x7fa5bf40a530, 0xc209a43080, 0xc2089576c0)
	/usr/src/go/src/net/http/server.go:1265 +0x41
github.com/GoogleCloudPlatform/kubernetes/ [[kubelet/v0.19.0 (linux/amd64) kubernetes/dd7a6a0] <IP_ADDRESS>:40225]

looks like the master isn't auth'd to the nodes after the restart. I'm going to check the kube-env and make sure something isn't getting rewritten (or not written).

OK, I've figured out the problem. We're clobbering kube-env vals of the master during the master upgrade, and then trying to get them from the master for the node upgrade.
Given some of these env vars will probably soon be transitioned off of the master altogether, the best solution here is probably to look at the current node template. Expect a fix in an hour or two.

This should be fixed with the latest commit. @roberthbailey please take a look when you have time. I'll verify the whole thing works in an hour or two and remove the WIP label then.

This is ready for review. Please let me know if you'd like me to split it into separate PRs for the cluster/gce/upgrade.sh fixes, etc.

I squashed and pushed (hopefully didn't kill any comments you were writing). Rebasing with 14 commits was getting annoying. PTAL.

LGTM.

Removing LGTM label while I manually run tests; want to ensure everything I touched is fine.

Tests
Services: ✓
Resize: ✓
The changes to Restart, RC, and Reboot are trivial enough I don't think they require an extra by-hand test like the above.

:+1:


Vertex color being doubled upon saving

import ssbh_data_py
mesh = ssbh_data_py.mesh_data.read_mesh("model.numshb")
mesh.save("model.numshb")

The file used is stage/battlefield_s/normal/model/floating_plate_set/model.numshb
Before:

After:

Aside from the vertex color information, data at 0x1E8008 in the example file also begins to differ from the original file. The mesh names are being stored in the incorrect order and the string pointers' relative addresses are shifted as a result.

Aside from the vertex color information, data at 0x1E8008 in the example file also begins to differ from the original file. The mesh names are being stored in the incorrect order and the string pointers' relative addresses are shifted as a result.
The example modifies the attribute data and adds an additional attribute, so it won't be binary identical with the original. ssbh_data will often not be exactly 1:1 due to differences in precision for attribute data, floating point rounding errors, etc.

I'm generating the rigging data in a slightly different order (per mesh rather than per buffer), which I'll adjust to preserve ordering for existing files. The code is using ssbh_lib for exporting, so I'm not too worried about offsets shifting. It's probably due to the other file changes like the rigging buffers changing order.

The vertex color doubling is definitely a bug. It's an easy fix, but you'll have to multiply by 0.5 or divide by 2 for now until the next release.


Implement JSON value to Bal type direct mapping utility

Purpose

The purpose of this module is to map JSON value directly into the Ballerina record without converting into intermediate steps. And to develop as an independent module under misc, such it can be reused in other places.

Fixes https://github.com/ballerina-platform/ballerina-lang/issues/36212
Approach

Please find the design details in the below documents. JSON value to Ballerina record mapping details can be found here[1] and the implementation specification here[2].
[1] https://docs.google.com/document/d/1hgVsywpozJEVS-DWQxY8iADCEc9LIQcMorSmOfPhF6Q/edit
[2] https://docs.google.com/document/d/19bxPh5sfR_ctOuBEDp4pJzMMHdYElPdb0nT2coWYZbU/edit#

Remarks

Issues related to this PR https://github.com/ballerina-platform/ballerina-lang/issues/36212, https://github.com/ballerina-platform/ballerina-lang/issues/36486

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This PR is being closed in lieu of Implement JSON value to Bal type direct mapping utility


Latency Improve

Question
Hi there, thanks for your great work!
I'm a beginner in quantization, and I ran the example usage script on llama-2-7b according to README.md. I noticed that the evaluation process for fake quantization (00:40) is faster than real quantization (01:21). I'm curious about what might be causing this or this phenomenon is normal. Intuitively, I expected the real quantized version to be faster. Below are the scripts and logs. Any hints would be appreciated. Thanks!
test scripts
# evaluate the AWQ quantize model (simulated pseudo quantization)
$env/python -m awq.entry --model_path /mnt/afs/user/liyawei/projects/llama/$MODEL \
    --tasks wikitext \
    --w_bit 4 --q_group_size 128 \
    --load_awq awq_cache/$MODEL-w4-g128.pt \
    --q_backend fake

# load and evaluate the real quantized model (smaller gpu memory usage)
$env/python -m awq.entry --model_path /mnt/afs/user/jarvis/projects/llama/$MODEL \
    --tasks wikitext \
    --w_bit 4 --q_group_size 128 \
    --load_quant quant_cache/$MODEL-w4-g128-awq.pt

output logs
pt-7eelyeph-worker-0 logs: PATH = /mnt/afs/user/jarvis/.scc/bin:/usr/local/lib/miniconda3/bin:/usr/local/nvidia/bin:/usr/local/cuda/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
pt-7eelyeph-worker-0 logs: LD_LIBRARY_PATH = /usr/local/cuda-11.8/lib64:/usr/local/nvidia/lib:/usr/local/nvidia/lib64
pt-7eelyeph-worker-0 logs: dir = /mnt/afs/user/jarvis/projects/llm-awq_test
pt-7eelyeph-worker-0 logs: env = /mnt/afs/user/jarvis/.conda/envs/lion_awq/bin
pt-7eelyeph-worker-0 logs: [2024-01-12 15:41:30,358] [INFO] [real_accelerator.py:158:get_accelerator] Setting ds_accelerator to cuda (auto detect)
pt-7eelyeph-worker-0 logs: Quantization config: {'zero_point': True, 'q_group_size': 128}
pt-7eelyeph-worker-0 logs: * Building model /mnt/afs/user/jarvis/projects/llama/llama-2-7b-hf
Loading checkpoint shards: 100%|██████████| 3/3 [00:37<00:00, 12.41s/it]
pt-7eelyeph-worker-0 logs: Loading pre-computed AWQ results from awq_cache/llama-2-7b-hf-w4-g128.pt
pseudo weight quantization...: 100%|██████████| 32/32 [00:04<00:00,  6.96it/s]
Downloading readme: 100%|██████████| 10.5k/10.5k [00:00<00:00, 52.3MB/s]
Downloading data: 100%|██████████| 733k/733k [00:00<00:00, 830kB/s]
Downloading data: 100%|██████████| 6.36M/6.36M [00:02<00:00, 2.77MB/s]
Downloading data: 100%|██████████| 657k/657k [00:00<00:00, 950kB/s]t]]
Downloading data files: 100%|██████████| 3/3 [00:03<00:00,  1.29s/it]
Extracting data files: 100%|██████████| 3/3 [00:00<00:00, 3112.27it/s]
Generating test split: 100%|██████████| 4358/4358 [00:00<00:00, 132771.44 examples/s]
Generating train split: 100%|██████████| 36718/36718 [00:00<00:00, 1145600.07 examples/s]
Generating validation split: 100%|██████████| 3760/3760 [00:00<00:00, 1030487.65 examples/s]
evaluating...: 100%|██████████| 166/166 [00:40<00:00,  4.08it/s]
pt-7eelyeph-worker-0 logs: Current GPU memory usage: 12.84 GB
pt-7eelyeph-worker-0 logs: Peak GPU memory usage: 14.91 GB
pt-7eelyeph-worker-0 logs: 5.610528945922852
pt-7eelyeph-worker-0 logs: [2024-01-12 15:43:41,536] [INFO] [real_accelerator.py:158:get_accelerator] Setting ds_accelerator to cuda (auto detect)
pt-7eelyeph-worker-0 logs: Quantization config: {'zero_point': True, 'q_group_size': 128}
pt-7eelyeph-worker-0 logs: * Building model /mnt/afs/user/liyawei/projects/llama/llama-2-7b-hf
pt-7eelyeph-worker-0 logs: Loading pre-computed quantized weights...
real weight quantization...(init only): 100%|██████████| 32/32 [00:00<00:00, 996.29it/s]
evaluating...: 100%|██████████| 166/166 [01:21<00:00,  2.03it/s]
pt-7eelyeph-worker-0 logs: Current GPU memory usage: 3.96 GB
pt-7eelyeph-worker-0 logs: Peak GPU memory usage: 6.03 GB
pt-7eelyeph-worker-0 logs: 5.610483646392822

me too fake and fp13 is faster than the real w4a16quant

me too fake and fp16 is faster than the real w4a16 quant, i do not now why


Add g6.xlarge Benchmarks + CI Check for Existing Benchmark Data

@flaub - This worked. We are ready to promote the label to prod.
When adding labels to test Benchmarks of SPECIFIC device types, using os/feature/device  labels via include should avoid runner overlap issues as long as cpu is not one of the runner's labels.
This should work for promotion to Prod:
labels: [self-hosted, prod, bench, "${{ matrix.os }}", "${{ matrix.device }}"]
if: needs.changes.outputs.trigger-bench == 'true'
needs: changes
strategy:
  fail-fast: false
  matrix:
    os: [Linux, macOS]
    feature: [prove]
    device: [cpu]
    include:
      - os: [Linux]
         feature: [cuda]
         device: [g6.xlarge]

If that works for you, I'd love to update the labels and test this over the weekend to ensure there is no overlap so we can start landing these.

Benchmark files generated in ghpages as expected after testing:

Application Benchmarks .csv
Datasheet .json

The Application Benchmarks page pulls the new type as expected for the next release: PREVIEW

PR 2004 is needed before the Datasheet Reports page will pull reports for additional benchmark types.

This is required for the page to correctly parse and render benchmarks that were available during previous releases versus the current one.
Without this, adding a new benchmark type to the existing array in datasheet-content.tsx will throw a prerender-error for each previous release that the benchmark type did not exist.
The same was previously done for applications-benchmarks-contents.tsx, adding a distinguishing array as a constants.tsx file.

Documented process for adding and testing new benchmarks in CI and on Reports page HERE

Leaving this as a Draft so it does not get landed yet, as we will vet all of this when everyone is back.
@flaub @ssh-nkar @nahoc @carterbrett @SchmErik @nvzqz


Const constructor audit.

Where possible this uses this boilerplate text instead of bespoke text
that doesn't say anything more useful:
  /// Abstract const constructor. This constructor enables subclasses to provide
  /// const constructors so that they can be used in const expressions.

Pre-launch Checklist

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

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

cc @HansMuller

Landing on green, please let me know if I'm wrong about the parent/ancestor thing and I'll fix in a subsequent PR. Thanks!


The simplest of queries returns with no [query] registered for [query]

I don't know what I'm doing wrong. This is my first sample rule copied from frequency example. This is the query:
filter:
- query:
    query_string:
      query: "level:INFO"

I can run this in Kibana against the same index I have and get lots of rows back. however using elastalert-test-rule rules\frequency.yaml I get the following error:
D:\app\elastalert>elastalert-test-rule rules\frequency.yaml
Successfully loaded SampleRule1

WARNING:elasticsearch:GET http://SAADCPHXVM04:9200/logs-*/_search?ignore_unavailable=true&size=1 [status:400 request:0.0
05s]
Error running your filter:
RequestError(400, u'parsing_exception', {u'status': 400, u'error': {u'line': 1, u'root_cause': [{u'reason': u'no [query]
 registered for [query]', u'type': u'parsing_exception', u'line': 1, u'col': 202}], u'type': u'parsing_exception', u'rea
son': u'no [query] registered for [query]', u'col': 202}})
INFO:elastalert:Note: In debug mode, alerts will be logged to console but NOT actually sent. To send them, use --verbose
.
WARNING:elasticsearch:GET http://SAADCPHXVM04:9200/logs-*/_search?_source_include=%40timestamp%2C%2A&ignore_unavailable=
true&scroll=30s&size=10000 [status:400 request:0.006s]
ERROR:root:Error running query: TransportError(400, u'parsing_exception', u'no [query] registered for [query]')

Would have written the following documents to writeback index (default is elastalert_status):

elastalert_error - {'message': "Error running query: TransportError(400, u'parsing_exception', u'no [query] registered f
or [query]')", 'traceback': ['Traceback (most recent call last):', '  File "d:\\app\\elastalert\\lib\\site-packages\\ela
stalert-0.1.11-py2.7.egg\\elastalert\\elastalert.py", line 311, in get_hits', "    res = self.current_es.search(scroll=s
croll_keepalive, index=index, size=rule['max_query_size'], body=query, ignore_unavailable=True, **extra_args)", '  File
"build\\bdist.win-amd64\\egg\\elasticsearch\\client\\utils.py", line 73, in _wrapped', '    return func(*args, params=pa
rams, **kwargs)', '  File "build\\bdist.win-amd64\\egg\\elasticsearch\\client\\__init__.py", line 625, in search', "
doc_type, '_search'), params=params, body=body)", '  File "build\\bdist.win-amd64\\egg\\elasticsearch\\transport.py", li
ne 318, in perform_request', '    status, headers, data = connection.perform_request(method, url, params, body, ignore=i
gnore, timeout=timeout)', '  File "build\\bdist.win-amd64\\egg\\elasticsearch\\connection\\http_requests.py", line 89, i
n perform_request', '    self._raise_error(response.status_code, raw_data)', '  File "build\\bdist.win-amd64\\egg\\elast
icsearch\\connection\\base.py", line 124, in _raise_error', '    raise HTTP_EXCEPTIONS.get(status_code, TransportError)(
status_code, error_message, additional_info)', "RequestError: TransportError(400, u'parsing_exception', u'no [query] reg
istered for [query]')"], 'data': {'query': {'sort': [{'@timestamp': {'order': 'asc'}}], 'query': {'bool': {'filter': {'b
ool': {'must': [{'range': {'@timestamp': {'gt': '2017-04-19T18:23:14.855Z', 'lte': '2017-04-19T18:38:14.855Z'}}}, {'quer
y': {'query_string': {'query': 'level:INFO'}}}]}}}}}, 'rule': 'SampleRule1'}}

One other thing i noticed was the range for timestamp. In the response coming back this is what i see:
{'range': {'@timestamp': {'gt': '2017-04-19T18:23:14.855Z', 'lte': '2017-04-19T18:38:14.855Z'}}
but in my rule i have:
timeframe:
  days: 10

It looks like that is also ignored
thanks
Jeff

I'm seeing something similar after updating. Old rules that are known to work.

Also seeing this for previously working rules after upgrading to 0.1.11
Rules are of the form
filter:
- query:
    query_string:
      query: "field:value"

Arg! I'm so sorry about this. Fixed now in master. I'll release a new version very soon.
Fixed in https://github.com/Yelp/elastalert/commit/95b3f0ad0bb9450987de09e45bb316a60f7a620b

This problem still continues even after upgrading to elastalert-0.1.12.dist
I just want to make sure it's nothing that I'm doing wrong.
BTW after every update to elastalert we have to go through a period of package finding since compatbilities break. This time the upgrade from 1.11 to 1.12 caused a few ripples on "botocore<1.6.0,>=1.5.0", requests==2.2.1, requests-oauthlib==0.5.0, and PyJWT>=1.4.2
The error from elastalert-test-rule:
D:\app\elastalert>elastalert-test-rule --config config.yaml rules\frequency.yaml
Successfully loaded SampleRule1

INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): SAADCPHXVM04
INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): SAADCPHXVM04
WARNING:elasticsearch:GET http://SAADCPHXVM04:9200/logs-*/_search?ignore_unavailable=true&size=1 [status:400 request:0.0
15s]
Error running your filter:
RequestError(400, u'parsing_exception', {u'status': 400, u'error': {u'line': 1, u'root_cause': [{u'reason': u'no [query]
 registered for [query]', u'type': u'parsing_exception', u'line': 1, u'col': 202}], u'type': u'parsing_exception', u'rea
son': u'no [query] registered for [query]', u'col': 202}})
INFO:elastalert:Note: In debug mode, alerts will be logged to console but NOT actually sent. To send them, use --verbose
.
INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): SAADCPHXVM04
INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): SAADCPHXVM04
INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): SAADCPHXVM04
INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): SAADCPHXVM04
WARNING:elasticsearch:GET http://SAADCPHXVM04:9200/logs-*/_search?_source_include=%40timestamp%2C%2A&ignore_unavailable=
true&scroll=30s&size=10000 [status:400 request:0.016s]
ERROR:root:Error running query: TransportError(400, u'parsing_exception', u'no [query] registered for [query]')

Would have written the following documents to writeback index (default is elastalert_status):

elastalert_error - {'message': "Error running query: TransportError(400, u'parsing_exception', u'no [query] registered f
or [query]')", 'traceback': ['Traceback (most recent call last):', '  File "c:\\programdata\\anaconda2\\lib\\site-packag
es\\elastalert-0.1.11-py2.7.egg\\elastalert\\elastalert.py", line 311, in get_hits', "    res = self.current_es.search(s
croll=scroll_keepalive, index=index, size=rule['max_query_size'], body=query, ignore_unavailable=True, **extra_args)", '
  File "d:\\app\\elastalert\\lib\\site-packages\\elasticsearch\\client\\utils.py", line 73, in _wrapped', '    return fu
nc(*args, params=params, **kwargs)', '  File "d:\\app\\elastalert\\lib\\site-packages\\elasticsearch\\client\\__init__.p
y", line 625, in search', "    doc_type, '_search'), params=params, body=body)", '  File "d:\\app\\elastalert\\lib\\site
-packages\\elasticsearch\\transport.py", line 318, in perform_request', '    status, headers, data = connection.perform_
request(method, url, params, body, ignore=ignore, timeout=timeout)', '  File "d:\\app\\elastalert\\lib\\site-packages\\e
lasticsearch\\connection\\http_requests.py", line 89, in perform_request', '    self._raise_error(response.status_code,
raw_data)', '  File "d:\\app\\elastalert\\lib\\site-packages\\elasticsearch\\connection\\base.py", line 124, in _raise_e
rror', '    raise HTTP_EXCEPTIONS.get(status_code, TransportError)(status_code, error_message, additional_info)', "Reque
stError: TransportError(400, u'parsing_exception', u'no [query] registered for [query]')"], 'data': {'query': {'sort': [
{'@timestamp': {'order': 'asc'}}], 'query': {'bool': {'filter': {'bool': {'must': [{'range': {'@timestamp': {'gt': '2017
-04-23T16:49:21.337Z', 'lte': '2017-04-23T17:04:21.337Z'}}}, {'query': {'query_string': {'query': 'level:INFO'}}}]}}}}},
 'rule': 'SampleRule1'}}

You can also change your query to
filter:
   - query_string:
      query: "level:INFO"

That worked @Qmando . thanks!


"undefined" string appearing in the doc links

What happened:
Refer the below image:

https://github.com/litmuschaos/litmus-docs/pull/241 is proposed fix.

Fixed by https://github.com/litmuschaos/litmus-docs/pull/241


[Prototype] DI Aware AuthZ Requirement changes

Hi @HaoK, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

@divega @blowdart Updated with the proposed DI aware IRequirements.  It causes some significant changes to some of the surface area.
Before: IRequirements were always instances, now we need to register factory methods to produce these, and only create them at the very end.  As a result all of the old collections of Requirements are now internal/hidden, as they have turned into Func of ISP => IRequirements.  Other than that the concepts are mostly the same, except we also had to drop any extension methods that directly authorized against Policies as well since they also no longer have instances.
I think these changes are relatively harmless in terms of usage...thoughts?

I'm ok with that.

Decided against this for now


Full Screen works only on Ios

This package doesnt support full screen on android. ?  😞
Please can you add full screen support for android.

Hello @tdammy92
This package does not support full screen at all. It only offers you what you need to implement it based on your needs. Packages like react-native-orientation-locker can come in handy, but that's really up to the user, and we dont want to force people to use OUR implementation of fullscreen, when they perhaps need something else.


Messages in group are not updated when a user sends his

existing group PM with two people
user has not yet participated
user sends messages to this group and his messaged does not appear
happens on mobile, but not on the web

@zulipbot claim

Closing as fixed.


LateInitializationError

The following error occurred when using Grid on Tab, No issues if I use the grid on the 1st tab, throws an error if I use it on the 2nd Tab.
LateInitializationError: Field 'stateManagerTrans' has not been initialized.
Any suggestions to avoid this error
Thanks in advance

Can you attach a simple sample code to reproduce the error?


New GCode viewer lib

Hi,
my GCode viewer experiment is quite usable now. https://github.com/aligator/dev/pull/3
Currently I am working on being able to show only parts of the gcode.
For now it supports only basic gcode commands which I also use in GoSlice.
I will export it into an extra js lib. (most likely MIT license)
Then we can use it here.

Now you can try the current state at https://aligator.dev/
Just insert gcode and an example file will be rendered.
You can also use the GoSlice cli with links to stl files. GoSlice is run as Webassembly (slower...) and after that it displays the result in the viewer. E.g.:
goslice https://cdn.thingiverse.com/assets/81/ad/25/a7/b1/Bearing_6000_V02_tolMin.stl (any normal goslice param can be appended...)
I added a slider at the bottom to change the visible layers.

Hi! Very cool terminal and gcode viewer :)
I only got a bit time to check out your gcode viewer this morning and it seems the axis in which it renders to is swapped (Z in 3D printing is up while in three.js it is Y, see the attached image).

I am not sure if this is a bug or feature 🤔
Let me know when you created a formal repo on the gcode viewer so I can integrate them into the slicer Web UI 👍🏻

It's a bug, should be fixed in the lib :-)
https://github.com/aligator/gcode-viewer
As you don't use npm in SlicerA, you can use the bundled version
<EMAIL_ADDRESS>or the minified one
<EMAIL_ADDRESS>(You may put the file directly into the repo, just add a note which version it is, to keep track of it...)
For examples look here:
https://raw.githubusercontent.com/aligator/gcode-viewer/main/example/index.html
https://github.com/aligator/dev/blob/main/src/windows/gcodeViewer.tsx
and also see the documentation in the readme and the comments in the code.
Feel free to create issues if needed :-)

Gcode viewer integrated into SlicerA for standalone mode.
See change log here

Very cool, will try it out :-)


Separate tileset options into streaming-options and content-options

The old TilesetOptions only has streaming-related options, so I renamed it TilesetStreamingOptions and created a separate options struct called TilesetContentOptions (open to suggestions for a different name for this one). The TilesetContentOptions is also passed into the Tileset constructor, but unlike the streaming options, the content options gets passed (through TileContext) into Tile and then from there to TileContentLoadInput. There, it becomes available to the content loaders while they are parsing content as well as creating gltf models. In my current, very narrow use case, I'm only using it for the watermask, but I assumed this will be a useful infrastructure for the near future; to be able to configure content parsing / gltf creation from outside the cesium-native API.
Watermask can now trivially be enabled/disabled from the cesium-unreal side as a result of these changes.

@kring Can you have a quick look at this when you get the chance? This is a pretty simple refactor PR. I made this separate so it would be easier to review compared to having this all be part of the watermask PR directly (since this is more general than just the watermask).

sorry for the delay, I'm looking through the PR currently

I'll let Bao review this properly, but I just took a quick look at a high level, and I want to throw out an idea. What do you think about keeping TilesetOptions with that name, and putting TilesetContentOptions as a field inside it? My reasoning is that there's at least one property (credit) that isn't exactly a streaming option, and there may be more in the future. And structuring it this way is a much less breaking change for existing code.

Let me think about this a little bit more. If this is done right, we might be able to tackle https://github.com/CesiumGS/cesium-native/issues/196 too


Implement TreeSet-based acyclic decompression

@gdalle The optimized version of the acyclic coloring is finally working! :muscle:
I was able to verify it on this example:
using SparseMatrixColorings

A = Float64[
   1  2  0  0  0  0  3  0  0  0
   2  4  5  0  6  0  0  0  0  0
   0  5  7  8  0  9  0  0  0  0
   0  0  8  10 0  0  0  0  0  11
   0  6  0  0  12 13 0  14 0  0
   0  0  9  0  13 15 0  0  16 0
   3  0  0  0  0  0  17 18 0  0
   0  0  0  0  14 0  18 19 20 0
   0  0  0  0  0  16 0  20 21 22
   0  0  0  11 0  0  0  0  22 23
] |> sparse

g = SparseMatrixColorings.Graph(A - Diagonal(A))
order = SparseMatrixColorings.NaturalOrder()

colors, tree_set = SparseMatrixColorings.acyclic_coloring(g, order)

result = coloring(
            A,
            ColoringProblem(;
                structure=:symmetric, partition=:column, decompression=:substitution
            ),
            GreedyColoringAlgorithm(),
        )
column_colors(result)

@test colors == [1, 2, 1, 2, 1, 3, 2, 3, 2, 1]

S = map(!iszero, A)
S = Float64.(S)
A0 = copy(A)
B = [
                            A0[1,1]    A0[1,2]+A0[1,7]                0
            A0[2,1]+A0[2,3]+A0[2,5]            A0[2,2]                0
                            A0[3,3]    A0[3,2]+A0[3,4]          A0[3,6]
                   A0[4,3]+A0[4,10]            A0[4,4]                0
                            A0[5,5]            A0[5,2]  A0[5,6]+A0[5,8]
                    A0[6,3]+A0[6,5]            A0[6,9]          A0[6,6]
                            A0[7,1]            A0[7,7]          A0[7,8]
                            A0[8,5]    A0[8,7]+A0[8,9]          A0[8,8]
                           A0[9,10]            A0[9,9]  A0[9,6]+A0[9,8]
                          A0[10,10]  A0[10,4]+A0[10,9]                0
        ]

A2 = SparseMatrixColorings.decompress_acyclic!(S, B, colors, tree_set)

Thanks! I merge main into this branch and adapted the interface so that your decompression code gets used in all the tests, and it looks like there are some failures still

Random tests strike again 😎

Fixed 😎

I added a few more tests to cover all possible bases, let me just merge those and then I think this PR will be ready to roll

Another thing to make sure of is that decompression does not modify the forest in the result object. I haven't checked

Another thing to make sure of is that decompression does not modify the forest in the result object. I haven't checked

forest is modified only at the first call or decompress. It can update the root parent of each edge if needed.

What matters is that we can call decompression twice in a row and get the correct result, which I think is the case. Just to make sure, you could duplicate the decompression test lines in test/utils.jl so that they run twice.

@gdalle
If we update our TreeSet structure, we can perform these computations only once when we create the tree_set at the end of the acyclic_coloring.
This will ensure that the decompression is optimal and performed in O(|E|) time.
We can still optimize the DFS order for the trees, but we have already made significant improvements to the decompression process.

@gdalle
using LinearAlgebra, SparseArrays
using SparseMatrixColorings
using MatrixMarket, SuiteSparseMatrixCollection

ssmc = ssmc_db(verbose=false)
dataset = ssmc[(ssmc.numerical_symmetry .== 1) .& (200000 .≤ ssmc.nrows .≤ 300000), :]
paths = fetch_ssmc(dataset, format="MM")
nb_pb = length(paths)

for (i, path) in enumerate(paths)

  pb = split(path, '/')[end]
  println("Problem $i/$nb_pb: $pb")

  # println("Lecture des données: ")
  A = MatrixMarket.mmread(path * "/$pb.mtx")
  println("size(A) = ", size(A), " | nnz(A) = ", nnz(A))

  # Star coloring
  result = coloring(
            A,
            ColoringProblem(;
                structure=:symmetric, partition=:column, decompression=:direct
            ),
            GreedyColoringAlgorithm(),
        )
  timer = @elapsed coloring(
            A,
            ColoringProblem(;
                structure=:symmetric, partition=:column, decompression=:direct
            ),
            GreedyColoringAlgorithm(),
        )
  colors = column_colors(result)
  ncolors = unique(colors) |> length
  println("Star coloring: ", ncolors)
  println("timer: ", timer)

  # Acyclic coloring
  result = coloring(
            A,
            ColoringProblem(;
                structure=:symmetric, partition=:column, decompression=:substitution
            ),
            GreedyColoringAlgorithm(),
        )
  timer = @elapsed coloring(
            A,
            ColoringProblem(;
                structure=:symmetric, partition=:column, decompression=:substitution
            ),
            GreedyColoringAlgorithm(),
        )
  colors = column_colors(result)
  ncolors = unique(colors) |> length
  println("Acyclic coloring: ", ncolors)
  println("timer: ", timer)
  println()
end

Problem 1/38: pwtk
size(A) = (217918, 217918) | nnz(A) = 11524432
Star coloring: 108
timer: 13.275666601
Acyclic coloring: 53
timer: 10.017835665

Problem 2/38: Lin
size(A) = (256000, 256000) | nnz(A) = 1766400
Star coloring: 11
timer: 0.570040176
Acyclic coloring: 7
timer: 0.678558693

Problem 3/38: bmw3_2
size(A) = (227362, 227362) | nnz(A) = 11288630
Star coloring: 135
timer: 12.257366888
Acyclic coloring: 71
timer: 7.83447513

Problem 4/38: fcondp2
size(A) = (201822, 201822) | nnz(A) = 11294316
Star coloring: 111
timer: 12.289692995
Acyclic coloring: 66
timer: 9.947373563

Problem 5/38: halfb
size(A) = (224617, 224617) | nnz(A) = 12387821
Star coloring: 117
timer: 14.194495256
Acyclic coloring: 60
timer: 9.290101493

Problem 6/38: hood
size(A) = (220542, 220542) | nnz(A) = 9895422
Star coloring: 89
timer: 9.413525359
Acyclic coloring: 55
timer: 6.929516684

Problem 7/38: troll
size(A) = (213453, 213453) | nnz(A) = 11985111
Star coloring: 108
timer: 15.561040888
Acyclic coloring: 57
timer: 11.82566261

Problem 8/38: CO
size(A) = (221119, 221119) | nnz(A) = 7666057
Star coloring: 264
timer: 10.860656442
Acyclic coloring: 152
timer: 9.852414572

Problem 9/38: Ga41As41H72
size(A) = (268096, 268096) | nnz(A) = 18488476
Star coloring: 565
timer:<PHONE_NUMBER>75
Acyclic coloring: 391
timer: 42.221200902

Problem 10/38: Si87H76
size(A) = (240369, 240369) | nnz(A) = 10661631
Star coloring: 283
timer: 31.545367728
Acyclic coloring: 176
timer: 17.024328905

Problem 11/38: BenElechi1
size(A) = (245874, 245874) | nnz(A) = 13150496
Star coloring: 71
timer: 15.361302623
Acyclic coloring: 42
timer: 11.290947979

Problem 12/38: 3Dspectralwave2
size(A) = (292008, 292008) | nnz(A) = 12935272
Star coloring: 102
timer: 30.127591632
Acyclic coloring: 39
timer: 23.510229553

Problem 13/38: thermomech_dM
size(A) = (204316, 204316) | nnz(A) = 1423116
Star coloring: 11
timer: 0.59547018
Acyclic coloring: 7
timer: 0.526237929

Problem 14/38: offshore
size(A) = (259789, 259789) | nnz(A) = 4242673
Star coloring: 29
timer: 2.930412158
Acyclic coloring: 14
timer: 2.581180775

Problem 15/38: citationCiteseer
size(A) = (268495, 268495) | nnz(A) = 2313294
Star coloring: 213
timer: 4.579315949
Acyclic coloring: 65
timer: 5.125990285

Problem 16/38: coAuthorsCiteseer
size(A) = (227320, 227320) | nnz(A) = 1628268
Star coloring: 106
timer: 1.37077632
Acyclic coloring: 87
timer: 1.615801889

Problem 17/38: coAuthorsDBLP
size(A) = (299067, 299067) | nnz(A) = 1955352
Star coloring: 128
timer: 1.737375587
Acyclic coloring: 115
timer: 2.237246244

Problem 18/38: delaunay_n18
size(A) = (262144, 262144) | nnz(A) = 1572792
Star coloring: 17
timer: 0.779370072
Acyclic coloring: 7
timer: 0.592075091

Very nice! I had no idea the number of colors would improve so much!
Do you want to update the TreeSet in this PR or merge first and optimize later? Also what's your opinion on #64?


Support and test the cudf backend

Depends on https://github.com/dask/dask/pull/10398
TODO:

[ ] Improve testing

Oh cool.  I'm curious to see what comes here.
My sense (correct me if I'm wrong) is that we probably don't want to annotate every test in order to support GPUs.  I'm thinking that this is just a temporary thing as you're playing around.  If not then let's chat.

My sense (correct me if I'm wrong) is that we probably don't want to annotate every test in order to support GPUs. I'm thinking that this is just a temporary thing as you're playing around. If not then let's chat.

Right, I'd rather not annotate everything, and I'm definitely still exploring here.
It isn't difficult to parameterize the df fixture to use both pandas and cudf (when available). However, it turns out that many tests fail for cudf. In some cases, the failures are from bugs (e.g. https://github.com/rapidsai/cudf/pull/13666). In other cases it's because of limits in cudf's API coverage. For example, explode doesn't work because we assume that the backend supports a list of columns (and cudf doesn't), and idxmin/max doesn't work, because cudf only has this operation implemented for groupby.
At the moment, I'm thinking that I should just configure pdf/df with something like:
@pytest.fixture(
    params=[
        "pandas",
        pytest.param("cudf", marks=pytest.mark.skipif(cudf is None, reason="cudf not found.")),
    ]
)
def backend(request):
    yield request.param

I'm thinking this would allow us to skip (maybe xfail?) specific tests for the "cudf" backend instead of annotating every test. That said, I'm still feeling open to completely different approaches. I'm certainly preoccupied with finding/fixing the actual bugs that I'm finding.

Update:

This PR is currently blocked by https://github.com/dask-contrib/dask-expr/pull/223 and https://github.com/rapidsai/cudf/pull/13692 (related to deterministic tokenization)
In order to reduce the test complexity here, I am thinking that I may roll back the pandas/cudf parameterization, and instead use an environment variable (e.g. TEST_DASK_EXPR_BACKEND) to define the backend library to import/use. This would allow one to run tests with the cudf backend by executing something like: TEST_DASK_EXPR_BACKEND=cudf py.test -v dask_expr

thx!


Support textDocument.signatureHelp LSP request

The service (something like SignatureHelpService) should be accompanied with an AbstractSignatureHelpProvider that gives us the current AST element at the cursor position.

@msujew I never tried to implement a new service from scratch but would like to have a go at it if possible. I can start in 2 weeks when I am back from vacation

#612


Update Travis Ruby versions

Description of changes
Bumps the Travis Ruby versions for JRuby <IP_ADDRESS> and Ruby 2.6.0-preview2.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Trying to stay up to date is always challenging. Thank you for the pull request.


Ability to get some 'SmartProperty' with extra information

This is a feature which obviously is not a simple one but can be useful. Implementation for all the features can be spread in multiple release.
The concept for 'SmartProperty' (named can be different obviously), example:
final SmartProperty<String> myProperty = new SmartProperty<String>("my.super.key");
final String value = myProperty.getValue();

but where it's interesting is for some extra information (meta information) about the property:
Date myProperty.getLoadedTime();
MetaPropertyInformation myProperty.getMetaInformation();
long myProperty.getMetaInformation().getLineNumber();

getLoadedTime() --> return the date/time when the property was loaded from it's config source
getMetaInformation() --> return a new object which can provide more details on where that property was setup (file name, URL etc...) and can provide potentially the line number where that property was defined.
the getLoadedTime() method may make more sense to be in the MetaPropertyInformation class.
The other big advantage of the "SmartProperty" class by using "getValue()" instead of potentially caching the value one time, it will automatically return the latest value if the source for the property is one that was setup to be reloaded every X minutes / seconds.

We can and should add this.
Linenumber would be a bit tough, but resource name and scheme should be easy
file:://foo.bar/, http://localhost:9090/consul/config/, etc.
Some parsers support line number and the ones that do .. we can expose. For others.. -1?
There is some prior art.
https://github.com/typesafehub/config/blob/b0ae5cac203ab24f8fd4a04b211b92e479e39490/config/src/main/java/com/typesafe/config/ConfigOrigin.java#L30
There is a ConfigValue, ConfigObject which has ConfigOrigin. I will probably go with these names if possible since this seems to be a popular lib. But I see that this is a nice feature.

I will add this to konf core.