multiple builder callbacks that match the same k8s object will only cause the first one to be called.

Is your feature request related to a problem? Please describe.
at npx pepr dev/build identify if multiple builder callbacks could match the same object.
When(a.ConfigMap)
  .IsCreated()
  .Mutate(request => {
      // will only be called for Created() requests
  });

When(a.ConfigMap)
  .IsCreatedOrUpdated()
  .Mutate(request => {
  // will only be called for Updated() requests but not Created() requests
  });

example 2:
// this will always be called, regardless of the data.
When(a.ConfigMap)
  .IsCreatedOrUpdated()
  .Mutate(request => {
      if (request.Raw.data?.["hello"]) {
        // DO SOMETHING
      }
  });

// this will NEVER be called, regardless of the data.
When(a.ConfigMap)
  .IsCreatedOrUpdated()
  .Mutate(request => {
      if (!request.Raw.data?.["hello"]) {
        // DO SOMETHING ELSE
      }
  });

// THIS IS THE CORRECT WAY:
When(a.ConfigMap)
  .IsCreatedOrUpdated()
  .Mutate(request => {
      if (request.Raw.data?.["hello"]) {
        // DO SOMETHING
      } else {
         // DO SOMETHING ELSE
      }
  });

if multiple builders match the same object, only the first one will be called. We don't chain them (and we do it silently, which is confusing)

Revised to confirm to Feature Request Template:
Describe the solution you'd like

Given a user has multiple actions operating on the same resource
When npx pepr dev/build is issued
Then the problem is identified by Pepr Core and the dev run/build fails describing the problem to the user

Describe alternatives you've considered
(optional) A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

This should be chained right now--are we sure they are not? If you're running in a debugger, you very well could run into issues if you're not careful with multiple at once, but we don't do anything to reduce the action callbacks that I'm aware of currently.

Assigning this for a spike, going to investigate this statement by @jeff-mccoy. There is an remedy for this through identification of the bindings

I woke up and it occurred to me how to fix this, so I've created a PR that demonstrates the behavior change. Since depending on the application, the problem may never happen, warn might be the right approach.

We are not able to reproduce any issue here, it seems like they are both being called in the even the case of overlap. We recently submitted a PR for chaining Validates that simplify the process of multiple validates operating on the same resource. We are closing this for now but feel free to open back up should there be a need.
https://github.com/defenseunicorns/pepr/pull/405


[i18nIgnore] (chore): Add tab component

Description (required)

Add tab component to tip in Keystatic page

Related issues & labels (optional)

Closes #
Suggested label:

How come there are failed Checked Links ? This PR doesn't even include one 🤔. At least the fragment and scripts are displayed correctly on Deployed Preview 😊

Thanks for adding this, @jacobthesheep!
And thanks for checking the preview and reporting back, @at-the-vr ! That's super helpful!
I've seen these failed link checks before, and these particular ones that don't have anything to do with the PR are usually  just a fluke and will pass if I rerun the tests. Doing that now... :raised_hands:

Checks have passed! I will tag @simonswiss in here because I realized that even Keystatic's own docs only show npm and not the other package managers. There's always the possibility that they haven't tested and/or don't (want to) support the other package managers... but I'll merge this now and I guess the best way to find out is to have someone try and complain!  :joy:
@jacobthesheep , did you try testing creating with pnpm and yarn? It seems safe to me, but Simon is now looped in, and if we get complains, we can revert to the simple npm install instructions!


fix: read light from front camera on iOS (optional)

I notice that on iOS, plugin reads light from camera, but always read from back camera (I test on iPhone 15). I added an optional parameter to force read data from front camera.

The new parameter was called useFrontCameraOnIOS, by default it's false.

I believe that {bool useFrontCameraOnIOS = false} is not an appropriate name for our interface.
I suggested secondarySensor or frontCamera[only] for naming. and we add documentation for this field as this feature works only on iOS devices and hasn't functionality on other platforms


Link to meteorhacks article not working in the docs

I only get an error message that a secure connection cannot be established.

for me the link is woking. I am using chrome 47

Yes, it's working now for me as well, so I am closing this.

The link is not working anymore https://meteorhacks.com/implementing-an-instant-search-solution-with-meteor.html. Maybe the content of the article should be included in the docs of this repo?


Support autocompletion and show hint for SQL table and column names in CodeMirror editor

Should be partially covered by #323


Add Trino support

Trino (formerly known as Presto) is a distributed SQL query engine designed to query large data sets distributed over one or more heterogeneous data sources.
It's an open-source project, using the Apache 2.0 license, and the JDBC driver is freely redistributable.
Trino is ANSI SQL compliant.
Tested using this script: https://gist.github.com/nineinchnick/d3496c05939856c1b0858af99457d85a

Any chance this can get merged? We also need Trino support in Flyway

We also need flyway support for Trino/Iceberg. Would love to have this change merged in.

Bump!

I just rebased this. @juliahayward can you take a look?

I'm not working on Flyway any more, having moved on to a new role... @madninjaskillz is this one for you?

Is there anything missing to merge this PR?

No idea .. currently the PR needs to be rebased, but it looks like nobody from the flyway project is available or willing to review and merge anyway. We dont know who is active from the git commit log and other channels. Maybe someone from the project can provide guidance.

I'll move this to https://github.com/flyway/flyway-community-db-support

Hi @nineinchnick I could not find this in https://github.com/flyway/flyway-community-db-support. We would like to also add support for Trino/Iceberg and we can resume work on this one.

I haven't yet found time to port this PR to the other repo. This is a very low priority for me, so if you want to try, go ahead!


[feature request] Support async version of DrawTarget.

Currently embedded-graphics only support interrupt-driven concurrency (I mean that if you want to do work while some DMA is writing out data to a screen, you have to use an interrupt). Using async it should be possible to write a version of DrawTarget that allows other work to be done while it is waiting for I/O.
I think this feature request is blocked on async traits, which in turn is blocked on GATs, so it is not (yet) possible to implement.

For buffered displays, the flush fn isnt in trait at all right?
Thats the bigger cost call I think, I was able to just asyncify it
https://github.com/jacobrosenthal/ssd1331/tree/async
The bigger issue going to be to pick an async trait while the community explores. I used the embassy one there

Experimenting in drivers is a good approach for sure, and I agree that the flush functionality for buffered drivers is going to be a large part of the total draw time.
The current e-g iterator API lends itself well to being interrupted, so I'm not sure I'd see a need to add async support to e-g itself, although the decision will be much easier to make when official language support for async traits, etc is added.

So my primary motivation is that writing pixels out in drivers can be done with DMA, while the cpu does something else. So I need some way to make a draw call (that calls out to drivers to push pixels to a display) say "Hey I've set the DMA up. Go do something else and I'll let you know when it's done." This is exactly the model that async/await in Rust supports.
In my case the pixels are written out using SPI, and a whole screen (320 * 320 * 16= 1_638_400 bits) takes a reasonable fraction of a second. I lose a lot of responsiveness if I stop the world while this is happening.

I think I'm mis-understanding a little bit here. I have a nrf52832 with a st7789 display. There isn't enough member on-chip to hold a framebuffer, so pixels have to be generated then sent directly to the display (over SPI). In the ideal case (not how it works for me yet) you have 2 buffers, and fill one with pixels while another is going out over SPI via DMA. Then once both jobs are done, you set the second buffer off over DMA and fill the first. Rinse and repeat until you've sent out data for the whole screen. So in this scenario, is "flushing" setting off the DMA for one buffer or the other?

The current e-g iterator API lends itself well to being interrupted, so I'm not sure I'd see a need to add async support to e-g itself, although the decision will be much easier to make when official language support for async traits, etc is added.

Can you say more about what you mean by this?

Thanks for the deeper explanation. I think I understand what you mean now - my comment above doesn't make much sense.
IIUC, you'd like something like this pseudo-Rust (iterators can't do chunks() or produce slices, pixel coords aren't checked for contiguousness, etc, etc):
impl DrawTarget for Disp {
    async fn draw_iter<I>(&mut self, pixels: impl Iterator<Item = Pixel>) {
        for chunk in pixels.into_iter().chunks(16) {
            self.fill_half_buf(&chunk);
            // Executor can go do other stuff while this is waiting
            self.swap_and_send_half_buf().await;
        }
    }
}

Which is currently impossible with the non-async DrawTarget. My original comment was suggesting that you could do the async purely in the display driver and leave e-g alone but that won't work :facepalm:.
I'd be tempted to use async_trait with a new AsyncDrawTarget under a feature flag if we want to experiment with this on the e-g side. async_trait is luckily no_std, so might be ok but are there any other limitations you know of?

Can you say more about what you mean by this?

Please ignore me - I didn't think this through properly.

What is the current state of this async implementation of the trait ? I would be really interested to have this for the same DMA purpose that was suggested initially. Async functions in trait are now stabilized (we some caveats) since rust 1.75 without the need of the extra dependency. So we should be able to add this to embedded-graphics. Is there any other difficult point that I missed ?

Is this a feature e-g would be interested in having developed further?
As in a more formalized version using something like the maybe_async macro like @ValouBambou suggested in #747


[36] Add Joe Groff's write up of two proposals

Thanks @BasThomas !
I think we covered this last issue. Any new information for this week?

🤔, overlooked that one. Other than this, nothing's been happening on swift-evolution. Had a quick look at swift, but didn't find anything interesting immediately.


cookie as session store

Hello! How to implement signed-cookie based session store? For setup cookies we need access to context or use returned value from write-session as new session key (like ring session stores).

Hmm. The current design does not allows that, so I think we can rethink it and improve it for the next version.

The session storage is refactored and will be available on the next version (0.8.0) if you want hack with it you can use the 0.8.0-SNAPSHOT.
Also, a jws cookie signed storage is implemented.


translation functions document

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Only parts completed, please do not merge. This pr was created to prevent others from doing the same work.
Category:

Document

@zhang2014 maybe we should merge at least partial result?

@blinkov
There are very few parts that are not completed. maybe it is better to wait for this part to be completed before merging?  And I need to review the documents at least once.

@zhang2014 as you wish, that was just a suggestion

