Correct data type for tf serving warmup file: tf_serving_warmup_requests

"""Generate Warmup requests."""
import tensorflow as tf
import requests
import base64
import numpy as np
import requests
from PIL import Image

from tensorflow.python.framework import tensor_util
from tensorflow_serving.apis import predict_pb2
from tensorflow_serving.apis import prediction_log_pb2

im_path = '/home/n/Documents/mask_rcnn/dataset/val/00.jpg'
img = np.array(Image.open(im_path))
x = np.array(Image.open(im_path))
image_data = x.tolist()
NUM_RECORDS = 2

def main():
    """Generate TFRecords for warming up."""
    with tf.io.TFRecordWriter("tf_serving_warmup_requests") as writer:
        predict_request = predict_pb2.PredictRequest()

        predict_request.model_spec.name = 'a_model'

        predict_request.model_spec.signature_name = 'serving_default'

        predict_request.inputs['image:0'].CopyFrom(
            tensor_util.make_tensor_proto(image_data))

        log = prediction_log_pb2.PredictionLog(
            predict_log=prediction_log_pb2.PredictLog(request=predict_request))

        for r in range(NUM_RECORDS):
            writer.write(log.SerializeToString())

if __name__ == "__main__":
    main()

This is file which generates tf_serving_warmup_requests,
however im getting an error from the server:
2020-06-19 13:16:46.659681: E tensorflow_serving/util/retrier.cc:37] Loading servable: {name: a version: 1} failed: Invalid argument: Expects arg[0] to be float but half is provided

Could you help to set correct format for data input ?

@Adblu,
TensorFlow Serving issues are tracked in the Serving repo. Could you please submit a new issue from this link and fill in the template, so that we can track the issue there. Thanks!

Solved this by changing the image into the list:
            tensor_util.make_tensor_proto(image_data.tolist()))


Network doesn't sort numerically

When sorting high to low, 10 Gbps shows up before 100 Gbps, which is wrong.

thanks @evelynmitchell going to fix it

@evelynmitchell I fixed it. We have custom sorting logic now now. https://github.com/yeo/ec2.shop/blob/master/static/js/app.js#L4-L43

Looks a lot better. 75 GB is out of order.

@evelynmitchell Oh sorry. can you believe it? I forgot to deploy haha. It should work properly now I promise.


add shebang line

added shebang line so instead of "python jumpcutter.py -h", you can just use "jumpcutter.py -h" Note: only works on bash though

Ooh, cool! Will the original command with "python" still work though? I don't want people coming directly from the video getting confused...

Yeah it should still work but I'd recommend the shebang line be:
#!/usr/bin/env python3

oh yea, will change pull request

Should i just close this request and make a new one?

just add another commit to this, or if you want to close it then i can make a new PR with my patch that I sent in my other comment

just make the new PR
im tired rn


Contributing Open- Source as a Community Manager

Create a general  video on how one can Contribute to  Open- Source as a Community Manager

Hello @peculiaruc

Is there a timeline I should be aware of? Delivery time.
Also, how long should the video be for?

Is there a timeline I should be aware of? Delivery time. Also, how long should the video be for?

I share these with you.

You did? I must have missed it. Please share again

@Maryblessing hi! Just checking in with this.
Do you need any help getting started?
Are you able to work on this issue in the next few weeks?

Is there a timeline I should be aware of? Delivery time. Also, how long should the video be for?

Hi! @Maryblessing Just checking in with this again. Do you need any help getting started? Are you able to work on this issue in the next few weeks?


NaN mean timer value and standard deviation

I am using 3.1.0 and have started seeing NaN values for the mean and standard deviation of timers.  (Until recently, I was using 3.0.1 and I never had a NaN value.)
"theTimer" : {
      "count" : 4332,
      "max" : 0.288696783,
      "mean" : "NaN",
      "min" : 6.00388E-4,
      "p50" : 0.003298735,
      "p75" : 0.003298735,
      "p95" : 0.003298735,
      "p98" : 0.003298735,
      "p99" : 0.003298735,
      "p999" : 0.003298735,
      "stddev" : "NaN",
      "m15_rate" : 0.08561987306180467,
      "m1_rate" : 0.03960663833117155,
      "m5_rate" : 0.10383331627579845,
      "mean_rate" : 0.02467728882193572,
      "duration_units" : "seconds",
      "rate_units" : "calls/second"
    },

I don't think this is expected, is it?
Looking back through the change-log, it appears that v1.0.2 (Mar 08 2010) eliminated NaN values from timers:

Timer now uses Welford’s algorithm for calculating running variance, which means no more hilariously wrong standard deviations (e.g., NaN).

Is this a bug?

Should be fixed by #1033


windows and deep paths

Windows has a limit of ~250 char path when used with php.
it would seem even though node_modules is excluded, its still having subdirs looped over. this causes issues with grunt packages like grunt-contrib-imagemin which is 5+ levels deep of node_modules
I realize this project mainly pulls in i18n tools but i felt this should be brought up.

Hi @ctalkington, would you mind testing out the skip-excluded-dirs branch to see if it fixes this issue for you?
A nice bonus is that this "should" help speed up the makepot task since it won't have to test every file in an excluded directory.

@bradyvercher file scan ignorance for the excluded dirs was really awesome. Great job xD

@bradyvercher this def fixes makepot buidling, for some reason addtextdomain is stalling, trying to figure out if this is related to change or previously happened.

ok seems i just didnt give it long enough, and i hadnt run it with this many php files before. have you considered adding some verbose lines to better track whats getting called by the task? or atleast on what files etc?

@shivapoudel Thanks!
@ctalkington Glad it was a relatively easy fix. I'll try to get that merged soon.
That addtextdomain task can definitely be pretty slow since each file has to be passed to the PHP script separately. I've looked into ways to speed that up, but haven't found anything worthwhile.
There's an issue for adding verbose feedback (#25), but it's not something I've had the time to take on. Feel free to leave some feedback on that ticket or submit a PR if there's anything in particular you'd like to see, though.

@bradyvercher much appreciated, it was a show stopper when using imagemin in my process.

Shipped in v0.5.2!

thanks!


ModuleNotFoundError: No module named 'pandas' Error in rule preprocess_merge_logs_for_multiqc:

the merge_logs_for_multiqc preprocess rule specifies a conda env but not a container, and so when run without --use-conda will produce a ModuleNotFoundError

I've only used snakemake from conda/mamba installs which includes pandas.  Feel free to add a note to the readme to clarify though, or add a pandas docker image; up to you.

I think I have just snakemake-minimal installed which doesn't come with all the bells and whistles. I'll probably go with the docker image route.

resolved with bd4c83c40


Swift 5.2 (Xcode 11.4b) support

I'm sure this is on your radar already. Xcode 11.4 includes Swift 5.2 and the current release was built with Swift 5.1.2.
Thanks, as always, for all the hard work!

Yes, and actually the next build of AudioKit will enable Swift library evolution, which in theory should make the framework automatically compatible among future versions of Swift.

🙌You all rule. Thanks!

Hi, the instructions (https://github.com/audiokit/AudioKit/blob/master/Frameworks/README.md) are updated? Trying to import to a new project but I get module not found for audiokit, I've double checked the release notes and issues here which seems that Xcode 11 / swift 5.1 is supported. So it seems that there's something I don't know about or can't find docs about it. Thank you!

@heldrida You're probably missing a crucial step. Where are you getting AudioKit from? You either need to manually build the frameworks with the build_frameworks.sh script or use a binary distribution (either via the zips or through CocoaPods) and then make sure your project is referencing the files in the correct location.

@megastep thanks for looking! I've tried the binary version available in the instructions; also build it myself without success (https://stackoverflow.com/questions/61212246/how-to-include-audiokit-4-in-a-new-project-xcode-11-and-swift-5-1)

Regarding your comment "then make sure your project is referencing the files in the correct location"
apart from the provided instructions, the latest version of Xcode places the "added framework" (as in "project configuration > general tab > frameworks, libraries and embedded content") in the directory "Frameworks > AudioKit.framework" (in the sidebar / Xcode navigator).

I just responded to your post on Stack Overflow. You should not try to embed static frameworks, so I suggest you try to disable that.

@megastep thanks for taking the time to help. I've tried that before and tried it again now, but still get the same issue No such module 'AudioKit', I'm afraid: Xcode Version 11.4 (11E146) and Apple Swift version 5.2 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)

Does it actually fail to build your project? Xcode is so buggy that sometimes it shows errors in the IDE that don't actually happen. Sometimes even restarting Xcode helps :(

I can open and build one of the example projects, let's say the "Hello world".
But I spent hours trying to run the most basic instructions for Xcode 11 (then updated to latest) and swift 5.1 (now 5.2, I think I started with 5.1), and no, it doesn't compile No such module 'AudioKit'

the only thing that is close to AudioKit is CoreAudioKit

I found a solution ( https://stackoverflow.com/questions/61212246/how-to-include-audiokit-4-in-a-new-project-xcode-11-and-swift-5-1/ )
Moved the file under the project root and changed the target and location to be relative to the project. I haven't fully tested but I don't get the "no such module audiokit" now. Not sure if this is a good practice. But guess not...

I've also tested by modifying the build settings, removed all sub directories to exclude in recursive searches extensions; and add the relative path where the audiokit.framework can be found to the framework search paths. The autocomplete works, but I still get the error  No such module 'AudioKit'. So, this far the only option that works is the comment before,


Made a new folder named switch

Made a new folder named switch containing a Python and CSV file. The code finds the counts of instances of a category, for example, it will find out how many companies were founded in a certain year.

In summary, this code reads data from a CSV file containing information about organizations, counts how many organizations were founded in each year, and then prints the year and count in ascending order of years.


Changed camera mode constants to bit flags. #538

Added FOLLOW_xxx and ORIENT_xxx constants that are bit flags, and redefined the values of existing constants in terms of these. While not bytecode compatible, this is source code compatible with normal usage of the existing constants.

I'm gonna close this PR as per https://github.com/mapbox/mapbox-plugins-android/issues/684#issuecomment-433947880 the functionality provided by the Location Layer Plugin is now part of the core Maps SDK (there's no need to add additional plugins) and the plugin is now deprecated. If this ticket is still relevant for the new LocationComponent, please cut a new PR on https://github.com/mapbox/mapbox-gl-native. Thanks!


Update README.md

Updates README.md for extension to include instructions for getting around 'The directory selected is not empty' error when saving Burp interface files.

Burp Suite gives an error when attempting to follow burp_extension/README.md to save the interface files because the target directory is not empty.
I know that including the interface files in the repo would require an update for every burp update, but, it would make the extension much easier to build/use.
I've updated the README for the extension to better explain how to get around this issue, but a much better solution would be to move the .java file to src/ and have it grab the interface files from API/burp/, or something.

