Newline required after opening brace triggered for allowed loop syntax

The WordPress coding standards state:

You are free to use the alternative syntax for control structures (e.g. if/endif, while/endwhile)—especially in your templates where PHP code is embedded within HTML, for instance:

<?php if ( have_posts() ) : ?>

        <?php while ( have_posts() ) : the_post(); ?>
            <article id="post-<?php the_ID() ?>" class="<?php post_class() ?>">

        <?php endwhile; ?>

<?php endif; ?>

The current version of the standard does not allow this though. Newline required after opening brace is thrown for the following code snippets:

<?php while ( have_posts() ) : the_post(); ?>
<?php if ( have_posts() ) : while ( have_posts() ) : the_post(); ?>

Running phpcbf on these two examples will produce the following, respectively:
<?php
	while ( have_posts() ) :
		the_post();
?>

<?php
	if ( have_posts() ) :
		while ( have_posts() ) :
			the_post();
?>

Where you put the <?php delimiter, is unrelated to the use of alternative control structure syntax.
<?php
if ( have_posts() ) :
	?>

		<?php
		while ( have_posts() ) :
			the_post();
			?>
			<article id="post-<?php the_ID() ?>" class="<?php post_class() ?>">

			<?php
		endwhile;
		?>

	<?php
endif;
?>

Would likely pass.

Updated the ticket title (the first title I wrote before diving deeper into the issue to debug)

The reference @jrfnl gave leads to:

When embedding multi-line PHP snippets within a HTML block, the PHP open and close tags must be on a line by themselves.

Though, to be fair, that's a little confusing when it relates to, for instance <?php endwhile; ?>.

Though, to be fair, that's a little confusing when it relates to, for instance <?php endwhile; ?>.

Yeah, they are allowed to both be on the same line, but if only one of them is on the line, then it has to be by itself without other code.
Which is why "multi-line" is the important word there.

But this isn't about the tags, it is about brace style. And the handbook does indeed include this example:
<?php if ( have_posts() ) : ?>

        <?php while ( have_posts() ) : the_post(); ?>
            <article id="post-<?php the_ID() ?>" class="<?php post_class() ?>">

        <?php endwhile; ?>

<?php endif; ?>

https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/#brace-style
The third line (<?php while ( have_posts() ) : the_post(); ?>) puts code on the line after the "brace."
It could be changed to this:
 <?php while ( have_posts() ) : ?>
     <?php the_post(); ?>

And that would also pass.
But I think this pattern is common enough that we might want to consider making a special allowance for it.

Which is why "multi-line" is the important word there.

Actually, it's not about "multi-line", but about "multi-statement". This is not clear enough in the handbook and I think it would be good to clarify this there.
Regarding the brace style example - IMHO it would be better to change that code snippet in the handbook to the below:
<?php
while ( have_posts() ) :
     the_post();
     ?>

But I think this pattern is common enough that we might want to consider making a special allowance for it.

The reason the handbook was adjusted and this sniff was added to the Core ruleset is that without it we get into trouble with fixer conflicts.
As it's been decided to add it, I would very much be in favour of applying it consistently and not having semi-random "exceptions".

I'm in agreement here - just the wording / example in the Handbook needs tweaking to make it clearer.

For some more context, Codex actually displays this loop format as well (acknowledging that parts of the Codex are outdated).
My point was only that this is very common out in the wild, and many learning resources I have seen people use have taught this style. Not against change, but just wanted to raise that this is very common, and may be worth looking at further.

I'm fine with updating the handbook and codex, I just wanted to make sure that we're all on the same page with regard to the fact that this has basically been the de facto standard up to now. Personally, I think that one statement per line is far more readable; it's easy to miss the second statement. So I'm happy to just say this isn't really feasible technically to add an exception for, and move on.

Pinging @pento @ntwb - if you agree with the above, could either of you adjust the handbook accordingly ?

Ping @pento @ntwb :arrow_up:

The Loop is a special thing in WordPress, I think exceptions should be made for The Loop
A rudimentary search here on GitHub for while ( have_posts() ) : the_post(); in PHP files resulted in 68 of the 100 results I looked at (the first 10 pages) to use that snippet on a single line.
Here's ~10 codex pages that reference that same single line snippet
https://codex.wordpress.org/The_Loop
https://codex.wordpress.org/The_Loop_in_Action
https://codex.wordpress.org/Class_Reference/WP_Query
https://codex.wordpress.org/Function_Reference/have_posts
https://codex.wordpress.org/Function_Reference/wp_reset_query
https://codex.wordpress.org/Pagination
https://codex.wordpress.org/Function_Reference/rewind_posts
And not just in English:
https://codex.wordpress.org/fr:La_Boucle
https://codex.wordpress.org/it:Il_Loop
https://codex.wordpress.org/pt-br:O_Loop
https://codex.wordpress.org/zh-cn:循环
It pretty much is a defacto standard IMHO and I would favor an exception being added for these to be honest.

Could it be a warning if the second statement on the same line is the_post();, but an error otherwise?

I disagree about this being specific to loop or needing an exception. In my opinion rule that is specifically about braces formatting is irrelevant to alternative syntax.
Alternative syntax is better suited for being mixed in HTML in some cases, exactly because braces and rigid formatting can get in the way of producing neat meaningful readable template.
I think this rule should just stay away from alternative if syntax altogether, neither the change in current coding standard in regard to it is needed.

I agree with @Rarst here. With HTML templating, you sometimes need to avoid whitespace. While you can get around this sniff by echoing prepared strings, the resulting template is far less readable.

I too agree with @ntwb and @Rarst and believe that an exception should be added for The Loop.


lower julia compat

Let's see if we can support julia >= 1.3

there should be a way to skip the doctests on 1.3.
Don't know why windows is failing though

if skip the doctest is acceptable, maybe just add a version condition for this: https://github.com/chengchingwen/Pickle.jl/blob/983fb8cc8711f22bca89e4d2d5c7ff8ed1663723/test/runtests.jl#L35
Windows and Mac failed because we try to install some python package (basically PyTorch) for testing which seems to always timeout. Should probably separate the testset into a base set that all platform should pass and a python package set that only test on linux.

@CarloLucibello I fix the compat problem on master, you might want to rebase this PR so we can merge other changes and tag a new release


Is this published?

First of all, sorry if I'm missing something obvious. I think this hasn't been published to the vscode marketplace yet, but I just wanted to double check. I can't find it anyway. If it isn't yet, I'm very much looking forward to it!

Not yet! I'm looking at getting this published by the end of the week. It's still in its infancy, but I want to get a few more things in place, some testing as I know there are crashes when you don't have the happy path, and to make the macOS installation at least, super simple.

Ace, thanks. Let me know if there's anything I can do to help.


New styling for Sell Complete sets and Orphaned Order messaging on the Trading Page

Low Priority styling changes for standout and consistency with our other messaging

I only want to update Orphaned orders...we should leave complete sets the way they are....some users will trade in and out of complete sets (shouldnt look like a warning message)....Also complete sets will occur automatically for v2... dont wast dev time on this update....
only want to update orphaned orders

updated title to remove sell complete sets

works -looks gd...closing


Update group records to have schemas in build

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


Next

@maurossi do you think we should just move to aospext to build llvm ?

Hi, I think that both ways are useful

Hello, I've been using this conceptual patch to build mesa with llvm-project with AOSP, i.e. for AOSPLESS != true
llvm_support.txt
I'd like to propose the integration in this Next PR or in a separate PR, I have already tested it


Unrecognized import path "gorgonia.org/vecf64"

What is the issue?
I tried to build the project from source, but running go build . fails with the following errors:
go: downloading gorgonia.org/vecf32 v0.9.0
go: downloading gorgonia.org/vecf64 v0.9.0
../../go/pkg/mod/github.com/pdevine/tensor@v0.0.0-20240510204454-f88f4562727c/internal/execution/generic_arith_vv.go:10:2: unrecognized import path "gorgonia.org/vecf32": reading https://gorgonia.org/vecf32?go-get=1: 436
../../go/pkg/mod/github.com/pdevine/tensor@v0.0.0-20240510204454-f88f4562727c/internal/execution/generic_arith_vv.go:11:2: unrecognized import path "gorgonia.org/vecf64": reading https://gorgonia.org/vecf64?go-get=1: 436

It appears the gorgonia.org domain has expired:

OS
Linux
GPU
AMD
CPU
AMD
Ollama version
0.3.12

Sorry you hit that.  It looks like the domain expired, but they have since renewed it.  You should be able to build from source again now.


mkcloud: add documentation about ha setups and internal variables

This PR supersedes https://github.com/SUSE-Cloud/automation/pull/285

LGTM although I would strongly recommend a further commit which changes the usage to use a <<EOUSAGE heredoc.

I agree that this is the next logical step. Do you prefer this in the same PR?

I don't care, whichever's faster!

Ok, then I will add the commit to this PR, it makes sense :)

@bmwiedemann @aspiers thanks for (another) review

@aspiers i don't see the code you are referring to in the timeline. i guess you have to comment in the Files changed tab.

@MaximilianMeister click on the commit and there you see the code with the comment

@jdsn i know, but i dont like that too much. and when you force push, adams comments are lost forever

@MaximilianMeister No, you can click on the outdated diff and still see the comments there.

@MaximilianMeister I did the force push before @aspiers commented, so nothing is lost here.

@jdsn yes because he did not comment in the commit tab. he commented in the timeline

:+1:

+1

+1 for my side, but makes sense to read the documentation from an external file, instead of embedding it with the code?

@aplanas thats a good idea, and we had that already discussed in https://github.com/SUSE-Cloud/automation/pull/228 which read from docs/mkcloud.md
i guess this will be one of the next steps for documentation enhancement

