Multiplexed fmcw

Time to get real, now that the board is working.
How far did you get on the multiplexing? I saw your Kicad file, did you:

Make it?
Write the code FPGA code to support it?
Python/pc code for it?
I'm interested in pushing a little forward that idea, so let me know!

Regarding point 3, I've made some progress actually.
Would you mind testing my version of the fmcw3 python code and let me know if it works on your end too?
You would need to install the files I used with pip install fmcw and then run the attached main file. Thanks!
rt_fmcw3.zip

I'll try to test this when I can. What's the purpose of this code? Is it to support antenna multiplexing? If so, my testing will be a bit delayed since I don't yet have the receiver antennas and haven't modified the FPGA code to support it.
One of the main goals of this project for me was to learn FPGA dev, so I've been working to get all functionality (except plotting of course) onto the FPGA. All the individual modules work and now I just need to connect them together and test it, so hopefully I'll have a complete solution (including realtime plotting and antenna multiplexing) soon. I'll post back when I do.

In a nutshell:

Work at a higher level than Henrik's code by providing functions/classes/modules... and documenting stuff a lot more
Add some features

Key features:

Runs Henrik's core physics
Display IF signals/Angle/Range time in real time. Optionally, connects to a webcam and records video of the scene imaged.
Saves data to binary & csv (in csv mode you save the integer values of the IF signal)
Way more robust management of the USB connection, less than 5% of the sweeps are dropped now.
 Performing the FFT on the FPGA would definitely be more efficient than on a laptop. However, it's a lot harder to write than a few call to Numpy so if you go that route I would be interested to see how you did it.

Nice job getting all this working with just python code. I'm looking forward to testing it. I actually think your solution makes more sense for most applications than mine. The FPGA code is more efficient, but less flexible when you want to change something and as you mentioned harder to program. I'll be happy to walk you through it when I'm sure it actually works.

Thanks! Let me know if my script works for you. If you use windows, there might be some linux specific implementations that derail it.
Also I added my personal script to the fmcw library so you can just run YYMMDD_rt_fmcw3.py from there and see what happens. Thanks!

I've created a slack channel for the fmcw so we stop writing endless issue threads
https://join.slack.com/t/fmcwworkspace/shared_invite/enQtNzYyNTcwNDI0MTgyLTU4NzEzMDA3NTU5ZjI2YTY3MTI5ZmQ0ZDFkOGNlNGRjMzgxNzE1NWZhYjgxZDIyNDlkM2U3YjRhY2RhMGNlOTg
Feel free to join!


pfs_middleware: log RPC durations

HTTP requests can be slow because Swift was slow or because proxyfsd
was slow. By adding some timing info (at DEBUG level), we should be
able to tell which thing is slow.
This is pretty straightforward, but I haven't got a working development environment to try it in. Unit tests pass, though.

For the typical ProxyFS RPCs, I'd say they are:
1 RPC per HEAD (stat)
2 RPCs per GET (stat & get-read-plan)
2 RPCs per PUT (provision-object & put-complete)
Do I have this about right @smerritt ?

This has languished plenty long enough...


Add textual favs support

I think it has a dependency on #9 and will require a new table with BLOB column of saved text, joined on file_id. Currently, the bot answers with a failure when a simple text message was sent as the object

Finally, I've decided to give up on normal forms and implement the simplest options, i.e. made the file_id and file_unique_id columns nullable and add a new nullable column text, completing them with a constraint.


IDE does not understand Javascript multi-line string

VSCode Version: 0.10.11 (0.10.11)
OS Version: OSX

Steps to Reproduce:

Create Java script file

Add following lines

