Spreadsheet scripts not working for lat / lng

Both the scripts for lat lng have stopped working. the original one on 'lat/lng' is just saying "automated lookup failed" and Jesse's script (on the "latitude" and longitude columns) isn't resolving the addresses either, but it will copy the values over if you manually enter in lat/lng

the old script might have exceeded calls, but Jesse's script isn't resolving addresses either, so It could be a google problem


[BUG] Volumes bounded on a deleted VM and unable to be removed

Describe the bug
https://user-images.githubusercontent.com/5169694/185370936-e07979ed-0079-4754-b2d0-bcb9872a5ebe.mp4
It discovered by daily e2e testing.
To Reproduce
Steps to reproduce the behavior:

Install Harvester with any nodes
Create a Image for VM creation
Create the VM vm1 via API endpoint: https://<CLUSTER_VIP>/apis/kubevirt.io/v1/namespaces/default/virtualmachines (POST method)
Delete the VM vm1 and volumes simultaneously. (DELETE method)

VM's API endpoint: https://<CLUSTER_VIP>/apis/kubevirt.io/v1/namespaces/default/virtualmachines/<VM_NAME>
Volume's API endpoint: https://<CLUSTER_VIP>/api/v1/namespaces/default/persistentvolumeclaims/<VOLUME_NAME>

Expected behavior
Volumes should able to be removed
Environment:

Harvester ISO version: v1.0.3
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): Baremetal DL360 4 nodes

Additional context
Dashboard's operation will NOT encountered this.
The issue can be reproduced by running test_create_vm_do_not_start e2e tests several times.

@lanfon72 I guess this is expected since the volume is still used.
If this blocks some QA tests, perhaps it's better to use calls like:
DELETE /v1/harvester/kubevirt.io.virtualmachines/default/test-vm-1?removedDisks=disk-0

Or add some code to wait for the volume to be unbound.

@bk201 Volumes attached VM has been removed, but volumes still here and can not be delete.
this is not always reproduced, and only happened when the VM create and delete simultaneously.

I have seen this also when using the terraform provider for Harvester to create and then destroy VMs..

The owner annotation in volume is not removed. Some investigation:
harvester-lzxcs:~ # kubectl get pvc
NAME                                            STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                                AGE
025fb39222fd4514a21bf7deeb438af6-disk-0-iok9h   Bound    pvc-50fd54b4-eadb-41b5-a030-8d3f1b938a71   10Gi       RWX            longhorn-2e5b1ca509ce4c96a3570bac0aac2d4d   6d23h
025fb39222fd4514a21bf7deeb438af6-disk-1-4xe1k   Bound    pvc-31218042-2e0b-458a-925e-a95b3328d1ff   10Gi       RWX            longhorn                                    6d23h
5d10e6b574f34bbdb52f00a730c58cd4-disk-0-exno6   Bound    pvc-2e6d0f86-96ff-4fdd-ab5d-ecff10dc56e6   10Gi       RWX            longhorn-15aee8028e514ed5b49d769b0e02f522   6d22h
5d10e6b574f34bbdb52f00a730c58cd4-disk-1-pxrdc   Bound    pvc-264048e8-d662-499e-9cb5-fb47f5e4f7e4   10Gi       RWX            longhorn                                    6d22h
c8220e2392b94b879ee27f5ea0eb0d16-disk-0-3kv8w   Bound    pvc-950e2d3f-b875-409f-bff7-f344abaa6cdf   10Gi       RWX            longhorn-4100e9d817354144833414fbaafc8c50   20h
c8220e2392b94b879ee27f5ea0eb0d16-disk-1-8npwc   Bound    pvc-ba1772a0-7314-4036-976c-ad7c7f3bfa4d   10Gi       RWX            longhorn                                    20h
s1-disk-0-sg2ma                                 Bound    pvc-381d8765-191b-4c93-9f67-3703c767074a   10Gi       RWX            longhorn-image-h4zks                        13d

From Harvester log:
# grep c8220e harvester-797b59b958-6swcz.log
time="2022-08-24T12:21:46Z" level=error msg="error syncing 'default/c8220e2392b94b879ee27f5ea0eb0d16': handler VMController.UnsetOwnerOfPVCs: Operation cannot be fulfilled on virtualmachines.kubevirt.io \"c8220e2392b94b879ee27f5ea0eb0d16\": StorageError: invalid object, Code: 4, Key: /registry/kubevirt.io/virtualmachines/default/c8220e2392b94b879ee27f5ea0eb0d16, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 93904e3a-e82c-495d-b5b1-65601cd735a2, UID in object meta: , requeuing"

QA manually deletes stale volume pvc-31218042-2e0b-458a-925e-a95b3328d1ff from LH GUI, stuck in deleting. log in longhorn-manager
time="2022-08-25T08:32:02Z" level=warning msg="Dropping Longhorn volume longhorn-system/pvc-31218042-2e0b-458a-925e-a95b3328d1ff out of the queue" controller=longhorn-volume error="fail to sync longhorn-system/pvc-31218042-2e0b-458a-925e-a95b3328d1ff: admission webhook \"validator.harvesterhci.io\" denied the request: can not delete the volume 025fb39222fd4514a21bf7deeb438af6-disk-1-4xe1k which is currently attached to VMs: default/025fb39222fd4514a21bf7deeb438af6" node=harvester-lzxcs

harvester-797b59b958-6swcz.log
supportbundle_2df6b5dc-0664-42d3-85e2-9b151792a654_2022-08-25T08-20-16Z 2.zip (drop some files to reduce size)

This is still reproducible in v1.1.1 master.

backport PR #3480 not merge yet.

Can we please test the following case:

Create a v1.1.1 harvester cluster
launch a VM
upgrade cluster to v1.1.2-rc1
delete the VM
VM should get deleted

@ibrokethecloud I think we can just verify this will not happen on v1.1.2-rc1 which upgraded from v1.1.1, because it is not always reproducible.
And we can also test the case that reproduced on v1.1.1 and upgrade to v1.1.2-rc1, then volumes should able to be deleted successfully.

Close as resolved, reproduced on v1.1-a002d078-head 100 times, not encountered this.
Test Information

Environment: qemu/KVM 2 nodes
Harvester Version: v1.1-a002d078-head
ui-source Option: Auto

Verify Steps:

Install Harvester with any nodes
Clone https://github.com/harvester/tests#run_tests and setup the test environment and config.yml
Execute pytest harvester_e2e_tests/ -vvvk "test_create_vm_do_not_start" several times


Add count distinct measure

Closes #163

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


R 101 Python Program added

R 101 is already added @dharsan19, please pull from the head branch.

Yes @VikashPR , But the program added is in python

Yes @VikashPR , But the program added is in python

Got it, then please remove the existing java code and add your python code


Adding save to HF support for async webcrawler

This pull request addresses https://github.com/unclecode/crawl4ai/issues/257. It introduces a persistence strategy layer to the project, allowing for more flexible data storage options.
Key changes:

Added an abstract DataPersistenceStrategy class for defining various persistence strategies.
Implemented HFDataPersistenceStrategy, a concrete strategy for pushing data to a Hugging Face dataset.
With this update, data extracted via the crawl process can now be seamlessly uploaded to the Hugging Face Hub as datasets, enhancing data sharing and accessibility.
Once this PR is adopted by the community, it will be easy to filter all datasets created using the crawl4ai library by visiting https://huggingface.co/datasets?other=crawl4ai

@AndreaFrancis A supernova thanks to your pull request! What excites me most is how beautifully it aligns with the library's design philosophy. Amazing work! I’ll review it soon, run some tests, and it’ll be my pleasure to merge it.  I’d love to invite you to our Discord, please share your email, and I’ll send over the invitation link.

@AndreaFrancis You are very welcome, looking forward to having talented developers and data scientists like yourself in the Crawl4ai community; we work together and form the no. 1 data extraction open source library in favor of data liberty. I will send the invitation link.


Document option 'wlp' for the include param of create-server mojo

If you want to package the liberty runtime, it is possible to do so by specifying 'wlp' as include. See https://www.ibm.com/support/knowledgecenter/was_beta_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/twlp_setup_package_server.html.
The documentation of the include param (create-server mojo) should be updated with this option. Also, it would be good with a config example for doing this.

This has been delivered to the 2.0-SNAPSHOT.


Action does not complete following time sync

Fixed by https://github.com/codyc1515/ha-yeelock/commit/c0ad89f3efaab26cbe3cf3de77cb65d6364b9b5c


ZipList. Tuple monoid/monad/functor/applicative

Codecov Report

Merging #3 (faa2d00) into main (a72736b) will increase coverage by 0.23%.
The diff coverage is 74.35%.

@@            Coverage Diff             @@
##             main       #3      +/-   ##
==========================================
+ Coverage   79.70%   79.93%   +0.23%
==========================================
  Files           1        1
  Lines         601      648      +47
  Branches      125      136      +11
==========================================
+ Hits          479      518      +39
  Misses         13       13
- Partials      109      117       +8

Impacted Files
Coverage Δ

include/hspp.h
79.93% <74.35%> (+0.23%)
:arrow_up:

Continue to review full report at Codecov.

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


modules

first the two mendatory modules, which are openssl and php modules

i will take in charge openssl as it is a part of the network implementation.

@polosskevin still hasn't started to focus on the projet, I'm finishing another project and will try to look into this asap, should start this weekend

@polosskevin If you hande the SSL module, the second one to handle is PHP, and we are two. Which module you wanna see implemented in third ?

You can propose one, we're not limited to 2. Providing a list of possible module could be a good solution.

