add cross-atac to snare norebook

I added the diffusion based atac imputation we talked about to the snare test notebook. I left the knn-based approach in there as a comparison. Since it also uses the neighborhood in RNA-expression space, the results are somewhat similar. In both cases, however, the regularization is quite strong (300 neighbors for the knn and 10 iterations for the diffusion based). It seems the 300 might have been chosen since it works well in the gene based correlations and I tried to produce comparable results with my 10 iterations.
@qinqian Please let me know if there is anything else I can do and thank you for all the organization and preparation!

Note that I apply the same kernel to the RNA expression before correlating it to the imputed ATAC signal. This is the analogy to the kin-kernel that was applied to ATAC and RNA in the previous example.

Thank you so much @katosh for your effort, I'll merge your codes into the workflow.
@katosh, another point to explore is to use joint cell clustering of the multiomics data for aggregating cells of ATAC-seq and RNA-seq for evaluation of regulatory effect. Please let me know if you would like to try this point.

Hi @qinqian, I agree that theoretically a joint clustering should improve this imputation approach. However, due to the different nature (scaling, sparsity) of the modalities (RNA and ATAC) I find it non-trivial to generally unite the two without drowning one of the two modalities in the noise of the other. I will continue to consider this in my work though and let you know when I find something I can share.


Fix custom type type casting used in multiple attributes

Change Summary
When a custom type with __get_pydantic_core_schema__ is used in another BaseModel, it generates a function schema with the custom type defined as an inner schema. However only the inner schema is stored, and thus subsequent usage of the same custom type in another field would result in only the inner schema being used, and the custom validation is not used.
The proposed solution here is that the ref should be linked to the function schema, not the inner schema.
Related issue number

fix #7102
Checklist

[x] The pull request title is a good summary of the changes - it will be used in the changelog
[x] Unit tests for the changes exist
[x] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

please review


About the paper

hi,  Shiming
Great job. Is it a real-time system?
By the way, can you share the paper on this project?
thanks.

Hi, jasdasdf
Thank you for your attention to our work. This is a real-time AEC, but it is still in the draft review stage. If there is any new information, I will concat you.

Hi, jasdasdf
Thank you for your attention to our work. This is a real-time AEC, but it is still in the draft review stage. If there is any new information, I will concat you.

OK，that's very nice of you, looking forward to your good news.

Hi, jasdasdf
Thank you for your attention to our work. This is a real-time AEC, but it is still in the draft review stage. If there is any new information, I will concat you.

OK，that's very nice of you, looking forward to your good news.

https://arxiv.org/abs/2106.07577


home-manager switch forcibly restarts emacs service

With services.emacs.enable = true, updating your environment kills emacs, which causes all your open buffers to be lost. This is not ideal. It should probably be blacklisted from restarts the same way e.g. X is in NixOS.

Yeah, that's quite annoying I can imagine 😟
If you have the chance, please give the branch in #670 a try, hopefully it will fix the issue.

Not restarting: emacs.service
Seems to work, thanks!


Updated solution in python 3

Updated the 30 days of code (Day 0) that is compatible with python 3

@rishabhrks1208 , closing this as it's already completed. checkout the issue, to see opened questions. Also read contributing guidelines too. Closing this PR.

@rishabhrks1208 , closing this as it's already completed. checkout the issue, to see opened questions. Also read contributing guidelines too. Closing this PR.

you should have mentioned it before @sagarchoudhary96

@rishabhrks1208 , it's already mentioned in the issue. it's marked completed in the list in first comment on the issue.


Create array of array dataset out of JSON list for testing

issue #6896
creating function for making array of array objects out of JSON lists and tests to test out its functionality. This implementation is used to simplify tests in velox/functions/prestosql/tests/ArrayAllMatchTest.cpp, ArrayAnyMatchTest.cpp, ArrayNoneMatchTest.cpp.

@soumiiow
Please run "make format-fix" on command line and commit the changes it makes. That will fix the CircleCI format-check error.

@soumiiow : Please can you check the linux-build failures and rebase your code if needed.

@soumiiow : I still see
262: [----------] Global test environment tear-down
262: [==========] 1159 tests from 40 test suites ran. (419240 ms total)
262: [  PASSED  ] 1151 tests.
262: [  FAILED  ] 8 tests, listed below:
262: [  FAILED  ] MinMaxByComplexTypes.arrayCheckNulls
262: [  FAILED  ] MinMaxTest.arrayCheckNulls
262: [  FAILED  ] SetAggTest.global
262: [  FAILED  ] SetAggTest.groupBy
262: [  FAILED  ] SetAggTest.arrayCheckNulls
262: [  FAILED  ] SetUnionTest.global
262: [  FAILED  ] SetUnionTest.groupBy
262: [  FAILED  ] MapAggTest.arrayCheckNulls
Did you rebase your code ?

@soumiiow : I still see
262: [----------] Global test environment tear-down 262: [==========] 1159 tests from 40 test suites ran. (419240 ms total) 262: [ PASSED ] 1151 tests. 262: [ FAILED ] 8 tests, listed below: 262: [ FAILED ] MinMaxByComplexTypes.arrayCheckNulls 262: [ FAILED ] MinMaxTest.arrayCheckNulls 262: [ FAILED ] SetAggTest.global 262: [ FAILED ] SetAggTest.groupBy 262: [ FAILED ] SetAggTest.arrayCheckNulls 262: [ FAILED ] SetUnionTest.global 262: [ FAILED ] SetUnionTest.groupBy 262: [ FAILED ] MapAggTest.arrayCheckNulls
Did you rebase your code ?

@aditi-pandit i did rebase my code an hour ago, and was looking into build failures. however, seems like I should be able to rebase again as my main branch needs to be synced again. will keep you posted!

@soumiiow @aditi-pandit Any update on this?

@mbasmanova : I have few minor nits. But please take a look as well.

addressed aditi's comments. @mbasmanova please take a look when you can


HTTP/3 panic if udp is not available

From https://github.com/cargo-bins/cargo-binstall/issues/1292 :

192.1 thread 'main' panicked at 'unable to create QUIC endpoint: Os *** code: 92, kind: Uncategorized, message: "Protocol not available" ***', /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/reqwest-0.11.18/src/async_impl/h3_client/connect.rs:41:58

Given that it's not unheard of for udp to be banned, and now it seems to be banned within docker, I think it's a good idea to make it "Option<>"nal.

We should change it to return an error at least, instead of panic. An eventual feature improvement could allow falling back to other protocols, but only if someone configures they want to allow that; http3_prior_knowledge implies "it MUST use http3". Panics are still bad, though!

An eventual feature improvement could allow falling back to other protocols, but only if someone configures they want to allow that

IMO fallback to other protocol should be the default, our user of cargo-binstall discovers this when running cargo-binstall inside docker and is probably blocked by the seccomp filer docker installed.
Also many corp env do the same and block udp, so fallback should be the default unless turned off by http3_prior_knowledge.


⚠ Bofrost.de has degraded performance

In 22e1121, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1804 ms

Resolved: Bofrost.de performance has improved in 363b099.


Add some missing delete statements from deleteAfterBlockNo (with a test)

Ignoring the Mac build for now (Max specific issue unrelated to this PR).


Missing timeoutSeconds in probes in stacks' app-deploy.yaml causes error when creating Knative Service

Needs to this fix
https://github.com/appsody/stacks/issues/313