@jdsn i know, but i dont like that too much. and when you force push, adams comments are lost forever

@MaximilianMeister This is not true.  As @jdsn they are sometimes still viewable via the outdated diffs expansion (even after a force push), but sometimes when those vanish (I haven't checked but I suspect they vanish when no hunks from the old commit remain still present in newer commits), you can still access them from the links in e-mail notifications and they are also retrievable from the API.  This is one of the things about GitHub which makes it worse than Gerrit.  I already blogged about this a year ago, including a link to a test PR showing some of the good and bad aspects of how it works.

@aplanas thats a good idea, and we had that already discussed in #228 which read from docs/mkcloud.md
i guess this will be one of the next steps for documentation enhancement

Maybe although the usage now calls expand_steps to dynamically generate the expanded steps.  We must be careful not to duplicate the definition of expandable steps in more than one place in the code or docs.

you can still access them from the links in e-mail notifications and they are also retrievable from the API.

@aspiers but maybe only as long as the ref logs are kept (30 days by default i think).
nevertheless i would still prefer to have all relevant discussion in one place

@MaximilianMeister @aplanas thats a good idea, and we had that already discussed in #228 which read from docs/mkcloud.md
i guess this will be one of the next steps for documentation enhancement

If our goal is to keep mkcloud as a big beast, then I would agree that it might make sense to have the documentation separately.
But what we currently try to achieve is, to split mklcoud into a set of smaller specialized tools. And these small tools should bring their own documentation with themselves. So the refactoring will also take care, that the documentation gets split off into smaller chunks.

@aspiers but maybe only as long as the ref logs are kept (30 days by default i think).

Maybe, I have not yet seen any evidence either way.

Nevertheless i would still prefer to have all relevant discussion in one place

So would I but as long as we continue to use GitHub for reviews, we have to live with this trade-off.  Gerrit doesn't have these problems but it has many other disadvantages.  Personally I would be willing to try http://gerrithub.io/ but I think others are opposed to it, not least because of the legal hoops involved in introducing yet another external tool.


Add ability to autoload based on an environment

This PR adds the ability to configure the autoload TeX package to autoload an extension when an environment is first used.  This allows amsCd to be autoloaded.

You re right, this would not provide for autoloading based on delimiters.  I'm not sure that is necessary, but I can look into it if you wish.
I understand your philosophy on autoload.  We can discuss this further, if you wish.  There is still time to have it removed before the final 3.0.0 release, if we come to that conclusion.  I'm going to merge this for now, and we can remove the autoload extension later (but before 3.0.0) if that is the decision.

OOPS, forgot to push the changes before merging.  I've added the commit to update-labs by hand.  Sorry about the confusion.


[Bug] Facility deletion modal incorrectly counting number of users assigned

Description
When I go to delete a facility, I get a confirmation modal explaining what will happen with users and patients that only have access to that facility (potentially orphaned users/patients). The modal is providing the wrong value for number of users only added to the facility.
Steps to reproduce
In dev4, org Bray and Morse Trading has 2 facilities and 3 users: 1 user has all facilities access as an admin and 2 are standard users with access to both facilities. When I use the support admin dashboard Manage facility tool to delete one of the facilities, the confirmation modal says "There are 2 users and 0 patients added only to this facility." This is incorrect.

Expected behavior
The modal should provide the value for users only added to a specific facility and that value should reflect the number of users that have access to the facility to be deleted and no other facility.
Additional context
Looks like getUsersInSingleFacility is written to get count of users total in that facility group when the logic is actually a little more complex.
If developing a query for this ticket is too involved/not performant, work with Jayna to come up with copy and we'll just use the existing query to give the value of all users in the facility.

@jayna-SkylightDigital


Move stuff to internal and improve comments

I'm looking over https://pkg.go.dev/github.com/transparency-dev/trillian-tessera and making it clearer to newcomers.
This moves fields and types into internal, which is more refined approach to the file-based solution taken thus far to #280.

@AlCutter PTAL as my new commit spices things up a bit


chore: make js sdk docs a landing page

🚀 Deployed on https://66c8b489bd7394c7d7e20d3a--cozy-fox-0defec.netlify.app


'Emission Factor Per Network Region' API is returning 'No results' ERROR-422

The GET 'Emission Factor Per Network Region' API expects an HTTP request from 'https://api.opennem.org.au/stats/emissionfactor/network/{network_code}'
For which I am passing the {network_code} parameter that I got from the API call from 'https://api.opennem.org.au/networks' and passing the 'interval' query at the end but getting the output as 'No results', "response_status": "ERROR".
Please look into this and kindly let me know if I am missing something.
I am using python & it's libraries for making the API call as follows :

Input

import requests
import json
url = 'https://api.opennem.org.au/stats/emissionfactor/network/NEM?interval=30m'
resp = requests.get(url).json()
print(json.dumps(resp, indent = 2))

Output

{
  "version": "3.11.9",
  "created_at": "2022-11-10T18:17:49",
  "response_status": "ERROR",
  "detail": "No results"
}

This is related to #160
We are changing the way we calculate emission intensities to do it per-interval using our aggregate tables and our own net-flow method. I will hook the API back up to these results

Okay, Thanks.


Add Dockerfile.rhel8

A separate file is required, as the changes necessary for building with
RHEL 8 content are not compatible with RHEL 7.

Thank you for this PR.  However, this repository is no longer being actively used for OpenShift as of 4.4+  It merged with https://github.com/openshift/cluster-node-tuning-operator as of the OpenShift 4.4 branch.  It is kept here only to provide fixes for 4.3- branches.


Event title tooltip should stringify

It would appear that in case where we want to stylize (bold, italic, etc) some parts of an event title, it shows up properly on the page but the tooltip contains [object Object] as values.
A solution would be to use the jsx-to-string library to stringify the value or better yet add a tooltipAccessor method.

On a similar note, how would you feel about removing the string literal here
https://github.com/intljusticemission/react-big-calendar/blob/aecb5da3f0e2915f06b9062d71bc5aa844e518a5/src/DayColumn.js#L172
We actually don't want a tooltip (don't have good use-case for it). But this code makes it impossible to remove and ends up with : null instead

Any plan to fix this?
Thanks


Text of cellState VS the date, is different?

Version Number:8.0.4
Why is the text of cellState different from the date?
//print message----
CellState(isSelected: false,
text: "8",
dateBelongsTo: JTAppleCalendar.DateOwner.thisMonth,
date: 2022-08-7 16:00:00 +0000,
day: JTAppleCalendar.DaysOfWeek.sunday,
row: (Function), column: (Function), dateSection: (Function), selectedPosition: (Function), cell: (Function),
selectionType: nil)
the text is 8 and it's correct, but the date is 2022-08-7, was there something i ignored?

The text is correct. Thats good.
Now for the date. I guess you printed it on console to get 2022-08-7 ?
If this is what you did, then may get correct/incorrect result. This is the nature of dates in swift for any app.
Why?
Because the print command has its own date formatting under the hood. So if you live in a time zone in the west near Apple's headquarters, you get a different result than printing a date if you live in the east half of the world (different timezone).
So whats the best way to actually print a date? Use a NSDateFormatter with the correct timezone settings, because you may/may not get correct results if you just print a raw date to console.
This is explained extensively here -> https://github.com/patchthecode/JTAppleCalendar/issues/252


find and findAll helpers, two types of queries

Follow up to alternative proposed in #15
find(selector: string): null | HTMLElement and findAll(selector: string): NodeList which work using document.querySelector and document.querySelectorAll

@rwjblue @cibernox I added the findWithAssert helper method. It seems good to use that for the helpers, click, fillIn etc.; since it will raise and error that the element to take action on was not found.

LGTM.
@rwjblue is there any downside on having many modules and reexport them?
My only suggestion is that if the public API of the addon doesn't intend to let people do import fillIn from 'ember-native-dom-helpers/test-support/fill-in', we should put those modules in a /-private folder. If on the contrary we want to allow them, this structure is fine.
But I find named exports from a single file more ergonomic for this usage.

@cibernox the upside to many modules is more explicit dependencies for each module, and maintainability. Also since we have a build the modules are simple referenced by their AMD name, each import test the same return value as the last import. So currently there is no added bloat from many modules vs one helpers file. And when ES2015 modules are supported everywhere my assumption is that this will still be a good thing.
Instead of putting files in a -private folder I added @private to the doc blocks for functions that should remain private. I was curious about making focus public but can't think of a good reason at this time. But if we find that developers import and use focus perhaps we should consider that.

According to the Grand Module Unification private modules must be inside a /-private folder, but I don't care that much as long as the import { a,b,c } from 'test-support/helpers' is the only publicly documented.

But I find named exports from a single file more ergonomic for this usage.

confirm

as long as the import { a,b,c } from 'test-support/helpers' is the only publicly documented

agreed


Update Post “found-flying-termites-on-the-gold-coast”

Automatically generated by Netlify CMS

👷 Deploy Preview for chic-shortbread-66a66b processing.

Name
Link

🔨 Latest commit
b5ad6e87c4d4173fa64814f950973542884d1407

🔍 Latest deploy log
https://app.netlify.com/sites/chic-shortbread-66a66b/deploys/652df1d4986b2a0008b9957c


STORM-1733 (0.10.x) Flush stdout and stderr before calling "os.execvp" to prevent log loss

Related to #1360

+1
@ptgoetz since you are cutting the 0.10.1 RC, should this wait to merge to 0.10.x branch?

+1


Update Qt and librdkafka versions

Update librdkafka to version 0.9.5 and builds via cmake
Update Qt to version 5.8 and include building QtWeb modules (WebEngine, WebSockets, etc.)
Use newer version of externpro (17.03.1)