Whoops, it turns out those instructions were broken in a couple of ways.  I ended up going a slightly different route with the instructions in the README, but thanks for the pull request.  (Agreed that a short build script that merges the dirs would be good to have, but I'm honestly not too likely to get around to it any time soon.)


[ISSUE #973] zookeeper registry

Impl ISSUE #973
Motivation
And zookeeper registry
Modifications
And zookeeper registry
Documentation
Does this pull request introduce a new feature?  yes

Does anyone approve it?

Well done！

please add the header for these files. @VNBear

copyright is a real headache o(╥﹏╥)o

@VNBear Hi, please merge this pr into registry-zookeeper branch.

@VNBear Hi, please merge this pr into registry-zookeeper branch.

ok, done


kubecm: 0.29.1 -> 0.30.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/sunny0826/kubecm/releases.
meta.description for kubecm is: Manage your kubeconfig more easily
meta.homepage for kubecm is: https://github.com/sunny0826/kubecm/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.30.0 with grep in /nix/store/3qpq0xwm066kgrk2la4486ldyp15p7ka-kubecm-0.30.0
found 0.30.0 in filename of file in /nix/store/3qpq0xwm066kgrk2la4486ldyp15p7ka-kubecm-0.30.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

kubecm

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3qpq0xwm066kgrk2la4486ldyp15p7ka-kubecm-0.30.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kubecm https://github.com/r-ryantm/nixpkgs/archive/aac47c9a7fbddbc542b21745d15633be33d4b4c1.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/aac47c9a7fbddbc542b21745d15633be33d4b4c1#kubecm

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3qpq0xwm066kgrk2la4486ldyp15p7ka-kubecm-0.30.0
ls -la /nix/store/3qpq0xwm066kgrk2la4486ldyp15p7ka-kubecm-0.30.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

kubecm

Maintainer pings
cc @qjoly for testing.

Result of nixpkgs-review pr 319088 run on aarch64-darwin 1

1 package built:

kubecm


Upgrade to Python 3.9 and related dependencies

Summary
This is related to Python 3.7 upgrade to 3.9. see https://github.com/UAL-RE/ReQUIAM/issues/170
When numpy 1.22 dropped support for Python 3.7, it creates a chain of reactions.

We use numpy and have to upgrade to Python 3.9 or later version
We use pandas 1.2.3 and tabulate 0.8.3. When upgrading to pandas 1.4.3, tabulate will have to be upgraded too.

Pandas shall go to 1.4.3 (latest version) (although pandas >=1.3.5 shall work)
tabulate shall go to 0.8.10 (required by Pandas 1.4.3)  (tabulate 0.8.3 is no longer working with pandas 1.4.3. , although tabulate >= 0.8.7 shall work)
Objectives
Migrate to Python 3.9 and related dependencies
Proposal

[x] Update setup.py
[x] Update requirements.txt
[x] Update .github/workflows/pypi-publish.yml
[x] Update .github/workflows/python-package.yml

/redata/commons/logger.py:
pandas_write_buffer(df: pd.DataFrame, log_filename: str):
df.to_markdown(buffer)
Note:
Version 1.4.3 reference: https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.to_markdown.html?highlight=to_markdown
Version 1.2.3 reference: https://pandas.pydata.org/pandas-docs/version/1.2/reference/api/pandas.DataFrame.to_markdown.html
No changes. so updating from Pandas 1.2.3 to 1.4.3 shall be no issue.


Add send_self method

In practice, often required a method to send messages itself to a component immediately.
This PR adds: send_self method and add a requirement for a mutable reference to send_back method.

I'd prefer if this was kept without mut. I've been creating Callbacks with send_back in the view method to pass them down as props to avoid that the Model gets too cluttered.

@davidkna Good point! I'll check it :ok_hand:

... but I haven't seen this needs in my work. Could you explain, why do you need callbacks in properties? You should prefer to use agents to communicate components.

@DenisKolodin I haven't used agents yet but I'll explore using them for this instead.
Being more familiar with react I've used callbacks to allow child components to notify their parents about changes related to props e.g. a child with an input informs the parent about a text change and has it update its state and rerender.

I have moved backward incompatible changes to a separate PR.

bors r+

Wait, how is send_self different from calling the update?

@madmaxio I think calling update by itself can't cause a rerender.

Nice, thx.


Class configuration not working

I'm setting up a smart-table, but I can't add a class to an entire column. I've got this configuration:
settings = {     columns: {       SERIENUMERO: {         title: this.translate.instant("invoices.NUMERO"),         type: 'text',         class: 'align-center'       },       TOTAL: {         title: this.translate.instant("invoices.TOTAL"),         type: 'text',         valuePrepareFunction: (cell,row) => row.TOTAL + " € ",       },       FECHA: {         title: this.translate.instant("invoices.FECHA"),         type: 'date'       },       EMPRESA: {         title: this.translate.instant("invoices.EMPRESA"),         type: 'string'       },       PDF: {         title: this.translate.instant("invoices.PDF"),         type: 'custom',         valuePrepareFunction: (cell,row) => row,         renderComponent: InvoicePDFButtonComponent       }     },     actions: {       add: false,       edit: false,       delete: false     },   };
But in the "SERIENUMERO" column I can't add the "align-center" class. It's courious, because if I check the HTML result code, I found the "align-center" class on the  of that column. But I want it in the entire column, not only on the header. Is this possible? Or this is a bug?

+1..

Same problem here

Same problem here

+1

Yeap, same problem in Angular 8.2.5 and version 1.5.0 from smart-table.

➕👍
Same problem here, class is only applied to  element i.e. Header of the Ng2SmartTable


[SecurityBundle] improve login error message

By @turbo-ele from https://github.com/sulu-cmf/SuluSecurityBundle/issues/35
currently: bad credentials

The text has been changed.


added bruno and filter functionality for particular user

@CodiumAI-Agent /review

PR Reviewer Guide 🔍

 ⏱ Estimated effort to review [1-5]
4

 🧪 Relevant tests
No

 🔒 Security concerns
- Sensitive Information Exposure: The JWT secret key appears to be hardcoded in several files, which could lead to security risks if the codebase is exposed. Use environment variables to manage the secret keys securely.

 ⚡ Key issues to review

Possible Bug: The use of jwt.verify without proper error handling in multiple places could lead to unhandled exceptions if the token is invalid. Consider wrapping these calls in try-catch blocks.

Code Duplication: Similar code for verifying JWT and fetching user details is repeated in multiple controllers. Consider creating a middleware or a utility function to handle JWT verification and user fetching to reduce code duplication and improve maintainability.

Error Handling: Several routes and middleware lack comprehensive error handling. Ensure that all possible errors are caught and handled appropriately to prevent the server from crashing and to provide meaningful error messages to the client.

Security Concern: Storing sensitive information such as JWT secret keys directly in the codebase as seen in the jwt.verify calls. It's recommended to use environment variables to manage such sensitive information securely.


Future goblin units

https://www.hiveworkshop.com/threads/hobgoblin.241873/

https://www.hiveworkshop.com/threads/goblin-bombardier.241877/

https://www.hiveworkshop.com/threads/goblin-rocket-trooper.135772/

https://www.hiveworkshop.com/threads/goblin-pyromaniac.135771/

https://www.hiveworkshop.com/threads/goblin-grenadier.48215/

https://www.hiveworkshop.com/threads/goblinfireworkerbackup.47788/


[bug] Account Action menu has invisible UI elements

In the Account Action menu, due to the TopLevelContainer Control node having Top Level and Clip Children enabled, the UI elements are invisible.
If this is unintentional, I've prepared a PR that fixes the issue, otherwise, please reject the PR, linked below

In lieu of actually linking the PR to this issue, which I seem to not have the permission to do, the url to it is https://github.com/V-Sekai/vsk_ui_demo/pull/2


Do not use local-timezone dates for doing date to string conversions to specific timezones.

This should not change any general behavior, but fixes issues when you try to insert dates which are within your timezone offset of a daylight saving time switchover time.
Using the locale-specific Date accessor functions is certainly not valid because, if your local timezone includes daylight saving time, there is no possible Javascript date value which could return the string, for instance, "2015-03-08 02:30".
Instead, use the getUTC methods of the Date object after simply adjusting the timestamp by the desired timezone offset.
I had difficultly understanding what in the world the test_timezone.js test was doing, so I wrote a new one. The new test is specifically:
No matter what date is used, no matter what system timezone, no matter what node-mysql timezone, no matter what server-side timezone, if you insert a Javascript Date object, you should get the same Date object back (this was previously failing if that date object happened to be near daylight saving time boundaries in the local system timezone).
Additionally, the string representation of the date in MySQL should be in the timezone specified by the node-mysql timezone (I believe that is what the old test was trying to check).  As far as I know the server-side MySQL TIME_ZONE variable doesn't affect DATETIME objects (however it does affect TIMESTAMP objects, which would currently fail these same tests, but that's probably a more significant change for another PR another day...).
After doing all of this, I went back to read through the old test_timezone, and saw it was suffering from the same general issues as SqlString.js - it was using the local timezone string representation of a date to store arbitrary dates (that typeCast function would just generate an invalid date object if run during one of the selected timezone offsets from 2:30am on the day daylight saving time kicks in, among other problems).
Rule of thumb with Javascript dates: if someone is calling .getTimezoneOffset() on a date object, they're probably doing it wrong.
This should fix #1045

Thank you so much! Sorry it took me a while to get back to you. So oddly the test you add does not fail with the current code (see Travis CI build https://travis-ci.org/felixge/node-mysql/builds/74812812). Would it be possible to include a test that fails without your changes and passes with them?

So, my test fails on the current code depending on what timezone the system you're running the tests on (the previous tests would fail, I think, based on a combination of both system timezone and actual time of running the test).
I'll look into if there's a way to tell node/V8 (or some kind of mock) to use a specific timezone, so that the test would reproduce on any system.  If you know of a good way of doing that, please let me know =).

Ah, gotcha. I think the changes are definitely good :) My worry here is that if they are not at least failing on Travis CI without the change, we could very well break timezone handling again with the 3.0 refactor and not know since the tests won't fail.
I see you have SET TIME_ZONE="+00:00"-like commands in the tests. Is there not a way to just use that to set it to, say, Pacific?