@zhang2014 any updates?

The data types document is not synchronized, the link here may report an error?
Maybe we should think about synchronization between documents in different languages.
For example, if documents are found to be updated in CI, create github issues by scanning [来源文章](https://clickhouse.yandex/docs/en/query_language/functions/ip_address_functions/) <!--hide--> of other documents and finding the contents to be synchronized.

@blinkov The translation has been completed and can be reviewed @sundy-li

LGTM, @zhang2014  I can't comment changes due to github bugs.
Request URL: https://github.com/yandex/ClickHouse/pull/5196/review_comment/create
Request Method: POST
Status Code: 422 Unprocessable Entity
Remote Address: <IP_ADDRESS>:443
Referrer Policy: no-referrer-when-downgrade

Some improvements
格式话 => 格式化
code point could be translated to 字符 or 码位
返回此字符串的Unicode code point长度 =>  返回此字符串的Unicode字符长度
以code point为单位  =>  以unicode字符为单位
但位置以Unicode code points返回  => 但位置以Unicode为单位计算


Add Creation of Tests

Currently, there is now way of creating tests.
This should be added, starting with "unit" tests, where the user gives an input and compares the lambda output with the expected output provided by the user

Maybe we could even add some kind of QuickCheck support at some point


Multi Domain Sentiment Analysis Dataset (MDSA)

I'll come back to this one in sometime :)

Also if you would use xml.etree.ElementTree to parse the XML it would be awesome, because right now you're using an external dependency xmltodict

Also if you would use xml.etree.ElementTree to parse the XML it would be awesome, because right now you're using an external dependency xmltodict

Its pseudo xml so elementtree fails. xmltodict seems to be working quite good for this. do we have examples of pseudo xml datasets?

for the other pseudo xml the text is parsed manually

Can you add xmltodict to the test dependencies in setup.py please to fix the CI please ?

Also can you add the dataset card with the tags and run make style ?

Hi :) have you had a chance to fix the test dependency and apply make style ?
Feel fee to ping me when it's ready for a review

Thanks for your contribution, @abhishekkrthakur. Are you still interested in adding this dataset?
We are removing the dataset scripts from this GitHub repo and moving them to the Hugging Face Hub: https://huggingface.co/datasets
We would suggest you create this dataset there. Please, feel free to tell us if you need some help.


Suggested edits for Notebook 3

The present example in notebook 3 looked odd to me with the red x sort of floating.
I would consider starting with value = True. Then mention in text if value = False the red x for invalid will appear.

I realize that these are probably from the documentation from widgets but it might look cleaner if the text doesn't overrun the field. For example, Pizza toppings: becomes truncated when the widget is displayed.

It's not clear in these HTML widgets what the placeholder is doing:

Next link 404s

Truncation is discussed in Notebook 4. Perhaps reference here in the text and leave the above examples as is.

@willingc -- thanks a ton for all of these detailed comments. They are very helpful!
@jasongrout can confirm, but as far as I can tell, placeholder doesn't actually do anything for the HTML widgets, or for Label. I dropped it from those, and changed one of the Text widget examples to show what the placeholder does (display text until the user types in the textbox or textarea).


My obs lacks WISH stream option

I built obs on GNU/Linux with -DENABLE_WEBRTC=ON, but then  in the stream options, I don't see WISH like in the screenshot in the readme of this project. Am I missing something? I'm using the current master of obs commit 3a1035576eb6a7c60c1757b3498d97da5d7bfb3b

typo: the title should say WHIP not WISH.

I figured out why. I ran obs --verbose | grep webrtc and I see this:
error: os_dlopen(../../obs-plugins/64bit/obs-webrtc.so->../../obs-plugins/64bit/obs-webrtc.so): libdatachannel.so.0.20: cannot open shared object file: No such file or directory
fixed with
cd $HOME/obs-studio-portable/bin/64bit
cp -a /usr/local/lib/libdatachannel.so* ../../obs-plugins/64bit


LDS ACK ERROR Address already in use

Logs from gateway:
-ingressgateway-5d5cb5fb56-lznx8.istio-system~istio-system.svc.cluster.local --max-obj-name-len 189 --local-address-ip-version v4 --allow-unknown-fields -l warning --component-log-level misc:error]
[2019-07-19 16:13:13.389][17][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:86] gRPC config stream closed: 14, no healthy upstream
[2019-07-19 16:13:13.389][17][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:49] Unable to establish new stream
2019-07-19T16:13:14.586776Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:16.586389Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:18.586318Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:20.586275Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:22.586265Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
[2019-07-19 16:13:23.476][17][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:86] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers. reset reason: connection failure
2019-07-19T16:13:24.588013Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:26.586300Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:28.586353Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:30.586144Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:32.586350Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
[2019-07-19 16:13:34.266][17][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:86] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers. reset reason: connection failure
2019-07-19T16:13:34.586376Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:36.586148Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:38.586188Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:40.586400Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:42.586399Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:44.586416Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
[2019-07-19 16:13:46.212][17][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:86] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers. reset reason: connection failure
2019-07-19T16:13:46.586313Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:48.586311Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:50.586261Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:52.586396Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:54.586225Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:56.586250Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:13:58.586382Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:00.586805Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:02.586694Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:04.586459Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:06.586552Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:08.586688Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
[2019-07-19 16:14:08.817][17][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:86] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers. reset reason: connection failure
2019-07-19T16:14:10.587063Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:12.586770Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:14.586623Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:16.592334Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:18.586917Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:20.587009Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
[2019-07-19 16:14:20.766][17][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:86] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers. reset reason: connection failure
2019-07-19T16:14:21.889337Z     info    watchFileEvents: "/etc/certs/..2019_07_19_16_14_21.981203222": CREATE
2019-07-19T16:14:21.889400Z     info    watchFileEvents: "/etc/certs/..2019_07_19_16_14_21.981203222": MODIFY|ATTRIB
2019-07-19T16:14:21.889486Z     info    watchFileEvents: "/etc/certs/key.pem": CREATE
2019-07-19T16:14:21.889502Z     info    watchFileEvents: "/etc/certs/root-cert.pem": CREATE
2019-07-19T16:14:21.889511Z     info    watchFileEvents: "/etc/certs/cert-chain.pem": CREATE
2019-07-19T16:14:21.889559Z     info    watchFileEvents: "/etc/certs/..data_tmp": RENAME
2019-07-19T16:14:21.889597Z     info    watchFileEvents: "/etc/certs/..data": CREATE
2019-07-19T16:14:21.889641Z     info    watchFileEvents: "/etc/certs/..2019_07_19_16_13_06.480796546": DELETE
2019-07-19T16:14:22.586178Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:24.586201Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:26.586273Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:28.586555Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:30.588143Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:31.889503Z     info    watchFileEvents: notifying
2019-07-19T16:14:31.889713Z     info    Received new config, resetting budget
2019-07-19T16:14:31.889725Z     info    Reconciling retry (budget 10)
2019-07-19T16:14:31.889747Z     info    Epoch 1 starting
2019-07-19T16:14:31.893702Z     info    Envoy command: [-c /etc/istio/proxy/envoy-rev1.json --restart-epoch 1 --drain-time-s 45 --parent-shutdown-time-s 60 --service-cluster istio-ingressgateway --service-node router~<IP_ADDRESS>~istio-ingressgateway-5d5cb5fb56-lznx8.istio-system~istio-system.svc.cluster.local --max-obj-name-len 189 --local-address-ip-version v4 --allow-unknown-fields -l warning --component-log-level misc:error]
[2019-07-19 16:14:31.916][17][warning][main] [external/envoy/source/server/server.cc:537] shutting down admin due to child startup
[2019-07-19 16:14:31.916][17][warning][main] [external/envoy/source/server/server.cc:546] terminating parent process
[2019-07-19 16:14:31.920][36][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:86] gRPC config stream closed: 14, no healthy upstream
[2019-07-19 16:14:31.920][36][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:49] Unable to establish new stream
2019-07-19T16:14:32.586395Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:34.586497Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:36.586293Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:38.586475Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:40.586359Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
[2019-07-19 16:14:42.536][36][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:86] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers. reset reason: connection failure
2019-07-19T16:14:42.586659Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
[2019-07-19 16:14:43.090][17][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:86] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers. reset reason: connection failure
2019-07-19T16:14:44.587009Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:46.586476Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:48.590667Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
2019-07-19T16:14:50.586902Z     info    Envoy proxy is ready
[2019-07-19 16:15:11.089][17][warning][config] [external/envoy/source/common/config/grpc_mux_subscription_impl.cc:73] gRPC config for type.googleapis.com/envoy.api.v2.Listener rejected: Error adding/updating listener(s) <IP_ADDRESS>_80: cannot bind '<IP_ADDRESS>:80': Address already in use
[2019-07-19 16:15:19.151][17][warning][config] [external/envoy/source/common/config/grpc_mux_subscription_impl.cc:73] gRPC config for type.googleapis.com/envoy.api.v2.Listener rejected: Error adding/updating listener(s) <IP_ADDRESS>_80: cannot bind '<IP_ADDRESS>:80': Address already in use
[2019-07-19 16:15:44.679][17][warning][main] [external/envoy/source/server/server.cc:426] caught SIGTERM
2019-07-19T16:15:44.696183Z     info    Epoch 0 exited normally