@incessantier @brobeson @swflb This updates a couple versions, also adds building of the Qt Web modules and some other cleanup.

#approved

Also had verbal approval from @swflb, merging.


[discussion] How to control for unusual situations

Node from #331
Instance creation will create costs. If the problem is a configuration issue or other problem, the instance has been created for a while, but Infrakit will endlessly reproduce it because of flavor.Health decides the instance is "Unhealthy". It is a useless cost. Is there any way to prevent this? In AWS, Instance cost is charged per 1 hour. (Partial hours are billed as full hours.) (e.g. max-retry-num? Using circuit breaker?)

@anarcher  Does this happen during creating new instances or only happens when performing a rolling update?


Crashloopbackoff while deploying nifi-with-ldap-authentication-with-toolkit

I am having issues deploying "deploy-secured-nifi-with-ldap-authentication-with-toolkit" on my k8s cluster and hoping you can help me identify what the problem is.
After deploying I have 3/4 nifi-0 pod ready and status is crashloopbackoff screenshot attached.
My K8s setup is on GCP with the below resources
Cluster size -4 Total cores -8 Total memory -32.00 GB
Changes I made to value.yml file are:
replica count =1
persistence:
storageClass: standard
accessModes:  [ReadWriteOnce]
configPartitionSize: 5Mi
dataPartition1Size: 10Gi
dataPartition2Size: 10Gi
dataPartition3Size: 10Gi
logPartitionSize: 5Gi
Configure resource requests for nifi pods
resources:
requests:
memory: "4Gi"
cpu: "0.5"
I also added my ldap url and credentials to ldap-value.yml file
Please let me know what other info or details you might require. I had attached "kubectl describe po nifi-0",  nifi-0 server logs
and app-logs.

server-log.txt
app-log.txt
describe.txt

Thank you @Smeks1 for trying the chart.
I found the following error message in the app-log.txt
Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: ldaps.bwt.ee:636; nested exception is javax.naming.CommunicationException: ldaps.bwt.ee:636 [Root exception is java.net.SocketTimeoutException: connect timed out]
It looks like it is not able to reach the ldap server at ldaps.bwt.ee:636

@sushilkm Hi,
Yes you are correct, the ldap server is not reachable. I'll need to whitelist the nodes IP but could this be the reason for crashloopbackoff? I wasn't expecting this to be the reason.

For now, I can only see that as the error message in the logs provided.

Okay, I’ll let you know the outcome once I have the IP whitelisted.

Hello,
I whitelisted my nodes ip but this didn't resolve the issue. I was still getting the above error. I deployed another container from my cluster just for the purpose of troubleshooting and from that container, I was able to telnet to the LDAP server. I have double checked my credentials (managerdn, managerpassword and url) and all seem correct. Do you have any other troubleshooting suggestions for me?

will it be ok, if I asked you what is the ldap url you are using.

Can I somehow share it with you privately? email/skype/whatsapp? my email address is<EMAIL_ADDRESS>whatsapp: +37253529124 or any other means best preferred by you

sure you can send me emails at<EMAIL_ADDRESS>

as discussed on email, it is working now. closing the issue.
You can reopen if you still have any problems or questions.
Thank you for trying the chart.


[iac.cls]add Abstract title and adjust spacing

add abstract title

Thanks! I'll review and merge asap


[TAB-8127] Can't pass the license system property to the start script

Wrong target branch?

Created PR incorrectly


termsnap: 0.3.0 -> 0.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tomcur/termsnap/releases.
meta.description for termsnap is: Create SVGs from terminal output
meta.homepage for termsnap is: https://github.com/tomcur/termsnap
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.0 with grep in /nix/store/zqm5kizrwi9lqzs2ip9qsv87n4bs9wjh-termsnap-0.4.0
found 0.4.0 in filename of file in /nix/store/zqm5kizrwi9lqzs2ip9qsv87n4bs9wjh-termsnap-0.4.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

termsnap

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/10855fbd29d00682867ccc9d091e44087c364f0e#termsnap

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

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

1 package built:

termsnap

Maintainer pings
cc @yash-garg for testing.


Multi-Auth + Socialite login not working

I'm trying to log in with Google.
I am saving user data in the database, but I can not log in.
Auth::login($authCustomer, true); // not working
my guard name: customer

I solved the problem: D
Auth::guard('customer')->login($authCustomer, true); :D :D


Fix failing CreateCoinBase and CreateNewBlock test cases

This PR fixes the following error:
Message: System.ArgumentOutOfRangeException : The UTC time represented when the offset is applied must be between year 0 and 10,000. Parameter name: offset
The error occurs in the following test cases:

CreateCoinbase_CreatesCoinbaseTemplateTransaction_AddsToBlockTemplate
CreateNewBlock_WithScript_DoesNotValidateTemplateUsingRuleContext
CreateNewBlock_WithScript_ReturnsBlockTemplate
CreateNewBlock_WithScript_ValidatesTemplateUsingRuleContext

With the latest master, all the mentioned tests pass for me. Under which conditions are those tests supposed to fail?

@quantumagi I agree that using the one method instead of 2 is better, I just do not see why it fails or when it fails, because for me those tests simply pass. So I'm just interested to understand the problem, but I have no problem with this change in code.

I've done a cross-check by reverting the changes against the latest code from master. It still fails with the two calls. Unfortunately I can't step into those methods for some reason.

@Aprogiena will approve this one when the PR is done then? Cheers 👍

I think we can handle this as a simple refactor as the remaining issue seems to be at my end.

I'm not running tests, so I now just comment on issues and pull request, so I cannot really approve, but it looks fine to me

@Aprogiena 👍
@quantumagi sorry I misunderstand, will now recreate the PR? I see Travis is still failing.

@fassadlr, those are unrelated errors which will be fixed by https://github.com/stratisproject/StratisBitcoinFullNode/pull/1332.


how to make binary fittable with alpine distribution?

how to build binary  from source code, fittable with alpine distribution?

Someone has to patch it to work with musl.

now i have switched to glibc without attempt to patch it


Delete this repo?

I don't think this is being used anywhere. My recollection is it was prototype which never went anywhere. Delete it for the sake of minimizing our public-facing code footprint?
@calebwaldorf

@srerickson Sure. Have cloned in the event it is needed in the future.


Problems with encoding special characters in the table

When converting url I get problems with the converted JSON. I download a Spanish page with accents. The text will show letters with question marks instead of the correct letter.
An example is the next url which is utf8 encoded:
http://competiciones.feb.es/estadisticas/Resultados.aspx?g=1&t=2018
Franz Jimeno

Just solved the problem. Had to add {request: {encoding:'binary'}} as an argument in convertUrl.

Thanks for the response Franz.

My solution with request-promise package:
const result = await request({ uri: url, encoding: 'latin1' })
const converted = tabletojson.convert(result)


Virtual machines should start on host restart

When the host system restarts, the virtual machines created with base-infra-bootstrap do no automatically start back up. We should make that an option, and default to yes (start on boot).

PR via https://github.com/redhat-nfvpe/ansible-role-vm-spinup/pull/28


Add builder method that uses DefaultAzureCredential

Addresses https://github.com/Azure/azure-sdk-for-net/issues/31622

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Messaging.EventGrid


[Website] enhance before and after screenshot

Current Behavior
On the homepage, there is a before and after section. The after screenshot is not the best.

Desired Behavior
Replace the after screenshot with a more intriguing version, like this one:

Crop the image as needed.

Contributor Guides and Resources

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🖥 Contributing to Meshery Website
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@leecalcote Can you assign this issue to me? Also should I use the image that is provided by you?

@leecalcote Can you please assign this issue to me ?, it would mean a lot thanks.


toggleSeries not working on Pie Chart

Codepen
https://codepen.io/Micene09/pen/REJBWW
Explanation
Labels and serie names are correctly defined but, toggleSeries is not working and the serie selected in the example provided never disappear.
Looking at the debugger, seems that there is something wrong about a data:realIndex attribute...

I agree this would be nice and good looking.
Can anyone perhaps give me a working example of how to use the updateSeries in React?
When I try to simply setState, I get an error in console, although the series and the graph is updated correctly.
can't access property "getAttribute", t.parentNode is null

any update on this feature

Hope that this will become an option

Any update on this feature?


Kustomize refactor

@palladius these are the changes that I propose.
For a changelist please see commits and shared doc.


有没有类似于 angular的route的resolve的功能呢？

What problem does this feature solve?
有没有类似于 angular的route的resolve的功能呢？
What does the proposed API look like?
有没有类似于 angular的route的resolve的功能呢？

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.


Cannot fetch prop value on shallow render

https://github.com/airbnb/enzyme/blob/master/docs/api/ShallowWrapper/prop.md contains the following example:
const wrapper = shallow(<MyComponent foo={10} />);
expect(wrapper.prop('foo')).to.equal(10);

When running it though, it does not work.
Full example used
import React from "react";

class MyComponent extends React.Component {
    render() {
        return (

                {this.props.foo}

        );
    }
}

MyComponent.propTypes = {
    foo: React.PropTypes.number
};

import {mount, shallow} from 'enzyme';
import {expect} from 'chai';

describe.only('enzyme test', () => {
    let wrapper;

    context('mount', () => {
        beforeEach(() => {
            wrapper = mount(<MyComponent foo={10} />);
        });

        it('debug works fine', () => { // this works
            expect(wrapper.debug()).to.contain('10');
        });

        it('prop works fine', () => { // this works
            expect(wrapper.prop('foo')).to.equal(10);
        });
    });

    context('shallow', () => {
        beforeEach(() => {
            wrapper = shallow(<MyComponent foo={10} />);
        });

        it('debug works fine', () => { // this works
            expect(wrapper.debug()).to.contain('10');
        });

        it('prop works fine', () => { // this does not work
            expect(wrapper.prop('foo')).to.equal(10);
        });
    });
});