Yeah, I completely agree, I do not want some other change to break this again =).  I was hoping that, since the tests previously failed, that maybe Travis CI's local timezone was one with daylight saving time, but perhaps only some hosts that run tests are (or if it's not in one of the US timezones, the particular date values to try inserting that would fail might not be in my dates I put in my test).
So, first, the SET TIME_ZONE commands change the timezone on the communications channel with MySQL, that was not the source of the bug (but I still think it's good to test that regardless of that setting that dates work).  The particular thing that was broken previously was based on the local system timezone (the timezone of V8 Date objects), not this.  Second, there's no MySQL command to set the communications time zone to Pacific without first inserting a whole bunch of stuff into the mysql.timezone tables.  There are shell scripts to populate those tables, but on my local vanilla installation of MySQL they tables were empty (or just had the handful or UTC timezones).

So, apparently, as far as I could tell, none of the date mocking libraries in Node handle mocking dates in a timezone with daylight saving time, so I had to write one.  Can see in the commit log of this branch that the the new tests failed on TravisCI on the old code (date_fix~1).  I think this PR is now ready to go.

Thank you so much!

This change is now published to npm as 2.9.0

Great, looks good!


parser should expand tilde

currently, if "~" is used to describe file or folder, it is not interpreted correctly. A solution is to use os.path.expanduser() python function in the parser.
Once done, remove all "expanduser" in the code.

Suggest to close : the shell (which invokes the program) is responsible for doing the expansion of ~. About the only time os.path.expanduser() is used is in very specific contexts (eg. reading of some config. files).


Will Preact stay API compatible with React 16?

We usually alias to Preact in production because of the payload savings, but now that we moved to React 16 which was officially released yesterday, preact-compat is down (for instance when returning arrays). That raises questions as to how far we can go with Fiber anyway, even if preact-compat can patch some minor things. But will it support returning arrays, numbers and strings as results, portals, and eventually async scheduling?

Hi there! All good questions. Preact-compat has to account for all of these changes, but some of them will remain in compat and not in core. Here's a list:

Returning Arrays from render(): yes, but this is a huge change for Preact itself. It will come, but it will take time.
Numbers & strings: this has always been supported in Preact.
Portals: I like the idea, but there are things like event bubbling redirection that might be unworkable within preact. We'll probably have to patch them into compat.
Async scheduling: this will absolutely be coming to Preact itself, and we'll ship a decent scheduler enabled by-default in preact-compat once it's available.

And hydrate
https://reactjs.org/docs/react-dom.html#hydrate

Waiting for hydrate since this is a breaking change for aliasing with Next.js

Returning Arrays from render(): yes, but this is a huge change for Preact itself. It will come, but it will take time.

Is there an issue to follow for that? #406 is closed. I don't know if it's appropriate to reopen that one or start with a new one: is there definitely agreement that it's for Preact rather than for Preact-compat?

@effulgentsia I think most people want Array returns in preact itself, but it's also quite possible doing so would necessitate a rewrite of the diff. In terms of ongoing discussion, @tkh44 was working some magic in #703.

@developit Watching this closely as Next.js is strictly packed with React 16. Is there any chance to help you out with missing API changes?

ReactDom.hydrate() will be tricky - ReactDom got quite the overhaul in React 16.

Does anyone have a rough timeline for React 16 compatibility? Particularly interested in support for the hydrate function.

Note, we added all of those in Preact X :tada: We even ship with a rough implementation fo Suspense but that is not ready for production yet :tada:


Returns empty array if no ids

Summary
Ensures .map() has an empty array / prevent initialise error.
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-38683
Checklist

Device Information
This PR was tested on:

Simulator: iPhone 12 / iOS 15
Simulator: Pixel 4 / Android 29

Screenshots

Release Note

Undefined array error corrected

Whoops yup, just pushed again.

Deferring QA.


VSCode freezes with NFS share when changing files

VSCode Version: Code 1.19.1 (0759f77bb8d86658bc935a10a64f6182c5a1eeba, 2017-12-19T09:35:14.671Z)
OS Version: Darwin x64 17.3.0
Extensions:

Extension
Author (truncated)
Version

Align
ste
0.2.0

(1 theme extensions excluded)

Steps to Reproduce:

nfs server
/etc# cat exports
/opt *(rw,fsid=0,insecure,sync,no_subtree_check,all_squash,no_wdelay,anonuid=0,anongid=0,sec=krb5p:krb5i:krb5)

nfs client (mac os)
mount -t nfs -o sec=krb5p,rw,soft,intr,sync,rsize=8192,wsize=8192,retrans=3,timeo=900,vers=3,actimeo=1,noatime,locallocks,rdirplus,resvport

Just open any files and click by Tabs, it will be freezed

I try VSCode half year ago, and this problem is exist, now it also exist.
Sublime Text - haven't such issue

Reproduces without extensions: Yes

This issue still happens with:
Version: 1.28.2
Commit: 7f3ce96ff4729c91352ae6def877e59c561f4850
Date: 2018-10-17T00:20:56.183Z
Electron: 2.0.9
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

However, I suspect that this is not really a bug in VSCode or node or any other dependency, but rather an NFS bug. Especially because this doesn't only freeze VSCode, but also any other applications that happens to access the changing files.
In our concrete case, linking a C++ executable from multiple object files freezes VSCode, the ld process, and some other random processes which happen to access the NFS share during the time until the NFS mounts have recovered. Frozen processes are in the D state (uninterruptible sleep) until the NFS mounts have recovered. This happens even when you start the linking process in a separate terminal from VSCode. Strangely enough, the problem doesn't appear to occur when compiling a single cpp file to an object file.
For the record, the NFS shares are mounted with the following options:
type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=krb5p,clientaddr=xxx.yyy.zzz.150,local_lock=none,addr=xxx.yyy.zzz.33)

We are building exploration builds that use a much newer version of our UI framework (Electron version 6.0.x). I wonder if this issue reproduces with one of these builds, could you try? Download:

macOS: Download
Linux (DEB): Download
Linux (RPM): Download
Windows: Download


Tracing: optimize implementation of find_trace_ids

Look into relying on aggregations (preferred) or custom search endpoint.

Closed via #2639.


Empty scope returned from SSO login in new Uber app v3.219.12

In the new Uber app released on 4 Nov, there is a critical breaking change.
During a SSO login, the granted scope is empty, even though the requested scope is indeed given.
In AccessToken.swift L108, scopesString now erroneously has %20 instead of space. Example: it should be profile ride_widgets instead of profile%20ride_widgets.

Looks like a url encoding issue, thanks for bringing this up, going to look into it right now

Found the issue with the encoding, working on a fix. In the meantime, your access tokens still work correctly for the requested scopes, it is just a bug with correctly notifying you which scopes were requested

Sorry on the delay here, SSO should be correctly returning scopes now as of Uber version 3.221
No SDK update is necessary


Refactor gistIoT to move general concepts to gistTop

E.g., gist:respondsTo: "The set of sensors that a controller is attached to."
Questions:

If all such terms that are useful in a general context are moved out of gistIoT, is there enough left to have a separate ontology module?
Should an upper enterprise ontology model such specialized domains as sensors?

Relates to the larger question in #201.

2020-03-24_ReviewOf_gist_IoT.docx
This is a doc with background and a list of classes and properties, helpful for the review.  Any comments?

This should be put on hold until we've determined whether to de-modularize gist. See #292.

Closed as part of #292, demodularize gist. No longer applicable.


component to select image

either:

[x] use already uploaded file from NC
[x] upload&use file

@badnames as @absurd-turtle is on holidays, can you please take this over?


rowTemplate messes up enableFullRowSelection/enableRowHeaderSelection

Hey there,
I just noticed that adding a typical rowTemplate such as the one given in http://ui-grid.info/docs/#/tutorial/317_custom_templates messes up enableFullRowSelection  and/or enableRowHeaderSelection.
Basically, I want to create a grid with selectable rows (without a checkbox) and an ng-dblclick action.
I just switched from ngGrid to ui-grid, so I might be missing something. Maybe I should use a different rowTemplate or something.

You probably need to start with the base row template, and check that all the selection etc works.  Then modify from that base, and keep checking that it's all working.

Indeed it, works as intended with the following rowTemplate content:
ng-dblclick="grid.appScope.onDblClick(row)" ng-repeat="(colRenderIndex, col) in colContainer.renderedColumns track by col.colDef.name" class="ui-grid-cell" ng-class="{ \'ui-grid-row-header-cell\': col.isRowHeader }\" ui-grid-cell
It would be useful to add this base row template to the Custom Template section of the tutorial.
Thanks anyhow!

@loykianos extracting the default templates and putting them up in the docs is on my plate. Thanks for confirming its usefulness! :)

+1

Please add tutorial on how to customize row template without loosing row selection.
http://plnkr.co/edit/4EpCvzRPXRxOoGvl1ktg?p=preview


Update flutter_map dependency to 6.0.x

The next version of flutter_map is coming soon, with breaking changes for all users and plugins!
Expected CHANGELOG: https://github.com/fleaflet/flutter_map/blob/release-prep/CHANGELOG.md
Likely to be merged PR with significant impacts: fleaflet/flutter_map#1615
Release prep PR: fleaflet/flutter_map#1632
New documentation (path liable to change): https://docs.fleaflet.dev/v/v6-1
Expected migration instructions, suitable for most users: https://docs.fleaflet.dev/v/v6-1/getting-started/migrating-to-v6
List of commits since v5 (more to come): https://github.com/fleaflet/flutter_map/compare/v5.0.0...master

Thanks for the heads-up @JaffaKetchup
All, we have 4 pull requests to get to 6.0:  #169 #177 #182 #184
I have limited time to get this in. It would be really helpful if you could all coordinate, agree on and review a single PR.

Just to note, v6.1.0 is now available. @greensopinion I'm happy to try to review one of the PRs, just possibly won't have time today.

Thanks Luke!
On Thu, Dec 7, 2023 at 11:29 PM Luka S @.***> wrote:

Just to note, v6.1.0 is now available. @greensopinion
https://github.com/greensopinion I'm happy to try to review one of the
PRs, just possibly won't have time today.
—
Reply to this email directly, view it on GitHub
https://github.com/greensopinion/flutter-vector-map-tiles/issues/175#issuecomment-1846682389,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEKDQ7SFYMZY3CWHF4XFVXDYIK6VJAVCNFSM6AAAAAA5TFMSTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBWGY4DEMZYHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

new version published, see example commit to upgrade


Add Agones Kubernetes API docs generator

Add gen-crd-api-reference-docs utility into build-image, generate Agones CRD reference html document, map this doc to existent docs structure.
Covers #409.

This is an initial commit. Some changes to the templates could occur in the future. Current look and feel:

Issue with resulting file position in Cloud Build:
Output to a file /go/src/agones.dev/agones/site/content/en/docs/Reference/agones_crd_api_reference.html
diff /workspace/site/content/en/docs/Reference/agones_crd_api_reference.html /tmp/generated.html

