k3d instructions

What would you like to be added:
k3d kubefed scripts
Why is this needed:
k3d is similar to kind, but requires less resources

/kind feature

I think I managed to get it working with the following
ctrl.yml
apiVersion: k3d.io/v1alpha2
kind: Simple
image: docker.io/rancher/k3s:v1.19.10-k3s1
servers: 1
agents: 0  # only create master node on kubefed control plane
# ports:
#   - port: <IP_ADDRESS>:8080:80
#     nodeFilters:
#       - agent[0]
#   - port: <IP_ADDRESS>:8443:443
#     nodeFilters:
#       - agent[0]
#   - port: <IP_ADDRESS>:5053:53/udp
#     nodeFilters:
#       - agent[0]
options:
  k3d:
    wait: true
    timeout: "60s"
    disableLoadbalancer: true
    disableImageVolume: true
  k3s:
    extraServerArgs:
      - "--no-deploy=traefik,servicelb,metrics-server"
    extraAgentArgs: []
  kubeconfig:
    updateDefaultKubeconfig: true
    switchCurrentContext: true

worker.yml
apiVersion: k3d.io/v1alpha2
kind: Simple
image: docker.io/rancher/k3s:v1.19.10-k3s1
servers: 1
agents: 1
# ports:
#   - port: <IP_ADDRESS>:9080:80
#     nodeFilters:
#       - agent[0]
#   - port: <IP_ADDRESS>:9443:443
#     nodeFilters:
#       - agent[0]
#   - port: <IP_ADDRESS>:5054:53/udp
#     nodeFilters:
#       - agent[0]
options:
  k3d:
    wait: true
    timeout: "60s"
    disableLoadbalancer: true
    disableImageVolume: true
  k3s:
    extraServerArgs:
      - "--no-deploy=traefik,servicelb,metrics-server"
    extraAgentArgs: []
  kubeconfig:
    updateDefaultKubeconfig: true
    switchCurrentContext: true

With these steps
docker network create k3d-bridge

k3d cluster create ctrl --config=./resources/ctrl.yml --network k3d-bridge
helm --namespace kube-federation-system upgrade -i kubefed kubefed-charts/kubefed --create-namespace

k3d cluster create worker --config=./resources/worker.yml --network k3d-bridge
helm --namespace kube-federation-system upgrade -i kubefed kubefed-charts/kubefed --create-namespace

kubectl config use-context k3d-ctrl

kubefedctl join k3d-ctrl --cluster-context k3d-ctrl \
    --host-cluster-context k3d-ctrl --v=2
kubefedctl join k3d-worker --cluster-context k3d-worker \
    --host-cluster-context k3d-ctrl --v=2

Since I'm on a Mac, I found the kind patch script in scripts/, and changed one line for k3d, and ran that
IP_ADDR="$(docker inspect -f "${INSPECT_PATH}" "${cluster}-server-0")"

Now I have
$ kubectl -n kube-federation-system get kubefedclusters
NAME         AGE     READY
k3d-worker   7m3s    True
k3d-ctrl     7m14s   True

And I verified the FederatedConfigMap example in the README worked...
$  kubectl -n federate-me describe fcm my-cm
...
Events:
  Type     Reason                 Age   From                           Message
  ----     ------                 ----  ----                           -------
  Normal   CreateInCluster        82s   federatedconfigmap-controller  Creating ConfigMap "federate-me/my-cm" in cluster "k3d-ctrl"
  Warning  CreateInClusterFailed  82s   federatedconfigmap-controller  Failed to create ConfigMap "federate-me/my-cm" in cluster "k3d-ctrl": An update will be attempted instead of a creation due to an existing resource
  Normal   CreateInCluster        81s   federatedconfigmap-controller  Creating ConfigMap "federate-me/my-cm" in cluster "k3d-worker"
  Normal   UpdateInCluster        81s   federatedconfigmap-controller  Updating ConfigMap "federate-me/my-cm" in cluster "k3d-ctrl"

Could run through the same, and tell me if I missed anything? If not, I can work on submitting docs/scripts, and maybe update the README to use deploy.k3d instead of deploy.kind??

/remove-lifecycle rotten


Replace AWS subgraph with Chainstack's

📄 Context
We will sunset subgraph support on our infrastructure, lowering costs and maintenance work. So we will be replacing the current AWS with another provider called Chainstack
✔ Solution
Replace all AWS-related configurations with Chainstack's. That includes;

Update the GraphQL Apollo configurations.
Update the ISR for the staking pool pages.
Check with the API stats needs any changes.
Remove all the code related to the extended version.
Remove any usage of the feature flags; aws and apr (all related to AWS and the extended version provided by Postgraphile )in the code base.

📈 Subtasks

[ ] Create a feature flag to switch between hosted services and Chainstack.
[ ] Update graphQL Apollo configuration with Chainstack information
[ ] Remove all code definitions related to the graphql extended version. i.e. components/hooks/tests/stories.
[ ] Check on API stats if any change is necessary.
[ ] Check on the safe wallet (a.k.a Gnosis Safe).

🎯 Definition of Done

[ ] Running Staking in the Preview environment works seamlessly.
[ ] Running Staking in a Production environment works seamlessly.
[ ] Switch feature flag will change the data source without causing problems.

That is a work in conjunction with subgraph issue#13


Use newer version of vue-template-compiler

Otherwise "webpack --watch --env.tns --env.ios" fails

I got an error running webpack
ERROR in ./VueComponent.vue
Module build failed: Error:

Vue packages version mismatch:

-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>
This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

This minor change resolves that error.

Thanks. I found that before. I was just waiting to grab more changes. This is a good way to let vue-template-compiler follow  vue.


Simulate GPTQ quantization

Implement GPTQQuantizer to simulate quantized weights and get the expected performance measures.

Could you explain more what you mean by simulating GPTQ?

Right now a model can be loaded with GPTQ only if it's already quantized on the hub (like the Bloke repos). While BnB allows for zero shot quantization which is applied instantly.
GPTQ Quantization requires a real dataset for calibration (like c4)  but that takes a lot of time. So if someone wanna know how a model will perform (latency vs memory) in its GPTQ format, they should wait 2 or 4 GPU hours. The idea is to skip that with a dummy dataset (can be just one sentence) to get the quantized weights and perform latency, training throughput and memory measurements.

Ah okay makes sense, thanks!


The week number is not correct on Sundays in the US region

Hi guys, thank you for the great Joplin plugin.
I would like to report a minor issue that I have with the journal on Sundays in the US region:
If I click on Sunday, 22th when creating a journal, I am getting the week 51.
If I click on Monday, 23rd, then I am getting the week 52.
In both cases it is expected to have the week 52 as weeks started on Sundays.
Thank you again.

Thanks for this feedback.
I need to look up information on how to correctly obtain the week number.


Label descendants are removed or "concatenated"

Hello,
What am I trying to do?
I'm trying to use Bootstrap display utility classes to render different elements inside the label on different screen sizes.
What is the issue?
The descendants of the .custom-file-label tag are being modified in a weird way.
Example 1:
This is the HTML I provide in my file:

    Upload
    Drop files here or click to upload

And this is what it is rendered as after the plugin is initialized:

UploadDrop files here or click to upload

Example 2:
This is the HTML I provide in my file:

Upload

Drop files here or click to upload

And this is what it is rendered as after the plugin is initialized:

UploadDrop files here or click to upload

Drop files here or click to upload

I am using React and Bootstrap v5 (I'm using v4 class names as well to make this compatible, since this plugin looks for v4 class names)

We have this issue too.
It's because the script uses HTMLElement.innerText to grab the label text to put into the file browser.


password for user ubuntu and root

Hi Thanks for the image, runs good! i just started the docker, and i was user " ubuntu" without giving a password. now i want to "su" to root or "sudo" or change the password of the standard user "ubuntu"!! But HOW?
my best

Hi there, not sure if this is still an issue for you.
You will find the default pw here: https://github.com/fcwu/docker-ubuntu-vnc-desktop/blob/develop/rootfs/startup.sh


Open void in the mining dimesion

I'm using the 1.18 generation datapack for 1.17 while using this mod and I come across a pocket of void where the rest of the cave would be.

Yep, 1.17 mods are designed for 1.17 not 1.18.

https://feedback.minecraft.net/hc/en-us/articles/4402614709389-Caves-Cliffs-Prototype-Data-Pack-for-Minecraft-Java-Edition
This is clearly a 1.17 datapack.

it changes world height which is not currently supported as a general standard.  I will be supporting the new world height when Mojang releases it with 1.18.

it's okay, a simple datapack with edited world heights seem to fix that

very good.  Mods cannot access the new world height, because it is not part of the Fabric API.
Enjoy.

You could just force a layer of bedrock at y 0 like in a superflat world

I'm fine waiting until I see how Mojang implements things in 1.18


Add FCM to the Functions sample to exercise IID integration.

LGTM once Travis goes green.

Thanks. Travis is failing because I haven't added FCM to the gradle file yet. I'll do that before I submit.

@bklimt any update on this/

Thanks for the reminder. I pushed the new build.gradle. If Travis turns green, I'll merge.

@bklimt thanks!  Make sure to use the "Squash and Merge" option

Yes, of course. I'm surprised the repo even allows merge commits.


Is it a good idea to prepopulate new installation with some sample questions, sample users?

The other day I've cloned the repository... I've created the account and realized:

there are very cool screenshots in the whitepaper
when starting on the platform everything is fresh
can we provide a default demo/demo credentials, can we pre-populate the system with a few a sample proposals for easier testing?

I'm worried about security considerations, even if the password is changeme some people won't... That's the downside of default credentials. Also the pre-populated database could be problematic in terms of security, maintenance.

Hello @stefek99 !
This is a legitimate question, and a practice often seen on distributed applications. The keyword here is fixtures. We aim to provide a command line that will populate the database with such fixtures for easier testing. But to do that, and to be able to maintain them sanely, we need some more architecture (see #220).

In regard to the security issues raised by such practice, well… A good solution is to generate random passwords for the dummy users and ask for a username and password during the installation of the fixtures.

Also, other option is to only create fixtures when Meteor.isDevelopment so you can start a site in production with an empty database and a dev site with some data.

Happy to take any recommendations and suggestions regarding this. I think it's a good idea.

I use:
https://www.npmjs.com/package/@cleverbeagle/seeder
Quite easy usage:
https://cleverbeagle.com/packages/seeder/usage
Example in action:
https://github.com/cleverbeagle/pup/blob/master/imports/startup/server/fixtures.js

@vjrj Seeder looks super-nice ! We should probably use it in the feature suite as well, no ?
This way, we can have fixtures written in gherkin, and that will provide boilerplates for bug reporters to expose their bugs using gherkin as well ?

SGTM!


Ability to add component meta

This pull request is related with the #24 issue.
This will let user to add meta information about the component, in their #{component}.yml file.
I didn't know the best way of configuring this so I changed a liitle the structure of the yml file, now you need to have stubs that would be an array of components.
There could be some problems for supporting previous components, so I added a extra check on the display of the component, to check it follow the correct format stubs_correct_format? so that way if in the future we change the format the user will know. Also if the user have previous stubs it will show the correct format to him thanks to this method stub_example, it will show an example component yml file.
I will wait for your feedback

@jgnatch  any opinions about the implementation ?

Hey @GustavoCaso at a first sight it looks well and it is something really handy so we are thankful for your contribution :grinning:
I'll probably take a look tomorrow and @kitop too.
If everything works as expected we'll definitely merge it.
Thanks again!
Nacho

Hey @jgnatch.
I'm really happy to contribute, I will try to contribute more, I really find it useful.
Also thanks for correcting my english grammar :hammer:
See you around.

@GustavoCaso looks good!
I'm giving it a deeper look, and some though to see if there's a way to make it a bit more backwards compatible. So expect some more feedback soon.

@kitop Added your feedback, hope you like it I will wait for your opinions

@jgnatch @kitop I have update my code to support Array and Hashes and remove the extra lines for the new hint. But I'm not able to fix the random failing test could give a hand or skip them to merge this pull request and open a new issue to fix this problem ??
Really appreciated, thanks.

@GustavoCaso Thanks!!
Re-run the test and now passed—yeah, that should be handled in a different issue/PR.
Will give it a look tomorrow evening :) Thanks again!!!

@kitop how we doing with this one ?

@GustavoCaso having some really busy days, sorry for the delay!!
Should be reviewed and merged soon :)

