Extract Comments from HackMD Book

Pull out comments from Getting Started on HackMD. These comments are in the Markdown code.
Pull out any comments from other files that use the HackMD comment feature

Comments have been extracted from the HackMD book and moved to: https://hackmd.io/SRCeeWL7Ty27_gR29QSbYg?view#Getting-Started-Comments

Added link to comments into Update Getting Started Page#465


VNFC Start/Stop is not working properly

Hello community,
Nowadays I'm working with VNFC as well in order to manage functionality of start/stop procedures. Whenever I take action about this , it seems that there is not problem on OpenBaton.
Initial status ;

after stop;

Below one is openbaton.log file output during action;

Until this moment , there is not any problem.
However when I check OpenStack side , specified instance is still running although it has been stopped.

I tried to find issue but I couldn't find the reason why VM is still active.
The only guess that I found -I'm not pretty whether it's related or not- is that this start/stop is just used for scripts

Thanks in advance

Hi,
I think your guess is right. Our start/stop focuses on the service running inside the VM. So if the stop script is correctly executed, the nfvo + generic vnfm will assume that the service is correctly stopped.
Does this answer help?

Is this behavior complaint with ETSI NFV specification? Will Openbaton have  support shutdown and start operation of a VNF  (VM)?

This behaviour is connected with the vnfm you are using. A different vnfm than the generic one could have a different logic:

running the stop scripts
invoking the shutdown of the machine in the vim (saved from the first instantiate message)
The start does then the same: start the machine if it is shut off

once the VM is shut off, you are then not able anymore to contact via the EMS, that will start automatically when the VM boots, so the re registration to the vnfm has to be handled but this only if you want to simply extend the generic vnfm. Another vnfm can choose a different way to communicate with the VM


Is this code only for Ubuntu 14.04

Hello,
I have tried the installation process with Ubuntu 15.10 but it is giving me some error while running below commands.
$ npm install
$ npm install gulp -g
Can you please suggest. Is this code works for Ubuntu 15.10 or 16th?
Thanks in advance.

@shyam9876lal  check your node version, you must run node v4


unable to download image

Expected behavior
Download image
Actual behavior
Showing context canceled error
Information about the Issue
Steps to reproduce the behavior

...
...

me too。

me too。

Just tried to downgrade kitematic to version 17.3... It is working now


How to set the developer  key in the project

I am unable to find a method to set the developer key in the project. Please suggest. In the Youtube library, we sent the developer key at the time of initialization of youtubeplayerview object.

I need this info too. We need to track user who watch from apps source. The data is important for content creator

Any news on this? I need to use an api key to track who watches from the app

There is not developer key for the IFrame player, as far as I know.


Small tweaks to sequence diagram generation.

Fix up name of font download and no transparency so it is easier to iterate.

Finally got seqdiag working locally and this change works for me.


Wrong code indentation caused the ol list to split.

@lespacedunmatin does the build error make sense?  I don't think this has anything to do with your update but if you have an idea about it, would like your input.

I may have used tabs instead of spaces or spaces instead of tabs…


Some comments after a static review of the code/design.

FOOOF notes

Variable/kwarg naming is inconsistent in style. Sometimes verbose names are used (’bandwidth_limits’) other times highly abbr. var. nm. are used (‘bg_use_knee’). Same holds true for FOOOF.atttr_ names, etc. I’d opt for a more verbose style.
I appreciate the intended convenience of FOOOF.model() but it’s auto-plot functionality has has two negative effects. a. It may lead to confusion: ‘model’ seems like a top-level generic command. It’s the first thing I would try if approaching the library cold. The user may however be running on a remote connection, where auto-plotting can be both unexpected and SLOW as the plot is sent over SSH/X11. That is, the name ’model’ seems like the generic top-level way to invoke FOOOF, but it is not. b. It adds a hard unnecessary dependency of FOOOF on matplotlib. Consider renaming to ‘report’?  I realize you address this in the examples; I don’t that is good enough.
The methods do not in plt do not test for a matplotlib install. This will lead to not-graceful failures. Wrap the matplotlib import in a try/except and flag failure to import throughout the package so things go smoothly?
The fit.FOOOF class has code intended for group.FOOOF (e.g., https://github.com/voytekresearch/fooof/blob/master/fooof/fit.py#L278). This is a pretty serious abstraction leak, even if it is ‘private’. Is this really the best solution?
It seems odd/inconsistent to generate a ‘FOOOFResult’ on request but not use that internally on FOOOF itself. What’s the use case here? Why use a named tuple instead of collecting/returning the key attrs_ as they are? …There should be one right way to do things.
While I really like the reporting-as-text-thing (‘print_results’) it uses a lot of whitespace. The report could be made more compact/succinct. If printing several results on the CL, the info density would be very low; there’d be more scrolling than necessary, which is a pain in some terminal environments, and even in the notebook.
What is the intended use case for being able to load past FOOFs back into FOOOF - https://github.com/voytekresearch/fooof/blob/master/fooof/fit.py#L365.  Who would do this? When? Why?
Docs on private attrs (https://github.com/voytekresearch/fooof/blob/master/fooof/fit.py#L66). If they are for users, remove the leading ‘_’. If they are private, don’t doc them in the top-level docs?  These are very useful to debug, but they are only useful if you know FOOOF internals. What level of competency do you expect from users?
Overall comment about 7/8: it is tempting to want to add things, “that might be nice to have” or “someone might want” but that comes with a real burden on maintenance and code complexity. I’d make sure the features/info you expose cover only the core expected uses and then let people’s actual use determine other additions. Maybe all that has passed that test; I don’t know. Just sayin’ :)
In FOOF (note the lack of one ‘O’) I had a notebook that the stepped through all the internal processing steps, showing intermediate results. Might be good to do the same for FOOOF.

(I'm going to do some runtime/performance analysis later as well...)

Wait I should say something nice: you folks did a great job!
I. proud.

Also, if any of my Qs have been answered in previous thread/issues/whatever do point me at that, with my apologies. :)

This is awesome, exactly the kind of code-review I was looking for, thanks @parenthetical-e !
All very good points, I will update / respond as I go through the clean-up round of the code-base over the next day or two.

Okay: bunch of comments, follow-ups etc. I tried to sign post where things are at for each point.
@voytek @rdgao : Your thoughts on some of the open questions would be great.
Where things are mentioned to be 'done', they are in PR #55

Request Input.

Hmmm. Yeah, I see what you mean. So, in my mind it was all pretty verbose, but I guess really the current approach is more like 'pretty verbose, but limiting to still max length of ~ 15 characters', creating an inconsistent use of abbreviations. Perhaps the most common deviation from being really verbose is using 'bg' in place of 'background'.
So, what should we change? I don't really like 'bg_use_knee' to start with. Move to 'background_use_knee'? Something else? What other public params / attributes might do well with changing? Nows the best time?
Related: I vote for changing 'max_n_oscs' -> 'max_n_gauss', since I think it's clearer to not overly conflate gaussians with distinct oscillations (because FOOOF has a tendency to use overlapping gaussians to fit what we would probably consider 1 oscillation). Thoughts?
^Y'alls thoughts here would be helpful, I think I'm in too deep / too used to it as is, to notice weirdness.

Request Input.

I agree. I think 'report' is better, but is it clear that report should take in data and run the model, as opposed to just reporting? What about 'fit_n_report'?
Or, we could drop the 'all in one', and have 'fit' (as is), 'report' (new: displays print_results & plots).
Either way, we should perhaps change 'create_report' -> 'save_report', as I think it's not currently obvious that 'create_report' saves, but doesn't return / display anything.

Agreed.

Not yet done (I need to check into how to do so), but yes, I agree on making mpl an optional dependency, and will do that.

Done.

Yep, this was a messy hack-fix. Updated to fix abstraction-leak.

Question / Request Input.

Hmm. This is something I pulled from scipy.stats.....
I'm not sure I quite understand the point, as it seems to me this does collect & return the key attrs as they are (at the moment you ask for results). Within FOOOF, this is basically just a mild convenience of bundling outputs, with labels, but becomes more important (I think) for collecting organized data in FOOOFGroup. I guess an alternative would be, in FOOOFGroup, to make all the results attributes into matrices all collect as it runs (similar to how FOOOFGroup has 'psds'), but the issue is quirky sizes: there's not an obvious clean way to stack oscillation outputs, of various sizes.
So: I'm not sure I'm clear on why this is disprefered, and/or I'm not sure how to cleanly get rid of it - but if you have a suggestion of how to do so I'd be interested.

Question / Request Input.

Yes, this might be over-tuned to using  notebooks. My (not great) rebuttal, is:

Making it more succint (removing extra lines, perhaps right justified) might make it harder to read (and less nice looking)
My expectation of the use case of these method is quick checking, not looking at any large number of them.
On my MacOS terminal, the prints do look fine / tractable.
My (could be wrong) guess is that notebook use of these methods will be more than terminal use, and so I'm okay with somewhat over-tuning to notebooks.

That said: I'm happy to be over-ruled on this, if others have votes on way or another.

Comment / Request Input.

I think this is actually fairly key (most users will / should use this), for several reasons / use cases:

This method can load a settings file, which is useful to ensure consistency by using and loading a settings config file.
Easy support for separating running FOOOF, from analyzing results.  Now, after, with load:

Easy checking of past-runs of model. You check the reports, some group / results are weird. Load, plot, explore what's happening.
Organized loading of FOOOF data for further analysis. You can load back into a FOOOF object, which keeps thing organized, and then use the object to support selecting data etc (ex. get_all_data) to then do whatever you want to do. The alternative is requiring users to do more low-level work loading loading and parsing the JSON files (or a bigger re-vamp of our IO, in one way or another, but from prior discussion here (#40 ), I didn't get a sense of preferable alternatives).

Conclusion: I'm open to replies / comments / suggestions, but my vote is keep / leave as is.

Done / Comment

Yep, I agree, this is a good point, and I don't want/expect users to have to care / think about them. I do want to keep them documented somewhere, so they are available for any users who do want to jump into the actual code. I've moved them to the documentation at the top of the file. Not sure if this is the best spot (is there some canonical location for private docs like this?). If anyone has suggestions of where to put em, let me know.

Comment / Request Input

I totally agree. Definitely something on my mind. I'm wary that I reckon I have a tendency to over-add, and that by largely tuning to myself as a user, I'm tuning to the least representative user. This might argue against, for example, having (or further adding to) fooof.analysis.
However, I do think I could argue, that all that is in here is pretty key. Part of my logic (related to 7 too), is that we should ourselves offer any functionality that otherwise a majority of users would likely have to often re-write (idiosyncratically) themselves, and in doing so, I've chosen a degree of adding things / trying to be friendly to the user (adding FOOOFGroup, IO, analysis, etc), over a what could otherwise have been design choice with a stronger inclination of being lean and concise. Another benefit is we get more input on the 'right' way to do things (standardizing saved outputs, for example, making sharing way easier).
Conclusion: I'm open to replies / comments and especially any particular suggestions of anything to hide / remove, or freeze further development off, but I think I stand by all that is currently in / exposed.

Done.

Yes, great idea! Added to tutorial materials. In PR #54

Okay: so I've opened a round of PRs now (tutorials, last_tweaks, and release).
Other than anything that comes up in those PRs, this Issue is the last thing to do before it should be ready to tag and release - I'm done all my updates.

I don't know what the conventions are for any of these in proper software engineering, so I'm just putting in my two cents as a naive user. It's just one set of opinions.

bg seems like a fine shortform for background, if it's consistently used elsewhere. I'm ambivalent about this, and prefer shorter args just to keep the code short. fit_bg_knee?

I would definitely vote for using max_n_gauss, though, because that's what it spits out, not definitive oscillations. It will take a bit of explaining the difference between gaussian and oscillation, i.e. the overlap problem, but it's a more much accurate portrayal of the algorithm.

Again, pretty ambivalent, but I like the all-in-one reporting, because I'm lazy. Maybe change the name to make it sound less prominent, like Erik said, but I would vote to keep this "one button and it works" functionality.

I would definitely like to keep this. The reporting/printout functionalities are probably my favorite things here because it got me onboard with using the thing right away. I have an aversion now to software that seems pretty easy to use in the tutorial, but every line seems to break when you try it on your own data. The report explains very clearly what the outputs are and the plotting lets me see right away if the fits look about right, and whether I've put in the right PSD. It's a great noob-friendly feature, and once one becomes a proficient user, they don't have to interact with this at all.

I haven't used this yet, but I think it's nice to have for reproducibility purposes. I don't know if you're still saving the PSDs as a part of that output, and that could be space/time consuming, but I would definitely like to save the configurations I've used, FieldTrip style, instead of going back to old notebooks to dig them up.

My thoughts:

Verbosity is preferred when it doesn't impair readability, and when less verbose options are non-obvious. fit_background_power_spectral_density_knees is, for example, too verbose, whereas fit_bg_psd_knee is fine, and obvious given the context of the code itself, for example.

No strong opinions here, honestly.

I agree with Gao: these are very useful things to help onboard new users, but also agree having mpl as a required dependency is unnecessary for power users. Can “easily” create a lean fooof that power users can run that don’t require mpl, but I believe the core fooof should require it because it’s so damned useful to be able to see what it’s doing and how it works.

Fix leaks!

Again no opinion here, but largely because I’ve not played with this latest version enough.

Strongly agree that the reporting can and should be more compact, with far less whitespace.

Yeah, when running large batches of data it’s nice to be able to pop back to explore strange fits.

I think Tom’s solution here is good.

no comments needed

Strongly agree here, and I think Tom’s new tutorials look great.

What I was trying to get at a deeper complexity/inconsistency. I’m going to try to explain using examples.I made it so during invocation there are two key terms/ideas for the user to keep track of as they configure FOOOF: ’peaks’ and ‘background’.

bandwidth_limits -> peak_width_range
max_n_gauss     -> max_n_peaks
min_amp             -> min_peak_amplitude
amp_std_thresh  -> min_peak_std  # (I don’t understand what this does)
bg_use_knee      -> background_mode = {‘knee’, ’fixed’)  # not boolean
verbose               -> be_like_erik
freqs_                  ->  freqs_
freq_range_         ->  drop? (redundant with freqs_ ?)
freq_res               ->  drop? (redundant with freqs_ ?)
Technically you  could foof raw fft; density is not needed. Plus why not be explicit?
psd_                                ->  power_spectrum_
we have a ridiculous name,,, own it :)
psd_fit                             -> foofed_psd_
background_params_     ->  background_params_
peak_params_                ->  peak_params_
A little more explicit/consistent
r2_  				      ->  r2_error_
error_                              ->  rmse_error_  (Is that what this is?)

I think report is fine. They have to look at the signature to call anyway.
Cool
Cool.
If you need it internally use it internally, OK, that’s not what I’m worried about. I don’t like exposing it because you are mixing type systems.

The primary type of FOOF before this is an instance of a class. So if I got a ‘result’ object back I’d expect it to an instance of class (e.g, a FOOFResults class) not a namedtuple which are very much  different beasts, akin to structs than class instances.
Note: I like that ‘namedtuples’ are gaining popularity, and when can be used with the coming (?) mypy-like optional typing scheme, they’ll be an interesting functional (yaaay!) alternative to classes (boooo!). We are not there yet; the language is not even close to there yet.

Agreeing with Brad’s agreement. I’ll mockup a counter-offer, :)

Keep it. But! I’ll bet y’all a burrito each this sees very little use outside the lab.

Cool

Cool.

Yay!

We have a ridiculous name... own it :)
psd_fit -> foofed_psd_