(Potentially relevant discussion: https://github.com/airbnb/enzyme/issues/331)

The wrapper represents what MyComponent renders, not MyComponent itself. The div it renders doesn't have any props.
There's no value anyway in rendering something with a prop, and then immediately testing that it has that prop - you aren't validating anything except the immediately preceding line of code in your test.

Yeah this is expected behavior, see https://github.com/airbnb/enzyme/issues/331#issuecomment-230578503. We should update that example though since it's incorrect. @vrinek want to open a PR with a better example?

@ljharb the fact that shallow & mount behave differently is alarming to me. I would expect them to represent something on the same level. Instead it seems like one represents the actual MyComponent and the other what's inside MyComponent. For reference, my understanding on the distinction of shallow vs mount is that mount will render every child component while shallow will not.
@Aweary Yes, the documentation is indeed incorrect and that was the source of my confusion. I'll try to find the time to open a PR on it.
Updated example I have in mind...
wrapper = shallow(
<MyComponent foo={10} />
);
expect(wrapper.find('MyComponent').prop('foo')).to.equal(10);

...along with an explanation on why the more intuitive shallow(<MyComponent foo={10} />) does not provide the expected results.

Seems to be fixed by https://github.com/airbnb/enzyme/pull/580. Closing...


[Bug]: Status 500 Uniquify people

Steps to reproduce the bug
1.Search "Orrell" in Uniquify People task, returned 4 hits
2.Selected person to keep and checked boxes for the other 3 be merged
3.Clicked merge
4.Seems to have worked but also saw the Status 500 error msg box
...

Screenshot

Expected behavior
No response
Additional Screenshots
No response
Environment

[ ] Development (native)
[ ] Development (docker)
[X] Sandbox
[ ] Production

Sandbox Used
sandbox
Version
SANDBOX - build 89f7b1cb8 on 2021-12-01T14:08:52Z
Browser Used
firefox

Re-testing. I no longer get the Status 500 message. So I think we can close this ticket.
NOTE: I'm not sure I'm getting the expected objects count after merge. (Will need to test further).
See logs (I merged several instances of Dmitry Dmitriev). I think this would be a new ticket, yes? @mjy @jlpereira

Yes, new ticket.  Remember that new names can (and do) come in at any time, requiring merges.


Envoy: improve logging format configuration

Before/After JSON:
{"level":"debug","time":"2024-03-04T12:11:46.931655Z","scope":"envoy connection","msg":"[Tags: \"ConnectionId\":\"2\"] closing socket: 1","caller":"external/envoy/source/common/network/connection_impl.cc:281","thread":947194}
{"time":"2024-03-04T12:15:57.204132Z","level":"debug","scope":"envoy connection","msg":"closing socket: 0","caller":"connection_impl.cc:281 closeSocket","thread":"956652","ConnectionId":"2"}

Before/After plain:
2024-03-04T12:21:24.654824Z     debug   envoy connection external/envoy/source/common/network/connection_impl.cc:281    [Tags: "ConnectionId":"2"] closing socket: 0    thread=963777
2024-03-04T12:21:00.256847Z     debug   envoy connection connection_impl.cc:281 closeSocket     [Tags: "ConnectionId":"2"] closing socket: 0    thread=962566

Primary benefit is to put envoys structured logs ([Tags: "ConnectionId":"2"]) into proper top level json keys. We also improve the source file format

I disagree that the file name change is an improvement. Please don't force foreign logging templates, it doesn't help debugging.

What is a 'foreign logging template'?

Using just file names is a glog pattern. I don't think it's a good one.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
92fdf99284488d1716ff9c6b5bfc49d440f6d05d
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

i recall there's performance issue withjson?

i recall there's performance issue withjson?

Any more info on this? We already have a 'json' format, its just partially broken

Using just file names is a glog pattern. I don't think it's a good one.

Reverted

i recall there's performance issue withjson?

This is only for debug logs, mostly, so I don't think performance is important here (there are some warn/error logs in envoy, but its extremely small volume). This is not impacting access logs

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
163fbf6a468836430907bfed2303557e6e224ad6
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
a09c26029bf45a71225ac9b86c63670984006e7a
link
true
/test integ-telemetry-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
a09c26029bf45a71225ac9b86c63670984006e7a
link
true
/test integ-telemetry-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-mc


Some Float value call method to_s get invalid format

I try code.
99999.9999999999417923390865325927734375.to_s
Get string
099999.999999999
Please, Help.

I get "100000". Could you tell me your config?
try mruby-config --cflags.

Thank you for fast response, Matz.
Sorry I'm late.
I run mruby-config --cflags
And I get
-g -std=gnu99 -O3 -Wall -Werror-implicit-function-declaration -Wdeclaration-after-statement -DDISABLE_GEMS -DMRB_DEBUG -DDISABLE_GEMS -I/.../mruby-iOS/mruby/include

Please tell us your platform and OS information as well.

I use mruby 1.1.0 and compile on OS X El Capitan with xCode 7.3.1 (gcc 4.8)

This issue was fixed by https://github.com/mruby/mruby/commit/6f893b5183450384e89b3d8f03f9ef32a7522624.
Please use newer version.

Thank you, syohex. I will try.


Query deviceManagement/managedDevices fail if filter

Describe the bug
Query deviceManagement/managedDevices fail if filter
To Reproduce
Steps to reproduce the behavior:

Go to 'graph-explorer'
Run query: https://graph.microsoft.com/v1.0/deviceManagement/managedDevices?$filter=deviceName eq 'XXXXXX'
See error

{
"error": {
"code": "InternalServerError",
"message": "{  "_version": 3,  "Message": "An internal server error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: 3e43f1c7-dece-dc29-0770-9d1ceae7e86e - Url: https://fef.msub01.manage.microsoft.com/DeviceFE/StatelessDeviceFEService/deviceManagement/managedDevices?api-version=2023-10-19&$filter=deviceName+eq+'COLAS17328'",  "CustomApiErrorPhrase": "",  "RetryAfter": null,  "ErrorSourceService": "",  "HttpHeaders": "{}"}",
"innerError": {
"date": "2024-05-22T09:41:40",
"request-id": "e0632382-b271-43e0-97fc-475ae068ed6f",
"client-request-id": "3e43f1c7-dece-dc29-0770-9d1ceae7e86e"
}
}
}

@clesieug I cannot reproduce this on my end, the provided query example works as expected:

Could you retry or run it with a different tenant?

Hello Musale
Thank you for your test.
The problem solved itself at the end of the day.
I'm waiting for microsoft to get back to me.
Certainly a problem on one of their endpoint.
Thank you

@clesieug glad to be of help. Open a new issue with the details if it re-occurs. Closing this one.


embassy-lora GenericSx126xInterfaceVariant equivalent for Sx127x Boards

I'm trying to understand if the GenericSx126xInterfaceVariant in order to put to work for the Sx127x LoRa boards with a rp-pico, so far no luck. I'm pretty sure that the lora-phy has the struct  SX1276_7_8_9 implementation. Being  said that, I can't see a way to couple it with the embassy-lora interface.
Is this caused by embassy-lora  missing a declaration of a similar GenericSx127xInterfaceVariant or just is my lack of understanding on how to properly use the existing trait with the available implementations over lora-phy ?

So far the Stm32l0InterfaceVariant is the only example of an InterfaceVariant involving an Sx127x.  It is used for an stm32l0 board with an embedded sx1276.  You can model your InterfaceVariant implementation off that.  If it seems like the new InterfaceVariant may be useful across MCU/sx127x board combos, go ahead and name it GenericSx127xInterfaceVariant.  Otherwise, give it a name that allows future users to identify the MCU/sx127x board combo your InterfaceVariant represents.
If it turns out that the Stm32l0InterfaceVariant meets your needs, please still create a GenericSx127xInterfaceVariant version.  I currently want to keep the STM InterfaceVariants separate.
Examples of usage of the Stm32l0InterfaceVariant with an sx1276 board are located in the stm32l0 Embassy examples with names starting with "lora".

I'll give it try to use Stm32l0InterfaceVariant.  In case it works I ĺl try to follow your advice on isolating the implementation with the combo. If in the application seems useful to the public the I'll try to do a pull request.
Thanks for the advice.


Build gradle error when run any androidTest

Summary:
when i run any test in androidTest it throw build an error
Steps to reproduce:
Open androidTest file
run any androidTest file
System logs:
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:checkProdDebugAndroidTestDuplicateClasses'.
> 1 exception was raised by workers:
  java.lang.RuntimeException: java.lang.RuntimeException: Duplicate class org.hamcrest.BaseDescription found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.BaseMatcher found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.CoreMatchers found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.Description found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.Factory found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.Matcher found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.SelfDescribing found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.StringDescription found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.core.AllOf found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.core.AnyOf found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.core.DescribedAs found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.core.Is found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.core.IsAnything found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.core.IsEqual found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.core.IsInstanceOf found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.core.IsNot found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.core.IsNull found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.core.IsSame found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.internal.ArrayIterator found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.internal.SelfDescribingValue found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)
  Duplicate class org.hamcrest.internal.SelfDescribingValueIterator found in modules jetified-hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3) and jetified-mockito-all-1.10.8.jar (org.mockito:mockito-all:1.10.8)

  Go to the documentation to learn how to Fix dependency resolution errors.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Device and Android version:
Android Device :Redmi y3(API :29)
Commons app version:
latest master

Which test did you try to run and also share the configuration file!

@madhurgupta10 i run almost every test in androidTest all the test thrown build gradle error

How exactly are you running a test, is it a Unit Test or Instumentation Test?