The PRs that resolved the issues in Appsody for nodejs-loopback (https://github.com/appsody/stacks/pull/398) and nodejs-express (https://github.com/appsody/stacks/pull/403) stacks have already been picked up and included in the corresponding Kabanero collections.
If there are other collections that need similar changes we will need to wait until these have been resolved by the Appsody stack owners and then merged into the collections repository.

Although the timeoutSeconds have not been added to the Appsody stacks for java-springboot2 and java-microprofile it has been added to the kabanero collections. Will work with the Appsody team to get these changes back ported to Appsody for these stacks.
PR:  https://github.com/kabanero-io/collections/pull/176

@groeges - Was the issue been fixed in the collection v0.3.0-RC4 or will it be fixed in the one after?

We made changes in the Appsody java-microprofile & java-springboot2 stacks to add the timeoutSeconds element to the readinessProbe in the app-deploy.yaml to resolve the KNative Service issues.
These Appsody changes have been picked up and merged into the corresponding Kabanero collections.

@marikaj123

@groeges - Was the issue been fixed in the collection v0.3.0-RC4 or will it be fixed in the one after?

No, the updates are not included in 0.3.0-rc-4 as the build was cut before the fixes went in.
If necessary a new rc.X release could be cut prior to the main release or we can just do the main release.


Explore implementing conventional commits and automating CHANGELOG

Implementing conventional commits could help add some automation for updating CHANGELOG/releases.

yea I was trying to follow this. does just the PR name have to follow it? or the first commit of the PR? or every commit...I guess we can just squash all PRs

either every commit has to follow, or we can squash and just have the PR name follow it. There is also a check for PRs which can prevent merges if commits don't meet the requirements for conventional commits.

Closing for now - if there is interest, I can reopen later on.


Add Cilium Multi-Networking lab

We should stop adding single Isovalent labs. All labs can be at most added as one entry / line, if at all.
AFAIK none of them provide any badge or certificate, hence doesn't belong to this repo.

Actually, the majority of the labs have exams and badges: https://www.credly.com/organizations/isovalent/badges


Improve versioning of the documentation website and fix page 404

Motivation and context

This PR contains:

improved versioning of the documentation website:

adds the display of the current version in the version selection menu
enable display the version menu on the mobile version of the site.
code from navbar_selector_menu.html move to navbar.html. Its done to correct display of the version menu on mobile version website.
version menu visible only on documentation pages

fix styles of the page 404

Preview site
https://tosmanov.github.io/cvat/
preview page 404:
https://tosmanov.github.io/cvat/docs/123
https://tosmanov.github.io/cvat/docs/123/456
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[x] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

I feel, the contributing section is not supposed to be always unfold, but now it is.

At the moment, the Contributing section does not divided into basic and advanced subsections. All contributing sections are at level 2 and they are always be visible. I see two solutions:

Comment out or delete the ul_show = 2 parameter in config.toml. In this case, only the Getting Started, Manual, Administration, Contribution sections will always be visible, and basic and advanced subsections will only appear on the open partition
Divide the contribution into basic and advanced.

I feel, the contributing section is not supposed to be always unfold, but now it is.

At the moment, the Contributing section does not have a division into basic and advanced subsections. All contributing sections are at level 2 they are always be visible. I see two solutions:

Comment out or delete the ul_show = 2 parameter in config.toml.  In this case, only the Getting Started, Management, Administration, Contributions sections will always be visible, and  basic and advanced subsections will only appear on the open partition.
Divide the contribution into basic and advanced.

Hiding the Contributing section and creating a link to the section in the menu is not suitable because in this case the subsections do not appear in the menu


Fix: typos and update links in contribute.md and index.js

This PR addresses a few small but important changes:

contribute.md:

Updated broken links:

Changed the Ephemera link from https://github.com/xmtp-labs to https://github.com/ephemeraHQ.

Fixed a typo: meerged → merged.

index.js:

Corrected a minor formatting issue: updated md:text-x to md:text-xl for better readability.

Hi @jhaaaa ,  Could you please take a look at my pull request when you get a chance? Thanks in advance for your time. 🙌


feature/VETHUB-216

create Crucible Filter Component, used as plugin component for main platform.

to test: "yarn test" at project root

yarn test passes. See suggestions. Otherwise LGTM.


Das_Geek: Watch mixi.network

Das_Geek requests the watch of the watch_keyword mixi\.network. See the MS search here and the Stack Exchange search here.

mixi\.network has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


add GoogleChrome/lighthouse module

Mandatory
Where is the source code for the Managed Module?
https://github.com/GoogleChrome/lighthouse/blob/main/proto/lighthouse-result.proto
Optional
Does this module have other module dependencies/imports?
import "google/protobuf/struct.proto";
import "google/protobuf/timestamp.proto";
import "google/protobuf/wrappers.proto";

Do you think this module is widely used by the community, and is not already provided on the BSR by the owners?
Not sure how many people are interacting with the Lighthouse proto directly, but in general, demand for headless Chrome via Puppeteer and other methods is growing.

We can add this one. Approved. Call it buf.build/googlechrome/lighthouse.

cc @mordfustang21

I'll start working on this. I'm thinking to set it to start syncing from latest commit on main as of today, and then all main commits onwards. Or any specific commit to use as initial reference? cc @bufdev @pgmitche

We don't have a preference, latest is great

Thanks for the wait on this. During testing of this sync we discovered that the file does not define a Protobuf package. We are sorry, we should have caught this earlier.

Sadly we cannot sync this module. While not declaring a Protobuf package is valid syntax, the BSR considers this a malformed Protobuf definition since a lot of its functionalities are based on the existence of such packages.
We recommend:

You could send an upstream PR to the original repository, and once the package is defined correctly in the source code, we can pick it up again.
You could vendor the file in your BSR modules, and embed it in one of your Protobuf packages.

upstream patch submitted
https://github.com/GoogleChrome/lighthouse/issues/15115
https://github.com/GoogleChrome/lighthouse/pull/15116

That merged, so we should be able to reopen this

Thanks for the upstream patch! I will pick up this work again next week.

@derekperkins probably something that we'll need is that the repo publishes an stable semver release with this new version of the file. This is so we're able to sync tagged releases instead of individual git references.

Hello @derekperkins, this module is already available at https://buf.build/googlechrome/lighthouse, thanks for the wait, I was trying to give a little room to see if they cut an stable semver release soon, but they haven't, so in the meantime we're just syncing all git commit SHAs in the main branch. I've left a TODO once they do new releases, to switch our sync to semver releases again.
Closing as resolved.

Awesome, thanks for your help @unmultimedio!


modify readme for topic and queue stream binders for typos

update typos that in the readme.md of topic and queue stream binder, property name should be sessionsEnabled instead of sessionEnabled.

Codecov Report

Merging #708 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #708   +/-   ##
=========================================
  Coverage     55.94%   55.94%
  Complexity      757      757
=========================================
  Files           181      181
  Lines          3207     3207
  Branches        237      237
=========================================
  Hits           1794     1794
  Misses         1277     1277
  Partials        136      136

Continue to review full report at Codecov.

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

#698 fixed by this PR.


Add support for std::wstring for open

Windows supported files that cannot be represented in std::sting. so the attached file cannot be loaded.
test.zip

All the places in OIIO that take strings for filenames assume utf8. In strutil.h, there are (on Windows) exposed utility functions std::string utf16_to_utf8(const wstring&) and wstring utf8_to_utf16(const string&).
Do you think that (a) everyplace in the API that takes a string as a filename also needs a second wstring-based wrapper that simply calls utf16_to_utf8 and then passes it to the usual string version of the call? Or (b) should we just be better at documenting that the filenames are utf8 and evangelize the existence of utf16_to_utf8?
I'm not a Windows programmer. I've never seen wstring used in the actual code myself (except, myself, when converting utf8 std::string to wstring to pass to Windows open commands and the like).  Is wstring very common in user code, arguing for solution (a) above? Or is it only for the rare case when somebody may be fitting OIIO into an application that is unusual in its use of wstring, in which case maybe (b) is easier?

Microsoft is strongly encouraging unicode which defaults to all string being wstring.  wstring is use primarily to support other languages that cannot be represented in the standard eight bits.
It is possible that some files cannot be converted to eight bits, but it works for this case.
If there are a lot of front facing API call that use std::string, it is probably not worth adding the layer and documentation is sufficient   If there are cases where std::string fails to encode the filename, then it may be worth revisiting.

My understanding is that on Windows, fopen(const char*) treats the string as ASCII by default, not UTF-8, so if you want to use Unicode characters in filenames, you have to open with _wfopen(const wchar_t*). On modern Unix-like systems, all the underlying OS and standard C/C++ functions involving filenames (like fopen()) treat those names as UTF-8.
To deal with this discrepancy, we avoid std::fopen and instead use our own Filesystem::fopen() that does a little extra magic on Windows of translating utf8 to utf16 and calling _wfopen underneath (and on Unix, just calls the system fopen straightforwardly). This translation is handled by Strutil::utf8_to_utf16(); that and its inverse, utf16_to_utf8(), are exposed (for Windows only) in strutil.h
OIIO therefore supports UTF-8 filenames for all its API functions that take filename strings (such as ImageInput::open()).
Our assumption thus far has been that if a Windows app with wchar-based unicode filenames makes OIIO API calls, it should just pass the filename through utf16_to_utf8 before handing it to OIIO.
But if this is a bit PITA because in Windows land people are just universally using wstring and not std::string at all, at least for filenames, then I wouldn't be averse to adding inline wrappers providing wstring flavors of the obvious filename-related methods, so something like
class OIIOClass {
    virtual bool open(const std::string& filename);   // Existing method, assumes UTF-8

    // Proposed non-virtual addition that does string translation
    inline bool open(const std::wstring& filaneme) {
       return open(Strutil::utf16_to_utf8(filename));
    }
};

I don't have a very strong feeling about whether, from an overall complexity and aesthetic perspective, this sprinkling of additional wstring shims all over the API is preferred over just better-documenting which API calls support UTF-8 and expecting Windows users who are already using wstrings in their apps to do the conversion themselves.
In the process of looking into this, I did just submit #3307 which slightly simplifies/modernizes our implementation of the UTF conversion utilities (which I think had even predated our ability to rely on C++11), which additionally removes the #if guards that exposed those utilities only on Windows. That makes it fairly easy to add the wstring wrapper methods on all platforms.
What's your current opinion about the best way to proceed -- adding more entry points for wstring filenames everywhere, or better documenting the utility functions and relying on the callers to use them?
It's not an especially big deal to add the new methods. Each one individually is trivial; the work is in tracking down all the places where they are needed, but that doesn't technically need to be done all at once. And because they are not virtual functions, they don't change ABIs and are safe to backport to the release branch.

I would prefer the std::wstring wrapper.  In Windows, every char function has the equivalent wchar_t function.

ok, that should be straightforward.

Took a stab at this in  #3312


Update index.html

Added a pokemon card

Can you attach a screenshot of how it looks on your system after adding the card? It would help me a lot


STL for Case

Not a real issue, but is it possible to share the stl file for printing the box as shown in the picture?
Would be nice to give it a nice fitting box.

The case is not 100% ready, design-wise, but quite usable as you saw in the picture.
I will upload what I've got so far.

I added my STL files to the project in the enclosure/ folder.


introduction of dynamic pgo

Not sure how to fix this "missing picture" issue (https://github.com/bytecodealliance/wamr.dev/actions/runs/6141637160/job/16662203449?pr=44). Pretty sure it's already uploaded in PR.


Application opens but it never comes out of minimize mode?

The program comes up and open up, it even shows on my taskbar and tray icon, but it won't open.

I had the same issue. i used "livestreamer-twitch-gui.exe --reset-window" to start it to fix the problem

Is that trough CMD?
Also I fix it by doing this, however this isn't the first time this happens.
Hover over the taskbar icon until the preview image window came up > right click > maximize

i used a windows Shortcut

i used "livestreamer-twitch-gui.exe --reset-window" to start it and fix the problem

Sounds like the window is being moved out of the visible desktop boundaries. If this happens again, could you please start the program with --remote-debugging-port=8888 and then open http://localhost:8888 in your browser? I'd like to know the width and height of your desktop and the value of
JSON.parse(window.localStorage.getItem("app")).window.records[1]

Did you maximize the application window by any chance? I'm asking because I needed to implement a workaround for this: maximizing the window also triggers a resize event on the window in addition to the maximize event (see here). So I'm curious if it's related to that or if there's something else which is causing this bug.

[also is it normal to have 4 processes from this program?]

yes, NW.js (based on chromium) uses a multi process architecture...

Yes, I noticed it happen when it was maximize, I had to delete the entire settings on the appdata folder to stop the bug, but I am pretty sure this happened when i maximize the window and leave it on the tray icon or minimize.
Hasn't happen to me as of now, but I am not using the full screen mode. (I'll try to reproduce the bug)

it seems to happen if you minimize the programm and than close it. (task manager or close via rightclick on taskbar) If i than try to start it, its started minimised.

Thanks for reporting the issue guys!
This was related to NW.js and Windows: when minimizing the application window, NW.js fired a move event with the coordinates -32000,-32000. I also fixed the maximize event on OSX (fired multiple resize events during the animation).
Should be working on all platforms now and I guess I have to release another version, since this was breaking the application. :weary:

Can you add a hotkey (F5) to refresh the page your viewing? also is there a way to use "recent viewed/activity" without being sign in?
didn't want to make another thread.

F5

I'm not 100% sure, but I don't think you're able to add those keybindings in NW.js (same as mouse4+5 - back and forth)

recent viewed/activity

Not yet implemented... Those are also just placeholders atm

It doesn't have to be "F5" but any key, you can even add "R".


Env in transform

Fixes #668.

@sjezewski whenever you have a chance.

Is there a way we can test the 'Secrets' feature as well?
Also - now that we have a place for docs, we need to make sure to document any new features (or they basically don't exist for users). This would probably go here I think

Alright this now has tests for secrets as well as an implementation for them.
Ready for another look I think.

Minor comment in the test, but the coverage looks good.
We still need to add these features to the pipeline spec documentation though.

@sjezewski another look? I think this is ready to go.

Really just a meme I guess, all I did was add it to docs.

Meme lgtm.


Host under AWS Elastic Beanstalk

Expand the implementation to host in AWS's Elastic Beanstalk. See https://aws.amazon.com/elasticbeanstalk/

Completed on simpledb branch


PFFile limit

I am planning to make an iOS app that will have 5  - 10 min videos. However I noticed that PFFiles has a 20mb limit. Is there anyway to use parse server and get around this limitation?
Also what if I started with the standard GridStoreAdapter. Then at some point in to future I needed to store PFFiles larger than 20mb. How would I get around this? what sort of issues would I be facing?

You can set the maxUploadSize option when you initialize parse-server to a larger value.
As for the rest of the questions, please use stackoverflow as this is not an issue with parse-server.


Feature request: greaterThan, smallerThan

Great library! I only realized there is no possibility to add a "greater than" or "smaller than" validation. Of course, minValue() can be used, but it is not really accurate. E.g. when I want a number to be positive (> 0) I have to do minValue(0.001) but now 0.0001 would be invalid so I need to use a very small number minValue(0.0000001) but still a smaller number that is positive would be invalid.
Therefor I would like to add a feature request to add:

greaterThan(), or gt()
smallerThan(), or st()
Optional: I found positive() from Zod very useful, but it is just a more humanly readable version greaterThan(0)

Thank you for creating this issue. I agree that we should add such actions. I am just unsure about the naming. It would be great if they would match somehow with minValue and maxValue.

Maybe:

valueGreaterThan
valueGt
greaterThanValue
gtValue

Feel free to create a PR with gtValue and stValue.

What is more common? "smaller than" or "less than"? Maybe we should use ltValue instead of stValue.

Sorry it should be less than, not smaller than. See for example https://orm.drizzle.team/docs/operators#lt
I am afraid I will not have the time to get in the project and make a PR.

Don't worry. I am already thankful for your contribution. I am sure someone else will work on it soon.

I'll work on adding ltValue & gtValue. I would recommend using a pattern like shown here till I complete adding the actions. The expected field of the issue might not make sense (Eg: parsing -1 would set expected to ≥0 and 0 to !0) but if the expected field is not used, it does the job.

This has been implemented by Elton in #978 and #985 over the last few weeks and will probably be reviewed and merged soon.


Unclear behaviour of recv(timeout=0) for Server (threading)

I think the behavior of recv(timeout=0) for the Thread-based Server is unclear.
Due to the design of my application, I can't use the "for message in websocket" and have to resort to an update() function that I call frequently to check if messages were received:

def update(self) -> None:
	"""
	Check for received data with proper handling of timeouts and connection closure.
	"""
	while True:
		try:
			# Attempt to receive data with a timeout
			data_rx = self.ws_client.recv(timeout=0)
		except TimeoutError:
			# No data received within the timeout period
			break
		except websockets.exceptions.ConnectionClosed as e:
			# Handle connection closure
			Log(f"Connection closed: {e}")
			self._is_connected = False
			break
		except Exception as e:
			# Handle any other exceptions
			Log(f"Error occurred: {e}")
			self._is_connected = False
			break

		# If no data received, exit the loop
		if data_rx is None:
			break

		self.log(f"RX: {data_rx}")

I was expecting when I set timeout=0 that only when a message was received I get it otherwise TimeoutError is raised so it's not blocking.
the behavior I'm getting is that with very low values like timeout=0.001 (1ms) it works, but with 0 I don't receive any messages.
Have I understood timeout=0 incorrectly? In the documentation it says:
"Set timeout to 0 to check if a message was already received." see

Probably https://github.com/python-websockets/websockets/blob/59d4dcf779fe7d2b0302083b072d8b03adce2f61/src/websockets/sync/messages.py#L146 should be changed to:
deadline.timeout(raise_if_elapsed=False)

Further changes may be needed if queue.SimpleQueue.get() chokes on negative timeouts — I think it does.

(This is also an opportunity to reconsider raise_if_elapsed — is it a good idea at all?)

(Maybe we need zero_if_elapsed?)


Make Tutorial how to mint from Mobile wallet on KodaDot #915

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Context

[x] Closes #915

Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

label blocked by #7208

cc @helloitsdamsky

cc @helloitsdamsky

@yangwao cc

hey @AshutoshSingh72, thanks for your contribution.
Unfortunately, the video you provided is:

hard to understand
somewhat sped up?
hard to follow
too long

Ideally, what we are aiming regarding quality is to have something like this:

https://www.youtube.com/watch?v=SKdx4pTgL04&t=16s

Key points:

Slow and clear pronunciation
Easy to understand
Easy to follow
Ideally under 5 min
Work on post-production
Explain your steps in understandable way for a non-tech user

Therefore, we’ll be looking forward for your next contributions, following the guidelines

As per #7303 (comment) this can be closed

I'll make changes today i'll follow your guidelines and make it perfect accordingly

hey @AshutoshSingh72, thanks for your contribution.
Unfortunately, the video you provided is:

hard to understand
somewhat sped up?
hard to follow
too long

Ideally, what we are aiming regarding quality is to have something like this:

https://www.youtube.com/watch?v=SKdx4pTgL04&t=16s

Key points:

Slow and clear pronunciation
Easy to understand
Easy to follow
Ideally under 5 min
Work on post-production
Explain your steps in understandable way for a non-tech user

Therefore, we’ll be looking forward for your next contributions, following the guidelines

Check @helloitsdamsky updated

Check @helloitsdamsky updated

For official tutorials that are onboarding our users to platform, we need native speakers or people who speak for very clearly. Unfortunately, i still can’t understand 20% of what you are saying.
I recommend making a script and using https://elevenlabs.io/ for clear and easy to understand output.

Check @helloitsdamsky updated

For official tutorials that are onboarding our users to platform, we need native speakers or people who speak very clearly. Unfortunately, i still can’t understand 20% of what you are saying.
I recommend making a script and using https://elevenlabs.io/ for clear and easy to understand output.

I'll try to enhance my speech by using that

Check @helloitsdamsky updated

I'll try to enhance my speech by using that

Check @helloitsdamsky updated

I'll try to enhance my speech by using that

Cc @helloitsdamsky i made it using eleven labs ai under 60 seconds

Let’s please close this, this is far from quality we’d like to present kodadot with. We will need to create guidelines for content creators, otherwise both parties are loosing time.


Installer not working on Mac OSX

install.sh currently does not work on Mac. The JSON returned by curl -s https://api.github.com/repos/apex/apex/tags does not currently seem to include newlines, which causes this command to fail to actually correctly parse the latest tag. The grep/sed commands need updated. The current output on my machine:
$ LATEST=$(curl -s https://api.github.com/repos/apex/apex/tags | grep name | head -n 1 | sed 's/[," ]//g' | cut -d ':' -f 2)
$ echo $LATEST
v0.8.0zipball_url

hmm I swear we fixed this once already, thanks for the report!

similar issue https://github.com/apex/apex/pull/340

grep and sed cross-platform a pain because Mac OSX doesn't include GNU versions. This works on Mac and Ubuntu in my testing:
curl -s https://api.github.com/repos/apex/apex/tags | grep -Eo '"name":.*?[^\\]",'  | head -n 1 | sed 's/[," ]//g' | cut -d ':' -f 2

This and the original will both break if you use : in a tag name, but I don't think you would do that...

install.sh works fine for me on OSX.

Ok, very interesting... it would appear that for certain user-agent headers, github returns API calls without  any spacing or newlines. Try this to replicate the problem I was having:
curl -A 'My User Agent' -s https://api.github.com/repos/apex/apex/tags | grep name | head -n 1 | sed 's/[," ]//g' | cut -d ':' -f 2

For some reason I completely forget, I had a .curlrc setting user-agent = "Mozilla/5.0 (Windows; U; MSIE 9.0; Windows NT 9.0; en-US)"
The modified command I shared works whether the response includes linebreaks or not.

oh wow, nice find

The fix does not work for older version of grep (say latest OpenBSD 6.0 has grep 0.9). The error is grep: repetition-operator operand invalid. grep -Eo '"name":.*[^\\]",'  is good. I'll create a PR.


Integration Bus

This PR introduces IntegrationBus and ability to exchange messages between BoundedContexts.
Highlights:

IntegrationBus along with TransportFactory are introduced and represent a mechanism of inter-BoundedContext communication. Each BoundedContext may produce events and rejections in which other contexts are interested (the latter are downstream in this case). The messages of interest are brought to their subscribers/reactors via a customizable Transport, inspired by Publish-Subscribe messaging systems.

React(external = true) and Subscribe(external = true) now allow to process events and rejections that are fired by another bounded context. Handler methods marked external play an anticorruption layer role (see ACL pattern in "Domain-Driven Design" by Eric Evans and "Implementing Domain-Driven Design" by Vaughn Vernon) .

TransportFactory and MessageChannel concepts are introduced. There is also a naïve in-memory transport implementation for test purposes.

In addition, BoundedContextId is introduced to identify bounded contexts. It is an improvement to a String used for identification previously.
IntegrationBus
This bus is available as a part of single BoundedContext. In a multi-component environment messages may travel across components from one bounded context to another.
IntegrationBus is always based upon some transport (see more on that below), that delivers the messages from and to it. The messages from external components received by the IntegrationBus instance via the transport are propagated into the bounded context. They are dispatched to the subscribers and reactors marked with external = true on per-message-type basis.
IntegrationBus is also responsible for publishing the messages, born within the current BoundedContext, to external collaborators. To do that properly, the bus listens to a special document message called RequestForExternalMessages, that describes the needs of other parties.
E.g. bounded context Projects has the external event handler method in the projection as follows:
public class ProjectListView extends Projection<...> {

@Subscribe(external = true)
public void on(UserDeleted event) {
    // Remove the projects that belong to this user.
    // ...
}

// ...
}

Upon a registration of the corresponding repository the  integration bus of Projects context sends out a RequestForExternalMessages saying that an Event of UserDeleted is needed from other parties.
Let's say the second bounded context is Users. Its integration bus will receive the RequestForExternalMessages request sent out by Projects. To handle it properly it will create a bridge between Users's event bus (which may eventually be transmitting UserDeleted event) and an external transport. Once UserDeleted is published locally in Users context, it will be received by this bridge (as well as other local dispatchers), and published to the external transport.
The integration bus of Projects context will receive the UserDeleted external message. The event will be dispatched to the external event handler of ProjectListView projection.
TransportFactory and MessageChannel
This PR introduces an initial implementation of Publish-Subscribe Channel pattern.
The TransportFactory allows to create channels for outgoing messages (Publishers) and incoming messages (Subscribers).  Each channel serves messages of a single type.
In scope of this PR an in-memory implementation is provided, which is only suitable for the publishers and subscribers located within the same JVM. In the nearest future a Google Cloud-based implementation will be added to Spine.
The framework version is set to 0.9.65-SNAPSHOT.
To be delivered in the following PRs:

Google PubSub-based implementation of Transport along with proper integration tests.
RabbitMQ-based implementation of Transport along with proper integration tests.

@alexander-yevsyukov PTAL.

This bus is available as a part of single BoundedContext

How do we connect an Integration Bus within BC1 to an Integration Context within BC2 then?

@alexander-yevsyukov

How do we connect an Integration Bus within BC1 to an Integration Context within BC2 then?

They need to connect by transport. E.g. have the same PubSub (or RabbitMQ, Kafka etc) broker. This is done by configuring the TransportFactory that is supplied to IntegrationBus.Builder.
Originally my intention was to have an IntegrationBus inside a BoundedContext and some sort of IntegrationService external to bounded contexts — as a rendezvous point. However this idea did not work — it appeared too complex to design with no single point of failure.
With the current approach bounded contexts know nothing about each other, but are able to interconnect via transport channels in a shared space.

@alexander-yevsyukov comments are addressed. PTAL again.


Rhmap 17478 set docker image tags

Summary
Explicitly setting latest tag for images in dockerfile for both fh-messaging and fh-metrics

Retest this please.


report exception details

index a369f1c..d3f6930 100755
--- a/git-remote-dropbox
+++ b/git-remote-dropbox
@@ -671,8 +671,8 @@ def main():
     helper = Helper(token, url)
     try:
         helper.run()
-    except Exception:
-        stderr('error: unexpected exception\n')
+    except Exception as e:
+        stderr('error: unexpected exception {}\n'.format(e))
     except KeyboardInterrupt:
         # exit silently with an error code
         exit(1)

Sorry, I should have looked at CONTRIBUTING.md and created a PR, but since this issue is open I'll wait for your response.

Hmm, that would provide more information, but the goal of #9 was to have more human-readable exceptions, not printing out Python exception information or a stack trace.

I understand. I'm still familiarizing myself with the operation of git-remote-dropbox. I'll keep watching and look forward to the day I have something to contribute.

Okay, sounds good.


fix up correct env vars so the cdelivery service works on openshift

fix up correct env vars so the cdelivery service works on openshift

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/fabric8-quickstarts-master-pullreq/320/
Test PASSed.


release-20.2: importccl: support IMPORT in mixed-version cluster

PR: https://github.com/cockroachdb/cockroach/pull/57599
From release notes:

Added support for running IMPORT in a mixed-version cluster. [#57599][#57599] {% comment %}doc{% endcomment %}

Closing in favor of #9563


Support copy host ip to the clipboard in box and dot views

related issue [Feature Request] IP address copy on click

@vincent99 do we need a PR for 1.6-dev as well?


Marketo cloud configuration issue

Required Information

[ ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: Aem as a cloud service
[ ] ACS AEM Commons Version:  4.8.4
[ ] Reproducible on Latest? yes/no : yes

Expected Behavior
While creating a cloud service configuration for Marketo, the page shows Select Configuration Root and then we can create a new cloud service configuration.
Actual Behavior
While creating a cloud service configuration for Marketo, the page shows Select Configuration Root but no data is displayed on the page. Attached is a screenshot showing this issue. Please help me resolve this.
Steps to Reproduce
Go to Tools > Cloud Services > Marketo and hit create. You will see a blank screen instead of seeing an existing root. Please help me resolve this issue. I've also attached the document I'm following to create this steps.

Links
https://adobe-consulting-services.github.io/acs-aem-commons/features/marketo-form/index.html

Also just confirmed the same after a review with Adobe Support.  Using the latest ACS Commons version used on the latest Cloud SDK reproduces this issue.

Also just confirmed the same after a review with Adobe Support.  Using the latest ACS Commons version used on the latest Cloud SDK reproduces this issue.

Also just confirmed the same after a review with Adobe Support. Using the latest ACS Commons version used on the latest Cloud SDK reproduces this issue.

Also just confirmed the same after a review with Adobe Support. Using the latest ACS Commons version used on the latest Cloud SDK reproduces this issue.


Can the object detection library run inference on a video file as input?

The example object detection view uses an InputImage to process individual images coming from the stream of a camera. Is there an accessible solution to skip the camera part and feed the file path of the video?

The example object detection view uses an InputImage to process individual images coming from the stream of a camera. Is there an accessible solution to skip the camera part and feed the file path of the video?

The Google API only take an InputImage for the detector, not for video files. You would need to pass one frame at a time. That is technically possible but outside the scope of this plugin.
More details here:

https://github.com/flutter-ml/google_ml_kit_flutter/tree/master/packages/google_mlkit_commons#creating-an-inputimage
https://developers.google.com/ml-kit/vision/object-detection
https://github.com/flutter-ml/google_ml_kit_flutter/tree/master/packages/google_mlkit_object_detection#googles-ml-kit-object-detection-and-tracking-for-flutter


Menambahkan Link Ebook Free Indonesia

What does this PR do?
Add Resource(s) | Remove Resource(s) | Add info | Improve Repo
For resources
Description
Why is this valuable (or not)
How do we know it's really free?
For book lists, is it a book?
Checklist:

[ ] Not a duplicate
[ ] Included author(s) if appropriate
[ ] Lists are in alphabetical order
[ ] Needed indications added (PDF, access notes, under construction)

Good resource, but check travis-ci to see what the linter is failing for. (spaces) (I have lots of Hacktoberfest submissions to process!)

Closing this PR, as the resource is already in the repository.


feat: generating proto files using buf

This PR replaces tonic_build into buf. After cosmos 0.47.0, the proto files generation applies buf mainly.
Deps: https://github.com/desmos-labs/desmos/pull/1097
Deps: #183

The chain interaction error because broadcast mode sync does not wait for the tx including a block, we need to have a fix for it.


fixing small syntax errors and forgotten lines

a few lines were forgotten

I've fixed those errors on video.vhd ... lol

more to fix, scopeio_rgtr doesn't output pointer_xy
On 5/25/19, Miguel Angel<EMAIL_ADDRESS>wrote:

I've fixed those errors on video.vhd ... lol
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/hdl4fpga/hdl4fpga/pull/12#issuecomment-495942202

Probably. I messed something up there
On Sat, May 25, 2019 at 4:30 PM emard<EMAIL_ADDRESS>wrote:

more to fix, scopeio_rgtr doesn't output pointer_xy
On 5/25/19, Miguel Angel<EMAIL_ADDRESS>wrote:

I've fixed those errors on video.vhd ... lol
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/hdl4fpga/hdl4fpga/pull/12#issuecomment-495942202

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/hdl4fpga/hdl4fpga/pull/12?email_source=notifications&email_token=ACYCMOM4766UAUYYLI6GUQLPXGHVRA5CNFSM4HPVFSG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWHX2UA#issuecomment-495942992,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYCMOJHB6BG3ZGFLQT5RH3PXGHVRANCNFSM4HPVFSGQ
.

I think I fixed it ... i hope
On Sat, May 25, 2019 at 4:30 PM emard<EMAIL_ADDRESS>wrote:

more to fix, scopeio_rgtr doesn't output pointer_xy
On 5/25/19, Miguel Angel<EMAIL_ADDRESS>wrote:

I've fixed those errors on video.vhd ... lol
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/hdl4fpga/hdl4fpga/pull/12#issuecomment-495942202

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/hdl4fpga/hdl4fpga/pull/12?email_source=notifications&email_token=ACYCMOM4766UAUYYLI6GUQLPXGHVRA5CNFSM4HPVFSG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWHX2UA#issuecomment-495942992,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYCMOJHB6BG3ZGFLQT5RH3PXGHVRANCNFSM4HPVFSGQ
.


feat(module:steps): support customized starting index

close #1994
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #1994
What is the new behavior?
Now user can specify the starting index.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

We should merge this after Ant Design accept a PR.


Move to Amazon Corretto OpenJDK from Oracle Java SDK and 64-bit check

TagUI uses SikuliX as the visual automation / computer vision / OCR engine. SikuliX requires Java JDK v8 (64-bit) or later. However, Oracle now only allows the free version of Java JDK to be used for private non-commercial use.
Raising an issue to make a new release for TagUI for Python, with the following changes -

when Java is detected as not installed on user computer, point user to install OpenJDK from Amazon Corretto website instead of Oracle Java JDK website
added a new check when Java is detected as installed but it is not 64-bit version, point user to install OpenJDK from Amazon Corretto website

Change 2 is needed, otherwise for users with 32-bit Java, it gets undetected as an issue and visual automation will not be able to run properly and without explanation why. This change will remove confusion and troubleshooting time for minority of users who are having only 32-bit Java.

Implemented in v1.16, and now available with pip install tagui --upgrade


[PROPOSAL] Move the Dart code to support the libraries layout

This is the first step towards Federation. Moving dart classes around to better adhere to the libraries convention we decided on Flame.
I'm not sure what's the best place for each piece but this is my initial proposal. Consider this more of a RFC!
This is what it looks like on a more visual manner:

Things I am not sure:

where to put web: for now, a web folder outside of src seems the best place for me (until we properly federate).
"api": I invented this folder to store basically all our enums. eventually some interfaces could live there as well. I didn't want to put it inside src because in my view anyone should be able to import each enum (or api) as they need. For example, ap_web instead of having to import the AP implementation it only need to import the enums that it need. That being said I did create the ap_api.dart file outside src. So we could alternatively move the entire folder inside src, not sure.
I intentionally did not move PlayerControlCommand from inside notification_service into api because eventually that will become a standalone ap_notifications module, so I am keeping it together for now.

How I envision the future:

Step 1: this change.
Step 2: migrate repo to monorepo similar to flame. Only package will be packages/ap for now
Step 3: split into this (ap), platform interface (ap_platform_interface) and make android/darwin/web into federated packages + split all the notifications code indo ap_notifications. Now we have 6 plugins inside the packages folder on the monorepo.

The new structure LGTM

According to the package layout conventions, the API folder should be inside src. If they are meant to be used by anyone, they could be exported by a file under lib, ex: lib/api.dart. This simplifies imports for the package user.

@renancaraujo they are exported under audioplayers_api. I just thought might be useful to import specific enums as needed. But if it's not allowed I can change it.

Also what about web?

@renancaraujo they are exported under audioplayers_api. I just thought might be useful to import specific enums as needed. But if it's not allowed I can change it.

There is no clear advantage of importing individual files. for most cases, tree shaking and the "import show" syntax tackle possible performance and semantic problems.

Also what about web?

I honestly don't have strong opinions on that, I have even see people putting web code outside lib/ (some kind of lib_web/).

I honestly don't have strong opinions on that, I have even see people putting web code outside lib/ (some kind of lib_web/).

Wow, I didn't even know that was allowed haha. But then that folder gets the web code directly or does it also need its lib_web/src and API?
Of course when we federate web will go to another package anyway but wanted to not cause any issues.


support urlmanager in Javascript side

well i think a lot people have problems with this board, when need work with ajax,forms,etc
i see this GIT, is hard migrate this to the native js yii2 ?
https://github.com/ains/Yii-JSUrlManager
can add this enhacement ?

Url::to() is based on UrlManager rules. It means that we should expose all the url rules to the client side and I'm unsure whether this idea is good since it leads to full disclosure of URL rules. On other hand security through obscurity does not work, so developer should take care about proper requests filtering to any URL.

There's no issue security-wise.

i know sam but in what site i can submit this enhancement,etc and the board of the route is important :S

As I've said security through obscurity does not work, so admin board protection with URL hiding is not a protection at all. But I'm still worried with this, because beginners might not know about this feature at all and use hidden URLs for some sensitive actions.

It's not the case to care about.

probably related to #7649

If somehow we  an have the lazy loading principle that way only the url rules that are manualy set or checked against the server are loaded

@SilverFire

It means that we should expose all the url rules to the client side and I'm unsure whether this idea is good since it leads to full disclosure of URL rules.

Even if I agree with @samdark regarding we must not care about someone does security through obscurity (security ignorance is not something you guys core developers should care about), a real implementation would allow to control of what rules you exposes, and what not.
As an example of how others handle this: https://symfony.com/doc/master/bundles/FOSJsRoutingBundle/usage.html
# app/config/routing.yml
my_very_secret_route:
    pattern: /admin
    defaults: { _controller: HelloBundle:Admin:index }
    options:
        expose: false

I suppose we should discard this issue as it should be coupled with particular JavaScript framework.
At 2.1 we are plainning to decople JQuery from the core and I do not like the idea we should proceed towards the way of JS code improvement.
I prefer developer to choose which JS framework to use: React, Angular, JQuery and so on.
Unless particular imlementation of this feature can not be made at raw JavaScript level - it is better to put it out of the Yii scope.

Agree.

@klimov-paul

as it should be coupled with particular JavaScript framework

Can you elaborate in details how it would be tied up to some particular JS framework? When implementing this we can just use plain ES5 without using jQuery or other similar libraries (BTW: jQuery is library, not framework). What's the issue with that?
How I see it would be just a several (maybe single) function(s) declared in global/window JS scope. They would simply receive route name and parameters, and return some URL. Do we really need here to be tied up with jQuery or something similar? I think no.
These URL generator functions could be used everywhere: Vue.js, Angular, plain old jQuery etc.They would be JS library/framework agnostic.

Please investigate and examine this implementation of FOSJsRoutingBundle for Symfony 2+: https://github.com/FriendsOfSymfony/FOSJsRoutingBundle/tree/master/Resources/js
It doesn't use any library/framework, and simply does the job.

At 2.1 we are plainning to decople JQuery from the core

I'm voting to drop asset manager support at all in 2.1+, or at least decouple and move it to the external optional extension. I don't like I need to disable it in every single project I'm crafting now, since I never used it at all: why would I need it, if Gulp or even Webpack does this job much much better?

I'm voting to drop asset manager support at all in 2.1+

That's totally separate issue.

Assinged to 2.1.x. Could be done but certainly not a priority.

Can you elaborate in details how it would be tied up to some particular JS framework?

Many JS libraries have URL routing built-in. Usually it is coupled with AJAX in order to create 'one page' sites. The first one in this list is Backbone (nowadays it is almost forgotten).
If I wish to create a URL manager for JS code I wish it to be bound to the JS framework AJAX routing rather then to abstract library.

It doesn't use any library/framework, and simply does the job.

It does not looks to be independent to me as it depends on Google Closure Library:
https://github.com/FriendsOfSymfony/FOSJsRoutingBundle/blob/master/Resources/js/router.js#L3-L6

I'm voting to drop asset manager support at all in 2.1+, or at least decouple and move it to the external optional extension.

I can see no sense in it: it is your choice whether to use it or not. Asset manager and asset bundles system allows you to add at least a first JS include to your page. You may not need anything else - it is your will. I can see no harm in its existance.
I can say same thing for mutex classes in the end - it may be I do not need them, but it does not mean we should exract it to the separated repo.
This issue is not the place for such disscussion, see #8452.

Speaking about separated extensions, I think this feature should be implemented as separated extension.
Personally I never needed it and consider it to be a bad practice.
Also its implementation will bring other problems in the future: translating simple URL rules like
'<controller:\w+>\<action:\w+>' => '<controller>/<action>'

can be simple. But yii\web\UrlManager allows creating of complex rules with complex logic, which may involve database access and so on. For example: I may create a CMS, which allows random pages creation with unique URL keyword assigned to them, so for accessing such page following URL will be used:
http://example.com/page-slug

How will JS library contact the Database to check if particular page-slug exist or not?
Starting implementation for such feature we should support everything - otherwise developer will consider feature is not working.

Separate extension is a good solution. If it will be good, I'm fine linking to it from the guide.

@klimov-paul

Asset manager and asset bundles system allows you to add at least a first JS include to your page.

Uh, is it really necessary? It triggers additional classes eating PHP memory, consuming time, etc. What is wrong with <script type="text/javascript"></script>? Why would we need to trigger asset manager to register a freaking single JS file? :smile:

Starting implementation for such feature we should support everything - otherwise developer will consider feature is not working.

Please check my comments above, I mentioned there is no need to expose all the application rules to the client side.

Ok, there is no point in additional discussions as this has been rejected.

@resurtm there are two separate discussions going on. The one about dropping assets should not be done here for sure (and it's not rejected). The one about routing is, indeed, rejected to be implemented in framework core in favor of community extension.

It seems you do not listen.

Uh, is it really necessary? It triggers additional classes eating PHP memory, consuming time, etc.

here I have told you:

first of all, this issue is not the place for such discussion
second: unless you invoke AssetManger, e.g. you put your scripts in 'good old' way using <script type="text/javascript"></script> no class source code will be included no object will be created, no memory will be consumed.

Please check my comments above, I mentioned there is no need to expose all the application rules to the client side.

Here I have told you that half-solution is not a solution.


4.0 pulsar fix

this is #827 against the right base branch

some minor fixes for various missing keys or empty lists

LGTM


Faild Paid only

It seems that Slack has disabled auto subscribe facility. Every body is getting "Failed, paid only" message when user enter email and press enter

Yeah – just had this error, too. On both a new team and an old one. Was able to make it work by using the token included in the POST from the website UI, rather than the API token.

Sadly, slack blocked this api.

it works again

@yhsiang I comfirmed it. Thank you for noticing it.


Improve vendor fork experience

Vendors need proper documentation and repo improvements to ensure their forks aren't difficult to maintain.

I think the main outstanding item here is configure the helm chart for new vendors.
FYI @joshleecreates, @austinlparker

Do you mean documenting this?
https://cloud-native.slack.com/archives/C03B4CWV4DA/p1664974983694979

That link isn't redirecting properly for me so not sure. But at least have something like this documented for kubernetes

I'd be curious if vendors would like more specific documentation around forking + maintaining too. Microsoft doesn't have a fork today so I don't have a lived perspective

What I meant to share was the comment on slack by @puckpuck showing how to use helm to deploy the demo and configure the collector to a specific vendor

I can take a first stab at documenting the fork process this week.

I'd be curious if vendors would like more specific documentation around forking + maintaining too. Microsoft doesn't have a fork today so I don't have a lived perspective

From my perspective the key part will be documenting the options available via custom a custom values file. That covers all of the use cases Instana will need for our fork.

Yeah that'd be great to get @joshleecreates

Thanks for taking care of this Josh!


Add RabbitMQ 3.7

Adds a bunch of variables since there are many differences between 3.5 and 3.7:

3.7 requires an erlang version  only present in Alpine 3.8
rabbitmqadmin requires a different version
use of rabbitmqadmin w/ 3.7 requires a flag to ignore untrusted CA, the 3.5 version was manually patched because it had no such flag
Download locations, file names, file types, and unzip commands are different between installers for 3.5 and 3.7
Ditto for the delayed message exchange plugin
Changed the username for testing from "user" to "testuser": the command rabbitmqctl list_users now returns a header that contains the string "user", which broke add_user_if_not_exists ()

Other things fixed:

The "It should be able to publish and retrieve a message" didn't actually publish or retrieve a message
Useless use of run; [ "$status" -eq "0" ] in bats test
Use library/alpine directly

@UserNotFound is this ready to go?

@UserNotFound is this ready for a final review?

Yes, thank you!


[documentation] grammatical fixes in first_rows.mdx

The changes made are grammatical and do not affect the ideas communicated in the file.

Thanks for the contribution!
Nevertheless, in that case, the text is part of a dataset, and should be maintained unchanged. WDYT @stevhliu?

Yeah I agree with @severo, it is an example from a dataset and not something we authored.

Thanks for the proposal. I'll close this one, but happy to get other feedback and contributions on the docs, we try to improve it regularly.


Docker with GPU

This PR replace the use of the cuda-10.1 image in favour of thetensorflow/tensorflow:1.15.5-gpu image.
It should solve the problem of the GPU not being really used when running it with docker
This python script can be used for testing the real use of GPU and also troubleshoot when it does not work (sometimes can happen that the GPU is not found - without any apparent reason):

According to my tests the GPU memory is filled up correctly

The image for testing is pushed with name lfoppiano/grobid:test

I can confirm it works also with derived docker images ;-)

@kermitt2 another aspect that I would be interested to test is to calculate the maximum batch size given a fixed max length size for a certain amount of GPU memory, I guess this could be done with delft via a python script?

another aspect that I would be interested to test is to calculate the maximum batch size given a fixed max length size for a certain amount of GPU memory, I guess this could be done with delft via a python script?

It depends on the model architecture. So I think there is no way in general to know in advance, but it might be related to the number of parameters of the model.

It depends on the model architecture. So I think there is no way in general to know in advance, but it might be related to the number of parameters of the model.

Sorry I meant by setting also the architecture

Sorry I meant by setting also the architecture

It sounds complicated to do in general for DeLFT, but for Grobid we can't know in advance the number of models that would be running on GPU so automating this is probably not doable.

Sorry I meant by setting also the architecture

It sounds complicated to do in general for DeLFT, but for Grobid we can't know in advance the number of models that would be running on GPU so automating this is probably not doable.

Yes sorry, indeed it makes no sense if more models are used in parallel.
What I'm not sure of is that JEP uses just one thread, right? So,  does it means that different models cannot be called in parallel?

In the current settings, all the DL models together are using an Executor of size 1, so different models can be loaded and called in parallel, but only one will run at the same time. The other are blocked while the run of the current one is done.
The motivation is that, if I am not wrong, one single model inference is done at the same time on one GPU (there is a kind of lock of the GPU managed by TensorFlow), so one JEP thread is enough. However, the JEP instance will indeed load and initialize several models if requested.
If you look at https://github.com/kermitt2/grobid/blob/master/grobid-core/src/main/java/org/grobid/core/jni/JEPThreadPool.java it's possible to manage a thread of pools with several JEP instances (one JEP instance is bounded by the thread that initialized it), so it should possible in theory to have multiple models running in different threads. But I think because I've never been able to use more than one GPU, I've never been able to really test the usage of parallel inference on multiple GPU further.

@bnewbold Could you test it with CUDA 11.x and let me know whether it works? It should work fine with CUDA 10.1 / 10.2

My current tests:

CUDA 9 -> not working, but not a problem
fallback to CPU when no GPU -> working

For CUDA 10.*, I still have a process running on the machine... I will also try to build on a machine without GPU and test on machine with GPU to be complete.

There is a typo in this change (FROM FROM), resulting in:
Error response from daemon: dockerfile parse error line 64: FROM requires either one or three arguments

There is a typo in this change (FROM FROM), resulting in:
Error response from daemon: dockerfile parse error line 64: FROM requires either one or three arguments

oh sorry about that...
You could try directly the image lfoppiano/grobid:test

There is a typo in this change (FROM FROM), resulting in:

@lfoppiano gasp you couldn't see my comment right? How can I make those things more visible?

There is a typo in this change (FROM FROM), resulting in:

@lfoppiano gasp you couldn't see my comment right? How can I make those things more visible?

oh... I did not see it..
I suppose that after the comment you have to "start review"?
I'm not sure but the Github workflow for review is too clumsy ....

I suppose that after the comment you have to "start review"?

it's what I did :(

I'm not sure but the Github workflow for review is too clumsy ....

yes... not sure how to do it now.

Coverage decreased (-0.003%) to 39.563% when pulling da3f14220f70733e278138e513e7650664eaa8e3 on feature/change-base-image-delft-docker into 98d9ed98a115f657b0139c5db8a85a360d279d0d on master.

I started testing on two VMs, but got interrupted and had to tear them down. If I have time tomorrow i'll give it a try.

It works for me too with CUDA 10.1
|===============================+======================+======================|
|   0  GeForce GTX 105...  Off  | 00000000:01:00.0  On |                  N/A |
| 45%   37C    P8    N/A /  75W |   3875MiB /  4036MiB |     17%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
...
|    0     22139      C   java                                        3335MiB |

I've updated the documentation and the image on DockerHub... this is ready to merge I think.

Great!


Remove "provider" module because of Beacon

trello#71

+1 on this, but wait for me to create the beacons/list endpoint first so the frontend has something to show.

@ngmiller @zach-taylor this is ready to go as soon as it would break the frontend :)

@cmbrose Excellent - I'll test this out and update the frontend accordingly. Should have a PR in the next couple of days


Tensorflow 1.13.0 reports wrong version

System information

OS Platform and Distribution: Linux Ubuntu 16.04
TensorFlow installed from: source
TensorFlow version: 1.13.0
Python version: 3.5.2
Bazel version : 0.22.0
GCC/Compiler version (if compiling from source): 5.4.0
CUDA/cuDNN version: cuda10.0 cudnn<IP_ADDRESS>
GPU model and memory: GTX1070

Tensorflow compiled and built without issue. But when created wheel with command
 ./bazel-bin/tensorflow/tools/pip_package/build_pip_package $HOME/opt/cuda_test/cuda10/tensorflow_pkg

The wheel created was called tensorflow-1.12.0-cp35-cp35m-linux_x86_64.whl
I changed 1.12.0 to 1.13.0 manually and install it with pip
cd $HOME/tensorflow_pkg
pip3 install --no-cache-dir ./tensorflow-1.13.0-cp35-cp35m-linux_x86_64.whl --user
Processing ./tensorflow-1.13.0-cp35-cp35m-linux_x86_64.whl
Requirement already satisfied: absl-py>=0.1.6 in /home/bernard/opt/cuda_test/cuda10/lib/python3.5/site-packages (from tensorflow==1.13.0) (0.7.0)
Requirement already satisfied: keras-preprocessing>=1.0.5 in /usr/local/lib/python3.5/dist-packages (from tensorflow==1.13.0) (1.0.5)
Requirement already satisfied: six>=1.10.0 in /usr/local/lib/python3.5/dist-packages (from tensorflow==1.13.0) (1.11.0)
Requirement already satisfied: keras-applications>=1.0.6 in /usr/local/lib/python3.5/dist-packages (from tensorflow==1.13.0) (1.0.6)
Requirement already satisfied: google-pasta>=0.1.2 in /home/bernard/opt/cuda_test/cuda10/lib/python3.5/site-packages (from tensorflow==1.13.0) (0.1.4)
Requirement already satisfied: gast>=0.2.0 in /home/bernard/opt/cuda_test/cuda10/lib/python3.5/site-packages (from tensorflow==1.13.0) (0.2.2)
Requirement already satisfied: protobuf>=3.6.1 in /home/bernard/opt/cuda_test/cuda10/lib/python3.5/site-packages (from tensorflow==1.13.0) (3.6.1)
Requirement already satisfied: numpy<2.0,>=1.14.5 in /home/bernard/opt/cuda_test/cuda10/lib/python3.5/site-packages (from tensorflow==1.13.0) (1.16.1)
Requirement already satisfied: grpcio>=1.8.6 in /home/bernard/opt/cuda_test/cuda10/lib/python3.5/site-packages (from tensorflow==1.13.0) (1.18.0)
Requirement already satisfied: wheel>=0.26 in /usr/local/lib/python3.5/dist-packages (from tensorflow==1.13.0) (0.31.1)
Requirement already satisfied: tensorflow-estimator<1.14.0rc0,>=1.13.0rc0 in /home/bernard/opt/cuda_test/cuda10/lib/python3.5/site-packages (from tensorflow==1.13.0) (1.13.0rc0)
Requirement already satisfied: termcolor>=1.1.0 in /home/bernard/opt/cuda_test/cuda10/lib/python3.5/site-packages (from tensorflow==1.13.0) (1.1.0)
Requirement already satisfied: astor>=0.6.0 in /home/bernard/opt/cuda_test/cuda10/lib/python3.5/site-packages (from tensorflow==1.13.0) (0.7.1)
Requirement already satisfied: tensorboard<1.13.0,>=1.12.0 in /home/bernard/opt/cuda_test/cuda10/lib/python3.5/site-packages (from tensorflow==1.13.0) (1.12.2)
Requirement already satisfied: h5py in /usr/local/lib/python3.5/dist-packages (from keras-applications>=1.0.6->tensorflow==1.13.0) (2.9.0)
Requirement already satisfied: setuptools in /usr/local/lib/python3.5/dist-packages (from protobuf>=3.6.1->tensorflow==1.13.0) (40.8.0)
Requirement already satisfied: mock>=2.0.0 in /usr/local/lib/python3.5/dist-packages (from tensorflow-estimator<1.14.0rc0,>=1.13.0rc0->tensorflow==1.13.0) (2.0.0)
Requirement already satisfied: werkzeug>=0.11.10 in /home/bernard/opt/cuda_test/cuda10/lib/python3.5/site-packages (from tensorboard<1.13.0,>=1.12.0->tensorflow==1.13.0) (0.14.1)
Requirement already satisfied: markdown>=2.6.8 in /home/bernard/opt/cuda_test/cuda10/lib/python3.5/site-packages (from tensorboard<1.13.0,>=1.12.0->tensorflow==1.13.0) (3.0.1)
Requirement already satisfied: pbr>=0.11 in /usr/local/lib/python3.5/dist-packages (from mock>=2.0.0->tensorflow-estimator<1.14.0rc0,>=1.13.0rc0->tensorflow==1.13.0) (4.0.4)
Installing collected packages: tensorflow
**Successfully installed tensorflow-1.12.0**

From last sentence of ouput above python still sees tensorflow-1.12.0
Now
$ python3
Python 3.5.2 (default, Nov 12 2018, 13:43:14)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.

import tensorflow as tf
Limited tf.compat.v2.summary API due to missing TensorBoard installation

I meet the same situation LOL

Same situation ...

Same issue ..

Same issue here...

same issue to me:
ubuntu 18.04.2 LTS
python 3.6.7
Bazel version : 0.22.0
NO GPU

And the PyPI hasn't been updated yet.

same issue,but my tensorboard run properly.
maybe you can try compile your code in terminal,
then try
tensorboard --logdir="./graphs" --port number(anyone you want)
and open the address you set in browser(ie.http://localhost:10086/)

Is it because TF_MINOR_VERSION is still 12? I have submitted #26051 to update it.

You can change the version by editing tensorflow-1.13.0/tensorflow/tools/pip_package/setup.py and change line 48 to _VERSION = '1.13.0' (typo in the original?) But the tensorboard error persists.
Limited tf.compat.v2.summary API due to missing TensorBoard installation

Yeah, it is because you need more than renaming the file to update the version.
Did you build it from the branch r1.13?

@gunan
I downloaded the 1.13 release tarball  from https://github.com/tensorflow/tensorflow/releases Now 1.13 appears to have been removed from the server (unreleased?) since is the latest version on the link is back to 1.13rc2 since maybe last night.

I made a mistake with that, and that tarball was created with the master version. 1,13,1 is being prepared which will have the correct sources.

@gunan
It works now, tf 1.13.1 compiled and installed successfully. Thanks!


⚠ Turnos 24x7 has degraded performance

In 6c9f4e5, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 856 ms

Resolved: Turnos 24x7 performance has improved in 948d485.


Implement internal add and remove mc owner.

This change is

src/main/kotlin/org/wfanet/measurement/kingdom/service/internal/testing/Population.kt, line 229 at r1 (raw file):
Previously, SanjayVas (Sanjay Vasandani) wrote…
Any reason not to split this up into separate createAccount and activateAccount methods? It's more explicit and you don't need to return two different values.

I have been doing it as one method for convenience purposes.

src/main/kotlin/org/wfanet/measurement/kingdom/service/internal/testing/Population.kt, line 229 at r1 (raw file):
Previously, tristanvuong2021 (Tristan Vuong) wrote…
I have been doing it as one method for convenience purposes.

But I suppose calling 2 methods instead of one isn't that bad.


How to exclude dependencies?

Hi,
I am running the following command:
terragrunt apply-all --terragrunt-include-dir devops/amazing-app/k8s/

In the terragrunt.hcl file there is a dependency block defined for another component.
When running the above command the component specified in the dependency block is being installed, I would like to install only the components specified in --terragrunt-include-dir without their dependencies.
Is there a way to achieve this?
Thanks

@yorinasub17, devops/amazing-app/k8s contains a single terragrunt.hcl file with a reference to a single module.
What I would like to do, is to run terragrunt apply-all --terragrunt-include-dir devops/app1/k8s/ --terragrunt-include-dir devops/app2/k8s/ and have terrgrunt to install only the components specified in --terragrunt-include-dir (app1 and app2) and install them according in the order of dependencies between them. I don't want terragrunt to install dependencies specified within these components which I have not included with --terragrunt-include-dir.
Please let me know if it makes sense.
Thanks!

--terragrunt-ignore-external-dependencies is probably the flag you are looking for: https://terragrunt.gruntwork.io/docs/reference/cli-options/#terragrunt-ignore-external-dependencies

@yorinasub17 I've already tried using this flag and it did nothing.
I assume it's meant for ignoring the dependencies of the dependencies.

That's probably a bug then. Can you share the following so we can take a look?

Your folder structure
terragrunt.hcl of devops/amazing-app/k8s
terragrunt.hcl of a dependency being pulled in
The FULL output of the logs from a terragrunt call.

So it seems that the behaviour is irregular.
Now when running terragrunt apply-all --terragrunt-include-dir devops/amazing-app/k8s the dependency is not being included, but running the same command on a different component which is configured exactly the same the dependency is being included.
I have cleared the cache on all folders with the same results.
Folder structure:
.
├── Makefile
├── README.md
├── devops
│   ├── amazing-app
│   │   ├── k8s
│   │   │   ├── terragrunt.hcl
│   │   │   └── values_us-east-1_dev.yaml
│   │   └── s3
│   │       ├── terragrunt.hcl
│   │       └── values_us-east-1_dev.yaml
│   ├── eks-ocean
│   │   └── eks-ocean
│   │       ├── terragrunt.hcl
│   │       └── values_us-east-1_dev.yaml
│   ├── example
│   │   ├── ecr
│   │   │   ├── terragrunt.hcl
│   │   │   └── values.yaml
│   │   ├── helm
│   │   │   └── values.yaml
│   │   ├── k8s
│   │   │   ├── terragrunt.hcl
│   │   │   ├── values.yaml
│   │   │   └── values_example.yaml
│   │   ├── kms
│   │   │   ├── terragrunt.hcl
│   │   │   └── values.yaml
│   │   └── s3
│   │       ├── terragrunt.hcl
│   │       └── values.yaml
│   ├── kms
│   │   └── kms
│   │       ├── terragrunt.hcl
│   │       ├── values_us-east-1_dev.yaml
│   └── testonico
│       ├── k8s
│       │   ├── terragrunt.hcl
│       │   └── values_us-east-1_dev.yaml
│       └── legacy
│           ├── main.tf
│           ├── outouts.tf
│           ├── terragrunt.hcl
│           ├── values_us-east-1_dev.tfvars
│           └── variables.tf

terragrunt.hcl of devops/amazing-app/k8s and devops/testonico/k8s:
terraform {
  source = "../../../modules/k8s"
}

skip = fileexists("values_${get_env("TF_VAR_environment", "")}.yaml") ? false : true

dependency "eks-ocean" {
  config_path  = "../../../devops/eks-ocean/eks-ocean"
  skip_outputs = true
}

include {
  path = find_in_parent_folders()
}

terragrunt.hcl of devops/eks-ocean/eks-ocean:
terraform {
source = "../../../modules/eks"
}
skip = fileexists("values_${get_env("TF_VAR_environment", "")}.yaml") ? false : true
prevent_destroy = true
include {
path = find_in_parent_folders()
}

Logs from ```devops/amazing-app/k8s```:

[terragrunt] 2020/02/19 10:48:55 Setting download directory for module /Repositories/infra to /Repositories/infra/.terragrunt-cache
[terragrunt] 2020/02/19 10:48:55 Module /Repositories/infra does not have an associated terraform configuration and will be skipped.
[terragrunt] 2020/02/19 10:48:55 Setting download directory for module /Repositories/infra/devops/amazing-app/k8s to /Repositories/infra/devops/amazing-app/k8s/.terragrunt-cache
[terragrunt] 2020/02/19 10:48:55 Setting download directory for module /Repositories/infra/devops/amazing-app/s3 to /Repositories/infra/devops/amazing-app/s3/.terragrunt-cache
[terragrunt] 2020/02/19 10:48:55 Setting download directory for module /Repositories/infra/devops/eks-ocean/eks-ocean to /Repositories/infra/devops/eks-ocean/eks-ocean/.terragrunt-cache
[terragrunt] 2020/02/19 10:48:55 Setting download directory for module /Repositories/infra/devops/example/ecr to /Repositories/infra/devops/example/ecr/.terragrunt-cache
[terragrunt] 2020/02/19 10:48:55 Setting download directory for module /Repositories/infra/devops/example/k8s to /Repositories/infra/devops/example/k8s/.terragrunt-cache
[terragrunt] 2020/02/19 10:48:55 Setting download directory for module /Repositories/infra/devops/example/kms to /Repositories/infra/devops/example/kms/.terragrunt-cache
[terragrunt] 2020/02/19 10:48:55 Setting download directory for module /Repositories/infra/devops/example/s3 to /Repositories/infra/devops/example/s3/.terragrunt-cache
[terragrunt] 2020/02/19 10:48:55 Setting download directory for module /Repositories/infra/devops/kms/kms to /Repositories/infra/devops/kms/kms/.terragrunt-cache
[terragrunt] 2020/02/19 10:48:55 Setting download directory for module /Repositories/infra/devops/testonico/k8s to /Repositories/infra/devops/testonico/k8s/.terragrunt-cache
[terragrunt] 2020/02/19 10:48:55 Setting download directory for module /Repositories/infra/devops/testonico/legacy to /Repositories/infra/devops/testonico/legacy/.terragrunt-cache
[terragrunt] 2020/02/19 10:48:55 Stack at /Repositories/infra:
=> Module /Repositories/infra/devops/amazing-app/k8s (excluded: false, dependencies: [/Repositories/infra/devops/eks-ocean/eks-ocean])
=> Module /Repositories/infra/devops/amazing-app/s3 (excluded: true, dependencies: [])
=> Module /Repositories/infra/devops/eks-ocean/eks-ocean (excluded: true, dependencies: [])
=> Module /Repositories/infra/devops/example/ecr (excluded: true, dependencies: [])
=> Module /Repositories/infra/devops/example/k8s (excluded: true, dependencies: [/Repositories/infra/devops/eks-ocean/eks-ocean])
=> Module /Repositories/infra/devops/example/kms (excluded: true, dependencies: [])
=> Module /Repositories/infra/devops/example/s3 (excluded: true, dependencies: [])
=> Module /Repositories/infra/devops/kms/kms (excluded: true, dependencies: [])
=> Module /Repositories/infra/devops/testonico/k8s (excluded: true, dependencies: [/Repositories/infra/devops/eks-ocean/eks-ocean])
=> Module /Repositories/infra/devops/testonico/legacy (excluded: true, dependencies: [])
[terragrunt] 2020/02/19 10:48:55 [terragrunt]  Are you sure you want to run 'terragrunt apply' in each folder of the stack described above? (y/n)

Logs from ```devops/testionico/k8s```:

[terragrunt] 2020/02/19 10:55:29 Module /Repositories/infra does not have an associated terraform configuration and will be skipped.
[terragrunt] 2020/02/19 10:55:29 Setting download directory for module /Repositories/infra/devops/amazing-app/k8s to /Repositories/infra/devops/amazing-app/k8s/.terragrunt-cache
[terragrunt] 2020/02/19 10:55:29 Setting download directory for module /Repositories/infra/devops/amazing-app/s3 to /Repositories/infra/devops/amazing-app/s3/.terragrunt-cache
[terragrunt] 2020/02/19 10:55:29 Setting download directory for module /Repositories/infra/devops/eks-ocean/eks-ocean to /Repositories/infra/devops/eks-ocean/eks-ocean/.terragrunt-cache
[terragrunt] 2020/02/19 10:55:29 Setting download directory for module /Repositories/infra/devops/example/ecr to /Repositories/infra/devops/example/ecr/.terragrunt-cache
[terragrunt] 2020/02/19 10:55:29 Setting download directory for module /Repositories/infra/devops/example/k8s to /Repositories/infra/devops/example/k8s/.terragrunt-cache
[terragrunt] 2020/02/19 10:55:29 Setting download directory for module /Repositories/infra/devops/example/kms to /Repositories/infra/devops/example/kms/.terragrunt-cache
[terragrunt] 2020/02/19 10:55:29 Setting download directory for module /Repositories/infra/devops/example/s3 to /Repositories/infra/devops/example/s3/.terragrunt-cache
[terragrunt] 2020/02/19 10:55:29 Setting download directory for module /Repositories/infra/devops/kms/kms to /Repositories/infra/devops/kms/kms/.terragrunt-cache
[terragrunt] 2020/02/19 10:55:29 Setting download directory for module /Repositories/infra/devops/testonico/k8s to /Repositories/infra/devops/testonico/k8s/.terragrunt-cache
[terragrunt] 2020/02/19 10:55:29 Setting download directory for module /Repositories/infra/devops/testonico/legacy to /Repositories/infra/devops/testonico/legacy/.terragrunt-cache
[terragrunt] 2020/02/19 10:55:29 Stack at /Repositories/infra:
=> Module /Repositories/infra/devops/amazing-app/k8s (excluded: true, dependencies: [/Repositories/infra/devops/eks-ocean/eks-ocean])
=> Module /Repositories/infra/devops/amazing-app/s3 (excluded: true, dependencies: [])
=> Module /Repositories/infra/devops/eks-ocean/eks-ocean (excluded: false, dependencies: [])
=> Module /Repositories/infra/devops/example/ecr (excluded: true, dependencies: [])
=> Module /Repositories/infra/devops/example/k8s (excluded: true, dependencies: [/Repositories/infra/devops/eks-ocean/eks-ocean])
=> Module /Repositories/infra/devops/example/kms (excluded: true, dependencies: [])
=> Module /Repositories/infra/devops/example/s3 (excluded: true, dependencies: [])
=> Module /Repositories/infra/devops/kms/kms (excluded: true, dependencies: [])
=> Module /Repositories/infra/devops/testonico/k8s (excluded: false, dependencies: [/Repositories/infra/devops/eks-ocean/eks-ocean])
=> Module /Repositories/infra/devops/testonico/legacy (excluded: true, dependencies: [])
[terragrunt] 2020/02/19 10:55:29 [terragrunt]  Are you sure you want to run 'terragrunt apply' in each folder of the stack described above? (y/n)

Can you update the logs with:

The actual command you ran
Which folder you ran from

I've updated the logs with the command I ran.
I ran it from the root directory where the parent terragrunt.hcl file is placed - /Repositories/infra/

Thanks! Will take a look at this at my earliest convenience.

Thanks @yorinasub17.
I did run the commands several times with and without --terragrunt-ignore-external-dependencies and it did not make a difference.

Ok I have reproduced the behavior and have a fix in https://github.com/gruntwork-io/terragrunt/pull/1062

Thanks!

This should now be fixed in https://github.com/gruntwork-io/terragrunt/releases/tag/v0.22.4. You can use --terragrunt-strict-include to exclude the dependencies.

I tested the fix to --terragrunt-include-dir and the new --terragrunt-strict-include feature and they are both working as expected.
Thanks!


fix: protobuf-java version for CVE-2024-7254

Fixes a vuln.
Issue to revert in future: https://github.com/open-feature/java-sdk-contrib/issues/1031

Is there a ticket we can follow in gRPC java?

Kinda - it's mentioned here.


[FEATURE] move model_name to distilabel_metadata dictionary with step name suffix

Is your feature request related to a problem? Please describe.
Along with the addition of raw_output_<step_name> and the proposed raw_input_<step_name> (https://github.com/argilla-io/distilabel/issues/698). I think it would be nice to align this a bit more also move the model_name to the distilabel_metadata and add a suffix of the step name, restulting in model_name_<step_name>.
Describe the solution you'd like
CURRENT
# [
#     {
#         "instruction": "What's the capital of Spain?",
#         "generation": "The capital of Spain is Madrid.",
#         "model_name": "gpt-4",
#         "distilabel_metadata": {
#             "raw_output_text-generation": "The capital of Spain is Madrid"
#         }
#     }
# ]

PROPOSED UPDATE
# [
#     {
#         "instruction": "What's the capital of Spain?",
#         "generation": "The capital of Spain is Madrid.",
#         "distilabel_metadata": {
#             "raw_output_text-generation": "The capital of Spain is Madrid",
#             "model_name-generation": "gpt-4"
#         }
#     }
# ]

Describe alternatives you've considered
N.A:
Additional context
N.A.

Hi here! I don't think we should move that to metadata, we can indeed ALSO move it to metadata, but not to be the only place, since some tasks do expect the model or some sort of identifier for e.g. the generations, and we're already actively using this along the codebase. Maybe what we need to do is to improve the wording and how we communicate about the model_name being automatically injected and in pipelines with more than 1 sequential task needing a rename / output mapping.
cc @gabrielmbmb @plaguss to share their opinion too (if any)

Hi @alvarobartt, I did not it was being used internally. How are we using it exactly? I think moving it ALSO would help with some tracing intermediary steps, results etc, likely with similar / mostly the same reasoning as for the raw_output and raw_input usages.

Hi @alvarobartt, I did not it was being used internally. How are we using it exactly? I think moving it ALSO would help with some tracing intermediary steps, results etc, likely with similar / mostly the same reasoning as for the raw_output and raw_input usages.

Oops sorry, maybe my wording was not the best! I meant we use that in some examples, tutorials, etc. as well as optional inputs in the preference / rating / ranking steps, so that would lead to potential conflicts with existing pipelines that do use that model_name or whatever rename is applied to that property. But I agree that adding that within the metadata makes a lot of sense, I was just advocating for not removing the current model_name but just copying it over to the metadata aka. raw outputs.

Hi! related to this change, we initially moved the model_name to the distilabel_metadata column but decided to keep it in its own column because it can be used easily with CombineColumns for example, what would yield a dataset similar to the UltraFeedback format for example. Also, having the model_name in it's own column makes it easier to update the column name if you want to store the column (just renaming the column):
text_generation = TextGeneration(
    llm=...,
    output_mappings={"model_name": "generation_model"},
)

or for multiple models, if one just let's the column be overridden and removes the model_name column at the end, less work to do.


Custom evaluation order

Changes

Closes #7 (oldest open issue!).
Allows using different C++ evaluation orders in "EventOrderingFunction" options.
Orders currently supported are: "OldestEdge", "LeastOldEdge", "LeastRecentEdge", "NewestEdge", "RuleOrdering", "ReverseRuleOrdering", "RuleIndex", "ReverseRuleIndex", "Random".
Lists of these are also supported, in which case the next one in the list is used in case of collisions.
If the list of specified functions is not sufficient to determine priority, the random among smallest is chosen (hence, i.e., {} can be used instead of "Random").

Tests

Evolve a WolframModel with all individual event ordering functions:

In[] := WolframModel[{{1, 2}, {1, 3}, {1, 4}} -> {{5, 6}, {6, 7}, {7, 5}, {5,
      7}, {7, 6}, {6, 5}, {5, 2}, {6, 3}, {7, 4}, {2, 7}, {4,
      5}}, {{1, 1}, {1, 1}, {1, 1}}, <|"MaxEvents" -> 100|>,
   "FinalStatePlot", "EventOrderingFunction" -> #] & /@ {"OldestEdge",
   "LeastOldEdge", "LeastRecentEdge", "NewestEdge", "RuleOrdering",
  "ReverseRuleOrdering", "RuleIndex", "ReverseRuleIndex", "Random"}

Note, most of them are not deterministic by themselves:

In[] := WolframModel[{{1, 2}, {1, 3}, {1, 4}} -> {{5, 6}, {6, 7}, {7, 5}, {5,
      7}, {7, 6}, {6, 5}, {5, 2}, {6, 3}, {7, 4}, {2, 7}, {4,
      5}}, {{1, 1}, {1, 1}, {1, 1}}, <|"MaxEvents" -> 100|>,
   "FinalStatePlot", "EventOrderingFunction" -> #] & /@ {"OldestEdge",
   "LeastOldEdge", "LeastRecentEdge", "NewestEdge", "RuleOrdering",
  "ReverseRuleOrdering", "RuleIndex", "ReverseRuleIndex", "Random"}

Use standard order in case of conflicts:

In[] := WolframModel[{{1, 2}, {1, 3}, {1, 4}} -> {{5, 6}, {6, 7}, {7, 5}, {5,
      7}, {7, 6}, {6, 5}, {5, 2}, {6, 3}, {7, 4}, {2, 7}, {4,
      5}}, {{1, 1}, {1, 1}, {1, 1}}, <|"MaxEvents" -> 100|>,
   "FinalStatePlot",
   "EventOrderingFunction" -> {#, "LeastRecentEdge",
     "RuleOrdering"}] & /@ {"OldestEdge", "LeastOldEdge",
  "LeastRecentEdge", "NewestEdge", "RuleOrdering",
  "ReverseRuleOrdering", "RuleIndex", "ReverseRuleIndex", "Random"}

Now, only "Random" is non-deterministic:

In[] := WolframModel[{{1, 2}, {1, 3}, {1, 4}} -> {{5, 6}, {6, 7}, {7, 5}, {5,
      7}, {7, 6}, {6, 5}, {5, 2}, {6, 3}, {7, 4}, {2, 7}, {4,
      5}}, {{1, 1}, {1, 1}, {1, 1}}, <|"MaxEvents" -> 100|>,
   "FinalStatePlot",
   "EventOrderingFunction" -> {#, "LeastRecentEdge",
     "RuleOrdering"}] & /@ {"OldestEdge", "LeastOldEdge",
  "LeastRecentEdge", "NewestEdge", "RuleOrdering",
  "ReverseRuleOrdering", "RuleIndex", "ReverseRuleIndex", "Random"}

all of the standard ordering functions appear to be completely deterministic in all of the cases that I've tried, with the obvious exception of "Random").

I'm not sure what you mean by standard ordering functions, but you typically need to use multiple of them to make them completely deterministic, and you can see in the first two examples, the outputs are actually different for almost all of the single functions.

"LeastRecentEdge" seems to give almost universally boring output

I guess you mean "LeastOldEdge". "LeastRecentEdge" is what we used by default.


Expression plot minimaps don't work on Windows

Reported by @young-x-skyee

@young-x-skyee I'm here to help with this where I can!

Thanks a lot, Cai! I'll be in CBU on Monday and post the details about the bug then.

When I'm trying to install the packages specified in poetry, this error occurred

And when I'm running the script using the old packages, I got this error

This is super weird. Good job tracking down the error. Do the unit tests run on Windows?

One more Q: this issue suggests the issue arrises in particular when doing expression plots with minimaps - is this actually a key part of causing the error or is it just a coincidence that that's what you were trying to do when you noticed it?

Correct! This latest issue is not related to the minimals - we found it while trying to fix that problem. We should split this into a new issue.

Ok, this one has details of the .nkg issue so I'll rename it and make a new one for the minimaps


Increase size of the language column in language_stat

In #12379 it was discovered that enry v2 has a maximum language length
of 34 characters which is larger than the 30 previously provided.
This PR updates the language column to 50.
Fix #12379
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Contains #12395

So actually thinking on, because sqlite doesn't need to change schema - varchar is mapped to text -  I think we might be able to get away with just using ALTER TABLE in this case.
I'll keep this code though and add a doctor command that will allow you to recreate tables from the schema - that will finally allow us to be able to get rid of the weird warning messages about defaults having changed.

Finally I think I've solved (again) all the issues with the different dialects.

@lafriks unfortunately a general solution is not very easy at all. In particular SQLite poses a particular problem here.
SQLite doesn't have a mechanism for changing the type of a column and you can't create a column with a unique not null constraint on an already existing table. So you're limited to copying the table and adding the column.
In reality the simplest thing to do is to recreate the table in its entirety from bean definition - I've provided that as another PR.
A general method that keeps the previous columns would be possible but I suspect that it may not be worth it.

Otherwise LGTM

make lg-tm work

Hmm it seems this migration is giving me some against MariaDB:
routers/init.go:71:initDBEngine() [I] ORM engine initialization attempt #3/10...
...rm/session_schema.go:25:Ping() [I] PING DATABASE mysql
...ations/migrations.go:310:Migrate() [I] Migration[145]: Increase Language field to 50 in LanguageStats
routers/init.go:77:initDBEngine() [E] ORM engine initialization attempt #3/10 failed. Error: migrate: do migrate: Error 1062: Duplicate entry 'JavaScript' for key 'UQE_language_stat_s'
routers/init.go:78:initDBEngine() [I] Backing off for 3 seconds

mysql  Ver 15.1 Distrib 10.4.13-MariaDB, for Linux (x86_64) using readline 5.1


Fix a typo causing a TypeError when attempting to call pdfHistory_clearHistoryState (issue 6121)

Fixes #6121.
Note: This "regressed" in PR #5823.

Since the patch is trivial, and given that it fixes a recent regression, I'm going to merge it with r=me.


Fix release pipeline

The release pipeline tries to make a git push with the ChangeLog after the tag is pushed; however, it should be the other way around as branch protection means that we can't have a bot push directly to the main branch. (We don't want to get rid of branch protection because of SOC2.)

Fixed by https://github.com/sourcegraph/lsif-typescript/pull/80


Recommend WSL2 for Windows users

This is now very common and we should suggest it before other debugging/perf adjustments.

@wycats @MelSumner can you confirm if this is generally correct?


[OTHER] suggestions on what to do with the home page

What would you like to share?
When you first land on the website, it looks like this with no content on the right side until a generator is clicked, I feel something should be there. What do you think

Additional information
No response

It's great having you contribute to this project by creating an issue Make sure you are assigned to this before you work on it and you read the Contributing.md file, Thank you! Welcome to the community :nerd_face:

I think you can give a brief description of the tool by making reference to the sidebar. example "All in one tool for Developers, Generate Gradient Border, Background and Animation with OneClick. Navigate the sidebar for all the tools" 🤦♂ my suggestion.

Make sure to use bold text like the above


unsupported value: +Inf" error not handled gracefully [backport to 1.8]

Backport https://github.com/influxdata/influxdb/issues/20249 to the 1.8 branch from master-1.x

Pull request:
https://github.com/influxdata/influxdb/pull/20276