Logs from pilot:
2019-07-19T16:15:19.373162Z     warn    ads     ADS:LDS: ACK ERROR <IP_ADDRESS>:33152 router~<IP_ADDRESS>~istio-ingressgateway-5d5cb5fb56-lznx8.istio-system~istio-system.svc.cluster.local-56 (istio-ingressgateway-5d5cb5fb56-lznx8.istio-system) node:<id:"router~<IP_ADDRESS>~istio-ingressgateway-5d5cb5fb56-lznx8.istio-system~istio-system.svc.cluster.local" cluster:"istio-ingressgateway" metadata:<fields:<key:"CONFIG_NAMESPACE" value:<string_value:"istio-system" > > fields:<key:"ISTIO_META_INSTANCE_IPS" value:<string_value:"<IP_ADDRESS>,<IP_ADDRESS>,fe80::3488:12ff:fea3:3c53" > > fields:<key:"ISTIO_PROXY_SHA" value:<string_value:"istio-proxy:a975561b980463f08689d3debe33bb9eefc80c3d" > > fields:<key:"ISTIO_PROXY_VERSION" value:<string_value:"1.1.3" > > fields:<key:"ISTIO_VERSION" value:<string_value:"1.2.2" > > fields:<key:"POD_NAME" value:<string_value:"istio-ingressgateway-5d5cb5fb56-lznx8" > > fields:<key:"ROUTER_MODE" value:<string_value:"sni-dnat" > > fields:<key:"istio" value:<string_value:"sidecar" > > > locality:<region:"us-central1" zone:"us-central1-a" > build_version:"a975561b980463f08689d3debe33bb9eefc80c3d/1.11.0-dev/Clean/RELEASE/BoringSSL" > type_url:"type.googleapis.com/envoy.api.v2.Listener" response_nonce:"e5021772-e732-4641-9a86-18278acd5b33" error_detail:<code:13 message:"Error adding/updating listener(s) <IP_ADDRESS>_80: cannot bind '<IP_ADDRESS>:80': Address already in use" >
2019-07-19T16:15:19.374483Z     info    ads     LDS: PUSH for node:badhealth-df448f8d5-4xglz.service-graph00 listeners:31

Version: 1.2.2

@mandarjog have you ever seen this before?

I have not been able to reproduce this yet, but I haven't tried hard either. If we cannot reproduce we can lower the priority

Presumably the same as #15658. Will update if I see this again


Moving containers around causes cluster to go down

I am running a stack of 3 VMQ container and 1 master container for container discovery purposes. Works fine.
I just set one Docker host to DRAIN and it moved some containers around, then the whole cluster stopped accepting connections and all my clients went down with it.
 They also complained that 3 cluster nodes were not reachable and the docs say that if a netsplit occurs (I don't know if 3-4 unreachable cluster nodes count as a netsplit) it stops accepting connections.
vernemq@9b128c6529b4:~$ vmq-admin cluster show
+---------------------+---------+
| Node                | Running |
+---------------------+---------+
|<EMAIL_ADDRESS>| false   |
+---------------------+---------+
|<EMAIL_ADDRESS>| true    |
+---------------------+---------+
|<EMAIL_ADDRESS>| true    |
+---------------------+---------+
|<EMAIL_ADDRESS>| true    |
+---------------------+---------+
|<EMAIL_ADDRESS>| true    |
+---------------------+---------+
|<EMAIL_ADDRESS>| false   |
+---------------------+---------+
|<EMAIL_ADDRESS>| false   |
+---------------------+---------+
|<EMAIL_ADDRESS>| false   |
+---------------------+---------+
|<EMAIL_ADDRESS>| false   |
+---------------------+---------+

Questions:

Is it possible at all to move a running master container without consequences?
Why would 3-4 cluster members being down screw up the entire cluster?
Why are these cluster nodes not removed from the cluster automatically when the container exits?

In the end I fixed it by opening up a shell of one of the containers and manually removing the running=false nodes:
vmq-admin cluster leave<EMAIL_ADDRESS>Thanks!

I have since learned about this PR https://github.com/vernemq/docker-vernemq/issues/191 which is merged and present in my container (running version 1.10.3).
The following code is present in /usr/sbin/start_vernemq
# SIGTERM-handler
sigterm_handler() {
    if [ $pid -ne 0 ]; then
        # this will stop the VerneMQ process, but first drain the node from all existing client sessions (-k)
        if [ -n "$VERNEMQ_KUBERNETES_HOSTNAME" ]; then
            terminating_node_name=VerneMQ@$VERNEMQ_KUBERNETES_HOSTNAME
        elif [ -n "$DOCKER_VERNEMQ_SWARM" ]; then
            terminating_node_name=VerneMQ@$(hostname -i)
        else
            terminating_node_name=VerneMQ@$IP_ADDRESS
        fi
        /vernemq/bin/vmq-admin cluster leave node=$terminating_node_name -k > /dev/null
        /vernemq/bin/vmq-admin node stop > /dev/null
        kill -s TERM ${pid}
        exit 0
    fi
}

Draining a docker node does not remove the containers I believe, it just stops them and spins up new ones on other nodes. Does this mean the SIGTERM handler is not called?

@Fossil01 I do not know what DRAINing a Docker node is or implies. I'll have to read up on it.

@ioolkos It just empties the host of all running containers and starts them on other hosts so you can do maintenance, reboot, troubleshoot etc.

A netsplit situation occurs if any of the nodes is down. To be available in a netsplit you have to enable the allow_register....etc config values but I guess you have that. The issue is then likely related to the Docker draining.

I have seen that and might change the config to allow subbing on netsplit etc. But I am more curious as of why my containers were not removed from the cluster prior to stopping the containers by Docker when I drained one host.
If it is removed from the cluster before going down then there should be no netsplit at all right? It should just continue running the cluster with one less member.

Any info on my last post? :-)

Closing due to no follow-ups on our part

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.


feat(codemagic_app_preview): remove workaround for triggering the build with a label

Closing it for now. Too lazy to work on that.


Final tool detail work for now

New features:

Optional types that are listed with a question mark, e.g. "Int?" have the ? stripped off for display. That's a WDL thing.
Data type is selectable
Cancel button
Show attribute errors (and missing required values) with an error icon with tooltip

Not implementing the autosuggesting of "this.foo" data attributes. React-select is not playing well with rc-table.

Not implementing the autosuggesting of "this.foo" data attributes. React-select is not playing well with rc-table.

Will you please file an issue for that so we can follow-up separately?

Will do


Codecov migration to marketplace app

Hi, Tom from Codecov here.
We noticed that you are using Codecov with fairly high frequency, and we’re so excited to see that! However, because you are not using our app, you may have experienced issues with uploading reports or viewing coverage information. This is due to rate-limiting issues from GitHub.
In order to prevent any future outages, we ask that you move over to our GitHub app integration.
The process is extremely simple and shouldn’t require more than a few clicks, and you should not expect any downtime. By moving to our app, you will no longer need an admin or separate account to manage the relationship with GitHub as the team bot.
Let me know if you have any questions, or if I can help at all with this process.

Hey, @thomasrockhu Thanks for reporting this issue. I've just installed and configured Codecov from market place successfully for vidgear. Is there anything else I need to change? if yes, then please let me know.

Hi @abhiTronix , thanks for getting back to me so quickly. I'm actually not seeing it activated for vidgear.
You can do this by going here, clicking on the abhiTronix button, and selecting

either all repositories, or specifically this repository. Let me know if that doesn't makes sense.

@thomasrockhu, Done :+1:  Please check again.

Awesome, looks great! Thanks @abhiTronix


Backport to 21.05 option nix.package

Not sure if we do backports here, but it doesn't hurt.
Motivation

NixOS/nixpkgs/release-21.05 is the current stable branch.
The backport is backward-compatible. A similar option has been part of the NixOS configuration long before they are added here.
There's no workaround to specify the Nix package to use without adding this option. This patch greatly increase the user experience for flake-based configuration (nix.package = pkgs.nixUnstable;).

I've thought about that for a while, and I don't think backporting is a good time investment given that our master branch is always or almost always compatible with previous nixpkgs. Unless somebody steps up to test both backports and non-ff upgrades to new releases, I'd prefer not to do backports.

@t184256 I had thought that there would be some version checks the way the home-manager does.
Backporting would not be necessary if stable nixpkgs users can use the master nix-on-droid directly.


typo: Double wored "by"

Docs Build status updates of commit 077ec52:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/databricks-monitoring/dashboards.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Simplify disjunction for routers via a new type class (WIP)

This simplifies the :+: method on routers by adding the smash treatment for coproducts. This means that if we write the following:
val router = (int :+: string) :+: (string :+: long)

We get a Router[Int :+: String :+: String :+: Long :+: CNil], not a router of a nested coproduct. This means that router.toService works with the router above.
Before this change you'd have to write the following to accomplish the same thing:
val router =
  (int :+: string).map(_.extendRightBy[String :+: Long :+: CNil]) orElse
  (string :+: long).map(_.extendLeftBy[Int :+: String :+: CNil])

This PR still needs tests, etc.—I just wanted to put it up for discussion and to address @IgorWolkov's question on Gitter.
(Note that the change in #315 isn't relevant for coproducts, since we'll never have a Router[CNil].)

Current coverage is 93.64%

Merging #324 into master will change coverage by -0.90% by 728b01d

Powered by Codecov

This is very nice!
I was about to drop you a message with idea to use Smash-like approach here. But you were faster :)

BTW, @travisbrown do you think should we rename Smash to HListShash for consistency?

@travisbrown Looks great! Thanks!


Literals within the Block are Return

A Body is a list of Expressions. Within this body, if there is a literal expression, that becomes an implicit return.
Check within the type checker to enforce the final expression within the body be a literal/variable.

Implicit returns are setup with the pretty printer. Function applications are the exception since they're a bit nebulous to decide when they should return or not.

Closing since we moved to Rust


Difficulty Using Template and Running Migrations on Vercel Deploy

Hello,
I'm having trouble understanding how to use the provided template, especially when it comes to populating the database and running migrations.
Details:
I've successfully deployed my app on Vercel.
I'm unsure about how to execute new migrations during each build on Vercel.
Questions:
Can someone provide a step-by-step guide on how to use the template to populate the database?
How can I ensure that new migrations are executed during each build on Vercel?
Any help or guidance would be greatly appreciated. Thank you!

@Canopix For the database, the template uses Drizzle ORM. You can find all the information on how to populate and run the migration by looking in the official documentation: https://orm.drizzle.team/docs/quick-start
By default, a new migration is executed before building and deploying to Vercel: https://github.com/ixartz/Next-js-Boilerplate/blob/main/package.json#L6


Supporting Probe for sriov-network-device-plugin

What would you like to be added?
liveness probe support
What is the use case for this feature / enhancement?
Many applications running for long periods of time may eventually or eventually transition to broken states, and cannot recover except by being restarted. Kubernetes provides liveness probes to detect and remedy such situations.  This is required for cluster to operate in healthy state.