$('.videos').append('
 \
                ' + count + ' - \
                 \
                    ' + videoTitle + ' \
                 \

');

IDE understand first line as string but  line 2 -5 it try compile and high lights keywords and other stuff

This seems to be fixed in 1.0:


Update URL_Threats.png

customer name has been hidden

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/5362

@JohanFreelancer9 Please copy review

@MSFTTracyP Please merge this PR. Thanks

Gentle reminder @MSFTTracyP


Bump to v2.8.2

Bump to v2.8.2

Can you verify a working helm install or helm upgrade using the packaged changes? i.e if you have a project called op-scim-bridge:
helm upgrade op-scim-bridge op-scim-bridge-2.10.2.tgz

Should we update the packaged dependencies? i.e helm dependency update charts/op-scim-bridge

Updated chart dependencies, and tested. All looks good. 👍🏻

Thanks, @alicethorne-ab !


serializers: added schema processors

closes https://github.com/inveniosoftware/invenio-rdm-records/issues/1231

I went through all the comments, there are many and it could be that some slipped through (they are not marked as outdated, nor resolved, and some are still present).
TL;DR:

Read through the non-resolved comments
Remove the asserts for type checking
Move LoaderMixin and DumperMixing to the root of custom fields (i.e. services) or even to invenio-records-resources since communities might need this too (check for other potential generic classes, there might be more)

Tests are passing with the latest flask-resources


Add ML Model pipeline

Can you add target_column before performing the EDA histogram? I got an error while running it. Otherwise, looks good! Thanks for tuning it and removing the outliers, I think that helps with the score.

Fixing that


[Feature][multistage] Thread-safe query planning

Move unthread safe vars needed by query planning from QueryEnv to PlannerContext.
This includes PlannerImpl, Validator and LogicalPlanner.
In the future, we should probably have our own planner etc and move only the shared state to PlannerContext.

Codecov Report

Merging #9344 (9d7437e) into master (334c978) will decrease coverage by 54.52%.
The diff coverage is 95.00%.

@@              Coverage Diff              @@
##             master    #9344       +/-   ##
=============================================
- Coverage     69.76%   15.24%   -54.53%
+ Complexity     4704      170     -4534
=============================================
  Files          1882     1829       -53
  Lines        100155    97893     -2262
  Branches      15226    14967      -259
=============================================
- Hits          69874    14920    -54954
- Misses        25344    81845    +56501
+ Partials       4937     1128     -3809

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
?

unittests2
15.24% <95.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

.../java/org/apache/pinot/query/QueryEnvironment.java
81.48% <91.66%> (-1.28%)
:arrow_down:

...org/apache/pinot/query/context/PlannerContext.java
90.90% <100.00%> (+15.90%)
:arrow_up:

...src/main/java/org/apache/pinot/sql/FilterKind.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ain/java/org/apache/pinot/core/data/table/Key.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...in/java/org/apache/pinot/spi/utils/BytesUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/java/org/apache/pinot/core/data/table/Table.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../java/org/apache/pinot/spi/utils/BooleanUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../java/org/apache/pinot/core/data/table/Record.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../java/org/apache/pinot/core/util/GroupByUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/apache/pinot/spi/trace/BaseRecording.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 1420 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@61yao - can you rebase please ?

lgtm
> Thus when using {@code QueryEnvironment#planQuery(String)}, caller should ensure that no concurrent
plan execution occurs.
> Only one query query can be planned at a time. Afterwards planner needs to be reset in order to clear the
 state for the next planning.

The above javadoc comments in QueryEnvironment can be updated

Done

@61yao - can you rebase please ?

Done.

@61yao - can you rebase please ?

Edit: Actually, the rebase is not done. Working on it.

I think I got the rebase done. Let me know if it works. Sorry, not very familiar with this..


Validate ros cloud-config as much as possible

Now we can use ros config validate to to validate ros cloud-config,  this is not enough. In particular, the user manually modifies the config. If the wrong configuration is added, it may cause the startup to fail.
I think we need to enhance the experience and give users friendly tips.
Such as the following:

before the reboot or shutdown
before ros  install -c
others if needed

Tested with rancher/os:v1.5.2-rc1 from May 21
Verified fixed
Test:

Set the wrong cloud-config
Run the reboot or shutdown command
Run sudo ros install -c

Result:

Display error message and command is not being run.


[ZEPPELIN-2920] move commonly used error handlers to util (FRONT)

What is this PR for?

Sometimes I can see manually written error handler and it's repeated again and again.
Even sometimes I can see missing 401 (unauthorized error) handler.

So I propose here generalizing error handler for front-end.
What type of PR is it?
[Improvement | Refactoring]
What is the Jira issue?
ZEPPELIN-2920
How should this be tested?
Add error-handler.service.test.js and CI will test it.
If you can test manually, u can easily reproduce errornous respsone by toggling offline in chrome developer tool like.

Questions:

Does the licenses files need update? - NO
Is there breaking changes for older versions? - NO
Does this needs documentation? - NO

CI failed but irrelevant
Failed tests:
  RemoteInterpreterServerTest.testStartStop:62 expected:<true> but was:<false>

https://s3.amazonaws.com/archive.travis-ci.org/jobs/273195461/log.txt?X-Amz-Expires=30&X-Amz-Date=20170909T042527Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20170909/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=92cb9be0c7d2f3504f8a989203f575f4401baeeb029b4ee48fead89b93e6c2cb

rebased since it's quite old

https://travis-ci.org/1ambda/zeppelin/jobs/286465199
https://s3.amazonaws.com/archive.travis-ci.org/jobs/286465199/log.txt?X-Amz-Expires=30&X-Amz-Date=20171011T113958Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20171011/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=15e71aa2c61cf1ee2f241e91b3d4ab31c47293888f81b865603c6d3171142ad4

[INFO] **************************************************
[INFO] *                    Failures                    *
[INFO] **************************************************
[INFO]
[INFO] 1) Search block e2e Test counter increase and decrease correctly
[INFO]   - Expected false to be true.
[INFO]   - Expected false to be true.
[INFO]   - Expected false to be true.
[INFO]   - Expected false to be true.


Allow GCN_LSTM to be saved and loaded

This allows the A parameter to the underlying FixedAdjacencyGraphConvolution layer to be None. If it's None, the adjacency matrix weight is created with zeros. In the case of saving/loading models, the weight is serialised during save and the A parameter is specified as None in the configuration, thus, when the model is loaded, the weight is created with zeros, but overwritten with the serialised weight.
NB. setting A to None shouldn't generally be used explicitly (only while saving/loading models), and so this isn't documented.
Fixes #1681

Thanks for checking in detail. I don't understand those warnings off the top of my head. If you have a chance, could you file an issue?

Thanks for checking in detail. I don't understand those warnings off the top of my head. If you have a chance, could you file an issue?

Sure, although there are quite a few other tensorflow warnings that seem worrying in the test run and I'm not sure I've got it installed correctly on my computer. I'll file an issue and I can investigate those worries through that.

Sure, although there are quite a few other tensorflow warnings that seem worrying in the test run and I'm not sure I've got it installed correctly on my computer. I'll file an issue and I can investigate those worries through that.


GitLab Pipeline troubleshooting

description
In a GitLab pipeline, the chko/docker-pushrm image seem to not pick the PUSHRM_TARGET environment variable.
upstream image: ko
This is a basic job. If you're not familiar with GitLab CICD, the variables: defined here will be available to the job as environment variables. The $CI_... variables are predefined by the GitLab Runner, and the $DOCKER_... ones are defined at the project level. Believe me, they are correctly defined and available :-)
pushrm:
  stage: release
  image: chko/docker-pushrm
  variables:
    DOCKER_USER: $DOCKER_HUB_LOGIN
    DOCKER_PASS: $DOCKER_HUB_PASSWORD
    PUSHRM_SHORT: Hello world image.
    # GitLab will evaluate variables once only, so we can not use $CONTAINER_IMAGE here.
    PUSHRM_TARGET: "docker.io/$DOCKER_HUB_REPOSITORY/$CI_PROJECT_NAME"
    PUSHRM_DEBUG: 1
    PUSHRM_FILE: $CI_PROJECT_DIR/README.md
  script:
    - docker-pushrm

The job fails:
Executing "step_script" stage of the job script
Using docker image sha256:1b4adda359ab661ef05cdfefff8820ff9706784d629b154bd3d9b8aaffa113c2 for chko/docker-pushrm with digest chko/docker-pushrm@sha256:f6abb69e71e5718c18802eac84922cf02f2b5a47eced516de271afe24a7b458b ...
level=debug msg="root cmd init config"
level=debug msg="home dir: /"
level=debug msg="subcommand \"pushrm\" called"
level=error msg="Invalid [IMAGE] argument - missing namespace. Example: docker.io/mynamespace/myrepo:latest"
Cleaning up file based variables
ERROR: Job failed: exit code 1

From the debug messages, we can assume the $PUSHRM_DEBUG  variable was effective, but it seem $PUSHRM_TARGET was not seen by docker-pushrm. I tried to hardcode it right in the variables:PUSHRM_TARGET statement but it didn't work either, so it is not about GitLab's variables evaluation.
custom image with entrypoint: ok
I created a custom image with an entrypoint.sh script which basically dumps env, in order to troubleshoot the environment variables.
The Dockerfile:
FROM chko/docker-pushrm:latest as builder
FROM alpine:latest
COPY --from=builder /docker-pushrm /
COPY entrypoint.sh /entrypoint.sh
ENTRYPOINT [ "/entrypoint.sh" ]

The entrypoint script:
#!/bin/sh
>&2 echo "[+] debug env..."
env | sort | grep PUSHRM
>&2 echo "[+] docker-pushrm"
/docker-pushrm

Using the very same pipeline job but using this custom image, it works:
Executing "step_script" stage of the job script
Using docker image sha256:325bcd222af62b99975287ce9ac971abf373e9b59d023802c369b79134e4d44e for letompouce/pushrm with digest letompouce/pushrm@sha256:3b4a5711ef79ca6391252fb2f6aa84caab79479d5281eed072f68d636baba197 ...
[+] debug env...
DOCKER_ENV_PUSHRM_DEBUG=1
DOCKER_ENV_PUSHRM_FILE=/builds/l3tompouce/org/lab/pushrm/README.md
DOCKER_ENV_PUSHRM_SHORT=Hello world image.
DOCKER_ENV_PUSHRM_TARGET=docker.io/letompouce/pushrm
PUSHRM_DEBUG=1
PUSHRM_FILE=/builds/l3tompouce/org/lab/pushrm/README.md
PUSHRM_SHORT=Hello world image.
PUSHRM_TARGET=docker.io/letompouce/pushrm
[+] docker-pushrm
level=debug msg="root cmd init config"
level=debug msg="home dir: /root"
level=debug msg="subcommand \"pushrm\" called"
level=debug msg="Using target: docker.io/letompouce/pushrm:latest"
level=debug msg="using README file: /builds/l3tompouce/org/lab/pushrm/README.md"
level=debug msg="server: docker.io"
level=debug msg="namespace: letompouce"
level=debug msg="repo: pushrm"
level=debug msg="tag: latest"
level=debug msg="repo provider: dockerhub"
level=debug msg="Dockerhub.GetAuthident called"
level=debug msg="using credentials for user letompouce from generic env var"
level=debug msg="Using Docker creds: letompouce ********"
level=debug msg="Dockerhub.Pushrm called"
level=debug msg="retrieve Dockerhub jwt token, status code: 200"
level=debug msg="push readme, response body: {\"user\": \"letompouce\", \"name\": \"pushrm\", \"namespace\": \"letompouce\", \"repository_type\": \"image\", \"status\": 1, \"description\": \"Hello world image.\", \"is_private\": false, \"is_automated\": false, \"can_edit\": true, \"star_count\": 0, \"pull_count\": 62, \"last_updated\": \"2021-07-17T08:10:08.663623Z\", \"is_migrated\": false, \"collaborator_count\": 0, \"affiliation\": \"owner\", \"hub_user\": \"letompouce\", \"has_starred\": false, \"full_description\": \"# pushrm test\\n\\nthis is a test.\\n\", \"permissions\": {\"read\": true, \"write\": true, \"admin\": true}}"
level=debug msg="push README, status code: 200"
level=debug msg="content validation successfull, readme successfully pushed to repo server"
Cleaning up file based variables
Job succeeded

Note that at this point, PUSHRM_TARGET is still defined in the variables: with "docker.io/$DOCKER_HUB_REPOSITORY/$CI_PROJECT_NAME" so it is definitively not a variable evaluation issue.
what now?
I feel like I'm missing something obvious, but what? Any help would be appreciated!
additionnal info
docker-pushrm version
1.6.0 from the chko/docker-pushrm image
Docker CLI version and platform
Docker 20.10.6 / Debian 10

@letompouce - good catch, thanks for reporting this!
I did not yet look at it, but it sounds like the script: "/docker-pushrm" puts an argument behind the entrypoint command. So /docker-pushrm (pure entrypoint) becomes /docker-pushrm /docker-pushrm (entrypoint plus gitlab script). Your custom entrypoint script ignores this argument (doesn't pass it to the executable), that's why I guess it works.
Unfortunately it seems in a gitlab job definition a script: "non-empty-string" is mandatory. If it was possible to not set it, it would probably work. So we need a different solution. I'll try to repro it later to see how it can be fixed.

my assumption was partly correct, but the problem goes deeper. Gitlab is actually trying to run something like:
/docker-pushrm
sh
-c
if [ -x /usr/local/bin/bash ]; then
	exec /usr/local/bin/bash
elif [ -x /usr/bin/bash ]; then
	exec /usr/bin/bash
elif [ -x /bin/bash ]; then
	exec /bin/bash
elif [ -x /usr/local/bin/sh ]; then
	exec /usr/local/bin/sh
elif [ -x /usr/bin/sh ]; then
	exec /usr/bin/sh
elif [ -x /bin/sh ]; then
	exec /bin/sh
elif [ -x /busybox/sh ]; then
	exec /busybox/sh
else
	echo shell not found
	exit 1
fi

It seems Gitlab doesn't support minimal FROM SCRATCH images (without shell, coreutils, etc) that only contain an executable  currently:
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26501
Maybe we need to add an Alpine image. I'll poke a bit more tomorrow.

It seems Gitlab doesn't support minimal FROM SCRATCH images (without shell, coreutils, etc) that only contain an executable currently:
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26501

Ah damn, that was the obvious thing I missed! Well, this Alpine based image is 14,5Mb instead of 9, I guess I can survive with that for the time being.

@letompouce I just pushed a new version of the container image (v1.8.0), which is now based on busybox. With that a .gitlab-ci.yml like this works now for me:
stages:
  - release

pushrm:
  stage: release
  image:
    name: chko/docker-pushrm
    entrypoint: ["/bin/sh", "-c", "/docker-pushrm"]
  variables:
    DOCKER_USER: $DOCKER_USER
    DOCKER_PASS: $DOCKER_PASS
    PUSHRM_SHORT: My short description
    PUSHRM_TARGET: docker.io/$DOCKER_USER/my-repo
    PUSHRM_DEBUG: 1
    PUSHRM_FILE: $CI_PROJECT_DIR/README.md
  script: "/bin/true"

(also documented here)
This basically satisfies GitLab's mandatory script execution and prevents that any arguments get passed to /docker-pushrm (so it only uses the env vars). It looks a bit ugly, but at least it shouldn't change behaviour for existing users (we basically just added some more files to the image, but didn't change entrypoint, etc) and we have a working recipe for a gitlab job.
Does this solve your issue?

Yeah that works! Transparent change for existing users, yet usable in GitLab, perfect!
However, I may maintain my own image with a custom entrypoint script, for the sole sake of saving a line in my job definition ;-)


SSL URL

The domain name location-conflation.com doesn't appear to be redirecting to the secure (SSL) site, such as when clicking a location link from the nsi.guide web site.
In the case of the NSI, the domain being used it https://ideditor.github.io/location-conflation/?referrer=nsi which is then redurected to the non-ssl version of location-conflation.com

Updated NSI to use new domain via ff4c492

Thanks!  I just clicked the button in the dashboard to redirect all traffic to the ssl url.. Let me know if that's working...

All working now 👍


HELP Dashboard-insert crud table

goodday
how do you insert table in dashboard page?
im using the "How to use (full example)"-crud example. instead of adding a link to show tag table in tag page, i wanted it to be inserted in dashboard page inside a  instead. is that possible?

Sure. You can extend the DashboardController and turn it into an actual CRUD controller. Also take a look at https://github.com/Laravel-Backpack/Base/issues/32.
Cheers!


Allow the injection of a custom InvocationHandlerFactory

NetflixOSS » feign » feign-pull-requests #219 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » feign » feign-pull-requests #220 SUCCESS
This pull request looks good

@adriancole I'm not sure if those changes are in line with the goals, but I think this is a way to use a custom HystrixCommand to wrap the calls.

Not really in favor of this. It is less dangerous to copy/paste and make
your own HystrixFeign. The invocation handler is coupled to how hystrix is
used internally.
By exposing something that was intentionally marked unsupported, we would
now have bugs related to this to add to the issues list.
What are you trying to accomplish?

@adriancole I have a couple of configured HystrixCommand and I want to use it with feign instead of use the HystrixInvocationHandler.
Do you think it's better copy/paste?

What about to receive in the ctor a HystrixCommand and pass it to the HystrixInvocationHandler?, and by default use the current behavior

Yeah let's focus on the feature! Invocation handler isnt exactly a scalpel
:)
Sadly I am mostly away this weekend, but rephrasing as an issue (in this
case customizing the HystrixCommand) would be a good start.
Ex is this for all feign commands or some? What does your invocation
handler look like?
In your local codebase, copy/paste fork etc until there's resolution on it.

so just looking at the code here.. most of what HystrixFeign does is set HystrixDelegatingContract and also HystrixInvocationHandler. Most of the code is in HystrixInvocationHandler, and that's what it seems you'd like to affect.
What if you just used normal feign contract and set HystrixDelegatingContract and custom invocation hander there? Would that work?
Alternatively, what is it about HystrixCommand that you are changing? I know some folks want to change the naming policy, for example. Is there something reusable in what you're doing that others might need?

@nmiyake fyi: I'll wait until weds or when this completes for the next release, whichever is sooner

@adriancole

What if you just used normal feign contract and set HystrixDelegatingContract and custom invocation hander there? Would that work?

I'll try that and I'll let you know if that works.

Alternatively, what is it about HystrixCommand that you are changing? I know some folks want to change the naming policy, for example. Is there something reusable in what you're doing that others might need?

I wanted to create my own HystrixCommand and/or be able to configure roperties like:
groupKey: "something"
key: "somethingElse"
requestVolumeThreshold: 1
enabled: true
errorThresholdPercentage: 10
sleepWindowMilliseconds: 10000
timeoutMilliseconds: 100

HystrixFeign is a work in progress, but most of the code is in the invocation handler. Changing the invocation handler to a new one is very much like having a new module, as the hystrix invocation handler is most of the lines in HystrixFeign.
I recommend using the normal Feign builder to do what you want, particularly while the current implementation evolves.
Ex.
Feign.builder()
         .contract(new HystrixDelegatingContract())
         .invocationHandlerFactory(yourCustomOne)
         ...

Please report back if the above doesn't work.
Also, see #342, soon to be HACKING which explains a bit the rationale around change cc @marcingrzejszczak who also asked about swapping the invocation handler. Generally speaking, things not designed for extensibility aren't likely to advertise extensibility.


v4.19.0

The goal is to be able to use new Zendesk Sell product with Zendesk App Market.

Hi @grzegorz-dyk , the fix is now merged. You should be good to rebase off master. 👍

Keith

Hi please don't mention me in comments and mail I am not the intended recipient.
Please check once
Megha


Lock down Postgres and backend so that only our apps (and local host) can access them

Implented coors for local host and frontend url


Sample app crashing on Android

though it look like an issue in maui FileSystem.OpenAppPackageFileAsync method

FileSystem.OpenAppPackageFileAsync(p.File).Result is returning null stream.So it might be maui issue.
Just letting you here.
Tried updating Maui version to 8.0.10 but issue persist

@akgulebubekir thanks alot I was also facing same issue and got resolved in 1.0.4 but now I have another issue there can you please check.
Hi, I am using 1.0.4 version and I am having overlapping text issue. I have list of items to print in as table so I have used stacklayout with ItemsSoucre property to bind the list of items. It looks good on screen as I have given desense width, but when I use pdfgenerate GeneratePdfFromView(view,PageOrientation.Portrait, PageSize.A4, PdfStyle.Uniform); like this and pass whole view. its creating pdf but the data from columns are overlapping .

This is another issue. Please use #5 for the problem.


preview: changing comparison of svg images from puppeteer to resvg

@XhmikosR there is two variants here:

Resvg has some problems with displaying srprite without dimensions (this is visible in png changes, the blue svg is corrupted or even dissapeared)
There is some problem in our code :D

I'll check the second variant

just thinking out loud here... maybe we could even just drop support for SVGs that don't have width/height and/or viewBox and just save us the trouble? Not sure how frequent are such SVGs. Here's how it's done on SVGOMG: https://github.com/jakearchibald/svgomg/blob/3c5f9925f3a8c19f53541ce10299bbc1e5fee7ad/src/js/svgo-worker/index.js#L13-L24

Then this will be a breaking change. But I'm down with it. I agree with the svgomg's solution.
SVG without any dimensions is broken and we should just throw an error or warning

We can make breaking changes assuming we document it in the release notes.
Not sure the SVGOMG's solution is 100% the same situation, it's probably a little different since SVGOMG doesn't need the dimensions. But we do need them AFAICT.

@XhmikosR this PR is just a demonstration so I did not run lint and stopped workflow.
I watched these screenshots more closely and noticed changes in normal svg, like test/expected/png/css.horizontal.mixed.png. As you can see, two of six svg are missing. This happens with  elements inside svg. So it's resvg issue and we should wait until it is fixed.

Thanks for trying resvg-js. For corrupt SVGs, can you submit an issue to the upstream resvg?

@yisibl i think it's the problem with core package of rust resvg package. I'll try.

@yisibl yeah I'll be never implemented, according to this

I think I should try to test screenshot testing via selenium webdriver due to https://github.com/puppeteer/puppeteer/issues/8009
I have never checked the bug-tracker of puppeteer, but when I saw it I was shocked. I think we can't rely on this package :(


Add snowball aws go sdk v2

Issue #, if available:
#3158
Description of changes:
We need to run some of the snow validations with aws snowball go sdk methods such as

DescribeDevice
DescribeDNI

Currently the snowball client is not publicly available in the aws-sdk-go-v2 module. We need to manually add the snowball client code in eks-a repo as a temporary solution.
Testing (if applicable):
N/A
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


feat(grpc) allow imported services

Recursively scan imported files for services and methods
Fix FTI-3027

@javierguerragiraldez Oops, I think we should also add the Changeling entry to the CHANGELOG.md file. Could you do that in a separate PR?


B99 and Demonstrator Engines are not syncing

Some of the sync issues I've seen:
Clients see the hosts demonstrators as regular locos and can rerail them. (on 1.9.0 the loco's license isn't required for this - not yet tested on 1.9.2)
Clients see their own ghost demonstrators that don't exist for the host.


[feature-request] flatpak for wider linux distribution

Please consider releasing a flatpack package so more linux distros can easily run LBRY.
More info at: https://flatpak.org/

Both, unless lbrynet-daemon has no dependencies.  I did not know the project was split, old bookmark.  I'll submit the issue on lbry-app too.

I have heard this request for a looooong time now
On Tue, Jun 19, 2018 at 11:12 AM, Curtis Lee Bolin<EMAIL_ADDRESS>
wrote:

Both, unless lbrynet-daemon has no dependencies. I did not know the
project was split, old bookmark. I'll submit the issue on lbry-app too.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry/issues/1261#issuecomment-398435363, or mute
the thread
https://github.com/notifications/unsubscribe-auth/APoYDPdEabSD5OStV0DgVB7wHUNIzpucks5t-RTRgaJpZM4UtnE6
.

--
Josh Finer
Director of Operations and Analytics
LBRY, Inc.

The daemon has pre-built binaries, no need for a flatpak. I believe we will be working on a docker alternative.

@tzarebczan, a docker image would be great.

@CurtisLeeBolin the flatpak was just updated to the latest build for the app: https://github.com/flathub/io.lbry.lbry-app


Inintended caching of EntityManager by EntityRepository from within a transactional context

Describe the bug
According to the docs (https://mikro-orm.io/docs/identity-map#how-does-requestcontext-helper-work) it should be pefectly safe to use a more "global" EM instance from within a transactional or request context (i.e. not having to pass down the EM instance passed to the transaction callback).
However, this expectation breaks in at least one specific scenario that is very easy to replicate.
When the first time a repository is accessed is within a transaction but from the "outside" EM instance (the one on which .transactional was called) then the repository will get "stuck" with the transaction-specific EM instance (can be verified by comapring em.id) which in the best case leads to DriverException: Transaction query already complete and in the worst case can cause data corruption due to improper isolation.
This problem can occur naturally when using MikroORM with NestJS and having services that call one another while each relies primarily on the (global) injected EM instance.
It is worth noting that .getContext() on the "stuck" EM instance is a no-op and returns self, thus the repository is corrupted for the entire lifetime of the application process.
Reproduction
Reproduction:
const orm = await MikroORM.init({});
// EM like the one injected in NestJS
const em = orm.em.fork({ useContext: true });
await em.transactional(async _ => {
    // this could happen in a nested service without access to tx-specific EM
    await em.getRepository(Post).find({id: 1});
});
// some time later, even in a different request
await em.getRepository(Post).find({id: 1});
// ^ DriverException: Transaction query already complete, run with DEBUG=knex:tx for more info

// the following does not work anymore, the EM of this repo is forever "stuck"
await em.getRepository(Post).getEntityManager().getContext().find(Post, {id: 1});

// em.id !== em.getRepository(Post).getEntityManager().id

If the repository happened to be accessed prior to a transaction, the issue does not happen:
const orm = await MikroORM.init({});
const em = orm.em.fork({ useContext: true });
// First repo access is outside a transaction
await em.getRepository(Post).find({id: 1});
await em.transactional(async _ => {
    await em.getRepository(Post).find({id: 1});
});
await em.getRepository(Post).find({id: 1}); // works!
// em.id === em.getRepository(Post).getEntityManager().id

Using tx-specific instance or explicitly calling .getContext() inside the transaction also resolves the issue:
const orm = await MikroORM.init({});
const em = orm.em.fork({ useContext: true });
await em.transactional(async emtx => {
    await emtx.getRepository(Post).find({id: 1});
    await em.getContext().getRepository(Post).find({id: 1});
});
await em.getRepository(Post).find({id: 1}); // works!
// em.id === em.getRepository(Post).getEntityManager().id

What driver are you using?
@mikro-orm/postgresql
MikroORM version
6.1.12
Node.js version
18.16.0
Operating system
MacOS
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Slack.
[X] The provided reproduction is a minimal reproducible example of the bug.

That's funny, the commit that broke this (af87693aae0c1a4bf95d4ad3f78e81a96439dded) was trying to fix the exact same error (#3074). Will need to reread that thread, as reverting this would probably break some other case...

It is worth noting that the aforementioned https://github.com/mikro-orm/mikro-orm/commit/af87693aae0c1a4bf95d4ad3f78e81a96439dded explicitly states "do not use context in em.getRepository()", however it is still used there (v6.1.12) and was added by https://github.com/mikro-orm/mikro-orm/commit/b5b03a61dbe1898a10ce8243d517a200fc8bcadf#diff-a62cd78c400d99253a3c0fb5a9bf26e1e63e0deb511059d28ba51014b58242ddR146 but the change does not seem related to the commit's intention.

Could this be causing other unintended consequences?
I’m currently trying to track down an issue(so I can make a reproduction) where entities are deleted and recreated with the same ID.
I thought it was an issue our side (and might be), but it’s seemingly random, like the identity map is incorrect on some occasions.

@ashleyww93 You can override .getRepository() with a custom EM to be able to get visibility into any occurence of this specific issue. Feel free to just log instead of a hard error.
// replace `PostgreSqlDriver` with you respective driver
export class ExtendedEntityManager extends EntityManager<PostgreSqlDriver> {
  public getRepository<Entity extends object>(entityName: EntityName<Entity>) {
    const repository = super.getRepository(entityName);
    const currentContext = this.id;
    const repoContext = repository.getEntityManager().id;
    if (currentContext !== repoContext) {
      throw new Error(
        `EntityRepository<${repository.getEntityName()}> context (${repoContext}) did not match the current EntityManager context (${currentContext})!`,
      );
    }
    return repository as any;
  }
}

defineConfig({
  // ...
  entityManager: ExtendedEntityManager,
});

Docs: https://mikro-orm.io/docs/entity-manager#extending-entitymanager

@ashleyww93 If this issue is the culprit of your problem, it may appear random because it requires the first .getRepository() call in the app process to be inside a transaction. After a server restart it may be completely up to chance whether it happens this way.

It is worth noting that the aforementioned https://github.com/mikro-orm/mikro-orm/commit/af87693aae0c1a4bf95d4ad3f78e81a96439dded explicitly states "do not use context in em.getRepository()", however it is still used there (v6.1.12) and was added by https://github.com/mikro-orm/mikro-orm/commit/b5b03a61dbe1898a10ce8243d517a200fc8bcadf#diff-a62cd78c400d99253a3c0fb5a9bf26e1e63e0deb511059d28ba51014b58242ddR146 but the change does not seem related to the commit's intention.

Yeah correct, and reverting this bit is not making any of the existing tests fail, I guess I will go with that, worst case we will revert it, but I agree it looks unrelated to the commit. That change also makes the e2e test suite of the real-world app pass, so it feels safe.

@B4nan Awesome! Thanks.
Any chance the test suite can be amended with a case like this?
await em.transactional(async _ => {
    // first even call to a repository, em is not tx-specific
    await em.getRepository(Post).find({id: 1});
});
assert.equal(em.id, em.getRepository(Post).getEntityManager().id)

Yeah, for sure, I will include the repro from OP.

@B4nan any chance on a v5 backport? I'm seeing this same issue, and v6 upgrade is proving to be surprisingly hard due to changes in date type handling.

and v6 upgrade is proving to be surprisingly hard due to changes in date type handling.

If you mean that dates are no longer mapped to Date objects, you can create the very same mapped type as in v5 and use it in v6 too.

@B4nan I did try that - copied the v5 type to my codebase, and used that. It mostly worked, except one condition - composite primary keys with dates. With UTC+ time zones, it would break updates.
Where v5 would issue update table set ... where id = 123 and date = '2024-06-19', in v6 even with v5 DateType, it would become update table set ... where id = 123 and date = '2024-06-18T18:00:00Z'.
With UTC / UTC- time zones the bug is not readily apparent, because date part stays the same when converting to UTC, and postgres drops the time partition when writing to date - as a result, you get expected values there.
Is it possible that conditions for update statements skip custom types, and just run the data through the default serializer?
Does this sound familiar, or should I make a reproduction repo?

Repro welcome, nobody complained so far.

@B4nan https://github.com/tmikoss/reproduction/tree/v6-date-type-repro here you go. Seems not to be an issue with sqlite, only postgres. Two samples, one with unmodified v5, one with my best attempt at fixing it.

The problem here is that v6 handles date parsing early, during result mapping, and since your property runtime type is Date, this mechanism kicks in. The type ignored timezones (same in v5), that's the first issue, which starts the cascade down the path. It did work with v5 because we did the date parsing later, during hydration, and I think it was skipped completely for the DateType.
You can disable the date parsing done by the ORM by setting the runtimeType option to something else than Date (string should be safe).
@PrimaryKey({ type: DateType, runtimeType: 'string' })
date!: Date;

You could just define a get runtimeType(): string on the type itself, but that is apparently not respected now and the type we get via reflect-metadata is preferred, will try to fix that when I have some spare time.
You still get the UTC date, but that works the same in v5 and can be fixed in the type implementation. Btw this whole mess with timezones was exactly the motivation to change this and keep strings at runtime :]

I want to take a closer look at the how/why and compare more with v5, but my time is quite limited this month.


prepareVariables will set relay params as null when we don't get that value.

l use prepareVariables to set the value from url to relay.l found when the return is
{
 first: 10
}

the variables of relay is
{
 assignStatus: null,
 filter: null,
 first: 10,
 ordersBy : null,
 search: null,
 status: null
}

The query is :
const ProductOrdersQuery = graphql`
    query cooperate_productOrders_Query (
      $status: [productOrderStatus],
      $first: Int,
      $search: String,
      $filter: EntityFieldFilter,
      $ordersBy: [OrdersByType],
      $assignStatus: [productOrderAssignStatus],
    ){
      viewer {
        ... productOrdersList_viewer @arguments(
          status: $status,
          first: $first,
          search: $search,
          filter: $filter,
          assignStatus: $assignStatus,
          ordersBy: $ordersBy,
        )
      }
    }
`;

and the fragment's has defaultValue:
      fragment productOrdersList_viewer on Account @argumentDefinitions (
        status: { type: "[productOrderStatus]", defaultValue: ["new", "running"] }
        search: { type: String }
        filter: { type: EntityFieldFilter }
        assignStatus: { type: "[productOrderAssignStatus]", defaultValue: ["new", "running", "done"] }
        ordersBy: { type: "[OrdersByType]", defaultValue: [{ field: "endTime", mode: "ASC"}] }
        first: { type: Int, defaultValue: 10 }
      ) { ... }

l think when the value from prepareVariables don't have the same key of the query variables. the query should use the default value. But l get null. l'm not sure this is a bug or l'm wrong.
Anyone know it, please give me some advice. thank you very much.

If you're explicitly setting those, I don't think you can implicitly get the default, and I think you always get nulls. You'd get the same interaction if you just used <QueryRenderer> directly, so there's nothing we can really do here. Perhaps you can follow up on the main Relay repo.


Minecart moving sound names messed up

net/minecraft/client/sound/MinecartSoundInstance (class_1107) and net/minecraft/client/sound/RidingMinecartSoundInstance (class_1108) are mismatched. 1107 is actually the sound when player is riding, and 1108 is the ambient minecart sound.
Confirmed in both 1.14.4 and 19w42a.

Can't reproduce, classes seem named correctly

look at the usage. one is played when a minecart is spawned in the world.

The issue comes from Mojang then, the sounds have wrong IDs

this is sound instance class not sound events

where do you find the ids? mind link?

When they call the super class in their constructor, the currently called MinecartSoundInstance and RidingMinecartSoundInstance classes respectively use SoundEvents.ENTITY_MINECART_INSIDE and SoundEvents.ENTITY_MINECART_RIDING. Those sound events are deobfuscated Mojang names, and refer to hardcoded IDs anyway.
That's why I don't get the issue here. Either it's a Mojang issue, either we don't understand what they mean by "riding" or "inside".

one is ridden sound and one is ambient sound. don't trust thonkjang after all!


'width' keyword in the EISMap object

I have two questions please:

the EISMap for the measurement width. What does the width map represent in this context?
How can I get the exposure time over which these maps are estimated (eg. start and end time, as well as the time cadence)?

Hello,
Thanks for using EISPAC!

The width returned by the fitting routine is defined as the standard deviation of the Gaussian function used to fit the spectral line. In spectroscopy this is commonly referred to as the "spectral" or "line" width. The equation for each component of the multi-Gaussian fit is given in the note at the bottom of following section of the online documentation: https://eispac.readthedocs.io/en/latest/guide/04-fitting.html#loading-fit-templates

Timing information is contained in the .meta dictionary of both the EISCube and EISFitResult objects. In particular, .meta['date_obs'] and .meta['duration'] contain arrays of, respectively, the start times (in UTC) and exposure lengths (in [s]) for each raster step in the image. Please note: since EIS always steps through the raster positions from solar west to east (i.e. right to left in the images), the first array element in the date_obs and duration arrays corresponds to the LAST raster position and the last array elements give the values for the FIRST raster position.

Sorry if this was not clear in the documentation. When we next update the docs, we will be sure add a section with more details about the timing and exposure information.
Thanks for your questions! I will leave this issue open for a few days, in case you have any follow-up questions. If you have additional questions about EIS or the code unrelated to the widths or timing, please feel to open a new issue (so as to make searching the issues easier in the future).

Thank you so much @MJWeberg
If I may ask another question, I was wondering what is the difference between the Doppler velocity maps and the non-thermal velocity? and how can I extract the non-velocity maps using the eispac?
Here's an example from this paper in which they used the EIS data


Regex: use PCRE_UCP

Fixes #11262
See https://www.pcre.org/original/doc/html/pcre_compile.html (search for PCRE_UCP.) It doesn't mention [:print:] but I assume it applies to that as well, because with this it starts working fine.

I'm fine with this change if it works. But according to https://github.com/crystal-lang/crystal/issues/4704#issuecomment-314694080 it might not work depending on the compile config of the linked libpcre.

It was a couple of years ago, maybe it has changed since then 👍

Should we add a spec for the sample in #4704 as well?

Done!

Let's merge it for 1.3 and see if there are any issues with the nightly builds.


Added vagrant for linux - v2.2.14

Windows and Darwin installations is only avaible as .msi and .dmg files. I dont think gofish can handle this?

Yeah. At this time gofish cannot install from .pkg or .msi file formats.
LGTM!


Can not reach the reported performance

Hi, thanks for this excellent work!
I try to train the model using the config: R50_FPN_daytime_cycle_conf.yaml on BDD100k.
However, the performance is only 18.126 AP which is the same as my retrained baseline (18.108 AP).
There is a 1.0 AP gap with the reported performance in the paper.

I have a similar problem, moreover, the baseline of R50_FPN_daytime.yaml can achieve 18.2 AP while R50_FPN_daytime_cycle_conf.yaml  ahcievs 18.7 AP.


fix: error message for the missing fk constraints

fix: a typo in the error message

Thanks for your contribution @dakimura 🙏
@all-contributors please add @dakimura as a contributor for code


Any re-implementation in pytorch?

For some unknown reason, the code runs very slow in my device and is hard to debug for me. Only the initialization takes almost 10 minutes.
Has anyone be able to re-implement the unpairwise results using pytorch? I have tried for several days using the fiveK dataset but only obtained the highest psnr of 18.0 and the visual results look unnatural like follows:

first row: input, second: model output, last: expert C

Somehow, this model is not taking as much time to load in my case.
Is it possible to share the exact images which you are using, so that I can test them with this current implementation and tell you how the output looks like using TF code?

Somehow, this model is not taking as much time to load in my case.
Is it possible to share the exact images which you are using, so that I can test them with this current implementation and tell you how the output looks like using TF code?

Many thanks for your reply. For the TF code, I generated the tif images (for both input and label) with the larger side fixed at 512 pixels using the lightroom. On my devices (using one GTX 1080, batchsize 1), it takes about 73 minutes to iterate 1 epoch.
While for my pytorch re-implementation, we currently simply resize both the input and label into 256x256 resolution. And I only implement the one-way GAN using the wgan-gp baseline. It takes less than two minutes for each epoch.
I am new to the gan and tensorflow, still working on it.
By the way, could you please share the psnr curves on the testing or validation set during the training progress?

By the way, I calculated the average PSNR on the given test set using the following matlab code and the result is only 12.7dB, which is much lower than the initial psnr ~18 dB without any training provided in the supplementary file. Both the input and label images are in the tif format. Have I made any mistake in the following code?
imName_Input = dir(fullfile('test','.'));
imName_Input = {imName_Input(3:end).name};
psnr = 0;
cnt = 0;
for i = 1:length(imName_Input)
try
im1 = double(imread(fullfile('test',imName_Input{i})));
im2 = double(imread(fullfile('label',imName_Input{i})));
mse = mean((im1(:) - im2(:)) .^ 2);
psnr = psnr + 20*log10(65535/sqrt(mse));
cnt = cnt + 1;
end
end
psnr/cnt

You should select the InputAsShotZeroed as the input data.

Somehow, this model is not taking as much time to load in my case.
Is it possible to share the exact images which you are using, so that I can test them with this current implementation and tell you how the output looks like using TF code?

Hi, I'm trying to use Pytorch to re-impleament the code, but for now I only got the highest psnr of 10.8

Hi,
When I run the TF.py in the "[Online_Demo_Models]_Deep-Photo-Enhancer/LPGAN_exp_G3_736" file, I face this error:
Shapes (2, 1, 32, 32, 128) and () are incompatible
in line: netG_test_output1 = model(netG, test_df.input1, False, netG_act_o, is_first=True)
Would you mind helping me with it? Thank you in advance.


Allows middle-click and ctrl+click outbound clicks to properly open as user intended? #15

Description
This PR resolves #15
I have just updated the script. We will do a thorough testing with the pre-releases.

Hmm.. any reason why the outbound link tracking is implemented separately from the official version? Maybe I'm missing something but it seems like you could just add plausible.outbound-links.js extension to the script if it's enabled and it should work the same and also get future updates/bug fixes, no?

@ukutaht I have implemented it separately because the plausible.outbound-links.js includes main plausible script code along with outbound links code and similarly there are 3-4 links for different purposes. So, it makes it better to just include the part of outbound links and attach it to the main script. I hope this answers your question.

Sorry I don't understand. Yes, the plausible.outbound-links.js includes the main script code as well, that's how it's designed to work. If Plausible users want outbound link tracking, we instruct them to replace their current script with plausible.outbound-links.js. The main script and outbound link code is not intended to be used as two separate scripts.
What problem is introduced when the plugin loads plausible.outbound-links.js instead of plausible.js when the user has enabled outbound link tracking?
Or the inverse - what's the benefit of duplicating the same code in the WP plugin?
The clear disadvantage is that support and maintenance is more difficult this way. When people have problems with outbound link tracking we won't know if they're running the official code or the plugin code. And when we release any updates like allowing middle clicks, then the WP plugin needs to be updated separately, creating more work for you. If the plugin just used our official outbound link tracking these problems would be avoided.

@ukutaht Let me playaround with the way you mentioned. I will ask you questions, if required.

@ukutaht I have improved the code based on your suggestion and the documentation here: https://plausible.io/docs/outbound-link-click-tracking

Looks good to me. Less code to maintain in the plugin and we can expect consistent behaviour between the plugin and installing the script directly according to docs.
In the future it's likely we'll have more script extensions (like tracking form conversions for example) that you can hook into easily to make the plugin more powerful. Thanks for making the changes :)