Totally.

Keep it. But! I’ll bet y’all a burrito each this sees very little use outside the lab.

You may very well be right, but @TomDonoghue's running literally millions of FOOOFs, so even if we're the only ones using it, we'll be using it a lot. This is a case where I'm happy to prioritize our needs over optimizing for some more general ideal.

Okay, so after the round of comments, it seems 2-10 are pretty much settled, with a couple changes pushed to actual_last_tweaks:

(2) change 'model' -> 'report'
(3) mpl is now an optional dependency, and updated to be able to run smoothly without it available, fail informatively if you try to use functionality that requires it, and skip tests if running without mpl (@parenthetical-e if you want to eyeball how I did this: I think it makes sense, but I wasn't 100% sure of the best way to do it).
(5) FOOOFResult: I guess I'm less worried than you are about 'mixing types'. Or, it's more that I don't have an action item here. Although it's easy not to return a FOOOFResult in FOOOF, for Group, it's not clear how to organize without them (they could be pushed more internal, but you would probably still sometimes have/want to deal with them). So, I don't know how to change, if you (or anyone) has suggestions, happy to try that, but as is, I'm going to leave as is for now.
(6) Concise printing: so, as something of a compromise, it now has an easy toggle between old-school (whitespacey), and a new concise version (good for terminal, etc). The duality is largely because the generated strings are recycled into the reports, and I don't think we want to squish them, and it keeps the more aesthetic printing available for notebooks. Currently, as defaults, calling string methods directly uses concise, where as reports are 'non-concise', but it's also exposed for users to choose. Check it out, and let me know if this fixes it in a way you're all happy with. (I like this solution, although I'm not sure about the best defaults, because it's also perhaps non-intuitive that calling print_results isn't quite the same representation as the reports).

Okay dokay!
(e)

On Dec 19, 2017, at 9:42 PM, Tom<EMAIL_ADDRESS>wrote:
Okay, so after the round of comments, it seems 2-10 are pretty much settled, with a couple changes pushed to actual_last_tweaks:
(2) change 'model' -> 'report'
(3) mpl is now an optional dependency, and updated to be able to run smoothly without it available, fail informatively if you try to use functionality that requires it, and skip tests if running without mpl (@parenthetical-e if you want to eyeball how I did this: I think it makes sense, but I wasn't 100% sure of the best way to do it).
(5) FOOOFResult: I guess I'm less worried than you are about 'mixing types'. Or, it's more that I don't have an action item here. Although it's easy not to return a FOOOFResult in FOOOF, for Group, it's not clear how to organize without them (they could be pushed more internal, but you would probably still sometimes have/want to deal with them). So, I don't know how to change, if you (or anyone) has suggestions, happy to try that, but as is, I'm going to leave as is for now.
(6) Concise printing: so, as something of a compromise, it now has an easy toggle between old-school (whitespacey), and a new concise version (good for terminal, etc). The duality is largely because the generated strings are recycled into the reports, and I don't think we want to squish them, and it keeps the more aesthetic printing available for notebooks. Currently, as defaults, calling string methods directly uses concise, where as reports are 'non-concise', but it's also exposed for users to choose. Check it out, and let me know if this fixes it in a way you're all happy with. (I like this solution, although I'm not sure about the best defaults, because it's also perhaps non-intuitive that calling print_results isn't quite the same representation as the reports).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I am going to open a new issue to discuss a proposed API overhaul.
Otherwise does everything here look good? If so, I will merge the 'last_tweaks_...' PR and re-branch for the API.

Go for it.

On Dec 20, 2017, at 7:35 AM, Tom<EMAIL_ADDRESS>wrote:
I am going to open a new issue to discuss a proposed API overhaul.
Otherwise does everything here look good? If so, I will merge the 'last_tweaks_...' PR and re-branch for the API.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@parenthetical-e : if you did/do any runtime/performance analysis, open a new issue for that.
Otherwise, this all seems covered, so I'm going to close this.
Thanks again for the in-depth comments!


README: include data licenses for data sources

You mixed up licenses.

Also, let's wait for Ubuntu's answer.

yep, thx

Ubuntu’s vulnerabilities seem to be licensed under GNU GPL v2 (https://code.launchpad.net/ubuntu-cve-tracker).

LGTM as soon as Ubuntu's license is listed. Thanks!

ptal

LGTM


How to send using streams

Hello.
How to send a message to a topic using streams ?
I'm trying to figure it out second day, reading sources, trying to make logic chains, looking to dir() outputs, but all time I get different errors.
In examples such task was absent, also I tried to copy behavior from tests - it didn't give the result.
My log story: https://pastebin.com/Rf0wYSf0
My draft code: https://pastebin.com/90jcPcaV (with all my attempts)
My code, which after receiving some message sends duplicate: https://pastebin.com/HxXNXV3F
How do I tried sending messages using streams:

created confluent_kafka Producer
manually sent message through RecordCollector (and he called Producer)
manually sent message through Processor (which called RecordCollector)
automatic sending message by Processor in case receiving of some message: https://pastebin.com/HxXNXV3F

But it still uses Producer.
My task is to send messages using streams, not by Producer.
Thank you.
Best regards,
Vladislav

Hi Vladislav,
have a look at the wordcount example here: https://github.com/wintoncode/winton-kafka-streams/blob/master/examples/wordcount/example.py#L56
To write back out, you just need to create a topology with a sink node, like this:
 sink('output-count', 'wks-wordcount-example-count', 'count')

That creates a sink named 'output-count', sending data from the 'count' processor to the 'wks-wordcount-example-count' topic.

@ah- , understood, thank you very much.
I looked at it, but didn't understood what it does.
Now all is well =)


Entity link editor suggests wrong parameters

also when adding a link pin out from a door composite it shows empty.
but when adding a link pin in it gives the correct parameters for the composite

This should now be fixed in staging!


Urgency based on a given date

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.
[X] I am only requesting a single feature. Multiple changes should be split into individual requests, with links between them.
[X] I believe my requested feature will be generally applicable to other users, not just me: it is not uniquely tied to my personal workflow.

🔖 Feature description
I really like using the Urgency for sorting my tasks. In my daily note, this only works for the daily note of today, since this is the date the urgency is based on. It would be great to be able to optionally add a date, the urgency is then based on and thereby be able to see tasks of upcoming daily notes sorted by their urgency on that day.
✔ Solution
Something like:
not done
sort by urgency on 2023-10-20
limit 6