@GustavoCaso Sorry for the late response! Everything looks great.
There's only one small thing that I guess it was a bit confusing in the talk.
Regarding the
def self.stub_example
  File.read(File.expand_path("../example.yml", __FILE__))
end

and related code that was changed in: a77f908639be30ed1f9923407099d5b003c0d012.
When I mentioned erb, I was thinking of making the yml file and erb, so example.yml.erb so you could interpolate things in there, like the name of the component.
The change introduces some more complexity, and I guess it was because of miscommunication. Sorry about that!
Ideally, going back to the original way it was done, but just changing stub_example to be an instance variable reading from a example.yml file (not even adding the erb stuff now) would simplify the code a bit.
Sorry if I wasn't clear the first time. I can merge and make that change myself if you prefer. Just let me know.

@kitop Don't worry I can do it myself, I really like to help.
So basically what you want is an yml.erb that can interpolate variables ?

I'd was thinking of that, but more than happy to hear what you think about it!
Just going back to how the example was rendered (by just reading a file), but make that file a bit more flexible so we could add component name and make the help a bit more friendly :)
Sorry again about the miscommunication!

@kitop I tried doing that, loading a file example with extension yml.erb and did not feel natural to me.
Already with current working functionality, there is an example.html.erbthat can by as flexible as you want it to be, passing the component name and all the future functionality added to the component, if the example file needed.
But what I did was added the name of the component to that file and display and example stubs so that the users knows how to proceed if they don't have stubs or the have invalid format.
Still giving support for previous stubs as Array

@kitop I have no idea such helper exists, the problem is using srtip_heredoc will place the example_stubs just below the :stubs: array and we don't want that.

A part from this is there anything else you would do differently.
I will wait for your feedback @kitop

@GustavoCaso Ah, I see. Thanks for the screenshot :) I guess the :stubs: should be in the string too to be formatted properly, but not a big deal.
Everything looks great! Thanks again for your collaboration. Will probably merge today.

@kitop I moved stubs into the example_stubs now we are using strip_heredoc
When you merge it I will start with the PR #24  for adding extra pages to the style guide

Hey @kitop what is the status with this one ?

@GustavoCaso merged. Thanks for your patience!

@kitop Thanks to you. This was my first contribution to open source. I really excited about it.
As mention before I will continue working with the other issue #24

Congrats @GustavoCaso!!
All contributions are welcome :)

:clap: :clap: :grinning:

Hi guys, do you realise this isn't yet in a tagged release so bundler isn't pulling in the changes?
I got around it by pulling in the master branch directly from github:
gem 'mountain_view', git: 'https://github.com/jgnatch/mountain_view', branch: 'master'

I'm not sure if that's intentional, or just an oversight.

@OddEssay totally an oversight! Just released v0.8.0 :smile:
Thanks for letting us know!
Readme still has to be updated to reflect latest changes, but the code is in there!


feat: Made home page responsive

Solved issue #152
Made the home page responsive. Working fine on mobile phones and tablets

You have Included only one audio files can you add the remaining files /.

@Ctoic I have added all audio files

Still not eorking. You are not following the theme.

I'm closing your pull request @imrehankhan always remember contribute quality code to a project.


CORE-3414 Made used LoggingExecutor configurable, added batchChangelogStatement flag to not add GO statement in printed out sql statements after each statement

See https://liquibase.jira.com/browse/CORE-3414
┆Issue is synchronized with this Jira Story by Unito
┆Fix Versions: Liquibase 4.0 beta 3

Hi @eicki ,
Thanks for your pull request!
Here’s what happens next:
A member of the Liquibase team will take a look at your contribution and may suggest:

Changes based on guidelines for PR submission
Additional tests (unit and/or integration)
Provide other feedback, like requesting changes.

The PR will be prioritized according to our internal development and testing capacity.
We’ll let you know when it’s ready to move to the next step or if any changes are needed.

Hello again @eicki , would you please resolve conflicts and consider adding tests please? :)

Made risk high due to no tests, conflicts on branch and no response from author.