Merged this PR as it is reviewed and approved.


Webpack - first attempts

This is slowly reaching the limit of my abilities so I'm putting this here in case someone has any ideas. At the moment, the static build can be created using npm run build. That will use webpack to create the static html and js files in a dist/ folder. You will need to install the new dev dependencies listed in package.json for this to work. At the moment there are four (separate?) problems:

Assets are not loaded correctly. Despite all my efforts I seem to be unable to tell webpack to include the files in pixmaps in the bundle. Even if I copy these files using CopyWebpackPlugin into the dist/ folder, the code still can't find the files.
CSS style sheets not loaded correctly. Something that seems to be working properly is that the CSS code is bundled together correctly using MiniCssExtractPlugin. The problem is the bundled js file seems to ignore it / be unable to import it / find it.
Web worker security issues. If you open the file in firefox, you'll be presented with the following error message:

Security Error: Content at file:///home/filo/VSCodeProjects/ccp4_wasm/baby-gru/dist/index.html may not load data from file:///baby-gru/CootWorker.js.

In Chrome the page fails to load and the message is:
DOMException: Failed to construct 'Worker': Script at 'file:///baby-gru/CootWorker.js' cannot be accessed from origin 'null'.

After few google-searches and dead-ends I think this is related to some security issues (modern browsers won't let you load workers when running a scripts from the local filesystem). There are some stackoverflow posts describing this, for example: https://stackoverflow.com/questions/58099138/getting-failed-to-construct-worker-with-js-worker-file-located-on-other-domain.
4. Cannot find createCCP4Module in index.html. This issue was already briefly described in slack. At the moment the browser complains that Uncaught (in promise) TypeError: window.CCP4Module is undefined. I know the problem is that once again the browser can't find the right file (in this case web_example.js). The interesting thing is, if I modify index.html to point directly at this file using the full path in my machine (so not a real solution, just testing), the error is substituted with:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at file:///home/filo/VSCodeProjects/ccp4_wasm/baby-gru/dist/baby-gru/wasm/web_example.wasm. (Reason: CORS request not http).

Which indicates that even if I fixed the webpack setup to point at the right file we would still have some CORS security issues.

Closing this now as it seems we are going to take a different direction. I won't close the branch just in case we need the code in the future.

Hi Filo,
For the last of these, the truth is that the static built version will never load using the file:// protocol, and will always have to be served by a (potentially tiny) web server.  This should not be a problem with using it in cloud…
M.

On 23 Nov 2022, at 15:56, Filomeno Sanchez @.***> wrote:
This is slowly reaching the limit of my abilities so I'm putting this here in case someone has any ideas. At the moment, the static build can be created using npm run build. That will use webpack to create the static html and js files in a dist/ folder. You will need to install the new dev dependencies listed in package.json for this to work. At the moment there are three (separate?) problems:
Assets are not loaded correctly. Despite all my efforts I seem to be unable to tell webpack to include the files in pixmaps in the bundle. Even if I copy these files using CopyWebpackPlugin into the dist/ folder, the code still can't find the files.
CSS style sheets not loaded correctly. Something that seems to be working properly is that the CSS code is bundled together correctly using MiniCssExtractPlugin. The problem is the bundled js file seems to ignore it / be unable to import it / find it.
Web worker security issues. If you open the file in firefox, you'll be presented with the following error message:
Security Error: Content at file:///home/filo/VSCodeProjects/ccp4_wasm/baby-gru/dist/index.html may not load data from file:///baby-gru/CootWorker.js.
In Chrome the page fails to load and the message is:
DOMException: Failed to construct 'Worker': Script at 'file:///baby-gru/CootWorker.js' cannot be accessed from origin 'null'.
After few google-searches and dead-ends I think this is related to some security issues (modern browsers won't let you load workers when running a scripts from the local filesystem). There are some stackoverflow posts describing this, for example: https://stackoverflow.com/questions/58099138/getting-failed-to-construct-worker-with-js-worker-file-located-on-other-domain.
4. Cannot find createCCP4Module in index.html. This issue was already briefly described in slack. At the moment the browser complains that Uncaught (in promise) TypeError: window.CCP4Module is undefined. I know the problem is once again the browser can't find the right file (in this case web_example.js). The interesting thing is, if I modify index.html to point directly at this file using the full path in my machine (so not a real solution, just testing), the error is substituted with:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at file:///home/filo/VSCodeProjects/ccp4_wasm/baby-gru/dist/baby-gru/wasm/web_example.wasm. (Reason: CORS request not http).
Which indicates that even if I fixed the file to point at the right file we would still have some CORS security issues.
You can view, comment on, or merge this pull request online at:
https://github.com/stuartjamesmcnicholas/CCP4-Web-Assembly/pull/59
Commit Summary
841f119 https://github.com/stuartjamesmcnicholas/CCP4-Web-Assembly/pull/59/commits/841f11950706296f9b576b5c6b44347077686798 first attempts with webpack
47d8d3e https://github.com/stuartjamesmcnicholas/CCP4-Web-Assembly/pull/59/commits/47d8d3e9e74cd2fcbe88d6e0a9a6a229f829e159 add babel config
File Changes (4 files https://github.com/stuartjamesmcnicholas/CCP4-Web-Assembly/pull/59/files)
A baby-gru/.babelrc https://github.com/stuartjamesmcnicholas/CCP4-Web-Assembly/pull/59/files#diff-b48e37edccf56c511c6e0c2d1558b1127d1bcd409743e0e48552d3105dce8132 (1)
M baby-gru/package.json https://github.com/stuartjamesmcnicholas/CCP4-Web-Assembly/pull/59/files#diff-12a9e4a2be4cf1bac4806231bd6774ec1de1eabfd3a09e4edfe5e168636571e2 (16)
A baby-gru/src/index.html https://github.com/stuartjamesmcnicholas/CCP4-Web-Assembly/pull/59/files#diff-49ecd665c1af058f4d39de621de9456ad7ab01d2ed0d72a9fe9f9eebb86c6d3e (65)
A baby-gru/webpack.config.js https://github.com/stuartjamesmcnicholas/CCP4-Web-Assembly/pull/59/files#diff-1355c9f2ef19736b9b5b9639fe614f840f4c2d2365775968f80d67c4e5c9ff9b (73)
Patch Links:
https://github.com/stuartjamesmcnicholas/CCP4-Web-Assembly/pull/59.patch
https://github.com/stuartjamesmcnicholas/CCP4-Web-Assembly/pull/59.diff
—
Reply to this email directly, view it on GitHub https://github.com/stuartjamesmcnicholas/CCP4-Web-Assembly/pull/59, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJJ2AHOQIRKQTBWRTRRAVLWJY5CXANCNFSM6AAAAAASJDZQ4A.
You are receiving this because you are subscribed to this thread.


Support Item prop style. Provide prop selected to itemRenderer

Issue Number
Without issue
Overview of PR
Allow to specify custom style for the item element. For example, it can be a different background color for each item (driven by some business logic, etc). Strange that it wasn't implemented before. it is so useful feature.
As well as, provide prop selected to the itemRenderer. I have a few cases when I need to know inside the item content does it selected or no. For example, I prefer to render some advanced information inside selected items. Or some way react to this prop in the child component lifecycle - open a modal, or send a request at last.

Thanks for opening this PR.
Can please open up an issue describing this PR and provide detail about how the current API doesn't give you what you need?

Can't you achieve this with the itemRenderer?

No, itemRenderer gives you access to the inner content of an item, but not to an item itself.

Oh, I see what you are saying.
Yeah this feature is needed, in the mean time you can try overriding the item class, might help you out :) Don't forget to use !important

The class is not suitable for me, because I'm in the situation when item background color is formed dynamically by the server. I can not prepare classes for every possible color :)

@morulus can you please open an issue for this PR? No PRs will get merged until there's discussion around its need.
Not saying this won't be added but it overlaps with another issue around refactoring itemRenderer.

The style issue https://github.com/namespace-ee/react-calendar-timeline/issues/347
The selected issue  https://github.com/namespace-ee/react-calendar-timeline/issues/348
Moreover, I found the related issue https://github.com/namespace-ee/react-calendar-timeline/issues/244

I want to consult with you.
Here is a chunk of code, implements style support:
const style = {
      left: `${dimensions.left}px`,
      top: `${dimensions.top}px`,
      width: `${dimensions.width}px`,
      height: `${dimensions.height}px`,
      lineHeight: `${dimensions.height}px`,
      ...this.props.item.style
    }

As you can see, It allows overwriting built-in properties. Probably, it is bad, because this can lead to anomalies. And it would be better to do it in this way:
const style = {
      ...this.props.item.style
      left: `${dimensions.left}px`,
      top: `${dimensions.top}px`,
      width: `${dimensions.width}px`,
      height: `${dimensions.height}px`,
      lineHeight: `${dimensions.height}px`,
    }

Thus, the built-in properties will be kept. How do you think?

All the usecases for this will be supported when #308 gets merged but  until then this will be useful.

Agree with @Ilaiwi .  I might merge this PR but these use cases will be achievable when #308 is merged.  I might prioritize that PR though as it's the direction we want to go anyways.

Ok. I've updated pr according to https://github.com/namespace-ee/react-calendar-timeline/pull/345#issuecomment-400348465. Changed the order of style in the spread. https://github.com/namespace-ee/react-calendar-timeline/pull/345/commits/caf2cdaa4eee2cb2b7ab7710bcefab463a501ee7

re: https://github.com/namespace-ee/react-calendar-timeline/pull/345#issuecomment-400348465
Yes absolutely, these styles should be overridden by any styles that the timeline is applying (i.e. left, top etc)


Hi there

I maintain the humpday package that compares global derivative-free optimizers. I'm curious to know how L2o approaches stack up against others, so just saying hi. I think it is a nice benchmark for more ambitious claims about RL in general. However, I'm sort of stuck on how to do this. What is a fair way to compare L20 that has learned Rastrigin against SHGO or whatever that has not?

Did you run the ModelBase code successfully? Can we talk about it?

Did you run the ModelBase code successfully? Can we talk about it?

Can you run it now? How did you solve error?


Support additional metadata ingestion from Schema Registry for Kafka Connector

Is your feature request related to a problem? Please describe.
We utilize the Kafka Connector within OpenMetadata, incorporating Avro schema definitions from Schema Registry for ingesting topics and their corresponding schema. However, OpenMetadata can ingest additional metadata from Schema Registry, encompassing details such as topic description, topic owner, column description, column tags, etc. Consequently, extracting specific metadata based on predefined rules proves highly beneficial.
Describe the solution you'd like

Following rules: https://docs.confluent.io/cloud/current/sr/fundamentals/data-contracts.html#rules
Additional metadata:

Topic description
Topic owners
Column description
Column tags

Example Avro schema:
"type": "record", "name": "TopicName", "doc": "TODO", "owners": ["David", "Jackson"] "fields": [   {     "name": "fullName",     "type": [       "null",       "string"     ],     "doc": "TODO",     "tags": ["pii"]   },   {     "name": "age",     "type": [       "null",       "int"     ],     "doc": "TODO",     "tags": ["sensitive"]   } ]

@ulixius9 lets check if we can do this for 1.5 otherwise move it to 1.6

Hi @harshach , Any update for this issue?


Warning: Request GET /search/issues?q=type... failed with 403: Forbidden

Been using this action for a while and noticed that I'm getting a few failed requests toward the end that I can't figure out the root cause of.

I'm using the publish-unit-test-result-action@v2 from within another custom action so I'm wondering if it has to do with inherited permissions or something.
The main ci/cd workflow:
testing-run-publish:
    runs-on: ubuntu-latest-8-cores
    permissions:
      contents: read
      issues: read
      checks: write
      pull-requests: write
    steps:
      - uses:sutom-test-publish-action@v2 #repo must be accessible to full org
        with:
          # some parameters
          ...

Then in the custom action I have the following:
name: "Test and Publish"
description: "Run Pytest Integration Tests and Publish Results"
inputs:
  image-name:
    description: "Docker image name"
    required: true
  registry-username:
    description: "Docker registry username"
    required: true
  registry-password:
    description: "Docker registry password"
    required: true
  registry-url:
    description: "Docker registry"
    required: false
    default: "dataanalysis.azurecr.io"
  dockerfile:
    description: "Path to Dockerfile"
    required: false
    default: "./Dockerfile"
runs:
  using: "composite"
  steps:
    - uses: actions/checkout@v3

    - name: Set up Docker Buildx
      uses: docker/setup-buildx-action@v2

    - uses: docker/login-action@v2
      id: login
      with:
        registry: ${{ inputs.registry-url }}
        username: ${{ inputs.registry-username }}
        password: ${{ inputs.registry-password }}

          # building test image locally only (no push) using the base image built in previous job
    - name: Build Testing Image
      if: inputs.build-context-target != ''
      uses<EMAIL_ADDRESS>      with:
        file: ./Dockerfile
        builder: ${{ steps.buildx.outputs.name }}
        load: true # load image into local docker daemon
        pull: true
        push: false
        tags: testing:latest
        target: testing

    - name: Run Pytest Integration Tests
      shell: bash
      run: |
        docker run --mount type=bind,source=${{ runner.temp }},target=/temp --rm ${{ inputs.target }}:latest

    - name: Upload Pytest Results Artifact
      if: always()
      uses: actions/upload-artifact@v3
      with:
        name: pytest-results
        path: ${{ runner.temp }}/result.xml

    - name: Download Artifacts
      if: always()
      uses: actions/download-artifact@v3
      with:
        path: artifacts

    - name: Publish Pytest Results
      if: always()
      uses: EnricoMi/publish-unit-test-result-action@v2
      with:
        files: "artifacts/**/*.xml"

Is the checkout causing a permissions issue here or is this something else?
Cheers!

You are doing nothing wrong, this is a known issue with the Github REST API. The search/issues endpoint is likely to raise a secondary rate limit error, because Github decides so: #419.
This issue should have been resolved with the latest release 2.6.0 (yesterday). Please check if you have seen Forbidden errors with the latest versions.

Looks like the new way of finding PRs does not work with PRs from forks. Working on a fix.

This should be fixed now, it should work without search_pull_requests.

Thanks!

Excellent, thanks for reporting!

A new version has been released that has changes related to this. Please report if this problem re-occurs. Thanks!


[CP Staging] fix: use correct variables for navigateToNextPage fn

Details

This PR fixes the incorrect usage of the navigateToNextPage function inside the ReceiptSelector native component.
Fixed Issues

$ https://github.com/Expensify/App/issues/28526
PROPOSAL: https://github.com/Expensify/App/issues/28526#issuecomment-1741503390
Tests

Launch New Expensify app.
Go to + > Request money > Scan.
Tap on the capture button.

Verify that the image gets selected and the user proceeds to the next step.

[x] Verify that no errors appear in the JS console

Offline tests

N/A
QA Steps

Launch New Expensify app.
Go to + > Request money > Scan.
Tap on the capture button.

Verify that the image gets selected and the user proceeds to the next step.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

https://github.com/Expensify/App/assets/30054992/b152ce6d-6cb1-4a52-810e-61f8bf671684

Android

https://github.com/Expensify/App/assets/30054992/9fda99cc-74f7-42e2-96f1-8a56c53d2483

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 1.3.75-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.75-12 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.77-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.77-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Refresh keycloak

⚠ IMPORTANT ⚠: This is a public repository. Make sure to not disclose:

[x] personal data beyond what is necessary for interacting with this Pull Request;
[x] business confidential information, such as customer names.

Fixes #680

Refreshes Keycloak instructions
Reduces build time

What's the new process for dealing with CSS changes? Do we just change the file directly without SASS or what? :thinking:

What's the new process for dealing with CSS changes? Do we just change the file directly without SASS or what? 🤔

The process is: We avoid CSS changes. :joy:
Please change the SASS and regenerate it. Happy to discuss if:

we should put all our CSS rules in SASS;
we should provide a Makefile to simplify CSS re-generation.

No opinion, but we ought to document it somehow.
Given how seldom we do this type of thing, I would very much appreciate if we had the workflow in the README.


Crash with WebRTC

Describe the bug
The moment you initialize a WebRTCPeerConnection (with stun server) while having GodotSteam installed, the application crashes:
terminate called after throwing an instance of 'std::bad_cast'
  what():  std::bad_cast
Aborted (core dumped)

To Reproduce
Steps to reproduce the behavior:

Create a new project with current stable Godot
Install GodotSteam GDExtension 4.1 from AssetLib
Install the official WebRTC plugin - Godot 4.1+ from AssetLib
Create a new scene and attach a script:

extends Node

func _ready():
	var rtc_peer := WebRTCPeerConnection.new()
	rtc_peer.initialize({"iceServers": [{"urls": [ "stun:stun.l.google.com:19302" ]}]})

Save and hit F6 to launch into the scene
Notice immediate crash

Expected behavior
No crash or at least graceful error handling.
Desktop (please complete the following information):

OS: Ubuntu
Version 23.10

Version of Godot:
v4.2.stable.official [46dc27791]
Version of GodotSteam:
4.4.3 from AssetLib
Additional context
Interestingly, when calling initialize() without the stun server config, it does not crash. However, this Google stun server is the default that every tutorial and demo uses.
Let me know in case you can confirm that the bug sits in the WebRTC GDExtension rather than in the GodotSteam GDExtension so that in that case, I can post this over on their repo instead.

The real question is this a Google issue or GodotSteam issue and why.  I have extremely limited internet access currently so it may take a bit to figure it out.

I mean, even if there's an issue with that Google STUN server, Godot shouldn't crash like that, no?
It would be great if someone could test this with debug symbols and get a stacktrace for the std::bad_cast to at the very least confirm which binary it's happening in.
Btw, the stun server is not optional, without it the peers can't connect properly, so this is quite a blocking problem.

Indeed, we'd hope that is just gave us some error or didn't work instead of crashing.  Now that I'm back online again, I can check into this more.  And I see that I'm talking with one of the authors tomorrow!  What a coincidence!  I'll have to make mention of this during that time, see what can be figured out.

After looking at the WebRTC Github page, it turns out there is an issue about it crashing with any other extension.  There is mention of changing the plug-in load order to prevent the crash but it does go on to mention some causes.

@Gramps Ah, good find! That is definitely the same issue and pretty much confirms that it's not caused by GodotSteam. I'll close this then. Thank you!

No problem! I hope the load order thing works for you.


Patch conda-pypi mapping with a specific name

Problem description
Right now users can specify their own mapping by this:
conda-pypi-map = { "conda-forge" = "https://example.com/mapping", "https://repo.prefix.dev/robostack" = "local/robostack_mapping.json"}

based on the discussion with @tdejager  it would be nice to have the ability to patch mapping, just by adding a name or fixing an existing one, without entire overwriting of it.

This would indeed be great!
Something like this?:
conda-pypi-map = { "conda-forge" = {patch = { boltons_py = "boltons"}}

As in "extra_url" you mean?


Adds more python3 compat fixes

Issues:
More PRs for 654
Problem:
python3 compat problems
Analysis:
patch adds more fixes for python3
Tests:
unit
functional

@wojtek0806 or @jasonrahm

@wojtek0806 @jasonrahm this PR is mergable. I just updated it to rebase on the upstream code. So feel free to merge whenever you want

reviewing now
From: Tim Rupp<EMAIL_ADDRESS>Reply-To: F5Networks/f5-common-python<EMAIL_ADDRESS>Date: Friday, November 18, 2016 at 11:07 PM
To: F5Networks/f5-common-python<EMAIL_ADDRESS>Cc: Jason Rahm<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [F5Networks/f5-common-python] Adds more python3 compat fixes (#827)
@wojtek0806https://github.com/wojtek0806 @jasonrahmhttps://github.com/jasonrahm this PR is mergable. I just updated it to rebase on the upstream code. So feel free to merge whenever you want
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/F5Networks/f5-common-python/pull/827#issuecomment-261694144, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AA0SSwL9Q_2C_D0l3XlxPhokUsrElw79ks5q_oQCgaJpZM4K3KEL.

@jasonrahm merge with reckless abandon


Authorization input box is not showing  in rest-hapi API swagger UI

Context
my package.json is look like

"rest-hapi": "0.23.2",
 "hapi": "^15.2.0",
"hapi-auth-bearer-token": "^3.1.1",
"hapi-auth-jwt2": "^7.2.4",
"hapi-passport": "0.0.6",
"hapi-swagger": "^2.2.4",

hapi-swgger version:    "hapi-swagger": "^2.2.4",

please give me solution

Closing since this feature works in current version.


Removed step to build samples temporarily

Disabling step to build sample to avoid npm clean which removes artifacts built in previous step. This is to unblock release.

/azp run storage - ci

/azp run storage - ci

@praveenkuttappan  you'll have to run storage pipeline from the UI

@praveenkuttappan  you'll have to run storage pipeline from the UI


It doesn't work again?

I was made it work fine in chrome,but few minutes ago,It doesn't work again.The Error msg is : Uncaught Script not found
Run autosave,The http://<IP_ADDRESS>:9104/ page display : X-URL header is missing

Where do you see "Uncaught Script not found"? Which version of Chrome do you use?

when I wanna save the edit,it appear from the bottom of the dev tools

It’s really hard to tell what’s gone wrong. Can you send me a page you’re working on? You can send it via private message if you wish to not show it publicly.

It's working now,thank you very much.


fix video_count and subscriber_count type

I get type error on calling getChannels function, it seems had changed video_count / subscriber_count type from sting to int.

Looks good at a glance. I'll test it tonight since CI seems to not be working.

Ah I see, the CI was working, I just needed to approve it to run

Thanks for the PR, I should probably set up a CRON workflow to catch this kind of thing.

Published as 2.0.0 https://pub.dev/packages/dart_holodex_api

Published as 2.0.0 https://pub.dev/packages/dart_holodex_api

Thanks for update! I'll take a check for release version.


Brave install has a virus?

Windows Defender is reporting a virus after Brave is installed then lunched.
This is what the command line says its installing from "https://updates-cdn.bravesoftware.com/build/Brave-Release/x64-rel/win/<IP_ADDRESS>/brave_installer-x64.exe"

RUN Virustotal on that its could be falsetto positivo?

Interesting scan result you got there @Turgo82, could it be outdated Definition Updates for Windows Defender?
Tried scanning the installer on my system (Windows 11 23H2, Build Number 22631.3447), and it should it as a clean file (without any viruses)
and did a Virus Total Scan just to make sure, and the results shows that it's a clean file as well, link to the scan: https://www.virustotal.com/gui/file/7625d0e3a61cabedb3b29dd4a46a1fdeee4def2899e666c744279f239f611e87

The installer looks clean as well on my end. Brave appears to generate a file that defender detects when brave is opened. Installing Brave from there main site doesn't have this issue.

@Turgo82 I see that it flagged a .crx file wich is a Chromium extension file this might be a built in extension not sure. Could you submit the specific extension file to Virustotal and send a link to results.


"task launch delay" undocumented

site:mesosphere.github.io/marathon "task launch delay"
only 1 cursory result

Thanks @mgummelt ,
I believe the corresponding docs section is https://mesosphere.github.io/marathon/docs/rest-api.html#backoffseconds-backofffactor-and-maxlaunchdelayseconds
But yes, those three words don't ever show up in the docs in that same order.
Do you feel like suggesting some edits?

I suggest we use consistent terms.  Calling it both "task launch delay" and "backoff" make it hard for a n00b (me) to understand the concept.  It also makes it hard to search the docs (which is what I did when I read the 0.10 changelog)

@mgummelt that makes sense.
ACs

[ ] Make sure the docs use a consistent naming for backoff, task launch delay and the likes.

Pinging @kolloch

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-3408. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


Add support to share challenges on social platforms

Challenge pages on https://dreamchallenges.org have buttons to share challenges on popular social platforms. For example:
Facebook
https://www.facebook.com/sharer.php?u=https%3A%2F%2Fdreamchallenges.org%2Fdream-4-in-silico-network-challenge%2F&t=DREAM%204%20%26%238211%3B%20In%20Silico%20Network%20Challenge

Twitter:
https://twitter.com/share?url=https%3A%2F%2Fdreamchallenges.org%2Fdream-4-in-silico-network-challenge%2F&text=DREAM%204%20%E2%80%93%20In%20Silico%20Network%20Challenge

Reddit:
https://reddit.com/submit?url=https://dreamchallenges.org/dream-4-in-silico-network-challenge/&title=DREAM%204%20%26%238211%3B%20In%20Silico%20Network%20Challenge

LinkedIn:
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdreamchallenges.org%2Fdream-4-in-silico-network-challenge%2F&title=DREAM%204%20%26%238211%3B%20In%20Silico%20Network%20Challenge&summary=Learn%20More%20%20%0D%0A%0D%0AThe%20goal%20of%20the%20in%20silico%20network%20challenge%20is%20to%20reverse%20engineer%20gene%20regulation%20networks%20from%20simulated%20steady-state%20and%20time-series%20data.%20Participants%20are%20challenged%20to%20infer%20the%20network%20structure%20from%20the%20given%20in%20silico%20gene%20expressio

Email:
?body=https://dreamchallenges.org/dream-4-in-silico-network-challenge/&subject=DREAM 4 – In Silico Network Challenge

This is one of the tweaks I mentioned in #411. Targeting to discuss this improvement with the team in sprint 22.12.

This idea is not limited to challenges but extend to all the artifacts of the registry (users, organizations, search queries?).

HeroX also includes tools to share their challenges on social media, via email, and with embeds.
See "Share" button on this page.


Incorporating Corrected Implementation of ROME in EasyEdit

Hi,
Recent works found some instability when using ROME resulting in model collapse. We found that the original implementation of ROME was not the correct representation of update equation derived in the paper, and we've created a repo with the corrected implementation of ROME, a version we're calling r-ROME.
We've explained in the paper the exact details of the irregularities in the original implementation in our paper here - https://arxiv.org/abs/2403.07175
We also find that the corrected implementation has better overall performance and better generalization and localization, and also allows for stable sequential editing without model collapse.
We also provide the corrected code here - https://github.com/scalable-model-editing/rebuilding-rome
We would be grateful if our work can be incorporated in your repository and framework. We also believe it will add value to the EasyEdit community.
Thank,
Akshat

Dear Akshat,
Thanks for your great work.
We will add r-ROME in EasyEdit.
We are recently rushing for the NeurIPS deadline and might need some time to integrate. If you are interested, you can also submit a PR.
Best,
Team of EasyEdit

Will do. Thanks so much. Will reach out here when we submit a PR.

Just submitted the PR to implement R-ROME: #237

Thanks for your contribution, I will reorganize your code and rename it to r-rome to retain the original implementation of rome.

Hi!
Again, thanks so much for considering our work to be part of the easyedit offering!
Wanted to check in to see if there is an update or an estimated timeline for incorporating r-ROME into Easyedit?

Neurips submission is coming soon. I will restart this matter after 5.22 and support it as soon as possible. Thank you for your timely follow-up. If you are interested, I also welcome you to submit a new PR. 😊

Hi, is the R-ROME implementation supporting llama2-7b and gpt-j as in hparams or basically all the models as stated in README?

I added a standalone implementation of R-ROME based on @akshat57 's implementation. In theory, it supports any models that are compatible with ROME, as there were no significant code changes.

Thanks. Though I couldn't run anything in fp16 format as error in matrix multiplication occured.

I have fixed this issue. Please update the code and try it again

Thanks. Though I couldn't run anything in fp16 format as error in matrix multiplication occured.

Sorry for the late reply.


feat: support use sql to construct graph for loader

closed #262

could u add a user case for it? (in the comment area)

could u add a user case for it? (in the comment area)

Vertices/edges and properties are not in the same table, need to join them.
Need to apply sql function on the specified column.

could u add a user case for it? (in the comment area)

Vertices/edges and properties are not in the same table, need to join them.
Need to apply sql function on the specified column.

Thanks. Do we have a minimal sql case for it? And it's useful for user-doc later

Thanks. Do we have a minimal sql case for it? And it's useful for user-doc later

select t1.name, t1.age, t2.city from t1 left join t2 on t1.id = t2.id where t2.date > '2021-01-01'

I can help to update doc later.


☂ Org-switch free UI + All VTubers support

[ ] Org preference settings (users can choose favorite orgs)
[ ] Render home according to user's preference orgs /
[ ] Organization page to explore music beyond favorite orgs /orgs/<org>

Consideration

Performance in generating recommendations for multiple orgs
Supporting "All Vtubers"

Suggest the migration to take several steps:

build a /favorites page
switch / to be /favorites (but also need support for non-logged in users)
split /orgs/ pages out (this is trivial at this point)

What the home / would look like after the migration?

There's no layout change just a query depending on:

/all or /org/all will be All Vtubers
If user logged in / will load favorites/recommended
If user not logged in / will load the same as 1. /all


Add Codecov to the CI - Tests coverage

Codecov eases visibility to check if we are failing to test any part of the code.
We proposed enabling it a long time ago, but we postponed it after the refactoring. I have been doing some tests (https://github.com/eavilaes/qbeast-spark/pull/5) and I think we can implement it now.
Codecov automatically posts comments with a bot in any PR. I personally find these comments quite annoying, so I have disabled them for the Qbeast-io organization in https://app.codecov.io/account/gh/Qbeast-io/yaml (only visible for people belonging to the org.).
This global yaml looks like this now:
comment: false

I have also added the CODECOV_TOKEN to the secrets of the repository. Once the tests for this PR have passed, the report should be available in Codecov.

PR report available: https://app.codecov.io/gh/Qbeast-io/qbeast-spark