@madhurgupta10 i simply run these test   and found build gradle error

@Prince-kushwaha  thanks for reporting. This issue seems to be only with Instrumentation tests, I have created a PR that should resolve this issue!


CLI: add UserDB password reset

Description
Add a command that allows resetting passwords.
Outcomes

[ ] Password reset available

There is already an update function...


multiple Pictures from a single PictureRecorder

Use case
I would like to reuse a PictureRecorder in multiple frames, i.e.:
final recorder = PictureRecorder();
final canvas = Canvas(recorder);

canvas.drawRect(..);
final pic1 = recorder.endRecording();
canvas.drawRect(..);
final pic2 = recorder.endRecording();

In this example, pic1 would have one rect drawn and pic2 would have two rects drawn, i.e. keeping canvas operations.
Proposal
This is currently not possible as "both the picture recorder and the canvas objects are invalid and cannot be used further." (from the docs).
This line does it on the Dart side.
https://github.com/flutter/engine/blob/ff1003a387132076afd3bacd1385ac491a1690dd/lib/ui/painting.dart#L4977
I am wondering: if we simply add a flag to not call these lines on the Dart side, would we be fine or is there some limitation enforcing this? It would be extremely useful to be able to compound canvas operations on a recorder.

We don't think we should support this as it would make supporting picture lifecycle in the engine harder. You could just call endRecording once to get the picture and cache that instead. In subsequent frames, create a new picture recorder and call drawPicture. Needing the cache the picture recorder itself is not necessary.

@chinmaygarde I tried what you suggested, but for some reason it crashes Flutter (stack overflow on web iirc) once I do that like 100-200 times, so it does not work. Should I open an issue about that?

(so canvas.drawPicture(recorder.endRecording()) and adding to that canvas and then recording that picture and painting it and adding to it recursively does not work more than a few times)

Not sure how how what I suggested could cause stack growth. My suggestion was to store the last frames picture in an ivar. In the new frame, create a new picture recorder with one draw containing the last picture and the new rect. If you can paste a snippet of your code, that would be helpful.

@chinmaygarde Exactly! I actually did this before you proposed it. On macOS, it crashes Flutter without any exception, but on web I got a stack overflow.
So I did think this far, but it just did not work, hence, I created the issue :)

@chinmaygarde this is my code from last week (glad I still had the draft):
  Picture? _p;
  Offset? _o;

  @override
  void u(double t) {
    final r = PictureRecorder(), pc = Canvas(r);
    if (_p != null) pc.drawPicture(_p!);

    _o = (_o ??= Offset(x.width / 2, x.height / 2)) +
        Offset.fromDirection(pi * Random().nextInt(4) / 2);
    pc.drawCircle(_o!, 4, Paint());

    c.drawColor(const Color(0xffffffff), BlendMode.srcOver);
    c.drawPicture(_p = r.endRecording());
  }

If you use this with my package funvas, you can get u to be called every frame. As I said, this crashed on macOS and on web after 1 or 2 seconds of running (assuming 100+ calls). Maybe something has changed since 7 days ago, but I doubt it ;)

@chinmaygarde How should we procede? The solution you proposed to close the issue does not work, so should we open a new issue or reopen this one?


implements passthrough to allow filtering and progress implementation

Introduces an anonymous function attribute Passthrough in opts param that allows manipulation and filtering objects, which can represent either send or receive jobs.
This could close issue #3

Thank you for the contribution!
I think this is a reasonable enhancement in making copying jobs more observable, but there are several things need to be discussed.
As I have mentioned in issue #3, I think a virtual filesystem like fs.FS which implements file type/extension filtering by its own, is a better choice to achieve such purpose. We can simply accept fs.FS as input, calling fs.WalkDir(fs, ".", WalkDirFunc)and processing those directories/files when WalkDirFunc returns nil error.
It help us keep simple and focus on copying works. Separate various filtering/selecting tasks into different WalkDirFunc implementations provided by users.
I believe thatscp itself should be easy to use and understand.
Thus, introducing a "interceptor" mechanism which is able to manipulate vital file properties like name/path etc, is consider to be not acceptable.
Here is my opinion of filtering. I think a dropin replace for traverse func  with fs.WalkDir is enough for that.
I don't have much idea on progress reporting right now, but I concern it might be too "heavy" for using io.MultiWrite on it.
CopyDirFsToRemote(localFS fs.FS, remoteTarget string, *DirTransferOption) error

var (
    SkipAll = fs.SkipAll
    SkipDir = fs.SkipDir
    // this is added for skipping files
    SkipFile = errors.New("skip this file")
)

type DirTransferOption struct {
    ...

    // WalkDirFunc is called on visiting each file or directory.
    // Compared to fs.WalkDirFunc, It adds additional capability to
    // skip certain files when SkipFile error is returned.
    WalkDirFunc fs.WalkDirFunc
}

// here is the WalkDirFunc signature for reference
//
// WalkDirFunc is the type of the function called by [WalkDir] to visit
// each file or directory.
//
// The path argument contains the argument to [WalkDir] as a prefix.
// That is, if WalkDir is called with root argument "dir" and finds a file
// named "a" in that directory, the walk function will be called with
// argument "dir/a".
//
// The d argument is the [DirEntry] for the named path.
//
// The error result returned by the function controls how [WalkDir]
// continues. If the function returns the special value [SkipDir], WalkDir
// skips the current directory (path if d.IsDir() is true, otherwise
// path's parent directory). If the function returns the special value
// [SkipAll], WalkDir skips all remaining files and directories. Otherwise,
// if the function returns a non-nil error, WalkDir stops entirely and
// returns that error.
//
// The err argument reports an error related to path, signaling that
// [WalkDir] will not walk into that directory. The function can decide how
// to handle that error; as described earlier, returning the error will
// cause WalkDir to stop walking the entire tree.
//
// [WalkDir] calls the function with a non-nil err argument in two cases.
//
// First, if the initial [Stat] on the root directory fails, WalkDir
// calls the function with path set to root, d set to nil, and err set to
// the error from [fs.Stat].
//
// Second, if a directory's ReadDir method (see [ReadDirFile]) fails, WalkDir calls the
// function with path set to the directory's path, d set to an
// [DirEntry] describing the directory, and err set to the error from
// ReadDir. In this second case, the function is called twice with the
// path of the directory: the first call is before the directory read is
// attempted and has err set to nil, giving the function a chance to
// return [SkipDir] or [SkipAll] and avoid the ReadDir entirely. The second call
// is after a failed ReadDir and reports the error from ReadDir.
// (If ReadDir succeeds, there is no second call.)
//
// The differences between WalkDirFunc compared to [path/filepath.WalkFunc] are:
//
//   - The second argument has type [DirEntry] instead of [FileInfo].
//   - The function is called before reading a directory, to allow [SkipDir]
//     or [SkipAll] to bypass the directory read entirely or skip all remaining
//     files and directories respectively.
//   - If a directory read fails, the function is called a second time
//     for that directory to report the error.
type WalkDirFunc func(path string, d DirEntry, err error) error

¡Por supuesto! Aquí tienes una respuesta ampliada que incluye tu sugerencia:

Thank you for your feedback and for considering my contribution!
I appreciate your suggestion regarding the use of a virtual filesystem like fs.FS for file type/extension filtering and agree that it can simplify the process by focusing on the copying tasks. However, I would like to point out that the proposed solution seems to primarily address file uploads. It doesn't appear to cover file downloads, which is an essential part of many SCP operations.
Additionally, regarding progress reporting, while I understand your concern about the potential overhead of using io.MultiWrite, it's a commonly used approach for implementing progress bars in various applications. It allows us to track progress efficiently without significantly impacting performance. I believe incorporating io.MultiWrite could provide a more user-friendly experience by giving real-time feedback during file transfers, which many users find valuable.
As a potential solution, I suggest we handle this pull request by focusing on the implementation of the progress bar. Specifically, we could add an io.Writer attribute to the configuration object and use it in conjunction with io.MultiWrite if it has been set. This way, we can provide progress reporting functionality without complicating the current structure too much.
For the file filtering and selection enhancements, we could consider addressing them in a separate pull request. This would allow us to thoroughly discuss and implement the best approach for those features without conflating them with the progress reporting changes.
Once again, thank you for your guidance. I look forward to your thoughts on these considerations and how we can proceed.

However, I would like to point out that the proposed solution seems to primarily address file uploads. It doesn't appear to cover file downloads, which is an essential part of many SCP operations.

You are absolutely right on that, for API & experience consistency, filtering should be able to apply on both upload & download.
Thank you for reminding me about that. The idea just came out of my mind, now proved to be impractical.

For the file filtering and selection enhancements, we could consider addressing them in a separate pull request. This would allow us to thoroughly discuss and implement the best approach for those features without conflating them with the progress reporting changes.

I agree, filtering design needs more discussion and consideration.
Solving the progress reporting issue is more practical.
I dig a littler deeper into io.MultiWriter, finding out that it just run a loop to write all io.Writer inside, one after another.
Apparently, the writer given in option, hoping to monitor progress, does not actually represent "bytes written to/received from wire".
I suggest using the return n of io.Writer/Reader for progress reporting, this may require some wrapping to stream.In/Out.
The anonymous function specified in option will be called on each Write/Read returns, with file metadata and tranferred bytes+total bytes.
For example:
// should be readonly and monitoring purpose only ?
type TransferMetaReadOnly struct {
  IsDir bool
  Name string // file or directory name
  Path string // directory path without name, could be absolutely or relatively, depending on condition
  TotalSize int64 // bytes
  TransferredSize int64 // bytes
  Perm os.FileMode // is this necessary ?
}