Locally I have for test-gen-api-docs: expected_docs := $(site_path)/$(REL_PATH) :
diff /Users/alexander.apalikov/go/src/agones.dev/agones/site/content/en/docs/Reference/agones_crd_api_reference.html /tmp/generated.html

Found an issue, I have added the special kubebuilder declaration in /pkg/apis/stable/v1alpha1/gameserver.go, which is redundant, like that:
// +kubebuilder:resource:path=gameservers

Reworked generation script it now handles the version in publishVersion shortcode.
Old code becomes expiredVersion with new base_version. Test now compares only what is in the middle of publishVersion with the output of go tool gen-crd-api-reference-docs.
Two calls to awk and one sed do the job.
We don't need to care about switching the versions on release process - it is automated for this file.

I think I need to add md instructions on how to use new make target gen-api-docs. It was created to work in a similar way to  make gen-install when we call this on each crd update and just git add the resulted .../Reference/agones_crd_api_reference.html. So basically two subsequent calls of 	$(MAKE) test-gen-api-docs would result in pass the test, but on CI if someone forgot to commit this html than test would fail.

Fixed one issue, there was a commit-id in a default template. So I removed it, so now different git commit would generate the same html.
https://github.com/GoogleCloudPlatform/agones/pull/645/files#diff-b75745dde8c5e52ecb85780a42ac3669

Apologies - looks like I never submitted those comments :/ they've been sitting there forever. But otherwise, this is good to go.

Merged master, fixed publishVersion and Makefile parameter.


Need cover with unit tests

I do not really feel comfortable without unit tests, especially when we getting more and more new contributions from the community, which is much appreciated.
So I'd like to cover sensitive functionality like packaging with tests.

I think if a comprehensive list of what needs to be covered (usecases/scenarios) is provided, it might make it easier for people to contribute to some unit tests?
As it stands I personally don't know what "packaging" should do exactly.

I think you are making two very good points. To help contributors
participate we could have a scenario list of typical situations that need
to be tested (I have a few in mind).
And then, a simple document explaining how this plugin works could be of
value too.
I wonder where this should live ? As MD in the repo ? In a GH wiki ?
Le mer. 29 sept. 2021 à 02:43, Sam Chung @.***> a
écrit :

I think if a comprehensive list of what needs to be covered
(usecases/scenarios) is provided, it might make it easier for people to
contribute to some unit tests?
As it stands I personally don't know what "packaging" should do exactly.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/floydspace/serverless-esbuild/issues/189#issuecomment-929728512,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJFT5EN7KW2UTX35KOEDPLUEJOK3ANCNFSM5EJDXTEA
.

I started preparing a wiki page and realized that the most common scenarios are well defined in the readme. So we can take basic test cases from there. For instance, a case when no configuration is required would be tested like we're having correct default options passed to esbuild's mocked build function and that we are not running packing logic.
Anyway, I will try to describe each scenario in more detail in the wiki and describe some test cases in AAA format, like what are inputs, what we do, and what we expect.
@olup feel free to add your ideas in the wiki.

I had a little think about this - maybe if we don't get unit test coverage we can at least setup some integration tests with snapshots. Anybody have a good idea on how we an achieve this?


Update subscription-creation-schema.md

In order for an event to fire when a specific file enters a container, the URI /blob is required. In the documentation, this was missing. I spent quite some time trying to figure out why my events were not firing. Once I added the /blob before the literal filename, all was well.

#sign-off


rgbscript: marquee

adds a marquee function
has moving "lights" with a count of lights+spaces
can select the color of the lights
has fadein depth from outside
handles corners cleanly so that the lights look even
tested different sizes on the devtool

So .. codacy is telling me that using 'var ' on a var is bad form.. and I should be using 'let' .. which makse sense .. however; our code interpreter in qlcplus doth not like 'let ' and in fact throws really.. really annoying error:
"marquee.js" Error at line: 99 , column: 7 : "Expected;', ;'"
Which tool me going to dinner and complaining to my duck before i figured out what had changed :) Hope this passes all the rest as I think it's a nice script that we're using on this years show.

Coverage: 28.078%. Remained the same when pulling 640f33dfee8a6318b3ebf9029ac7d164cc1c9e66 on sandinak:rgbscripts into b802ff94e9525024bed44597a39e8c55c64c6781 on mcallegari:master.

Hey can we please close #1301 and #1302 before throwing more stuff on the table? Thanks

Closed the other two .. one was a dupe .. one needs re-write .. this one is ready; but I can't merge because of Coacy.

Thanks 👍


⚠ Bofrost.at has degraded performance

In 01cb193, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1937 ms

Resolved: Bofrost.at performance has improved in 8d881af after 20 minutes.


Update prom module to use one query per metric instead of label in single query

pod_energy_stat and node_energy_stat will be removed from kepler exporter metrics soon.
According to https://sustainable-computing.io/design/metrics/#kepler-metrics-overview, kepler will export metric with the following format for aggregated value.
kepler_[container|node]_[metric]_total

The new prom should filter the kepler prefix and compute current value from aggregated value.
Note: some metrics are still in progress. Track https://github.com/sustainable-computing-io/kepler/issues/495
Signed-off-by: Sunyanan Choochotkaew<EMAIL_ADDRESS>

should be fine with https://github.com/sustainable-computing-io/kepler-model-server/pull/77.


To Do List

Create a CLI To Do List

https://github.com/201flaviosilva-labs/play-code/commit/9a61b9704f17b72c79a57cf45ec462630aaafde6


Add back button to top of View Application page

Steps to Reproduce: log in as client -> click "My Applications" -> Click "View Application"
Issue: There is no back button at the top of the View Application page - this is especially troublesome for longer forms where you have to scroll for a very long time until you can reach the back button at the bottom of the page
Resolve by: for now, moving the back button from the bottom left to the top left corner of the page (above the progress bar). @leonna26 could we update the design to account for this problem?

Fixed with #174.


[eas-cli] Add support for asset excludes

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.

Why
Closes ENG-6894.
Server component: https://github.com/expo/universe/pull/10875
Depends on: https://github.com/expo/eas-cli/pull/1488
EAS Update currently has an asset limit of 1000. More than this creates a poor UX for end-users as they must then download a lot of assets on their mobile network. But, some apps using classic updates have more than this. We need a solution to allow them to move to EAS Update. This PR provides that solution.
The way this is going to work is:

configure project eas.json to have update.assetExcludePatterns (array of globs)
eas-cli will read that config and exclude matching assets from upload process
eas-cli will indicate to www that certain assets were excluded so that www knows not to try to create edges for them (this PR)

How

Add update section to eas.json config
Read that config during asset upload
Exclude assets matching the config from upload
Report to the server during publish that certain assets were excluded.

Test Plan
In combination with https://github.com/expo/universe/pull/10875:

create app
add updates.assetExcludePatterns to eas.json
add an asset that matches the glob
run ~/expo/eas-cli/packages/eas-cli/bin/run update --branch preview --message "testing3", see that it reports that assets were excluded and see the update doesn't have the asset (note that this update won't work in expo go).

/changelog-entry new-feature Add support for EAS Update asset excludes

Going to close this for now while I investigate whether this should be part of expo export instead of purely in EAS CLI.

@wschurman any news on this one? We're blocked heavily with the 1000 updates limit and it seems Expo is automatically pulling svg assets as well, even if we always require them with Platform.OS === 'web' ? require(svg) : require(png) pattern.


Correcting the number of flop for MatMul

Cf https://github.com/tensorflow/tensorflow/issues/19746
Given two matrices A of shape (m, p) and B of shape (p, q), the number of floating point operations (FLOP) should be mq(2p-1).
Calculating the number of FLOP using tensorflow's profiler gives 2mqp instead of mq(2p-1).
import tensorflow as tf
g = tf.Graph()
with g.as_default():
    m, p, q = 25, 16, 9
    A = tf.Variable(tf.zeros([m, p]))
    B = tf.Variable(tf.zeros([p, q]))
    C = tf.matmul(A,B)

    flops = tf.profiler.profile(g, options = tf.profiler.ProfileOptionBuilder.float_operation())
    if flops is not None:
        print('FLOP should be', m * q * (2 * p - 1))
        print('Calculated FLOP', flops.total_float_ops)

There is a test that fails:
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
-----------------------------------------------------------------------------
/b/s/w/ir/run/bazel-out/k8-opt/bin/tensorflow/python/kernel_tests/matmul_op_test.runfiles/org_tensorflow/tensorflow/python/kernel_tests/matmul_op_test.py:231: ComplexWarning: Casting complex values to real discards the imaginary part
  m * k).astype(dtype).reshape([m, k])
/b/s/w/ir/run/bazel-out/k8-opt/bin/tensorflow/python/kernel_tests/matmul_op_test.runfiles/org_tensorflow/tensorflow/python/kernel_tests/matmul_op_test.py:235: ComplexWarning: Casting complex values to real discards the imaginary part
  k * n).astype(dtype).reshape([k, n])
sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss2018-06-06 17:48:56.892095: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2 AVX
.........................ssssssssssss........................ssssssssssssF.....................................................................................................................................
======================================================================
FAIL: testTransposedStatistics (__main__.MatMulStatsTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/b/s/w/ir/run/bazel-out/k8-opt/bin/tensorflow/python/kernel_tests/matmul_op_test.runfiles/org_tensorflow/tensorflow/python/kernel_tests/matmul_op_test.py", line 156, in testTransposedStatistics
    self.assertEqual(7200, flops)
AssertionError: 7200 != 6975
----------------------------------------------------------------------
Ran 268 tests in 3.490s
FAILED (failures=1, skipped=85)

@drpngx The unit test is wrong, I corrected it.

XLA error: (binary_ops_test)
2018-06-08 18:22:19.585682: E tensorflow/stream_executor/cuda/cuda_driver.cc:903] failed to allocate 4B (4 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY

MacOS error:
==================Model Analysis Report======================
Doc:
scope: The nodes in the model graph are organized by their names, which is hierarchical like filesystem.
requested bytes: The memory requested by the operation, accumulatively.
output bytes: The memory that is output from the operation (not necessarilty allocated by the operation)
peak bytes: The peak amount of memory that the operation is holding at some point.
residual bytes: The memory not de-allocated after the operation finishes.
Profile:
node name | requested bytes | peak bytes | residual bytes | output bytes
_TFProfRoot (--/80.00KB, --/80.00KB, --/80.00KB, --/80.00KB)
  mul (80.00KB/80.00KB, 80.00KB/80.00KB, 80.00KB/80.00KB, 80.00KB/80.00KB)
  _retval_mul_0_0 (0B/0B, 0B/0B, 0B/0B, 0B/0B)
======================End of Report==========================
Parsing Inputs...
=========================Options=============================
-max_depth                  10000
-min_bytes                  0
-min_peak_bytes             0
-min_residual_bytes         0
-min_output_bytes           0
-min_micros                 1
-min_accelerator_micros     0
-min_cpu_micros             0
-min_params                 0
-min_float_ops              0
-min_occurrence             0
-step                       -1
-order_by                   micros
-account_type_regexes       .*
-start_name_regexes         .*
-trim_name_regexes
-show_name_regexes          .*
-hide_name_regexes
-account_displayed_op_only  true
-select                     bytes,output_bytes,peak_bytes,residual_bytes
-output                     stdout:
==================Model Analysis Report======================
Doc:
scope: The nodes in the model graph are organized by their names, which is hierarchical like filesystem.
requested bytes: The memory requested by the operation, accumulatively.
output bytes: The memory that is output from the operation (not necessarilty allocated by the operation)
peak bytes: The peak amount of memory that the operation is holding at some point.
residual bytes: The memory not de-allocated after the operation finishes.
Profile:
node name | requested bytes | peak bytes | residual bytes | output bytes
_TFProfRoot (--/80.00KB, --/80.00KB, --/80.00KB, --/80.00KB)
  mul (80.00KB/80.00KB, 80.00KB/80.00KB, 80.00KB/80.00KB, 80.00KB/80.00KB)
  _retval_mul_0_0 (0B/0B, 0B/0B, 0B/0B, 0B/0B)
======================End of Report==========================
..
======================================================================
FAIL: testComplexCodeView (__main__.PrintModelAnalysisTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Volumes/BuildData/tmpfs/bazel_output/_bazel_kbuilder/d1b2600cd78e76a92812a06683f5de10/execroot/org_tensorflow/bazel-out/darwin-opt/bin/tensorflow/python/profiler/model_analyzer_test.runfiles/org_tensorflow/tensorflow/python/profiler/model_analyzer_test.py", line 240, in testComplexCodeView
    self.assertLess(145660, tfprof_node.total_float_ops)
AssertionError: 145660 not less than 140929L
----------------------------------------------------------------------

Are the stats used to make memory projections?

The failed test looks like it just needs to be updated with the new number; not sure about the OOM error. @hawkinsp might have a better idea?

Nagging Assignee @drpngx: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @drpngx: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@hawkinsp - Any chance you want to help out here? Not sure how the original test value was calculated, but this contribution is waiting on some assistance in fixing the test.

@karmel The XLA failure looks like a flaky test, I very much doubt it has anything to do with this change.

Great, thanks. Approving, in that case.

My pleasure.

Hm. Not sure why this didn't ever complete. Rerunning tests.

I would like to push back on this change for the following reasons:
It is not clear if the fix is even correct in practice. I mean that is that the flops ARE mq(2p-1). I agree this is the case on the white board but, the following very reasonable implementation:
sum = 0
for i=0 to p
sum += a[i] * b[i]
has 2mpq FLOPS and not mq(2p-1)

The change is incomplete (i.e. it creates inconsistencies). The flop computation of conv2d, depthwise convolutions and possibly others where not fixed. I think that having slightly inflated consistent flop computation is  better than having two formulas giving different results.

This change is negligible when used for diagnostic reasons (unless one is multiplying very small matrices), but brakes some code that actually uses these numbers.


Better version of Footer

Change the Footer's design to this.

Links:
Github
Twitter

Hii @Utkarshn10 , I would like to work on this issue.

Hey @krushnarout thanks for contributing to Focusly. Issue assigned.


MB-15203 fix playwright expect await

Jira ticket for this change
Summary
Ensure we await all async expectations in playwright tests. This reduces flakiness.
Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Run the e2e tests
make e2e_test

Messages

:book:
:link: MB-15203

  Generated by :no_entry_sign: dangerJS against 6feb276ce90573544df086669e849a9f1814bf42


[Feature]: Gitlab regex comparison expression is not correctly replaced

What operating system are you using?

[x] Linux
[ ] macOS
[ ] Windows

What version of the tool are you using?
gh version 2.20.2 (2022-11-15)
gh actions-importer github/gh-actions-importer v1.0
actions-importer/cli v1.0.14322
What happened?
When importing Gitlab CI configurations the regex comparison expression =~ is not replaced. This expression is currently not supported by GitHub. We could instead replace it to something like contains(). We could get this even further when using startsWith() or endsWith() depending on the regex values configured.
Example:
# original expression:
  except:
    refs:
      - master
    variables:
      - $CI_COMMIT_MESSAGE =~ /^Merge tag.*/

# output:
if: !(github.ref == 'refs/heads/master' && $CI_COMMIT_MESSAGE =~ /^Merge tag.*/)

# desired output:
if: !(github.ref == 'refs/heads/master' && contains(github.event.head_commit.message, 'Merge tag'))

# or even better
if: !(github.ref == 'refs/heads/master' && startsWith(github.event.head_commit.message, 'Merge tag'))

(The replacement of $CI_COMMIT_MESSAGE is separated to #8)
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks for opening this! At this time, we don't have plans to support converting regexes to context expressions automatically within Actions Importer. The reasoning is that the simpler cases may be possible (e.g. the examples you shared above), but regexes are quite a bit more flexible than context expressions and it is not feasible to programmatically handle all scenarios. Actions Importer does not attempt to achieve a 100% conversion rate for existing pipelines, but rather an 80% rate. There should be an expectation that any output of the product should be reviewed and tweaked manually, prior to taking the output on as a production workload. Unfortunately, Regex conditions coming from GitLab fall into that category.

Any workflow that is converted by the GitHub Actions Importer should be inspected for correctness before using it as a production workload. The goal is to achieve an 80% conversion rate for every workflow, however, the actual conversion rate will depend on the makeup of each individual pipeline that is converted.

☝ from the docs


vue.runtime.esm.js:1897 TypeError: Cannot read property 'token' of null

TypeError: Cannot read property 'token' of null
    at a.openJitsi (App.vue:71)
    at re (vue.runtime.esm.js:1863)
    at a.n (vue.runtime.esm.js:2188)
    at re (vue.runtime.esm.js:1863)
    at a.Ln.t.$emit (vue.runtime.esm.js:3903)
    at a.click (VBtn.ts:163)
    at re (vue.runtime.esm.js:1863)
    at HTMLButtonElement.n (vue.runtime.esm.js:2188)
    at HTMLButtonElement.Qi.o._wrapper (vue.runtime.esm.js:6961)
oe @ vue.runtime.esm.js:1897
ie @ vue.runtime.esm.js:1888
ne @ vue.runtime.esm.js:1848
re @ vue.runtime.esm.js:1871
n @ vue.runtime.esm.js:2188
re @ vue.runtime.esm.js:1863
Ln.t.$emit @ vue.runtime.esm.js:3903
click @ VBtn.ts:163
re @ vue.runtime.esm.js:1863
n @ vue.runtime.esm.js:2188
Qi.o._wrapper @ vue.runtime.esm.js:6961

Run inside docker container.

sso is running under sso.domain1.com
jisti is running under meet.domain2.eu
this project is running under auth-meet.domain2.eu

The SSO login is working, but on the auth page
a. the Room is not automatically filled inside the form
b. when doing manually, this error occurs

Hi, this error occures when the config could not be loaded from the server.
Are there any other errors in the console/network tab before this one?

Hi Fabian, you mean the config from the keycloak server?

Yey I found, its because:
2022-08-26 16:47:43,886 WARN  [org.keycloak.events] (executor-thread-97) type=LOGIN_ERROR, realmId=master, clientId=jitsi, userId=null, ipAddress=79.***.***.70, error=invalid_redirect_uri, redirect_uri=http://auth-meet.***.eu/api/config?auth_callback=1

It is redirecting to http, even I set everything to https.
        environment:
          JITSI_SECRET: "***"
          DEFAULT_ROOM: "meet"
          JITSI_URL: "https://meet.***.eu/"
          JITSI_SUB: "meet.***.eu"

omg its working now. It was a network issue. the jitsi lxc container could not reach the sso lxc. :)


Update Developer Guide for add_contact feature

Maybe we can try to style the box titles in the sequence diagrams to be more contrast from their background colors. Overall, LGTM!

Maybe we can try to style the box titles in the sequence diagrams to be more contrast from their background colors. Overall, LGTM!


"Added UserContext and Loader components to Signup page"

This commit updates the Signup component to use the UserContext and Loader components from the project's Context and Loader directories. The UserContext is used to manage
Description

The SignUp page component had issues with Loader component and after the successful completion of registration the token was not updated to the UserContext which led to blank screen was fixed.

Resolves: #53
Checklist

Before submitting this pull request, kindly verify that the ensuing checkpoints have been reached.

[x] Have you adhered to the repository's defined coding convention rules?
[ ] Have you updated the 'documentation.md' file with the method/function documentation?
[x] Have you sent a message along with the result or response?
[x] Have you used the try-catch technique?
[ ] Has the method/class been added to the documentation (md file)?

Screenshots

Uploading a screenshot illustrating the approach you developed for validation is required.

I certify that I have carried out the relevant checks and provided the requisite screenshot for validation by submitting this pull request.
I appreciate your contribution.

@EAGLEARCHER Please resolve conflicts


Add new term persistent atrial fibrillation

closes https://github.com/monarch-initiative/mondo/issues/7887

Closing since I can not sort why there are changes to some imports in this PR.


Configure sidecar for 50% dead letters

I want some real dead letters to mess with, trying it out here first.

No longer needs this for testing.


Cleaning up / refactoring Marlin

Our Marlin code base deserves some cleaning up. We still have left-overs from Marlin's initial AHP which are not necessary due to the coboundary sumcheck, and there are some structural improvements by arkworks we might want to take over.
In short,

we can get rid of individual degree bounds in the AHP, and rebrand AHP to an algebraic oracle proof instead (to be in alignment with our paper),
we could move constraint system related traits (i.e. the large part of the ahp/constraint_system.rs file) to ginger  (arkworks seems to have done that), and
we should move the matrix arithmetization to the indexer submodule.

Beyond that, I recommend to switch to the Lagrange kernel instead of the UnnormalizedBivariateLagrangePoly, even if it comes slightly costlier in circuit. This is mainly for the following reasons.

The matrix arithmetization step becomes much simpler (we simply index the non-zero entries of the plain R1CS matrices ), and
we are in full alignment with our paper and the security analysis therein.

If we keep with the generalized derivative, I at least opt to remove the double transposition of matrices: The indexer outputs the transpose of the representation with respect to the (non-normalized) kernel (to be in alignment with the lincheck from Fractal), and then again transposes the arguments for Marlin's t-polynomial in the inner sumcheck.
For details see the TODO's I have pushed in a separate branch inline_docu for our cargo doc.

P.S.: As we need to stay compatible with the mainchain verifier, I'd opt to provide two versions of Coboundary Marlin in our repo: coMarlin, which is in full alignment with our paper, and coMarlin_gd which works with the generalized derivative.


code formater tool

I have to disable auto-format function of my code editor when I modify code to keep the code style, a code formatter may help with this.
Clang-tidy is a good choice.

Thanks for your feedback! Do you mean the C++ code style of the project? Since I'm using Xcode on macOS, I can imagine that many other IDEs have issues with how Xcode handles .cpp/.hpp files...

Yes, I mean the c++ code style.According to doc, it eems XCode does't have a integration with clang-tidy.
Clang-tidy can be integrated with cmake, you want to have a try.


Contributors

Added contributors to the readme

Hi, I won't have time to get to this...maybe someone else can pick it up, sorry I added names in a bit of a rush.


Always queue artifact transform executions

A while ago we added an optimization to improve sync times with Android projects: https://github.com/gradle/gradle/pull/3498. The optimization removed the overhead of executing through the BuildOperationExecutor, and by doing this removed 7% of sync time:

Only create a build operation if we don't already
have a cached value in memory. Otherwise we end up
flooding our build operation infrastructure with
synchronization requests and also create lots of
garbage descriptor objects.

The optimization added some complexity at the time, but that complexity grew considerably when we also added parallel execution of transforms via BuildOperationQueue.
This is the current form of the optimization:
https://github.com/gradle/gradle/blob/78cebdf34007e2c12e6da5a3b2ae6b1fbf3d3ff1/subprojects/dependency-management/src/main/java/org/gradle/api/internal/artifacts/transform/TransformingAsyncArtifactListener.java#L78-L87
It would be desirable to remove this complexity as it blocks some improvements around snapshotting and unified execution of different work types in Gradle.

cc: @gradle/execution

Simply removing the optimization is a no-go, as with the parallel execution of transforms the resulting regression is large: above 70% in one measurement with Santa Tracker sync: https://github.com/gradle/gradle/commit/c55e7840e8e8c27d3738e6abb0eef0c288f6a538
Speed Results for test project 'largeAndroidBuild' with tasks : we're slower than 6.8-commit-7651a88fcbc with 99% confidence.
Difference: 5.598 s slower (5598 ms), 72.66%
Current Gradle median: 13.302 s min: 13.018 s, max: 14.122 s, se: 271.87 ms}
    > [13.018 s, 13.478 s, 13.505 s, 14.122 s, 13.441 s, 13.449 s, 13.083 s, 13.082 s, 13.313 s, 13.387 s, 13.582 s, 13.412 s, 13.172 s, 13.25 s, 13.234 s, 13.191 s, 13.291 s, 13.952 s, 13.199 s, 13.137 s]
Gradle 6.8-commit-7651a88fcbc median: 7.704 s min: 7.376 s, max: 8.672 s, se: 367.19 ms}
    > [8.128 s, 8.171 s, 8.101 s, 8.672 s, 7.721 s, 7.891 s, 7.95 s, 7.619 s, 7.654 s, 7.669 s, 8.527 s, 7.687 s, 7.725 s, 7.517 s, 7.441 s, 7.465 s, 7.376 s, 8.285 s, 7.47 s, 7.462 s]