I had quick check on this , but unfortunately we did n't had any stuck situation in past.  This request is more from monitoring aspect and proactive detection of any such situation.

was implemented https://github.com/k8snetworkplumbingwg/network-resources-injector/pull/125
closing this issue


Updated Audio Sources and Typo in Stream Audio to Volumio

Added information to the NAS drive share section in docs/08_FAQs/03_Audio_Sources.md detailing connecting using a domain account
Updated Bluetooth section in docs/08_FAQs/03_Audio_Sources.md to reference Bluetooth input functionality in MyVolumio
Corrected typo in docs/00_User_Manual/05_Stream_audio_to_volumio.md.

Thanks!


Load/Update content dynamically on press of header component

I want to load/update content through API call based on click of header content.
https://stackoverflow.com/questions/45541989/load-update-content-dynamically-on-press-of-header-component

@preetampatil3d Link seems to be broken

Closing this as inactive as there's been no activity for over 30 days. If the problem re-occurs on the latest version of react-native-collapsible then ping me to reopen or create a new issue.

I think I have a similar issue.
I have a little font awesome icon (angle-right) on my header that I want to change to be (angle-bottom) when the header  expands.
To do this I would need to refresh header when it is pressed.
Accordion closed

Accordion expanded

Is it possible to do this?

@MarcoLLeite See the solution in https://github.com/oblador/react-native-collapsible/issues/145

That didn't really work for me, as the event doesn't get triggered.
Anyway, I managed to get it done on the _setSection(section)
Thanks anyway


How to get coco json format?

thanks, source code.
I ran the Anaconda env, pytorch = 1.0.1 on winodws 10
I run the line python eval.py --trained_model=weights/yolact_base_54_800000.pth --score_threshold=0.15 --top_k=15 --image=my_image.png and then see the result image.
Now, I hope to get the coco style's json from this result image.
so I typed  python eval.py --trained_model=weights/yolact_base_54_800000.pth --output_coco_json --score_threshold=0.15 --top_k=15 --image=my_image.png but no generated json file anywhere.
result
Config not specified. Parsed yolact_base_config from the file name.
Loading model... Done.
How to get coco json file from my image data using eval.py ?
I will transfer coco json file to label me json file, then modify the polygon or add new polygon.

Have you solved it? You may get some help from #625. Give "--dataset" parameter instead of "--image"

@PL-96 Thanks, you means that python eval.py --trained_model=weights/yolact_base_54_800000.pth --output_coco_json --score_threshold=0.15 --top_k=15 --dataset=my_image.png right?

@7eta that, but not just limited to 1 image, but even to the image folder. When running eval.py on an image folder, even with --output_coco_json I havent been able to get the json output. I've only been able to get it when validating the dataset.

@PL-96 Thanks, you means that python eval.py --trained_model=weights/yolact_base_54_800000.pth --output_coco_json --score_threshold=0.15 --top_k=15 --dataset=my_image.png right?

you may add custom_dataset definition in config.py like coco2017_testdev_dataset and set 'has_gt' to False. Then use "--dataset" parameter

@7eta
I also want to print out the result in the json file, but I can't find a way.
If the problem is solved, please share it with me.


Update dependencies

ansi-regex v5.0.0 => v5.0.1 (fixes CVE-2021-3807)
follow-redirects v1.14.3 => v.1.14.7 (fixes CVE-2022-0155)
node-fetch  v2.6.1 => v2.6.7 (fixes CVE-2022-0235)

How does using an older version of Connect JS SDK affect users and how do we communicate that they should upgrade (if they should)?

The described vulnerabilities should not actually affect this SDK. I'll prepare a patch release anyway to give the users of the SDK an option to update these dependencies.

The vulnerability alerts are about flaws in transient dependencies, all of which depend on specific circumstances we don't use these dependencies in. As a result, these advisories don't pose a risk to users of this SDK 🙂


MAINT: backports for SciPy 1.5.2

backport the already-large number of PRs suitable for the maintenance branch,
and I re-milestoned the associated PRs/issues to 1.5.2 (so that lists scripts can be used
to auto-generate author/PR lists)
update the release notes for SciPy 1.5.2 to reflect the backports
known issues include at least 1 new author without a properly-mailmapped name,
some PRs were captured twice because both the main and backport PR were milestoned,
and we have previously observed consistent ARM64 CI fails in backport PRs for
test_lgmres.py:109: in test_arnoldi (we'll see if that continues here, but I've been ignoring
it)

Overall looks good. I would have left out the one ENH commit I think, that doesn't quite belong in a bugfix release.

The cKDTree gurus told me it was intrinsically linked to the bugfix

Oh okay, never mind then:)

All green, in it goes!


fix(controller): "Current task state not recognized"

Prerequisite: merge https://github.com/OpenDevin/OpenDevin/pull/1516
Fix https://github.com/OpenDevin/OpenDevin/issues/1492#issuecomment-2090316167

@amanape I tried to fix the reset issue; based on my testing, you should be able to reset tasks easily.
However, I'm debating regarding whether the PAUSE button should have any effect when the agent is awaiting user input. Awaiting user input is technically a type of "pause" itself? WDYT?

@xingyaoww You're right, disabling the pause button while the agent is waiting makes more sense. Another alternative would be your suggestions in #1508
Personally, I think

directly change the send button into "[continue]"

is a good one.

I tried to fix the reset issue; based on my testing, you should be able to reset tasks easily.

@xingyaoww @amanape i slightly adjust the reset behavior here. #1519


Greater London Authority added

Greater London Authority added to organisations.csv and organisations.json. This relates to https://github.com/GSS-Cogs/ds-squad/issues/1.

Where did the freetext com from for the GLA definition?

It was taken from wikipedia.


Dev Home itself should not shown in the extension list

Dev Home version
No response
Windows build number
No response
Other software
No response
Steps to reproduce the bug
Go to extension page.

Expected result
It should only show extensions
Actual result
It shows not only extensions but also Dev Home App itself.
Included System Information
No response
Included Extensions Information
No response

Hi @jiayac -- this is actually the expected behavior. It might not be super clear at first, but the list in your screenshot is actually the list of extension providers. If you expand the item, you can see all the extensions that provider contains. You'll see that for Dev Home, you can actually choose to disable the "Hyper-V Extension" underneath it. That's why "Dev Home" is in the list.


Make clients.acme.factory optional and use discovery instead

Q
A

Bug?
no

New Feature? yes

Version
N/A

I propose to make the factory key of the client configuration optional (clients.acme.factory).
In such case, we will use the discovery to find an available implementation. Of course, the config node would be disabled when no factory is set.

I like this one. Do you want to send a PR?

Yes!


Let's create the dialog box that pops up if the claim has ancestors.

I'm getting the following error:
11.49 7:31  Error: React Hook "useState" is called in function "deleteDialog" that is neither a React function component nor a custom React Hook function. React component names must start with an uppercase letter. React Hook names must start with the word "use".  react-hooks/rules-of-hooks

Oops, I guess I forgot my capitalization system. Now it compiles.

It works! Although it has no styling at the moment.

TODO:

Add "Cancel" and "Delete" buttons.
Stop dragging from working on the claim that is slated for deletion.

TODO:

Make the "Cancel" and "Delete" buttons successfully change color on mouse over.
Made the "Cancel" button deactivate the dialog.
Stop dragging from working on the claim that is slated for deletion.

Optional TODO:

Make rounded-md consistent across the app (in particular in the navigation bar).

TODO:

Stop dragging from working on the claim that is slated for deletion.

Optional TODO:

Make rounded-md consistent across the app (in particular in the navigation bar).

Everything is done, let's merge!


Tabs component's tablist does not need to be in a nav

Please see https://github.com/IBM/carbon-components-react/issues/2171

not stale

@joshblack Is this really fixed? I didn't see a commit go by that fixed it. The above commit just changes a comment somewhere - it may be referencing the wrong issue number?
The Vanilla Tabs and React Tabs example pages still have a nav as a parent for the tab list, so I think (?) that this issue was closed accidentally? Unless those example pages still need to be updated?


ci: update ci job run conditions

Hi there,
after merging #652, you immediately received a couple or PRs by dependabot, which is great.
Dependabot creates an individual branch per updated dependency it found. With the current CI configuration each PR runs 12 CI jobs, 6 on the branch and 6 on the PR. A bit too much.
Running CI jobs only on master and PRs is also part of #586. But as that PR is still WIP, I wanted to suggest to merge this smaller change as soon as possible, to reduce the number of CI job runs.
What do you think?

coverage: 91.339%. remained the same when pulling 4566e24ab311826d469d7a83b16752fc833bc30b on afuetterer:github-actions into ee4d7ffa0a6e9e0bdbfb4a366dcbff015eb9e6ff on rdmorganiser:master.

thanks @afuetterer , I agree to make this into a PR and have just one question.
In #586, I wrote for the on: push: condition to include tags and release/**.  However, at the moment we don't have any special pipeline for tags or release so this is actually not be needed right?
on:
  push:
    branches:
      - master
      - 'releases/**'
    tags:
      - '*.*.*'
  pull_request:


Update file-input.html

Set the cursor as pointer when the input is hovered
Cf. http://stackoverflow.com/questions/1537223/change-cursor-type-on-input-type-file/24488438#24488438

Changes Unknown when pulling 09eeea169cc3332bb2e199ae270be47257556b0b on fredericlefeurmou:patch-1 into ** on rnicholus:master**.

Thanks for the pull request! Which browsers were you able to test out to be sure there were no obvious UI regressions?

I would like this to get merged. I can't style the cursor myself because there's no CSS mixin to use.

Not sure what you mean by "CSS mixing". Why can't you just target the element or any of its children in your stylesheet?

CSS mixins: https://www.polymer-project.org/1.0/docs/devguide/styling#custom-css-mixins
I can't style the children DOM element because it's in the shadow DOM.

Shadow DOM isn't used by this component.


Release @google-cloud/text-to-speech v0.5.1

This pull request was generated using releasetool.

Release is at https://github.com/googleapis/nodejs-text-to-speech/releases/tag/v0.5.1