Additionally, a single write/read should be enough for transferring tiny file, but this might not be enough for progress reporting, An extra call to the anonymous function with proper metadata should be executed before write/read, in order to have the "start" and "end" event properly generated.

Regarding the use of io.MultiWriter, the bytes written in the io.Copy(multiwriter, stream) call are indeed the exact bytes of the file being transferred. The io.Writer designated for progress reporting within MultiWriter is still a call to the .Write() function with each chunk intended to be written.
The approach of wrapping stream.In/Out is certainly viable. However, since we are using io.Copy(), wrapping stream.In would mean wrapping the Write() method. For example:
func (w *Wrap) Write(p []byte) (n int, err error) {
  w.callbackfunc(somestuff) // some stuff to communicate progress
  return w.originalStreamIn.Write(p)
}

This means that for each chunk written (since io.Copy copies in small chunks), there would be a call to Wrap.Write(), and thus a call to w.callbackfunc.
If we were to wrap Read(), we would need to wrap sendJob.Reader for uploads and stream.Out for downloads. While this is feasible, it does introduce a certain complexity and might be considered an unusual approach.
I am eager to understand how you envision the solution in more detail. If you could provide further clarification or examples of how you would like the progress reporting to be implemented, I would be more than willing to adapt and implement it accordingly.

I am really busy on work today. Sorry for the delayed response.
No problem, let's go through your design and explain my concern, one by one.

The io.Writer designated for progress reporting within MultiWriter is still a call to the .Write() function with each chunk intended to be written.

(Feel free to correct me if I didn't get your point)
I think, you are going to replace the Writer with a MultiWriter [original, monitoring], because the added monitoring Writer will be called on each chunk written to original Writer.
By adding up written chunks' length,  the progress of file during sending/receiving could be calculated.
This make sense for the most of time. But, as I have mentioned in previous post: looking a little deeper into implementation of MultiWriter, you will find that those writers inside MultiWriter are actually called one by one: If one fails to write out the data, MultiWriter exits immediately, reports error to its caller, and all the subsequent Writers are discarded.
Assuming the first chunk is 4MiB, and the file total size is 16MiB. An error occurs at 2MiB written to original Writer, according to the implementation described above, the monitoring Writer won't be called and the error will be immediately reported. Apparently, the real progress for transferring should be  2/16*100%=12.5%, but you actually get 0% with an IO error.
Here are some definition issue/corner cases need to be discussed.

How do we define "progress" of a file transfer ?
I prefer using the bytes written to wire, divided by total size of current file, as the definition of progress.
Instead of “mirroring write" which might not be accurate when error occurs, statistics collected by wrapping Write function is more precise and perfectly satisfis the definition of "bytes written to wire"

How do we calculate the progress of a partial transmitted chunk on error ?
According to the "progress definition" above, I think we'd better include those bytes successfully transmitted of the chunk while calculating, not silently discard the partial failed chunk.

How do we define the observation approach of progress reporting ? Is there any key points/events ?
Like other notification system, events are the key-point.
I think, for monitoring purpose, "start" and "end" events must be generated for the caller on each item. Thus, there must be at least 2 calls to the anonymous callback function: one at the beginning, and one at the ending. The intermediate state "transmitting" might not be very useful for tiny files, and the chance when we could see it also depends on how io.Copy acts on tiny/huge files.
If we are going to provide an approach for monitoring, WHAT and WHEN the caller get notified must be declared and guaranteed in advance.
For example, you can not say: Caller will be notified twice or more times during transmission. It depends on the size of file.
You should say: Caller will be at least notified twice(on beginning and ending), plus several times of "transmitting" events with the count of bytes already transmitted.
And, to make it better, we can mandatory split file into chunks by using io.CopyN, it helps us always generate "transmitting" events to the caller at a relatively fixed rate, no matter how big/small the file is.

Performance issue.
Both you and my approach are synchronous. Next chunk won't be written to wire until the callback returns. If user do some thing slow in the callback(eg: drawing a bar on screen), it will significantly slowdown the transmitting.
This might not be important as we do not concentrate on performance, but at least there should be a warning about performance degradation on such usage.

That's a lot of discussion above. Let me file a checklist if you are still interested in.
Assuming we are going to make file transfer observable.

List out what metadata should be provided for observer. (eg: file name/path, transmitted size, total size etc)
Give an explanation of definition/terminology introduced if any.
Declare WHEN the observer will be notified with those metadata.
Potential side effects, or a brief introduction of how the monitoring mechanism works.

In a nutshell, I hope it can be defined clear and implemented without confusion or undefined behavior.
Thank you again for your patience and devotion.

No worries at all about the delay! I completely understand that work can get busy, and I appreciate you taking the time to provide such a detailed response.
It’s clear that we’re both aligned on the complexity and importance of solving this problem in a robust way. I appreciate your thoroughness in outlining the potential issues and the checklist for defining how progress reporting should work.
Given the points you’ve raised and the checklist you provided, I’ll take some time to consider and propose a solution that addresses these concerns. I believe this will help us continue iterating on the discussion and refine the approach to ensure we have a clear, well-defined, and reliable implementation.

I wanted to let you know that I've updated the pull request with a new proposal for the code.
In this proposal, I've introduced a new function copyWithCallback(dst io.Writer, src io.Reader, buf []byte, cb func(n int64)) (written int64, err error). This function is based on io.copyBuffer, but it accepts an anonymous callback function that is called with each chunk written. This function is used both for uploads and downloads within the new methods I've added to sessionStream, called get(w io.Writer, ti *streamTransferInfo) (n int64, err error) and put(r io.Reader, ti *streamTransferInfo) (n int64, err error).
These methods are responsible for sending the start, tick, and end events to the anonymous function that the user configures in the DirTransferOption object, called ObserverCallback func(scp.ObserveEventType, scp.TransferInfo). This callback function receives the event type as the first parameter and the transfer information as the second parameter, allowing the user to track the number of bytes transmitted.
Additionally, the calls to ObserverCallback are executed in separate goroutines, so they won't affect the transfer performance.
As a small improvement, I've also increased the size of the transfer buffer to try and enhance the transfer speed for small files.
I've made an effort to include detailed comments in the code to ensure it is clear and easy to understand.
Of course, I’m open to any changes or suggestions you may have. We can take this code as a starting point to align our positions and continue refining the solution.
Thank you for your time and feedback!

Thank you for the detailed explanation!
I've noticed a lot of changes since last time. This might need more time for reviewing and advice.

I've tested the code in a real-world environment, and the proposed solution is actually faster than the original scp command. I've attached an image to show the results.


Please add search bars for adding new content to tiles.

Is your feature request related to a problem? Please describe.
i like the idea of a gm screen but the drop down menus are difficult to navigate when you have so much data.
Describe the solution you'd like
instead of the drop down menus id like search bars. either as a replacement but in addition to all the tiles. this would increase the functionality of this module 10 fold.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I believe this is covered by #7

As a side note @ThingsCouldGetDicey you can drag and drop directly into cells.


flowforge broker error

Current Behavior
Getting below error
flowforge-broker_1  |<PHONE_NUMBER>: Bad socket read/write on client forge_platform: Unknown error. forge_1             | [2022-08-21T03:47:56.344Z] INFO: Reconnecting to comms broker flowforge-broker_1  |<PHONE_NUMBER>: New connection from <IP_ADDRESS>:36780 on port 1883. flowforge-broker_1  | time="2022-08-21T03:47:56Z" level=error msg="http request error: Post \"http://forge:80/api/comms/auth/client\": dial tcp <IP_ADDRESS>:80: connect: connection refused" flowforge-broker_1  | time="2022-08-21T03:47:56Z" level=error msg="Post \"http://forge:80/api/comms/auth/client\": dial tcp <IP_ADDRESS>:80: connect: connection refused"
Expected Behavior
No response
Steps To Reproduce
docker-compose up
Environment

FlowForge version: 0.8.0
Node.js version: 16.13.2
npm version:
Platform/OS: Ubuntu 20.04
Browser: Chrome

edit the broker/mosquitt.conf file to change the auth_opt_http_port number to 3000
auth_opt_http_host forge
auth_opt_http_port 3000
auth_opt_http_getuser_uri /api/comms/auth/client
auth_opt_http_aclcheck_uri /api/comms/auth/acl

Thanks @hardillb . Its working fine with updated port


Canceling setting changes not works with unallowed values

Steps to reproduce.

Edit any Integer setting manually (not with a slider but via direct value entering).
Set the value above or below the restriction.
Hit "Done".
The changed setting will show the appropriate cap instead of the entered value, but ignore that.
Exit the settings configuring screen by hitting "Cancel".
Re-open the mod settings - they will show the values you've entered.
Restarting the game fixes the issue (because the the settings file was not changed), but until then game will use the wrong values.

Might be fixed by the switch to game provided edit box, need to check

Investigated the issue.
The value changes 2 times when being overflown. First, the original value (i.e. 0), then the value that is over the restrictions (i.e. 200), then the rounded down value (0-100, 100) by the game.
Our do-undo system will capture 200 as the original value instead of 0 and 100 as the changed value
The do-undo system is not expecting changing the value in the middle of the whole flow, will need further investigation.

Not possible anymore with the UI system, the new input box we use does not allow setting a value, plus when setting via the UI we clamp the value.
This still should be possible if we edit the value directly in the model, but we never had a mechanism for clamping the values in the model, this falls on the mod developer.
We could clamp the value when we receive a PropertyChanged event, but I don't think the UI module should enforce this behaviour


ToT prompt that explicitly encourages experts to build on eachother's…

… work. Includes markdown formatting.

Thanks for the PR!


configurable at build time

added makefile to allow for variable definition without source code
modifications
adds some error handling
catch and permit error when history folder exists
move existing default values to top; still allows non-make build/config
take basename of argv[0]; errored out when contained slashes
passed args to goroutine for concurrency safety
create as package for easier dep management

I have no idea what I'm doing with anything related to go mod, sum, pkg, or otherwise, and I appreciate your contribution. Well done!


Move to keyset pagination

Description
This PR modifies "chunk" behavior to follow keyset pagination patterns. We gather sets of pages as pagesets which are based on a key per table which is used to help create pages of rows from tables. pagesets are gathered ahead of time to retain the ability to parallelize where appropriate. This change required a new configuration parameter to be specified per table and the overall join.
Operationally this reduces the amount of data stored in tables throughout, reduces the complexity of the sorting performed, and avoids unnecessary data loading which occurs during the use of OFFSET.
Changes here made it unnecessary to create metadata columns and as a result I've removed those from all spots I could find.
Changes here are intended to address #214 , which turned out to be more related to data size than the sorting implementation. This is confirmed by a now passing large_data_tests test of JUMP data using the full dataset (instead of a truncated version).
Closes #214
What is the nature of your change?

[x] Bug fix (fixes an issue).
[ ] Enhancement (adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] This change requires a documentation update.

Checklist
Please ensure that all boxes are checked before indicating that a pull request is ready for review.

[x] I have read the CONTRIBUTING.md guidelines.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] New and existing unit tests pass locally with my changes.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have deleted all non-relevant text in this pull request template.