(TeamCity build)

It seems that the overhead in a small part does indeed come from the build operation infrastructure, mostly because we are now locking more on the BuildOperationQueue.
However, the majority of the overhead seems to come from extra locking in LogToClient and DaemonConnectionBackedEventConsumer. See samples captured for different stacks with and without the optimization:

(Google sheet)
There is also much more data allocated (about 50% more), mostly due to the events allocated serialized by SynchronizedDispatchConnection (that is triggered from LogToClient and DaemonConnectionBackedEventConsumer).

I've printed out the events going through LogToClient, and indeed there are much more progress events produced when the optimization is disabled:
$ ls -lh
total 10496
-rw-r--r--  1 lptr  staff   2.7M Sep 23 11:58 event-trace-BAD.log
-rw-r--r--  1 lptr  staff   2.1M Sep 23 11:56 event-trace-GOOD.log

event-logs.zip
There are 3819 ProgressComplete events in the GOOD variant (with optimization) while 6304 such events in the BAD variant (when the optimization is removed).

It is unlikely that these events are useful to any client. It would be great to be able to avoid dispatching them. Doing so would have a number of advantages:

we could remove the workaround in introduced in https://github.com/gradle/gradle/pull/3498,
we would further decrease the amount of memory allocated by log dispatching,
we could revert back to using a blocking queue in LogToClient, which make profiling Gradle nicer, but is currently blocked because of the slight regression it introduces due to the high volume of events dispatched (see https://github.com/gradle/gradle/pull/14153).

Removing the progress events emitted by transforms does have an effect, but not enough:
result.assertCurrentVersionHasNotRegressed()
|      |
|      java.lang.AssertionError: Speed Results for test project 'largeAndroidBuild' with tasks : we're slower than 6.8-commit-06049431f1b with 99% confidence.
|      Difference: 4.913 s slower (4913 ms), 62.27%
|        Current Gradle median: 12.802 s min: 12.649 s, max: 13.691 s, se: 282.21 ms}
|        > [12.89 s, 12.933 s, 12.79 s, 13.691 s, 12.649 s, 12.815 s, 12.772 s, 12.961 s, 12.696 s, 12.739 s]
|        Gradle 6.8-commit-06049431f1b median: 7.89 s min: 7.633 s, max: 8.674 s, se: 282.47 ms}
|        > [8.072 s, 8.156 s, 7.966 s, 8.674 s, 7.811 s, 7.877 s, 7.836 s, 7.633 s, 7.673 s, 7.902 s]
|
|
|        at org.gradle.performance.results.CrossVersionPerformanceResults.assertCurrentVersionHasNotRegressed(CrossVersionPerformanceResults.groovy:86)
|        at org.gradle.performance.regression.android.RealLifeAndroidStudioMockupPerformanceTest.get IDE model for Android Studio(RealLifeAndroidStudioMockupPerformanceTest.groovy:45)

OK, so I think the result after removing TransformOperation's progressDisplayName() is understandable: we are still generating progress events, only without the display name. This seems to remove some of the locking, but has no effect on the most congested part, which is LogToClient...dispatch():

What I don't understand here is how LogToClient getting blocked causes the increase in build time: it all should happen on a background thread. It surely doesn't take 12 seconds by itself to push those messages back to the client?

Could it be that most of the execution time is caused by GC?
 The total of GC adds up to 12.57 seconds with a total execution time of 13.69 seconds:

This is how the same looks like with the optimization enabled: full of GC, but to a slightly smaller extent. GC time adds up to 9.92 seconds, with a total execution time of 10 seconds.

I tried running with -Xmx12g instead of -Xmx5g, but it didn't change much. There are somewhat fewer GC runs, but the memory gets freed up when it reaches 4GB anyway.
With optimization removed (12.9 seconds):

Original state with optimization in place (10 seconds):

The execution times stay the same

In both cases there's significantly more GC activity, due to significantly more allocation without the optimization. However, I doubt that alone would account for much in the way of wall-clock execution time.
The other difference I found was around lock contention. There are a few important locks:

DefaultResourceLockCoordinationService.withStateLock() that worker threads lock on. In both scenarios executor threads are locked on this for 2.5-4 seconds. There are a few hundred milliseconds more locking on this with the optimization removed, where a handful of build operations threads get tangled in during some of the invocations, but I doubt it is significant for the total build time.
DefaultWorkerLeaseService.getWorkerLease() is almost never locked on with the optimization in place, but is locked on for a few hundred milliseconds by build operation threads when the optimization is removed. Again, I don't think this is significant.
and then there is SynchronizedDispatchConnection.dispatch() and flush() that block the single Asynchronous log dispatcher thread (and sometimes also Thread-XXXX the thread of DaemonConnectionBackedEventConsumer.ForwardEvents). With the optimization we see total blocking times 1.32-1.75 seconds (max blocking time 40-50 ms), while without the optimization these jump to 4.96-5.82 seconds (max blocking time 112-193 ms).

That last one, the one locking on the connection looks like the most significant thing. But it still feels strange that blocking the daemon communication more could slow things down so much.
The flip side is if we can reduce the communication, and with that reduce the lock contention from the current 1.32-1.75 seconds to something much smaller, perhaps that will show up in the total build time in a significant way, too.

The increased lock contention is clearly visible when comparing the blocking times (pink lines) for Asynchronous log dispatcher* threads:

(Left is with optimization removed, right is with optimization.)

I've written up findings here: https://docs.google.com/document/d/1GsumRV17dnfQwuSEhBtE3V2nwYLW2uhpEV5AgcsfeDs/

The execution engine now supports identity caching, so we won't be doing this.


[Project Moon TRPG] New features update

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

New update:
-Distortion view and sheet behaviors
-Plain-text import/export of data + option for automatic save/load of data when Distorting
-UI adjustments and fixes

Character Sheet Info Roll20 Internal Use only.


Please implement .into::<write_fonts::tables::whatever>() for all read_fonts::tables::Whatever

We recently wanted to modify a name table entry in a font in fontspector, and this is what we had to do:
        let new_record = NameRecord::new(
            3,
            1,
            0x0409,
            NameId::LICENSE_DESCRIPTION,
            OFL_BODY_TEXT.to_string().into(),
        );
        let mut new_records: BTreeSet<NameRecord> = name
            .name_record()
            .iter()
            .filter(|record| record.name_id() != NameId::LICENSE_DESCRIPTION)
            .map(|r| {
                #[allow(clippy::unwrap_used)]
                NameRecord::new(
                    r.platform_id(),
                    r.encoding_id(),
                    r.language_id(),
                    r.name_id(),
                    r.string(name.string_data())
                        .unwrap()
                        .chars()
                        .collect::<String>()
                        .to_string()
                        .into(),
                )
            })
            .collect();
        new_records.insert(new_record);
        let new_nametable = Name::new(new_records);
        let new_bytes = FontBuilder::new()
            .add_table(&new_nametable)
            .unwrap()
            .copy_missing_tables(font)
            .build();

This would be much more fluent if we could easily turn a read_fonts::NameRecord into a write_fonts::NameRecord:
        let new_nametable = Name::new(name
            .name_record()
            .iter()
            .map(|r| {
				let mut record = r.into();
				if record.name_id() == NameId::LICENSE_DESCRIPTION { record.string =  OFL_BODY_TEXT.to_string().into() }
				record
            })
            .collect()
        );
        let new_bytes = FontBuilder::new()
            .add_table(&new_nametable)
            .unwrap()
            .copy_missing_tables(font)
            .build();

which is much better.