The release build has started, the log can be viewed here. :sunflower:

:egg: You hatched a release! The release build finished successfully! :purple_heart:


Danger syntax fixes

Interesting that the last one didn't fail, the syntax changed.

I must have waited too long to submit the PR, the CI build ran entirely before the PR was made

:+1:


Support using @ex.capture on methods.

When constructing arguments for a bound method invocation, the first
argument of the signature ('self') should be ignored, as it is passed
automatically.

Nice work, thank you very much!


make gui_target is not able to find .odb file

Describe the bug
[INFO][FLOW] Using platform directory ./platforms/nangate45
make: *** No rule to make target 'gui_6_final.odb', needed by 'gui_final'.  Stop.
How can i update OpenRoad ?
Expected Behavior
it should open gui
Environment
[WARNING] Your current OpenROAD version is outdated.
It is recommened to pull the latest changes.
If problem persists, file a github issue with the re-producible test case.
kernel: Linux 5.19.0-38-generic
os: Ubuntu 22.04.2 LTS (Jammy Jellyfish)
cmake version 3.24.2
CMake Error: The source directory "/home/embedded/Documents/OpenROAD-flow-scripts" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.

To Reproduce
make DESIGN_CONFIG=./designs/sky130hd/ibex/config.mk
Relevant log output
No response
Screenshots
No response
Additional Context
No response

Does results/sky130hd/ibex/6_final.odb exist?  The gui target only loads an existing file.

I found the issue i was using "make gui_final" but to open the design I need to do make gui_final DESIGN_CONFIG=./designs/sky130hd/ibex/config.m


Wrong Chain p2p error despite correct genesis.json

Brief:
I'm getting a go away wrong chain message from my peers, not sure how though.  My intention is to run on the EOS mainnet.
["p2p.eosio.cr:9876" <IP_ADDRESS>:9876]received go_away_message, reason = wrong chain (log_plugin/to_console_log_plugin.go:63)

My genesis.json that I changed in both mindreader/producer from here.
{
  "initial_timestamp": "2018-06-08T08:08:08.888",
  "initial_key": "EOS7EarnUhcyYqmdnPon8rm7mBCTnBoot6o7fE2WzjvEX2TdggbL3",
  "initial_configuration": {
    "max_block_net_usage": 1048576,
    "target_block_net_usage_pct": 1000,
    "max_transaction_net_usage": 524288,
    "base_per_transaction_net_usage": 12,
    "net_usage_leeway": 500,
    "context_free_discount_net_usage_num": 20,
    "context_free_discount_net_usage_den": 100,
    "max_block_cpu_usage": 200000,
    "target_block_cpu_usage_pct": 1000,
    "max_transaction_cpu_usage": 150000,
    "min_transaction_cpu_usage": 100,
    "max_transaction_lifetime": 3600,
    "deferred_trx_expiration_window": 600,
    "max_transaction_delay": 3888000,
    "max_inline_action_size": 4096,
    "max_inline_action_depth": 4,
    "max_authority_depth": 6
  }
}

And my config.ini peers:
p2p-peer-address = peer.main.alohaeos.com:9876
p2p-peer-address = eosbp-0.atticlab.net:9876
p2p-peer-address = p2p.eosio.cr:9876
p2p-peer-address = p2p.eos.cryptolions.io:9876
p2p-peer-address = eos.csx.io:9876
p2p-peer-address = mainnet.eosamsterdam.net:9876
p2p-peer-address = mainnet.eosarabia.net:3571
p2p-peer-address = peer.eosn.io:9876
p2p-peer-address = p2p.eosflare.io:9876
p2p-peer-address = peer1.eosphere.io:9876
p2p-peer-address = api.eosvenezuela.io:9876
p2p-peer-address = node1.zbeos.com:9876

Docker command used
docker run -d -v "/root/work/dfuseeos/dfuse-data:/dfuse-data" -v "/root/work/yamls/pre_dappservices:/etc/dfuseeos-configs" -v "/root/work/dfuseeos/producer:/producer" -v "/root/work/dfuseeos/mindreader:/mindreader" --name mindreader docker.io/dfuse/dfuse-eosio:latest /app/dfuseeos -c /etc/dfuseeos-configs/mindreader.yaml start -vvvv

Version:
/app/dfuseeos --version
dfuseeos version dev-

https://github.com/dfuse-io/dfuse-eosio/blob/671e39b821778c7256fb9994151f1c5dc8318b5f/node-manager/superviser/superviser.go#L164
There were existing blocks in the mindreader blocks directory.  This was preventing the genesis.json from being ready.
User error.


[rcore] Add ToggleFullscreen() implementation for PLATFORM_WEB

a. Preface

@raysan5 I'm sorry for the very long PR. I know this is going to be a real pain to review. Tried to simplify things as much as possible, but it's a complicated problem with a lot of background information. Please, take your time.

b. Context

Unfortunately "fullscreen" is very challenging to handle completely and reliably on web. So far I've identified 5 "types" of "fullscreen" that affects raylib with emscripten:

I. F11 fullscreen

Invoked by the user pressing the F11 key.
Will bring the entire page to fullscreen.
There's not much we do about this. The user will always be able to press F11, bringing the whole page to fullscreen.
Luckly, the F11 fullscreen won't break the other "types" of "fullscreen". So the user can invoke the F11 fullscreen and then, after, any other "type" of "fullscreen" and that other "type" will work without a problem, albeit inside the F11 fullscreen "context"/"space".

II. HTML5 fullscreen

Invoked by some variation of document.someElement.requestFullscreen().
Will create its own way of fullscreen.
Has very few options (doc), and none of which are particularly useful for us.
Appears to use the same inner "process" of creating a "fullscreen" like Emscripten fullscreen, although through different methods.

III. Emscripten fullscreen

Invoked by emscripten_request_fullscreen() or emscripten_request_fullscreen_strategy().
Will create its own way of fullscreen.
Has more options (doc) which are useful for us, but doesn't have some options we need (e.g.: "borderless windowed", aka "fullscreen desktop").
Appears to use the same inner "process" of creating a "fullscreen" like HTML5 fullscreen, although through different methods.

IV. Emscripten soft fullscreen

Invoked by emscripten_enter_soft_fullscreen().
Will create a "simulated"/"fake" fullscreen.
Won't cover web browser GUI, etc. And, since it's not a "fullscreen", won't trigger the default "Esc to leave fullscreen" browser message/dialog.
Requires a special emscripten_exit_soft_fullscreen() to leave and will expressly conflict with other "types" of "fullscreen" (specially Emscripten fullscreen).

V. Emscripten Module fullscreen

Invoked by Module.requestFullscreen().
Will create its own way of fullscreen.
Was the only method that provided the minimal options for the 2 "types" of "fullscreen" we need ("real fullscreen" and "borderless windowed").
However, conflicts with HTML5 fullscreen and Emscripten fullscreen, due to the inner "process" through which the "fullscreen" is created.

c. Conclusion