Thanks @falquaddoomi for the review and comments! I made some adjustments based on what you mentioned.

Thank you @gwaybio, @jenna-tomkinson and @falquaddoomi for your reviews! After making adjustments for all comments I believe this is now ready and I'll merge this in.


Update Vulnerable Dependencies

We should update these vulnerabilities as soon as the updates are available.
These might affect us but there is no current update available.

[ ] https://github.com/NASA-PDS/doi-ui/security/dependabot/9

These won't affect us since they are not exposed after the build process but we should still update as soon as possible.

[ ] https://github.com/NASA-PDS/doi-ui/security/dependabot/12
[ ] https://github.com/NASA-PDS/doi-ui/security/dependabot/14
[ ] https://github.com/NASA-PDS/doi-ui/security/dependabot/29
[ ] https://github.com/NASA-PDS/doi-ui/security/dependabot/30

The full descriptions of these are at #137

This ticket is obsolete since we have now more vulnerability to fix and more dependencies to upgrade.


Update perf and latest features for llm models (Oct 21)

Ticket
N/A
Problem description
N/A
What's changed

Updated perf and stable release versions for llm models on front page README
Updated MODEL_UPDATES with latest model features

Checklist

[x] Post commit CI passes
[x] Blackhole Post commit (if applicable)
[x] Model regression CI testing passes (if applicable)
[x] Device performance regression CI testing passes (if applicable)
[x] New/Existing tests provide coverage for changes

ms for ttft looks much better, thanks.

let's remove llama-2, no one cares and it is the same perf anyways
I think unet should have some perf boost, ask @esmalTT

ms for ttft looks much better, thanks.

let's remove llama-2, no one cares and it is the same perf anyways
I think unet should have some perf boost, ask @esmalTT

@uaydonat We don't have UNet on the table. Is it still the case that we can't add it since it's proprietary?

We are adding back unet now.


Update HeaderMatcher proto to be publicly visible

Title: Update HeaderMatcher proto to be publicly visible
Description:

Currently, the HeaderMatcher proto is contained in the route.protofile which is in the  "//envoy/api/v2:friends" visibility group of the API. However, this matcher, and the associated code is more widely useful than just from this group. My recommendation would be moving this particular advanced matcher, and maybe other related advanced matchers to the envoy/type/matcher api subgroup so they may be consumed by protos outside of the core API. Barring this drastic action, simply making the route.proto publicly visible would also solve this issue.

[optional Relevant Links:]

https://github.com/envoyproxy/envoy/blob/c776fc3bd710d1c4a5e576144986cbff8f013bf4/api/envoy/api/v2/route/BUILD#L16
https://github.com/envoyproxy/envoy/blob/c776fc3bd710d1c4a5e576144986cbff8f013bf4/api/envoy/api/v2/route/route.proto#L1289

Agreed, cc @htuch

I think in v3 this makes sense, ideally we move some of this to udpa.type.v1. We should get more of the @envoyproxy/udpa-wg involved as we do this.

@mattklein123 I'm more than happy to take this on. I've never contributed to upstream envoy before, but I've been doing envoy development over at solo.io for a while.  Not sure how it works, does someone need to assign me, or should I assign myself?

@eltanya assigned, the WG aspect will make sense when you put the types in https://github.com/cncf/udpa

@EItanya friendly ping.

Just started working on this and I have a few questions about the scope of this PR.
When I first opened this, I Was not only referring to the protos themselves, but also the host of utility functions which have been created for them. Most of them located here.
I have already extracted them HeaderMatcher message and the QueryParameterMatcher message from the route proto, but I was wondering if this PR is meant to also update the code, or does that happen when stable v3 comes out?
Should have a PR up soon, just working out the proto dependencies.

The code and API changes can be largely handled independently. For the API changes, you'll need to not actually make any breaking changes in the v2 APIs, but instead add in parallel the new paths using the types you are refactoring, and deprecate the old paths with deprecated annotations.
The code can actually move today without any breaking change, so up to you how to sequence or handle this. I'd suggest getting a WiP out ASAP to ensure that we're aligned on the direction.


Add contributor filter & aggregations to API

I think this might be deployed already; I need to test it.

(requires a reindex, a voice said)

(still getting notifications for some reason)

I think the reindex is done, I just need to test it.
Try clicking the unsubscribe button on the right?

James has confirmed this is working.


"Failed to load the jupiter-notebook package": Unexpected token

I successfully installed the developer version (thanks to advice gleaned from #23):

git clone https://github.com/jupyter/atom-notebook.git
cd atom-notebook
PYTHON=python2.7 apm install
apm link

When I open Atom, I get the following failure-to-load error. The error message links me to #8, but I don't think these issues are actually the same.

I also tried uninstalling the package in Atom, and then reinstalling via PYTHON=python2.7 apm install jupyter-notebook (that is, downloading the package and not using the cloned repo). I still get the same error.

Atom Version: 1.4.0
System: Mac OS X 10.11.2
Thrown From: jupyter-notebook package, v0.0.8
Stack Trace
Failed to load the jupyter-notebook package
At Unexpected token .

SyntaxError: Unexpected token .
    at Module._compile (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:77:42)
    at Object.defineProperty.value [as .js] (/Applications/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:208:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:50:27)
    at Object.<anonymous> (/Users/alexchase/atom-notebook/node_modules/jupyter-js-services/node_modules/jupyter-js-utils/lib/dialog.js:3:1)
    at Module._compile (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .js] (/Applications/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:208:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:50:27)
    at Object.<anonymous> (/Users/alexchase/atom-notebook/node_modules/jupyter-js-services/node_modules/jupyter-js-utils/lib/index.js:7:10)
    at Module._compile (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .js] (/Applications/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:208:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:50:27)
    at Object.<anonymous> (/Users/alexchase/atom-notebook/node_modules/jupyter-js-services/lib/config.js:3:13)
    at Module._compile (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .js] (/Applications/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:208:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:50:27)
    at Object.<anonymous> (/Users/alexchase/atom-notebook/node_modules/jupyter-js-services/lib/index.js:7:10)
    at Module._compile (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .js] (/Applications/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:208:21)

Commands

Config
{
  "core": {}
}

Installed Packages
# User
jupyter-notebook, v0.0.8

# Dev
No dev packages

If you write require('<path-to-sources>/atom-notebook/lib/main.js') in Atom devtools console, it gives the location of error:
atom-notebook/node_modules/jupyter-js-services/node_modules/jupyter-js-utils/lib/dialog.css:6
It is probably related to: https://github.com/jupyter/jupyter-js-utils/blob/master/src/dialog.ts#L8

Opened an issue at https://github.com/jupyter/jupyter-js-utils/issues/20

Right, all of the jupyter-js-* repos assume the ability to require() a css file by name, which is provided by loaders such as Webpack and SystemJS, I'll update the readme to reflect this.

Interesting... I'm not running into this problem but @maxxk is. We're obviously not running Webpack or SystemJS in atom-notebook, we're simply importing/requiring jupyter-js-services (https://github.com/jupyter/atom-notebook/blob/f185c49f646f15db2371e4307ac493c232c85d12/lib/notebook-editor.js#L12). Any ideas??

Jupyter-js-services relies on jupyter-js-utils, which as a require()d css file, dialog.css.

I think this may warrant splitting utils into those requiring css and those not requiring it, so that jupyter-js-services can continue to be used in a node context.

Agreed. Let me know if you need my assistance 👍

@jasongrout, shall we make another repo called something like jupyter-js-graphical-utils or jupyter-js-visual-utils?

@minrk, same question ^^

@blink1073 for things like the dialogs? I suppose so, since they are used by multiple applications. I might say gui-utils.

Yep, anything that requires the DOM or css, gui-utils sounds good.

We just made https://github.com/jupyter/jupyter-js-domutils.  @blink1073 - you have permission to push to it.

Should be fixed by depending on "jupyter-js-utils": "^0.4.0".

Great! @blink1073 atom-notebook depends on jupyter-js-services, so would you like to me to submit a PR of jupyter-js-services that depends on this new version of jupyter-js-utils? Or would you like to do it?

Oh, sorry, that should say "jupyter-js-services": "^0.4.0", which already depends on the updated js-utils.

👌

On Jan 15 2016, at 12:31 pm, Steven Silvester
<EMAIL_ADDRESS>wrote:

Oh, sorry, that should say "jupyter-js-services": "^0.4.0", which already
depends on the updated js-utils.

—
Reply to this email directly or [view it on GitHub](https://github.com/jupyter
/atom-notebook/issues/30#issuecomment-172085128).![](https://github.com/notifi
cations/beacon/AAfRYv7m64sD57CbrCW9HGP0L3CwQ1hSks5paU6UgaJpZM4HEyYK.gif)

@aechase @maxxk https://github.com/jupyter/atom-notebook/commit/ee702cecd93f65f6e326978f8e8eaff2bc1a0155 should fix this. Either update jupyter-notebook to 0.0.9 inside of Atom or clone the current repo. Let me know if this solves it...

@gnestor Solved! I can now install and load using PYTHON=python2.7 apm install jupyter-notebook. Thanks for the quick work, everyone.

👍


Log Data is Truncated in PodeWebFileStream

Describe the Bug
When streaming a log file using PodeWebFileStream, the full contents of the log are not showing. Here is an example showing stack trace data missing. Is there a way to increase the number of lines shown, or to include all data? I tried the -Height parameter but it doesn't change the amount of data shown, only the size of the text field.
Log file:

Stream:

Ooo, that's interesting. It looks like it's skipping content or somehow mashing different lines together 🤔 When I get a moment, I'll test it and see what happens.
As for -Height, it's just for the display height of the textbox on the frontend :)


Simplify Align.expected_outputs() CRAM path construction

Reported in #543, and in a similar Align inputs context from elsewhere, is the following failure:
  File "/production-pipelines/cpg_workflows/stages/stripy.py", line 76, in queue_jobs
    cram_path = inputs.as_path(sequencing_group, Align, 'cram')
  File "/production-pipelines/cpg_workflows/workflow.py", line 309, in as_path
    return res.as_path(key)
  File "/production-pipelines/cpg_workflows/workflow.py", line 178, in as_path
    raise ValueError(f'{res} is not a path object.')
ValueError: gs://cpg-perth-neuro-main/cram/CPG297432.cram is not a path object.

Messages like this are usually because res is a string rather than some kind of path object. However in this case (as revealed by studying the code or by mypy), the problem is that sequencing_group.cram is a CramPath, which — despite the name! — is not a pathlib.Path-like class.
Hence the minimal change to make this work would be:
-            'cram': sequencing_group.cram      or sequencing_group.make_cram_path().path,
+            'cram': sequencing_group.cram.path or sequencing_group.make_cram_path().path,

However in this PR I've taken the opportunity to refactor this to treat cram and crai together, which is hopefully clearer.
We want .path and .index_path from sequencing_group.cram if it has been set; otherwise fall back to the generic make_cram_path(). Fixes #543.

I'm disappointed that static type checking did not point out this issue when this code was introduced in PR #537. This may be due in part to the fact that (at least on my local machine's installation) mypy does not see the type annotations in cpg_utils/_init.py_, instead just reporting sequencing_group.make_cram_path().path's type as Any.