So this does exist for at least most tables (but not records) but it doesn't use From and Into because in the most general case we need to pass in the data that will be used to resolve fields that are offsets; instead we have two pairs of traits, FromObjRef/ToOwnedObj (which require offset data) and FromTableRef/ToOwnedTable which don't (because a table has its own offset data).
So given a read_fonts Name table, you can do,
use write_fonts::from_obj::ToOwnedTable;
let write_name: write_fonts::tables::name::Name = read_name.to_owned_table();

which maybe is what you're looking for?
iirc there was some issue with impling From and Into directly, possibly related to the orphan rules? There's an old issue #723 about trying to improve the ergonomics here.

Thanks, I will give that a try. We don't really have many examples of modifying fonts in different ways, so I'm hoping that as we continue to port things, we will discover what the needs and the patterns are.

Well this is much tidier:
        let mut name: Name = f.font().name().unwrap().to_owned_table();
        // Can't mutate it directly because it's a BTreeSet, convert to Vec
        let mut records = name.name_record.into_iter().collect::<Vec<NameRecord>>();
        for record in records.iter_mut() {
            if record.name_id == NameId::LICENSE_DESCRIPTION
                && record.platform_id == 3
                && record.encoding_id == 1
                && record.language_id == 0x409
            {
                record.string = OFL_BODY_TEXT.to_string().into()
            }
        }
        name.name_record = records.into_iter().collect();
        let new_bytes = FontBuilder::new()
            .add_table(&name)
            .unwrap()
            .copy_missing_tables(f.font())
            .build();

Now the only gnarly bit is that name_records is a BTreeSet which isn't an ideal data structure for mutation - and write_fonts is all about mutation...

This would be much more fluent if we could easily turn a read_fonts::NameRecord into a write_fonts::NameRecord

I wonder how we could make to owned more obvious/discoverable, whether there is somewhere we could add docs or a ref or w/e to make it easier.
For context, https://docs.rs/write-fonts/latest/write_fonts/#loading-and-modifying-fonts aspires to explain about to owned. Did you look at the docs? Were they unclear? Did you look somewhere else?

I did read that section. I personally found it unclear. (Mentioning traits without mentioning the methods they provide and why you might want them is a blind spot for me.) Of course now I've been told that the first sentence is the important bit, it all makes sense.
I prefer docs in the "Here is something you want to do. (Here are some problems you may face.) Here's how to do it. Here's a real life example." format. I'll send a doc PR.

Now the only gnarly bit is that name_records is a BTreeSet which isn't an ideal data structure for mutation - and write_fonts is all about mutation...

Interesting, I hadn't really thought about how BTreeSet can't implement iter_mut.
The reason it's a BTreeSet is because it lets us enforce the invariant that NameRecords are always sorted. We could do this instead with some custom SortedVec type or similar, but maybe that's trading one annoyance for another...

Just sort them when you build them?

We don't have mutable access to the objects when writing them. We could provide custom logic for writing that handled the sorting (there's an annotation for that) and given that we need a custom annotation anyway (to specify that we use BTreeSet, here) maybe that would be preferable? Shouldn't be too tricky...


UI test: Do no require database access for testing

Currently playwright testing supposes the server is started with yarn start, so that it is running is a complete setup.
Here are many options to choose from for this:

We could simply catch the requests to the server and return the expected data, with potentially "faking" data for specific cases (like serverValidations or serverFieldUpdates). That scenario would not require starting the server and should be used if we just want to test the UI and filling the survey, without actual interaction with the server, as we stub the server

Another approach would be to just mock the database calls, if possible. The server could maybe be run with jest to mock knex calls? This would mean that we test the complete flow of the survey, with server interactions, just without database.

Or we could prefer to have the full application running, including the database calls, so we can have full integration testing. If we do so, we should plan for a way to delete test data once the tests are complete, maybe using a different DB for those tests.

Normally, we can use playwright.config.ts with webServer for that.
I was not able to use it correctly, probably because of the folder path.
webServer: [
        {
            command: 'yarn build:dev',
            // url: 'http://localhost:8080',
            // reuseExistingServer: !process.env.CI,
        },
        {
            command: 'yarn start',
            // url: 'http://localhost:8080',
            // reuseExistingServer: !process.env.CI,
        }
    ],

Or we could prefer to have the full application running, including the database calls, so we can have full integration testing. If we do so, we should plan for a way to delete test data once the tests are complete, maybe using a different DB for those tests.

I think this would be simpler to do, but @greenscientist said it adds a bit of complexity to the CD/CI. We can use test.afterAll() to delete the data after. But, I think I will vote for the option that is more similar to what the user will get, so we can test a real survey.
test.afterAll(async ({ browser }) => {
    functionToDeleteTestData();
    browser.close;
});


Inconsistent plan with create_environment_v2 and composer_net

TL;DR
With 2 cloud composer deployed in shared network like here, planning one composer make the plan of the other one inconsistent.
Deploying 2 composers can be usefull if you have a prod and a dev project
Each time you apply the example, it works fine for the concerned layer, but in the otehr one, you will have the following error :
module.composer_env.google_project_iam_member.composer_agent_service_account[0] must be replaced
Expected behavior
Once applied, the plan should be empty.
Observed behavior
Each time I apply, I have this resource which want to be replaced
  # module.composer_env.google_project_iam_member.composer_agent_service_account[0] must be replaced
-/+ resource "google_project_iam_member" "composer_agent_service_account" {
      ~ etag    = "a8Ge3sGGfd6=" -> (known after apply)
      ~ id      =<EMAIL_ADDRESS>-> (known after apply)
      ~ member  =<EMAIL_ADDRESS># forces replacement -> (known after apply) # forces replacement
        # (2 unchanged attributes hidden)
    }

Terraform Configuration
module "composer_env" {
  depends_on = [
    module.composer_net
  ]
  source                           = "git@github.com:terraform-google-modules/terraform-google-composer.git//modules/create_environment_v2"
  project_id                       = "xxx"
  network_project_id               = "xxx"
  composer_env_name                = "composer"
  composer_service_account         = module.composer_net.composer_sa_email
  kms_key_name                     = "projects/xxx/locations/europe-west1/keyRings/xxx/cryptoKeys/xxx"
  region                           = "europe-west1"
  network                          = "projects/xxx/global/networks/xxx"
  subnetwork                       = "projects/xxx/regions/europe-west1/subnetworks/xxx"
  pod_ip_allocation_range_name     = "composer-pod-main"
  service_ip_allocation_range_name = "composer-service-main"
  grant_sa_agent_permission        = true
  use_private_environment          = true
  enable_private_endpoint          = true
  environment_size                 = "ENVIRONMENT_SIZE_SMALL"
  resilience_mode                  = "STANDARD"
  storage_bucket                   = google_storage_bucket.this.name
  scheduler = {
    cpu        = 2
    memory_gb  = 1
    storage_gb = 1.875
    count      = 1
  }
  web_server = {
    cpu        = 1
    memory_gb  = 2
    storage_gb = 10
  }
  worker = {
    cpu        = 1
    memory_gb  = 2
    storage_gb = 1
    min_count  = 2
    max_count  = 6
  }
}

Terraform Version
Terraform v1.6.3
on linux_amd64
+ provider registry.terraform.io/hashicorp/google v5.13.0
+ provider registry.terraform.io/hashicorp/google-beta v5.13.0

Additional information
This is perhaps due to a local being used to calculate the service account name. The replacement is caused by this line :       ~ member  =<EMAIL_ADDRESS># forces replacement -> (known after apply) # forces replacement So perhaps by changing this line in the code source, it should work
iam.tf :
member  = format("serviceAccount:%s", local.cloud_composer_sa) into member  =<EMAIL_ADDRESS>local.cloud_composer_sa)
After trying to change that, nothing changed

I can't do this morning, but I might work on it this afternoon

@Sarapuce if you are deploying 2 composer instances in same shared VPC network then it will be better to set grant_sa_agent_permission to false in all but one module call. This should fix the issue.

Yep it works ! Thanks !


how to auto pass parameter to multi_script_CLI.py without keyboard

Before submitting an issue, make sure you have:

[x] Searched the bugtracker for similar issues including closed ones
[x] Updated to the latest version
[x] Read the README and docs

Purpose of your issue?

[ ] Bug report (encountered problems/errors)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

Describe your issue
i'm using centos vps server. how to setup supervisor to pass parameter for multi_script_CLI.py ?
I do not have access to the command line.
Can I automatically pass the parameters without keyboard press?

Why not run individual scripts instead?


Fix hovering on toggled texture buttons

It seems that DRAW_HOVER_PRESSED introduced a small bug in the TextureButton class. When one of these buttons is toggled (toggle mode being active) the button disappears when the mouse is over it.
Steps

Download this project: TextureButtonBug.zip
Play it.
Toggle the button and see how it disappears while the mouse is over it.

I basically copied the code from the DRAW_HOVER case to the DRAW_HOVER_PRESSED one and removed the if (hover.is_null()) conditional. Let me know if this is the right way to do it!

Wouldn't it be cleaner to move the check for HOVER_PRESSED above the check for PRESSED and just not break?

Yes you're right @DualMatrix. I just changed my commit.

So I looked back to #22384 where I added the HOVER_PRESSED mode and I'm unsure this is the best solution. IMO HOVER_PRESSED should't even be called when Pressed automatically implies Hovering like in regular Buttons. I thought this was already the case but apperenlty I implemented it a bit differently. I think I should move the check that tests whether hover_pressed is possible to where the notification in sent ,not where it is recieved. This would be the cleaner solution I think.

I suppose it depends if we want to allow a "hover pressed texture" for TextureButtons in the future (I think it could make sense). If so, I think we can leave it like this. If not, I think you're right, the notification shouldn't even get there. What do you think?

The same bug likely happens in LinkButton where DRAW_HOVER_PRESSED is also discarded.

You're right, I tested it with the "Font Color Hover" and "Font Color Pressed" and it is happening. I've updated the PR title and the commit, although @DualMatrix may come with a better solution.

If it makes sense to have this "hover pressed" functionality for TextureButton and LinkButton (including being able to select a texture or a font color for it in the inspector) we could merge this as it is right now and open an "enhancement" issue (I can do it myself) about this new functionality. What are your thoughts on this?

@samuelpedrajas I don't see how HOVER_PRESSED makes sense for regular buttons, since it being pressed automatically means it's being hovered over at the same time right?

@DualMatrix If toggle mode is active then the button stays pressed even when the mouse is not over it, that's why I thought it was a good idea, but I may be missing something.

@samuelpedrajas Oh, I wasn't aware of that, in that case the HOVER_PRESSED functionallity should probably be extended to all buttons that offer that mode

Came here from an issue relating to this bug...  It solves the bug, but Should there not be an option to add a texture for HOVER_PRESSED, and have it default to the PRESSED texture if not defined?

