You must provide config details in order to use Whatsapi Registration Tool

I try to register my phone number. And I have whatsapi.php in config directory ..
But
UnexpectedValueException in WhatsapiTool.php line 17: You must provide config details in order to use Whatsapi Registration Tool
in WhatsapiTool.php line 17
at WhatsapiTool::create()
at forward_static_call_array(array('Xaamin\Whatsapi\Facades\Native\WhatsapiTool', 'create'), array()) in Facade.php line 23
at Facade::instance() in Facade.php line 40
at Facade::__callStatic('requestCode', array('770********1', 'sms')) in RegisterController.php line 20
at RegisterController->requestCode()
at call_user_func_array(array(object(RegisterController), 'requestCode'), array()) in Controller.php line 80

Are you using Laravel? If yes then see documentation to puclish config files.
If not, you need to read documentation for non laravel users
Configuration
Non Laravel users
If you're using another Framework, different from Laravel, you must put manually the config file Config/config.php on the right path.
    // Include the composer autoload file
    include_once "vendor/autoload.php";

    // Import the necessary classes
    use Xaamin\Whatsapi\Facades\Native\Whatsapi;
    use Xaamin\Whatsapi\Facades\Native\Registration;

    // Or, if you want you can add a class alias
    // class_alias('Xaamin\Whatsapi\Facades\Native\Whatsapi', 'Whatsapi');
    // class_alias('Xaamin\Whatsapi\Facades\Native\Registration', 'Registration');

Now, we tell Whatsapi about the config values.
    // Of course, you can use the Config class from your favorite Framework.
    $config = __DIR__ . 'config/whatsapi.php';

    Whatsapi::setConfig($config);

Yes, I am using laravel. And I have already published a config file:
php artisan vendor:publish --provider="Xaamin\Whatsapi\WhatsapiServiceProvider" --tag="config"
But I have same problem.

I am using Laravel 5.2

Can you put here some code? The block code where you are registering the phone number and the use statements at the top of your controller.

I found out what the problem is. I changed
use Xaamin\Whatsapi\Facades\Native\WhatsapiTool;
to
use WhatsapiTool
Thank you. I've already sent a message via WhatsApp
PS Sorry for my English

No problem. I'm learning english as well.

I had this problem too but after setting it to use WhatsapiTool i get [status] => fail [reason] => old_version
please help

I had this problem too but after setting it to use WhatsapiTool i get [status] => fail [reason] => old_version
please help


Mainnet Release v2.1.0 Kṛttikā

🧱  New Raiden Light Client SDK, dApp and CLI

INFO: The Light Client SDK, CLI and dApp are all work in progress projects. All three projects have been released for mainnet and all code is available in the Light Client repository. As this release still has its limitations and is a beta release, it is crucial to read this readme including the security notes carefully before using the software.

This new version adds a feature to the dApp that protects the user from loading temporary updates unintentionally. Besides the side effect of loading a different version temporary it is important that users always confirm updates and manually trigger the installation of a new version. Unintended updates can for example happen on a force-reload of of the web-browser. For more information, refer to the notes from the v2.0.0 release.
Raiden dApp
Added

[#3024] Prevent the usage of uninstalled versions

@andrevmatos feel free to edit the test how ever you like.

We need to rebase once #3028 got merged. The end-to-end tests should then run also with the bumped version here.

For the protocol: the end-to-end tests work locally. We suffer from some flakyness here that is not related to our changes. Andres can explain it better.

Workflow succeeded! CircleCI hangs due to some parallel and canceled jobs.


DWC Business Builder

@cheg7 There are no files in your PR. What did you change?

@cheg7 There are no files in your PR. What did you change?

Hi @MichaelCzcz , I had added metadata to the tutorials as suggested by Daniel. It seems like we need actual changes in the file to be able to compare the changes. I now have modified something in each file and have 7 changes. Request you to merge it to production.
Thank you!


Distinct in and out transitions are not recognized

I've come across something that feels like a bug to me.
When I try to define distinct slide-in and slide-out transitions, they seem not to be recognized and instead the default, defined in PITCHME.yaml, is used.
Specifically:

The PITCHME.yaml file defines the default transition to be transition: fade
:ok: Slides with no specific @transition shortcut use the default
:ok: Slides with a single @transition[transition-type] use this for their slide-in and slide-out transition as expected
:x: Slides with distinct slide-in and slide-out transitions like @transition[transition-type transition-type] use the default for both which is not what I would expect from the docs

Sample slide show:
https://github.com/ElpyDE/gitpitch-transitions/ (View with GitPitch)
Additional observation
If I leave the PITCHME.yaml empty, the behavior gets even more erratic. Some slides then use the default slide transition and others fade. See branch no-default or View with GitPitch. This branch is otherwise equal.
Related issues
The only related bug seems to be #196 where the slide-in and slide-out transitions are mentioned and seem to work.

PS: This bug aside... THANK YOU for GitPitch... it's really awesome!

Hi @ElpyDE I believe I'm the culprit here. Or at least my current documentation is misleading. If you are specifying distinct in and out transitions for your slides then I believe you are going to have to postfix an -in or an -out to the stand transition names.
For example, if you plan for a slide to zoom in and to convex out then the transition names you will need to use are zoom-in and convex-out respectively.

Can you please try this approach within your sample presentation and let me know if the behavior of your slides is now as expected?

That was it...
See here with your changes: https://gitpitch.com/ElpyDE/gitpitch-transitions/master
Thank you!

FYI, the transition docs have been updated to more clearly explain proper usage of slide-in and slide-out transitions.


Corrupt compression package

Hi, why after I downloaded the compressed package of "one2one" from "Getting the CVPR 2021 NTIRE data (with depth maps)" here, when I decompressed "Train", I was prompted that the compressed file was damaged.

Do you get any solution? We hit the same problem.

yes, the same issue. The package is corrupted and only part of the data could be achieved

I just ran into the same issue, even though the data never changed. The issue is likely coming from the hosting, an issue was resolved over a year ago but there seems to be something else again.
You can reach the support team of the hosting platform here: EPFL IC IT, email<EMAIL_ADDRESS>Connected lab at EPFL: IVRL
Hope the team will be able to sort it out for you quickly!

same issue


Mistake in prompt on purpose?

I just wanted to ask if the wrong double braces "}}" in the prompt are intentional? (In line 26)
"edges": [
        { "from": 1, "to": 2, "label": "roommate" }},
      ]

https://github.com/varunshenoy/GraphGPT/blob/main/public/prompts/main.prompt#L26

Fixed in #16. Thanks for the catch!


How to declare independent functions in schema.yaml

I notice that schema.yaml seems to only support methods that belong to a class object, and the examples do the same.
I wonder how to declare a function which is not any class obj's element in the schema.yaml file.

Hi, take a look at the iowow example: https://github.com/hgarrereyn/GraphFuzz/blob/master/experiments/iowow/in/f1/schema.yaml
Its a bit tricker to infer the usage automatically, so you need to define a custom template that describes what to do with the inputs.
If you have a particular use case / problem, I'd be happy to take a look!

Thanks for your example. It seems that when declaring independent functions, it is not done merely by modifying the YAML file. Instead, it involves using the gfuzz gen cpp ./schema.yaml . command to generate the fuzz_exec.cpp file and then further manually modifying it to implement the functions. Is that correct?

I am trying to adapt GraphFuzz to  cJSON

You can do everything inside the yaml file. Do you have an example of a function you want to add?


Improve example in README

This pr improve for

Change OMISE_KEY to OMISE_SECRET_KEY
Change OMISE_PUBKEY to OMISE_PUBLIC_KEY
Move OMISE_PUBLIC_KEY and OMISE_SECRET_KEY to const and set
sample key for easy to find in Omise web.

Thanks for the PR! I've rolled this into 59fca1f72bdd37a62c0b443729e42302f79ede55 and made the example actually go run-nable in the process.


Week 18 Review Issue

CPT Scoring 2

No hack work?  Makes me question what you are doing with time.

Table on grading does not work.  This is showing lack of quality and concern for performance.
No hacks?


Stand-alone Jar is fubar

I've been meaning to report this ever since 2.x came out, with the switch to javafx and webviews.  As it were, you could just grab the nightcode release .jar and run it no problem.  This was (is?) a great feature, since newbs and /or folks in restricted environs could get a decent clojure environment if they only had a JRE installed.  Ever since the switch to 2.x, the editor works great, but run-with-repl using the uberjar launch setup I mentioned has just fundamentally been broken.  Earlier, the repl would just stall out and become non-responsive after evaluating one or two simple forms (like (+ 2 3)).  More recently, I just tried loading a project to revisit NC using 2.3.7, and I get a slew of errors in the repl.
To recreate the problem, I started the jar like a newb would (2x click from Windows 10 /w java 1.8 installed), started a new project called "crashtest", then RunWithRepl.  It compiled the core ns, then got me into the repl.  At which point, I entered (+ 2 3) and pressed enter to eval....
The output from the repl is here
Highly interesting: if I run with the distributed .exe nightcode installer, I can't reproduce this problem!  Unfortunately, my use case precludes using the installer, but allows the uberjar....

I wasn't able to recreate this. I even fired up a Windows 10 VM and ran the jar the same way, and the REPL behaved normally. It looks like the REPL is trying to evaluate the text that Nightcode is printing to standard output. Weird! I will try to think of what could cause this, but it'll be hard to do a fix until I can recreate the issue.

That's befuddling.  I'll try more things to see if I can provide additional forensics on my end.  Note:  the uber-jar problem occurred on windows 7 as well; in that case it manifested as the eventually-dead REPL (probably a similar error wasn't bubbling up to the REPL output....).  Of note:  when I'm encountering issues, I'm not running on a VM (not sure if / why that would effect things; but it's an independent variable...).

Here's another datapoint [may not be relevant].  Using 'boot run' I get into NC, then run with repl, NC tells me there's no class "nightcode.core", and in the console I get this.

build.boot appears to succeed, then produces a jar that can't be launched  .

So, I created a commensurate  lein profile to see if boot was doing something unseemly.  Lein builds the uberjar (and launches) no problem.  Lein repl works fine too.  Except the REPL issue is still there.  As I mess around with it more, it "looks" like the output that should be emitted as a log (i.,e. running with repl, and later on error traces) are being redirected as input to the REPL's input stream.

Current guess is that the line 90 of builders.clj, in the event handler for "onEnter", we might be pushing unintentional text to the pipe.  Checking it out...

Looks like I was right....
Check out this commit to see what I did.  I'm thinking about work-arounds for this particular problem (like filtering the text coming from the pipe), but I'm still getting oriented.  Perhaps someone else has ideas?