@polosskevin I'm on module_dumpio which is a logger
https://httpd.apache.org/docs/2.4/mod/mod_dumpio.html


Feature Request: start recording without location.

Allow log recording without knowing the Geo location of the device.
I can't disclose my client's offices, but I sure would like to discretely log the levels and tip off the engineering teams. I would not want to habe their data in a public cloud for searches.  Nor my own home to be honest.
Is this related to "No locations in range". I don't really understand what that means.  Without a location registered, the app won't allow recording, though I am not sure of that. What I mean to say is the Start Recording button is dark/ghosted?  Or it it is not ghosted, clicking it has no effect, nor is there a tool tip saying why it can't be clicked.
Could be this is a bug not a feature, so I'd be happy to give a fuller bug report in a new issue #

Start Recording being greyed out if no Location is selected is by design - if the location is not showing up there, there is the manual recording option as alternative. However in your usecase, as you want it completely without geolocation, I think just using the official App and exporting or screenshoting the History should do the job? This App really is about matching the data to locations.


V1.2.3

The issue https://github.com/microsoft/azure-pipelines-tasks/issues/15487 is preventing this PR to pass checks.


Hourly key reward (playtime)

Hi how can I add like hour key reward ? I mean player get's key automaticlly every hour. Any ideas how to fix it ? Whenever I tried it by myself it ended with message like Given key to offline %player%. Or @p....

Hello Billyxxdd,
This shouldn't be an issue. Even when giving keys to players who are offline, it adds them to their virtual key balance. How are you giving out the keys to players? I'm assuming some kind of playtime tracking plugin.
Please reach out if you have any questions on discord or reply to this comment here.
Thanks,
Eva (Discord Administrator)


Add gentx for Orangeclub

Any ideas what is wrong? :D

Any ideas what is wrong? :D

We are testing Github Actions. We'll let you know if there's any issue with your submission. Looks good to me

@Vasya-kripto is it possible for you to close this PR and open another PR to test the integration?


Gradle should fail early when attempting to publish an artifact with invalid dependency coordinates

Current Behavior
When publishing a maven lib based on a Gradle project into the local maven repository creates faulty *.pom and *.module files within that repository (invalid Java FX lib dependencies).
The created dependency cannot be used by other Gradle projects, unless the *.pom and *.module file are manually corrected in the maven repository by deleting the faulty dependencies. The Gradle project that wants to use the dependency, cannot be built:

Working Directory: /Users/Mike/Development/git/repository/autumo-documents-ui
Gradle user home: /Users/Mike/.gradle
Gradle Distribution: Specific Gradle version 8.4
Gradle Version: 8.4
Java Home: /Library/Java/JavaVirtualMachines/jdk-17.0.2.jdk/Contents/Home
JVM Arguments: None
Program Arguments: None
Build Scans Enabled: false
Offline Mode Enabled: false
Gradle Tasks: run

> Task :compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> Could not resolve all files for configuration ':compileClasspath'.
   > Could not resolve ch.autumo.commons:autumo-ui:1.0.0.
     Required by:
         project :
      > Could not resolve ch.autumo.commons:autumo-ui:1.0.0.
         > Could not parse POM /Users/Mike/.m2/repository/ch/autumo/commons/autumo-ui/1.0.0/autumo-ui-1.0.0.pom
            > Missing required attribute: dependency groupId

Workaround:

Delete all dependency entries related to Java FX modules in  POM and MODULE file in the local maven repository where the library project has been published

Attachments:

Invalid POM and MODULE file
Gradle build script for Java FX library that is used by another project

autumo-ui-1.0.0.module.TXT
autumo-ui-1.0.0.pom.TXT
build.gradle.TXT
Expected Behavior
Valid dependency entries within the published "lib-name-x.y.z.pom" an "lib-name-x.y.z.module" in the local maven repository, that can be used as a valid dependency by other gradle projects.
Context (optional)
I try to use a a published (local maven repository) Java FX Gradle library JAR from another Gradle project as a dependency. So the goal is proper Java FX/Gradle modularisation in development.
Steps to Reproduce

Use a similar Gradle build script as provided in the attachments and publish the built JAR into local maven repository
Create a Gradle project that will use that that JAR as a dependency
Built the project, it fails with the behaviour explained above

Gradle version
8.4
Build scan URL (optional)
No response
Your Environment (optional)
Gradle user home: /Users/Mike/.gradle
Gradle Distribution: Specific Gradle version 8.4
Gradle Version: 8.4
Java Home: /Library/Java/JavaVirtualMachines/jdk-17.0.2.jdk/Contents/Home
Java Release Option fo code compatibility: Java 1.8 (8)
OS: macOS Ventura
Development IDE: Eclipse and Gradle CLI (Same behaviour in Eclipse and CLI)

Sorry that you're having trouble with Gradle!
Most probably your issue is caused by an external plugin, which cannot be addressed in the Gradle Build Tool project.
We recommend you open an issue on its issue tracker.
We have some integration tests with major plugins to catch potential problems early, but we don't have the capacity to cover all plugins available.
If you think you have come across a Gradle bug, please provide a reproducer for this issue and we’ll consider reopening it.

Java FX plugin creates dependencies on Java FX modules without a group id and it results in dependencies like this:
{
        "group": null,
        "module": "javafx.base"
      },

So it should be fixed in the plugin.
However, Gradle should fail sooner - at the publication time, so we leave this issue open.

Thanks for your answer! Would it possibly help, if you get the plugin list from me?

Sorry, I don’t follow. Why do you think this list should be useful in the context of implementing the fail fast approach here?

Because you said that the problem is most likely connected to an external plugin, so I thought a plugin-list of my IDE could be helpful. But it doesn't matter, because I solved the problem:
The problem lies in the Gradle-script itself:
For the "build" I have to remove the Java-FX-SDK-path fully from the script and add proper dependencies:
javafx {     version = "19"     modules = [ 'javafx.controls', 'javafx.fxml', 'javafx.web' ]     // **This here must be removed**:     //sdk = '/Users/Mike/Library/Java/javafx-sdk-19' } dependencies { 	implementation "org.openjfx:javafx-controls:19" 	implementation "org.openjfx:javafx-fxml:19" 	implementation "org.openjfx:javafx-web:19"         ....

Sorry for the confusion. I meant Gradle plugins, not Idea plugins.

No worries, thank you for the hint, it works now how it should. PS: I am still an Eclipse guys :)

Resolved a described above.


Add documentation for new contributors

This PR is intended to help others (e.g. @rly) get oriented in the NWB GUIDE repo. Based on additional suggestions, we can easily add/remove content to help intended contributors.

Looks great, thanks for condensing everything so nicely


Fix: top command abnormal render

Description of your changes
Related issues:

https://github.com/derailed/k9s/issues/448
https://github.com/gdamore/tcell/issues/203
https://github.com/rivo/tview/issues/118

But I'm not sure if this can solve #6076
I have:

[ ] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

/cc @Hanmengnan


set label refactor

refactor set-labels function using go/sdk instead of kyaml.

@zyy98 Some general suggestion to make this PR in good shape without compromising test coverage:

Let's make the minimum change to ./tests, some tests may have duplicate coverage like additional-labels and both-additionalLabelFields-fieldSpecs. It's fine for now. Those tests are just to help us guarantee the refactoring does not break the UI (except additionalFieldSpec).

We need some more tests in ./tests:

If the input resources.yaml does not have any KRM resources
If the input contains wrong functionConfig Group or Kind name (for SetLabel)
If the input FunctionConfig contains wrong Data type, e.g. it's not a string map but a string struct or a slice, etc (for ConfigMap)

Overall it looks much better! Good job @zyy98  leave several minor comments.


Robust Graph Hashing

We currently use the base julia hash, which becomes very susceptible to collisions if used on graphs with more than 8192 vertices (see here).
See also discussion here.
We need to switch to a more robust hash, at least for large graphs.