@Jalu1 Yeah, thats also what I had in mind

the entire switch statement can be reworked to be more efficient, working on that now

Alright, I rebuilt the structure of the switch statement so it is cleaner and includes support for the extra texture. Can I add to the fork?


Addition of verbose flag

$ lab issue ls --verbose
#1 Issue title
        Issue link
        Issue description
        Assignees, Labels
#2 Issue title
        Issue link
        Issue description
        Assignees, Labels
...

Would love to have such an interface.

Along the same lines, lab issue show/get is something I've thought about that showed more detailed view. Theres a GitLab issue open for creating a lab cli that suggests and interesting design here: https://gitlab.com/gitlab-org/gitlab-ce/issues/17575#note_11927381

Can we have a discussion over gitter?

How does this look @zaquestion? https://asciinema.org/a/xIsmfvlSB8I7BIRjARYJooOxo


remove Language enum

see https://github.com/gbif/gbif-api/issues/29

replace it with normalised and validated 2 or 3 letter ISO codes.

We should also expose all language codes in the vocab API, allowing to restrict languages to the major 2 letter ones only to populate UI forms, @thomasstjerne ?


Add tests for UK Federation trust fabric

There is some overlap in errors from other rulesets which I have tried to eliminate as much as possible (e.g., with check_schemas and check_mdiop). I think what remains is unavoidable.

There are definitely cases in real usage where multiple rules fire, so this is as you say unavoidable to some extent as long as we're checking the rulesets as they exist today.
Longer term we might want to look at whether we can capitalise on having good test coverage to reduce the number of checks we're doing. For example, there are plenty of places where we look for, e.g., https:// at the start of a URL but if we checked a whole collection of these in one "check protected endpoints" stage then we could remove that distributed checking. Something to look at, anyway.

Yeah. I guess we can look at the expected errors yaml files to spot current overlaps, maybe as a help to find where current overlaps lie.


This is a security research. please ignore...  zdqjez

This is a security research. please ignore...  zdqjez

CC @BillyONeal @dan-shaw

CC @JavierMatosD


Parameter option output-feed=true should only be used when the file does not exist

Two options:

The file is created by the alvisNLP plan -> output-feed can be used to prevent an error from occurring because of the absence of the file.
The file is already here -> output-feed shouldn't be used as we cannot check if the file was generated by the current alvisNLP plan, if it is used regardless an error should inform the user.

Works, except when the file is declared as a parameter :
[2023-06-30 10:08:44.761][testing-output-feed.map-label] SEVERE /work_home/mcourtin/gits/corpus-bsv/src/alvisNLP/mapping.txt does not exist
[2023-06-30 10:08:44.761][alvisnlp] SEVERE error in plan: some parameter values do not satisfy constraints


Enable scanline when 15khz screen mode from GUI, and fix frame drops.

Sample

and Fix command bar flicker in Lemmings 2.
before
https://github.com/user-attachments/assets/31fb51d1-df14-4882-8453-4c4cae3b1fdd
after
https://github.com/user-attachments/assets/256fa63d-e969-4c35-bd04-0129b8eff898


How was it possible to break master CI merging a PR?

Very good point about the CI rules @tagpro 💯
Originally posted by @ecoologic in https://github.com/zendesk/zendesk_api_client_rb/pull/470#discussion_r781604352

As we don't store Gemfile.lock (too bad), the first thing I checked was that the rubocop version was the same, in case the rules changed, but this doesn't seem to be the case:

https://github.com/zendesk/zendesk_api_client_rb/runs/4755598961?check_suite_focus=true#step:4:63
https://github.com/zendesk/zendesk_api_client_rb/runs/4691254475?check_suite_focus=true#step:3:85

I still think locking the gems would be a good idea.


is linking stories actually working?

This isn't so much of a technical bug, as an issue with how RASA stories work and how to debug with botfront.
I have a story which uses the "link" feature but it doesn't seem to "navigate" to the new story.

and the related setup story:

the setup intent is detected, but the linked conversation does not flow.
I could imagine the second bot utterance is that right might not get triggered,
but would think the reception of basics.yes would trigger the story to continue.

checking botfront logs it seems the fallback policy is being used
 rasa.core.processor  - Received user message 'yes' with intent '{'name': 'basics.yes', 'confidence': 0.9903191328048706}' and entities '[]'
 rasa.core.processor  - Logged UserUtterance - tracker now has 12 events.
 rasa.core.policies.fallback  - NLU confidence threshold met, confidence of fallback action set to core threshold (0.3).
 rasa.core.policies.memoization  - Current tracker state [{'prev_action_listen': 1.0, 'intent_get_started': 1.0}, {'prev_utter_NahGlWNw': 1.0,
p_phone': 1.0}, {'prev_utter_oREp2ekS': 1.0, 'intent_setup_phone': 1.0}, {'prev_action_listen': 1.0, 'intent_basics.yes': 1.0}]
 rasa.core.policies.memoization  - Launch DeLorean...
 rasa.core.policies.memoization  - Current tracker state [None, None, None, {}, {'prev_action_listen': 1.0, 'intent_basics.yes': 1.0}]
 rasa.core.policies.memoization  - There is no memorised next action
 rasa.core.policies.memoization  - Current tracker state [{'prev_action_listen': 1.0, 'intent_get_started': 1.0}, {'prev_utter_NahGlWNw': 1.0,
p_phone': 1.0}, {'prev_utter_oREp2ekS': 1.0, 'intent_setup_phone': 1.0}, {'prev_action_listen': 1.0, 'intent_basics.yes': 1.0}]
 rasa.core.policies.memoization  - There is no memorised next action
 rasa.core.policies.ensemble  - Predicted next action using policy_0_FallbackPolicy
 rasa.core.processor  - Predicted next action 'action_default_fallback' with confidence 0.30.
 rasa_addons.core.nlg.graphql  - Requesting NLG for utter_default from http://botfront:3000/graphql.
 sgqlc.endpoint.http  - Query:

I looked into the exported story files
and it looks like the labeled branch is just refering to itself in each case, not to the branch it should include / link to?
ie in no case does get_started story . branches link to the setup story?
Is this a bug in the exporter? Or how botfront internally models the conversation data?
# Intro stories

## Get started
* get_started
  - utter_NahGlWNw
> Get_started__branches

## Get started__setup-phone
> Get_started__branches
* setup_phone
  - utter_oREp2ekS

## Get started__other
> Get_started__branches
* random
  - utter_y1Ra8s0k

## Get started__chitchat
> Get_started__branches
* greeting
  - utter_Xch7Oq2D

## Get started__joke
> Get_started__branches
* ask_joke
  - utter_zhBT9KMO

# setup

## setup
  - utter_IZXAtrSA
> setup__branches
## setup__yes
> setup__branches
* basics.yes
  - utter_UApYQ-It
## setup__no
> setup__branches
* basics.no
  - utter_Ds_rRtP1

when I looked at the same export in botfront JSON format I don't see any links, maybe that feature isn't supported in the exporter?

Yes, it is. And in 0.20 there's a Rasa importer that will also get branches and links from projects exported for rasa

OK it could be my misunderstanding how rasa branches work. I only see self-referencing branches in the exports above. There is no way that the other story is linked to.
I tried hand modifying and re-importing but
## Get started__setup-phone
> Get_started__branches
* setup_phone
  - utter_oREp2ekS
> setup__branches

I find rasa checkpoints confusing
you have to put the link at the top of the branch, not where you want it to run.
like where you want to include it?
not at the point where you want it to link from?
I think it's their philosophy to not run a state machine but to run the whole conversations from ML predictions. So I think the checkpoints are just used like pre-processor flags to basically "include"  / inline expansion of some content before passing to the trainer. Not sure though.
https://rasa.com/docs/rasa/core/stories/#checkpoints
I'll try messing around directly with the .md files and rasa train

Hi,
Can you please share your export files here (both rasa and botfront)?
Also the file giving you the error?
Thanks!
I can confirm that linking works on the latest release.

I started working on a very simple example with linked stories just in RASA itself, and they completely do not work the way I thought... I'm trying to understand the logic and create a simple example. It's probably the case that your system is just using RASA logic.
basically you cannot link > to a story and then expect the NLU to continue. I'm not quite sure what this feature is doing... >.<

May be you could paste de stories you are trying to link?

https://forum.rasa.com/t/checkpoints-how-they-work-with-graphs/25835
I posted on the forum about it here. I think checkpoints seem to be pretty much unusable as is.
https://forum.rasa.com/t/checkpoints-how-they-work-with-graphs/25835
I guess you have a lot of experience building bots with rasa, as well as this wonderful editing tool. But putting the link feature at the bottom of one story in your UI I think is gonig to confuse people as I don't think that's how checkpoints work; since that is where you define them, not link to or use them... at least as far as I can understand. But as I said... either I'm missing something or this feature is really half-baked.

FWIW I put the scripts etc. for the bot here
https://github.com/dcsan/rasa-test/blob/master/bots/barbot/data/stories.md
this was just hand scripted not using botfront, but the point stands.

@dcsan From the point of view of Rasa, this is the story this ends up being equivalent to:
``## tell joke ++ asked joke

utter_joke

greet

utter_greet
utter_goodbye``

Also, the error you got above by importing your file are due to not following the Botfront branching convention: the story is called Get started__setup-phone but its branch-out checkpoint is called setup__branches; it should be Get started__setup-phone__branches.

@pheel thanks! so
## asked joke
> telljoke
* greet
- utter_greet
- utter_goodbye

## tell joke
- utter_joke
> telljoke

becomes
## tell joke ++ asked joke
- utter_joke
* greet
- utter_greet
- utter_goodbye

in this case where the checkpointed story does have a intent

this story works and gets expanded:
## asked joke
> telljoke
- utter_goodbye

but this one does not:
## hello goodbye
* greet
  - utter_greet
> telljoke
* goodbye
  - utter_goodbye

so it seems the checkpointed content has to be at the very start of a sequence....

That's right. The Rasa checkpoint syntax works that way. Botfront does raise an error when you try to import that kind of story, cf. your previous screenshot about "sandwiching". :) Feel free to reopen the issue if needed.

sure it's fine to close it, not an error with botfront, but i think you can see why the UI with
"link to story -> "
is a bit confusing? it does imply some type of routing to the next story.


Fix parsing --require-sha and HOMEBREW_CASK_OPTS.

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

Fixes https://github.com/caskroom/homebrew-cask/issues/24924.

Keeps failings tests on one of the setups.

@vitorgalvao, fixed the failing tests.


Feature Request: Force 2FA on Users

Would be nice if you could force all registered users on the panel to enable 2FA. Just to increase security that one bit more.

And an option to force administrators only