I could then insert the date of the daily note using the Templater plugin.
❓ Alternatives
No response
📝 Additional Context
No response

Thanks for the suggestion. It's a nice idea.
In case anyone is looking at implementing this, here is a rough idea of what needs to be done...
But note that whilst writing this, I remembered an alternative option...
Urgency calculation
https://github.com/obsidian-tasks-group/obsidian-tasks/blob/d71e8a609d7e46f909572ce71291307b9a2303e6/src/Urgency.ts#L16

On the above line, replace window.moment() with a new parameter, such as today.
Probably provide a default value = window.moment()  for that new parameter

Sorting code
Here is the current code for sorting by urgency:
https://github.com/obsidian-tasks-group/obsidian-tasks/blob/7c19f3fb4fd0b1aa73c663ff19a0f34511bced3b/src/Query/Filter/UrgencyField.ts#L37-L42
It accesses the urgency value stored in the task.
This is a nice efficiency thing, as the value stored in each task is not recalculated repeatedly during the sort operation.
This would need to be changed so that:

the code for interpreting sort by urgency needs to optionally be able to read the date to use for sorting
the sort function itself needs to change, to pass in the requested date to the Urgency calculation

Other stuff

Tests should be written as the above is done
User documentation would need to be written....

See the Contributing Guide for info on all this...

This seems somewhat related to:

#1393

When writing the comment above, I was thinking that this other request was actually for running the search on a simulated date, but it's only about explaining it on a particular date...

@m4x74 Can you please explain why you are only interesting in the urgency being calculated from a different date?

Related areas:

https://publish.obsidian.md/tasks/Queries/Filters#Urgency
https://publish.obsidian.md/tasks/Queries/Sorting#Urgency
https://publish.obsidian.md/tasks/Queries/Grouping#Urgency
https://publish.obsidian.md/tasks/Scripting/Task+Properties#Values+for+Other+Task+Properties - task.urgency

A seemingly simple request is generating a lot of things to figure out, to ensure that the behaviour of Tasks remains consistent across related features....

I am leaning towards the alternative implementation - https://github.com/obsidian-tasks-group/obsidian-tasks/issues/1393#issuecomment-1346450515 - that I proposed in a comment in #1393
not done
(due after this week) AND (due before sunday)
today 2022-12-01

So that the entire query is calculated with the date being set to a different date.
Then all features would behave consistently.

First of all, thanks for the effort you're making here @claremacrae! <3 Sorry for the delayed response, but here it comes:

@m4x74 Can you please explain why you are only interesting in the urgency being calculated from a different date?

I'm not 100% sure if I understood your question correctly, but it's not that I'm only interested in setting the date in urgency. urgency is just the use case I stumbled upon. But I really like your idea of setting an alternative date for the complete query (described in #1393). This would solve my issue as well as others!

Thanks @m4x74  - very helpful.

I'm going to close this in favour of the more general #1393.


Add source for hollow docs

Also create deployment shell script to automate updates.
The script still needs to be run manually, for now.

Apart from all the markdown files, the interesting changes in this PR are:
.gitignore
deploy_docs.sh
requirements.txt


How to debug no signals being received

Thanks for giving us such detailed help on your side project 😁. Unfortunately I'm having trouble getting any radio signal.
I have one of those blue board radios you recommended:
https://www.ebay.com/itm/404407215875
I have an esp32 dev board, same pinout as your diagram, and I triple checked my wiring. I even tried with a different esp32 dev board. I got the radio configured and enabled and double checked that the pin assignment were correct from the start.
The remote I have is a "somfy telis 4 rts pure"
I'm just not getting any incoming logs or db signal strength. What's my next step?
Thanks!

Ok, progress:

That's the 4-blind remote that I'm not seeing signals from. It looks like I can actually see signals coming from my spare 1-blind remote.
Looks like when I have the espsomfy device open on both my computer and phone, only one will get the logs. Fair enough, but I forgot I left the browser open on my computer when I went into the other room.

Ok, looks like with some tuning, I'll be able to get to where I need. Thanks again for your awesome writeup and software!


exceptions.AttributeError: 'RasaCoreServer' object has no attribute 'config'

Rasa Core version (e.g. 0.7.1):
Operating system (windows, Ubuntu, ...):
I run rasa_core as http server via "python -m rasa_core.server -d examples/babi/models/policy/current -u examples/babi/models/nlu/current_py2 -o out.log" and encounter the following issue:
Issue:
2017-10-12 05:06:13-0400 [_GenericHTTPChannelProtocol,1,<IP_ADDRESS>] Unhandled Error
Traceback (most recent call last):
File "/home/osboxes/.local/lib/python2.7/site-packages/twisted/web/server.py", line 255, in render
body = resrc.render(self)
File "/home/osboxes/.local/lib/python2.7/site-packages/klein/resource.py", line 206, in render
d = defer.maybeDeferred(_execute)
File "/home/osboxes/.local/lib/python2.7/site-packages/twisted/internet/defer.py", line 150, in maybeDeferred
result = f(args, kw)
File "/home/osboxes/.local/lib/python2.7/site-packages/klein/resource.py", line 200, in _execute kwargs)
---  ---
File "/home/osboxes/.local/lib/python2.7/site-packages/twisted/internet/defer.py", line 150, in maybeDeferred
result = f(args, kw)
File "/home/osboxes/.local/lib/python2.7/site-packages/klein/app.py", line 126, in execute_endpoint
return endpoint_f(self._instance, args, kwargs)
File "/home/osboxes/.local/lib/python2.7/site-packages/klein/app.py", line 211, in _f
return _call(instance, f, request, a, **kw)
File "/home/osboxes/.local/lib/python2.7/site-packages/klein/app.py", line 48, in _call
result = f(instance, args, kwargs)
File "/home/osboxes/Documents/projects/rasa_nlu/rasa_nlu/server.py", line 69, in decorated
if '' in self.config['cors_origins']:
exceptions.AttributeError: 'RasaCoreServer' object has no attribute 'config'

The command I am issuing is "http://<IP_ADDRESS>:5005/conversations/default/parse" using Postman with a body {"query":"hello there"}. My rasa_core http server is running on a Ubuntu VM and I'm issuing this command from my Windows hosting machine.
It's working perfectly fine when I issue the same command using Curl from the Ubuntn VM the same machine where the rasa_core http server is running.
I will create a ticket in rasa_core git repo.
Thank you very much.

Content of domain file (if used & relevant):

Alright, so to make this reproducible:

did you install from pypi or git?
the postman request is run from a different machine than the one hosting the server, right?

I installed rasa_core from pypi, my pip package list look like: "rasa-core (0.7.1, /usr/local/lib/python2.7/dist-packages/rasa_core-0.7.1-py2.7.egg)".
Yes. My postman request from a Windows machine and rasa core running on a Ubuntu.

We already figure this out. Previously postman was a Chrome plugin, I faced this issue. After I installed postman as an independent application, this issue is gone.
The code that causes this issue is actually from rasa_nlu in the file 'rasa_nlu/rasa_nlu/server.py'
def check_cors(f):
    """Wraps a request handler with CORS headers checking."""

    @wraps(f)
    def decorated(*args, **kwargs):
        self = args[0]
        request = args[1]
        origin = request.getHeader('Origin')

        if origin:
            if '*' in self.config['cors_origins']:
                request.setHeader('Access-Control-Allow-Origin', '*')
            elif origin in self.config['cors_origins']:
                request.setHeader('Access-Control-Allow-Origin', origin)
            else:
                request.setResponseCode(403)
                return 'forbidden'

        return f(*args, **kwargs)

    return decorated

When I ran Postman as Chrome extension:

variable 'origin' is not null, the if condition is true.
the 'self' object is actually a RasaCoreServer instance instead of RasaNluServer instance. RasaCoreServer instand has no 'config' attribute, thus the error arises.

When I ran Postman as a independent application:

variable 'origin' is null. If condition is false, error disappears.

Good catch :+1: fixed.


Disable profiling_marker_thunks.swift on arm64e

The test fails because the output is different due to pointer signing
rdar://138114215

@swift-ci smoke test


from joblib: UserWarning: Persisting input arguments took XXX to run.

(dandi-devel) jovyan@jupyter-yarikoptic:/shared/ngffdata$ time dandi digest -d zarr-checksum test64.ngff/0/0/0/

/home/jovyan/fscacher/src/fscacher/cache.py:138: UserWarning: Persisting input arguments took 0.53s to run.
If this happens often in your code, it can cause performance problems
(results will be correct in all cases).
The reason for this is probably some large input arguments for a wrapped
 function (e.g. large strings).
 If you can, kindly provide the joblib's team with an
 example so that they can fix the problem.
  ret = fingerprinted(*args, **kwargs_)
/home/jovyan/fscacher/src/fscacher/cache.py:138: UserWarning: Persisting input arguments took 1.30s to run.
If this happens often in your code, it can cause performance problems
(results will be correct in all cases).
The reason for this is probably some large input arguments for a wrapped
 function (e.g. large strings).
 If you can, kindly provide the joblib's team with an
 example so that they can fix the problem.
  ret = fingerprinted(*args, **kwargs_)
/home/jovyan/fscacher/src/fscacher/cache.py:138: UserWarning: Persisting input arguments took 0.60s to run.
If this happens often in your code, it can cause performance problems
(results will be correct in all cases).
The reason for this is probably some large input arguments for a wrapped
 function (e.g. large strings).
 If you can, kindly provide the joblib's team with an
 example so that they can fix the problem.
  ret = fingerprinted(*args, **kwargs_)
... still running

trying on #67 state of things
jovyan@jupyter-yarikoptic:~/fscacher/src/fscacher$ nl -ba cache.py | grep -3 138
   135                      + fprint.to_tuple()
   136                      + (tuple(self._tokens) if self._tokens else ())
   137                  )
   138                  ret = fingerprinted(*args, **kwargs_)
   139              lgr.log(1, "Returning value %r", ret)
   140              return ret
   141

jovyan@jupyter-yarikoptic:~/fscacher/src/fscacher$ git describe
0.1.6-17-g7ec27c1

jovyan@jupyter-yarikoptic:~/fscacher/src/fscacher$ git branch
* gh-66
  master

and not sure why it took long since all args here should be quite concise afaik (path).  Needs to be investigated on either to be addressed/sped up

it was that dandi digest -d zarr-checksum I was benchmarking on dandi HUB (original description has the path etc).  that zarr does have some number of files on the lowest level.  for a directory are we adding an entire list of files into the "fingerprint" and not some "hash value" of it?

@yarikoptic Yes, the fingerprint for a directory consists of a sorted list of fingerprints of all files within it.