The console works by internally storing the start position, which is how many characters from the beginning the prompt is. The only way the behavior you're experiencing could occur is if that value remained 0 instead of being updated properly.
All REPL output (including lein's preamble) is added to the pane via the append-text! function, which eventually calls update-console-start! with the new start position. I'll have to think about this...there must be some reason it is not updating with the correct start position.

After looking through paren-soup, and the associated calls for creating and initializing the console (editor), I'm not seeing where the console history is ever initialized to anything beyond 0.  That fits the current circumstances (if console start is 0, then everything is read on the call to enter! from the editor).....
Note: using 'reload-selection' (can't find eval....and having trouble finding the keyboard shortcut for eval..) works fine.  Looking at the source, it makes sense, since it manually invokes the .onenter method from the bridge, and pushes in text that's pre-conditioned to work with a console-history at 0....
Subsequently trying to use the REPL goes back to the old (zeroed?) console start....which reverts to the compilation errors as the console tries to eval the preamble and repl-header...

See the reset-console-start! function, called at the end of append-text! via reset-console-history!.

Edited my previous comment with the correct function name.

I'm tracking now.  So you setup a pipes from clj/java->js  via (clj) nightcode.builders/pipe-into-console!, which - via a thread polling at 100ms intervals - invokes (cljs) nightcode.paren-soup/append on valid reads, which in turn invokes paren-soup/append-text! on the editor.  This should be causing updates to the console editor start as we go along.  So somewhere in that chain of causality, the editor is not realizing (or being initialized) that the console start has progressed beyond 0.  Is this looking like the right trail?   In other words, if things are working properly, I should be able to interrogate the console via some call to .executeScript on the webview, to scrape out the current value of :start on the console, and it should be positive after the repl is initialized?

That's right. Unfortunately this is quite hard to debug. I suppose you'd have to clone paren-soup, add a (.log js/console ...) call somewhere to log that value, run boot local in paren-soup to install it locally, change the paren-soup version in Nightcode's build.boot to match it, uncomment this line so a Firebug pane appears inside all editor/console panes, and run boot build-cljs in Nightcode, then finally build the new jar using the mechanism you came up with. Oy! 😓 Theoretically, the resulting copy of Nightcode would display a little Firebug pane in the console (you'll definitely need to resize it to see the console itself) and then you should see your console.log calls. Not sure if you wanted to get this deeply into it, but I figured I'd try figuring out a debugging technique here.

I actually don't mind going down that route.  If you're around for a bit in near-realtime, and don't mind getting on #clojure on IRC freenode.net, I'd like to ask some architectural ?s so I can get my head straight [vs. writing a book on here].

For the record, the Sling-Blade solution to this problem was to update my JDK to 1.8.0_144, after which apparently a bug in the JavaFX WebEngine had been fixed.  I was running 111.  Keep your JDKs up to date.
This doesn't affect the boot-related build bug from issue 216.

FYI I just fixed the issue with building the JAR on Windows.


The Magic Python 🐍

Our client would like start collecting data on who's visiting our website. Unfortunately, rather than using actual plug-ins, our client would like us to write and use a Magic 8 Ball program to tell them if the website is popular.
To do this, we need to use a written Python script for Magic 8 Ball, but we think the Magic 8 Ball's messages are rather boring. To fix it, please do the following:

[ ] Open the utils/python folder and the magic-8-ball file.
[ ] Change some of the magic 8 ball messages to messages of your choice.
[ ] Merge the file into master

Please submit your PR with a checklist, showing that you have done these three things.
BONUS #1: Refactor the Python code for an even better script.
BONUS #2: Squash your commits.

Can I take #4?

Absolutely! Please do!

First, python is in the root directory, not under utils/
2nd, how do I test my change before commit?
Thanks.

Sorry @jinzhong2 we don't have a test suite set up for the Python utils yet, but I can review it!

I'm ready to merge (already updated my github tree). How do I generate a pull request? I clicked a new pull request, and put my github link, but it says nothing is different?


End-to-end user journey recording

We need to create an end-to-end video showing the user journey from beginning to end for csvcubed.
@canwaf wishes to use the eurovision dataset again.
Deadline for this is 15:00 on Weds 6th April.
Video outline
1. Installing csvcubed

[ ] Using pip install both csvcubed and csvcubed-models
[ ] Show installation instructions page

2. Show valid csv for conversion

[ ] Create a single-measure dataset with no units or measures
[ ] Create a multi-measure dataset with some missing observations

3. Show convention serialisation

[ ] Use csvcubed build to build a 4-star csv-w from csv

4. Show configuration process

[ ] Show how templating the qube-config.json file works using the schema
[ ] Show the tool tips in the screen cast while writing the json from scratch
[ ] Configure three columns beyond "convention"

[ ] Time period configuration using template
[ ] Use an existing country dimension manually
[ ] Set up observation status using template to excuse missing

5. Show configured serialisation

[ ] Use csvcubed to build a 5-star csv-w from csv

6. Show validation steps

[ ] Use csvcubed to inspect single-measure csv-w, showing summary

[ ] Dive into single-observation's concept scheme for x

[ ] Use csvcubed to inspect multi-measure csv-w, showing more detailed summary

[ ] Inspect one of the concept schemes

Create a single-measure dataset with no units or measures

Every dataset should have at least one measure and at least one unit. Do you mean with no units of measures column?
I'd do this second tbh. Whilst it's useful to be able to show this to the internal team, we want to lead with the canonical shape data, which you'll be demonstrating in the multi-measure dataset.

Show the tool tips in the screen cast while writing the json from scratch

Good plan
Make sure to add on the end some discussion of how we'll load the data into PMD by re-using the upload to pmd pipeline type we already have working interally with the data engineers.

Also, make sure to show that we have documentation pages detailing the conventional column names users can use - presumably in the quick start guide.


[TRACKING] Breaking changes in Falco 1.0.0

This issue keeps track of all deprecated Falco features that will be removed in Falco 1.0.0:

append in Falco rule is deprecated in favor of override (see https://github.com/falcosecurity/falco/pull/2992)
syntax like- rule: Write below etc
  enabled: false

is deprecated in favor of override (see https://github.com/falcosecurity/falco/pull/2992).  - rule: Write below etc
    enabled: false
    override:
       enabled: replace

Please note that the enabled key is only deprecated when used as an override! So a rule like this is perfectly legit:- rule: legit_rule
  desc: legit rule description
  condition: evt.type=open
  output: user=%user.name command=%proc.cmdline file=%fd.name
  priority: INFO
  enabled: false

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

https://github.com/falcosecurity/falco/pull/3162 deprecated old rules_file config key in favor of new rules_files.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Good candidate :point_right: https://github.com/falcosecurity/libs/issues/2057

I'd also revisit the systemd units; perhaps we could have Falco packaged per-driver, like falco.rpm (modern_ebpf), falco-kmod.rpm, falco-ebpf.rpm and falco-plugins.rpm ?
Also, we could drop the falco.service alias for falco-kmod (or add it to other units?).

I'd also revisit the systemd units; perhaps we could have Falco packaged per-driver, like falco.rpm (modern_ebpf), falco-kmod.rpm, falco-ebpf.rpm and falco-plugins.rpm ?

@FedeDP
I'd prefer to split the drivers into different packages. For example:

falco.rpm (modern_ebpf built-in)
falco-driver-kmod.rpm (optional package, just the kmod, overwrite the Falco unit, depends on falco.rpm and requires kernel headers)
falco-driver-ebpf.rpm (optional package, just the legacy, overwrite the Falco unit, depends on falco.rpm and requires kernel headers)

Installing falco-driver-kmod.rpm and falco-driver-ebpf.rpm simultaneously should be disallowed.

Yep that is what i proposed :D

Yep that is what i proposed :D

Great. What I did not understand from your proposal is whether the driver package depends on the main package (or not).

That's a different story, i have no opinions on that. Either we could ship all packages like "full" packages with just minor differences (eg: falco.service unit would be configured and installed for the chosen driver only), or we could ship a default falco package with the executable and then the driver-flavored packages would install the rest with the needed deps (eg: falco-driver-kmod would install the falco-kmod systemd unit, the /usr/src/falco-... driver sources, would have the dkms and kernel headers deps, and so on)

That's my point. I'd avoid shipping all packages like full, since it seems to me not aligned with distro best practices. Moreover, the other solution should work better when uninstalling packages (since each package just tracks its own files, and does not overlap with files coming from other packages).

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale


Fix an issue where the depth format in MVKCmdClearImage was not getting set correctly.

Without this, clearing a depth stencil image causes a runtime crash with this message:
-[MTLRenderPipelineDescriptorInternal validateWithDevice:]:2400: failed assertion `No valid pixelFormats set.'

The fix is to simply keep track of the pixel format here.

Thanks. Good catch.


Akka licence available won't be using 'http4s'

@vimleshtna There is a separate task to clean up the http4s code.


New package: Seelen.SeelenUI version <IP_ADDRESS>

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@eythaann please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Seelen"

Hi @eythaann,
This package installs itself into a folder which I can't access without modifying security properties. Is this expected?

Hi @eythaann,
This package installs itself into a folder which I can't access without modifying security properties. Is this expected?   Click Continue:

Hi @stephengillie, yes this is the normal behavior for MSIX apps, you shouldn't run it directly from the executable instead you have to run the app using the app icon in start menu, or run shell:AppsFolder\Seelen.SeelenUI_p6yyn03m1894e!app in the explorer.

Verify:


Use npt_copy=4

So far so good, this should be the last major change before NEMO4.2 release. I'll let it run a bit more before merging.

The REBUILD_NEMO issue has been fixed! We can use the .F90 in main:
https://forge.nemo-ocean.eu/nemo/nemo/-/commit/3def55a68264d8dc5ba1f85e40168ebd2b126ce0


Values of simulated instances for event '8' missing.

The sensor values of the simulated instances for event '8' are missing.
They don't have the original values that were available in the previous version (1.0.0), except for the P-PDG tag values, which remain the same.

Hi, @mthlimao. This is a highly relevant issue. Thanks for this contribution. In a first analysis, I found that instances of other types also have this problem. We will further evaluate what happens and release a fixed version ASAP. Meanwhile, the previous version is perhaps better suited for certain experiments.

This issue was resolved with the PR #67. @mthlimao, thanks for having pointed out this issue.


Will ipc-flux work with  tags?

This looks really cool. I have a single browser window that has 3 webview tags in it like below.  So the processes look like this:
Main process <> Render process <> <webview> render process

I was wondering if this will still work for direct messaging from main process -> <webview> render process since you have to pass the browser window in the following call from main:
ipcFlux.dispatchExternal(targetBrowserWindow, 'init');

Or will I have to set up a relay through the render process that spawned the  processes?
Thx!

I haven't tested with webview, nor have I used webview before. Unfortunately I really don't know, but I'd be happy to investigate for/with you on this.
I mean, If it works with ipc-renderer / ipc-main, then it should work as expected.
If you send something to the main process from within the webview, you could reply to it from main.

Doesn't seem to bc the messaging is a bit different between a render and a webview render process. So you can get to main from web view fine but my case requires getting to the "embedding" render process which is the direct parent. I was actually thinking of forking this to make it work but would love to put our heads together on it. This is so useful.
I haven't done this before, should we just continue the discussion here?  I can post a bit more detail a little later if so.

So I did a bit of digging into your code. It's a bit beyond me as in certain respects as I am more of a python guy, but here is the high level issue:
To give a little color, I have a use case where I am trying to plug into a third party messaging web application to handle some automation tasks based on my internal user needs. So I have a single browser window that has a single render process that has three  tags in it, as in the code image above (1 third party site and 2 internal web apps that will eventually be true Electron object down the road). The "host" render process is the coordinator of activity and relaying messages between the <webview> render processes. It's def a hacky situation but kind of ideally dealt with in an Electron context. I had it set up as a Chrome extension before. Something like this:
- Main process
    - Render process (host)
        - webview 1 - third party website (guest)
        - webview 2 - internal (guest)
        - webview 3 - internal (guest)

All communication using ipcRenderer and ipcMain (as I understand) only travels between the main process and a render process (either normal render process or a render process for a <webview>). A <webview> process is considered just another render process ("guest" process) and therefore it can only send messages directly to the main process using ipcRenderer.send.
If the <webview> process wants to send a message directly to the host/embedding render process that created it, it was to use the call ipcRenderer.sendToHost. It sill uses the ipcRenderer.on to listen for inbound messages.
Conversely, if the host render wants to talk to the guest render process, it has to use:
var webview = document.getElementById('webview')
webview.send('ping', {command: 'test'})

And for host to listen to guest, it must listen with:
webview.addEventListener('ipc-message', ...)

A hack would be to use the main process as a relay to send a message from webview > main > render, and then back again, but not ideal. Any ideas on a fix? I seems like it would be a small adjustment to your code but its not clear to me how to do it.

In terms of the handshake process, the whole thing is currently a bit of a mess. Disregard the handshake failure messages right now as they aren't directly connected to the messaging process. Honestly, I'm thinking about removing them as they're causing more trouble than it seems to be worth. The only use case that would see benefit would be in debugging, but even then, it may not be worth the effort required to make it work nicely.
ipc-flux is still in active development, with the handshake process my top priority right now, followed by state and commit functionality.
I'm still investigate webview, mostly just trying to wrap my head around it completely, especially in relation to ipc-flux.
I haven't had the opportunity just yet to have a proper stab at a solution, but hopefully I will be able to soon.
As far as the whole of ipc-flux goes, is there anything you think needs to be improved upon/reworked or renamed (specifically function handlers)?

UPDATE
I pushed a new release yesterday 0.3.10 which should fix any handshake issues.

Great, thanks for letting me know.

Rishi Patel |<EMAIL_ADDRESS>On Thu, Aug 24, 2017 at 5:13 PM, Harry Park<EMAIL_ADDRESS>wrote:

UPDATE
I pushed a new release yesterday 0.3.10 which should fix any handshake
issues.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/harryparkdotio/ipc-flux/issues/1#issuecomment-324790634,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADn5wUiGzw8XYgT88jAjT0sTiU7yPSWfks5sbhGcgaJpZM4O_R9u
.

UPDATE
I pushed a new release 0.3.13 with minor fixes (due to adding eslint into the testing process). I also added documentation on how to setup ipc-flux in <webview>, and communicating from main to webview.

Awesome, I will check it out tomorrow!

Rishi Patel |<EMAIL_ADDRESS>On Mon, Aug 28, 2017 at 5:58 PM, Harry Park<EMAIL_ADDRESS>wrote:

UPDATE
I pushed a new release 0.3.13 with minor fixes (due to adding eslint
into the testing process). I also added documentation on how to setup
ipc-flux in , and communicating from main to webview.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/harryparkdotio/ipc-flux/issues/1#issuecomment-325523717,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADn5wX1yubboUS4bcP2Ubb6FAbXb6ummks5sc2JAgaJpZM4O_R9u
.

Took a quick look. Question -- will it still work if it is setup in the preload file instead of the src file? I can't remember if I tried it this way as it was early on in my reading that I tried this library.
I have to have nodeIntegration turned off bc I am loading another website in the webview, but can still  use node in the preload file and have it persist, which is what I do. I will test with a dummy app tomorrow:
https://electron.atom.io/docs/api/webview-tag/#preload

Just tested it then; it works, and you're right that you don't need to add nodeintegration if happen to be using preload. I'll add this to the docs.


add map circle feature

// simple example in Kotlin //
companion object {
val COL_CIRCLE_LINE = Color( 0.1, 0.1, 0.1, 0.5 ) // dark grey
val COL_CIRCLE_FILL = Color( 0.4, 0.4, 0.4, 0.5 ) // light grey
}
// to create
val fenceCircle = MapCircle(Coordinate(fence.latitude, fence.longitude), fence.radius)
.setVisible( true )
.setColor( COL_CIRCLE_LINE )
.setFillColor( COL_CIRCLE_FILL )
// to add
this.mapView.addMapCircle( fenceCircle )
// to remove
this.mapView.removeMapCircle( fenceCircle )

Thanks for the trying and your comments.
Yes, right. I noticed it as well, and am trying to fix it, but it's not working well.
When the zoom rate is changed, some circles are disappearing from the map, which I couldn't figure it out.
Could you please have a look at the recent commit?
If there is no way to fix it, please merge it and leave it as known issue.

the reaction to the resolution change should be done in the Javascript part, I merged the PR, but will undo this commit for the zoom change and have a look at this. Thanks again for your contribution!

just a short notice: I implemented the scaling of the circles when the resolution is changed. I added corresponding code to the demo application. I now need to add this to the 1.x branch for Java 8 as well, and then will release a version with this code- probably tomorrow evening.

Thanks for letting me know. That sounds great. I'm looking forward the code soon.
Have a great week!


I.grabTextFrom [1] Error | Error: Element was not found by text|CSS|XPath

After a switch to codeceptjs@3 I faced this issue:

Looks like a regression because of 2 years of stable work under codeceptjs v2,
I use I.seeElement as prove:

   "codeceptjs": "^3.1.1",
   "webdriverio": "^7.9.1"

yes, this was a breaking change in CodeceptJS
please see upgrade guide https://github.com/codeceptjs/CodeceptJS/wiki/Upgrading-to-CodeceptJS-3


Cannot query field "allSanityPost" on type "Query"

Hi,
I cloned the repo, followed the blog post here and added all the content in my local Sanity Studio as described in the article, but I keep getting Cannot query field "allSanityPost" on type "Query" when I run yarn start.
Any idea why?
Thank you

Hi,
Same problem for me but I've followed a different configuration following https://www.sanity.io/blog/live-coding-with-gatsby-js-and-sanity-io-how-to-make-a-portfoliand o-website to the letter.
It's like graphiql did not know anything about the sanity studio schema.
I followed gatsby-source-sanity plugin instructions, set up sanity studio and schemas, deployed graphql API enabling Graphql playgroung which works as expected, but for Gatsby graphiql interface is like data did not exists.
I'm wondering if there's some step missing for me.
Thanks a lot.

I have recloned the repo today, yarn install, yarn run init (using the project and dataset that I already created) and after that yarn start shows no errors related to graphql. Did one of the last commit solved the issue?
Anyway there's still a little bug, I had to yarn add gatsby-react-router-scroll in the web/ folder to make it working, but now seems fine.

Had the same issue but redeploying the graphql and deleting the .cache folder fixes it

Hey guys Im getting this error too but deleting cache and redeploying graphql is not working

I also have a similar issue. The new schema shows in my Sanity studio, but not in GraphQL when run locally. I've tried deleting cache (in which there's no point since npm run dev clears cache first)
Appreciate any solutions


_49-[GDTCCTUploader readyToUploadTarget:conditions:]_block_invoke + 281 crash

pod 'Fabric', '1.10.2'
pod 'Crashlytics', '3.14.0'
pod 'Firebase/Core' , '6.18.0'
pod 'Firebase/Auth' , '6.18.0'

pod 'Google-Mobile-Ads-SDK', '7.55.1'
crash info:

@wangjunhua1 could you also share version of GoogleDataTransport?

@wangjunhua1 could you also share version of GoogleDataTransport?

pod 'GoogleDataTransport', '5.1.0'
pod 'GoogleDataTransportCCTSupport', '2.0.1'

Thanks for the report, I'll be getting to this soon.

Hello, I encountered the same problem.
Crashed: Thread
EXC_BAD_ACCESS 0x0000000000000001
0  libobjc.A.dylib            0x1b54cf284 objc_retain + 100
1  libdispatch.dylib          0x1b5441fd8 _dispatch_client_callout + 20
2  libdispatch.dylib          0x1b544e7f4 _dispatch_lane_barrier_sync_invoke_and_complete + 60
3  SlideMenuControllerSwift   0x10093a4f0 -[GDTCCTUploader readyToUploadTarget:conditions:] + 108 (GDTCCTUploader.m:331)
4  SlideMenuControllerSwift   0x100935764 __52-[GDTCORUploadCoordinator uploadTargets:conditions:]_block_invoke + 464 (GDTCORUploadCoordinator.m:120)
5  libdispatch.dylib          0x1b5440b7c _dispatch_call_block_and_release + 32
6  libdispatch.dylib          0x1b5441fd8 _dispatch_client_callout + 20
7  libdispatch.dylib          0x1b5448450 _dispatch_lane_serial_drain + 568
8  libdispatch.dylib          0x1b5448e7c _dispatch_lane_invoke + 368
9  libdispatch.dylib          0x1b5451f20 _dispatch_workloop_worker_thread + 580
10 libsystem_pthread.dylib    0x1b54a76d0 _pthread_wqthread + 280

Hello, I encountered the same problem, too.

Have same issue, after update...

I'm pretty sure this is because of unsynchronized access of a property which is resulting in calling -count on an incomplete object. Fix is incoming momentarily.

Can a historical  stable version of the SDK be provided here?
The crash caused by this problem is too high，Can the latest version be stable?

Same issue here. When can we expect a public fix?

+1. A lot of crashes with this issue.

+1!

Also crashing.

same

The crash should not be present in GoogleDataTransport 5.0.0 (@mikehaney24 to confirm), and will be fixed in the next release of Firebase. If you're experiencing this crash please try downgrading or wait for the next release.

@morganchen12
When can we expect the next release?

We do our best to ship releases biweekly, so if there are no delays the fix will be pushed sometime next week.

Locking issue to prevent additional "ETA please" requests. Monitor release notes.

I've also added the next release milestone to this issue which can be monitored in GitHub.

We've pushed an ad-hoc release for GoogleDataTransportCCTSupport pushing the version to 2.0.3. This release should be available now, please pod update, ensure the GDTCCT version is 2.0.3, and let us know if it doesn't resolve the issue.

The crash should not be present in GoogleDataTransport 5.0.0 (@mikehaney24 to confirm), and will be fixed in the next release of Firebase. If you're experiencing this crash please try downgrading or wait for the next release.

Which version should I choose to ensure stability？
Hope to provide the exact version number for each SDK，thanks。
SDK dependencies：
pod 'Firebase/Analytics'
pod 'Firebase/RemoteConfig'

You should be able to avoid this crash with pod GoogleDataTransport, '~> 5.1.0'.

Is there a timeline to update https://firebase.google.com/download/ios or a way to download history releases as zip?

@steipete We generally only publish zip builds with full Firebase releases. For that, you can track the milestone tag on this issue - targeted to happen later this week.
As you know, it's also possible to create your own binary distribution from any CocoaPods with https://github.com/firebase/firebase-ios-sdk/tree/master/ZipBuilder

Ah, didn't think about that. That's perfect - thanks Paul!

This is looking fixed to us, can anyone confirm? Relatedly, is anyone seeing any issues in the new version?

Happening on GoogleDataTransportCCTSupport 3.0.0.

Can you give me a stack trace for the crash you're seeing?

@mikehaney24 We don't see craches with this issue after update GDTCCT version to 2.0.3. Thank you.


Handle overlapping unit ranges

And ignore sequences and functions that start at 0.
Fixes #67

Coverage decreased (-0.1%) to 3.15% when pulling fe75f15a63c6c534744fe95d40f669566216ae76 on philipc:issue-67 into ba9f195c4a7f380c5ede1339bc8d9d293be22acb on gimli-rs:master.


edit subgraphs

dflow editor should be able to open a subgraph and edit it

no subgraphs, simplify the spec


not working with ubuntu

I am unable to get this to work in Ubuntu. I can not install the dependencies xprop and xwininfo which may be the reason.
$ sudo apt-get install xprop
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package xprop
sudo apt-get install xwininfoReading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package xwininfo

Hi @samwalrus !
Give me a moment to fire up my VM and test this...

@samwalrus, clearly I messed up writing the README. xprop and xwininfo seem to be included in another package for xorg. Try these two commands to see if you've already got them.
type xprop
type xwininfo

This should return the path for each, if it exists.
I really appreciate you bring this to my attention btw! 👍


Run Artman smoke tests as part of CircleCI

Run the full suite of artman smoke tests. This does even more tightly couple gapic-generator to artman for now, but it will save us time down the road when we go to release artman and gapic-generator has broken artman.
Soon after this, I can put in a CircleCI job filter so these smoke tests only run on the master branch, given that they take a long time (~40 minutes).

PTAL
Check out https://circleci.com/gh/googleapis/gapic-generator/9989 for the artman smoke test run!

Oh wow it caught some actual failures that are locally reproducible, namely the containeranalysis_v1beta1 artman failures.

This is blocked by https://github.com/googleapis/gapic-generator/issues/2454, which is a regression in gapic-generator that prevents some artman calls from succeeding.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@bfb49ba). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #2443   +/-   ##
=========================================
  Coverage          ?   86.53%
  Complexity        ?     5289
=========================================
  Files             ?      458
  Lines             ?    21055
  Branches          ?     2298
=========================================
  Hits              ?    18219
  Misses            ?     2011
  Partials          ?      825

Continue to review full report at Codecov.

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

https://github.com/circleci/circleci-images/issues/275 causes the Ruby failure


fixing issues for windows platform

this pull request is intended to fix few bugs for windows platform:

https://github.com/phonegap/phonegap-plugin-barcodescanner/issues/56  preview is hidden behind ionic views
https://github.com/phonegap/phonegap-plugin-barcodescanner/issues/42  only front camera is being used, while back camera should be selected if available. + kaleidoscope effect which was caused by setPreviewRotation. instead I am rotating video preview element.

@VladyslavGoloshchapov, have you tried the solution for preview rotation from official documentation?
I suspect that problem with corrupted preview might be resolved by replacing setPreviewRotation to direct manipulation of media stream properties (as described in the article above)

@VladyslavGoloshchapov, thanks for contribution, your changes was integrated into master.
However, i decided do not pick a fix for preview orientation, since it seems to works incorrectly in portrait mode (at least for me). Please address notes, related to orientation changes and submit a separate PR for this.
Thanks again.

well portrait mode was not perfect for me either. problem was that I didn`t have time to apply your comments to my commit.
I am not super familiar with WinJS devices API, so I used examples from their site to do some urgent fixes. As far as I understand not everything was fine.
Thanks for correct fix

Update: preview orientation change from this PR was pulled in with some tweaks


Cannot reset "visibility" property on webview view in package.json

Testing #105764

Use the webview view extension sample: https://github.com/Microsoft/vscode-extension-samples/tree/master/webview-view-sample
Modify the view contribution point to set "visibility" to "visible"

		"views": {
			"explorer": [
				{
					"type": "webview",
					"id": "calicoColors.colorsView",
					"name": "Calico Colors",
					"visibility": "visible"
				}
			]
		},

Run extension and expand the explorer, view is visible as expected
Change "visibility" to another value, or remove the property, and rerun the extension

The view seems to now be cached in an expanded state and the new "visibility" value is ignored

Actually, I think this is working as expected - I think I collapsed and reopened the view, which would prevent the initial state from being picked up again.


Added logFactory.ReloadConfiguration and LogManager.ReloadConfiguration

fixes #3938

Unit test fails, as how to handle (event, exception) is still a discussion when the config is null

Please make a ReloadConfiguration that takes a LoggingConfiguration as parameter. Please make a new ConfigurationReloading-event that can be used in applyOnReload. Make sure the new event also has IsNewConfiguration.

Please make a new ConfigurationReloading-event

We can't have a new event? As it should also work when you reload things by changing the nlog.config (when autoreload is on)

We can't have a new event? As it should also work when you reload things by changing the nlog.config (when autoreload is on)

You should have the callback happening before initializing the targets. Not after. Which is why it should be ConfigurationReloading (BEFORE) and not ConfigurationReloaded (AFTER)

I think you're right. Damn another event.
Funny, as this was always wrong then: https://github.com/NLog/NLog/wiki/Combine-XML-config-with-C%23-config

Yes I know :). It only worked with "smart" targets like FileTarget that adapted to properties being changed after initialization. But very few target has that flexibility / complexity.

Or does that work thanks to     LogManager.ReconfigExistingLoggers();? (I always find this call a bit strange)

If we have a ConfigurationReloading, do we still need ConfigurationLoading? (or it is nice to have them both - but maybe it should be ConfigurationChanging then)

LogManager.ReconfigExistingLoggers() will ensure that "new" targets are initialized, and new rules are applied in filtering.
But it doesn't help when making modifications to existing targets.

Please make a ReloadConfiguration that takes a LoggingConfiguration as parameter.

I get the idea, but I think it's a bit strange. Would it be more logical if we have `LoadConfigration(configuration, bool behaveAsReload)? (better name also OK)

No you are misunderstanding me. This PR adds this method:
LogFactory.ReloadConfiguration()
I want also this method (That can be called by MEL-NLogLoggingConfiguration):
LogFactory.ReloadConfiguration(LoggingConfiguration newConfig)
I don't want new methods on the Setup()-API

want also this method (That can be called by MEL-NLogLoggingConfiguration):
LogFactory.ReloadConfiguration(LoggingConfiguration newConfig)

I don't understand this. A reload is always of the current config? It's now a replace-reload. What's na use case for that?

How is MEL-NLogLoggingConfiguration going to signal that it is performing a reload?

How is MEL-NLogLoggingConfiguration going to signal that it is performing a reload?

By doing LoadConfigration(configuration, bool behaveAsReload).
I don't think we going agree with that. I could live with LogFactory.ReloadConfiguration(newConfig);

I could live with LogFactory.ReloadConfiguration(newConfig);

Excellent


Changes for the Issue #321 ,

Refactored the code for CodeBlock for changing themes and swithced themes for dark mode and light mode as well, and fixed an small issue where variable name is removed in SearchDialog which was failing builds
PR Fixes:

1 Added Changes in Themes layout so it switches the themes for CodeBlock, using highlight.js vs and vs dark themes (it can be changed to others based on preferences)
2 Refactored the CodeBlock so it accepts themes and conditionally importing theme files
3 In SearchDialog there was empty variable name which was failing local running dev, so when checking i have added the variable name which was used in file in useRef : 'scrollableContainerRef'

Resolves #321
Checklist before requesting a review

[Done] I have performed a self-review of my code
[Done] I assure there is no similar/duplicate pull request regarding same issue

closing because of conclifcts, please reopen if u have the time


Automations on your truma.yaml slow down the Home Assistant host

Hello Dr. Christ.
My Raspberry PI3 was slow down with the automations loaded from your truma.yaml file.
Thats happend durig opening of your automations in Home Assistant to investigate the function.
With every opening of another automation, the system was a little bit slower.
I must reboot my HA host.
At the end, I migrated all your automations in the Home Assistant system and deleted your automations from your truma.yaml file.
My Raspberry PI3 runs now as fast as before.
This is an info and not realy a bug.
It is possible that HA has here a bug.
BR
Andreas (kartzie)

Hi,
In my HA installation in my RV, the Truma and Aventa automations have been running for more than 9 months without any problems. My hardware is an ODROID system, my INETBOX simulation runs on RPI. I think you still have a bug in your implementation. Nevertheless, thanks for the hint about the useless Boolean switch "truma_water_button" , which I have removed from the code.
I assume that it is fine for you to close the two issues, you opened.

Hi.
Your program works fine as expected.
My system will be slower if I open your automations in Home Assistant to investigate the Automation.
It seems, that Home Assistant itselfe have a problem to display the automatisation details.
BR
Andreas


IMPORTANT ANNOUNCEMENT: About viddy v1.0.0

Hello everyone,
I am the owner of this project. I am currently working on the development of viddy v1.0.0, which is almost complete and will be released soon.
In a very bold decision, I am going to replace the current viddy, which is written in Go, with Rust. There are several reasons for this, but the main one is that I will be more motivated to maintain it. Additionally, I have been dissatisfied with some aspects of the current implementation of viddy. This is not because of Go, but because my initial implementation was poor. This has led to some of the bugs currently being reported, but I believe a reimplementation will resolve some of them.
Fortunately, viddy has been integrated into many package registries. If a build is required, Rust will be needed, so changes are expected. I apologize for the inconvenience and appreciate your understanding.
In viddy v1.0.0, the following features are planned to be discontinued. If you need these features, please contact me. I will do my best to include them. As for other compatibility, I am making every effort to maintain it as much as possible.

-c, --clockwork option
--pty option

I've found better way to handle terminal size.

The Rust version of Viddy will be managed in this repository. I apologize to all contributors, but I plan to delete all Go code (it will remain in git). If there are strong objections, I will consider separating the repository or keeping the Go code. Please let me know.

By the way, if I switch to Rust, will I have to change this Gopher logo? I really love this logo and don’t want to change it.

Wow, that's a big change. Thanks for giving the community a heads up! Do you have any plans to make your rust branch public here before the 1.0 release? That would help package maintainers prepare.

@rrotter Thank you for your comment!
Yes, I can do that!

I've released v1.0.0-rc.0 https://github.com/sachaos/viddy/releases/tag/v1.0.0-rc.1 🎉

I've released viddy v1.0.0-rc.2 🎉
Now, viddy can save and load history!
https://github.com/sachaos/viddy/releases/tag/v1.0.0-rc.2

Big change indeed! I’ll check out the release candidates soon, but as someone who defaults to Go these days for simple programs, I’m curious about your experience with rewriting from Go to Rust. I understand this is somewhat unrelated to the main issue, and you might not be planning to discuss it, but if you are, I’d love to read about it. Thanks!

Just got a chance to check out v1.0.0-rc.2, seems to work well other than the following --

Doesn't seem to handle tabs correctly

viddy 'echo "1\t2"' prints 12

Doesn't seem to handle escape sequences correctly

viddy 'echo "\e[34m blue \e[39m default \e[0m all"' prints default in blue

Doesn't seem to support arrow keys for scrolling like the Go version
Horizontal scrolling seems to move by 10 columns instead of 1 like the Go version (I don't necessarily think this is worse, just reporting a difference I observed)

@avamsi Thank you so much!
That's very helpful!

@avamsi

Horizontal scrolling seems to move by 10 columns instead of 1 like the Go version (I don't necessarily think this is worse, just reporting a difference I observed)

Yes, this was an intentional change. The small scroll width was inconvenient, so I will also consider mouse support. Thank you.

@avamsi

Doesn't seem to handle escape sequences correctly

I couldn't reproduce that.
When I run the command, the output is like following.
The same issue occurred with both the watch command and go viddy.
Can you share the backup file (the feature is included in rc.2)?

I couldn't reproduce that.

Oh. This is what the Go Version prints for me --

And this is what the Rust version prints --

watch doesn't work for me though --

Can you share the backup file (the feature is included in rc.2)?

Looks like I can't upload sqlite files here directly, I put it on Google Drive for now -- https://drive.google.com/file/d/11U-kjxFHC1glvlDpCToNZe2myWUc-uXt/view?usp=drive_link.

Ah, looks like I was supposed to do watch --color, which works fine --

@avamsi Thank you! What is the using OS?
Are you changing the shell in configuration files?

What is the using OS?

I'm currently on a Chromebook running Debian (via Crostini), I could test on a MacBook if you want.

Are you changing the shell in configuration files?

Nope.
Are you unable to reproduce? What does just echo '\e[34m blue \e[39m default \e[0m all' print for you?

@avamsi
It seems like depending on shell.

bash → fail
sh → fail
zsh → success

I reproduced that issue by using zsh.
$ viddy --shell zsh 'echo "\e[34m blue \e[39m default \e[0m all"'

Ah, I see -- yes, I use zsh.

Looks like echo -e '\e[34m blue \e[39m default \e[0m all' should do the trick in Bash.

@avamsi I think we have fixed the reported issues 1.
Thank you for your contributions (PR and issue reporting)! 🙏

My pleasure! Thanks for fixing these quickly and in general, your work on viddy -- big fan!

I have released viddy v1.0.0-rc.3 https://github.com/sachaos/viddy/releases/tag/v1.0.0-rc.3

Hi. Thank you very much for your project. Today I try new release v1.0.0-rc3 on centos7 forked system, but it requires new versions of glibc.
[centos@bootstrap build]$ viddy
viddy: /lib64/libc.so.6: version GLIBC_2.29' not found (required by viddy) viddy: /lib64/libc.so.6: version GLIBC_2.32' not found (required by viddy)
viddy: /lib64/libc.so.6: version GLIBC_2.33' not found (required by viddy) viddy: /lib64/libc.so.6: version GLIBC_2.34' not found (required by viddy)
Maybe is there a way to compile the program for a less recent version of glibc ?

I have released viddy v1.0.0-rc.5 🎉
I believe most of the problems have been solved. (Yes, there are still some issues and feature requests remaining.)
I'm planning to release v1.0.0 in a few days.
https://github.com/sachaos/viddy/releases/tag/v1.0.0-rc.5

@slashburygin Thank you for the report!
I've released musl binary from v1.0.0-rc.5.
If you have time, please try it.
https://github.com/sachaos/viddy/releases/tag/v1.0.0-rc.5

Now all is ok, thank you very much.
Small diff between versions: now interval option is integer, not float.
error: invalid value '1.8s' for '--interval ': invalid float literal

Oh, sorry, now I can set interval without s, for example 1.8

@slashburygin Thank you!
That behavior is not the same as the old version.
(The go version of Viddy can handle 1.8s)
However, it is a bit difficult to fix because the crate being used cannot handle it.
So I don't fix it now.
https://github.com/sachaos/viddy/issues/131

I released viddy v1.0.0.
https://github.com/sachaos/viddy/releases
I submitted a PR to homebrew-core.
https://github.com/Homebrew/homebrew-core/pull/181977

I close this announcement issue because v1.0.0 released.
If there are some problems, feel free to create a new issue.
We will track the status of the package registry in a separate issue.
https://github.com/sachaos/viddy/issues/136

@avamsi

I’m curious about your experience with rewriting from Go to Rust.

I've written the blog post about my experience of migrating from Go to Rust.
If you are interested in, please read that!
https://dev.to/sachaos/release-of-viddy-v100-migration-from-go-to-rust-2g41

Thanks for the writeup! Matches my experience / expectation trying out Rust here and there but more importantly, it's encouraging to see someone else go through the learning curve / trade offs etc. (and come out the other side)! :)


feat: When the compare mode is visible, ensure the visor is not covered by the header

Hi everyone,
On the camera/scanner page, if the compare mode is visible, two buttons are visible, but they may cover the visor.
To prevent this, a slight padding is applied.
As always, a video: https://github.com/openfoodfacts/smooth-app/assets/246838/8f28a353-7222-4111-bb5a-fc6602fbc252
Will fix #4012

Codecov Report

Merging #4229 (9372329) into develop (95c3a67) will decrease coverage by 0.08%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           develop    #4229      +/-   ##
===========================================
- Coverage    11.00%   10.93%   -0.08%
===========================================
  Files          282      282
  Lines        14015    14096      +81
===========================================
- Hits          1543     1542       -1
- Misses       12472    12554      +82

Impacted Files
Coverage Δ

...oth_app/lib/data_models/continuous_scan_model.dart
0.00% <0.00%> (ø)

...es/smooth_app/lib/pages/scan/camera_scan_page.dart
1.51% <0.00%> (-0.31%)
:arrow_down:

...ackages/smooth_app/lib/pages/scan/scan_header.dart
0.00% <0.00%> (-2.09%)
:arrow_down:

... and 5 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Very 👍


Make transaction TTL optional

Internally represent no-ttl/infinity with 0 to keep serialisation short.

edoc failed :-(

Added a note in the Release notes


fix(client): support external file imports inside of email components in previews

This PR implements a fix for https://github.com/resendlabs/react-email/issues/613.
React Email should now be able to preview files that container imports like import Theme from '../src/theme' (sibling directory of /emails).
In order to do this, email files are no longer copied over to the .react-email/emails/ folder but instead files are created which only re-export their default export, like so:
.react-email/emails/my-template.tsx:
import Mail from '../../my-template.tsx'
export default Mail`

Also resolves that static files where not copied over correctly and throwing an error every time.

General feedback:
Firstly: thanks for your great work! I really appreciate this! 👏
Secondly, I found the contributing experience quite cumbersome as the contribution guide or readme do not explain how to develop in this repository. Through a lot of trial and error, I made it work like so:
cd demo
../packages/react-email/node_modules/.bin/ts-node ../packages/react-email/source/index.ts dev

which was quick awkward.
(for which I also had to install typescript in the react-email folder).
I assume that you have some monorepo setup somewhere that solves this nicely, but I could not find it.
Maybe you can provide a guide on how to do it properly (or point me to an existing one)

I just noticed that this might be a breaking change if people have reusable components inside /emails/, like /emails/components/Layout.tsx as it. Such that it will throw a warning:
Attempted import error: '../../../emails/components/Layout.tsx' does not contain a default export (imported as 'Mail').

Import trace for requested module:
./emails/components/Layout.tsx
./emails/ lazy ^\.\/.*$ namespace object
./src/app/preview/[slug]/page.tsx

I could limit the import to not go over the emails folder recursively. Are folders within the emails directory officially supported?

Yeah, this should allow importing components or other files from emails or outside emails.

I was working on this branch successfully the last couple of days :)
@bukinoshita should I change this to only load the files directly under /emails/*?

I could limit the import to not go over the emails folder recursively. Are folders within the emails directory officially supported?

Yeah, I think so for now. Because we're only copying the emails/static folders.

@bukinoshita I limited it to only use the files from the emails directory directly 🙂
If you could merge it, I would resolve the conflicts with my other PRs.

Oh I also noticed something different: I think this also solves automatic reload when changing files. At least I had a lot of problems before working on this branch and now it just works. :)

Nice, thanks!

@EyMaddis Sorry for the delay, can you check the conflicts?

@bukinoshita Done :)

Hey, thanks for your work on this PR. When will this get packaged and released to NPM?
Says last release was 14 days ago. Just looking to use components with react-email in my project and this has been a roadblock.

This is still on issue on windows 10...


Help debugging issue with port-forwarding

Hey @DeCarabas, hope you're doing well! I'm using fwd here at new gig and I'm running into an issue where a port isn't being forwarded by fwd.
Running lsof, here are two ports with active listeners:
coder@dev-chris:~$ sudo lsof -i:8250
COMMAND   PID  USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
vault   17947 coder    9u  IPv4  26541      0t0  TCP localhost:8250 (LISTEN)
coder@dev-chris:~$ sudo lsof -i:6060
COMMAND  PID  USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
coder   1782 coder    7u  IPv4  38156      0t0  TCP localhost:6060 (LISTEN)

6060 is forwarded, 8250 is not.
Without going too much further into the code, are there additional debugging steps that you would recommend I take to debug this? I've tried turning on logs but nothing shows up.
Running fwd with -s does port-forward 8250. Here are the debug logs:
[CLIENT] Port config PortDesc { port: 8250, desc: "vault login -method=oidc --format=json -address=https://sitetest3-vault.simulpong.com:8200" } -> PortConfig { enabled: true, description: None }                                                                                │
│[CLIENT] Starting port 8250 to 58311

you could add -vvv at the port forwarding code

Hmm, I'm not sure. If it works with -s but doesn't work otherwise then it's something to do with permissions reading procfs, which means there's something about the way that vault is being run that doesn't let your normal user poke at it. I don't know anything about your case though. (Or vault? Is that the HashiCorp vault?)
I despair of using logging for this, only because (a) the logging will be very verbose and (b) we don't have a good way of going through so much logging. Maybe using strace on fwd on the server side would help identify what isn't working? I expect you would just see open fail with EACCES though, which is just not that useful. :(
I guess: how is the process in question being run?

Thank you both for the responses! Is there a way to run the server in debug mode so that I can add logging? I'm building my own version of the server but adding logging seems to make the client hang :)

Is there a way to run the server in debug mode so that I can add logging?

Make sure the debug version is the one on your path on the server. The client just runs ssh <whatever> fwd --server, so ssh is going to find the one in your path...

but adding logging seems to make the client hang

This is concerning and I would be happy to debug this too.

One other thing you might try: although not documented, fwd supports a certain amount of manual configuration. If the port for vault is known, then you could try writing a configuration file named ~/.fwd which contains the following TOML:
[servers.dev-chris.ports]
8250 = { enabled=true, description="vault" }

(Replace dev-chris with the name of the server you use with fwd, and 8250 with the port number.)
This doesn't work very well before 0ad0fb1, but I fixed it up recently. Maybe that's a workaround, if you can't figure it out otherwise?

I've been thinking about this and as of a9bbd29 I changed the policy about what ports get reported from the server to the client.
Now, if you're running a sufficiently new client, the client will report all ports from the server, even if it cannot identify the process that is listening on the port (say, because of permission issues).
These "anonymous" ports will be disabled by default, for security reasons, but they can be manually enabled with the UI.
(If this is too onerous, the configuration solution above still works.)

I've been thinking about this and as of a4745c9 I changed the policy about what ports get reported from the server to the client.
Now, if you're running a sufficiently new client, the client will report all ports from the server, even if it cannot identify the process that is listening on the port (say, because of permission issues).
These "anonymous" ports will be disabled by default, for security reasons, but they can be manually enabled with the UI.
(If this is too onerous, the configuration solution above still works.)

Thank you! I will give the new client a try!


Uniqueness validation

Today, I noticed that when using validates :field, uniqueness: true on a model with belongs_to_multitenant doesn't cause the validation query to be restricted to the tenant.
My goal was a tenant-scoped uniqueness, but one could argue that application wide uniqueness can be meaningful in multitenant applications as well. In that spirit, I don't think it is a bug, but a sentence like "Multitenant doesn't affect Rails built-in uniqueness validation; for tenant-scoped validation use validates :field, uniqueness: { scope: :tenant_id }" in the readme would be helpful.

great idea, and if you have any thoughts on how to organize in the README, I'd gladly accept a pull request.


The false branch of #if is not grayed out.

Semantic highlighting is disable between the false branch of #if/#endif, however it's better to have those code grayed out.

It's not a bug, no such feature yet.

This works for me.

Ah Okay, now I got it... Indeed, there's no "graying out" just turn off. Actually I wonder whether graying  out is even possible in vim/neovim, I think there's no such feature in the editor itself.

Hmmm, it may be possible to implement on NeoVim using an empty floating window with &winblend set to some transparency value.

Maybe I'm misunderstanding the issue, but I believe https://github.com/clangd/clangd/issues/132 is related. According to the most recent comment there, clangd-11 should support this, although possibly some client changes are required (?) - https://github.com/clangd/vscode-clangd/pull/54/files

@mellery451 there's no graying-out capability on [neo]vim. It's possible to fake it on neovim through an overlay window as commented before, but I think it's hard to implement. Basic single-tone "graying out" already works.

sorry to change the subject, but are there docs on how to get the "basic" (comment lowlight) option working with clangd? I can make it work if I use ccls as the LS, but never have been able to get it working with clangd, even if I use clangd-11

"basic" (comment lowlight)

I get that by enabling semantic highlighting by integrating with vim-lsp-cxx-highlight, as commented in README.

yeah, that has never worked for me. It works as soon as I enable ccls in coc.nvim, but with clangd alone, I never get the disabled region shown as such. I've tried with every available version of clangd.

@mellery451 no idea why it doesn't work for you...

Maybe I'm misunderstanding the issue, but I believe clangd/clangd#132 is related. According to the most recent comment there, clangd-11 should support this, although possibly some client changes are required (?) - https://github.com/clangd/vscode-clangd/pull/54/files

If I understand correctly, the inactive code ranges were added very recently (https://github.com/llvm/llvm-project/commit/0aaa2acc4ca0389a79a46bca3dc5b9365c641d77#diff-bc83abf3e556418f438c09a672856449) so you might need this patch for such functionality. It didn't make it into any release yet, so I think the only way it would work would be a nightly release via clangd/clangd Releases.
@hokein might have more context and correct me if I am wrong.

clangd-10 supports inactive region partially, it sends InactiveCode token, but without computed ranges (the original plan was required special handling in all client side), so the current implementation doesn't gray out the inactive region.
Yeah, with the patch https://github.com/llvm/llvm-project/commit/0aaa2acc4ca0389a79a46bca3dc5b9365c641d77, it should just work with coc-clangd, but you need a weekly-build clangd.

My clangd version is 10.0.1 and anytime I write #if 0 it grays out the code.

Looks like that just works for #if 0, for #if 1 < 0 it doesn't.

@oblitum that #if 0 thing comes from the c syntax file (:help c.vim) because it's so common for c progs to block comment with it. It has nothing to do with actual preprocessor/compiler info.

hmm, ok, my bad then.

clangd-11 is released and I believe the patch that @hokein mentions above should be included. What else needs to be done to enable this with coc-clangd? Or is this strictly dependent on vim-lsp-cxx-highlight to support it?

is this strictly dependent on vim-lsp-cxx-highlight to support it?

Yes, vim-lsp-cxx-highlight is needed for semantic highlighting by now.
coc will add semanticTokens support, https://github.com/neoclide/coc.nvim/pull/2756, vim-lsp-cxx-highlight is not needed anymore. Bellow screenshots don't use vim-lsp-cxx-highlight.

good news - thanks. I want to suggest NOT using #if 0 to test this feature, however...as I mentioned above, that particular construct has been part of the c-syntax file in vim for years so you might be fooled into thinking highlighting/lowlighting is working with that when in fact it's just the syntax file doing it. Better to use something like #ifdef _DEBUG or something like that.


Support for VT100 DECOM Orgin Mode

Windows build number: [Version 10.0.16299.248]
If you telnet to mapscii.me, it starts off looking OK (aside from possible unicode issues if you don't have a good enough font). However, if you try to zoom in (pressing the A key), you'll notice that the updated view scrolls into place instead of refreshing smoothly, and the first line of the display will appear to be incorrect.

The reason this is happening is because they're setting the DECOM origin mode at the start of every screen refresh (\033[?6h), and one of the side effects of that sequence is that the cursor is supposed to be reset to the home position. Since Windows doesn't support that sequence, the cursor is in the wrong place when the new screen is output.
The end result is that half of the first line for the updated view is appended to the end of the previous view, and ultimately won't be seen. And the rest of the page then slowly scrolls into position as it's output instead of smoothly overwriting the previous content.
I'm not sure if the screen margins are ever set, so that functionality may not be necessary for mapscii to work correctly, but it definitely seems to be relying on the mode change resetting the cursor to the home position, so it would be good if the Windows console could support that.

Did this get fixed?

Nope, not yet. Still on the backlog.

is DECOM supported at all, or is it just the cursor reset that isn't working?

I don't believe DECOM is supported at all.

Hmm, I'll tell you why I'm curious. I've got a simple multiplexer I'm trying to build, and I'm setting a scroll region to isolate the bottom line for a status bar, a la screen/tmux (using conpty.) I find that the text in the scroll region gets corrupted/cleared at some point, like the cursor is ending up outside the scroll region in the bottom margin. If I force a long dir -R from the root, eventually the "status" bar gets wiped. I'll try to get a better repro and open a new issue. I was wondering if using DECOM was the fix.

God bless you for trying to do this - I've had plans to try and create one for a while now, but there are some other things that are higher priority at the moment.
I doubt that DECOM would be the fix, considering that tmux is able to function perfectly fine w/o it. Presumably the bug would repro without conpty involved - if you can get me a set of VT sequences that repro the behavior, I'll be happy to take a look. (though preferably in a separate issue :P)

The first thing I tried was seeing if tmux/screen had similar issues, but to be honest, they have such different architectures with what I've got that I couldn't be sure. I'll try without conpty to see if there's an issue.

@zadjii-msft -- this is what's currently bothering me most: https://github.com/Microsoft/console/issues/394#

Related to #94?

Marking this one Help-Wanted! This could be a nice pickup task.
DECOM origin mode is described here:

When DECOM is set, the home cursor position is at the upper-left corner of the screen, within the margins. The starting point for line numbers depends on the current top margin setting. The cursor cannot move outside of the margins.
When DECOM is reset, the home cursor position is at the upper-left corner of the screen. The starting point for line numbers is independent of the margins. The cursor can move outside of the margins.

I've spent some time looking into this, and I think it's something I can handle if nobody else is working on it.
My approach would be to add two new booleans in the AdaptDispatch class - one to track the current origin mode, and a second to track the origin mode associated with the saved cursor position.
When the origin mode is relative, there would then need to be adjustments to the line number in the CursorPosition method, the VerticalLinePositionAbsolute method, and the _CursorPositionReport method. The HardReset and SoftReset methods would also require some additions to reset the origin mode to absolute positioning. Oh and the CursorSavePosition and CursorRestorePosition methods would need to save the origin associated with the cursor, as mentioned above.
I'm still investigating some of the edge cases, but I think that's the gist of it. However, I should point out that I'll only be able to get back to this again next weekend, in case someone else is keen to take it on before then.

That certainly seems like the way I'd do it. I doubt that anyone else is going to take a stab at it before that, so I'll just put you on it :P

Good news! This was released for the in-box console with insider build 18945!


Extend module template with the managed CRDs

Description
We need the information about CRDs installed by the module for Kyma Dashboard and Kyma CLI. The information can be extracted from the module manifest, but it is not always the complete list (sometimes CRDs are installed by the module operator). It makes sense to have an explicit list of CRDs in the module template spec.
Reasons
No response
Acceptance Criteria

[ ] module template contains list of managed CRDs

Feature Testing
No response
Testing approach
No response
Attachments
No response

one proposal:
To support the list of managed CRDs, can we put it into some resources, for example, a configmap, or even a dedicated CR. Then LM can deploy it to SKR as a normal module resource during module enabling.
The CLI, busola can use this configmap to cleanup blocking resources during module deleting.
If module is stuck under delete, anyway LM blocks all the module resources to be deleted, so this configmap will present in SRK before module CR get deleted.

one proposal:
To support the list of managed CRDs, can we put it into some resources, for example, a configmap, or even a dedicated CR. Then LM can deploy it to SKR as a normal module resource during module enabling.

I was thinking about adding that information to the module template spec. We can add it to module metadata and then CLI can pass it to the module template. No work for KLM. Just one additional field to process by Kyma CLI create module command. What do you think?

Hi @pbochynski ,
thanks for the answer, actually, I have some concerns if it's good to put this information in module template.

The remote module template at the moment can be immediately removed if delete kyma triggered by kap operator, there is no dependency on it, but if we put this information inside module template, then it means LM should wait for all module get deleted successfully before remove module template. The current logic needs to be changed. But if it's a module resources, anyway, the lifetime of this data is bound to the module, a bit more reliable. btw, is it a valid use case that when kyma is under deleting, we need to use this information?

change module template spec requires a solid definition for the format of this data, at the moment, it's just CRD, probably, with GVK information is fine, but later, if need to add more concrete resources, for example, support label for specific resources, it needs to change again. But this is resolvable, we can define this field as raw json data, and extend the unmarshal logic in the CLI and busola later.

I second you about add it to module metadata, as annotation, then it's more flexible, we just need to be aware of the size limit, but annotation is 265kb, should be enough.

If point 1 is irrelevant, I think we can go with your idea.

I think introducing another config map or another CR for describing module is not the best approach. Let me use the example. Right now module contributors have to provide metadata (module-config.yaml). This is the config for serverless with additional CRD list:
name: kyma-project.io/module/serverless
channel: fast
version: v1.0.3
manifest: serverless-operator.yaml
defaultCR: default-serverless-cr.yaml
beta: false
labels:
  "operator.kyma-project.io/controller-name": "manifest"
  "operator.kyma-project.io/managed-by": "lifecycle-manager"
annotations:
  "operator.kyma-project.io/doc-url": "https://kyma-project.io/#/serverless-manager/user/README"
moduleRepo: https://github.com/kyma-project/serverless-manager.git
managedResources:
  - kind: Function
    group: serverless.kyma-project.io
    version: v1alpha2
  - kind: Serverless
    group: operator.kyma-project.io
    version: v1alpha1

which will produce such module template:
apiVersion: operator.kyma-project.io/v1beta2
kind: ModuleTemplate
metadata:
  name: serverless-fast
  namespace: kcp-system
  labels:
    "operator.kyma-project.io/controller-name": "manifest"
    "operator.kyma-project.io/managed-by": "lifecycle-manager"
    "operator.kyma-project.io/module-name": "serverless"
  annotations:
    "operator.kyma-project.io/doc-url": "https://kyma-project.io/#/serverless-manager/user/README"
    "operator.kyma-project.io/is-cluster-scoped": "false"
spec:
  channel: fast
  data:
    apiVersion: operator.kyma-project.io/v1alpha1
    kind: Serverless
    metadata:
      name: default
    spec:
      dockerRegistry:
        enableInternal: true
  managedResources:
    - kind: Function
      group: serverless.kyma-project.io
      version: v1alpha2
    - kind: Serverless
      group: operator.kyma-project.io
      version: v1alpha1
  descriptor:
     ...

Now about your concerns above.

LifecycleManager is not processing that information at all. It is just the information for Kyma dashboard (or kyma CLI) which resources should be removed if force flag is enabled for module deletion.
ModuleTemplate is already returned as json from API server. Busola can read values directly and pass them in the delete request to the API server. This extension of spec is backward compatible and if we need more info we need to introduce it in the backward compatible way. Anyway only we produce module templates so even incompatible changes can be addressed.
Annotations will be more awkward and harder to parse by clients IMHO.

@valentinvieriu You probably should tell us your preference, as you are a customer of this feature :)

Hi @pbochynski,

LifecycleManager is not processing that information at all. It is just the information for Kyma dashboard (or kyma CLI) which resources should be removed if force flag is enabled for module deletion.

I got your point, I think I need to clarify the use case I'm concerned about more clearly. The use case is when Kyma CR is under deletion, the ModuleTemplate which synced to remote SKR cluster will be deleted, in this case, there is no moduletemplate for Kyma dashboard (or kyma CLI) to consume with. So the question is during cluster deprovision, is it necessary to let customers still possible to use some tools like Kyma CLI to interactive cluster to force delete module so that cluster can be deprovision faster, maybe it's not needed, eventually the cluster should be deleted automatically.
tbh, another reason I'm not telling is, actually I plan to convince you to stop module template sync in the future, but this is just an immature idea atm. I see this module template which synced in remote cluster, they just serve the feature to offer some module metadata, and most of the information in OCM descriptor is irrelevant to the customer. So why not introduce a metadata resource (e.g: a configmap) into the module manifest yaml. This way, LM could deploy and sync it into the SKR cluster, just like any other module resources. By doing this, we could eliminate the need for the current module template synchronization code and simply retain the resource synchronization logic, which simplifies the LM reconciliation logic a lot and also improves the performance of LM. However, introducing more responsibilities into the module template basically makes this option impossible.

Kyma deprovisioning is something different. If Kyma is deprovisioned we already have a logic to clean up all resources in the SKR.
Another topic is what should be synced to the cluster. I see potential optimization in making the module template smaller (skip some irrelevant OCM fields) or consolidating it into one resource. But for me it is just optimization. We need a list of available modules with their metadata in the target cluster.  Right now for that purpose, we have ModuleTemplate CRs. I am not sure if replacing that list with single resource is going to change the KLM performance significantly. If you say that it reduces reconciliation time more than 20% we should start such initiative.
Converting custom resource to config map does not bring any value in my opinion (with CR we get schema and validation)

As we talked with @pbochynski there are two options for determining a list of managed CRDs: https://github.com/kyma-project/lifecycle-manager/issues/1211#issuecomment-1914887213
For now, I will close this issue, if we decide to go that way we will reopen it and continue the work here.


ERROR: illegal image file

ERROR: illegal image file When using bosh_cli_plugin_micro version 3143.
Output below:
Stemcell properties                                          OK

Stemcell info
-------------
Name:    bosh-aws-xen-ubuntu-trusty-go_agent
Version: 3143

  Started deploy micro bosh
  Started deploy micro bosh > Unpacking stemcell. Done (00:00:09)
  Started deploy micro bosh > Uploading stemcelllog writing failed. can't be called from trap context
create stemcell failed: Unable to copy stemcell root image: command 'sudo -n /home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_aws_cpi-2.1.0/scripts/stemcell-copy.sh /tmp/d20151123-32475-1ngmlsr/sc-20151123-32475-1
c9pwj0/image /dev/xvdf 2>&1' failed with exit code 1
Script output:
ERROR: illegal image file: /tmp/d20151123-32475-1ngmlsr/sc-20151123-32475-1c9pwj0/image
:
/home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_aws_cpi-2.1.0/lib/cloud/aws/stemcell_creator.rb:71:in `rescue in copy_root_image'
/home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_aws_cpi-2.1.0/lib/cloud/aws/stemcell_creator.rb:54:in `copy_root_image'
/home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_aws_cpi-2.1.0/lib/cloud/aws/stemcell_creator.rb:19:in `create'
/home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_aws_cpi-2.1.0/lib/cloud/aws/cloud.rb:493:in `block in create_stemcell'
/home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_common-1.3143.0/lib/common/thread_formatter.rb:49:in `with_thread_name'
/home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_aws_cpi-2.1.0/lib/cloud/aws/cloud.rb:473:in `create_stemcell'
/home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_cpi-1.3143.0/lib/cloud/internal_cpi.rb:22:in `invoke_cpi_method'
/home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_cpi-1.3143.0/lib/cloud/internal_cpi.rb:10:in `method_missing'
/home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_cli_plugin_micro-1.3143.0/lib/bosh/deployer/instance_manager.rb:228:in `block (2 levels) in create_stemcell'
/home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_cli_plugin_micro-1.3143.0/lib/bosh/deployer/instance_manager.rb:85:in `step'
/home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_cli_plugin_micro-1.3143.0/lib/bosh/deployer/instance_manager.rb:227:in `block in create_stemcell'

Was able to work around the issue by manually applying the fix from: https://github.com/cloudfoundry-incubator/bosh-aws-cpi-release/commit/d99ce44eb7f47d9e2b4573a96cdc1b2881df3481 to /home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_aws_cpi-2.1.0/scripts/stemcell-copy.sh

Is this a bosh-bootstrap bug or bosh_cli_plugin_micro bug? And is it caused by a regression in new stemcell?
On Mon, Nov 23, 2015 at 2:44 AM, Ruben Koster<EMAIL_ADDRESS>wrote:

Was able to work around the issue by manually applying the fix from: https://github.com/cloudfoundry-incubator/bosh-aws-cpi-release/commit/d99ce44eb7f47d9e2b4573a96cdc1b2881df3481 to /home/ubuntu/.rvm/gems/ruby-2.1.5/gems/bosh_aws_cpi-2.1.0/scripts/stemcell-copy.sh
Reply to this email directly or view it on GitHub:
https://github.com/cloudfoundry-community/bosh-bootstrap/issues/324#issuecomment-158902144

It is a bosh_cli_plugin_micro bug. Also encountered it when using a different stemcell. Will check to see when it was introduced.

@cppforlife could the above be an bosh_cli_plugin_micro issue?

not micro cli specific. im guessing this is os specific.
error comes from here: https://github.com/cloudfoundry-incubator/bosh-aws-cpi-release/blob/master/src/bosh_aws_cpi/scripts/stemcell-copy.sh. its probably related to grep regex inconsistencies on os-es.
Sent from my iPhone

On Nov 23, 2015, at 11:19 AM, Ruben Koster<EMAIL_ADDRESS>wrote:
@cppforlife could the above be an bosh_cli_plugin_micro issue?
—
Reply to this email directly or view it on GitHub.

@cppforlife The last commit in that file fixes something related the the regex. In which version of the bosh_aws_cpi gem will this fix be included?

Worked around it by using the upstream stemcell-copy script which is loaded from the PATH by the cpi by default.

This workaround needs to be included in bosh_bootstrap unless a new versions of the bosh_aws_cpi gem will be published. @cppforlife @drnic


Command "python setup.py egg_info" failed with error code 1

pip install xgboost, have a error:Command "python setup.py egg_info" failed with error code 1 in /private/tmp/pip-build-OQHKqM/xgboost/
my system is macOS 10.12.4
python version is 2.7.10
I have install gcc from brew firstly.
I have tried sudo pip install xgboost.

I have solved it. just reinstall python 2.7 by brew.


Content filling and bug hunting

Bro_n_Bro in header and in home section.
Networks: update text for Omniflix to "We love NFTs a LOT "
Contributions: add all networks.

Closed in honor of https://github.com/bro-n-bro/bro_site/issues/5


Consider sorting the file list by path before processing

It's currently difficult to know how far get_cover_art art has progressed in processing a folder with many subfolders.
Sorting the file list prior to processing will allowe users to guage how far progressed they are by having reference to the currently processed folder relative to the director list.

This is a good idea and easy to do, done!  If you grab the latest version (1.5.10) the file list should be sorted.


ActionView::Template::Error in admin/radar_entries#index

Exception in Hacken.in
ActionView::Template::Error in admin/radar_entries#index
PG::UndefinedColumn: ERROR:  column radar_entries.event_id does not exist
LINE 1: ...CT  1 AS count_column FROM "radar_entries"  WHERE "radar_ent...
^
: SELECT COUNT(count_column) FROM (SELECT  1 AS count_column FROM "radar_entries"  WHERE "radar_entries"."event_id" IN (568, 336, 539) AND "radar_entries"."state" = 'UNCONFIRMED' LIMIT 30 OFFSET 0) subquery_for_count
View on Bugsnag
Stacktrace
gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:822 - async_exec
gems/activerecord-4.1.8/lib/active_record/connection_adapters/postgresql_adapter.rb:822 - block in exec_no_cache
gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract_adapter.rb:373 - block in log

View full stacktrace

If you are a curator, you can't see the radar entries. It crashes with this exception.
I think @skade "discovered" this one.

Phew, I was just going through the issue list to see if that is already reported...


Release new version 0.5.3

Release new version 0.5.3

Coverage increased (+3.08%) to 79.157% when pulling 0454b8a3c0f5110ba117f8e861bb254564325675 on dev into 4eb23da04b691d4cd2349564a297312a8b165029 on master.


Upload new localization ui image for documentation to reference.

#sign-off

@msmimart: I'm sorry - only the author of this article, @, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@stevenxzhou Before we merge the image, could you reduce the size so that no dimension (height or width) is larger than 1200 pixels? This is a limit that's indicated in the internal contributor guide. The image currently is 1816 x 1125. Thanks. #hold-off

@stevenxzhou Is it possible that, after resizing the image, you can add the image to PR #https://github.com/MicrosoftDocs/azure-docs/pull/65936 and close this PR? It's safest to merge a new image and its MD reference in the same PR. If not, we'll merge them at the same time.

@ktoliver I have uploaded the image to the doc update PR. https://github.com/MicrosoftDocs/azure-docs/pull/65936 can you please take look. Thank you!!


Regression between "--network default" vs "--network bridge" and "--link" (works with "default", does not work with "bridge")

It would appear that we've got a regression related to --network default vs --network bridge and their interactions with --link.  In 1.11, using --link with either no --net flag or --net bridge was equivalent, but with the build of master I compiled today, --net bridge causes links to no longer function appropriately.
I discovered this because I use network_mode: bridge in some of my docker-compose.yml files to force certain containers to be in the standard bridge network instead of creating a new custom network.  Now, I can easily work around that issue by using network_mode: default instead, but that feels hacky unless it's the intended behavior (especially given that this functioned appropriately on Docker 1.11).
$ docker version
Client:
 Version:      1.12.0-dev
 API version:  1.25
 Go version:   go1.6.3
 Git commit:   d602391
 Built:        Fri Jul 22 10:54:41 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.0-dev
 API version:  1.25
 Go version:   go1.6.3
 Git commit:   d602391
 Built:        Fri Jul 22 10:54:41 2016
 OS/Arch:      linux/amd64

$ docker info
Containers: 13
 Running: 13
 Paused: 0
 Stopped: 0
Images: 4545
Server Version: 1.12.0-dev
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 3430
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: overlay host bridge null
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.11-gentoo
Operating System: Gentoo/Linux
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.4 GiB
Name: nameless
ID: XTOG:WDQV:MC46:UH5F:CQXH:VTNK:CDR6:7BEE:JDRJ:4U2D:LUQM:EYN2
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Username: tianon
Registry: https://index.docker.io/v1/
Insecure Registries:
 <IP_ADDRESS>/8
 <IP_ADDRESS>/12
 <IP_ADDRESS>/16
 <IP_ADDRESS>/8

Steps to reproduce the issue:
$ docker run -d --name test busybox top
919e3d99bcdd2275ab72cdefe8695319830353e90444180205142c76cd782d3d
$ docker run --rm --link test busybox cat /etc/hosts
<IP_ADDRESS>	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
<IP_ADDRESS>	test 919e3d99bcdd
<IP_ADDRESS>	291f33ed018e
$ docker run --rm --link test --net default busybox cat /etc/hosts
<IP_ADDRESS>	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
<IP_ADDRESS>	test 919e3d99bcdd
<IP_ADDRESS>	04539d360b76
$ docker run --rm --link test --net bridge busybox cat /etc/hosts
<IP_ADDRESS>	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
<IP_ADDRESS>	74a47a4e8556

Expected to see instead:
$ docker run --rm --link test --net bridge busybox cat /etc/hosts
<IP_ADDRESS>	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
<IP_ADDRESS>	test 919e3d99bcdd
<IP_ADDRESS>	04539d360b76

(firing up Docker 1.11 now to verify the previous behavior; will post verified results once I've got them)

$ docker version
Client:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Wed Apr 27 00:34:20 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Wed Apr 27 00:34:20 2016
 OS/Arch:      linux/amd64
$ docker run -d --name test busybox top
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
8ddc19f16526: Pull complete
Digest: sha256:a59906e33509d14c036c8678d687bd4eec81ed7c4b8ce907b888c607f6a1e0e6
Status: Downloaded newer image for busybox:latest
9b7052437ffa9b7975e15cc117b802315731b543747ef30eb7fb1cea2e7a0878
$ docker run --rm --link test busybox grep test /etc/hosts
<IP_ADDRESS>	test 9b7052437ffa
$ docker run --rm --link test --net default busybox grep test /etc/hosts
<IP_ADDRESS>	test 9b7052437ffa
$ docker run --rm --link test --net bridge busybox grep test /etc/hosts
<IP_ADDRESS>	test 9b7052437ffa

/cc @mavenugo @mrjana

(still having trouble getting the docker:1.12.0-rc4 images pushed properly -- issues with the official images signing system, but here's rc3's results:)
$ docker version
Client:
 Version:      1.12.0-rc3
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   91e29e8
 Built:        Sat Jul  2 00:17:11 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.0-rc3
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   91e29e8
 Built:        Sat Jul  2 00:17:11 2016
 OS/Arch:      linux/amd64
$ docker run -d --name test busybox top
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
8ddc19f16526: Pull complete
Digest: sha256:a59906e33509d14c036c8678d687bd4eec81ed7c4b8ce907b888c607f6a1e0e6
Status: Downloaded newer image for busybox:latest
fec9255a59554b13343a0eaf2a0d1c59d6d8c553ffdff959a7f82f23bfb6d065
$ docker run --rm --link test busybox grep test /etc/hosts
<IP_ADDRESS>	test fec9255a5955
$ docker run --rm --link test --net default busybox grep test /etc/hosts
<IP_ADDRESS>	test fec9255a5955
$ docker run --rm --link test --net bridge busybox grep test /etc/hosts
$

/cc @tiborvass FYI


Unique ID Generation for Headings with Duplicate Titles

This commit addresses the issue where headings without an explicit ID resulted in ambiguous IDs for repeated headings (e.g., multiple "Summary" headings).
Changes made:

PHP:

When a heading lacks an ID, a unique identifier is now generated by appending the heading's index to its content-derived ID. This ensures each heading ID is distinct, even when the heading text is repeated across the document.

Issue: #12


Create auto package action on sync

We need an action on "sync" that will automatically run the packager so that updates to global are pushed as a new release.

pr created https://github.com/N6REJ/.wow-settings/pull/21****


make doc great again

What problem does this PR solve?
make doc is broken. This PR will fix it.
Release note

No release note

It looks really weird that make doc requires a toolchain different from the one defined in rust-toolchain.
I think we should update the toolchain of TiKV to an approriate version to solve the problem.

@sticnarf Well you may be right, since https://github.com/rust-lang/rust/pull/83412 is merge.


"type: null" gives error

My code:
props: {
  value: {
    type: null, // this means "any type"
    required: true
  },
}

I getting error:

If i change null to other type - every thing works.

null isn't a valid Vue type
https://vuejs.org/v2/guide/components-props.html#Type-Checks

A few hours ago I did a PR, but he was not counted due to failures on the site. https://outage.report/github

GitHub does not work, when it will work I will do PR, there I fixed two bugs.