Hi sorry for not responding, we meanwhile implemented a couple of other things in liquibase, (but we are still using 3.5.x, we will upgrade to latest version in the upcoming months and while doing that we will create pull requests for those changes as well as rebasing this PR

@eicki perfect!  Best place to start would be to resolve the Liquibase.java file so the auto build can  compile and run the tests, we can move forward from there.  Thanks again!


feat: arm64 builds

Hi, is there any change you could release arm64 binaries/docker images?
Thanks!

Hey, good idea!
Will try to extend our release github actions to include those.

Thanks!

Just to be clear you were looking for linux arm64 builds, not OSX ones right?

@gruuya - indeed, mostly to run in docker. Thanks

Actually, I believe we're blocked here until GitHub offers Linux Arm64 hosted runner images: https://github.com/actions/runner-images/issues/5631


Added Partition of Array algorithm

Name the program which is added
Partition of array
Programming Language
C++
I AM
a student
GITHUB USERNAME
MilanshuRathi

Thanks for choosing our repository for contributing to Hacktober Fest 20
As a part of the new process this Issue is marked as hacktoberfest-expiry & closed
Please check our new updated contribution guidelines here


Branch request: tsc-1.5.0-beta

I would like to submit a small change to auth0 from my branch but it applies to 1.5.0-beta and not -alpha. Could a new branch be created for tsc-1.5.0-beta?
Branch: https://github.com/aarondandy/DefinitelyTyped/tree/tsc-1.5.0-beta-auth0-fix

@aarondandy tsc-1.5.0-alpha branch is already using 1.5.0-beta. https://github.com/borisyankov/DefinitelyTyped/blob/tsc-1.5.0-alpha/package.json#L39
please send your change to 1.5.0-alpha branch.

https://github.com/borisyankov/DefinitelyTyped/pull/4101

Done.


Use Apple Universal Links for iOs for opening ss:// links right in the app

What would you like the app to enable you to do?
I want to be able to open Outline invitations from browser or anywhere automatically in Outline app. Say, I share a link with a friend, I want him to be able to open Outline App on-clicking my invitation.
Describe alternatives you've considered
Current solution, with auto-paste in client is okay, yet sub-optimal.
Additional context
See more on Apple Universal links for iOs devices: https://developer.apple.com/library/archive/documentation/General/Conceptual/AppSearch/UniversalLinks.html

You can send a link ss://... and when a user clicks on it, iOS automatically opens Outline with the configuration inserted.


ceph-docker-osd CPU Usage rate very very high

PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
28750 root      20   0 1133936 176848  23364 S 465.8  0.7  26:38.37 ceph-osd -i 10 -k /var/lib/ceph/osd/ceph-10/keyring
28438 root      20   0 1116804 220084  23660 S 465.2  0.9  26:45.00 ceph-osd -i 9 -k /var/lib/ceph/osd/ceph-9/keyring
21411 root      20   0<PHONE_NUMBER>92  21652 S   9.0  0.6   1:26.98 ceph-osd -i 11 -k /var/lib/ceph/osd/ceph-11/keyring
My environment is Ubuntu14.04.3 Docker version 1.8.1, build d12ea79
Double  Intel(R) Xeon(R) CPU           L5520  @ 2.27GHz
Memory 32G

Kernel 4.0.9 My Comand is
docker run -itd --name=ceph-osd-11 --net=host -v /data/disk3/ceph-11:/var/lib/ceph/osd/ceph-11 ceph/osd
But I install ceph-osd in Physical machine Cpu Usage is little

This sounds very much as if you are running separate OSD containers on the same machine.  In that case, you need to share the ipc namespace between them.  The easiest way to do that is to add --ipc=host to each of those docker run commands.  You can also execute a single container with each of the OSD directories bound in.  In this case, the container will appropriately launch the number of OSD's whose directories you pass.
See Issue #19 for more information.

@Ulexus  My problem has been solved. By add --pid=host
Thank you very much


tf.python.keras.layers.preprocessing.index_lookup.IndexLookup cannot be saved and loaded

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information
Please check this Colab using tf-nightly.
Also reproduced in 2.2.0rc2
https://colab.research.google.com/drive/1QFmqgiGLsHN3shnEuhakAWLrqjT0nD6B

Have I written custom code (as opposed to using a stock
example script provided in TensorFlow):
OS Platform and Distribution (e.g.,
Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if
the issue happens on mobile device:
TensorFlow installed from (source or
binary): - TensorFlow version (use command below):
Python version: - Bazel
version (if compiling from source):
GCC/Compiler version (if compiling from
source):
CUDA/cuDNN version: - GPU model and memory:

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with: 1. TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)" 2. TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Describe the current behavior
After saving and loading the model the output of the layer is different.
Describe the expected behavior
The output should be the same
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
https://colab.research.google.com/drive/1QFmqgiGLsHN3shnEuhakAWLrqjT0nD6B
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

Was able to reproduce the issue.Please find the gist here

@saikumarchalla Thank you for the feedback!
AutoKeras is pending on this issue for the next release.
So it would be good to have an estimated timeline of resolving this issue,
so that our team can better coordinate to figure out a solution on our side.

Hi @haifeng-jin - because IndexLookup isn't officially exported yet, we need to treat it as a custom symbol. Can you try adding custom_objects={"IndexLookup": preprocessing.index_lookup.IndexLookup} to your load_model call? This worked for me at head in nightly.

@markomernick @k-w-w
It works! Thank you for the help.
I am closing this issue now.


Add a User Profiles page 🌟🌟🌟

👤✨ I want to create a normal user profile page and a profile icon in the home page navbar that redirects to the profile page...
PA please assign me for this task...

@SaurabhS55 @pulkitpathak99 @Rizwan102003 PA please assign me

@Subhajit-2023-44 we do not need this feature currently. Please find any other issue to work on.


i can not find IDbConnectionFactory

i can not find IDbConnectionFactory
//Your DB Provider MicroOrmConfig.SqlProvider = SqlProvider.MySQL; //Your db factory services.AddSingleton<IDbConnectionFactory, DbFactory>(x => new DbFactory(appSettings.DbConnectionString));

@zmy012 You should implement Factory yourself


Deployment

Feature Description
[Describe the new feature you'd like to see in detail. Provide relevant context and any specific requirements or constraints.]
Why is this feature needed?
[Explain the problem or use case that this feature would address.]
Proposed Solution
[Provide a high-level overview of your proposed solution or any ideas you have for implementing the feature.]
Additional Information (optional)
[Add any additional information or context about the feature request.]
Assignees
[Specify the GitHub usernames of the assignees responsible for working on this issue. You can add multiple assignees by listing their usernames separated by commas.]
assignees:

assignee1
assignee2
assignee3

Hi @TabotCharlesBessong I really want to work on this issue

Ok, what about the other issues, I will be starting later today
On Sun, Mar 17, 2024, 7:00 AM Soham Roy @.***> wrote:

Hi @TabotCharlesBessong https://github.com/TabotCharlesBessong I really
want to work on this issue
—
Reply to this email directly, view it on GitHub
https://github.com/TabotCharlesBessong/MoshReactCourse/issues/13#issuecomment-2002322696,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATT4OGRQ3UKBZ44M4IIG76DYYUWRDAVCNFSM6AAAAABEZ44YLCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGMZDENRZGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


Can't use until reboot as Dualshock

When my dualshock's battery dries, I plug it to my computer to charge it up, I can use it on charge while dualshock emulated profile is on but when I unplug my dualshock, I cannot use dualshock emulated profile again until reboot

Please note that this version of DS4Windows is dead. You can get up-to-date builds from here: https://github.com/Ryochan7/DS4Windows/releases

Please note that this version of DS4Windows is dead. You can get up-to-date builds from here: https://github.com/Ryochan7/DS4Windows/releases

Sorry, I was already using the latest version, I did not realize that I was on the wrong section. Thank you for the link.

Sorry, I was already using the latest version, I did not realize that I was on the wrong section. Thank you for the link.


Kernel Restarting: The Kernel appears to have died, it will restart automatically.

After solving previous problem a new problem has arrived. The problem is:
After completing 1st iteration any Browser is unable to show Total amount of accuracy depend on Testing & validation data set. For more clearance a screenshot has given:

However, when i've tried to run the same code with 10,000 number of training data set it shows low amount of accuracy (average 50-55%) which is violate the main target of the project:

By this, classifier cant do correct  prediction i.e. near of 50% images gives correct result & rest are not....
Actually my target point is to run complete program without any issue. But now after solving one software issue this issue depend on software or hardware issue .... i really cant understand :( !!

Hi,  extremely sorry for the delay in my response. As long as you the test accuracy is increasing (as in your case) you don't have to worry. Run for more epochs. It is likely getting hanged because you might have less RAM and since we are loading all the images in the test/validation set at the same time, the load in CPU RAM is likely to be high. To negate this, you can perhaps send a small batches of test/validation images


Optimal intervention function

Assume a consistent policy of social distancing/masking will be implemented, resulting in a 50% decrease from baseline transmission. Assume that we want to minimize the time that the policy is in place, and once it has been put in place and then ended, it can't be re-implemented. Looking forward from “today’s” date of Dec. 28, 2021, what are the optimal start and end dates for this policy, to keep projections below the hospitalization threshold over the entire 3-month period? How many fewer hospitalizations and cases does this policy result in?

Now assume that instead of NPIs, the Board wants to focus all their resources on an aggressive vaccination campaign to increase the fraction of the total population that is vaccinated. What is the minimum intervention with vaccinations required in order for this intervention to have the same impact on cases and hospitalizations, as your optimal answer from question 3? Depending on the model you use, this may be represented as an increase in total vaccinated population, or increase in daily vaccination rate (% of eligible people vaccinated each day), or some other representation.

optimal_intervention(prob,p,effectiveness (e.g. 0.5),x,threshold)
Way to do it: do a 3 time solve. Solve to policy_start, then remake with lower parameter value, solve to policy_end, remake, solve to t end. Evaluate policy_end - policy_start. Global constraint that threshold is not hit, in terms of time above the threshold so that it's continuous.


"Unseen" command for ended series should show episodes left

Preferrably without adding a third line in the output, e.g.:
   19 The Walking Dead  (2010-2022)  ended                             tt1520211
       Next:  s11e17 Lockdown                                      45min 2022-10-02

Should show e.g.:
   19 The Walking Dead  (2010-2022)  ended   9 left                    tt1520211
       Next:  s11e17 Lockdown                                      45min 2022-10-02

Maybe it could show episodes left in the current season but also the total.

This is implemented, although the alignment of the text is wonky (this is a more general overhaul of format_episode_title()).

Can close this. The above-mentioned alignment isn't really related to this specific feature.


add_callback issue.

Hello,
I have a request and issue on the callbacks.
I cannot remove the callbacks I created :[ . I can add it and remove it directly. But I can't remove an old callback.
This works:
def activated(event):
    print(event)

button.add_callback("pressed",activated)
button.remove_callback("pressed",activated)

This does not:
def activated(event):
    print(event)

button.add_callback("pressed",activated)

## in interpreter   (activated is accessible in the interpreter)
>> button.remove_callback("pressed",activated)

Also, is it useful to have two callbacks for the same event ? My initial guess was that the new event would replace the previous one.
Cheers,
Jeremy.

I'm not sure to understand the difference between the two versions of your example. Using callbacks in interactive mode or in a script should not make any difference.
What I can think of is that you actually redefined the activated function and thus when you want to remove it as a callback it's not found anymore (it's not the same function). Is that right?

Also, is it useful to have two callbacks for the same event ? My initial guess was that the new event would replace the previous one.

Yes I guess you are right. Having multiple callbacks on the same event could be useful in complex setup but at the moment it's probably not worth the API complexity. We could imagine something like:
button.callbacks['pressed'] = activated
button.callbacks['pressed'] = eraseWithAnotherFunction
del button.callbacks['pressed']

Would this feel clearer?

Ok I see why,  was not sure what happened to the function when we redefine it.
Just one event will be much clearer, and it is not that hard to create a method to extend the previous callback to add event after or before the exsiting one.
Thanks :)


Prep for 1.9.0 release

dbt-core is on 1.8.4 and other adapters are all still using 1.8.x or below versioning. However, since the recent refactor, dbt adapters no longer require staying in pace with dbt versioning. From dbt team:

We generally recommend that major version bumps reflect major changes to the adapter and should therefore be reserved. Minor versions should reflect meaningful changes to behavior.

This release includes a major version bump for DuckDB from 0.10.x to 1.0.0 and support for the new DuckDB Secrets Manager, which could be categorized as a "meaningful changes" to the behavior (the feature gap between 0.10.x and 1.0.0 isn't huge - it was mostly bugfixes and stability improvements - and the secrets behavior is an addition that is backward compatible).
I started a discussion on dbt community Slack here: #adapter-ecosystem.
Update: Bumping major version based on discussion with dbt team

Pro case: this is a major change (the secrets manager switchover and the DuckDB 1.0.0 constraint).
Con case: will be confusing to users, I'm not 100% confident that the dbt folks are actually going to maintain compat with 1.8.x adapters when they do dbt-core 1.9.0 and will we then need to do a dbt-duckdb 1.9.x that fixes the compatibility issues with dbt-core 1.9.x which will be extra-extra confusing

That makes sense. For now we can just keep the adapter major version synced with the with dbt-core major version, and after they go through the 1.9 update we can reevaluate. wdyt?

(I meant to just comment but fat fingered the wrong button)


StatSender interface signature has changed

Hi there,
Tried configuring the StatSender in statsdmetrics.CommandFactory{} and realised the statsdmetrics.StatSender interface no longer matches the StatSender interface in go-statsd-client.
https://github.com/cactus/go-statsd-client/blob/6348b56a993b50ba0d50dd9c3515c79dab38d639/statsd/client.go#L18-L28
Seems like they've introduced a new variadic parameter for tags at the end

Thanks for the update.  I don't think I can change this API to match because it would be a breaking change for users of the library.  I recommend maybe a comment at the interface with a recommendation that people implement a custom metric's collector.
We have one for prometheus here.  If you want to make one for statsd with the new API, you can reference it and I'll update the docs to point to it as an alternative.

Will close as wontfix for v3 since we cannot break people's code, but will address in v4 here: #115


testing outputs of db-checkbook build

After running our pipeline from start to finish we realized that the output file shape was different than expected, so adding some basic tests to ensure that the output we export to DO is correct.
tagging @DeaBardhoshi
to do:

[x] create test file containing functions to test the output of running build.py
[x] ensure that the source data is the expected size (nycoc_checkbook.csv and all of the cpdb shapefiles)
[x] test the results of merging the cpdb geometries
[x] test cleaning checkbook nyc data
[x] test results of the groupby on fms_id of the checkbook data
[x] test the results of left joining the cpdb geometries onto the checkbook nyc dataset

Note for future: to improve testing for this pipeline, the functions in build.py should be re-written to be more modular, and in such a way that makes it simpler to run tests on sample data. For example, _merge_cpdb_geoms() takes no arguments and grabs the cpdb data from the .library folder, which makes it strenuous to manually pass test data to verify the outputs of this function.

also, definitely want to return to this and add testing for high sensitivity fixed asset category assignment


Set boundary conditions at model xy boundary when clipping

In GitLab by @JoerivanEngelen on Apr 17, 2023, 14:09
Add option to set boundary conditions at model boundary on the xy plane when clipping.
Behaviour iMOD5
By default, iMOD5 sets fixed heads at the model boundaries with the CHD package.
Heads for the boundary are taken from the heads defined under the CHD package section in the projectfile.
If not provided these are taken from the initial conditions.
The flag for this behaviour is APPLYCHD. If turned off, no heads are specified and effectly all these cells are turned into no-flow boundaries, but this probably is not commonly used.
Proposed behaviour iMOD Suite
Define optional argument (e.g. heads_for_boundary) in model.clip_box to set heads at model boundaries.
If provided, this sets a CHD package at the model boundary.
If None, no heads are specified at the model boundary.
The projectfile converter passes heads, either defined in the CHD section or to the initial state, to this argument.
In the future, similar behaviour can be implemented for the concentration to the SSM package.
Acceptance Criteria

Apply fixed head (Constand Head Package) if clip model is called with right kwarg.
Needs to work with projectfile converter
Only assign to cells if IBOUND == 1
Only does something if grids are provided via keyword argument heads_for_boundary
3 options:

If None: No flow (Do nothing)

If special-cased key: "initial": Use InitialCondition package to specify heads

If xarray DataArray: Use provided grids to specify heads

Workings
heads
-----

0.01 0.01 0.01 0.01
0.01 0.01 0.01 0.01
0.01 0.01 0.01 0.01
0.01 0.01 0.01 0.01

-> clip

0.01 0.01 0.01 0.01
0.01 0.01 0.01 0.01
0.01 0.01 0.01 0.01

-> find edges

0.01 0.01 0.01 0.01
0.01  nan  nan 0.01
0.01 0.01 0.01 0.01

In GitLab by @JoerivanEngelen on May 19, 2023, 11:35
added #384 as child task

added #405 as child task

added #402 as child task

added #403 as child task

added #404 as child task

added #418 as child task

added #419 as child task

removed child task #402

added #420 as child task

removed child task #420


CI: Add documentation on triggering the deployment workflow

Summary
Add documentation to the README on triggering the deployment workflow.

@adamfeuer @v01d @Ouss4 since you all have been helping out with the documentation I figured I should point you at this and add it to the README.

Thanks @btashton – this is what we run to deploy the website, including documentation, is that right?

yeah eventually this trigger will get called from the OS CI, but we need secrets configured for that and INFRA was looking into it so it is a quick manual step for now.

@btashton Cool, thank you. LGTM. 👍

yeah eventually this trigger will get called from the OS CI, but we need secrets configured for that and INFRA was looking into it so it is a quick manual step for now.
If the PR is against this repo then no additional action is needed.

Is there a link you can share to the request to INFRA? I would like to ping them to have this sorted out.

@btashton sorry to bother you, not sure if you were notified about my last comment

@v01d sure https://issues.apache.org/jira/browse/INFRA-20805  it was originally just about the PAT for deploying our container images to GitHub Container Registry, but it has the same PAT secret issue.  They said they needed to look into this, but I added a comment just not about this other use case explicitly.

Cool, thanks. I see you also just pinged them.

@btashton we're still not getting response from INFRA on this, which is worrying. Also, is it your intention that they create a PAT for us and then add it as a secret or the PAT would be from one of us?

@btashton we're still not getting response from INFRA on this, which is worrying. Also, is it your intention that they create a PAT for us and then add it as a secret or the PAT would be from one of us?

My intention is they create one because otherwise the PAT will include our private repos due to scoping. I can more it back to waiting for infra from review so it goes to the top of the  queue.
In the meantime we can also wire up a job that run every couple hours that syncs if there has been a change. Then it is automatic, and we still have the manual button if needed.

That's a good idea

@v01d do you want to give it a go? Otherwise I could pick it up over the weekend since I don't think there is a huge rush.
I'm thinking we just kick the build every two hour and don't worry about inspecting the commits in OS for changes since changes in some markdown external to the doc would also require a new build. It's not like these commits are that big and we could always prune the asf-site branch if needed.

Sure, I can give it a try. I assume GH actions supports a cron job, right? I will open an issue for this.

Yep you are looking for on.schedule
https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#onschedule


Costco API

Costco API Endpoint Fails
When searching for products on costco the results are not returned.
To Reproduce
Steps to reproduce the behavior:

Go to home page
Click on search
Scroll down to see the empty results
See error

Expected behavior
It should not be empty

Costco's website returns a 403 while trying to retrieve the html content using an automated tool. It might be due to Costco's access restrictions. So we will have to drop this API.


#soarca-107 feature: added example playbooks

Will close this PR in favor of #10 with better branch name.


Pods are going into CrashloopBackoff

Hi Team,
I am using latest version of splunk-connect-for-kubernetes helm chart but few pods are going into crashloopbackoff. Can someone please help here.
Error
NAME                                     READY   STATUS             RESTARTS   AGE   IP                NODE                NOMINATED NODE   READINESS GATES
lv-splunk-logging-5q9pf                  0/1     CrashLoopBackOff   12         47m   <IP_ADDRESS>    las2-mlgpu31        <none>           <none>
lv-splunk-logging-nzzld                  0/1     CrashLoopBackOff   13         47m   <IP_ADDRESS>    las2-mlgpu18        <none>           <none>
lv-splunk-logging-qjfgw                  0/1     CrashLoopBackOff   13         47m   <IP_ADDRESS>    aws-mlgpu03         <none>           <none>
lv-splunk-logging-zmvxp                  0/1     CrashLoopBackOff   13         47m   <IP_ADDRESS>    las2-mlgpu11        <none>           <none>

kubectl logs :
2023-02-06 14:42:08 +0000 [info]: init supervisor logger path=nil rotate_age=nil rotate_size=nil
2023-02-06 14:42:08 +0000 [info]: parsing config file is succeeded path="/fluentd/etc/fluent.conf"
2023-02-06 14:42:08 +0000 [info]: gem 'fluentd' version '1.15.3'
2023-02-06 14:42:08 +0000 [info]: gem 'fluent-plugin-concat' version '2.4.0'
2023-02-06 14:42:08 +0000 [info]: gem 'fluent-plugin-jq' version '0.5.1'
2023-02-06 14:42:08 +0000 [info]: gem 'fluent-plugin-kubernetes_metadata_filter' version '3.1.0'
2023-02-06 14:42:08 +0000 [info]: gem 'fluent-plugin-prometheus' version '2.0.2'
2023-02-06 14:42:08 +0000 [info]: gem 'fluent-plugin-record-modifier' version '2.1.0'
2023-02-06 14:42:08 +0000 [info]: gem 'fluent-plugin-splunk-hec' version '1.3.1'
2023-02-06 14:42:08 +0000 [info]: gem 'fluent-plugin-systemd' version '1.0.2'
2023-02-06 14:42:08 +0000 [INFO]: Reading bearer token from /var/run/secrets/kubernetes.io/serviceaccount/token
2023-02-06 14:42:11 +0000 [error]: config error file="/fluentd/etc/fluent.conf" error_class=Fluent::ConfigError error="Invalid Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api: Timed out connecting to server"

What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version): 1.17
Ruby version (use ruby --version):
OS (e.g: cat /etc/os-release):
Splunk version:
Splunk Connect for Kubernetes helm chart version: 1.5.2
Others:

Hi @kavita1205, can you share your values.yaml file? Also, did you make any changes to the template files?

Hi @harshit-splunk , I have fixed this issue by fixing calico networking pods.
Now, I am facing issue i.e. logs are not being generated in SCK. For the same, I have raised issue here in #849.


Split class to seperate files

jobs.js contains huge list of class. Probably it will be more readable if each class or will be in separate file

Done with other refactors.


[bug] Lock Current Status not updated

Describe the bug
A clear and concise description of what the bug is. Describe what causes the bug, what you observe, and what happens as a result.
BE469 - Touchscreen Deadbolt (Node 20)
BE469ZP - Touchscreen Deadbolt Z-Wave Plus (Node 21)
When the door lock for Node 20 is manually locker/unlocked I can see notifications like "Manual lock/unlock operation" but the state of the lock does not change.
When the door lock for Node 21 is manually locker/unlocked I can see notifications like "Manual lock/unlock operation" AND the state of the lock does changes as expected.
Device information
Which device(s) is/are affected (make/model)?
BE469 - Touchscreen Deadbolt (Node 20)
What are the node IDs?
Node 20
Last Known Working Configuration

[ ] New device

[ ] Previously working device (node-zwave-js)

Which library version/docker image/adapter version?
Have you made any recent configuration changes to the device? Describe.

[x] Previously working device (other platform)

Which platform? Vera
Have you made any recent configuration changes to the device? Describe.
Moved to zwave2mqtt & hass

Installation information
How did you install node-zwave-js?

[ ] Zwavejs2mqtt (latest) docker image
[x] Zwavejs2mqtt (dev) docker image
zwavejs/zwavejs2mqtt                          dev<PHONE_NUMBER>af        3 hours ago         314MB
[ ] ioBroker.zwave2 adapter
[ ] Pkg
[ ] Manual docker build

Against which branch of node-zwave-js?
With which branch of zwavejs2mqtt?

[ ] Other (describe)
[ ] Manually built (git clone - yarn install - yarn run build:full)

To Reproduce
Steps to reproduce the behavior:
'The door lock and lock it from the inside. Then check the zwave2mqtt logs and note that the only message is:
2021-01-22 13:38:16.160 INFO ZWAVE: Node 20: notification: Manual lock operation
If you do the same for Node 21 you can see:
2021-01-22 13:38:01.226 INFO ZWAVE: Node 21: notification: Manual lock operation
2021-01-22 13:38:01.387 INFO ZWAVE: Node 21: value updated: 98-0-currentMode 0 => 255
2021-01-22 13:38:01.390 INFO ZWAVE: Node 21: value updated: 98-0-outsideHandlesCanOpenDoor false,false,false,false => false,false,false,false
2021-01-22 13:38:01.393 INFO ZWAVE: Node 21: value updated: 98-0-insideHandlesCanOpenDoor false,false,false,false => false,false,false,false
2021-01-22 13:38:01.395 INFO ZWAVE: Node 21: value updated: 98-0-latchStatus open => open
2021-01-22 13:38:01.397 INFO ZWAVE: Node 21: value updated: 98-0-boltStatus unlocked => locked
2021-01-22 13:38:01.399 INFO ZWAVE: Node 21: value updated: 98-0-doorStatus open => open

Additional context
Add any other context about the problem here.
Relevant part extracted from zwavejs_1.log for the not working node, Node 20:
13:38:16.042 SERIAL « 0x010a00040014029840b80087                                          (12 bytes)
13:38:16.044 SERIAL » [ACK]                                                                   (0x06)
13:38:16.045 DRIVER « [Node 020] [REQ] [ApplicationCommand]
                      └─[SecurityCCNonceGet]
13:38:16.059 SERIAL » 0x01110013140a98803e95e48b36d235e5058886                            (19 bytes)
13:38:16.060 DRIVER » [Node 020] [REQ] [SendData]
                      │ transmit options: 0x05
                      │ callback id:      136
                      └─[SecurityCCNonceReport]
                          nonce: 0x3e95e48b36d235e5
13:38:16.063 SERIAL « [ACK]                                                                   (0x06)
13:38:16.068 SERIAL « 0x0104011301e8                                                       (6 bytes)
13:38:16.069 SERIAL » [ACK]                                                                   (0x06)
13:38:16.069 DRIVER « [RES] [SendData]
                        was sent: true
13:38:16.091 SERIAL « 0x011800138800000200b67f7f7f7f0101030000000002010000c8              (26 bytes)
13:38:16.091 SERIAL » [ACK]                                                                   (0x06)
13:38:16.093 DRIVER « [REQ] [SendData]
                        callback id:     136
                        transmit status: OK
13:38:16.150 SERIAL « 0x0125000400141d9881b978d04e1c804caece8661c77809de8ce37b3e5cf805e06 (39 bytes)
                      7a53887b5000d
13:38:16.152 SERIAL » [ACK]                                                                   (0x06)
13:38:16.156 DRIVER « [Node 020] [REQ] [ApplicationCommand]
                      └─[SecurityCCCommandEncapsulation]
                        │ sequenced: false
                        └─[NotificationCCReport]
                            notification type:   Access Control
                            notification status: 255
                            notification event:  Manual lock operation

zwavejs_1.log
zwave2mqtt.log
Relevant part extracted from zwavejs_1.log for the working node, Node 21:
13:38:01.122 SERIAL « 0x010a00040015029840c300fd                                          (12 bytes)
13:38:01.126 SERIAL » [ACK]                                                                   (0x06)
13:38:01.130 DRIVER « [Node 021] [REQ] [ApplicationCommand]
                      └─[SecurityCCNonceGet]
13:38:01.148 SERIAL » 0x01110013150a988036a536a65bb6419905864f                            (19 bytes)
13:38:01.149 DRIVER » [Node 021] [REQ] [SendData]
                      │ transmit options: 0x05
                      │ callback id:      134
                      └─[SecurityCCNonceReport]
                          nonce: 0x36a536a65bb64199
13:38:01.151 SERIAL « [ACK]                                                                   (0x06)
13:38:01.157 SERIAL « 0x0104011301e8                                                       (6 bytes)
13:38:01.157 SERIAL » [ACK]                                                                   (0x06)
13:38:01.158 DRIVER « [RES] [SendData]
                        was sent: true
13:38:01.182 SERIAL « 0x011800138600000300c17f7f7f7f0101030000000002010000b0              (26 bytes)
13:38:01.184 SERIAL » [ACK]                                                                   (0x06)
13:38:01.190 DRIVER « [REQ] [SendData]
                        callback id:     134
                        transmit status: OK
13:38:01.215 SERIAL « 0x0125000400151d98818daabfdc146956091209d554bb4930038dc13631edec3a0 (39 bytes)
                      671ff82c10049
13:38:01.217 SERIAL » [ACK]                                                                   (0x06)
13:38:01.222 DRIVER « [Node 021] [REQ] [ApplicationCommand]
                      └─[SecurityCCCommandEncapsulation]
                        │ sequenced: false
                        └─[NotificationCCReport]
                            notification type:   Access Control
                            notification status: 255
                            notification event:  Manual lock operation
13:38:01.294 SERIAL « 0x010a00040015029840c300fd                                          (12 bytes)
13:38:01.295 SERIAL » [ACK]                                                                   (0x06)
13:38:01.297 DRIVER « [Node 021] [REQ] [ApplicationCommand]
                      └─[SecurityCCNonceGet]
13:38:01.313 SERIAL » 0x01110013150a98807d16a782a16f6819058789                            (19 bytes)
13:38:01.314 DRIVER » [Node 021] [REQ] [SendData]
                      │ transmit options: 0x05
                      │ callback id:      135
                      └─[SecurityCCNonceReport]
                          nonce: 0x7d16a782a16f6819
13:38:01.317 SERIAL « [ACK]                                                                   (0x06)
13:38:01.322 SERIAL « 0x0104011301e8                                                       (6 bytes)
13:38:01.323 SERIAL » [ACK]                                                                   (0x06)
13:38:01.323 DRIVER « [RES] [SendData]
                        was sent: true
13:38:01.348 SERIAL « 0x011800138700000300c67f7f7f7f0101030000000002010000b6              (26 bytes)
13:38:01.349 SERIAL » [ACK]                                                                   (0x06)
13:38:01.350 DRIVER « [REQ] [SendData]
                        callback id:     135
                        transmit status: OK
13:38:01.380 SERIAL « 0x0123000400151b9881cdb4f6eed2a4a0511cb4bc089814cbfb7d1b2fcc6a0849c (37 bytes)
                      38cc400ac
13:38:01.381 SERIAL » [ACK]                                                                   (0x06)
13:38:01.385 CNTRLR   [Node 021] [~] [Door Lock] currentMode: 0 => 255                  [Endpoint 0]
13:38:01.389 CNTRLR   [Node 021] [~] [Door Lock] outsideHandlesCanOpenDoor: false,false [Endpoint 0]
                      ,false,false => false,false,false,false
13:38:01.392 CNTRLR   [Node 021] [~] [Door Lock] insideHandlesCanOpenDoor: false,false, [Endpoint 0]
                      false,false => false,false,false,false
13:38:01.394 CNTRLR   [Node 021] [~] [Door Lock] latchStatus: "open" => "open"          [Endpoint 0]
13:38:01.396 CNTRLR   [Node 021] [~] [Door Lock] boltStatus: "unlocked" => "locked"     [Endpoint 0]
13:38:01.398 CNTRLR   [Node 021] [~] [Door Lock] doorStatus: "open" => "open"           [Endpoint 0]
13:38:01.400 DRIVER « [Node 021] [REQ] [ApplicationCommand]
                      └─[SecurityCCCommandEncapsulation]
                        │ sequenced: false
                        └─[DoorLockCCOperationReport]
                            current mode:           Secured
                            active outside handles: false, false, false, false
                            active inside handles:  false, false, false, false
                            latch status:           open
                            bolt status:            locked
                            door status:            open

Logfile:
zwavejs and zwave2mqtt logs

I have tried to attached the logs, let me know if they don't show up. trying again in the comment
zwavejs_1.log
zwave2mqtt.log

I have tried to attached the logs, let me know if they don't show up. trying again in the comment
zwavejs_1.log
zwave2mqtt.log

I can't say for sure, but I guess (based on your logs and because I can't find anything in the manual) that Node 20 (which does not support Z-Wave+) expects us to poll for the current status.
I'm still in the process of adding an API for that which can be used over MQTT. Once that is in, you'll have to add some kind of automation in HA to poll the lock status when the Manual lock operation notification is received.

I can't say for sure, but I guess (based on your logs and because I can't find anything in the manual) that Node 20 (which does not support Z-Wave+) expects us to poll for the current status.
I'm still in the process of adding an API for that which can be used over MQTT. Once that is in, you'll have to add some kind of automation in HA to poll the lock status when the Manual lock operation notification is received.