We might avoid such a warning and gain some speed up overall if it would be some hash of that list right away, or even never store a full list of entries (do we use actual entries anywhere) and incrementally hash it as e.g. hash = md5(f'{hash}{file_hash}') starting with a file_hash on first one.  Could be some faster one than md5.  But this might be slower than just hashing full list of entries once -- please check.

so I decided to look for "order independent hash", got to https://stackoverflow.com/questions/30734848/order-independent-hash-algorithm (java oriented)  which pretty much boils down that we can use xor operation (should be quick!) to incrementally grow hash so it would be independent of the order!


[question] zod validation/transform and openApiDoc from zod spec definition

I am trying to use the zod validation in a holistic approach. For this the body should be validated and transformed. And from the same definition the swagger spec should be generated. Currently there are some code places in my project that need to be maintained redundantly (API spec request and response and typescript types of DTOs). I am trying to avoid this by using the zod definition as a single source of truth. I have two questions about this.

I'm validating the request body with zod. This works, but I wonder if there is a way to remove the additional properties already with the validate. Otherwise I can always call zod's parse in the controller function. Then the validate annotation is no added value for me here. Or am I missing something?

import { RequestEvent } from "nhttp";
import { Controller, Post } from "nhttp_controller";
import { Validate, z } from "nhttp_zod";

const User = z.object({
  username: z.string(),
  password: z.string(),
  user_info: z.object({
    name: z.string(),
    address: z.string(),
  }),
}).strip(); // allow additional properties but strip them away

@Controller("/user")
export class TestUserController {
  @Validate(User)
  @Post("/")
  save(rev: RequestEvent) {
    console.log(`created user: ${JSON.stringify(rev.body)}`)
    const user = rev.body;
    // const user = User.parse(rev.body);
    return user;
  }
}

Request with following payload, with only validate, additional properties are not stripped away. With additional parse they are:
{
  "username": "user1",
  "password": "password1",
  "user_info": {
    "name": "User 1",
    "address": "Address 1"
  },
  "ffo": "bar" // this property is not stripped away
}

I also try to generate a swagger spec with nhttp_swagger from the zod definition. That works great (for example with this library @anatine/zod-openapi), but I'm not sure, if and how I can pass the schema down to swagger.
Is there a way to do this? Maybe like this?

import { generateSchema } from "npm:@anatine/zod-openapi";

@ApiRequestBody({
  description: "endpoint for xy",
  required: true,
  schema: generateSchema(User),
})
@GET("/xy")
myFunction() {}

btw: I think there is a problem with the import via default in your example of the lib/zod-validator.ts. It fails with Unable to resolve signature of method decorator when called as an expression.
https://github.com/nhttp/nhttp/blob/e5943f218a8909dbb8da2d41e8516e45a4181d6e/examples/zod-validator.ts
Using it with a named import works as expected.

thanks for asking. rev.body not mutating or does not take values from the schema. i will mutate rev.body in next release for support .strip() or any methods.
this is core middleware in zod-validator:

Before :
...
schema.parse(rev.body};
return next();
...

Next Release :
...
rev.body = schema.parse(rev.body};
return next();
...

In next release, rev.body take value from schema. and support  .strip() or any method.

The schema keys only support class-validator. if prefer custom, please use content.

import { generateSchema } from "npm:@anatine/zod-openapi";

@ApiRequestBody({
  description: "endpoint for xy",
  required: true,
  content: {
     "application/json": {
        schema: generateSchema(User)
     }
  }
})
...

@zingmane now, you can try v1.3.2 zod-validator libs. i update mutate rev.body to support strip or any methods.

Thanks, that is a great improvement.
You're right, I overlooked the capital/lowercase letter.


Fix infinite loop over non-visible elements

Fixes issue where if an element is hidden on the page, react-truncate will infinitely loop calling requestAnimationFrame taking up CPU.
Solution is: If the target's parent isn't visible, don't try to calculate its width.
If there's a better solution, please feel free to comment, adjust commits.
Fixes issue #61

I'm not overly happy with the test as I had to add 'isVisible' to the component for it to test it.
@PabloSichert as you're more familiar with the code, perhaps you know a better way. I haven't used 'unexpected' much before, just enzyme for react testing.

@PabloSichert This was updated to use the current target instead of parent

Is this likely to be merged at all?

@jordie23 can you clarify what do you mean by "hidden on the page" - hidden with css using let's say display: none or just not scrolled to the view?

Hidden with css display: none , for example on a responsive page.

Ok, that was good to know.
I suggest to continue with these steps:

prove the fail case first by adding test for the infinite loop of requestAnimationFrame.
then finish the solution you are proposing.

Are you fine with that approach?


client: use ceph_uid fact to set uid/gid on admin key

That task is failing on containerized deployment because ceph:ceph
doesn't exist.
The idea here is to use the {{ ceph_uid }} to set the ownerships for
the admin keyring when containerized_deployment.
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1540578
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

jenkins test luminous-ansible2.4-xenial_cluster


Upmerge from v1.15.x  branch

This seems to be the only net changes when I upmerge the v1.15.x branch to the master branch after reverting the BUILD and build.yaml changes and re-ran generate_projects.sh.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences


controls not woking

i'm trying to use controls prop but keep getting error

"i used a thing, it didnt work".  Can you actually explain the logic behind giving such little information?  What is the expected response to this?  Is it, "here's a magic code snippet that will fix your extremely vague problem"?


Paket Pack builds bad pakage when specifying relative target path external to package directory.

Paket <IP_ADDRESS> and Paket <IP_ADDRESS>-alpha. Running on Mac.
When I use a target path that is external (and non absolute) to a directory outside of the /packages/group/ directory it results in duplicate files, where the duplicate files are at the wrong path.
I'm using relative paths because I want the install/update for some of my packages to be deployed somewhere other than the packages directory. I know it's an atypical approach but it should still be an approach that is supported.
When I list the files in the package using unzip -l mypackage.1.0.3.nupkg:
Archive:  mypackage.1.0.3.nupkg
  Length     Date   Time    Name
 --------    ----   ----    ----
    16545  02-12-16 17:26   ../../../Assets/Packages/mypackage/Editor/Users/buildcomputer/jenkins/nodes/unitySlave/workspace/<jenkins_job>/Assets/file1.cs   (WRONG!!!)
      262  02-12-16 17:26   ../../../Assets/Packages/mypackage/Editor/Users/buildcomputer/jenkins/nodes/unitySlave/workspace/<jenkins_job>/Assets/file1.cs.meta  (WRONG!!!)
    16545  02-12-16 17:26   ../../../Assets/Packages/mypackage/Editor/file1.cs   (CORRECT)
      262  02-12-16 17:26   ../../../Assets/Packages/mypackage/Editor/file1.cs.meta    (CORRECT)
      533  02-12-16 17:26   mypackage.nuspec
      669  02-12-16 17:26   package/services/metadata/core-properties/coreProp.psmdcp
      489  02-12-16 17:26   _rels/.rels
      541  02-12-16 17:26   [Content_Types].xml
 --------                   -------

A couple things to note:

There are duplicates (file1.cs and file1.cs.meta) show up twice in two different paths. The wrong paths have been denoted above with (WRONG!!!!).
The wrong files seem to contain a near absolute path, but does not actually contain the full path either. Namely, it's missing the "Editor" folder.

My project.template file
type file
copyright My Company 2016
id mypackage
version 1.0.3
authors
    me
projectUrl
    http://mypackage.com
description
    my description