Export to Turtle/JSON-LD does not work after re-execute

Steps to reproduce:

Run Odalic on top of Books-v1.csv

propose new classification for series, use that

re-execute

try to export, nothing is displayed.

Hi, @josef-janousek . The exceptions should not be swalloved now. You can look at it.

@tomas-knap , @brodecva : This fault was caused by invalid URI (without prefix part) which was sent by client UI after proposal. Now I added checks for this situation to the RDF export adapter. So when the IRI is not valid, no triple is produced and error message is written to the log, but the whole process of exporting is not interrupted. Maybe another question could be, if we eventually should inform the user about the occurence of invalid IRI more than just in the log.

Relates with: https://github.com/odalic/odalic-ui/issues/248.
May relate also with: https://github.com/odalic/odalic-ui/issues/240


Documentation is ambiguous

The documentation is not obvious, I mean I know what watchdog timer is and how it should work and all, but the API reference is not clear.
I can't understand what event gets called when, and what does each function do (feed function has the documentation that it feeds the dog!).
I don't even know how this maps to the watchdog timer standard where there is a reset (or a kick), that resets the timer, and a callback that gets invoked if time passes (timeout) and no reset was invoked.
If you could please make things more clear, I (and probably other people) would be grateful.

I think I got to understand it but not the text nor the example were clear enough, I had to read the internal code and test it.
First of all I didn't understand the very "main" verbs about the watchdog:

"Reset" means the watchdog "alarms". In a typical use case if the watchdog "resets" you would need to reset something because it was frozen or failing.
"Feed" means you delay the "reset" event. It means the system is working fine.
"Sleep" means you pause the need for "food". It will be activated again (I think) when the watchdog is "fed".

Then I needed to understand how they actually work in detail:

A new watchdog won't reset unless it's "feeded" for the first time. It's the first feed that starts the timer.
After a reset, if you need the timer to run again you need to "feed" the watchdog. Otherwise it's stopped.
The "food" object is modified internally in a way that will make different watchdogs interact with each other in a way you don't expect (they will copy the default timeout from one to another) so it's important that you create a new food object for each watchdog if you have several of them with different timeouts.

About that last point I think that's a mistake of design and should be corrected.


searching for "IntelliSense" or "completions" doesn't provide expected result

I had someone ask how to turn off completions for Dockerfiles and it turns out the setting editor.quickSuggestions controls whether or not the completion list shows up.
  // Controls if suggestions should automatically show up while typing
  "editor.quickSuggestions": {
    "other": true,
    "comments": false,
    "strings": false
  },

It took me a long time to find this setting because I searched for "completion" "IntelliSense" and probably a bunch of other things to no avail.
With the bing search now in place, I would have expected that this setting would show up for "completion" or "intellisense", but it still doesn't.  I also searched for "other" but it doesn't show up. If I search for "comments" it does (but it looks like a result of bing search).

It does return that setting for "intellisense" but for me, it's hidden behind settings for the npm-intellisense extension which score much higher. I think the scores for those core settings should be higher, will follow up on that.
What settings do you see for "intellisense"?
I'll add "completion" as a synonym of "suggestion".

yes, i get all of the npm-intellisense suggestions but not the core one.

I don't think this will require a code change in VS Code, moving to February to unblock the release

@roblourens Moving to March since you are not here ...

i just want a file scope suggestion, how can i do this?
my settings
{
    "editor.tabSize": 2,
    "editor.quickSuggestions": {
        "other": false,
        "comments": false,
        "strings": false
    },
    "editor.acceptSuggestionOnEnter": "on",
    "editor.quickSuggestionsDelay": 10,
    "editor.suggestOnTriggerCharacters": true,
    "editor.wordBasedSuggestions": true,
    "editor.parameterHints": true,
    "editor.suggestSelection": "recentlyUsedByPrefix",
}

but nothing happend

@chrisdias has the setting changed? I can't find that setting now.
@crapthings please file a separate issue if that still happens for you on the latest version of VS Code.

i still see "editor.quickSuggestions" as a setting in settings.json, although now it is seems to be subsumed by "editor.suggest.*"


OSX Bundle needs a log window

May be this should be a own issue as it targets all OSes, but I wanted to ask to include the log output into the main window instead of having a dedicated window? May be configurable by command line parameter?
I imagine the same output as in the log window appearing in the main window e.g. bottom left and after 5 secs fading out. Would that be a good idea?

I agree @drtrigon and we already discussed about that on Discord. I'd like to try a small integrated window using imgui.

Would that be copy/pastable ?

I think so yes, we can see an input selected in the screenshot here: https://raw.githubusercontent.com/wiki/ocornut/imgui/web/v167/v167-misc.png

moving to 2.2 unless you want to tackle imgui right away @Meakk

Lets tackle that with imGui


Password reset

[x] Offer password reset on login screen
[ ] Offer password reset after failed login

Use new API route /users/reset_password for this task.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Can we close this? We implemeted this with the website


USDC Stuck in force bridge

Hello nervos team
I withdrew my usdc to force bridge but the fees is too high so i wanted to withdraw them back to yokai but there is no option to send them back and no way to swap them to other assets . And now my 150$ Usdc is stuck and I cannot do anything.
There are a lot of people who are facing this issue with their 1000’s of USDC stuck if you check ypur discord.
Please help and provide us a solution to withdraw usdc.

The wallet Force Bridge uses is  pw-wallet, which does not support sudt transfer yet.
We are working with the community to develop some tools to accomplish this. It is expected be finished in 1~2 weeks.
Your asset is safe in the wallet. We will inform you as soon as we figure out the solution.
Sorry for the inconvenience.

Same here for ETH. Sent some as a test from YokaiSwap to the bridge, but no way back atm.
Also would be nice if those would show up in MetaMask, which they don't (at least not for me).

Is there any further update for this case?

The wallet Force Bridge uses is pw-wallet, which does not support sudt transfer yet.
We are working with the community to develop some tools to accomplish this. It is expected be finished in 1~2 weeks.
Your asset is safe in the wallet. We will inform you as soon as we figure out the solution.
Sorry for the inconvenience.

Is there any further update for this case? my usdc has stucked for almost 2 weeks now

Same here, would really love to get my funds back from Force Bridge without the need to pay the gas fee.

Hello. I am also interested in the question at what time is it planned to launch the reverse withdrawal of funds from the bridge?

Hi, @vkhnychenko @William2809 @Shivay57
The CKB wallet have been switched from pw-lock to omni-lock.
Use this tool to migration assets from bridge to Yokai  again.
Vsit Asset Migration Guide for more details.


ClusterLoader - Resource usage constrains

Changes:

Adding template provider to measurement config
Resource usage constrains validation
Resource constrains can be specified with yaml file. Resource validation was moved to resource usage measurement. If constraint is violated, metric violation error will be returned.

/assign @wojtek-t

/lgtm