Do you think that it would make sense to monitor the /nodeID_20/nodeID_20/notification/Manual_lock_operation and re-trigger a set lock call? Would this cause an issue if the door is locked and I send a lock request again?

Do you think that it would make sense to monitor the /nodeID_20/nodeID_20/notification/Manual_lock_operation and re-trigger a set lock call? Would this cause an issue if the door is locked and I send a lock request again?

Yes and no. I would issue a get call, but that isn't possible yet.

Yes and no. I would issue a get call, but that isn't possible yet.

I was thinking to do a set call, since the notification tells me what it needs to be :)

I was thinking to do a set call, since the notification tells me what it needs to be :)

Thats a dirty workaround, but should do the trick for now.

Thats a dirty workaround, but should do the trick for now.

In case somebody cares:
I order to tell Home Assistant to use MQTT Device Trigger I had to post to the following topic:
homeassistant/device_automation/nodeID_20/Manual_lock_operation/config
The following payload
{
  "automation_type": "trigger",
  "topic": "zwave/nodeID_20/notification/Manual_lock_operation",
  "type": "button_short_press",
  "subtype": "button_1",
  "device": {
    "identifiers": [
      "zwavejs2mqtt_0xf4c9e959_node20"
    ],
    "manufacturer": "Allegion",
    "model": "Touchscreen Deadbolt (BE469)",
    "name": "nodeID_20",
    "sw_version": "88.21"
  }
}