F11 fullscreen is no problem and can co-exist without issues. We can just forget it's there.
HTML5 fullscreen is insufficient. It's missing any sort of scale option (doc).
Emscripten fullscreen is, at this moment, insufficient. It's missing an option to not scale the content but scale the canvas. I've tried all combinations (test_html5_fullscreen.c L154-L161) but none provided that.
Emscripten soft fullscreen is not really an option for what we need.
Emscripten Module fullscreen is not perfect (doesn't have the fine-grained scale options from Emscripten fullscreen), but provides the minimal options we need.

d. Changes

Since HTML5 fullscreen and Emscripten fullscreen don't have the options we need right now, had to go with the Emscripten Module fullscreen route.

It's important to understand that there are 2 contexts for "fullscreen" for us:

One where we call it from inside raylib.
This we can track and control through CORE.Window.flags, ToggleFullscreen(), ToggleBorderlessWindowed(), SetWindowState() and ClearWindowState().

And one where the user call it from outside raylib.
This we have no control of and we have limited capacity to track.
This happen, for example, when the user clicks the Fullscreen button from the shell.html file (L181).

The problem of these 2 contexts is exactly not being able to track the one called from outside raylib. Which causes the Toggle*() and *WindowStates() to malfuction (e.g.: do nothing since it won't have the flags set or work inverted).

To address that a new platform.ourFullscreen bool variable was added (R76). When it's true it means that "fullscreen" process is being operated by raylib calls. When it's false it means it wasn't us. We'll get in more detail later.

To actually handle the "fullscreen" when ToggleFullscreen() or *WindowStates() are called, we:

First check if the document is already on "fullscreen" (R147-R148).
Note 1: EM_ASM_INT was used because we need to set flags inside raylib and outside JS (R155-R157).
Note 2: document.fullscreenElement was used because, under my testing, it appeared to be the most reliable way to check if we were on some "type" of "fullscreen".

If it is, we leave whatever "type" of "fullscreen" we were in (R150).
Note: EM_ASM and document.exitFullscreen() were used because, under my testing, it appeared to be the most reliable way to leave whatever "type" of "fullscreen" was active.

Since we left the whatever "type" of "fullscreen" we were in, we also reset the raylib flags (R155-R157).

But, before that (otherwise the flag would have been reseted), we check if we where on a (our) FLAG_FULLSCREEN_MODE "fullscreen" (R152).

If we were, it means this Toggle means leave fullscreen, so we stop there.

If we weren't, it means this Toggle is coming after some other "type" of "fullscreen" other than FLAG_FULLSCREEN_MODE, so we will continue (R153) and proceed to enter a (our) FLAG_FULLSCREEN_MODE "fullscreen" (R161-R172).

If we were not in any "type" of "fullscreen" to begin with, we continue to enter a (our) FLAG_FULLSCREEN_MODE "fullscreen" (R159-R161).

To enter (our) FLAG_FULLSCREEN_MODE "fullscreen" we call Module.requestFullscreen(false, false); inside a short setTimeout (R164-R169) and them set the necessary flags (R170-R171).
Note 1: the Module.requestFullscreen(); parameters are lockPointer that we keep as false and resizeCanvas that we keep as false to achieve the same type of fullscreen from the other platforms.
Note 2: the setTimeout was necessary to handle the browser mode change delay.

Side-note: the old notes were kept as a reference in case it's needed in the future (R174-R238).

After this "fullscreen" call is done, it should trigger a "fullscreen change" event and the EmscriptenFullscreenChangeCallback() (R1440).

But, to allow that, the emscripten_set_fullscreenchange_callback had to be changed to EMSCRIPTEN_EVENT_TARGET_WINDOW instead of #canvas (L1139-R1178), because #canvas won't be reliably tracked.

Here is when platform.ourFullscreen (that is set to true right from the start of ToggleFullscreen R144) becomes important:

If platform.ourFullscreen is true, we already cleaned and set the flags ourselves inside ToggleFullscreen() (R155-R157, R170-R171), as needed. So all we need to do is reset the platform.ourFullscreen to false (R1444).

However, if platform.ourFullscreen is false, then this "fullscreen change" event if coming from outside raylib.

If it's coming from outside raylib and is not on "fullscreen" (R1447-R1448), it means the user just left some "type" of "fullscreen" (e.g.: pressed the Esc key). So the assume we're no longer in some "type" of "fullscreen" and reset our raylib flags to match that non-fullscreen state (R1450-R1452).
Note: this will handle the item 4 issue.

Basically the same process happen for ToggleBorderlessWindowed(). The only difference being the variable names, the respective flags and entering the "borderless windowed" "fullscreen" (R242):

For that, we use Module.requestFullscreen(false, true); instead, where true means resizeCanvas, achieving the FLAG_BORDERLESS_WINDOWED_MODE "fullscreen" (R268).

We also need to use canvas.style.width="unset"; to  handle the possibility of a width="value%" like on the default shell.html file (R271).

There the setTimeouts are also used to handle the browser mode change delay (R266-R269).

e. Known issues

With all this handling ToggleFullscreen() and ToggleBorderlessWindowed() and the *WindowState() become "hot swappable", meaning that the user can jump from FLAG_FULLSCREEN_MODE "fullscreen"  to FLAG_BORDERLESS_WINDOWED_MODE "fullscreen" with just a single ToggleBorderlessWindowed() or SetWindowState(FLAG_BORDERLESS_WINDOWED_MODE); call. The same being true for the opposite (from FLAG_BORDERLESS_WINDOWED_MODE to FLAG_FULLSCREEN_MODE).

There's one limitation tho: at the moment, I wasn't able to find a way to parse the Module.requestFullscreen() resizeCanvas parameter issued outside raylib. Getting that information would allow to find which "type" of "fullscreen" was issued from outside. And that would allow to better toggle it out.

E.g.: if the user press the fullscreen button on the shell.html file, the canvas will go fullscreen as expected (that's outside raylib). Then if the user uses ToggleFullscreen() it will leave the fullscreen and then reenters the "fullscreen" (that's inside raylib). From there, everything works as expected. But, if we had that information, we could instead just leave the fullscreen shortcutting it.

~It's a minor issue, but if we ever figure out how to get that info, we can handle that exactly at R1453.~
Note: found a way to handle it using the following code inside ToggleFullscreen():
const int cw = EM_ASM_INT( { return document.canvas.width; }, 0);
const int csw = EM_ASM_INT( { return parseInt(document.canvas.style.width); }, 0);
if (cw < csw) enterFullscreen = false;
However, it causes SetWindowState() to break on that case. IMHO, this is such a minor issue that doesn't justify the overengineering, so better just leave it as is.

IMPORTANT NOTE: @raysan5 I just realized that the other platforms don't have these toggles operating in "hot swap". Please let me know if I should revert this here so it matches the other platforms behavior for parity and consistency.

As mentioned previously, Emscripten Module fullscreen conflicts with HTML5 fullscreen and Emscripten fullscreen:

If the user enters "fullscreen" with ToggleFullscreen() or SetWindowState(), then leaves, then enters "fullscreen" with HTML5 fullscreen (e.g.: calling document.getElementById("canvas").requestFullscreen()) this will "break" the page content (but not the canvas, which will continue to work). By "break" I mean, for some reason, that document.getElementById("canvas").requestFullscreen() call will, at that moment, cause the <canvas> to replace <body>.

The same will happen if the user enters "fullscreen" with HTML5 fullscreen (e.g.: document.getElementById("canvas").requestFullscreen()), then press Esc to leave, then enter "fullscreen" with ToggleFullscreen(), then leaves, then enter "fullscreen" again with HTML5 fullscreen (e.g.: document.getElementById("canvas").requestFullscreen()).

Unfortunately I have no solution for this yet. But as long both methods are not mixed, everything should work fine.

f. Outro

Nevertheless, I think this implementation covers most use cases and works for both a minshell.html-style or a shell.html-style shell files.

Also, hopefully this PR documents enough detail to help for context or future updates of "fullscreen" for PLATFORM_WEB.

g. Notes

If Emscripten fullscreen eventually gets updated to provide an option to not scale the content but scale the canvas, we likely could replace the Module EM_ASM calls with something like:

// To enter emscripten fullscreen:
EmscriptenFullscreenStrategy strat = {
    .scaleMode = EMSCRIPTEN_FULLSCREEN_SCALE_SOMETHING,
    .canvasResolutionScaleMode = EMSCRIPTEN_FULLSCREEN_CANVAS_SCALE_SOMETHING,
    .filteringMode = EMSCRIPTEN_FULLSCREEN_FILTERING_DEFAULT,
    .canvasResizedCallback = NULL
};
emscripten_request_fullscreen_strategy("#canvas", 1, &strat);

// To leave emscripten fullscreen:
emscripten_exit_fullscreen();

h. Code example

This change can be tested for PLATFORM_WEB (requires ASYNCIFY) with:

#include "raylib.h"

int main(void) {
    InitWindow(800, 450, "test");
    SetTargetFPS(60);
    while (!WindowShouldClose()) {

        if (IsKeyPressed(KEY_F)) ToggleFullscreen();
        if (IsKeyPressed(KEY_G)) SetWindowState(FLAG_FULLSCREEN_MODE);
        if (IsKeyPressed(KEY_H)) ClearWindowState(FLAG_FULLSCREEN_MODE);

        if (IsKeyPressed(KEY_B)) ToggleBorderlessWindowed();
        if (IsKeyPressed(KEY_N)) SetWindowState(FLAG_BORDERLESS_WINDOWED_MODE);
        if (IsKeyPressed(KEY_M)) ClearWindowState(FLAG_BORDERLESS_WINDOWED_MODE);

        BeginDrawing();
        ClearBackground(RAYWHITE);

        DrawText("[F] ToggleFullscreen()", 20, 20, 20, BLACK);
        DrawText("[G] SetWindowState(FLAG_FULLSCREEN_MODE)", 20, 40, 20, BLACK);
        DrawText("[H] ClearWindowState(FLAG_FULLSCREEN_MODE)", 20, 60, 20, BLACK);

        DrawText("[B] ToggleBorderlessWindowed()", 20, 100, 20, BLACK);
        DrawText("[N] SetWindowState(FLAG_BORDERLESS_WINDOWED_MODE)", 20, 120, 20, BLACK);
        DrawText("[M] ClearWindowState(FLAG_BORDERLESS_WINDOWED_MODE)", 20, 140, 20, BLACK);

        EndDrawing();
    }
    CloseWindow();
    return 0;
}

i. Environment

Compiled on Linux (Ubuntu 22.04 64-bit) and tested on Firefox (115.3.1esr 64-bit) and Chromium (117.0.5938.149 64-bit) for both minshell.html and shell.html files.

j. Edits

1: editing.
2: typos, editing and formatting.
3: editing, formatting.
4: typos, correction.
5: updated status on known issue 1.
6: added item iv important note to known issues 1.

@ubkp Thank you very much for the super-detailed review and documentation of this issue! Just let me some days to review it carefully.

@ubkp Ok, just reviewed it. Again, thanks for the super-detailed review of all fullscreen modes available on Web, I worked on that long time ago but I couldn't come up with a proper solution, actually my focus was mostly on emscripten_request_fullscreen_strategy() but most of my tests did not work as expected.
The proposed processes and assumptions look ok to me. About the known issues:

There's one limitation tho: at the moment, I wasn't able to find a way to parse the Module.requestFullscreen() resizeCanvas parameter issued outside raylib. Getting that information would allow to find which "type" of "fullscreen" was issued from outside. And that would allow to better toggle it out.

Isn't it possible to compare the CORE.Window.screen/CORE.Window.previousScreen with the new canvas size (queried using EM_ASM_INT()) to get that parameter?

IMPORTANT NOTE: @raysan5 I just realized that the other platforms don't have these toggles operating in "hot swap". Please let me know if I should revert this here so it matches the other platforms behavior for parity and consistency.

I think this is a minor detail, it's also highly dependant on users and I doubt many of them mix the toggle modes on their codebases.
In that regards, I see many of the potential conflicts/issues depend on users mixing modes so I think it's ok to leave that good-practices work to them. If many users hit those constrains and complain, we can review it in the future.
Thanks again for all the work put into this improvement.

An additional note: All my review was based on provided code and example but not on actual "production code". I got several tools relying on it, if I see some unexpected issue with this update I will just report it.


[RFR] Controls tests modified

Signed-off-by: Karishma Punwatkar<EMAIL_ADDRESS>modified:   mta/fixtures/apis.py
modified:   mta/fixtures/business_service.py
modified:   mta/fixtures/job_function.py
modified:   mta/fixtures/stakeholder.py
modified:   mta/fixtures/stakeholder_group.py
modified:   mta/fixtures/tags.py
modified:   mta/tests/migration/controls/test_business_services.py
modified:   mta/tests/migration/controls/test_stakeholder.py
modified:   mta/tests/migration/controls/test_tags.py

@kpunwatk please ryn pre-commit checks


Default export error: The expression of an export assignment must be an identifier or qualified name in an ambient context.

Something's wrong with the default export.
The error occurs only with just importing / calling the module.

Sorry, since I tried to solve the problem as fast as I could, I haven't tested my module in javascript.
I found a solution for that, so a new release of the package with a new feature will solve this problem.
Please wait for then.

Sorry, since I tried to solve the problem as fast as I could, I haven't tested my module in javascript.
I found a solution for that, so a new release of the package with a new feature will solve this problem.

it's okay. do your best


Moderation: empty edits allowed or buggy diff?

See https://godotengine.org/asset-library/asset/edit/77
There is no diff to review for this edit, so either empty edits are not discarded, or there were actual changes but the diff does not show them properly.

@akien-mga yep, empty edits are allowed, and do completely nothing.
That being said, checking for them through code is not that easy, as it has to consider the previews as well.

so.... I put the address of youtube video and thumbnail. Just changing the dropdown to select Video instead Image. And saved.

@akien-mga Ah, just saw a use for them -- if we allow putting things like master for the version commit to be downloaded, making an empty edit is the only way to have the hash updated...

Yeah, but as per #63, we don't want to allow that anymore, used should provided a commit hash or tag so that we know it won't change (tags may change, but then the asset devs are on their own, since the sha256sum will be broken).
@marcosbitetti's comment hints that there might be an issue with videos submission though (may be related to #56).


Uncaught DOMException: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.

Hi @extremeheat ,
I faced an error while running the code as shown below:
###########
const { py, python } = require("pythonia");
const np = await python("numpy");
const plot = await python("matplotlib.pyplot");
// Fixing random state for reproducibility
await np.random.seed(19680801);
const [mu, sigma] = [100, 15];
const x = await py${mu} + ${sigma} * ${np.random.randn(10000)};
// the histogram of the data
const [n, bins, patches] = await plot.hist$(x, 50, {
density: true,
facecolor: "g",
alpha: 0.75,
});
await plot.xlabel("Smarts");
await plot.ylabel("Probability");
await plot.title("Histogram of IQ");
await plot.text(60, 0.025, "$\mu=100, \sigma=15$");
await plot.xlim(40, 160);
await plot.ylim(0, 0.03);
await plot.grid(true);
await plot.show();
python.exit();
#############
The error shown on console window is as shown below:
Uncaught DOMException: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
at StdioCom.writeRaw (C:\directory\node_modules\pythonia\WebsocketCom.js:75:20)
at C:\directory\node_modules\pythonia\Bridge.js:233:52
at C:\directory\node_modules\pythonia\Bridge.js:119:28
at new Promise ()
at waitFor (C:\directory\node_modules\pythonia\Bridge.js:119:5)
at Bridge.call (C:\directory\node_modules\pythonia\Bridge.js:233:24)
at Object.apply (C:\directory\node_modules\pythonia\Bridge.js:411:26)
at python (C:\directory\node_modules\pythonia\index.js:85:17)
May I know the cause of this error? is the socket ws://<IP_ADDRESS>:8768/ not working in my computer?
or did I forget to do something at the background?
the error occurred when executing the first line of the code.

This is strange since websocket comm should only loaded in a browser environment. What environment are you running your code in? A standard node runtime should not trigger this issue.

This is strange since websocket comm should only loaded in a browser environment. What environment are you running your code in? A standard node runtime should not trigger this issue.

Thanks a lot for your fast response.
below is the content of our package.json file:
{
"name": "directory",
"version": "1.0.0",
"devDependencies": {
"nw": "^0.54.0",
"nw-builder": "^3.5.7"
},
"scripts": {
"dev": "nw src/",
"prod": "nwbuild --mode build --platforms win64 --buildDir dist/ src/"
},
"dependencies": {
"fs-extra": "^11.1.1",
"graceful-fs": "^4.2.11",
"jsonfile": "^6.1.0",
"mathjax": "^2.7.4",
"plotly.js-dist-min": "^2.20.0",
"polyfill-library-node": "^1.1.0",
"pythonia": "^1.0.1",
"universalify": "^2.0.0"
}
}
I run command
npm run dev
and get the error.

Please update your dependencies and see if the problem is resolved. This should be fixed with v1.0.2

Please update your dependencies and see if the problem is resolved. This should be fixed with v1.0.2

It works!
Thanks a lot for your helps. ^_^


add documentation: Ubuntu installation

I was following this page: https://docs.docker.com/installation/ubuntulinux/
After I installed docker but and ran the command: $ sudo docker run hello-world
It returned:
FATA[0000] Get http:///var/run/docker.sock/v1.17/version: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?
can you please add a step in the instructions to run: service docker restart
This fixed the issue for me.

Which ubuntu version are you using?
After I ran the instructions on ubuntu-14.04, docker daemon was automatically started after Step 3 : $ wget -qO- https://get.docker.com/ | sh and sudo docker run hello-world ran normally for me.

I am also having the same issues with vivid (ubuntu-15.04). docker service/daemon doesn't start automatically. You have to start it manually to get it working.

I installed docker on a clean version ubuntu 15.04 using wget -qO- https://get.docker.com/ | sh  and the docker daemon started automatically after the install. @Pensu  : Can you reliably reproduce this issue?

Same here for me. Docker service/daemon doesn't start automatically. I have to start it manually to get it working. I'm also on a clean Ubuntu 15.04
' docker --versiondisplays onlyDocker version 1.6.0, build 4749651`

docker --version displays only Docker version 1.6.0, build 4749651. On Ubuntu 14.04.2 LTS there were a lot more information. :)

Probably need to try docker version (not --version), which gives more output

Oh gosh my fault! you're right @thaJeztah :)

You're welcome! It is confusing, so nothing to be ashamed about :)

I seem to have the same problem with Ubuntu 15.04 (fresh installation). Probably it has something to do with the change from upstart to systemd as init system. I assume some startup scripts have to get adjusted to fix it.
Some info about my system:
asmaps@asmaps-x240 ~ % cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.04
DISTRIB_CODENAME=vivid
DISTRIB_DESCRIPTION="Ubuntu 15.04"

asmaps@asmaps-x240 ~ % docker ps
FATA[0000] Get http:///var/run/docker.sock/v1.18/containers/json: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?

asmaps@asmaps-x240 ~ % sudo service docker status
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: http://docs.docker.com

After sudo service docker start:
% sudo service docker start
asmaps@asmaps-x240 ~ % sudo service docker status
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
   Active: active (running) since Mo 2015-04-27 17:25:44 CEST; 2s ago
     Docs: http://docs.docker.com
 Main PID: 7788 (docker)
   Memory: 324.0K
   CGroup: /system.slice/docker.service
           ├─7788 /usr/bin/docker -d -H fd://
           └─7867 docker-proxy -proto tcp -host-ip <IP_ADDRESS> -host-port 3141 -container-ip <IP_ADDRESS> -container-port 3141

Apr 27 17:25:45 asmaps-x240 docker[7788]: time="2015-04-27T17:25:45+02:00" level=info msg="-job allocate_interface(dbc101d4ec384ff26cd597ba34350adad8e842ae3697a3fbccd6c9bfb394947a) = OK (0)"
Apr 27 17:25:45 asmaps-x240 docker[7788]: time="2015-04-27T17:25:45+02:00" level=info msg="+job allocate_port(dbc101d4ec384ff26cd597ba34350adad8e842ae3697a3fbccd6c9bfb394947a)"
Apr 27 17:25:45 asmaps-x240 docker[7788]: time="2015-04-27T17:25:45+02:00" level=info msg="-job allocate_port(dbc101d4ec384ff26cd597ba34350adad8e842ae3697a3fbccd6c9bfb394947a) = OK (0)"
Apr 27 17:25:45 asmaps-x240 docker[7788]: time="2015-04-27T17:25:45+02:00" level=info msg="+job log(start, dbc101d4ec384ff26cd597ba34350adad8e842ae3697a3fbccd6c9bfb394947a, scrapinghub/devpi:latest)"
Apr 27 17:25:45 asmaps-x240 docker[7788]: time="2015-04-27T17:25:45+02:00" level=info msg="-job log(start, dbc101d4ec384ff26cd597ba34350adad8e842ae3697a3fbccd6c9bfb394947a, scrapinghub/devpi:latest) = OK (0)"
Apr 27 17:25:45 asmaps-x240 docker[7788]: time="2015-04-27T17:25:45+02:00" level=info msg="Loading containers: done."
Apr 27 17:25:45 asmaps-x240 docker[7788]: time="2015-04-27T17:25:45+02:00" level=info msg="docker daemon: 1.6.0 4749651; execdriver: native-0.2; graphdriver: aufs"
Apr 27 17:25:45 asmaps-x240 docker[7788]: time="2015-04-27T17:25:45+02:00" level=info msg="+job acceptconnections()"
Apr 27 17:25:45 asmaps-x240 docker[7788]: time="2015-04-27T17:25:45+02:00" level=info msg="-job acceptconnections() = OK (0)"
Apr 27 17:25:45 asmaps-x240 docker[7788]: time="2015-04-27T17:25:45+02:00" level=info msg="Daemon has completed initialization"

asmaps@asmaps-x240 ~ % docker version
Client version: 1.6.0
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 4749651
OS/Arch (client): linux/amd64
Server version: 1.6.0
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 4749651
OS/Arch (server): linux/amd64

asmaps@asmaps-x240 ~ % docker ps
CONTAINER ID        IMAGE                      COMMAND             CREATED             STATUS              PORTS                    NAMES
dbc101d4ec38        scrapinghub/devpi:latest   "/run.sh"           55 minutes ago      Up About a minute   <IP_ADDRESS>:3141->3141/tcp   devpi

:+1: I'm seeing the same results as @asmaps on my fresh 15.04 install (also installed docker with the script)

+1. I need to sudo service docker restart after every reboot

I'm having the same issue on Ubuntu 15.04. After "sudo service docker restart" it starts working.

Docker service won't start automatically for me either:
> cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"

> docker version
Client version: 1.6.0
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 4749651
OS/Arch (client): linux/amd64
FATA[0000] Get http:///var/run/docker.sock/v1.18/version: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?

@tianon @jfrazelle are there still known issues with the install script? Given it's a mish-mash of versions reported above, I'm not sure all reporters are having the same issue. Anything you think could be worthy to check in order to debug?

@tianon @jfrazelle are there still known issues with the install script? Given it's a mish-mash of versions reported above, I'm not sure all reporters are having the same issue. Anything you think could be worthy to check in order to debug?

Seems to me it is the same problem. People need to run systemctl enable
docker for it to restart on 15.04 because it is systemd
This will be fixed in our new install script which uses the new rpms and
debs we have been working on.
On Saturday, May 9, 2015, Sebastiaan van Stijn<EMAIL_ADDRESS>wrote:

@tianon https://github.com/tianon @jfrazelle
https://github.com/jfrazelle are there still known issues with the
install script? Given it's a mish-mash of versions reported above, I'm not
sure all reporters are having the same issue. Anything you think could be
worthy to check in order to debug?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/12002#issuecomment-100573745.

for me looking into /var/log/upstart/docker.io.log hint me in the direction apparmor was missing
so i did apt-get install apparmor followed by
sudo service docker restart
and it worked

@innovia the issue with Ubuntu 15.04 is another one. Apparmor is installed. Systemd is used instead of Upstart.

I am not familiar with the docker internals but it is clear to me that either docker itself sort one of its dependencies has a dependency on apparmor itself. Now, obviously having to manually install a package is non-ideal. If I could, I'd open a pull request and patch the debian/ubuntu package dependencies but I'm afraid I am not so great (at least not yet).
What I'm trying to say is, maybe instead of updating the documentation, the dependency tree should be fixed somehow.

Talking only about 15.04 (The Ubuntu install instructions do not describe how to install on 15.04, and just doing wget -qO- https://get.docker.com/ | sh will work only untill you reboot. So here is the solution for 15.04:

Ubuntu 15.04 uses systemd, and the get.docker.com install script does not support this yet.
After running wget -qO- https://get.docker.com/ | sh, run docker version to check that it's running. This should be the case.
Now check if it is configured to run at startup, with systemctl is-enabled docker. If this shows 'disabled', then you need to run systemctl enable docker
Reboot the server and run docker version again, to check that your systemctl enable docker fixed the problem.

There is a fix for this problem for Ubuntu 15.04:
sudo systemctl enable docker
(source)

Wow, glad to found this issue, but sudo systemctl enable docker doesn't work for me, as it shows:
Synchronizing state for docker.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d docker defaults
Executing /usr/sbin/update-rc.d docker enable
Failed to execute operation: Operation not supported

and sudo systemctl is-enabled docker shows masked.

 Are you trying to connect to a TLS-enabled daemon without TLS?

sudo apt-get install apparmor and restarting the docker service worked for me

sudo apt-get install apparmor and restarting the docker service worked for me

@jfrazelle ^^ I think you were working on that part as well (apparmor)?

Ubuntu 15.04 comes with Docker 1.5 and worked out of the box. But after wget -qO- https://get.docker.com/ | sh it not longer did.  But sudo systemctl enable docker worked for me.

I had this very issue -though remembered to solve it this way back from a while ago- I'd too recommend someone expert on Ubuntu and debian installs to fix up (at least warning users) to install Apparmor as a dependency, please. I am not keen on understanding high level bash scripts that's why I cannot create a PR myself, sorry.

sudo systemctl enable docker fixed it for me too.
I was on a clean 15.04 installation, I installed docker from get.docker.com
Thanks @michielbdejong

Personally, I had to manually edit the /lib/systemd/system/docker.service and get rid -H fd:// option. I have no idea what I am doing though.

I also had to edit /lib/systemd/system/docker.service, but just to edit the options.
That's because upstart implementations uses /etc/default/docker.conf to inject options as DOCKER_OPTS. Systemd implementations instead lacks something alike, but I think it merits an other issue about it.

This is not a docs/only issue. This is an issue with the docker-lxc package for 15.04. The package install should take care of enabling docker daemon in systemd

I also ran into this issue on Ubuntu mate based on 15.04 although I actually prefer to not have docker run on startup so I just turn it on and off with sudo service docker start and sudo service docker stop as needed.

all so simple, first of all try to write ¨sudo docker run hello-world¨, daemon answer only to root user >< i spend so many time read about this problem, try so many different methods to fix this, and after all I enter into var/run/docker/docker.socket and see ther daemon user is root, that´s why I try to write sudo before docker word and it´s work >< 14.04 Ubuntu

Just confirmed that systemctl enable docker is still missing from the https://get.docker.com/ script when run on Ubuntu 15.04. Is someone working on this?

@michielbdejong : Related discussion here : https://github.com/docker/docker/pull/14217

Also, changes are coming to the installation process; https://github.com/docker/docker/pull/13680

@thaJeztah : I did not follow that PR, but does it address the issue of docker not starting automatically on Ubuntu 15.04 and above?

@ankushagarwal not fully sure; iiuc, updating the install scripts is part of that plan, and it's possible that automatic starting is part of that rewrite. However, I think I also read that making Docker start automatically on boot was intended to be a change/decision made by the user.
Erm, so in short: I don't know (yet) :blush:

Running 15.04, the sudo systemctl enable docker solution worked fine for me. No errors.
Restarted to make sure it worked and there's no problems.
@thaJeztah the docs should be updated to reflect the choice, if it's intended as a choice. It would also probably help to add to the docs the official instructions for making the docker command run with out sudo

@srcspider agreed!

on redhat
chkconfig docker on' service docker restart`
'''
Stopping docker:                                           [FAILED]
Starting cgconfig service:                                 [  OK  ]
Starting docker:                                           [  OK  ]
'''
'''
[root@tmp]# docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from hello-world
535020c3e8ad: Pull complete
af340544ed62: Pull complete
hello-world:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
Digest: sha256:02fee8c3220ba806531f606525eceb83f4feb654f62b207191b1c9209188dedd
Status: Downloaded newer image for hello-world:latest
Hello from Docker.
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:

The Docker client contacted the Docker daemon.
The Docker daemon pulled the "hello-world" image from the Docker Hub.
The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash
Share images, automate workflows, and more with a free Docker Hub account:
https://hub.docker.com
For more examples and ideas, visit:
https://docs.docker.com/userguide/
[root@tmp]#
'''


chore: Add back double verify proof to test suite

This has been fixed in the latest version of Noir. Resolves #1927
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Looking at that intermittent failure. Think we need to a few more docker logins to not get throttled.


Update repo link in README

point to the new address

@cncolder thanks for your PR! However we're in the process of migrating this plugin into a mono repo: https://github.com/csstools/postcss-plugins/tree/main/plugins/postcss-nesting so further work on these repos has been halted.
This repo will soon be archived and a message will show up in all of them

Thank you @cncolder for this PR.
The repo has moved to https://github.com/csstools/postcss-plugins and we have made the necessary changes there.


facebook limitation

How I can increase fetched items from facebook bridge ? rss-bridge can fetch only 4 items.

Facebook will only return a few posts when first loading the target page. Then subsequent posts should be loaded with a script or button on the page, so retrieving more items would be a bit complicated....
You can use a frequent refresh rate to keep up with new posts in your rss feed reader, and decrease cache duration in the facebook bridge here.

Thank you, I hope you can create new other bridge based on Facebook Graph, which can fetch 100 posts from facebook page.
Facebook Graph API needs developer account for creating app, this simple script good start :
https://github.com/scottfalkingham/facebook-rss-parser

Oh. The idea behind rss-bridge is to free the data from weird proprietary APIs, see 'Rant' at the bottom of the project's main page. The goal is to have bridges ready to use without the hassle or dependency of proprietary stuff or developer accounts. That's why we go through the hassle of parsing html code from publicly viewable webpages.
Seems like the facebook-rss-parser project you linked to is ready to use for producing RSS feeds from their API so why not just use it if you wish to?


How can we record sound from microfon as well?

Is that possible?

The GIF format does not support audio, just images.
So this would be usable only for the avi export option.
Thus i guess this might be out of scope for this Project...

@sirtet  yep of course i am talking about video exporting :D

@sirtet Yes, it's a bit out of scope right now.

+1 for capturing the mic. The editor is nice and for making quick tutorials audio capture would be ideal.

+1 for capturing the mic

+1 for capturing the mic.

@NickeManarin please reconsider? I got delighted by how much ScreenToGif has grown when I upgraded from 2.12 to 2.27.3 after a long time of using the older version. There are so many more options now, the interface is better, there's dark theme, and all of that. I really think being able to add sound either when recording the frames or as an added overlay later when editing the frames would be a huge really helpful new feature, even if it's a simple audio track. I'm sure FFmpeg has the ability to add the track to the exported video. Of course, more serious editing should be done on the exported video using a proper video workstation. But a single audio track will get the easiest types of audio inclusion done. (Examples: narration or background music)

@NickeManarin please reconsider? I got delighted by how much ScreenToGif has grown when I upgraded from 2.12 to 2.27.3 after a long time of using the older version. There are so many more options now, the interface is better, there's dark theme, and all of that. I really think being able to add sound either when recording the frames or as an added overlay later when editing the frames would be a huge really helpful new feature, even if it's a simple audio track. I'm sure FFmpeg has the ability to add the track to the exported video. Of course, more serious editing should be done on the exported video using a proper video workstation. But a single audio track will get the easiest types of audio inclusion done. (Examples: narration or background music)

This is a planned feature, but first I need to rework the editor, to support multiple tracks.

This is a planned feature, but first I need to rework the editor, to support multiple tracks.

Any update on this?
I can record video, but can't capture audio. That's disappointing.
I know the app's original purpose was to record GIFs, but now, when we can export it as video, why not add an audio capture ability?

Ahh, nevermind. I took a look at https://github.com/NickeManarin/ScreenToGif/issues/423

how to recoerd sound?

IMO an editor revamp is unnecessary. Just attach an audio sample to each visual frame on the same timing. Deleting a frame would cut out the matching audio.
This may sound limiting, but remember that it's always possible to export the video from ScreenToGif, and then open it in Kdenlive. In contrast to recording audio in a separate program, and trying to match the timing in post, this is doable and can be completely lossless (Depending on settings). A full video editor feels out of scope for ScreenToGif, and defeats the purpose of it.