files
    Assets/Editor/** ==> ../../../Assets/Packages/mypackage/Editor/

I can't really reproduce, but please try latest version. I changed something that might be related

globbing in 2.50.7 seems to be somewhat broken:
this is a reproducible case:
https://gist.github.com/flowsprenger/8280a7f0f2cf5f64b8b1
it probably does not cover all cases, i see the paket.template being packaged too in the project i am currently working on, but i don't have a simple reproducible case as of now

We changed pack in 2.50.9 - can you please try with that version?

I did, the output is from 2.50.9. 2.50.6 is the last that works fine.

so I revert 3fcac1d and await a repro from @galaxystar!?

Sounds reasonable to me. Alternatively I can pin Paket's version again, seems we need a mechanism to do this over all our repos anyway.

@flowsprenger please try latest

@forki works again :)

Would be great if you could contribute your repro as an integration test so
that we don't break it again
On Feb 15, 2016 12:00 PM, "Florian Sprenger"<EMAIL_ADDRESS>wrote:

@forki https://github.com/forki works again :)
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/1472#issuecomment-184166739.

@galaxystar since you seem to use unity, maybe its worth having a look at https://github.com/wooga/Paket.Unity3D/ which allows to install using paket.unity3.exe and paket.unity3d.reference files.
@forki alright, shall have a look at how to do that

thx would be of great help

@forki I just tried 2.50.10 with the same (wrong) results. I have a temp work around (using zip -d to remove the files with the erroneous directory). It's not ideal, but it works in the short term for this special case.
@flowsprenger I looked into Paket.Unity3D. It seems to be abandoned. No forks, no changes in 6 months, 5 issues, most of which were unaddressed and their mono build seems to be failing. I'd prefer to stick with vanilla Paket as it seems to do everything I need it to and gives me the flexibility to swap packages in/out as I see fit (such as when switching platforms).

I'm not near a pc for 2 weeks  but if you can come up with a repro I'll try
to address when I'm back.
On Feb 16, 2016 23:22, "galaxystar"<EMAIL_ADDRESS>wrote:

@forki https://github.com/forki I just tried 2.50.10 with the same
(wrong) results. I have a temp work around (using zip -d to remove the
files with the erroneous directory). It's not ideal, but it works in the
short term for this special case.
@flowsprenger https://github.com/flowsprenger I looked into
Paket.Unity3D. It seems to be abandoned. No forks, no changes in 6 months,
5 issues, most of which were unaddressed and their mono build seems to be
failing. I'd prefer to stick with vanilla Paket as it seems to do
everything I need it to and gives me the flexibility to swap packages
in/out as I see fit (such as when switching platforms).
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/1472#issuecomment-184899027.

I just tried with 2.50.10 and it worked locally, but gave me problems on my build machine. I then went through the full installation process for Mac (downloaded repository and installed using the install script) and it worked correctly. I must have had some frankenstein installation through my manual installation process. Thanks for all the help, I really appreciate it!


[Ionic 4.1.1] Scroll state not preserved after back navigation in Firefox

Bug Report
Ionic version:

[x] 4.x
Current behavior:
In Firefox, when navigating back to a previous page, the scroll position is at the top instead of at the position it was before.
Expected behavior:
Scroll position is preserved when navigating back in Firefox (as it is in Chrome).
Steps to reproduce:

git clone https://github.com/pwespi/ion-list-test
cd ion-list-test
npm i
npm run start
open http://localhost:3333/ in Firefox
scroll down, click an item, click back button
scroll position is at top

Related code:
A sample application via GitHub
https://github.com/pwespi/ion-list-test
Other information:

Tested with Firefox 65.0.2 in Windows 10.
Ionic info:

Ionic PWA toolkit project with
"dependencies": {
    "@ionic/core": "4.1.1"
  },
  "devDependencies": {
    "@stencil/core": "0.18.0"
  }

Ionic:

   ionic (Ionic CLI) : 4.10.3

System:

   NodeJS : v10.15.0
   npm    : 6.4.1
   OS     : Windows 10

Thanks for the issue! I am able to reproduce this -- we will look into it. Thanks!


Add testing of FileDBRegistry MERGEOK

Remove PreGeneratedRegistry.
Allow files to not exist after bootstrap.

@hmusum PR

PR builds don't work at the moment


Documentation update

Pull Request Test Coverage Report for Build 413

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.839%

Totals

Change from base Build 408:
0.0%

Covered Lines:
3193

Relevant Lines:
3515

💛  - Coveralls


Admin - store product data in database

Submit product form
Validate product inputs
Save data to database

Product form validation https://github.com/amitsiliguri/ecom/commit/bcba37f01c7856452dace8d2acfaf352ec581e40

https://github.com/amitsiliguri/ecom/commit/4d1a86d621b52e56cfaaee6db54861b1db026feb
TODO :: Product Image Upload

https://github.com/amitsiliguri/ecom/commit/dfd4c343c1b4c41f57a2d6a2c3fab159e897ea3f
Product Image Upload -- Done


More a question than an issue

Hello,
Do you guys know how much time does it get for the website to get updated. For example, i created a new wallet for more than a week and when i launch a search, the wallet is still labelled as "ghost" with 0 erg.
Thanks in advance for any response !

Data is provided by the Ergo Watch API and should show the exact same balance as on the blockchain (realtime).

Do you see the expected (non-zero) blockchain balance when pasting your wallet address in e.g. https://ergoscan.io?
Could you be using a wrong box address? See this explanation about Ergo boxes on the RankMyWallet FAQ page

Hey, thanks for the fast response.
Yes, i do see the correct balance on ergoscan.
I tried to send everything on a new adress i generated but the problem remains the same
(for more context i also have an old wallet, and when i enter the adress, i have an amount that is an old amount, this is why i was thinking to an update that have to be done, maybe the website make some screenshot every x time..)
Weird, can't explain why

Thank you for the additional feedback. I have asked for a sanity check in the Ergo Watch Discord.

Thank you for reporting, there was indeed an issue with the database which should now be fixed.
To see the reason, visit the Discord channel link I pasted above.

Yes , i followed the discussions on Discord and it is now working fine !
Thank you for the follow-up !


Add React 16 to peerDependencies

Currently you get a peer dependency warning if you use React 16 with this library.

This was resolved in this PR: https://github.com/FormidableLabs/redux-little-router/commit/7c97af5f87ae8ede5eee9397eb0d94ad2c1cd6a0#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R127


chore: clean http server module

Stack:

#1443 ⬅
#1425
#1424
#1423
#1422

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is


Disable appcache after enabled it

Due to the way appcache work. It is impossible to disable appcache after enable it. If one remove the appcache configuration in package.json or switch it to falsy value. Browser will try and fail to download the mainfest.appcache. So the website isn't updated. I suggest we add an option to appcache like this:
"appcache: "disabled"

And we will write this to manifest.appcache :
CACHE MANIFEST

NETWORK:
*

Yeah I got the issue while I was playing in dev mode. Pretty annoying.
I was thinking about this indeed. Are you sure this "empty" file will be enough to clean all the cache?
Maybe we should use "disabled" when false? Eg: I use true, remove the value, I will expect to have no cache anymore.

I didn't test this appcache config yet. But if I'm right, we can always write this file to dist folder to disable appcache.

According to this SO answer : http://stackoverflow.com/a/4829472
All we need to do is not produce manifest.appcache anymore. Need to test this

Haha. After 2 refreshes (with manifest deleted and no manifest props in  tags). appcache is gone.

Coo.


Failed to create Statefulset : guid already exists Error

Description
We deployed cf-for-k8s 0.1.0 version and performed scalability tests . We pushed source code based apps and reached till 800 apps. During the course of tests at we could see the below errors.

{"timestamp":"2020-04-24T14:46:28.275329914Z","level":"error","source":"handler","message":"handler.desire-app.bifrost-failed","data":{"error":"failed to desire: failed to create statefulset: statefulsets.apps \"app-2-6-light-2-space-2-dedc6afb16\" already exists","guid":"22875703-d484-48c0-8e35-e9e50f30ca72-25926a2f-476d-4650-b904-a7e45134bdb0","session":"38768"}}
{"timestamp":"2020-04-24T14:46:28.469625717Z","level":"error","source":"handler","message":"handler.desire-app.bifrost-failed","data":{"error":"failed to desire: failed to create statefulset: statefulsets.apps \"app-2-1-light-21-space-2-3ab4ad2579\" already exists","guid":"5d94793f-de02-4294-98e0-fd97db282f87-d6e2c77c-c911-4fb7-9d64-9fb330fba0f4","session":"38769"}}
{"timestamp":"2020-04-24T14:46:28.708660473Z","level":"error","source":"handler","message":"handler.desire-app.bifrost-failed","data":{"error":"failed to desire: failed to create statefulset: statefulsets.apps \"app-2-5-light-15-space-2-85ef1faa94\" already exists","guid":"68558507-37cc-4cc6-81ee-de4585b9120e-d46e4837-f455-47e0-aa66-4a065e47e9e3","session":"38770"}}

We are sure that we didn't push with same appname.
Steps to reproduce
Deploy cf-for-k8s and push source code based apps beyond 500.

Hello @KesavanKing,
This is actually a desired behaviour in Eirini (see here) and not a bug. Long story short, we believe the Cloud Controller is requesting the app twice through the process_sync and the desire_app_handler, so it sounds more like an issue in CAPI.
Best Regards,
@mnitchev && @yulianedyalkova

Hi @KesavanKing,
We actually reconsidered this and decided to make our api idempotent in this regard and not fail when the app is requested a second time. It will just log it when it happens.
Regards,
@mnitchev && @herrjulz


update READMEs

top-level README added
updates to diagnostic-channel README

landed in https://github.com/Microsoft/node-diagnostic-channel/commit/541a77372831a719193234b68430b85a5a1783e2
Thanks!


404 on /1.0/certificates

Required information

Distribution: Ubuntu
Distribution version: Focal + HWE
The output of "lxc info" or if that fails:

Kernel version:
LXC version:
LXD version: 5.1-4ae3604
Storage backend in use: ZFS

Issue description
A brief description of the problem. Should include what you were
attempting to do, what you did, what happened and what you expected to
see happen.
Adding my server as a remote on my local client (Powershell LXD 5.1 installed via choco) the server returns a 404
root @ epyc # lxc config set core.trust_password=QUyLH9mReRueF2k

PS C:\WINDOWS\system32> lxc remote add epyc <IP_ADDRESS> --protocol lxd --password QUyLH9mReRueF2k
Error: not found
PS C:\WINDOWS\system32> lxc remote add epyc <IP_ADDRESS> --protocol lxd --password QUyLH9mReRueF2k
Error: not found
PS C:\WINDOWS\system32> lxc --version
5.1

I executed snap set lxd daemon.debug=true but the logs in journalctl are pretty unreadable as every special character is escaped :(
I replaced ", \t with their respective characters and stripped the \n for your convenience
Also the GET on /1.0 is done twice so I only included it once
May 07 09:33:38 epyc lxd.daemon[1105813]: time="2022-05-07T09:33:38+02:00" level=debug msg="Allowing untrusted GET" ip="<IP_ADDRESS>:58333" url=/1.0
May 07 09:33:38 epyc lxd.daemon[1105813]: time="2022-05-07T09:33:38+02:00" level=debug msg="WriteJSON  {   "type": "sync",   "status": "Success",   "status_code": 200,   "operation": "",   "error_code": 0,   "error": "",   "metadata": {    "api_extensions": [     "storage_zfs_remove_snapshots",     "container_host_shutdown_timeout",     "container_stop_priority",     "container_syscall_filtering",     "auth_pki",     "container_last_used_at",     "etag",     "patch",     "usb_devices",     "https_allowed_credentials",     "image_compression_algorithm",     "directory_manipulation",     "container_cpu_time",     "storage_zfs_use_refquota",     "storage_lvm_mount_options",     "network",     "profile_usedby",     "container_push",     "container_exec_recording",     "certificate_update",     "container_exec_signal_handling",     "gpu_devices",     "container_image_properties",     "migration_progress",     "id_map",     "network_firewall_filtering",     "network_routes",     "storage",     "file_delete",     "file_append",     "network_dhcp_expiry",     "storage_lvm_vg_rename",     "storage_lvm_thinpool_rename",     "network_vlan",     "image_create_aliases",     "container_stateless_copy",     "container_only_migration",     "storage_zfs_clone_copy",     "unix_device_rename",     "storage_lvm_use_thinpool",     "storage_rsync_bwlimit",     "network_vxlan_interface",     "storage_btrfs_mount_options",     "entity_description",     "image_force_refresh",     "storage_lvm_lv_resizing",     "id_map_base",     "file_symlinks",     "container_push_target",     "network_vlan_physical",     "storage_images_delete",     "container_edit_metadata",     "container_snapshot_stateful_migration",     "storage_driver_ceph",     "storage_ceph_user_name",     "resource_limits",     "storage_volatile_initial_source",     "storage_ceph_force_osd_reuse",     "storage_block_filesystem_btrfs",     "resources",     "kernel_limits",     "storage_api_volume_rename",     "macaroon_authentication",     "network_sriov",     "console",     "restrict_devlxd",     "migration_pre_copy",     "infiniband",     "maas_network",     "devlxd_events",     "proxy",     "network_dhcp_gateway",     "file_get_symlink",     "network_leases",     "unix_device_hotplug",     "storage_api_local_volume_handling",     "operation_description",     "clustering",     "event_lifecycle",     "storage_api_remote_volume_handling",     "nvidia_runtime",     "container_mount_propagation",     "container_backup",     "devlxd_images",     "container_local_cross_pool_handling",     "proxy_unix",     "proxy_udp",     "clustering_join",     "proxy_tcp_udp_multi_port_handling",     "network_state",     "proxy_unix_dac_properties",     "container_protection_delete",     "unix_priv_drop",     "pprof_http",     "proxy_haproxy_protocol",     "network_hwaddr",     "proxy_nat",     "network_nat_order",     "container_full",     "candid_authentication",     "backup_compression",     "candid_config",     "nvidia_runtime_config",     "storage_api_volume_snapshots",     "storage_unmapped",     "projects",     "candid_config_key",     "network_vxlan_ttl",     "container_incremental_copy",     "usb_optional_vendorid",     "snapshot_scheduling",     "snapshot_schedule_aliases",     "container_copy_project",     "clustering_server_address",     "clustering_image_replication",     "container_protection_shift",     "snapshot_expiry",     "container_backup_override_pool",     "snapshot_expiry_creation",     "network_leases_location",     "resources_cpu_socket",     "resources_gpu",     "resources_numa",     "kernel_features",     "id_map_current",     "event_location",     "storage_api_remote_volume_snapshots",     "network_nat_address",     "container_nic_routes",     "rbac",     "cluster_internal_copy",     "seccomp_notify",     "lxc_features",     "container_nic_ipvlan",     "network_vlan_sriov",     "storage_cephfs",     "container_nic_ipfilter",     "resources_v2",     "container_exec_user_group_cwd",     "container_syscall_intercept",     "container_disk_shift",     "storage_shifted",     "resources_infiniband",     "daemon_storage",     "instances",     "image_types",     "resources_disk_sata",     "clustering_roles",     "images_expiry",     "resources_network_firmware",     "backup_compression_algorithm",     "ceph_data_pool_name",     "container_syscall_intercept_mount",     "compression_squashfs",     "container_raw_mount",     "container_nic_routed",     "container_syscall_intercept_mount_fuse",     "container_disk_ceph",     "virtual-machines",     "image_profiles",     "clustering_architecture",     "resources_disk_id",     "storage_lvm_stripes",     "vm_boot_priority",     "unix_hotplug_devices",     "api_filtering",     "instance_nic_network",     "clustering_sizing",     "firewall_driver",     "projects_limits",     "container_syscall_intercept_hugetlbfs",     "limits_hugepages",     "container_nic_routed_gateway",     "projects_restrictions",     "custom_volume_snapshot_expiry",     "volume_snapshot_scheduling",     "trust_ca_certificates",     "snapshot_disk_usage",     "clustering_edit_roles",     "container_nic_routed_host_address",     "container_nic_ipvlan_gateway",     "resources_usb_pci",     "resources_cpu_threads_numa",     "resources_cpu_core_die",     "api_os",     "container_nic_routed_host_table",     "container_nic_ipvlan_host_table",     "container_nic_ipvlan_mode",     "resources_system",     "images_push_relay",     "network_dns_search",     "container_nic_routed_limits",     "instance_nic_bridged_vlan",     "network_state_bond_bridge",     "usedby_consistency",     "custom_block_volumes",     "clustering_failure_domains",     "resources_gpu_mdev",     "console_vga_type",     "projects_limits_disk",     "network_type_macvlan",     "network_type_sriov",     "container_syscall_intercept_bpf_devices",     "network_type_ovn",     "projects_networks",     "projects_networks_restricted_uplinks",     "custom_volume_backup",     "backup_override_name",     "storage_rsync_compression",     "network_type_physical",     "network_ovn_external_subnets",     "network_ovn_nat",     "network_ovn_external_routes_remove",     "tpm_device_type",     "storage_zfs_clone_copy_rebase",     "gpu_mdev",     "resources_pci_iommu",     "resources_network_usb",     "resources_disk_address",     "network_physical_ovn_ingress_mode",     "network_ovn_dhcp",     "network_physical_routes_anycast",     "projects_limits_instances",     "network_state_vlan",     "instance_nic_bridged_port_isolation",     "instance_bulk_state_change",     "network_gvrp",     "instance_pool_move",     "gpu_sriov",     "pci_device_type",     "storage_volume_state",     "network_acl",     "migration_stateful",     "disk_state_quota",     "storage_ceph_features",     "projects_compression",     "projects_images_remote_cache_expiry",     "certificate_project",     "network_ovn_acl",     "projects_images_auto_update",     "projects_restricted_cluster_target",     "images_default_architecture",     "network_ovn_acl_defaults",     "gpu_mig",     "project_usage",     "network_bridge_acl",     "warnings",     "projects_restricted_backups_and_snapshots",     "clustering_join_token",     "clustering_description",     "server_trusted_proxy",     "clustering_update_cert",     "storage_api_project",     "server_instance_driver_operational",     "server_supported_storage_drivers",     "event_lifecycle_requestor_address",     "resources_gpu_usb",     "clustering_evacuation",     "network_ovn_nat_address",     "network_bgp",     "network_forward",     "custom_volume_refresh",     "network_counters_errors_dropped",     "metrics",     "image_source_project",     "clustering_config",     "network_peer",     "linux_sysctl",     "network_dns",     "ovn_nic_acceleration",     "certificate_self_renewal",     "instance_project_move",     "storage_volume_project_move",     "cloud_init",     "network_dns_nat",     "database_leader",     "instance_all_projects",     "clustering_groups",     "ceph_rbd_du",     "instance_get_full",     "qemu_metrics",     "gpu_mig_uuid",     "event_project",     "clustering_evacuation_live",     "instance_allow_inconsistent_copy",     "network_state_ovn",     "storage_volume_api_filtering",     "image_restrictions",     "storage_zfs_export",     "network_dns_records",     "storage_zfs_reserve_space",     "network_acl_log",     "storage_zfs_blocksize",     "metrics_cpu_seconds",     "instance_snapshot_never",     "certificate_token",     "instance_nic_routed_neighbor_probe",     "event_hub",     "agent_nic_config",     "projects_restricted_intercept",     "metrics_authentication",     "images_target_project",     "cluster_migration_inconsistent_copy",     "cluster_ovn_chassis",     "container_syscall_intercept_sched_setscheduler",     "storage_lvm_thinpool_metadata_size",     "storage_volume_state_total",     "instance_file_head",     "instances_nic_host_name",     "image_copy_profile",     "container_syscall_intercept_sysinfo",     "clustering_evacuation_mode"    ],    "api_status": "stable",    "api_version": "1.0",    "auth": "untrusted",    "public": false,    "auth_methods": [     "tls"    ]   }  }" http_code=200
May 07 09:33:38 epyc lxd.daemon[1105813]: time="2022-05-07T09:33:38+02:00" level=info msg="Sending top level 404" url=/1.0/certificates
May 07 09:33:38 epyc lxd.daemon[1105813]: time="2022-05-07T09:33:38+02:00" level=debug msg="Error Response  {   "type": "error",   "status": "",   "status_code": 0,   "operation": "",   "error_code": 404,   "error": "not found",   "metadata": null  }" http_code=404

To make sure my LXD install for Windows is not the issue here I created a Focal VM, installed the latest LXD snap and tried to add my server as a remote:
~
root @ lxd1 # snap install lxd --channel=latest
2022-05-07T09:45:54+02:00 INFO Waiting for automatic snapd restart...
lxd 5.1-4ae3604 from Canonical✓ installed

~
root @ lxd1 # lxc remote add epyc <IP_ADDRESS> --protocol lxd --password QUyLH9mReRueF2k
If this is your first time running LXD on this machine, you should also run: lxd init
To start your first container, try: lxc launch ubuntu:22.04
Or for a virtual machine: lxc launch ubuntu:22.04 --vm

Generating a client certificate. This may take a minute...
Certificate fingerprint: 8cce00621d1cfd14ccfad6726183439c6c7ab1315f9e8f9a1db0c3d528b9f3d9
ok (y/n/[fingerprint])? y
Error: not found

Server logs are the same as with my lxd client on windows

[ ] Any relevant kernel output (dmesg)
[ ] Container log (lxc info NAME --show-log)
[ ] Container configuration (lxc config show NAME --expanded)
[x] Main daemon log (at /var/log/lxd/lxd.log or /var/snap/lxd/common/lxd/logs/lxd.log)
[ ] Output of the client with --debug
[ ] Output of the daemon with --debug (alternatively output of lxc monitor while reproducing the issue)

What version is the LXD server running on <IP_ADDRESS>?
Can you go to it locally and run:
lxc query /1.0/certificates

What version is the LXD server running on <IP_ADDRESS>?
Can you go to it locally and run:
lxc query /1.0/certificates

The server on <IP_ADDRESS> runs the latest snap, 5.1-4ae3604. It's an Ubuntu 20.04 server.
~
root @ epyc # lxc query /1.0/certificates
[]

~
root @ epyc # lxc version
Client version: 5.1
Server version: 5.1

~
root @ epyc # snap list
Name    Version      Rev    Tracking       Publisher   Notes
core18  20220309     2344   latest/stable  canonical✓  base
core20  20220329     1434   latest/stable  canonical✓  base
lxd     5.1-4ae3604  23001  latest/stable  canonical✓  -
snapd   2.55.3       15534  latest/stable  canonical✓  snapd

Just to be sure I just rebooted the server but the "Error: Not Found" remains

Can you run remote add with --debug added?

Ha I found the issue!
The HTTPS listener was not configured. I only configured the metrics listener and used :8443 for it...
I changed the metrics to :8444 and added the config for core.https_listener for :8443 and everything works.
Apologies!

That would explain it :)


fix: no pop when it is not at top

Status
READY
Breaking Changes
NO
Description
fix #84 #77
This prevent popping when another modal is on top of flow builder
Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[x] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore
[ ] 🧪 Testing

#89 has been merged to address #84. Can you re-test and let us know if you're still experiencing issues?

Closing for now since I believe this has been addressed.


hide privacy indicator from timeline/GroupItem.svelte

Summary
We are using this component https://github.com/themesberg/flowbite-svelte/blob/main/src/lib/timeline/GroupItem.svelte
however we don't need the privacy indicator (either "private" or "public") and we would like a way to remove it.
Basic example
the indicator does not disappear when the value is undefined or the isPrivate property is missing
isPrivate: undefined,
alternatively, a class name with semantic meaning could be assigned to each sub-component, so that it can be hidden through css
Motivation
despite the component being really useful, the private/public indicator is often unnecessary for many use-cases

I can add isPrivacy prop to control the span block.

great, thanks a lot !


typographix-polytechnique-reports:0.1.5

I am submitting

[ ] a new package
[x] an update for a package

Changelog

Fixed heading spacing which broke with v0.12
Logo is optional for cover page

Thank you for the update :)


Issue with jinja call and endcall syntax with v0.14.0

Describe the bug
sqlfmt error with jinja syntax for start and endcall that used to parse previously.
To Reproduce
Run sql-fmt on the following code:
{% call dbt_unit_testing.mock_ref('some_table') %}
id | foo
1 | 2022
{% endcall %}

Expected behavior
Should not fail to parse
Actual behavior
sqlfmt encountered an error: Encountered closing bracket '{% endcall %}' at position xxx, before matching opening bracket. Context: {% endcall %}

Additional context
Version v0.14.0 appears to break this

And an even more simple example fails as well:
{% call foo() %}
select * from foo
{% endcall %}

ok, I see the problem... I thought in dbt, the call blocks have to be labeled {% call statement(...) %} or {% call noop_statement(...) %} -- it seems the package is creating new jinja macros called mock_ref, etc., and calling those with the call syntax? I actually didn't realize that was possible. Are these equivalent?
{% set args %}
select * from foo
{% endset %}
{{ foo(args) }}

The reason I ask is because for call statement blocks, I know the contents have to be SQL, but for arbitrary set or call blocks, they can be data (as in your original example), so we'd need to skip formatting them entirely

@tconbeer Thanks!  Will look for a new version with this change and try it out...


We need pass Mediaitem inside MyFactory

We need use More conditions inside MyFactory.class
For example in my App we using three kind of urls
1.Normal
2. Custom User agent      //Some urls need pass special user agent
2. Need Authentication    // Some Urls need Login
Right now we  access  only "url" inside MyFactory . We meed access all MediaItem inside MyFactory
ex We need like this
 `  public MusicPlayer createMusicPlayer(@NonNull Context context, @NonNull **MusicItem musicItem**) {
        if(musicItem.type.Contain("useragent1"){
              useragent = "bbbb";
      ]else{
         useragent = "ccc";
     }
     if(musicItem.type.Contain("needlogin"){
          we can use okhttp authentication

May be we can use "extra" for or we need "Type"  and "Categories " for inside model.. I Bellevue you understand

@webwayscript This method has been refactored:
public MusicPlayer createMusicPlayer(
   @NonNull Context context,
   @NonNull MusicItem musicItem,
   @NonNull Uri uri
)

Thank you Bro its working all fine now .. Thank you


Default firewall blocks guest-to-guest communication in libvirt

Describe the bug
Default firewall rules block guest-to-guest communication in libvirt.
I'm not sure if that behaviour is intended as I don't understand rpfilter. But I don't think nixos's firewall should behave like this by default. Because of that anyone trying to use guest-to-guest communication would have to spend some time debugging, or, hopefully, they find this issue.
Steps To Reproduce
Just enabling networking.firewall.enable = true.
To fully reproduce you would need to create 2 VMs using virsh/virt-manager and bridge network without NAT. Add both VMs to the network, configure interfaces on both, and test connection with ping.
I can add more step-by-step instructions if that's needed.
Additional context
The culprit is networking.firewall.checkReversePath setting it to "loose" resolves the problem.
It's the same with iptables and nftables.
Metadata
install: cannot remove '/tmp/env-vars': Operation not permitted
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.60-hardened1, NixOS, 24.05 (Uakari), 24.05.6668.e8c38b73aeb2`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.8`
 - channels(nix): `""`
 - channels(root): `"home-manager-24.05.tar.gz, home-manager-unstable, nixos-24.05, nixos-hardware, nixos-unstable, nur, plasma-manager-5-5.tar.gz"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Notify maintainers
@duament

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

I would guess that the reverse path filter should only apply to packets on input/output chains and it shouldn't drop forwarded packets.


Add ETCD_UNSUPPORTED_ARCH environment variable

Added the ETCD_UNSUPPORTED_ARCH environment variable so that the etcd container will run.  Without this was getting an error in the etcd container log:
{"log":"2016-04-16 21:35:35.095147 E | etcdmain: etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=arm set.\n","stream":"stderr","time":"2016-04-16T21:35:35.101447739Z"}

Thanks @watkinspd


SDK: Need SDK "submit TX" functionality to be decoupled for use with Ledger app (TX signing)

UPDATE This is addressed by https://github.com/anoma/namada/pull/1498 and is currently in testing
In order to utilize the signing feature of the Ledger Namada app, we would need to be able to sign a transaction outside of the SDK for these accounts, as private keys stay within the context of the Ledger device.
If we were to split the current SDK submit transaction functionality into the following steps, we could utilize the signing provided in the Ledger app, and still use the SDK to submit the transaction:

Prepare transaction data (the data to be signed)
Sign Tx (either use Namada SDK or Ledger Namada app)
Submit Tx

Note This blocks issue #253 (only on the issue of signing with the hardware wallet)

Closing this, as this has been completed!


Use disabled variation tag in playlist.xml

Signed-off-by: renfeiw<EMAIL_ADDRESS>

tested internally: /Grinder_TKG/831, /Grinder_TKG/832(disabled target)


Is downloading videos in multiple smaller files possible?

Checklist

[x] I'm asking a question
[x] I've looked through the README and FAQ for similar questions
[ ] I've searched the bugtracker for similar questions including closed ones

Question

I'm using youtube-dl for downloading twitch VODs and editing them into highlights. The problem is working with very lengthy videos (up to 8 hours) considering limitations on editing softwares, which don't allow to put the entire multiple hour video at the same time. Would it be possible for videos to be saved in segments, either by their size or length? I'm sorry if the answer to the question is somewhere in the documentation, I tried looking through it but it was confusing at times, I might've just missed it.

youtube-dl -v "https://www.twitch.tv/videos/xxx" --hls-prefer-ffmpeg --external-downloader-args "-ss 00:30:00 -to 00:40:00"
this example only downloads between 30 to 40 minutes. change the values to accordingly.

Had to install ffmpeg but it seems to be working now, thanks!

@ItsGrinn FFmpeg is useful for lots of stuff, not only with youtube-dl.

If you try your method on twitter youtube, it will be downloaded completely. I only know that you can use the youtube-dl - g parameter to download the specified time period on YouTube


Data Currency Info

Consider adding a "data current as of" element to the widget. Maybe this is a hover over item or maybe it goes at the bottom in small text, or maybe there isn't really room and we should do it else where on the pages that use this widget. It's something that we should ideally have on most of our pages so a standard approach would be good to aim for.

Is there an AGOL item/feature layer that I could get this date from dynamically?

One approach might be to pull the most recent last_edited_date from any of the datasets in the web map. This column automatically updates when I update and publish the source data.


Host functions called from another host function cannot know the right MemoryInstance

In the current implementation, host functions try to get the MemoryInstance of HostFunctionCallContext from <function>.ModuleInstance.Memory of the parent stack's (in interpreter) or of the function itself (in jit).
However, a host function doesn't have associated MemoryInstance nor wasm modules in the first place. So, a host function only finds nil as MemoryInstance when it's called from another host function.
FYI, it looks wasmtime also doesn't provide the access to memory instances when a host function is called from another host function because there's no caller context in that case, but let me check.
https://github.com/tetratelabs/wazero/blob/a6cd1549ba093e35d09fe07cd1a049b70e798185/wasm/interpreter/interpreter.go#L516
https://github.com/tetratelabs/wazero/blob/a6cd1549ba093e35d09fe07cd1a049b70e798185/wasm/jit/engine.go#L390
This also prevents the WASI implementation from testing APIs by "import-and-exported-back" style, where tests call each WASI API by having a wasm module import a WASI API and re-export it to the host.

I was thinking in the PR maybe we can default to a zero length constant Memory or initialize an empty one if we are afraid some code might mutate it.
zero := uint32(0)
noMemory := &MemoryInstance{Min: 0, Max: &zero, Buffer: []byte{}}

Meanwhile these safety issues keep coming up which casts doubt on the idea that exposing the memory buffer directly is a good idea. At some point we may want to use an interface to centralize all the bug handling and make it less easy to make them

I think this is something unspecified so I just passes the memory instance from the module on this host function is initialized currently if it is directly called by other host funcs, but year we should check how other runtimes do..

for this one, please use the available memory (if someone forgot to add a memory, we can treat nil as zero max). I don't think there's a reasonable alternative as WebAssembly 1.0 (MVP) can have at most 1 memory. If we later find some new information, we can revise, but meanwhile not crash


Cant save when starting with webhook

I have tried to testing the Webhook-Parameter. When I start with the webhook parameter, I cannot save the task. I always seem to have to use "StartAction". Then the saving works. However, I understand that the webhook call should work without this function, right?
Example:
https://i.imgur.com/4vp4iRi.png

To use the Webhook trigger, you need to set Activated Triggers to true on the side menu. You can keep the StartAction unconnected.

Okay, you have to know that. Are there cases where this is not needed? Otherwise, from the user's point of view, it would make the most sense to prevent the deletion of the StartAction.
At the very least, I would expect an error message: "Your task is faulty and therefore cannot be saved.
Currently nothing happens. Which is a little unsettling.

I agree, will look into a solution for this.


Use this in a plugin/shortcode?

Hi,
Been reading up on this plugin and I like what I see. As with most of these template engines, the documentation seems to focus mainly on usage within themes (I might have missed something).
I'm creating a plugin which I'd like to make a little more maintainable. It uses the Facebook Graph API and fetches events from a Facebook page and makes them available in a shortcode: [events].
Using HTML in a PHP string is never going to look pretty, so I'd like to use Twig/Timber to separate code from the view in this shortcode. Is that possible using this plugin?
This is my current code for the shortcode:
function fevents($atts ){
	global $fbevents; // This is the Facebook Graph Object
	$output = get_transient('cstfbevents'); // Transient cache get
	$output = "
";
	foreach($fbevents->getProperty('data')->asArray() as $single){
		$output .= "
";
		$basetime = strtotime($single->start_time);
		$carbontime = Carbon::createFromTimeStamp($basetime, 'Europe/Amsterdam');
		//$output .= "photos->data[0]->icon."\"/>";
		//if(isset($single->cover->source)){ 	$output .= "cover->source}');\">";
		//$output .= "
".$single->cover->offset_x."
"; $output .= $single->cover->offset_y;}
		$output .= "
".$single->name."
";
		if(isset($single->description)){ 	$output .= "".$single->description.""; }
		//$output .= "".$single->start_time."";
		$output .= "<time>{$carbontime}</time>";
		$output .= "
";
	}
	$output .= "
";
	set_transient('cstfbevents', $output, HOUR_IN_SECONDS); // Set transient cache

	return $output;
}
add_shortcode( 'events', 'fevents' );

Thanks in advance!

It's really simple to use Timber in plugins.  Here is a shortcode plugin i made earlier this week:
function events_feed(){
$context = Timber::get_context();
$events = get_posts(array(
'post_type'		=> 'event',
'posts_per_page'=> 3,
'meta_key'		=> 'event_date',
'orderby'		=> 'meta_value_num',
'order'			=> 'ASC'
));
foreach ($events as $event){
	$context['events'][] = new TimberPost($event->ID);
}
Timber::render('_events.twig', $context);

}
add_shortcode('events_feed', 'events_feed');
You can see a more comprehensive plugin here:
https://github.com/asecondwill/Flexible-Content-Widget
I've just realised they both output, rather than return the html.  not sure that is ideal.

Thanks! And echoing is something I want to avoid, so I may have to look into that. Perhaps there's a way to render the output inside a variable? Then you can output it. I think Blade allows you to do that. By the way, transient caching (a wonderful set of functions I only discovered two days ago in WP) should work fine, right? :)

You can use Timber::compile() to save the rendered twig output to a variable
https://github.com/jarednova/timber/wiki/Timber-docs#compile

thanks for pointing that out @anugupta
@jorenmartijn  -  you good on this now? might be worth closing to keep the tickets down for Jared.

It seems simple enough. Haven't been able to try it out yet, but I'll do that asap. So yes, it can be closed. Let me have a look at how to close this...

closes #565


Helsinki oppii finalization and localization.

Minor changes and improvements all over the site and localization of static content to english, swedish and finnish.

Merging for tests.


Update test.yml

name: Tests
on: [push]
jobs:
phpunit:
name: PHPUnit
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- uses: nathanheffley/laravel-phpunit-action@master


Suppress advantage gain for first Dual Wielder hit

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have run linting on my code to follow the follow the style of this project.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generate no new unhandled or unexpected warnings.

Related Issue(s)
Fixes or addresses #issue(s): #205
Description
Motivation and context
Characters usng the Dual Wielder talent gain advantage for a successful first strike. This should only be gained when the second strike has been succesfully resolved.
Summary of changes

Added new guards for checking against Winning and Outmanouvring advantage scenarios, as the Dual Wielder talent can be applied to melee and ranged attacks.
The WFRP4e system on Foundry does flag the first Dual Wielder attack, but not the second offhand attack. As the second is manually targeted and resolved if the first is successful, this implementation works by ignoring the Dual Wielding strike for advantage purposes, and treating any subsequent as any regular attack.
If the second offhand attack is not successful, then both hits will not have been, so no advantage is gained.
If it is successful, then advantage is gained as normal
This is treated the same whether using group or personal advantage.

Development / Testing Environment

Foundry VTT: v10.291
WFRP4e System: 6.22
GM Toolkit:  dev:1f85c56

The WFRP4e system on Foundry does flag the first Dual Wielder attack, but not the second offhand attack.

Actually, this isn't quite true. In the second attack:

preData.dualWielding === false
preData.options.offhand === true

Parking this here for future reference in case this needs to change, but for now the current implementation works so I'm not going to explicitly check for offhand.


fix: improve help formatting

Codecov Report
Attention: Patch coverage is 99.15254% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 98.97%. Comparing base (d165d33) to head (4a5e36a).

Files
Patch %
Lines

src/help.ts
98.86%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #69      +/-   ##
==========================================
+ Coverage   98.47%   98.97%   +0.49%
==========================================
  Files           7        7
  Lines         262      292      +30
  Branches       74       81       +7
==========================================
+ Hits          258      289      +31
+ Misses          4        3       -1

Flag
Coverage Δ

unittests
98.97% <99.15%> (+0.49%)
:arrow_up:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Moderator update

I added moderator rules for our chats and our personal group overall

perma link would not work if i merge it, /moderation/rules_zoominguess/, please copy that exactly onto your perma link and commit, and re-pull request


Integer failure error can be improved

Hello again, just logging here a potential improvement of the error message for s.spec.number.
I have:
const school = s.spec.map("schoolSpec", {
   city: s.string
});
const friend = s.spec.map("friendSpec", {
   name: s.spec.string,
   age: s.spec.number,
   school
});

and (using the new js-spec-chai:
it("test", () => {
  const obj = {
    name: "andrea",
    age: "18",
    school: {
      city: "Turin",
    }
  };
  obj.should.conform(friend);
})

I receive AssertionError: friendSpec → i: i failed for 18 at [age]. which could be improved to AssertionError: friendSpec → age: s.spec.number failed for 18 at [age]. for instance.

Interesting, I was under the impression it should read one of isInteger, int or integer instead of i. Looks like I should test my getName properly 😅
Thanks for reporting!

How about this error message @arichiardi? Doesn't PR #54 fix this one too?


cleanup event message for broker retry

in #2280 I cleaned up some of the verbose logging messages in the broker operation retry.  I inadvertently changed one of the messages that gets set on the instance event to include some additional debug context.
from kubectl describe serviceinstance test-service output:
Warning  RetryBackoff              0s                 service-catalog-controller-manager  BrokerOpRetry: Delaying update retry, next attempt will be after 2018-08-16 21:08:17.390164084 +0000 UTC m=+108.839431041
This removes the word "BrokerOpRetry: " from the event message.

@MHBauer its removed from the event message.  It is still in the log as intended.

this makes it easies to grep and grock:
 kubectl logs -l app=catalog-catalog-controller-manager -n catalog | grep BrokerOpRetry

Isn't the log the same either way?

/approve


feat: add playground

Describe your changes
Introduce a playground where users can interact with code and look at live demos. The idea is to introduce playground initially and later maybe convert it into a challenge ground, like we have in reactdev
what is Playground?

A final code of the accessibility best practice that is described throughout the pattern template. This allows the user to interact with code, see the output, and open the code in codesandbox.

There are 4-5 options available to embed editor, I have listed them here.
I am currently using sandpack-react. An open source, well-documented library with a lot of functionality out of the box.
I have tried out this in the form component. Need opinion and corrections to improve.
Screenshots
https://github.com/user-attachments/assets/f4c6e5d7-794f-4eea-8b71-de1861a3955b

Link to issue
Closes # issue-403
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] Followed the repository's Contributing Guidelines.
[x] I ran the app and tested it locally to verify that it works as expected.
[x] I have checked my code with an automatic accessibility tool such as Axe Dev Tools or Wave
and it shows no errors.

Some nice work so far. Things I'm concerned about:

The current colours in the sandbox do not meet colour contrast thresholds of 4.5:1. Is there a way to update the theme to find one that has good colour contrast and also matches the current site theme in light/dark mode?
The component is not keyboard accessible meaning anyone using a keyboard is unable to edit the code. Is there something that can be done about this?
How does it work with JS?
I tried making edits to the code and nothing happened. Then after about 3 minutes the preview crashed. I would expect if it was an interactive playground that any edits I make would be reflected in place without me having to go to open the sandbox in full.

Hey @EmmaDawsonDev 👋
(Answering to above points according to their numbers)

Yes, There are themes available. Here is the link to theme. Can you please help me here to select the one that suits site theme and matches color contrast thresholds?

I will check and come back on keyboard accessibility of editor.

This supports vanilla js and all framework of js. You need to pass the required template to SandPack or SandpackProvider like

  <SandpackProvider template="react">
    <SandpackLayout>
      <SandpackPreview />
      <SandpackCodeEditor />
    </SandpackLayout>
  </SandpackProvider>

Replace the react with the template you require. More about templates.

Can you please provide more details on error (screen shot of error), the node, yarn version? also screen recording ? So I can reproduce. As you can see in above video it worked well for me 😬

Some nice work so far. Things I'm concerned about:

The current colours in the sandbox do not meet colour contrast thresholds of 4.5:1. Is there a way to update the theme to find one that has good colour contrast and also matches the current site theme in light/dark mode?
The component is not keyboard accessible meaning anyone using a keyboard is unable to edit the code. Is there something that can be done about this?
How does it work with JS?
I tried making edits to the code and nothing happened. Then after about 3 minutes the preview crashed. I would expect if it was an interactive playground that any edits I make would be reflected in place without me having to go to open the sandbox in full.

Hey @EmmaDawsonDev 👋
(Answering to above points according to their numbers)

Yes, There are themes available. Here is the link to theme. Can you please help me here to select the one that suits site theme and matches color contrast thresholds?
I will check and come back on keyboard accessibility of editor.
This supports vanilla js and all framework of js. You need to pass the required template to SandPack or SandpackProvider like

  <SandpackProvider template="react">
    <SandpackLayout>
      <SandpackPreview />
      <SandpackCodeEditor />
    </SandpackLayout>
  </SandpackProvider>

Replace the react with the template you require. More about templates.

Can you please provide more details on error (screen shot of error), the node, yarn version? also screen recording ? So I can reproduce. As you can see in above video it worked well for me 😬

reported accessibility issue in sandpack https://github.com/codesandbox/sandpack/issues/1173

I have noticed few things here,

for voice-over that reads all the tags, the editor is available, and it's possible to edit the code.
The top buttons have the role of tab. But they do not follow the tab accessibility pattern.
I guess you might have missed, editor is accessible via the tab, when focused, you need to explicitly click on enter key to activate it and esc key to come out of it

Solving editor accessibility here https://github.com/codesandbox/sandpack/pull/1184

Apologies for not getting to this very quickly! I've just started a new job so I've been a bit overwhelmed with new information and will also be away quite a bit in the next couple of weeks travelling.

Here's a screenshot of the sandbox when I open it. My system is set automatically to lightmode but the sandbox doesn't seem to change even when I switch the page to darkmode. The html tags in green are too light and the grey icons/text on the grey buttons don't have enough contrast either

Hey @Yoggie9477 ,  please don't merge this PR, I have a few things to take care. I will resume work from 2nd week of October .

I want to thank you so much for your work on this and apologise for being so slow to get back to you. This does look promising but for ease of maintenance just now I think it would be easier to go with embedded codepens.


Changing playspace from couch to roomscale causes steamvr to restart

When i leave my couch playpace, and change it to roomscale, alvr restarts, causing steamvr to restart as well.
I dont think this is intended behaviour.
ALVR version 19
Steamvr version 1.24.6
Meta Quest 2
OS: windows 11 pro 22H2
CPU: Ryzen 5 5600x
RAM: 16gb 3200mts
GPU: GTX 1080

Having a similar correlated issue: turning off passthrough restarts ALVR and SteamVR, similarly to what's happening here.


Crash when previewing compute in scenario editor when not using non-fail scenario

The Scenario editor will also throw an exception when previewing compute without non-fail scenario selected. In this case it appears to be because the simulation creator in line 538 of the SpecificIASEditorVM class is passed NonFailureSelectedStageDamage, when in this use case it is null (the exception is thrown on line 536). A fix for this at least may be to test if this value is null before attempting to pull the aggregated stage damage element from it and pass it to the simulation creator.

@AlexRyanUSACE I am not able to replicate this issue - neither in debug nor release. Working off of latest, I published a build and can successfully preview the compute.

This only happens immediately after creating a new Scenario. After saving the new scenario, closing the editor, and re-opening, preview compute works as expected.
@Brennan1994 does this ring any bells for you?

I am following a trail. I don't think that non-fail scenario stuff has been completely hooked up between the IASEditorVM and the SpecificIASEditorVM. I think that this property should probably have at least one reference!

why, upon creating a new scenario, should we expect that a non fail stage damage function exists??

it seems that somewhere we are creating a dummy simulation upon creating a new scenario and we forgot to add non fail stage damage to that dummy


Use registry hostname in clone

Something like dat clone datarchive.org/joe/dataset. need the registry hostname in there somewhere

We have dat.land hardcoded in there right now so we should change it and just do this at the same time.

cool it'll be datproject.org/joe/dataset


10.12.4 iso still results in errors on install ISO bootup

Have you had any success using this script with 10.12.4? The README suggests you have, however when I tested it, I still end up with the IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0 error.
If you were able to get a working ISO, where there any special actions you had to do for it to work?

I've tested the script with VMware Fusion 8.5.x and ESXi 6.5.x, and in both cases, both 10.12.4 and 10.12.5 installers worked. Are you using another virtualization solution?

I've been using VirtualBox running on a Windows Host. I did finally get this to work, but it only worked on El Capitan and I have not been able to get it to update to Sierra or later.