The above would automatically create a trigger for "Back Door Lock" called '"First Button" pressed'
Then in an automation I could use the following automation(I used the Automation UI to select for ticker the "Trigger Type" as  "Device" and "Action Type" as "Device") - the following YAML was auto generated:
- id: '1611336587134'
  alias: 3 - Back Door Lock
  description: ''
  trigger:
  - platform: device
    domain: mqtt
    device_id: d864eb9d8e0e99f9f9fff9740d232e4d
    type: button_short_press
    subtype: button_1
    discovery_id: nodeID_20 Manual_lock_operation
  condition: []
  action:
  - device_id: d864eb9d8e0e99f9f9fff9740d232e4d
    domain: lock
    entity_id: lock.nodeid_20_lock
    type: lock
  mode: single

I'll close the issue considering the above as the solution, even though it's more of a work around.

In case somebody cares:
I order to tell Home Assistant to use MQTT Device Trigger I had to post to the following topic:
homeassistant/device_automation/nodeID_20/Manual_lock_operation/config
The following payload
{
  "automation_type": "trigger",
  "topic": "zwave/nodeID_20/notification/Manual_lock_operation",
  "type": "button_short_press",
  "subtype": "button_1",
  "device": {
    "identifiers": [
      "zwavejs2mqtt_0xf4c9e959_node20"
    ],
    "manufacturer": "Allegion",
    "model": "Touchscreen Deadbolt (BE469)",
    "name": "nodeID_20",
    "sw_version": "88.21"
  }
}

The above would automatically create a trigger for "Back Door Lock" called '"First Button" pressed'
Then in an automation I could use the following automation(I used the Automation UI to select for ticker the "Trigger Type" as  "Device" and "Action Type" as "Device") - the following YAML was auto generated:
- id: '1611336587134'
  alias: 3 - Back Door Lock
  description: ''
  trigger:
  - platform: device
    domain: mqtt
    device_id: d864eb9d8e0e99f9f9fff9740d232e4d
    type: button_short_press
    subtype: button_1
    discovery_id: nodeID_20 Manual_lock_operation
  condition: []
  action:
  - device_id: d864eb9d8e0e99f9f9fff9740d232e4d
    domain: lock
    entity_id: lock.nodeid_20_lock
    type: lock
  mode: single

I'll close the issue considering the above as the solution, even though it's more of a work around.


Buildsystem and workflow improvements to the new Android custom builds

SCons: Generate android_source.zip during build

This is now needed after #27781, as this android_source.zip template
is used for custom Android builds from the editor.
I have yet to confirm that it works as expected though, my first test gave me a different and non-working APK when using a custom build with no custom config, compared to normal builds.

Android: Improve dialogs about custom build template

Still not perfect but it makes things a bit clearer regarding the fact that it's going to install source code in the project folder for custom Android builds, as opposed to downloading the regular templates.
Fixes #28736 - at least to some extent, the rest of the confusion is simply due to no official templates existing yet with this android_source.zip file.

Android: Extract libs from pre-built APKs when installing build template

First commit ignored the libs folder in the android_source.zip, but I learned that it's actually necessary. Instead of zipping it, we extract the libs directly from the pre-built APKs, so the android_source.zip stays 250 kiB instead of 54 MiB :)

Other things I plan to work on:

Bring back the move of the generated APK to bin/ when building the default templates. Need to find a way to have this behavior when building from Godot's repo, but not with custom builds. Any clue @godotengine/android @m4gr3d?
Adjust docs for 3.2 (godotengine/godot-docs#2599).

I have yet to confirm that it works as expected though, my first test gave me a different and non-working APK when using a custom build with no custom config, compared to normal builds.

So according to @reduz the libs folder with the compiled libs for all arches and targets also need to be zipped... Which would make it impossible to do this via SCons, as each scons call builds one lib, so the zipping should happen at the end. Could be done via Gradle, but then it's kind of the same issue as the currently disabled moving of the generated APKs, we don't want it in custom builds.
I'll see if I can change the custom export system so that it extracts the libs directly from android_release.apk and android_debug.apk, instead of requiring them included in android_source.zip. That would save some disk space too for the templates.

Are you sure this would be impossible with SCons? Can't the zip be done with a command that runs after all lib commands are done? I don't know much about SCons, so can't tell how this is done, but I would be surprised if it wasn't possible.

Are you sure this would be impossible with SCons? Can't the zip be done with a command that runs after all lib commands are done? I don't know much about SCons, so can't tell how this is done, but I would be surprised if it wasn't possible.

Yes, because currently to built the 8 libs (4 arches, release + debug), we call SCons 8 times with different android_arch and target arguments. So only the 8th SCons call should actually create the android_source.zip, if it can find out somehow that all wanted libs have been built.

I'll see if I can change the custom export system so that it extracts the libs directly from android_release.apk and android_debug.apk, instead of requiring them included in android_source.zip. That would save some disk space too for the templates.

I've done that, it seems to work well.

Amended the last commit to fix install path and permissions for the libs. Now I've tested the custom export successfully on my phone :)

@m4gr3d That does sound better, but I'm not familiar enough with the Android build pipeline to implement that myself. This PR just adds some band aid on what @reduz implemented in #27781, and I assume he also doesn't know a lot more than that on how to build things for Android in a convenient way.
If you want to make a proposal for a better workflow using aar archives, that would definitely be welcome.

@m4gr3d That does sound better, but I'm not familiar enough with the Android build pipeline to implement that myself. This PR just adds some band aid on what @reduz implemented in #27781, and I assume he also doesn't know a lot more than that on how to build things for Android in a convenient way.
If you want to make a proposal for a better workflow using aar archives, that would definitely be welcome.

@akien-mga Sounds good. I'll prepare a PR using aar archives and send it within the next couple of days for review.

@m4gr3d Awesome, thanks! I'll merge this PR nevertheless in the meantime, so that the slightly improved workflow is available in the upcoming 3.2-alpha1 in case we release it before your upcoming changes would be merged.


[MODELS] Disable GPU skinning for MacOS platform

The Apple OpenGL drivers for MacOS does not seem to support more than 8 VBOs per mesh, so the new feature to add two additional VBOs to support GPU skinning breaks all model loading on the Mac, even if the model is not animated, simply due to the fact that it tries to allocate the index buffer at ID 8
This PR disables these VBOs for the apple platform via a new #define in rlgl RL_SUPPORT_MESH_ANIMATION_VBO
This can allow us to disable the buffers for other platforms that may have the same issues, if apple is not the only vendor with this issue. I moved the optional buffers to buffer indexes 7 and 8, making the index buffer be 6, so that they can still be used on the Mac.
I have also added notes to functions and examples that say that the feature is not supported on apple platforms due to limitations in the driver.
Oh and I also added the GPU skinning example to MSVC.
I tested this by validating that Meshes did not load on a mac (2011 intel mac) before the change and do load after the change. I also validated that GPU skinning does still work on windows (Hence adding the example to MSVC projects).

This should resolve issue #4346

@JeffM2501 Thank you very much for reviewing this issue! That was a good catch! Sadly, there is always some kind of nuance with macOS... Pinging @orangeduck that probably was not aware of this macOS limitation.

Yes sadly I was not aware of this limitation :( - thanks a lot for this @JeffM2501


improvement: improve typespec on errors/2

AshPhoenix.Form.errors(@form, for_path: :all)

returns a map of errors, updated the typespec to reflect this (hopefully it's correct, it's getting pretty gnarly)

Pull Request Test Coverage Report for Build 3b5d79586922da2ad20f191f03c84d234c8cb770-PR-27

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

Totals

Change from base Build 01720f931ed5b4a2f0ab835084d98bb573675fec:
0.0%

Covered Lines:
582

Relevant Lines:
1263

💛  - Coveralls

🚀 Thank you for your contribution! 🚀


fix fix the be coredump caused by a constant in the field…

… function
Proposed changes
1、fix the be coredump caused by a constant in the field function
2、repetition
create database test;

CREATE TABLE `test01` (
  `k1` date NOT NULL,
  `k2` int(11) NULL
) ENGINE = OLAP UNIQUE KEY(`k1`) DISTRIBUTED BY HASH(`k1`) BUCKETS 1 PROPERTIES (
  "replication_allocation" = "tag.location.default: 1",
  "in_memory" = "false",
  "storage_format" = "V2",
  "disable_auto_compaction" = "false"
);

insert into test01 values ("2024-07-09",59);
insert into test01 values ("2024-07-08",130);
insert into test01 values ("2024-07-09",100);

select
    *
from
    test01
where
    k1 >= '2024-07-08'
order by
    field(1, 2, 3);

3、be stack
(gdb) bt
#0  0x000055dcfeb45f29 in doris::vectorized::FunctionFieldImpl::execute(doris::vectorized::Block&, std::vector<unsigned long, std::allocator<unsigned long> > const&, unsigned long) ()
#1  0x000055dcfeb47908 in doris::vectorized::FunctionMultiSameArgs<doris::vectorized::FunctionFieldImpl>::execute_impl(doris_udf::FunctionContext*, doris::vectorized::Block&, std::vector<unsigned long, std::allocator<unsigned long> > const&, unsigned long, unsigned long) ()
#2  0x000055dcfca4030c in doris::vectorized::PreparedFunctionImpl::execute_without_low_cardinality_columns(doris_udf::FunctionContext*, doris::vectorized::Block&, std::vector<unsigned long, std::allocator<unsigned long> > const&, unsigned long, unsigned long, bool) ()
#3  0x000055dcfca40dea in doris::vectorized::PreparedFunctionImpl::default_implementation_for_constant_arguments(doris_udf::FunctionContext*, doris::vectorized::Block&, std::vector<unsigned long, std::allocator<unsigned long> > const&, unsigned long, unsigned long, bool, bool*) ()
#4  0x000055dcfca40138 in doris::vectorized::PreparedFunctionImpl::execute_without_low_cardinality_columns(doris_udf::FunctionContext*, doris::vectorized::Block&, std::vector<unsigned long, std::allocator<unsigned long> > const&, unsigned long, unsigned long, bool) ()
#5  0x000055dcfca411c9 in doris::vectorized::PreparedFunctionImpl::execute(doris_udf::FunctionContext*, doris::vectorized::Block&, std::vector<unsigned long, std::allocator<unsigned long> > const&, unsigned long, unsigned long, bool) ()
#6  0x000055dcfb13bc94 in doris::vectorized::IFunctionBase::execute(doris_udf::FunctionContext*, doris::vectorized::Block&, std::vector<unsigned long, std::allocator<unsigned long> > const&, unsigned long, unsigned long, bool) ()
#7  0x000055dcfc1adf06 in doris::vectorized::VectorizedFnCall::execute(doris::vectorized::VExprContext*, doris::vectorized::Block*, int*) ()
#8  0x000055dcfc1b0477 in doris::vectorized::VExprContext::execute(doris::vectorized::Block*, int*) ()
#9  0x000055dcfb03cf44 in doris::vectorized::Sorter::partial_sort(doris::vectorized::Block&, doris::vectorized::Block&) ()
#10 0x000055dcfb03de4a in doris::vectorized::FullSorter::_do_sort() ()
#11 0x000055dcfb03e9c1 in doris::vectorized::FullSorter::prepare_for_read() ()
#12 0x000055dcfb0348a2 in doris::vectorized::VSortNode::open(doris::RuntimeState*) ()
#13 0x000055dcf9dbeb7f in doris::PlanFragmentExecutor::open_vectorized_internal() ()
#14 0x000055dcf9dc023e in doris::PlanFragmentExecutor::open() ()
#15 0x000055dcf9d989a0 in doris::FragmentExecState::execute() ()
#16 0x000055dcf9d9bfae in doris::FragmentMgr::_exec_actual(std::shared_ptr<doris::FragmentExecState>, std::function<void (doris::PlanFragmentExecutor*)>) ()
#17 0x000055dcf9d9c4e2 in std::_Function_handler<void (), doris::FragmentMgr::exec_plan_fragment(doris::TExecPlanFragmentParams const&, std::function<void (doris::PlanFragmentExecutor*)>)::{lambda()#1}>::_M_invoke(std::_Any_data const&) ()
#18 0x000055dcfa04bcb5 in doris::ThreadPool::dispatch_thread() ()
#19 0x000055dcfa04110f in doris::Thread::supervise_thread(void*) ()
#20 0x00007f03f1150ea5 in start_thread () from /lib64/libpthread.so.0
#21 0x00007f03f14639fd in clone () from /lib64/libc.so.6

run buildall

cherry-pick https://github.com/apache/doris/pull/25859

run buildall


Instructions for using formio.js in react-formio for bug fix ?

Hi, I am trying to test some bug fixes in formio.js and using it in react-formio. Unfortunately when importing in the react-starter-app I am getting the following error
../react-formio/lib/utils.js
Module not found: Can't resolve 'formiojs' in '~/projects/react-formio/lib'

The workflow I am using is as follows:

npm i in formio.js
npm link in formio.js
npm i in react-formio
npm link formiojs in react-formio
npm i in react-starter-app
npm link react-formio in react-starter-app

Anything that I am doing wrong or is there a different workflow to test the changes ?

I believe the issue is that you are linking from the wrong directory in formiojs. For now (we will change this in 5.x) when you link formiojs, you need to do so from the "lib" folder and not the root. When we publish to npm for formiojs, we do so from that directory.
Hope this helps.


[stable/ambassador] rbac updates for CRDs and single namespace usage

What this PR does / why we need it:
Adds a cluster role for checking if ambassador crds are defined, even if running in single namespace mode with role instead of cluster role.
Removes namespace permission when rbac is namespaced.
Which issue this PR fixes

fixes datawire/ambassador#1576
fixes #14243
fixes #13557

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
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/hold
Want to make sure this actually solves whatever use case people with single namespace has!
/assign @kflynn

PR looks sane; I’ll wait for feedback from users before doing anything else...

Perhaps we need to skip rbac-crds when rbac.namespaced: true assuming we can't create cluster roles at all in this use case. Which in the end would mean the user can't use CRDs in that setup.
You could still do ambassador in single namespace mode with cluster roles ( rbac.namespaced: false and scope.singleNamespace: true), which would allow for CRDs to be used.

Why don't we just skip rbac-crds when crds.create: false?
I could see a usecase of wanting namespaced RBAC while still wanting to use the CRD functionality. If there is some restriction against creating or giving access to anything at the cluster level, then CRDs aren't going to be desirable anyway.

@nbkrause
If you install 2 instances or more of ambassador only one of them can create the CRDs, but all of them could watch for them in their respective namespace. Ambassador requires that it can see that the CRD definitions exist, so they would need a cluster role for this.

Is there any use case where one would do
rbac.namespaced: true
scope.singleNamespace: false

Wondering if rbac.namespaced is superfluous? It makes little sense to me why one would limit ambassador to only see things in its namespace but be configured to look in all of them :)

Split the fix for #13557 to another PR https://github.com/helm/charts/pull/14604 so its not blocked :)


Correction for raw affiliation INSERM U-1111, Centre International de Recherche en Infectiologie (CIRI), Lyon, France

Correction needed for raw affiliation INSERM U-1111, Centre International de Recherche en Infectiologie (CIRI), Lyon, France
raw_affiliation_name: INSERM U-1111, Centre International de Recherche en Infectiologie (CIRI), Lyon, France
new_rors: 02vjkv261;029brtt94;059sz6q14
previous_rors: 02vjkv261;029brtt94
works_examples: W2051055899
contact: aa9807b54c99b75faeac97ec01146154:eb0fc3df30dd5f06d79328307abf @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-01. The new affiliations should be visible within the next 7 days.


PostgreSQL Hyperscale ARM Template -  no data tables in Adventureworks

Scenario which you are working on
Deploy an Azure PostgreSQL Hyperscale on AKS using an ARM Template
Describe the bug
Adventureworks sample database is deployed. However no data tables are in. There are only meta data tables respectively system tables. There should be tables like Customer, Product, SalesOrderDetail etc.
To Reproduce
Steps to reproduce the behavior:

Run all steps in Deploy an Azure PostgreSQL Hyperscale on AKS using an ARM Template

Expected behavior
Adventureworks data tables should be in the database. e.g. select distinct table_name from information_schema.columns order by 1 does not return tables of the Adventureworks database.
Screenshots

Additional context

With the latest repo update git clone https://github.com/microsoft/azure_arc.git the issue was fixed. Thank you!

Thx for the update @AlexanderTodorovic!
We are currently working on some optimizations for the data services scenarios as well as adding some features to align with the services rollouts.


Paid subscription for AppVeyor account aspnetci

AppVeyor offers $29.5 per month for open-source projects: http://www.appveyor.com/pricing.
It would be really cool if aspnetci account gets the paid subscription, so contributors don't have to wait for hours/days to get back the job results.
Also note that even with paid subscription, AppVeyor runs one job at a time per account. Meaning if aspnetci account is setup for multiple projects, 'one job at a time' rule applies globally, but it is blazing fast compared to free subscription. If you have a sponsorship, you better setup different accounts for each project. :)
More details can be gathered from @FeodorFitsner via https://github.com/appveyor/ci/issues.