The main issue is fixed (#7). Leave this open until the collision behavior is investigated more carefully.


Use ca-certs library

According to https://github.com/mirage/ca-certs/issues/6, ca-certs is going to opam.
Delete

https://github.com/oxidizing/letters/blob/master/lib/ca_certs.ml
https://github.com/oxidizing/letters/blob/master/lib/ca_certs.mli

, install ca_certs and use Ca_certs.trust_anchor_filename.

Done


Fixing Task Reassignment Status Update Issue

Closes

#1336

At present, when a task is reassigned, only the new assignee's status is updated. However, if the task was previously pre-assigned, the old assignee's status remains unchanged. This could be considered a loophole, as someone might take a task and then reassign it to another person, keeping their status perpetually active.
This pull request addresses the mentioned issue. Upon task reassignment, the status of the old assignee, if present, will be updated accordingly.
This PR contains both the code changes as well as the Tests.
Testing Stats:
Utils :

Controller:

Please mention other PR related details like DB changes and all.....


Support for build env

As per docs, we can specify the environment variables in the oc-new command. So this feature should be present in oc-new-app in the form of an input.

resolved in #17


BUG: Noteskin is retained in chart editor from previous song if Shift + Enter into song

Describe your bug here. Mind you, if you are modding, please try testing your bug in a clean version of the engine instead, this ensures the bug is actually caused by the engine itself. Also, if you're using an older version of JSE, please try the latest action build in the Actions tab or the latest release build. The issue has probably been fixed since that version. Oh yeah, and also be sure to check the pinned 'JS Engine: Known Issues' issue, to double check if your issue hasn't already been found!

In the latest commit, shift entering from a song with a different noteskin (week 6 demonstrated) will keep it and make the notes invisible apart from sustains
Command Prompt/Terminal/Crash logs (if existing)
No response
Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
None.
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
No
Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.
Yes

erm actually, if you enter a week 6 song and go to the chart editor it duplicates the behavior.
this is because normal note loading works differently from the week 6 note loading


Improve terminal action hover UI

Improve description when only one terminal is opened:

Ideally it should be the same as:

Also, use markdown for process description:

Third UI issue:
Originally posted by @amunger in https://github.com/microsoft/vscode-python/issues/21129#issuecomment-1522479376
also you can tell that I struggled a bit to actually click the actions in the dialog

1 Improve description when only one terminal is opened:

https://github.com/microsoft/vscode/issues/177774

2 We should probably use markdown backticks for process description:

It was originally styled like that but it was much too large and less readable considering the default shell integration injection command line.

also you can tell that I struggled a bit to actually click the actions in the dialog

https://github.com/microsoft/vscode/issues/162336

It was originally styled like that but it was much too large and less readable considering the default shell integration injection command line.

Maybe not for the whole command line but atleast for the file paths I think using backticks makes it more readable.

Args could be paths too though and the default Windows profile can be really huge:


Hope to support virtual threads, or provide an interface that can rewrite the thread pool

Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Describe alternatives you've considered

Can you clarify which thread pool you need to rewrite?

It's done.
Below is the code example.
Config c = redisson.getConfig();
c.setNettyExecutor(Executors.newVirtualThreadPerTaskExecutor());

RedissonClient r = Redisson.create(c);


Partial ordering of module selectors

we do a partial sort on the selectors, where we place
the dynamic selectors at the end compared to the other ones.
This allows a more efficient resolution in some cases.
One such case is when using constraints, as resolving the selector happened before the constraint was really accounted for in the graph. Now these constraints get resolved at the same time, reducing the number of potential version changes for a given dependency.
This is particularly impactful when using dependency locking as this means there is a strict constraint for each dependency in the graph.

Performance test indicate that this scheme has a clear benefit for locking use cases. Other perf test sometimes show a minor impact.
So unless there is a technical reason to not do this change, even if it creates a small regression in performance, the gains on the other side are worth doing the change.


torch 2.0.1,  met some problem in function accuracy() and solved

line 18
the function view() has some problem when calculating topk=5
RuntimeError: view size is not compatible with input tensor's size and stride (at least one dimension spans across two contiguous subspaces).
the instruction may solve this problem
correct_k = correct[:k].view(-1).float().sum(0) changed to correct_k = correct[:k].float().sum()

sorry, this  issues is for mobilenetv2


WebApp - Add content in case search haven't result

Describe the bug
To reproduce the bug

[x] Select account
[x] Select token
[x] Select address book
[x] ....

Steps:

Go to Select token screen
Input token not exist
Observe the displayed screen

Actual: Show blank screen

Version test : https://7def5afc.subwallet-webapp.pages.dev/
Validation passed in cases:

Select account

Select token

Select address book

....

Version test : https://7def5afc.subwallet-webapp.pages.dev/

[ ] Button Transfer on Transfer screen
[ ] Button Buy now on Buy token screen

Expected result : The button's location is near the fields
Actual result : The button's position is far away from the fields

Version test : https://8784840b.subwallet-webapp.pages.dev/
Validation passed


ci: Remove epoch_finish timestamp from release & Update actions

This PR contains:

[x] The removal of epoch_finish timestamp from the release (tag, release title, release body) (as discussed in #146).
[x] Update @actions/upload-artifact and @actions/download-artifact to v4 (so Node.js 20 will be used as Node.js 16 used in v3 is deprecated).
[x] @actions/checkout to v4 (so Node.js 20 will be used as Node.js 16 used in v3 is deprecated).

Now ready for review, the test release coming with these changes is here.
P.S.: 121.0.6167.139-1 is coming, I'll work on it this weekend.

@claudiodekker You might be interested in knowing these changes in advance so you can prepare for it on your end. This one will stay here for a longer time :D

@Cubik65536 Ha, thanks for the heads-up! I already saw it but when I did it was still in WIP/Draft state.

@actions/checkout to v4 (so Node.js 20 will be used as Node.js 16 used in v3 is deprecated).

Would it make sense to adopt Dependabot to bump this kind of things automatically in the future?

@PF4Public I wouldn't. Typically these constitute "major" version changes, meaning that options can change. Github's pretty stable in that sense with most of these actions, but I've seen certain options/flag change in the past.

@claudiodekker Well, I should've written "semi-automatic" :) Dependabot only creates PRs with changes, here are examples: https://github.com/nodejs/node/pulls/app%2Fdependabot

@PF4Public Ah, right, yeah I misunderstood. I thought you meant doing something like this to auto-merge patch-level changes: https://github.com/claudiodekker/word-generator/blob/master/.github/workflows/dependabot-auto-merge.yml

@actions/checkout to v4 (so Node.js 20 will be used as Node.js 16 used in v3 is deprecated).

Would it make sense to adopt Dependabot to bump this kind of things automatically in the future?

We could, but it's not necessary. Sometimes even the new major version doesn't change any option, it's not suitable for us to update (that's why my last CI change PR didn't update to v4s, all the options are the same, an internal change broke everything). I'd suggest that we stay to the manual update so we can just update when really needed.

P.S.: An update to 121.0.6167.139 is included now in the PR.

I'll just merge it.

@claudiodekker Do you have some knowledge on Homebrew Cask? Our brew cask code also has to be updated so Homebrew would work with the new tag format. Wondering if you can help me do that because I will be a little busy for the next few days and may not be able to do that quickly.

@Cubik65536 Yeah, sure, where can I find the code for this?

@Cubik65536 Yeah, sure, where can I find the code for this?

You can find it here: https://github.com/Homebrew/homebrew-cask/blob/master/Casks/e/eloston-chromium.rb

You will need to change the livecheck section. Don't touch the version and sha256 info unless there's already a finished build here. /cc @claudiodekker
Thanks a lot! You saved my life 🤣

By the way, just a note here, according to this GitHub blog article, we can now use ARM machine to run our CI, and I do plan to migrate our arm building to this later (avoid the cross compiling will save a lot of time).

@Cubik65536 Got an update ready (& tested against your "test" repository). As it turns out, the livecheck regex itself was already tolerant to timestamp-less version tags, so there was little work to do there.
I did however also take the opportunity to clean up some of the cask definition and fix a brew audit issue, so all that's left now is to wait for the build to finish, and submit the PR with the up-to-date hashes, but you can rely on me to do that tomorrow once the build finishes 👍
If you're interested in my changes though, here's the commit: https://github.com/claudiodekker/homebrew-cask/commit/fabbbfcee945b1bdd2d2ff01f0ac1a22e52cc574

@Cubik65536 Got an update ready (& verified against your "test" repository). As it turns out, the livecheck regex itself was already tolerant to timestamp-less version tags, so there was little work to do there.
I did however also take the opportunity to clean up some of the cask definition and fix a brew audit issue, so all that's left now is to wait for the build to finish, and submit the PR with the up-to-date hashes, but you can rely on me to do that tomorrow once the build finishes 👍
If you're interested in my changes though, here's the commit: claudiodekker/homebrew-cask@fabbbfc

Your changes look good! Thank you!

@Cubik65536 Cask changes have been PR'd: https://github.com/Homebrew/homebrew-cask/pull/165983


Update README.md

Changed default tensorboard port to reflect https://github.com/openai/universe-starter-agent/pull/18
added libgcc to dependencies.
re-worded tmux instructions to avoid confusion

Closing: tensorboard is now on port 12345


Update HasRoleAndPermission.php

hasRole and permission works with $key not $value

hasRole and permission works with $key not $value


Fix reactOnRailsPageUnloaded when there is no component on the page

In reactOnRailsPageLoaded, if we finds no react component, the function return  and context.roots is not initialized. This cause findContext().roots in reactOnRailsPageUnloaded to be undefined, and for .. of throws an exception.
This should mostly affect app using both hotwire and react_on_rails, as the recommended way to load js is to do the same file everywhere, otherwise the issue can be avoided by just not loading react_on_rails

This change is

Nice, I actually hit this while I was trying react_on_rails a couple days ago. It made me think it was unstable so decided not to use it.

@NhanHo can you please add a CHANGELOG entry?
I'll merge as soon as this passes CI.

@justin808 I fixed the linter issue and added changelog. If you decide to merge the other PR, you can close this one.
Thanks a lot for your work on Shakapacker and related projects.

@NhanHo Please merge https://github.com/shakacode/react_on_rails/pull/1499/files into your branch and I'll merge.

@justin808 Updated

Thanks @NhanHo!


[New Port Request]

Library name:coz
Library description:causual profiler
Source repository URL: https://github.com/plasma-umass/coz
Project homepage (if different from the source repository):
Anything else that is useful to know when adding (such as optional features the library may have that should be included):

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now, consider making a pull request instead.


Runtime type

Note: this builds on #4606. Only the last commit belongs to this PR.
This adds a runtime_type enum that can be passed in the init_params struct, to choose which runtime to start. If the distributed runtime isn't enabled and it's requested an exception will be thrown during init. The default is to use the distributed runtime if available and otherwise the local one.

Previously we discussed to extend the runtime_mode enum instead of introducing yet another enum type. Would this make sense or is it preferrable to have those separated?

I don't remember the context, but if I made that statement it may have been because I didn't understand runtime_mode properly. I think the two enums are mostly orthogonal, except for the fact that with runtime_type_local the runtime_mode doesn't make a difference.

Previously we discussed to extend the runtime_mode enum instead of introducing yet another enum type. Would this make sense or is it preferrable to have those separated?

I don't remember the context, but if I made that statement it may have been because I didn't understand runtime_mode properly. I think the two enums are mostly orthogonal, except for the fact that with runtime_type_local the runtime_mode doesn't make a difference.

Playing devils advocate here... Wouldn't that mean that adding runtime_mode::local to the runtime_mode enumeration is sufficient? The existing enum values simply imply distributed operation.

Previously we discussed to extend the runtime_mode enum instead of introducing yet another enum type. Would this make sense or is it preferrable to have those separated?

For the record, we discussed this here: #4127

My memory... thanks @hkaiser. You're absolutely right about extending runtime_mode. It's much simpler to do that instead.

I just pushed some changes but have not tested them properly yet. I'll be back at this one...

If we go with class enums, should we again gradually phase out the unscoped enums? Is there a good convention for doing this kind of compatibility? I can think of two ways:
enum class runtime_mode {
    console = 0,
    // ...
    #if compatibility
    runtime_mode_console = console,
    // ...
    #endif
}

#if compatibility
using enum runtime_mode;
#endif

but this is likely to introduce name conflicts.
The other would be:
enum class runtime_mode {
    console = 0,
    // ...
}

#if compatibility
static constexpr runtime_mode runtime_mode_console = runtime_mode::console;
// ...
#endif

I guess we wouldn't break too many people's code with the runtime mode since that's almost always default or specified on the command line. The partitioner mode is another one which probably has few users. If we're going all in with this there are definitely other enums that would break user code by becoming class enums.

enum class runtime_mode {
    console = 0,
    // ...
}

#if compatibility
static constexpr runtime_mode runtime_mode_console = runtime_mode::console;
// ...
#endif

This is the way to go, I think.

@hkaiser I changed runtime_mode to be an enum class, but I added a generic compatibility option for unscoped enum compatibility. I suggest we use that one for all enums that need to be changed, and remove the option in 2.0.0. I'll try to change some other enums before 1.5.0 as well.

https://cdash.cscs.ch//testDetails.php?test=21992139&build=109075 seems to be unrelated (I've seen it on other PRs now as well). Seems like either the stacksize test or stacksize handling is still not quite fixed. I'm reopening #4648 as a reminder to look at it again.


Show Detail Page

[x] Mobile Styles
[ ] Action buttons narrow view

Mobile and desktop views now


Rq Integration does not seem to capture exceptions when initiated in Flask app. (Question)

This is sort of what my app.py looks like. The entire code is found here
Exceptions raised in flask in the /error route are caught by sentry, but the errors raised in broken_function after I enqueue it in the route /enqueue do not seem to get caught.
Will I have to initialize it separately for each, or am I doing something wrong which is most likely the case.
app.py
import sentry_sdk
from sentry_sdk.integrations.rq import RqIntegration
from sentry_sdk.integrations.flask import FlaskIntegration

sentry_sdk.init(os.environ['SENTRY_DSN'], integrations=[FlaskIntegration(), RqIntegration()])

app = Flask(__name__)

@app.route('/')
def hello_world():
    return 'Hello, World!'

@app.route('/error')
def error():
    return 1/0    #Works and is caught by sentry

@app.route('/enqueue')
def enqueue():
    q = Queue(connection=Redis())
    result = q.enqueue(broken_function, "Error within RQ job.")   #does not work

worker.py
from rq import Connection, Worker, Queue

with Connection():
	worker = Worker(map(Queue, ['default']))
	worker.work()

pip freeze
blinker==1.4
certifi==2020.6.20
click==7.1.2
Flask==1.1.2
itsdangerous==1.1.0
Jinja2==2.11.2
MarkupSafe==1.1.1
pkg-resources==0.0.0
redis==3.5.3
rq==1.5.2
sentry-sdk==0.19.1
urllib3==1.25.11
Werkzeug==1.0.1

I run app.py like SENTRY_DSN={sentry_dsn_url} app.py and worker.py as simply python worker.py.

Right, that's because you don't initialize the SDK in the RQ worker at all. You need to initialize it in both, or import the flask app in your worker, for anything to function.


Feature/profile

@vishmittal,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Hitting 'X' in a non-reactive property pane doesn't reset the values in the property pane

Category

[ ] Question
[ ] Typo
[X ] Bug
[ ] Enhancement / Suggestion
[ ] Additional article idea

Expected or Desired Behavior
When hitting 'X' in a non-reactive property pane, then hitting edit again, the expectation would be that the property pane shows the currently saved values for the properties.
Observed Behavior
When you go back to the property pane, the previously edited values (not the saved values in the webpart) are shown.

Fix is in progress.

Hopefully a fix for this comes soon...
In addition, the "Apply" button should save the changes and close the property panel. Also, a cancel button that serves the same purpose as the X in the top right corner would help users a lot.

The fix is checked in. It should be out in public in a week. Please check back on Friday, the 12th.

the "Apply" button should save the changes and close the property panel

We have not done this intentionally to avoid unnecessary screen redraws on the user.

a cancel button that serves the same purpose as the X in the top right corner would help users a lot.

We had a discussion on this and tabled it for now. I will bring this up with the designers again.


Use self to access private method in BaseFormatConverter

Addition to https://github.com/yiisoft/yii2/pull/20014 - using self ensures that PHP won't use method with the same name in child class.

👍🏻


feat: Add Intro Modal

Description
The modal version of https://github.com/BuidlGuidl/burnerwallet/pull/57. I haven't added any spinners yet after clicking the button, still thinking about that part.

Thanks for this @ChangoMan !!
I definitely prefer this approach!! (with some tweaks**) Yes, the landing page can hold more info, but this feels more natural (the transition of closing the modal doesn't feel the same as navigating to another page). If we want to display more info, we can always link to a page with some docs. (from the modal or the settings drawer). Intuitive experience > a lot of info displayed.
We didn't have any "welcoming experience" before, so I feel this is a good first iteration. Going for a full landing page feels like too big of a jump.
**Tweaks that I'd make:

Less text. I can't see the button in my phone. We can probably remove the 2nd paragraph & the 3rd bullet point, and shorten the 2nd bullet point a bit.
Idea for the animation:

When clicking the button, we show a spinner in the button.
At the same time we remove the saturate-0 (or make it less strong)
At the same time, we do some randomness magic where the background of the wallet shows diff colors (I guess like creating diff random values). The modal is still open, but you will be able to see it.
We do this for 2 seconds? And then close the modal.

In any case, If I'm the only one who likes this option, happy to go with #58 haha. If we are divided we can ask Austin and some other people.

Sound like we like the modal! I'll trim down the text, let me know if it looks better on your phone. I'll also mess with the animation and I can add the landing page at /info easily.
Should we wait until the wallet connect PR gets merged? This PR will alter the structure quite a bit and might mess up that PR.

Sound like we like the modal! I'll trim down the text, let me know if it looks better on your phone. I'll also mess with the animation and I can add the landing page at /info easily.
Should we wait until the wallet connect PR gets merged? This PR will alter the structure quite a bit and might mess up that PR.

Maybe if @Pabl0cks think the WC is working well enough to be merged, we can merge it, and add the known issues as new issues to fix them (I'm working on fixing these issues, but these are not easy ones :-( )

Nice job @ChangoMan!! I really like the modal, the slim version of it looks nice on my mobile and is pretty concise, I like it.
When we merge the extra warning when the user receives real funds, we'll have a double message about doing a pk backup, which I think is good. And there we can be more explicit on the risk on not doing the backup (losing funds).

What if we move the landing page to another URL, like /info, for now?
I think that like Pablo commented on the Landing Page PR, this will be useful for people with no context about the Burner Wallet and it will be good content to be indexed by the search engines, so the users can find the site when looking for a wallet.

Now I'm totally up for this modal too! ♥ But yeah we could have a /info or /how-works page explaining all that info.
Probably won't be enough to get any SEO traffic, unless we start getting nice backlinks to it, but it won't hurt to have it, and can help some users that want to know how their burner works.

Should we wait until the wallet connect PR gets merged? This PR will alter the structure quite a bit and might mess up that PR.

Tonight I can do the last tests and we merge it? We'll have to continue working and testing on it, and next iteration of WC we can improve the UI/UX a bit too, but since is a bit hidden feature I guess we could merge the first iteration as it is 🙏

This is looking great! Now it fits nicely on my phone.

Yes, we can create a docs / FAQ / info page and link to it from the settings drawer or even the initial modal
A 1 - 2 seconds animation will be amazing too

But we can tackle these two in different PRs. This looks good for a merge!
Regarding merging #46 , up to Pablo and Damu. Per Pablo's last comment it seems that it's ready! IMO If it's hidden, doesn't need to be super polished.
Thanks all!

@ChangoMan #46 is merged now. There are some conflicts to be resolved now. After resolving I can do a final review.

@damianmarti Merge conflicts should be resolved!


fix: flaky timeout test

I fixed the flaky timeout test when calling a query, and skipped the subscriptions one due to a known issue. The tests were sometimes failing (see run 1 and run 2].
The only reason I see that they were sometimes failing is due to AbortSignal.timeout not changing the signal's aborted field to true before the request is sent and a response is received.

Will be made obsolete by reverting of the commit where the tests were added


Out of memory error

When I run the application on Samsung galaxy on8, I got this error and app crashes.
Caused by java.lang.OutOfMemoryError
Failed to allocate a 8388620 byte allocation with 7232536 free bytes and 6MB until OOM
com.microsoft.azure.storage.core.Utility.analyzeStream
com.microsoft.azure.storage.core.Utility.analyzeStream (Utility.java:199)
Thanks & Regards.

@tec-anDro-DeV , can you please share the doc link to further assist?

@tec-anDro-DeV , Do you have any update on this issue?

@tec-anDro-DeV , Please provide the link of the doc so that we will be able to help you. I am closing this issue now. Please provide the link and tag me if you want to reopen this issue.


feat(connector): Add topic to mqtt additional columns

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

Make the MQTT topic available as an additional column
Revert the change made in https://github.com/risingwavelabs/risingwave/pull/18961 to restore MQTT functionality

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[x] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

It's now possible to include the topic on which MQTT messages have been received by using INCLUDE topic in your SELECT

@tabVersion With ae9f988 (#19017) I've modified this so that it uses the partition instead of a separate topic column.
Meanwhile https://github.com/foundation-zero/risingwave-docs/commit/8d2b58fdf02bcffc5e36d5fbcad4c039aa686c73 is ready for a pull request once this is merged

Let's merge


Overflow issues with CupertinoContextMenu, Columns and ListViews

Steps to Reproduce

wrap a column with a CupertinoContextMenu
add 2 or more children to the Column
place 2 or more columns in a ListView
open the CupertinoContextMenu

Expected results: The opening animation should not result in a overflow issue. The child should be scaled up and down instead of resizing it.
Actual results: The child is resized during the opening animation, which cause a overflow issue.
Code Sample:

code sample
// Flutter code sample for CupertinoContextMenu

// This sample shows a very simple CupertinoContextMenu for an empty red
// 100x100 Container. Simply long press on it to open.

import 'package:flutter/material.dart';

import 'package:flutter/cupertino.dart';

void main() => runApp(MyApp());

/// This Widget is the main application widget.
class MyApp extends StatelessWidget {
  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: MyStatelessWidget(),
    );
  }
}

/// This is the stateless widget that the main application instantiates.
class MyStatelessWidget extends StatelessWidget {
  MyStatelessWidget({Key key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child:ListView.builder(
            itemBuilder: (context, index) => CupertinoContextMenu(
            child: Column(
              children: <Widget> [
                Container(
                  color: Colors.red,
                  width: 100,
                  height: 100,
                  margin: const EdgeInsets.all(16),
                ),
                Container(
                  color: Colors.green,
                  width: 100,
                  height: 100,
                  margin: const EdgeInsets.all(16),
                ),
              ],
            ),
            actions: <Widget>[
              CupertinoContextMenuAction(
                child: const Text('Action one'),
                onPressed: () {
                  Navigator.pop(context);
                },
              ),
              CupertinoContextMenuAction(
                child: const Text('Action two'),
                onPressed: () {
                  Navigator.pop(context);
                },
              ),
            ],
          ),
          itemCount: 20,
        ),
      ),
    );
  }
}

Logs

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, v1.17.3, on Microsoft Windows [Version 10.0.18363.836], locale de-DE)

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[√] Android Studio (version 4.0)
[√] VS Code (version 1.45.1)
[√] Connected device (1 available)

• No issues found!

Looks like it's  due to animation

flutter doctor -v
[✓] Flutter (Channel dev, 1.19.0-4.0.pre, on Mac OS X 10.15.5 19F101, locale
    en-GB)
    • Flutter version 1.19.0-4.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision 2f7a59a8da (3 days ago), 2020-06-05 03:44:02 -0700
    • Engine revision d17c84e7af
    • Dart version 2.9.0 (build 2.9.0-13.0.dev 02915ec5ce)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.45.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.11.0

[✓] Connected device (5 available)
    • SM M305F                     • 32003c30dc19668f • android-arm64  • Android
      10 (API 29)
    • Android SDK built for x86 64 • emulator-5554    • android-x64    • Android
      9 (API 28) (emulator)
    • macOS                        • macOS            • darwin-x64     • Mac OS
      X 10.15.5 19F101
    • Web Server                   • web-server       • web-javascript • Flutter
      Tools
    • Chrome                       • chrome           • web-javascript • Google
      Chrome 83.0.4103.97

• No issues found!

Unfortunately it's still an issue, did anyone find a solution or custom previewBuilder function to prevent that?

So annoying, that basic UX infrastructure like this isn't properly built out. If this was done well, implementing it would take 5 minutes, it took me hours so far and doesn't look like it's possible to make it great...

code sample
// Flutter code sample for CupertinoContextMenu

// This sample shows a very simple CupertinoContextMenu for an empty red
// 100x100 Container. Simply long press on it to open.

import 'package:flutter/material.dart';

import 'package:flutter/cupertino.dart';

void main() => runApp(MyApp());

/// This Widget is the main application widget.
class MyApp extends StatelessWidget {
  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: MyStatelessWidget(),
    );
  }
}