I believe we do have that plan /cc @Eilon

We use the Pro FOSS plan from AppVeyor. We have a whole lot of repos, though, so even having our own queue sometimes means that builds have to wait a while.


Re-add GPSFix plugin to kinetic-devel

The GPSFix plugin had been removed from the kinetic-devel branch long
ago because the gps_common package hadn't been released into Kinetic
at the time; it exists now, so there's no reason for this plugin to
not exist.

LGTM, but I haven't tested it yet.


read-only file system

I'm not sure if this is a bug or a feature, but the tests which write to the file system don't work when I use rust-cross
# cross test --lib --target i686-unknown-linux-gnu
...
---- cmd::tests::test_fmt::test_fmt stdout ----
        thread 'cmd::tests::test_fmt::test_fmt' panicked at 'called `Result::unwrap()` on an `Err` value: Error(Io(Error { repr: Os { code: 30, message: "Read-only file system" } }), State { next_error: None })'
, /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/result.rs:868
thread 'cmd::tests::test_fmt::test_fmt' panicked at 'called `Result::unwrap()` on an `Err` value: Error(Io(Error { repr: Os { code: 30, message: "Read-only file system" } }), State { next_error: None })', /build
slave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/result.rs:868

it looks like /tmp is still allowed, which works just fine for me. My guess is that this is a feature!


flutter_tester is unable to handle engine-managed platform calls

While trying to wire up asset support for widget tests, I came across a very odd bug.
First off, I tried this very simple widget test which should fail:
void main() {
  testWidgets('Counter test', (WidgetTester tester) async {
    await tester.pumpWidget(MaterialApp(home: Image.asset('doesnt_matter')));
    await tester.pumpAndSettle();
    Finder counterButton = find.byType(Image);
    expect(counterButton, findsOneWidget);
  });
}

but it was succeeding.

Sidebar: One might argue that this should not fail but let's not get hung up on that since it has nothing to do with this issue.

At first, I thought we were doing this intentionally (swallowing asset exceptions in tester) but after tracing the code, I found out that the platform call in PlatformAssetBundle was not returning:
final ByteData asset =
        await BinaryMessages.send('flutter/assets', encoded.buffer.asByteData());

I traced this in the engine and finally found out that the posted tasks in task runner were not executing (thus the null/empty response returned by the asset manager was never making it to Dart):
void PlatformMessageResponseDart::CompleteEmpty() {
  FML_LOG(ERROR) << "CompleteEmpty";
  if (callback_.is_empty())
    return;
  FML_DCHECK(!is_complete_);
  is_complete_ = true;
  FML_LOG(ERROR) << "Posting task";
  ui_task_runner_->PostTask(
      fml::MakeCopyable([callback = std::move(callback_)]() mutable {
        FML_LOG(ERROR) << "CompleteEmptyPostTask";
        std::shared_ptr<tonic::DartState> dart_state =
            callback.dart_state().lock();
        FML_LOG(ERROR) << "Check Dart State";
        if (!dart_state)
          return;
        FML_LOG(ERROR) << "Let's Call Dart";
        tonic::DartState::Scope scope(dart_state);
        tonic::DartInvoke(callback.Release(), {Dart_Null()});
      }));
}

Output:
Shell: [ERROR:flutter/shell/common/engine.cc(430)] Calling asset manager
Shell: [ERROR:flutter/shell/common/engine.cc(433)] Done!
Shell: [ERROR:flutter/shell/common/engine.cc(440)] Sending back empty!
Shell: [ERROR:flutter/lib/ui/window/platform_message_response_dart.cc(82)] CompleteEmpty
Shell: [ERROR:flutter/lib/ui/window/platform_message_response_dart.cc(87)] Posting task

@chinmaygarde suggested a patch to make tester multi threaded: https://gist.github.com/chinmaygarde/5b1b75016869163a20879d1bf058036c but that did not help. Also it is worth reiterating that the test exits successfully with no timeouts.
Even weirder is if I put a await Future.delayed() in the test code, then I have a deadlock where the test times out no matter how short the delay is. But I see the tasks executing:
void main() {
  testWidgets('Counter test', (WidgetTester tester) async {
    /// For instance, you can pump the entire app.
    await tester.pumpWidget(MaterialApp(home: Image.asset(
       'whatever',
    )));
    await tester.pump();
    await Future.delayed(const Duration(milliseconds: 1), () {});
    Finder counterButton = find.byType(Image);
    expect(counterButton, findsOneWidget);
    print('test done');
  });
}

results in:
Shell: [ERROR:flutter/shell/common/engine.cc(430)] Calling asset manager
Shell: [ERROR:flutter/shell/common/engine.cc(433)] Done!
Shell: [ERROR:flutter/shell/common/engine.cc(440)] Sending back empty!
Shell: [ERROR:flutter/lib/ui/window/platform_message_response_dart.cc(82)] CompleteEmpty
Shell: [ERROR:flutter/lib/ui/window/platform_message_response_dart.cc(87)] Posting task
Shell: [ERROR:flutter/lib/ui/window/platform_message_response_dart.cc(90)] CompleteEmptyPostTask
Shell: [ERROR:flutter/lib/ui/window/platform_message_response_dart.cc(93)] Check Dart State
Shell: [ERROR:flutter/lib/ui/window/platform_message_response_dart.cc(96)] Let's Call Dart
Shell: [ERROR:flutter/lib/ui/window/platform_message_response_dart.cc(90)] CompleteEmptyPostTask
Shell: [ERROR:flutter/lib/ui/window/platform_message_response_dart.cc(93)] Check Dart State
Shell: [ERROR:flutter/lib/ui/window/platform_message_response_dart.cc(96)] Let's Call Dart

Again, but I don't see the Dart code executing:
 class PlatformAssetBundle extends CachingAssetBundle {
   @override
   Future<ByteData> load(String key) async {
+    print('Load key $key');
     final Uint8List encoded = utf8.encoder.convert(Uri(path: Uri.encodeFull(key)).path);
     final ByteData asset =
         await BinaryMessages.send('flutter/assets', encoded.buffer.asByteData());
+    print('Got back $asset');
     if (asset == null)
       throw FlutterError('Unable to load asset: $key');

I never managed to get "Got back null" message which I expected.

The flutter_tester process is exiting before the deferred tasks for the flutter/assets message can run.
The main function in the test Dart code has returned, and the async function passed to testWidgets is also running to completion.  At this point the ScriptCompletionTaskObserver in flutter_tester calls Dart_HasLivePorts(), which returns false.  So flutter_tester thinks there is no remaining work on behalf of the test and it terminates its message loop.
The remaining tasks on the message loop will running during termination.  But any additional work queued by those tasks (such as the task posted by PlatformMessageResponseDart::CompleteEmpty) will not run.
If you run flutter_tester with the --run-forever flag it will never terminate the message loop.  With --run-forever the CompleteEmpty queued task will run, and the Dart code will get the response and throw an exception in PlatformAssetBundle.load

Another factor affecting the timing is the test controller in the Flutter tools.
When the test controller receives notification that the test has succeeded, it explicitly kills the flutter_tester process (see https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/test/flutter_platform.dart#L490)
So even though the controller is starting flutter_tester with the --run-forever flag, the controller will probably stop flutter_tester before it has a chance to run the deferred tasks and log the asset loading exception.

Thanks for explaining. This also explains why @chinmaygarde thought this was a timing issue. Internally, we bring in optimized/release versions of flutter_tester which runs faster and is why we see that exception in our test logs. We actually run into a separate timing issue there with flaky tests because sometimes the exception bubbles up before the test gets a chance to complete and is caught by the test framework as failure. Other times, it is logged after the test passes marking it as success.

At this point the ScriptCompletionTaskObserver in flutter_tester calls Dart_HasLivePorts(), which returns false. So flutter_tester thinks there is no remaining work on behalf of the test and it terminates its message loop.

Can we do something about this to make this behavior more predictible?

The cleanest solution to this class of problems would be changing the test's implementation so that it does not finish until all the async tasks related to the test have completed.

From your comment, it is not clear. Do you expect the test framework to accommodate this? or should the user test somehow track which tasks it has spawned and wait for all those to finish?

The latter - the test function should not return until it has waited for all tasks related to the test to finish

That's pretty difficult to do for widget tests which test a high level widget. Its children may or may not load platform assets. Unless we provide a machinery in the framework (test or otherwise) to do so, I don't think that's a reasonable request and if we provide that machinery, I don't see why test framework can't do this.

Following on....
I put in a hack to see whether I can make the test wait for the Future created by the platform message.
diff --git a/packages/flutter/lib/src/services/asset_bundle.dart b/packages/flutter/lib/src/services/asset_bundle.dart
index a89b2f56d..6ae6456b2 100644
--- a/packages/flutter/lib/src/services/asset_bundle.dart
+++ b/packages/flutter/lib/src/services/asset_bundle.dart
@@ -212,11 +212,16 @@ abstract class CachingAssetBundle extends AssetBundle {

 /// An [AssetBundle] that loads resources using platform messages.
 class PlatformAssetBundle extends CachingAssetBundle {
+  static Future<ByteData> activeCall = null;
+
   @override
   Future<ByteData> load(String key) async {
+    print('Load key $key');
     final Uint8List encoded = utf8.encoder.convert(Uri(path: Uri.encodeFull(key)).path);
-    final ByteData asset =
-        await BinaryMessages.send('flutter/assets', encoded.buffer.asByteData());
+    activeCall = BinaryMessages.send('flutter/assets', encoded.buffer.asByteData());
+    final ByteData asset = await activeCall;
+    activeCall = null;
+    print('Got back $asset');
     if (asset == null)
       throw FlutterError('Unable to load asset: $key');
     return asset;

Then I await PlatformAssetBundle.activeCall; in the test defined in the first comment of this issue.
I saw the engine try to complete the call but Dart never received it and timed out (similar to what happened when I put a fake await Future.delayed).
@jason-simmons took a look at this (thank you!) and I quote:

Took a look at this.  I don't fully understand the whole story, but we should chat with @Hixie about how to build the kind of test you have in mind.  The test infrastructure is using various zone wrappers to simulate the way that the production environment would handle async tasks.
In your test, the PlatformAssetBundle.activeCall future is completing.  But when the completion microtask is scheduled, it's actually going to a FakeAsync zone wrapper instead of the engine's real microtask queue.  I'm not sure how the test is supposed to force a drain of the fake microtask queue.

To restate my two-part goal:

I want to wire up support in the tester for asset-loading widgets such that widget tests reliably fail when asset could not be loaded.
Since #1 is a "breaking change" (as in it will break lots of existing tests), I want to tests to be able to configure whether they want asset loading to be tested or not.

Even weirder is if I put a await Future.delayed() in the test code, then I have a deadlock where the test times out no matter how short the delay is. But I see the tasks executing:

This part is expected. The tests are running in a fake async zone, so time doesn't advance unless you call pump. But if you're awaiting a future, then you're not calling pump. So nothing happens.

To run an actual async task within the fake async zone, you can use runAsync.

What does asset loading in a test look like? There's no bundle to load the assets from. Or do you mean mock assets? I think that should work today without needing any real asynchrony.

Right, runAsync won't help me here either I presume since the async task being invoked isn't invoked in the test code. I am grasping this problem more now 👍
Here's the use case I am trying to solve. It also leads to a P1 goal which sits above the goals I mentioned before:
MyApp (approximate widget tree representation):
MyApp >
Scaffold >
  AppBar
  Body >
    Column >
      Image.asset('assets/my_profile.png')
      Text('My Profile')

Here's a widget test:
  testWidgets('MyApp test', (WidgetTester tester) async {
    await tester.pumpWidget(MyApp());
    await tester.pumpAndSettle();
    expect(find.byType(Text), findsOneWidget);
  });

Test has no clue that in the MyApp widget, there's a widget that tries to load an asset.
Today, everything passes even though the asset is unable to load (due to timing (Jason's guess)). Then developer defines a screendiff test:
  testWidgets('MyApp test', (WidgetTester tester) async {
    await tester.pumpWidget(MyApp());
    await tester.pumpAndSettle();
    expect(find.byType(Text), findsOneWidget);
    await expectLater(find.byType(MyApp), matchesGolden('MyApp'));
  });

The test now becomes flaky since loading the asset my_profile always fails but sometimes the test manages to finish before the failure bubbles up to test harness.
P1 goal is to make this behavior consistent and deflake the test. We should do one of the following:

Declare loading assets within the widget tester a non-goal and provide a mock PlatformAssetBundle for tests (driven by runtime context?). That means users, by design, can't rely on widget tests to make sure they are loading the assets correctly.
Fix this issue so the assets can be loaded in the tester environment provided that the engine switch --flutter-asset-path is set correctly. flutter_tester seems to wire this up: https://github.com/flutter/engine/blob/2707b7433874a8b03e4a1f7341d45b5cdcc8dfc6/shell/testing/tester_main.cc#L151 which is why I started pursuing a fix.

Mehmet and I discussed this.

We should probably support exposing the actual app asset bundle to tests in flutter test (to match the way we do to tests in flutter run). If we do this, we should probably also make the test framework hook the asset loading platform channel so that it keeps tests pending until all requests are resolved.
In the meantime, flaky tests should be updated with a DefaultAssetBundle that uses a mock asset bundle that fails everything synchronously. Search for TestAssetBundle for some examples of this.

It seems that this issue blocks internal work for me, should I assign myself here @mehmetf ?

Is this still a valid issue?
Not sure if this is the way to reproduce this issue, but I ran the first test in the OP and it fails now.
Test logs
Testing started at 11:21 ...
/Users/pedromassango/dev/Projects/flutter_personal_fork/bin/flutter --no-color test --machine --start-paused --plain-name "Counter test" test/widget_test.dart

══╡ EXCEPTION CAUGHT BY IMAGE RESOURCE SERVICE ╞════════════════════════════════════════════════════
The following assertion was thrown while resolving an image:
Unable to load asset: AssetManifest.json

When the exception was thrown, this was the stack:
#0      PlatformAssetBundle.load (package:flutter/src/services/asset_bundle.dart:225:7)
<asynchronous suspension>
#1      AssetBundle.loadString (package:flutter/src/services/asset_bundle.dart:68:33)
#2      CachingAssetBundle.loadString (package:flutter/src/services/asset_bundle.dart:167:18)
#3      CachingAssetBundle.loadStructuredData (package:flutter/src/services/asset_bundle.dart:188:5)
#4      AssetImage.obtainKey (package:flutter/src/painting/image_resolution.dart:176:18)
#5      ScrollAwareImageProvider.obtainKey (package:flutter/src/widgets/scroll_aware_image_provider.dart:113:74)
#6      ImageProvider._createErrorHandlerAndKey.<anonymous closure> (package:flutter/src/painting/image_provider.dart:455:15)
#10     ImageProvider._createErrorHandlerAndKey (package:flutter/src/painting/image_provider.dart:452:16)
#11     ImageProvider.resolve (package:flutter/src/painting/image_provider.dart:330:5)
#12     _ImageState._resolveImage (package:flutter/src/widgets/image.dart:1154:16)
#13     _ImageState.didChangeDependencies (package:flutter/src/widgets/image.dart:1107:5)
#14     StatefulElement._firstBuild (package:flutter/src/widgets/framework.dart:4814:11)
#15     ComponentElement.mount (package:flutter/src/widgets/framework.dart:4630:5)
...     Normal element mounting (132 frames)
#147    Element.inflateWidget (package:flutter/src/widgets/framework.dart:3596:14)
#148    MultiChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:6263:32)
...      See exception logs above.
The test description was: Counter test

This is a design choice of the flutter_test framework. flutter_tester itself is perfectly able to load assets.


Add additional communication mode mechanism via Nearby Messages

Is your feature request related to a problem? Please describe.
This is a react-native changes needed to accommodate https://github.com/idpass/idpass-smartshare/issues/4
Describe the solution you'd like
This is a smartshare-react-native changes needed to accommodate the changes in smartshare.aar library
Additional context
The React Native wrapper of smartshare.aar to have an option to use Nearby Message communication mode for:

Android <-> IOS communication.
Android <-> Android communication
IOS <-> IOS communication

Google Nearby Messages added to Smartshare library:
https://github.com/idpass/smartshare-react-native/tree/feature/nearby-messages
It is now possible to communicate between iOS and Android.


List collection in the parser omits sublists

Issue
When a user writes a list of ingredients or directions with a sublist, the sublist is not parsed in and is omitted in the output.
This issue was first seen in @jimbobbennett's pull request #3.
In this PR, @jimbobbennett submitted a recipe which included the instruction:
1. Whilst the condensed milk is boiling, make the pie base:

    1. Grease a pie dish with butter

    1. Put the digestive biscuits in a plastic bag and smash and roll with a rolling pin till you have fine crumbs

    1. Melt a small amount of butter in a pan and mix in the biscuit crumbs. You need enough butter for the crumbs to stick together, but not too much, so keep adding small bits of butter as needed until the crumbs start to bind.

    1. Spread the crumbs into the pie dish and press them firmly to the bottom and sides to make a pie base

    1. Put in the fridge till the butter cools and sets

The compiler did not render the indented instructions:

Root cause
The get_list_within_section function does not recursively collect items. It only checks the first set of children within a list and returns the strings. Source
Possible solutions
Instead of returning a list of strings, the parser should return a list of nodes which may be leafs or have children. No new class should be needed, the existing Node class in the marko package will do the job just fine.
The Recipe class will need to be changed such that the ingredients and instructions attributes are lists of Node instead of str.
The render_recipe_page will need to be changed to render HTML from the markdown nodes before being passed to the Jinja template.

This will also be fixed with the solution proposed in issue #7.


Update docs and carousel example for order-.

Will do thanks. I was trying to get it quickly to work.
On Jul 20, 2017 21:48, "Mark Otto"<EMAIL_ADDRESS>wrote:

@mdo commented on this pull request.
In docs/4.0/utilities/flex.md
https://github.com/twbs/bootstrap/pull/23130#discussion_r128599617:

{% endexample %}
Responsive variations also exist for order.
{% for bp in site.data.breakpoints %}
-- .order{{ bp.abbr }}-first
-- .order{{ bp.abbr }}-last
-- .order{{ bp.abbr }}-0{% endfor %}
+- .order{{ bp.abbr }}-1
You might be able to make this more succinct with some Liquid iteration:
{% for bp in site.data.breakpoints %}
{% for i in (1..12) %}
.order{{ bp.abbr }}-{{ i }}
{% endfor %}
{% endfor %}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/twbs/bootstrap/pull/23130#pullrequestreview-51295264,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVVtT1Ybzg6-AnWGZkrW1IZlkYgG4WJks5sP6DugaJpZM4OePZS
.

So, can we merge this? Without this, the info on docs will be wrong.


Missing/Incorrect mesh material

Screenshots
Expected behaviour (last working on dd1dc106cb713b4182a15eaf758e2ba98bcdefc5)

Current behaviour (from 0eee0da6c5220f1e97719b4568c94788f9ba56c5 onwards)

Reproducible Code
using Colors
using MeshCat
using Polyhedra
using QHull

vis = Visualizer()
open(vis)

v1 = [1 1 1 1 0 0 0 0
      1 1 0 0 1 1 0 0
      1 0 1 0 1 0 1 0.]'

p1 = polyhedron(vrep(v1), QHull.Library())

m1 = Polyhedra.Mesh(p1)

material = MeshPhongMaterial(color=RGBA(1, 1, 1, 1))

setobject!(vis[:m1], m1, material)

I am using https://github.com/rdeits/MeshCat.jl (master branch d1bec32) and setting the meshcat version to be used in https://github.com/rdeits/MeshCat.jl/blob/master/deps/build.jl#L5.
I incorrectly opened an issue in https://github.com/JuliaPolyhedra/Polyhedra.jl/issues/180 concerning this.

Thanks for the bug report! I've just fixed this on the javascript side, and I'll include it with the next MeshCat.jl release.

Thanks, Robin! :smiley:


AuthUser is not updating when using plain javascript for Auth.

Describe the bug
I'm not using Firebase UI, i'm using vanilla javascript to sign in user (via phone auth), so when the user is signed in, I can confirm it in  firebase.auth().currentUser, but the useAuthUser() is not returning the user nor I can see a api request to login, as this is supposed to be done automatically when user's logs in.
confirmResult.confirm(otp.current.value).then((result) => {
    console.log(firebase,auth().currentUser); //this shows me user is logged successfully
}

useAuthUser() returns this:
AuthUser
{id: null, email: null, emailVerified: false, claims: {…}, getIdToken: ƒ, …}
claims: {}
clientInitialized: false
email: null
emailVerified: false
firebaseUser: null
getIdToken: ƒ ()
id: null
serialize: ƒ ()
signOut: ƒ ()
[[Prototype]]: Object

Version
0.13.1-alpha.0"
To Reproduce
Steps to reproduce the behavior:

Follow the steps for vanilla javascript phone auth -

const AuthUser = useAuthUser()
  useEffect(() => {
    console.log("AuthUser", AuthUser);
    //not changed even when user is logged
  }, [AuthUser])

Expected behavior
Automatically update AuthUser when user is logged

Yes ofcourse I was using it in functional component, I realised i didn't export my component with withAuthUser()(Component) . Do you think an error message could be displayed if someone uses useAuthUser while not exporting component with withAuthUser. That'd be better.  :)

That makes sense. Opened #155

Ill second this, I think bit more clarity could have been added to the docs to "include the withAuthUser" for sign in so that the session is set correctly.