/// This is the stateless widget that the main application instantiates.
class MyStatelessWidget extends StatelessWidget {
  MyStatelessWidget({Key key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: ListView.builder(
          itemBuilder: (context, index) => CupertinoContextMenu(
            child: Column(
              children: <Widget>[
                Container(
                  color: Colors.red,
                  width: 100,
                  height: 100,
                  margin: const EdgeInsets.all(16),
                ),
                Container(
                  color: Colors.green,
                  width: 100,
                  height: 100,
                  margin: const EdgeInsets.all(16),
                ),
              ],
            ),
            actions: <Widget>[
              CupertinoContextMenuAction(
                child: const Text('Action one'),
                onPressed: () {
                  Navigator.pop(context);
                },
              ),
              CupertinoContextMenuAction(
                child: const Text('Action two'),
                onPressed: () {
                  Navigator.pop(context);
                },
              ),
            ],
          ),
          itemCount: 20,
        ),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.6, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.22.6 at /Users/tahatesser/Code/flutter_stable
    • Framework revision 9b2d32b605 (5 days ago), 2021-01-22 14:36:39 -0800
    • Engine revision 2f0af37152
    • Dart version 2.10.5

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (2 available)
    • RMX2001 (mobile)     • EUYTFEUSQSRGDA6D          • android-arm64 • Android 10 (API 29)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E • ios           • iOS 14.3

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 1.26.0-13.0.pre.194, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.26.0-13.0.pre.194 at /Users/tahatesser/Code/flutter_master
    • Framework revision 71aec53acb (5 hours ago), 2021-01-26 21:53:04 -0800
    • Engine revision b11bef83a5
    • Dart version 2.12.0 (build 2.12.0-263.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (4 available)
    • RMX2001 (mobile)     • EUYTFEUSQSRGDA6D          • android-arm64  • Android 10 (API 29)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E • ios            • iOS 14.3
    • macOS (desktop)      • macos                     • darwin-x64     • macOS 11.1 20C69 darwin-x64
    • Chrome (web)         • chrome                    • web-javascript • Google Chrome 88.0.4324.96

• No issues found!

code sample
// Flutter code sample for CupertinoContextMenu

// This sample shows a very simple CupertinoContextMenu for an empty red
// 100x100 Container. Simply long press on it to open.

import 'package:flutter/material.dart';

import 'package:flutter/cupertino.dart';

void main() => runApp(MyApp());

/// This Widget is the main application widget.
class MyApp extends StatelessWidget {
  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: MyStatelessWidget(),
    );
  }
}

/// This is the stateless widget that the main application instantiates.
class MyStatelessWidget extends StatelessWidget {
  MyStatelessWidget({Key key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: ListView.builder(
          itemBuilder: (context, index) => CupertinoContextMenu(
            child: Column(
              children: <Widget>[
                Container(
                  color: Colors.red,
                  width: 100,
                  height: 100,
                  margin: const EdgeInsets.all(16),
                ),
                Container(
                  color: Colors.green,
                  width: 100,
                  height: 100,
                  margin: const EdgeInsets.all(16),
                ),
              ],
            ),
            actions: <Widget>[
              CupertinoContextMenuAction(
                child: const Text('Action one'),
                onPressed: () {
                  Navigator.pop(context);
                },
              ),
              CupertinoContextMenuAction(
                child: const Text('Action two'),
                onPressed: () {
                  Navigator.pop(context);
                },
              ),
            ],
          ),
          itemCount: 20,
        ),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.6, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.22.6 at /Users/tahatesser/Code/flutter_stable
    • Framework revision 9b2d32b605 (5 days ago), 2021-01-22 14:36:39 -0800
    • Engine revision 2f0af37152
    • Dart version 2.10.5

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (2 available)
    • RMX2001 (mobile)     • EUYTFEUSQSRGDA6D          • android-arm64 • Android 10 (API 29)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E • ios           • iOS 14.3

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 1.26.0-13.0.pre.194, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.26.0-13.0.pre.194 at /Users/tahatesser/Code/flutter_master
    • Framework revision 71aec53acb (5 hours ago), 2021-01-26 21:53:04 -0800
    • Engine revision b11bef83a5
    • Dart version 2.12.0 (build 2.12.0-263.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (4 available)
    • RMX2001 (mobile)     • EUYTFEUSQSRGDA6D          • android-arm64  • Android 10 (API 29)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E • ios            • iOS 14.3
    • macOS (desktop)      • macos                     • darwin-x64     • macOS 11.1 20C69 darwin-x64
    • Chrome (web)         • chrome                    • web-javascript • Google Chrome 88.0.4324.96

• No issues found!

I can still reproduce it in version 2.2.2

As a workaround, wrapping your widget in a SingleChildScrollView will solve the issue, or at least will let you ship the next version of your app until someone comes up with a real solution.
CupertinoContextMenu(
  child: SingleChildScrollView(
    child: Container(
    // your widget's content goes here...

Is there any update on this issue. I am running on Flutter 3.0.5 and the issue still persists.

The method from @ahmedmkamal is working for me.
Using SingleChildScrollView for a child of CupertinoContextMenu and a child of previewBuilder.
Like this.
              CupertinoContextMenu(
                      previewBuilder: (BuildContext context,
                          Animation<double> animation, Widget child) {
                        return SingleChildScrollView(
                            child: Column(
                          children: [
                           // your widget's content goes here...
                          ],
                        ));
                      },
                      actions: [
                        CupertinoContextMenuAction(
                          isDefaultAction: true,
                          trailingIcon: CupertinoIcons.doc_on_clipboard_fill,
                          child: const Text('Copy'),
                        ),
                      ],
                      child: SingleChildScrollView(
                        child: Column(
                          children: [
                            // your widget's content goes here...
                          ],
                        ),
                      ))

Still persists in Flutter 3.7

Is this still an issue, I'm failing to reproduce this.


Consecutive + CSS selectors sometimes cause problems in WebKit.

We add ~ as an alternative here. + is still needed, though, as ~
itself has problems in iOS 9 WebViews.
@addyosmani @surma PTAL!

I assume these changes have been well tested on iOS - have we verified that the additional updates don't break in our target desktop browsers? Will test shortly.

Yup, tried it out on Safari and WebViews, both mobile and desktop. Also tried on Chrome and Firefox desktop. Haven't tried IE, will give that a go.

IE11 seems fine as well, can't test Edge at the moment.

Also, for testing background, these fixes are meant to fix desktop Safari in OS X 10.10 (mobile was already working correctly, with the previous fixes).
Sadly, because the engines appear to be different, fixing the previous problem introduced the one we're now fixing in this bug.
If we're going to have bugs, it'd be nice if we could at least have a consistent set of them inside of a browser family ;)

LGTM :)

And thanks for taking this on, @sgomes!


RuntimeError: Download failed

Keep getting this error when the generator starts to try and output the 3D generated mesh. I have also done as it suggests and downloaded the files and put them in the /models/3dphoto folder but it does not matter and I get the same error message.
Running 3D Photo Inpainting ..
Downloading https://filebox.ece.vt.edu/~jbhuang/project/3DPhoto/model/edge-model.pth to ./models/3dphoto/edge_model.pth
All done.
*** Error completing request
*** Arguments: (0, <PIL.Image.Image image mode=RGB size=1456x816 at 0x15805F820>, None, '', '', 1, 0, 512, 512, False, True, False, False, 0, 1, False, 1, True, True, False, False, ['left-right', 'red-cyan-anaglyph'], 2.5, 0, 'polylines_sharp', 0, True, True, False, False, False, 'u2net', False, 0, 2, False, None, True, False, True, False) {}
    Traceback (most recent call last):
      File "/Users/vigfus/stable-diffusion-webui/extensions/stable-diffusion-webui-depthmap-script/scripts/depthmap.py", line 888, in run_3dphoto
        ensure_file_downloaded(edgemodel_path,"https://filebox.ece.vt.edu/~jbhuang/project/3DPhoto/model/edge-model.pth")
      File "/Users/vigfus/stable-diffusion-webui/extensions/stable-diffusion-webui-depthmap-script/scripts/depthmap.py", line 1476, in ensure_file_downloaded
        raise RuntimeError('Download failed. Try again later or manually download the file to that location.')
    RuntimeError: Download failed. Try again later or manually download the file to that location.

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "/Users/vigfus/stable-diffusion-webui/modules/call_queue.py", line 55, in f
        res = list(func(*args, **kwargs))
      File "/Users/vigfus/stable-diffusion-webui/modules/call_queue.py", line 35, in f
        res = func(*args, **kwargs)
      File "/Users/vigfus/stable-diffusion-webui/extensions/stable-diffusion-webui-depthmap-script/scripts/depthmap.py", line 1236, in run_generate
        outputs, mesh_fi, meshsimple_fi = run_depthmap(
      File "/Users/vigfus/stable-diffusion-webui/extensions/stable-diffusion-webui-depthmap-script/scripts/depthmap.py", line 835, in run_depthmap
        mesh_fi = run_3dphoto(device, inpaint_imgs, inpaint_depths, inputnames, outpath, fnExt, vid_ssaa, inpaint_vids)
      File "/Users/vigfus/stable-diffusion-webui/extensions/stable-diffusion-webui-depthmap-script/scripts/depthmap.py", line 1006, in run_3dphoto
        del rgb_model
    UnboundLocalError: local variable 'rgb_model' referenced before assignment

---
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/gradio/routes.py", line 422, in run_predict
    output = await app.get_blocks().process_api(
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/gradio/blocks.py", line 1326, in process_api
    data = self.postprocess_data(fn_index, result["prediction"], state)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/gradio/blocks.py", line 1229, in postprocess_data
    self.validate_outputs(fn_index, predictions)  # type: ignore
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/gradio/blocks.py", line 1204, in validate_outputs
    raise ValueError(
ValueError: An event handler (f) didn't receive enough output values (needed: 5, received: 3).
Wanted outputs:
    [gallery, textbox, model3d, html, html]
Received outputs:
    [None, "", "
UnboundLocalError: local variable 'rgb_model' referenced before assignment

Time taken: <wbr>2m 26.24s

"]

Any suggestions on why this is happening and how to fix this?
My setup:
Macbook pro

2,4GHz Quad-Core Intel Core i5
Intel iris plus graphics 655 1536 mb
16GB ram 2133MHz
Mac OS Ventura 13.4.1

Stabel diffusion

version: v1.4.1
Python: 3.10.7
Torch: 2.0.1
Xformers: N/A
Gradio: 3.32.0

please make sure the manually downloaded files have underscores in their names, and not a hyphen.
eg : "./models/3dphoto/edge_model.pth"

🤦♂ Thanks @thygate , that was almost too embarrassing 😅

It's my mistake, I spent quite a bit staring at it myself the first time this popped up .. :blush:
glad you have it solved.


Support for OpenAPI v3

Fixes #1316
Fixes #1317
Fixes #1310
Fixes #1329

Release Note
camel-k supports OpenAPI v2 and v3
rest-dsl trait has been renamed to openapi

kubernetes failure is due to:
error creating build container: Error committing the finished image: error adding layer with blob
"sha256:d4d5efc19f7b7f4481c3fea5002e04eff45a5dbee252421e307e4b5533e555f5": error
creating layer with ID "19047015d6f133131546ee9264f61ce99e04ae5ff374f94e554dd39d9f2e37f6":
no space left on device

This can be merged as the spectrum one is good.. but we should look at why this is failing in another issue.
Is there some cache by default in the buildah strategy? @astefanutti


Container API Test with HostName

New Test for Creating a Container using API with custom Hostname
Signed-off-by: Rajdeep Dua<EMAIL_ADDRESS>

Can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "dry-run-test" git@github.com:rajdeepd/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

This will update the existing PR, so you do not need to open a new one.

Can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "dry-run-test" git@github.com:rajdeepd/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

This will update the existing PR, so you do not need to open a new one.


Error counters

I am trying to aggregate all errors generated by AletheiaKafka producer and am unable to do that with a wild card since the below counter is part of the hierarchy but is not an error counter.
Please change the location of the following counter .Aletheia.DatumTypes..DatumProducer.RecommendationKafka_Chidc.Data.Tx.KafkaTopicProductionEndPoint.Send.Attempts.Failures.Duration.count so that all counters below ...Send.Attempts.Failures can be aggregated.

We've changed the producer's failure metrics sub tree in aletheia-0.42, so it should be easier to make these kinds of aggregations.


added meta-tags, title and favicons

Changes:
-Changed the position of the meta tags

Added images for favicons and meta banner
Added favicon link tag

Test cases checked

Verified the title showing up

Added meta titles and tags


Poll fn is also defined in futures_preview

I see you've defined your own poll_fn, but also have the futures_preview dependency which includes a similar function. I don't know why this was done - just in case you didn't know this was the case.

@PvdBerg1998 thanks for sharing; we're indeed aware. A minor-but-important difference between the two is that our poll_fn is an async fn, while the futures-rs version wasn't at the time we ported it.
We're fairly conservative in the structs we expose, making a deliberate effort to match stdlib. In addition to that we like being able to define our own documentation, as it makes it easier to link between implementations.
I hope this makes sense. Thanks for raising!


Disable class-wide undefined field warnings

Discussed in https://github.com/sumneko/lua-language-server/discussions/967

Originally posted by adamnejm March  1, 2022
Is there a way to disable Lua Diagnostics.(undefined-field) for a certain class?
I'd like to keep all other functionality of ---@class without forcing users to do ---@diagnostic disable: undefined-field.
Simple example:
---@class Animal
local Animal = {}

---@return Animal
local function new(tbl)
	return setmetatable(tbl, Animal)
end

local tiger = new { name = "Tiger" }
print(tiger.name) --> Tiger

---@class Animal
---@field [string] any

Will be implemented in version 3.X

Done.


New release to have fixed doc links

Hello @tmeckel,
Can you create a new release of this provider? For the SEO on our website, we had to remove some broken links, one of them being for this time provider:
https://github.com/pulumi/registry/pull/2322/files#diff-51d9b356a4353a5991053ed4b737cf5d60854ee538111510da2d551a1e980e79
The link is already in this repo, but not released yet.

@ringods any special requirements? Or simply create a new version tag v0.0.10, which will fire of the GitHub workflow.

No special requirements. Triggering the release would be enough.

Closed by #28


Make app control media volume, set volume to max for playback test

When pressing volume buttons, media volume will be changed instead of the default (ringer volume). Also, when pressing the playback test button, the media volume will be set to 100%.

Looks good, merging.


Designable UITableViewCell

Hello everyone.
I'm struggling with @IBDesignable UITableViewCells.
When I create a tableViewCell, it 's possible to change the background color of the cell to red:

But I can't see my label, and I can't update the text of the label.
Could someone make an example for at custom table view cell with a label, or explain how to update my custom designable table view cell?
Thank you!

why do you have a NibDesignable view, then a cell inside it?

How to design UITableViewCells is well explained in readme and also in #21 .
Here's also a sample of how to create tableViewCells

Perfect, i got it to work. Thank you!


Sidebar bug

The Sidebar  has a layout issue on the bottom. The last component is not shown completely (see picture).

Fixed in main branch. Thank you ! :)


Use util::Status in frontend.cc and frontend_signer.cc

... and don't CHECK fail when we can't add an entry to the consistent store, just return an error instead.

Done reviewing.

If all you change is the sentence in the util::Status, LGTM, feel free to merge. If you do the "inline UpdateStats" thing, there's a bit more involved, might be worth another look?

LGTM


Fix list editor panics during insertion

Fixes #6522

Fixed occasional panics when inserting or moving elements around.
Improved mouse events handling in list editor to behave correctly during box selection.
Removed vectorEditor feature flag, enabling the list editor permanently.
Replaced node background shape with Rectangle and removed unnecessary separation between hover area and background. Switched node hover state to use new mouse events system.
Adjusted size of hover area of the list editor such that it is harder do accidentally insert a new element and easier to drag the nodes around.
Fixed mouse down event propagation inside list editor when clicking without dragging. This allows dropdowns nested within list items to work correctly.

Important Notes
The mouse handling changes involve an unfortunate huge hack, where we enable mouse events on the mouse shape during box selection. That way we know for sure that no other shape will be able to receive mouse enter event. Then the list editor widget is modified to only actually respond to events when its background is hovered. We will definitely want a more proper way to handle mouse event contention, but it's definitely out of scope for current bugfixing.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

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

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

Quick feedback from trying this branch. The Vector Dropdowns now work :).
But has a detrimental affect on being able to connect links.
https://user-images.githubusercontent.com/4699705/236422595-8efca0c3-cab7-4548-8f44-cbd232ebd77d.mp4

Stuff from my trying to use this build today:

As above dragging to establish a connection is hard.
Ctrl clicking into edit a node, then moving the cursor by clicking doesn't seem to work.
If a Vector is pointed at a non-vector (e.g. single value or a function) then you just get a dot.

Seemed to get extra dots on things that aren't vectors.

The + to add the first item doesn't seem to work.
Comma's seems to be sometimes visible and sometimes not.

I have fixed the issues with edge dragging. My previous event resume implementation have broken the mouse down events in new event system. Now it works again and nodes can be connected as expected, including inside list editor. Ctrl clicking/edit mode is also fixed with that.

@Frizi what is the status? I would love to test it :)

QA Report 🔴
In general, looks much nicer. I like how dropping the edge to the vector looks and works now.
There are still issues that I spotted, but they might be fixed separately, I suppose:

On the node table.rename_columns Map.from_vector, the Map.from_vector part is not visible.

Adding elements to the vector after Map.from_vector adds Boolean.True. That is probably incorrect (it's probably an engine issue, though).
Connecting the edge to this vector is hard. It's hard to find a free place. It seems like the free place is right on top of the square bracket. That seems weird. In the video, you can see that I try to target that point for a very long time. Again, pixel-hunting is depressing.

https://github.com/enso-org/enso/assets/6566674/13f35e60-4a3f-4833-bfa6-5a692b29f8f6

Sometimes (almost every time for me), dropping the edge there adds two elements.

https://github.com/enso-org/enso/assets/6566674/0d45c438-f79f-4967-8e14-45d8443441dc

After recording the previous video, I removed the first element of the vector, and the cursor got stuck in the red cross state. Hovering the node again fixed it, so it is not that important.

There is a place where the cursor turns green on this node, and pressing LMB produces bizarre code modifications. I don't see the same behavior for other functions, like String.split.

https://github.com/enso-org/enso/assets/6566674/a46eb5b0-81de-4e94-aab4-0ab8ff381cbd


recursion when used with sugarskull

When used alongwith sugarskull we get the error "too much recursion", specifically on firefox 3.6.23 .
Here is jsfiddle http://jsfiddle.net/zfTBS/1/ .
I have tried with latest versions of all libs but no luck. jquery(1.6.4), webshims (1.8.2) and SugarSkull latest.
I am not sure whether webshims/SugarSkull so have added one issue for sugarskull too.
Same thing works well on Chrome.
Thanks :)

Actually, this issue comes from webshims lib, but should be fixed in SS. First of all I'm not sure how this should work. But I see, that SS trys to go through all properties of your declared function test. I don't think, that this is intended. However, in non polyfilled browsers functions do not have listed properties. In case of a polyfilled browser, they have.
SS should check wether the property is a true member of the object or not, using the hasOwnProperty method. Additionally SS should check wether the for in loop on your test function is really by design or an accident.

sorry, im not sure i understand your comment, the regify function does not operate on a function, it operates on an object literal. can you try to rephrase your question?

never mind.


Update dependencies in order to fix security vulnerabilities

Besides #285 npm audit reports multiple vulnerabilities:
# npm audit report

ajv  <6.12.3
Severity: moderate
Prototype Pollution in Ajv - https://github.com/advisories/GHSA-v88g-cgmw-v5xw
fix available via `npm audit fix`
node_modules/eslint/node_modules/ajv
node_modules/table/node_modules/ajv

ansi-regex  4.0.0 - 4.1.0 || 5.0.0
Severity: high
 Inefficient Regular Expression Complexity in chalk/ansi-regex - https://github.com/advisories/GHSA-93q8-gq69-wqmw
 Inefficient Regular Expression Complexity in chalk/ansi-regex - https://github.com/advisories/GHSA-93q8-gq69-wqmw
fix available via `npm audit fix`
node_modules/cliui/node_modules/ansi-regex
node_modules/eslint/node_modules/ansi-regex
node_modules/inquirer/node_modules/ansi-regex
node_modules/inquirer/node_modules/strip-ansi/node_modules/ansi-regex
node_modules/table/node_modules/ansi-regex
node_modules/yargs/node_modules/ansi-regex

async  <2.6.4
Severity: high
Prototype Pollution in async - https://github.com/advisories/GHSA-fwr7-v2mv-hh25
No fix available
node_modules/async
  istanbul  *
  Depends on vulnerable versions of async
  node_modules/istanbul

braces  <=2.3.0
Regular Expression Denial of Service (ReDoS) in braces - https://github.com/advisories/GHSA-cwfw-4gq5-mrqx
Regular Expression Denial of Service in braces - https://github.com/advisories/GHSA-g95f-p29q-9xw4
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/braces
  micromatch  0.2.0 - 2.3.11
  Depends on vulnerable versions of braces
  Depends on vulnerable versions of parse-glob
  node_modules/micromatch
    anymatch  1.2.0 - 1.3.2
    Depends on vulnerable versions of micromatch
    node_modules/anymatch
      chokidar  1.0.0-rc1 - 2.1.8
      Depends on vulnerable versions of anymatch
      Depends on vulnerable versions of glob-parent
      node_modules/chokidar
      node_modules/watchpack-chokidar2/node_modules/chokidar
        babel-cli  *
        Depends on vulnerable versions of chokidar
        node_modules/babel-cli
        watchpack-chokidar2  *
        Depends on vulnerable versions of chokidar
        node_modules/watchpack-chokidar2
          watchpack  1.7.2 - 1.7.5
          Depends on vulnerable versions of watchpack-chokidar2
          node_modules/watchpack
            webpack  4.44.0 - 4.46.0
            Depends on vulnerable versions of watchpack
            node_modules/webpack

glob-parent  <5.1.2
Severity: high
Regular expression denial of service in glob-parent - https://github.com/advisories/GHSA-ww39-953v-wcq6
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/eslint/node_modules/glob-parent
node_modules/glob-parent
node_modules/mocha/node_modules/glob-parent
node_modules/watchpack-chokidar2/node_modules/glob-parent
  glob-base  *
  Depends on vulnerable versions of glob-parent
  node_modules/glob-base
    parse-glob  >=2.1.0
    Depends on vulnerable versions of glob-base
    node_modules/parse-glob

minimist  <=1.2.5
Severity: critical
Prototype Pollution in minimist - https://github.com/advisories/GHSA-xvch-5gv4-984h
Prototype Pollution in minimist - https://github.com/advisories/GHSA-vh95-rmgr-6w4m
Prototype Pollution in minimist - https://github.com/advisories/GHSA-vh95-rmgr-6w4m
fix available via `npm audit fix`
node_modules/fsevents/node_modules/minimist
node_modules/fsevents/node_modules/rc/node_modules/minimist
node_modules/handlebars/node_modules/minimist
node_modules/minimist
node_modules/mocha/node_modules/minimist
  mkdirp  0.4.1 - 0.5.1
  Depends on vulnerable versions of minimist
  node_modules/fsevents/node_modules/mkdirp

path-parse  <1.0.7
Severity: moderate
Regular Expression Denial of Service in path-parse - https://github.com/advisories/GHSA-hj48-42vr-x3v9
fix available via `npm audit fix`
node_modules/path-parse

shelljs  <=0.8.4
Severity: high
Improper Privilege Management in shelljs - https://github.com/advisories/GHSA-4rq4-32rv-6wp6
Improper Privilege Management in shelljs - https://github.com/advisories/GHSA-64g7-mvw6-v9qj
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/shelljs

tar  <=4.4.17
Severity: high
Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization - https://github.com/advisories/GHSA-5955-9wpr-37jh
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links - https://github.com/advisories/GHSA-qq89-hq3f-393p
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links - https://github.com/advisories/GHSA-9r2w-394v-53qc
Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization - https://github.com/advisories/GHSA-3jfq-g458-7qm9
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning - https://github.com/advisories/GHSA-r628-mhmh-qjhw
fix available via `npm audit fix`
node_modules/fsevents/node_modules/tar

20 vulnerabilities (2 low, 3 moderate, 14 high, 1 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Especially the used versions of babel packages look quite outdated, as the un-scoped versions, used in the package.json, were not updated for 4 years (e.g. babel-core, meanwhile renamed to @babel/core).

Addressed in #288. Released in:

https://www.npmjs.com/package/lightstep-tracer/v/0.33.0
https://www.npmjs.com/package/lightstep-tracer/v/0.33.0-no-protobuf


Enabling logging in cloud-asr

Hi,
thank you for the project!
I'm running with make run_locally command.
For some reason I see that mysql db is always empty.
I was trying to find logs (on master/worker nodes), but somehow I didn't see any.
is there any way to enable logs?
thanks

Hi,
are you using Mac or Linux? What is the output of ls mysql_data?
Unfortunately, there is no logging except for the standard Docker logs - you can try docker logs cloudasr-com-web.
Best,
Ondrej

Hi Ondrej,
Thank you for the response.
I'm actually on Win now and run this from within cygwin.
mysql_data is empty.
I guess something doesn't play well with the volume mappings, as I don't see schema.sql file in the mysql container under the /docker-entrypoint-initdb.d/schema.sql.
BTW, I'm able to test the 'recognize' functionality, so the system seems to be partially operational in my setup.
thanks.

Ok, I haven't tested CloudASR on Windows - the problem here is with make mysql_data step which should create db schema. Please, let me know if you manage to fix the volume mappings, it would be really helpful.
Yes, API functionality should work correctly - only web interface needs MySQL.


Added definition of Ruby 2.4.0preview2

see https://www.ruby-lang.org/en/news/2016/09/08/ruby-2-4-0-preview2-released/
And I applied OpenSSL-1.1.0 to this definition.

oops, I just merged #993 but I see this is slight different because this includes openssl 1.1.0, what is the reason for this?

2.4.0preview2 is first version of OpenSSL 1.1.0 supporting. I hope to test with this feature. but It is not requirements of 2.4.0 preview2 :octocat:  I close this.
Thank you for your merging!

@hsbt Feel free to open a PR updating OpenSSL to 1.1.0 and I'll merge it 😊


Airflow execution_date is not the same as dbt_airflow_macros.execution_date()

I notice that the dbt_airflow_macros.execution_date()  only generates values for when the dbt cloud job is triggered from airflow and not when the dag is ran.
I will like to be able to import the execution_date() of airflow task run to dbt. Do you know any way to do this?

I have same issue
this is my dag info
[2023-02-14, 05:35:30 KST] {taskinstance.py:1277} INFO - Marking task as SUCCESS. dag_id=wf_d_dbt_test, task_id=run.tg_area.fact_cust_record_week_adong_prdt_gcode, execution_date=20230205T083000, start_date=20230214T053412, end_date=20230214T053530
and this is dbt log
DECLARE EXECUTION_DATE DATE DEFAULT DATE('2023-02-14');
I cleared job at 2/14 that scheduled 2/5 then dbt just get start_date not execution date.


sztp: Support running tests on Fedora with podman

Fixes #138

Proper SELinux support for volume mounts
Do not use nested docker-compose run, see #138
Do not use ${PWD} in compose file, breaks on Fedora with podman

Signed-off-by: Steven Royer<EMAIL_ADDRESS>

thank you @seroyer for fixing this issue


Updated C28750

Updated to the latest format

Docs Build status updates of commit ea687bc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-driver-docs-pr/devtest/28750-banned-istrlen-usage.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 63f15d7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-driver-docs-pr/devtest/28750-banned-istrlen-usage.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@MugBergerFries - Let me know if this one is ready to merge to live.

@DOMARS Yes, good to go, thanks!


switch to structured logging

This automatically adds additional fields like reconcile_id etc.. from the controller context.
before :
2023-05-18T01:53:14+03:00 INFO  controllers.KeystoneAPI Reconciled Service init successfully
after:
2023-05-18T02:00:28+03:00       INFO    Controllers.KeystoneAPI Reconciled Service init successfully    {"controller": "keystoneapi", "controllerGroup": "keystone.openstack.org", "controllerKind":"KeystoneAPI", "KeystoneAPI": {"name":"keystone","namespace":"openstack"}, "namespace": "openstack", "name": "keystone", "reconcileID": "512a4d9b-f31d-4fa4-a4cc-cd6c13e4455d"}
*by using per reconcile function respective logger objects, the intention is to lay the ground for parallel reconciliation in future and avoid race conditions as ctx objects are reconcile run specific.
*example logs lines  are currently from keystone operator #220_patch until this operator deployment patch testing  is is done

/ok-to-test

/hold
In order to avoid a merge conflict, we need to hold this until https://github.com/openstack-k8s-operators/dataplane-operator/pull/303 can be merged. PR 303 is the top priority in order to get merged at this time.

/unhold
rdoproject.org/github-check jobs should be passing now.

code testing seems to have an issue :
2023-10-19T13:12:17+03:00       ERROR   Could not wait for Cache to sync        {"controller": "barbican", "controllerGroup": "barbican.openstack.org", "controllerKind": "Barbican", "error": "failed to wait for barbican caches to sync: timed out waiting for cache to be synced"}

/retest

continued here : https://github.com/openstack-k8s-operators/dataplane-operator/pull/488


docs: new guide for validation of AsyncAPI files

Description

New guide for validation of AsyncAPI document.

Related issue(s)
Fixes #994

@fmvilas @smoya @derberg This NEW guide is now ready for technical review. ✨

Hey @Annysah, how's the next draft coming along? does Lukasz's feedback make sense to you? 😄

Hey @Annysah, how's the next draft coming along? does Lukasz's feedback make sense to you? 😄

Haha 😄 yes it does.

Dear @alequetzalli & @derberg, I would love your feedbacks on the update. Thank you!

left my review ✌🏽😄

Thanks @alequetzalli & @derberg for the feedbacks.

left my review ✌🏽😄

Thanks @alequetzalli and @derberg

Hello @alequetzalli & @derberg ,
I've implemented the requested changes, kindly help review.
Thank you!

@alequetzalli & @derberg, all done!

technically all good from my side
@alequetzalli I guess you need to have a final look.

yaay!!

Approved, but we can't merge yet because the prev/next buttons point to message validation guide PR https://github.com/asyncapi/website/pull/1005 which @starlightknown is still working on 😄
@derberg

/rtm


Crash on 0.9 for a certain app

Xperia 5.1.1
Not sure if fixed yet, discover-> search https://github.com/SecUSo/privacy-friendly-pedometer -> New locale-> something -> crash
D AndroidRuntime: Shutting down VM
E AndroidRuntime: FATAL EXCEPTION: main
E AndroidRuntime: Process: io.github.lonamiwebs.stringlate, PID: 13631
E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'java.util.Iterator io.github.lonamiwebs.stringlate.classes.resources.Resources.iterator()' on a null object reference
E AndroidRuntime: 	at io.github.lonamiwebs.stringlate.activities.TranslateActivity.loadStringIDsSpinner(TranslateActivity.java:562)
E AndroidRuntime: 	at io.github.lonamiwebs.stringlate.activities.TranslateActivity.setCurrentLocale(TranslateActivity.java:594)
E AndroidRuntime: 	at io.github.lonamiwebs.stringlate.activities.TranslateActivity.access$400(TranslateActivity.java:45)
E AndroidRuntime: 	at io.github.lonamiwebs.stringlate.activities.TranslateActivity$4.onClick(TranslateActivity.java:292)
E AndroidRuntime: 	at android.support.v7.app.AlertController$ButtonHandler.handleMessage(AlertController.java:157)
E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:102)
E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:211)
E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:5373)
E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Method.java:372)
E AndroidRuntime: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1020)
E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:815)
E AndroidRuntime: 	at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:102)

Fun fact: that's the application I wanted to translate before I came up with the idea for Stringlate 😆
I can reproduce the bug on v0.9, and on the current master branch. The problem occurs because their strings.xml file contains <> characters (i.e. some text inside a <string>). These are indeed invalid XML characters, and < and > should be used for text instead.

So, I should raise an issue there?

No, it's fine. Stringlate should consider as correct whatever the Android build considers correct. I didn't expect that the build would work with those characters (I would swear I've seen warnings of it before), but since it works, we should just mimic the behavior.

Thank you for testing the application in so much depth :)


create custom 404 page

When a URL does not exist, I wanted to have a custom 404 page. This is done now!


Allow renovate not only monday - fix json

Purpose
Fix json
Checklist

[ ] I have performed a self-review of my own code
[ ] I have added relevant logging with appropriate levels to my code
[ ] New event_codes have been documented on the wiki page
[ ] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[ ] I have added tests to prove my work
[ ] I have added welsh translation tags and updated translation files
[ ] I have run an accessibility tool on any pages I have made changes to and fixed any issues found
[ ] I have notified the Interaction Designer of any content changes so that appropriate screenshots/flow diagram changes can be made
[ ] The product team have tested these changes

Broken PR