meas_airspeed status aspd_com_err

Since we updated the airspeed calibration to fail if the airspeed driver has a non zero comms error count I've seen several people struggling to calibrate. After working with someone and going through the usual suggestions, use a short i2c run, 3.3V sensor, etc they were still getting low single digit error counts.
A took a look at the current driver and it's counting a comms error every time there's an i2c read failure, or the status flag from the sensor is non zero. According to the MEAS i2c guide only status 3 indicates a fault detected.

It's not clear yet if this explains some of the calibration difficultly, but it seems wrong to me. Bench tested so far, but more testing coming.

The past couple days we've tested 1.5.5 released firmware compared to a test firmware from @dagar with a modified MEAS i2c airspeed driver.
Conclusion first:
The modified driver seems to have cleared up our airspeed calibration problem.  It turns out we are getting occasional "Stale Data" status packets.  The standard 1.5.5 firmware counts these packets as errors preventing successful airspeed calibration.  The modified driver does not and instead prints a "WARN .... Stale Data" message in the console.  After many hours of testing today the modified driver has yet to get any aspd_com_err counts and always calibrates successfully.  I hope this improved driver finds it way into the released firmware.
Setup and background
We've had a lot of airspeed sensor calibration headaches for a while now.  Usually the problem is a "error count non zero" warning preventing calibration.  It typically takes 4-5 system reboots before getting a successful calibration.  Our hardware is pixracer and i2c-as airspeed sensor from AUAV (great guys!).  We have a nice clean professional installation.  However, our i2c wire harness to the airspeed sensor in the wing is almost 1 meter long and through an interconnect . Of course we suspected the wire length as the source of our problems at first, but we see the same "error count non zero" problems when plugging the sensor in directly using a short 15cm cable.
(okay yes, "1 meter professional i2c cable" might be an oxymoron, but we are stuck with i2c for now - I'll offer that we've used CANbus airspeed sensors on other UAV programs and they are great for all sorts of reasons not least among them reliability - okay off my soapbox).
As background investigation I read the following other posts related to airspeed problems:
https://github.com/PX4/Firmware/issues/6314
https://github.com/PX4/Hardware/issues/55
https://github.com/PX4/Firmware/issues/3544
https://github.com/PX4/Firmware/pull/6324
Test Details
This testing was done on multiple UAVs with ~1 meter cables as well as a simple bench setup with short cables.  We plugged in a dronecode probe (https://zubax.com/products/dronecode-probe/) and used "perf" in the console to monitor "apsd_com_err" event counts.  Here is a picture of the bench setup (sorry don't have a pic of the UAV install):

Firmware 1.5.5:
We consistently see single digit "aspd_com_err" events over test durations of 20-40 minutes.  The first event often occurs within the first minute or two after boot preventing airspeed calibration.  I suspect this is what we've been seeing for the past couple months as the source of our calibration problems.  Similar results across multiple UAVs and the simple bench setup.  Here is a typical "perf" output from one of many ~30 minute tests:

Firmware 1.5.5.(with modified MEAS i2c driver)
No more "aspd_com_err" event counts!  Similar results across multiple UAVs and the simple bench setup.  Here is a typical "perf" output from one of many ~30 minute tests:

Also, with the test firmware we get a new WARN message in the console.  Here is an example after letting the simple bench test setup (short i2c cable) sit for about and hour:

We also tested unplugging the i2c cable during operation.  When this happens we get many many error counts.  I suppose this is expected/correct behavior.
  All calibrations where successful.


Avoid using c++'s stream?

As in here:
https://github.com/dtolnay/cxx/blob/8308e991189ce6d8c2eb535a5369772d97ff8fb5/src/cxx.cc#L79
we use std::cerr which is known to escalate the binary size and is unsuitable for embedded environments. Many people disable exceptions for smaller binary sizes, so I think this request is valid. Can we use fprintf instead?
I can submit a PR if accepted.

Thanks. Please check #1240.


Add nesteds tasks

It would be helpful to be able to indent-dedent tasks to create nested tasks (sub-tasks of taks).

This is an interesting idea, though could be pretty complex! Can you elaborate on how it might work? Like what the expected behavior might be? You can certainly indent tasks now, but they have no relationship with the parent task.

I just came by to suggest something similar. I think that maybe introducing a new distinct command eg. 'parent-task' for this would be useful?
This could set up a task with its own marker that then 'observes' the state of each task that is directly beneath and with a greater indentation than the parent task. Terminating the list by a blank line(?) automatically, or by applying a secondary tag with another command given on another selected line manually (though that sounds more cumbersome/messy :/ )?
The parent task could have a tag appended to it (a la @done/@cancelled), something like @status(2/6) to show the number of completed sub-tasks, updated on the action of resolving (completing/cancelling) any sub-task. When all sub-tasks are completed the parent marker updates to show green tick (all sub-tasks completed), red cross (all sub-tasks cancelled) or a new third type of marker green tick with a small red cross subscript (majority sub-tasks completed) or red cross with small green tick subscript (majority sub-tasks cancelled).
Archiving removes a sub-task from the check and @status could go to (2/5, 1 archived), and cancelling could go to (2/5, 1 cancelled)? Parent tasks could be 1 ordinary sub-task of a higher (grand)parent task that uses just the same command.
...or something else entirely :p Certainly not thought of every possibility and not a perfect approach, but figured that sounds more doable than more full automation.

Thanks for weighing in on this, @eboracus! Right now, nested projects are supported, which comes a bit closer to the goal here too, just a thought.
I think the behavior you describe makes sense. The @status tag could be updated whenever children are updated, but it would get weird when you have more than two levels nested, right? Like, if you have something like:
task a
  task b
  task c
    task d
    task e

What happens when you complete or cancel task c? When you complete task e and task c receives an @status(1/2), what status would task a get? If you complete both task d and task e, would task c automatically be considered completed as well? I think the answers to these questions are definitely solvable, just need to make sure that the behaviors are expected. That's why i'm asking so many questions :) There could definitely be a new icon for "parent" tasks that's like a little right-pointing arrow to show it's not a project but also doesn't act like a normal task. It could allow special behavior on those types of tasks that, if you hit "complete" on a parent task, it automatically sets the complete flag on all the children of that task, thus "completing" the parent task too.
I guess i'm not so worried about the archiving process because you can keep all the tags as they are and just stack everything as normal. Maybe it keeps the indentation hierarchy, but i don't know if that's super important.

I've not used projects is that covered in the readme, I didn't see any reference.
Yes above I was admittedly, in the interests of more straight forward and faster implementation, just leaving things as: C only gets completion when D & E are completed and has no separate manual completion toggle of its own. And additionally C (or D && E together) counted as simply 1 item in A's status list.
I can definitely see having a separate manual toggle being pretty desirable too, maybe have it so issuing the command once creates a auto-completing parent task, issuing the same command again on that task creates a toggle-able completion parent task. Or just the same create task command as exists now with multiple values(?) Not sure whether two commands or 1 with three possible values would be better.
But for separately toggle-able parent tasks how about something like:

[ ] Task 1 @status(3/3, primary[0/1])
[x] Sub-task 1.1 @done()
[x] Sub-task 1.2 @done()
[x] Sub-task 1.3 @done()

where an arrow icon could turn to the subscript green tick version when all sub-tasks are done, but not the primary.
And for nested tasks:

[ ] Task 2 @status(2/5, 1 sub-task[1/2])

[x] Sub-task 2.1 @done()
[ ] Sub-task 2.2

[ ] Sub-sub-task 2.2.1
[x] Sub-sub-task 2.2.2 @done()

[x] Sub-task 2.3 @done()

[x] Sub-sub-task 2.3.1 @done()

[ ] Sub-task 2.4
[ ] Sub-task 2.5

possibly more concise labelling than sub-task in the brackets though :confused: And maybe, for more complex nesting, just stating how many sub-task are 1 away from completion, how many are 2 away etc... (and how many are 0 away with only the primary task uncompleted). Hopefully that would stop the status from becoming too difficult to read at a glance. :/
Is this implementable in the current setup?

Projects (or headers in the readme) are created by adding a : to the end of a line:
Header 1:
  ☐ First task under header

When completing or cancelling a task under a header, it automatically gets added as a tag for reference when archiving :)
Thank you for giving this so much thought! I imagine a first iteration could be pretty straightforward:

A parent task is any task item that has child task items nested within.
A parent task item cannot be manually completed or cancelled.
A parent task item will only be changed to completed if all tasks within have also been completed or cancelled, as long as at least one item was completed.
A parent task item will only be changed to cancelled if all tasks within have all been cancelled and none completed.
If all child tasks are completed and the state of the parent item has been set to completed and the user then un-completes the child task, the parent task will also be un-completed.
As children tasks are completed or cancelled, a running count in a tag on the parent item will be kept, looking only at first-level children and not grandchildren.

Some example views:
> Task 1 @status(1/3)
  ☐ Task 1.1
  > Task 1.2 @status(1/2)
    ☐ Task 1.2.1
    ✔ Task 1.2.2 @done()
  ✔ Task 1.3 @done()

✔ Task 1 @done()
  ✔ Task 1.1 @done()
  ✔ Task 1.2 @done()
  ✘ Task 1.3 @cancelled()

✘ Task 1 @cancelled()
  ✘ Task 1.1 @cancelled()
  ✘ Task 1.2 @cancelled()
  ✘ Task 1.3 @cancelled()

This should be doable within the current setup. I'm not as comfortable with toggling manual/automatic states on tasks as that may bloat the tag architecture. How do these initial rules and examples sound to you? Can you see any odd cases where they would break down?

Yes, that looks pretty reasonable to me, I don't see any major issues.
That's good that the creation of a task group can be automated (so no manual initial setup), wasn't sure if things under the hood were conducive to that without overhauling... nice. :+1: A an option of a toggle on the main task would still be 'nice', for example:
Understand issue X

Read text 1
Read text 2
Ask person Y

Reading the second text/asking someone wouldn't necessarily immediately complete the understanding and, in this case at least, adding an "Understood" as a 4th sub-task wouldn't be the most elegant way of completing things, given its repeating the opening main task.
Certainly a pretty minor issue though so its no problem if it can't be brought in in a simple way, just worth noting I think.

I just swung by the issues page to simply ask if it'd be possible to immediately indent a task after using Cmd-Enter by hitting Tab (without moving the cursor in front of the checkbox first). However, this is even cooler. :) @irrationalistic I really like your suggestion in your last post. My team and I use the tasks package extensively in Atom and we'd really appreciate this enhancement because we often have to deal with nested tasks. Thanks for the excellent work you put into this package, it's a great tool for our daily work. :)

Thanks, @cs-1! Glad this is helping you out :)
I haven't had a lot of time to work on this and i think there are still some edge cases to work out. Any help would be appreciated if anyone wants to submit a pull request ;)


Is it possible to add additional field of alert_info into ElastAlert Metadata Index ?

When using Slack alerter, Metadata Index of elastalert  will contain these two fields about alert_info.

alert_info.slack_username_override
alert_info.type

What I want to do is to add new filed alert_info.slack_channel_override into elastalert Metadata Index.
Is there any way to realize that?

I guess the implementation is here.
https://github.com/Yelp/elastalert/blob/f4bad06f35e44d664072f9a7a80580650c62fbef/elastalert/alerts.py#L1223-L1225
So the only way to add new fields into metadata index is creating a new Alerter that inherits from SlackAlerter and that has a method get_info returning new fields?
Any other way easier?

Probably no one will answer. Because we cannot take responsibility.
This is because ElastAlert may not work properly.
The source code is open to the public, so if you do it at your own risk, you can't say it freely...

We also recommend asking questions on the Gitter channel
https://gitter.im/Yelp/elastalert


improve build scripts and fix known err

improve build scripts of root build script and emesher build script;
fix reading config value error;

Very helpful


[Bug] Make opacity for fuision linear

Describe the Bug
....
Steps to Reproduce
......
The current behavior
........
The expected behavior
.........
OS
.....
Node version
.....
Browser
.....

This is the example to check about linearity of fusion
https://www.cornerstonejs.org/live-examples/changecolormap
But the example is broken
Viewport.ts:439 Actor cornerstoneStreamingImageVolume:PT_VOLUME_ID does not exist for this viewport


Downloading assets breaks when query parameters are in the URL

Describe the bug
A clear and concise description of what the bug is, and ways to reproduce it.
When using a http url as asset src the download action breaks when there are query parameters within the url. The generated destination / file path includes the query parameters after the extension which causes a write error.
Nexrender version 1.8.0
Running on windows server 2016

Oh that is very bad bug indeed, I'll try to come up with a fix asap.

published as fix in v.1.8.10

While the issue is fixed, there is still an issue with urls where the extension is not explicitly stated within the url. For example https://foo.bar/files/. The worker downloads the file just fine but because it cannot find an extension it gets saved without one and can't be used in after effects. Is it possible to provide our own filename in this scenario? I retrieve extensions by content-type headers and mime types.

I'm not sure yet on how to tackle this issue. Does anybody have any ideas?

I'm not sure yet on how to tackle this issue. Does anybody have any ideas?

Could do a HEAD request to the url given to determine its content type which should be the same as the returned file.


Add El Pinguino

Project details:

Club: ESHS Programming Club
Name: El Pinguino
Description: El Pinguino lets you scrape Travelmob locations by country and convert to JSON.
URL: https://github.com/HackerParadise2014/el_pinguino
GitHub: https://github.com/HackerParadise2014/el_pinguino
Authors:

Max Wofford

:shipit:

That was a bad idea.


python312Packages.sentry-sdk_2: 2.14.0 -> 2.15.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.sentry-sdk_2 is: Official Python SDK for Sentry.io
meta.homepage for python312Packages.sentry-sdk_2 is: https://github.com/getsentry/sentry-python
meta.changelog for python312Packages.sentry-sdk_2 is: https://github.com/getsentry/sentry-python/blob/refs/tags/2.15.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.15.0 with grep in /nix/store/32jcnzwhlcggcd6rvwq6nyf4phbvhwqi-python3.12-sentry-sdk-2.15.0
found 2.15.0 in filename of file in /nix/store/32jcnzwhlcggcd6rvwq6nyf4phbvhwqi-python3.12-sentry-sdk-2.15.0

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

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

pretix
python311Packages.sentry-sdk_2
python312Packages.sentry-sdk_2
weblate

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/32jcnzwhlcggcd6rvwq6nyf4phbvhwqi-python3.12-sentry-sdk-2.15.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/3e31a64d9262e6347a053b3394c52b3a412159a2#python312Packages.sentry-sdk_2

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/32jcnzwhlcggcd6rvwq6nyf4phbvhwqi-python3.12-sentry-sdk-2.15.0
ls -la /nix/store/32jcnzwhlcggcd6rvwq6nyf4phbvhwqi-python3.12-sentry-sdk-2.15.0/bin

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

9 packages built:

pretix
pretix.dist
python311Packages.sentry-sdk_2
python311Packages.sentry-sdk_2.dist
python312Packages.sentry-sdk_2
python312Packages.sentry-sdk_2.dist
weblate
weblate.dist
weblate.static

Maintainer pings
cc @mweinelt for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

included in staging-next, c2e30aea833d17937ce25aff8d472b5c741f2839


Impossible to come back to normal after expired refresh token error

How frequently does the bug occur?
All the time
Description
After 30 days of being logged in, users get a expired refresh token error, that I catch in syncManager.errorHandler. This seems to be the normal behavior. My problem is, I can't get back to a normal state after getting this error. If I logout/login the user, I get the same error.
I'm using email/password auth, I don't know if this happens with other authentication providers.
What to do after this error?
Stacktrace & log output
expired refresh token

Can you reproduce the bug?
Yes, always
Reproduction Steps
Repo: https://github.com/jeanbaptistebeau/realm_expiredrefreshtoken

Change the realm app ID in Authentication.swift
Run the app
Press register to create the user
Press sign in
Now the app should be working fine, you can add objects, log out and login again
Quit the app
Now go to the device settings > General > Date and time and set it manually to 2 months in the future
Run the app again
You should get the "expired refresh token" error and thus be logged out of your account
Try pressing sign in: from now on, you should get the same error everytime you log in

Version
10.15.1
What SDK flavour are you using?
MongoDB Realm (i.e. Sync, auth, functions)
Are you using encryption?
No, not using encryption
Platform OS and version(s)
iOS 14
Build environment
Xcode version: 12.5.1
Dependency manager and version: Cocoapods

@jeanbaptistebeau we've merged a PR in core that may address this issue– was your original issue that the clock was too far forward on your device?

@jsflax it seems to be included in cocoa v10.19.0.
Could you tell me what happens now, when the user gets an "expired refresh token" error? The error handler of the sync manager won't be called?

HI @jeanbaptistebeau It looks like instead of checking this on core, we are checking this on the server, so you can still use the error handle to check if you need to refresh the user access token.
Let us know if the fix worked for you, and close the issue if that's the case.


Spelling Error fixed

Coverage remained the same at 85.885% when pulling ffdd26de7c2d73039f592b659e18a06574a8631f on Henning-K:patch-1 into a53febdfdf99d16c0177f5c605bd98481a4ec50f on Geal:master.


Using nostr for contacts instead of internal system

Yes, a couple of people have suggested this.
Do you have any examples of people using nostr in a react-native app?
or do you have any example of how to create direct two-way messaging with nostr in a react-native app?

Maybe this can help:
https://github.com/neb-b/daisy
https://github.com/dyegolara/nostr-attached
https://github.com/t4t5/nostr-react
https://github.com/nostr-dev-kit/ndk-react

Thanks, I'll have to spend time looking at building on nostr.  However, I am having a hard time understanding why Blitz needs to use nostr for messaging.

Because it's decentralized, secure, and fits perfectly with Bitcoin's ethos. Plus, it opens up possibilities for cool features in the future and helps Blitz grow by connecting with the broader Bitcoin community.


Loki customers, sales, marketing, partnership

Goals
1. Current customers know without ambiguity that they can use a Managed Loki from us. Those who want to use our Managed Loki get the support they need in order to start using it.

[ ] Loki + friends demo for customers https://github.com/giantswarm/giantswarm/issues/15694 - Potentially, live event to maximize attendants. Recording so SEs and customers can access even after the live event. @piontec and @brinker211 (sig-customer-happiness)
[ ] Work with SEs to work w customers https://github.com/giantswarm/giantswarm/issues/15622 @ced0ps
[ ] What else?

2. Sales Enablement. Franz, Henning, and everyone in Giant Swarm know how to talk about our Managed Loki.
Ref: Managed Apps Unique Value Proposition
When talking to prospective customers (esp. buyers, not just users)

For whom is our Managed Loki best for?
What are their alternatives?
When should they use our Managed Loki vs an alternative? (e.g. when security, owning your logs, etc. are important)

[ ] Confirm w @foschubert and @henninglange that this would be valuable.
[ ] Do research to answer above questions
[ ] Talk to people to answer above questions. Who? @puja108 @teemow ? @piontec ?

3. Marketing. Provide logging guidance for prospective users (not buyers) in Room 2.

[ ] Why we are bullish on Loki https://github.com/giantswarm/giantswarm/issues/14031
[ ] What else? Is the goal even right? (I think w our UVP, it shouldn't be basic intro to Loki...) Brainstorm w @Oshratn , @HelloHeatherC

4. Partnership - Our offering, including this Managed Loki, is completely open source. This is because we don't believe in any form of crippleware, enterprise edition etc.
We want to prevent customers from getting locked in. We want to contribute to our open source partners. What can we do? e.g.

When we talk to customers who we think are better off using (1) DIY open source,  (2) Grafana Cloud, (3) Grafana Enterprise, we want to send these customers to them.
If they encounter customers who fit our offering better, we would appreciate a chance to talk to them.

[ ] Brainstorm w @Jul85

With the experience, customers, and knowledge we have, what can we contribute to Grafana (company)?
What can we propose to do together?
As @HelloHeatherC shared in this issue, Linkerd tweeted about @glitchcrab adding us as contributor. Maybe we can get on a call w Linkerd to brainstorm, apply the learnings to Grafana?

@giantswarm/team-halo FYI

Per point #2 I suggest adding this into sales enablement. I will add it to the next round for now.

Sidenote: We've been pushing and talking about and even contributing to Loki from day 1. The upstream Helm chart was written by Julien over night at KubeCon Seattle. We also in general have a good relationship with Grafana (Tom Wilkie is a friend of many ppl at GS and we also know others) .

Wed, 17. Feb 2021 call w @Oshratn and @Jul85 meeting notes

[ ] Write down next actions
[ ] Summarize and share

@JosephSalisbury said he can reach out

Hi @cokiengchiara ,
I reached out to Grafana yesterday and got a reply by a guy named Simeon Yep, who is responsible for business development. I will settle an appointment with him and loop @piontec in also (anyone else. Will keep you updated :-)

2. Sales Enablement. Franz, Henning, and everyone in Giant Swarm know how to talk about our Managed Loki.

Just to share progress - I got started on this. My goal is a one-pager.
As Franz, I want to know enough about Loki, so I can be a good counterpart in 5mins of conversation with a management in customer org.
What is Loki?
Loki is a logging management app. 5 main use cases for logs are: Debugging and troubleshooting (why did my application crash?), monitoring, cybersecurity, compliance, and business intelligence.
Why use Loki vs other tools for logging?
When choosing a logging solution, you can choose between proprietary or open source. Within open source, the top two options are EFK and Loki (w Promtail and Grafana). Once you decide on Loki, you can choose between DIY, SaaS (? Grafana Cloud), Managed Upstream (Grafana Enterprise Stack), or Independently Managed (e.g. Giant Swarm, Metric Fire).

Option 1: Proprietary (e.g. DataDog, SolarWinds)

I will not dwell on this and assume our target customers are more interested in open source tools.
Advantages

Easier and faster to set up than DIY
No need to devote a team of engineers to run

Disadvantages

Lack of flexibility
Priced for large enterprises. Too expensive for most.
Vendor lock in.

Option 2: Open source

In general, “logging management” has 3 parts: You collect and forward the logging data, store it somewhere, and finally, do something useful with it, such as visualize, query, and create alerts from it. Two most popular options are Elasticsearch (EFK) and Loki (w Promtail and Grafana).

Option 2a: Elasticsearch. With Fluentd and Kibana. (EFK)

Parts

Collect and forward data - Fluentd

Store it - Elasticsearch

Do something useful (visualize, query, and create alerts) - Kibana

Why EFK?

Collects lots of data from logs and stores them in a big index.

Advantages

Execute complex queries very fast

Disadvantages

Index can be bigger then original data. Means

Expensive to store. Aside from cost, you have to be mindful about what you log.

Complex

Option 2b: Loki. With Promtail and Grafana.

Parts

Collect and forward data - Promtail

Store it - Loki

Do something useful (visualize, query, and create alerts) - Grafana

Why Loki?

Which of our customers are using it?

Why Loki?
What are they using Loki for?

@cokiengchiara another dimensions on eg Datadog and also MetricFire is that they store data outside of the customers datacenter and control. This is an issue for some of our customers.

@cokiengchiara another dimensions on eg Datadog and also MetricFire is that they store data outside of the customers datacenter and control. This is an issue for some of our customers.

thank you! Would it be the same w Grafana Cloud?

Yes

In the Open Source + commercial space we should include - IMHO - https://www.graylog.org/products/open-source

RFC 0014 - Giant Swarm Managed Apps UVP is the transition between DIY and Upstream Enterprise https://github.com/giantswarm/rfc/pull/16/files

@piontec and I had a chat with Grafana Labs today:

we met up with Simeon (he is responsible for partners and business development, but more for their enterprise offering)
Grafana recently had a deal with AWS and AWS is offering Grafana now
during the call we came to the conclusion that he is not the perfect contact for us at the moment, but he will connect us to the community team ( which seems to be more suitable for us to talk since we don't want to sell any licenses or offer their enterprise solution)
he mentioned their upcoming Observability con - I will talk to their community manager about it, maybe there is an opportunity for a talk if we want to do that.

another dimensions on eg Datadog and also MetricFire is that they store data outside of the customers datacenter and control. This is an issue for some of our customers.

In the above context, it might be interesting to also look at opstrace, as they offer Loki (or rather a whole open source observability stack containing it) and their approach is to always host it in a (separate) k8s cluster inside the customer account (they spin up a standard EKS or GKE currently). They do the management somehow, but also have automation AFAIR. Their spin on it is that they do not go with Grafana, but replace it with their own product (also open source).

Mon, 15. Mar 2021

Edited and prepared for publishing https://github.com/giantswarm/giantswarm/issues/14031#issuecomment-797628460 -- waiting for feedback

For this cycle:

[ ] Repackage and push the stuff we’ve created about Loki. https://www.google.com/search?q=site:giantswarm.io+loki&ei=4z02YIi-Noe6gAbP4ryADQ&start=0&sa=N&ved=2ahUKEwjIu_rOuoLvAhUHHcAKHU8xD9A4ChDx0wN6BAgLEDI&biw=1420&bih=946
[ ] 16.03.2021 Edit simple Managed Loki sales enablement doc https://github.com/giantswarm/roadmap/issues/271#issuecomment-781443190

RFC will not be done this cycle. But want to work on it next after this cycle.

he mentioned their upcoming Observability con - I will talk to their community manager about it, maybe there is an opportunity for a talk if we want to do that.

@Jul85 were you able to talk w the community manager? :)

Hi @cokiengchiara: I reached out to them again yesterday but still got ne feedback yet. I will try again via linkedIn. Maybe that works better. Will keep you updated.

Update: Lukasz and I will have a meeting with the Loki community manager next week.  @cokiengchiara

Finally merged this one: https://intranet.giantswarm.io/docs/product/managed-apps/loki/

Feedback from Henning

Like the format! Very useful. If we create this for other building blocks/apps a central place eg on our wiki would be good, so we know where to turn to and read things up again...

Asking if anything that’s missing from the format? And, based on recent sales conversations — for which building blocks / apps would sth like this be most useful right now?

Issues waiting other people have own tickets

https://github.com/giantswarm/giantswarm/issues/15622
https://github.com/giantswarm/giantswarm/issues/14031

Longer term will work on maybe this week https://github.com/giantswarm/rfc/pull/16

So closing this.
@Jul85 please share Loki community manager notes in slack or sth 😀


Traverse in Reverse is unnecessary complex

The current implementation has time complexity O(n^2). It could be improved to O(n) by using recursion. I think it would be beneficial to have both approaches as it is the classic dilemma time vs. memory optimization.

nb

@ivancho-ifa which algorithm?

which algorithm

Guys, I believe this issue is about the reverse traversal of a Linkedlist Datastructure.


umd file index.development.js returns null for devtools

Describe the bug
The UMD file https://unpkg.com/browse/<EMAIL_ADDRESS>returns null for devtools.
I'm my case I'm consuming via shadow-cljs , the clojurescript compiler,
According to @tkdodo it also can affect cdn consumers.
Your minimal, reproducible example
https://unpkg.com/browse/<EMAIL_ADDRESS>Steps to reproduce
1- consume the umd package via cdn
2 - render query tools component
3 - it'll render null
Expected behavior
Query tools component render
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
Linux
react-query version
4.0.10
TypeScript version
No response
Additional context
No response

it's fixed in the beta we just released:
https://unpkg.com/browse/<EMAIL_ADDRESS>there are some other issues in there though, so it will be available once we generally fix this :)


Bugfix/ballot 3

Ensure that election is still running by using node version numbers for mvcc updates, a few ms window was open during which the existing-leader-but-its-ephemeral-node-gone heuristic would let 2 leaders coexist.
Close and reopen connection to zookeeper after each election failure, to ensure that ephemeral nodes are not kept around because of reused session id (would prevent ballot processes from noticing when a new election is required).
Improve logs for better debugging (with finer timestamps and hostname).

@vrancurel I created BALLOT-4 to track


[WFRP4e Core] The items image does not import on MacOS Monterey (Mac M1 Pro)

Hello,
I have a Mac M1 Pro computer on MacOS Monterey and a PC on Windows 10.
I use FoundryVTT on both plateform with the WFRP system and 3 officials modules I bought :

Core
Starter Set
Rough Nights

When a world is created and everything is activated / initialized on Windows 10, I've the items image loading fine. But on the Mac, the items images don't load up, i've default black images.
Maybe it's a permission issue on an images folder on Mac ? I sent you a discord invitation if you want to discuss about it, or if you need some screenshots or more information.
Thanks in advance.From: Mano#0633foundry: 9.269wfrp4e: 5.4.1wfrp4e-core: 2.4.4wfrp4e-rnhd: 2.4.2wfrp4e-starter-set: 2.3.4

Using custom icons


reorg for retry

Move all direct git operations into a separate construct, VersionWriter.
If a version manager that needs git is added, we also add a git writer
If spm is added, a git writer is added
If only cocoapods, and timestamp or manual, no git writer is used
All git operations can be disabled by calling noGitOperations() in the Gradle dsl
Custom git operations can be managed with a custom writer
Github release versions moved to the writer rather than the manager

Includes an update to the integration tests

Status update: Currently waiting for KG to update based on comments


What's prop name for AdMob App ID?

When I created a new AdMob app, I got an App ID and Ad unit ID for every ad unit. But I don't see where to assign App ID, for example, with AdMobBanner there is only adUnitID prop.
Thanks,

I know how to do it now :)

@Tiendq and how?

Can write how you did it ?
I tried what @Dictory said but I get errors in Android Studio.
Can you maybe provide a sample of how the full code in MainActivity.java ?
Thank you !

@Kris4an7
package ...
import ...
import com.google.android.gms.ads.MobileAds;

public class MainActivity extends AppCompatActivity {
    ...
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);
        // Sample AdMob app ID: ca-app-pub-3940256099942544~3347511713
        MobileAds.initialize(this, "YOUR_ADMOB_APP_ID");
    }
    ...
}

from quick start

@Tiendq @Dictory Out of curiosity, what is the point of assigning the AdMob App ID if ads seem to work fine with just the adUnitId? Do I miss out on anything? I didn't know about AdMob App ID.

@booboothefool Well, none from my experience.
I thought I need it, hence the question, but it turned out to work fine without it.
Thanks for the answer @Dictory !

@booboothefool it's for reporting, you could have several ad units in an app.

When I try @Dictory's method, my app "keeps stopping"


Improve the app.installation_store field consistency

App/AsyncApp enables developers to use only installation_store without oauth_settings / oauth_flow for fetching installation data. With this support, developers can serve Slack OAuth flow as a separate app and share the installation data with an app that handles incoming requests from the Slack API servers.
This pull request improves the consistency of app.installation_store field to return a single instance to remove the risks of confusing situations by misconfiguration.
Category (place an x in each of the [ ])

[x] slack_bolt.App and/or its core components
[x] slack_bolt.async_app.AsyncApp and/or its core components
[ ] Adapters in slack_bolt.adapter
[ ] Document pages under /docs
[ ] Others

Requirements (place an x in each [ ])
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've run ./scripts/install_all_and_run_tests.sh after making the changes.

Codecov Report

Merging #136 into main will increase coverage by 0.12%.
The diff coverage is 87.09%.

@@            Coverage Diff             @@
##             main     #136      +/-   ##
==========================================
+ Coverage   91.24%   91.36%   +0.12%
==========================================
  Files         148      148
  Lines        4224     4248      +24
==========================================
+ Hits         3854     3881      +27
+ Misses        370      367       -3

Impacted Files
Coverage Δ

slack_bolt/app/app.py
85.79% <84.61%> (+0.66%)
:arrow_up:

slack_bolt/app/async_app.py
94.96% <87.50%> (+0.52%)
:arrow_up:

slack_bolt/logger/messages.py
87.17% <100.00%> (+0.69%)
:arrow_up:

slack_bolt/oauth/async_oauth_settings.py
100.00% <0.00%> (+1.81%)
:arrow_up:

Continue to review full report at Codecov.

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


docs: clarification on wildcards and subdomains in FQDNs.matchPattern

Using * in CiliumNetworkPolicy to FQDNs.matchPattern does not include all levels of subdomains. This update to the docs clarifies this limitation.
Issue is highlighted in #22081
Signed-off-by: flxman<EMAIL_ADDRESS>Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Thanks for contributing!

@joestringer thanks for the approval. I am not sure why the CI PR validation fails though, considering it is just some docs.

It might be a false positive. Could you please squash the commits together and repush? Then I'll retrigger the testsuite. As long as the docs test passes, this should be OK to merge.


Update toc.yml

Docs Build status updates of commit d31fad0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamicsax2012-technet/about-accounting-distributions-and-subledger-journal-entries-for-vendor-invoices.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-accrued-loss.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-analyzing-reported-costs-for-current-production-orders.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-analyzing-variances-for-a-completed-production-order.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-assets-acquired-through-procurement.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-automatic-adjustment-transactions.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-audit-policy-violations-and-cases.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-cash-flow-in-project-control.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-changing-the-project-group.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-competencies.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-compensation-plans.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-automatically-creating-service-orders.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-cost-templates.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-costing-versions-containing-item-purchase-prices-related-to-bom-calculations.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-ax-table-classes.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-costing-sheet-setup.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-posting-profiles.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-posting-setup-for-project-transactions.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-product-builder-items.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-production-terminology.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-process-documentation.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-product-builder-processes.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-purchase-order-posting-types.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-product-change-cases.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-product-configuration-models.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-purchase-requisition-statuses.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-purchase-order-upgrade.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-profile-types-for-time-and-attendance-registrations.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-purchase-agreements.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-purchase-requisitions-enterprise-portal.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-profile-calendars-for-time-and-attendance-registrations.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-profiles-for-time-and-attendance-registrations.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-purchase-requisition-workflows.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-project-types.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-project-statements.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-project-transactions.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-project-periods.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-project-stages.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-purchase-order-encumbrances.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-purchase-order-types.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-project-quotations.md
:warning:Warning
View
Details

dynamicsax2012-technet/address-districtname-property-microsoft-dynamics-retail-ecommerce-sdk-core-models.md
:warning:Warning
View
Details

dynamicsax2012-technet/addorremovediscountcodesrequest-constructor-microsoft-dynamics-commerce-runtime-messages_1.md
:warning:Warning
View
Details

dynamicsax2012-technet/address-addresstype-property-microsoft-dynamics-retail-sharepoint-web-services-viewmodel.md
:warning:Warning
View
Details

dynamicsax2012-technet/add-the-packing-unit-and-quantity-to-a-sales-order-lines.md
:warning:Warning
View
Details

dynamicsax2012-technet/address-partynumber-property-microsoft-dynamics-commerce-runtime-datamodel.md
:warning:Warning
View
Details

dynamicsax2012-technet/address-county-property-microsoft-dynamics-retail-sharepoint-web-services-viewmodel.md
:warning:Warning
View
Details

dynamicsax2012-technet/address-emailcontent-property-microsoft-dynamics-retail-ecommerce-sdk-core-models.md
:warning:Warning
View
Details

dynamicsax2012-technet/address-email-property-microsoft-dynamics-retail-ecommerce-sdk-core-models.md
:warning:Warning
View
Details

dynamicsax2012-technet/address-addressfriendlyname-property-microsoft-dynamics-retail-ecommerce-sdk-core-models.md
:warning:Warning
View
Details

This comment lists only the first 50 files in the pull request.

dynamicsax2012-technet/about-accounting-distributions-and-subledger-journal-entries-for-vendor-invoices.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-accrued-loss.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 120: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa590435(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 122: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa590971(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

dynamicsax2012-technet/about-analyzing-reported-costs-for-current-production-orders.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-analyzing-variances-for-a-completed-production-order.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-assets-acquired-through-procurement.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 60: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa573347(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 184: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa575857(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 186: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh209549(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

dynamicsax2012-technet/about-automatic-adjustment-transactions.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 94: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa553205(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

dynamicsax2012-technet/about-audit-policy-violations-and-cases.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 67: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh209729(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 69: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh227519(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 71: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh208562(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

dynamicsax2012-technet/about-cash-flow-in-project-control.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 119: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa599440(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 121: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa586038(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 123: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa552521(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

dynamicsax2012-technet/about-changing-the-project-group.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-competencies.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 42: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa589077(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 44: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa557412(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 46: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa571288(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 54: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa550286(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 62: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa619900(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 66: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa575899(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 70: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa591442(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 74: [Warning] Link 'https://technet.microsoft.com/en-us/library/jj677419(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 78: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa577265(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 78: [Warning] Link 'https://technet.microsoft.com/en-us/library/aa554489(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

dynamicsax2012-technet/about-compensation-plans.md

Line 1: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh694711' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 1: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh208814' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 1: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh803014' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 1: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh209560' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 1: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh242871' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 1: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh209705' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 1: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh209312' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 1: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh803008' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 1: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh694712' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 1: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh781096' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 1: [Warning] Link 'https://technet.microsoft.com/en-us/library/hh781109' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-automatically-creating-service-orders.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-cost-templates.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-costing-versions-containing-item-purchase-prices-related-to-bom-calculations.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-ax-table-classes.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-costing-sheet-setup.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-posting-profiles.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-posting-setup-for-project-transactions.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-product-builder-items.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-production-terminology.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-process-documentation.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-product-builder-processes.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-purchase-order-posting-types.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-product-change-cases.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-product-configuration-models.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-purchase-requisition-statuses.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-purchase-order-upgrade.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-profile-types-for-time-and-attendance-registrations.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-purchase-agreements.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-purchase-requisitions-enterprise-portal.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-profile-calendars-for-time-and-attendance-registrations.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-profiles-for-time-and-attendance-registrations.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-purchase-requisition-workflows.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-project-types.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-project-statements.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-project-transactions.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-project-periods.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-project-stages.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-purchase-order-encumbrances.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-purchase-order-types.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/about-project-quotations.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/address-districtname-property-microsoft-dynamics-retail-ecommerce-sdk-core-models.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/addorremovediscountcodesrequest-constructor-microsoft-dynamics-commerce-runtime-messages_1.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/address-addresstype-property-microsoft-dynamics-retail-sharepoint-web-services-viewmodel.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/add-the-packing-unit-and-quantity-to-a-sales-order-lines.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/address-partynumber-property-microsoft-dynamics-commerce-runtime-datamodel.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/address-county-property-microsoft-dynamics-retail-sharepoint-web-services-viewmodel.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/address-emailcontent-property-microsoft-dynamics-retail-ecommerce-sdk-core-models.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/address-email-property-microsoft-dynamics-retail-ecommerce-sdk-core-models.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

dynamicsax2012-technet/address-addressfriendlyname-property-microsoft-dynamics-retail-ecommerce-sdk-core-models.md

Line 2: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.

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.


Fix npm run build:tests

Building tests was failing locally with Error: No example in "randomFunctionName".
Parsing comments sometimes didn't work properly due to carriage return characters.
It turned out that not all \r were removed.

👌


edited readme file and added gitignore to exclude pycharm idea folder…

… from the test project

Oleksii, good evening! Please check my home work so I can merge to main branch.

Oleksii, please review my pull request.


Path with spaces

Hi,
When I try to open an HTML file with folder names containing space, it breaks the path in several chunks and open each with a different part of the path in a separate tab.
I think you can easily reproduce it.

Your issue happens due to app not appending the double quotes on start and end, unlike which is done for URLs
or simply I could say App currently doesnt support opening html files directly. Need some registry tweaks for that work properly (I suppose u could do it as workaround, but I wont recommend it if u dont know). I will include this in stable v0.7 release.

Thanks :)


Separate 2 and 3 hits pairing and add normalization factor

close https://github.com/dachengx/axidence/issues/23

coverage: 51.224% (-1.0%) from 52.186%
when pulling e6ef7828f1d7534a9a26f311f8cfa2299bdbfb3d on n_hits_separate
into 79fd51c2df01438f476e9a64eb6d46e863890c25 on main.


fix(kic): fix kubernetes ingress controller docs

Description
This PR includes some minor fixes to KIC docs. It also updates the CLI flags reference and RBAC permissions list.
This PR might have references to KIC 2.9 but nothing that should be rendered before it's release so we should be good to merge it before 2.9 gets released.
Testing instructions
Netlify link:
Checklist

[x] Review label added
[x] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

@Kong/docs-maintainers Can we get this PR reviewed? It's needed for the upcoming KIC 2.9 release


Respect directives in .shellceckrc

In my project I have a .shellcheckrc next to my .sh files, as defined in https://github.com/koalaman/shellcheck/wiki/Ignore
This .shellcheckrc looks like this:
disable=2086
disable=3006
disable=3010
disable=3018
disable=3043

This means that shellcheck (the cli command) will ignore those codes in any of the files in that directory or below.
However, the VSCode extension only respects the directives in the files themselves.  I would hope that the VS Code extension can read the .shellcheckrc file and follow the directives therein, otherwise there is a disconnect between what successfully builds in my project and what files VS Code shows as "green".
Also funny enough, this extension also "shellchecks" the .shellcheckrc file even though the .shellcheckrc file format is not shell syntax or shell related. I think it would make sense (since this type of file is specific to shellcheck) to have it excluded from checking by default?
Thanks!

Please check this configuration. I suspect that in your case, you would want to turn it on.


CI:  fails running "sudo cilium config ConntrackLocal=true"

Test Name
Suite-runtime.RuntimeKafka Kafka Policy Ingress

Failure Output
time="2022-05-03T02:34:54Z" level=debug msg="running command: sudo cilium config PolicyEnforcement=default"
cmd: "sudo cilium config PolicyEnforcement=default" exitCode: 0 duration: 5.723549241s stdout:

time="2022-05-03T02:35:00Z" level=debug msg="running command: sudo cilium config ConntrackLocal=true"
cmd: "sudo cilium config ConntrackLocal=true" exitCode: 1 duration: 1.329499832s stdout:

err:
Process exited with status 1
stderr:
Error: Unable to change agent configuration: Patch "http:///var/run/cilium/cilium.sock/v1/config": EOF

Stack Trace
n/a

Standard Output
n/a

Standard Error
n/a

Resources

Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-Runtime-net-next/2089/testReport/(root)/Suite-runtime/RuntimeKafka_Kafka_Policy_Ingress/
ZIP file(s): https://jenkins.cilium.io/job/Cilium-PR-Runtime-net-next/2089/testReport/junit/(root)/Suite-runtime/RuntimeKafka_Kafka_Policy_Ingress/attachments/18e00001_RuntimeKafka_Kafka_Policy_Ingress.zip

Anything else?
It's interesting to see that the first command sudo cilium config PolicyEnforcement=default was success, then the next was failing mentioning that the process is unreachable.
Wondering whether the  PolicyEnforcement=default did not created this behavior?

Originaly comming from PR: #18414. We can noticed that the agent is configured using masquerqding iptable. All the changes from PR #18414 are related to BPF,

Copying & pasting the entire output from jenkins in case we lose it, as the original description here doesn't include all of the information about this failure:
Stacktrace
/home/jenkins/workspace/Cilium-PR-Runtime-net-next/runtime-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:465
Expected command: sudo cilium config ConntrackLocal=true
To succeed, but it failed:
Exitcode: 1
Err: Process exited with status 1
Stdout:

Stderr:
 	 Error: Unable to change agent configuration: Patch "[http:///var/run/cilium/cilium.sock/v1/config":](http://var/run/cilium/cilium.sock/v1/config) EOF

/home/jenkins/workspace/Cilium-PR-Runtime-net-next/runtime-gopath/src/github.com/cilium/cilium/test/runtime/kafka.go:108
Standard Output
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs

Standard Error
02:34:47 STEP: Running BeforeAll block for EntireTestsuite RuntimeKafka
FAIL: Expected command: sudo cilium config ConntrackLocal=true
To succeed, but it failed:
Exitcode: 1
Err: Process exited with status 1
Stdout:

Stderr:
 	 Error: Unable to change agent configuration: Patch "[http:///var/run/cilium/cilium.sock/v1/config":](http://var/run/cilium/cilium.sock/v1/config) EOF

02:35:02 STEP: Running JustAfterEach block for EntireTestsuite RuntimeKafka
===================== TEST FAILED =====================
02:35:02 STEP: Running AfterFailed block for EntireTestsuite RuntimeKafka
cmd: sudo cilium endpoint list
Exitcode: 1
Err: Process exited with status 1
Stdout:

Stderr:
 	 Error: cannot get endpoint list: Get "[http:///var/run/cilium/cilium.sock/v1/endpoint":](http://var/run/cilium/cilium.sock/v1/endpoint) dial unix /var/run/cilium/cilium.sock: connect: connection refused
	 Is the agent running?

cmd: sudo cilium policy get
Exitcode: 1
Err: Process exited with status 1
Stdout:

Stderr:
 	 Error: Cannot get policy: Get "[http:///var/run/cilium/cilium.sock/v1/policy":](http://var/run/cilium/cilium.sock/v1/policy) dial unix /var/run/cilium/cilium.sock: connect: connection refused
	 Is the agent running?

===================== Exiting AfterFailed =====================
02:35:18 STEP: Running AfterEach for block EntireTestsuite RuntimeKafka
02:35:38 STEP: Running AfterEach for block EntireTestsuite

[[ATTACHMENT|[18e00001_RuntimeKafka_Kafka_Policy_Ingress.zip](https://jenkins.cilium.io/job/Cilium-PR-Runtime-net-next/2089/testReport/junit/(root)/Suite-runtime/RuntimeKafka_Kafka_Policy_Ingress/attachments/18e00001_RuntimeKafka_Kafka_Policy_Ingress.zip)]]


jshint, es6 & ESlint

None of the extensions are working, can you please help me!!!!

/needsMoreInfo


Makefile:46: recipe for target 'statics' failed

This issue is present but closed but now i am feeling this difficult to debug this problem though it is a small error i think so
please guide me to debug this

I installed GO language using command
sudo snap install go --classic
go version =>go version go1.12.9 linux/amd64
then cloning the git repository git clone https://github.com/brocaar/loraserver.git
cd loraserver
sudo make dev-requirements
sudo make
I am getting the go-bindata executable file not found in $PATH
so i did go get -u github.com/jteeuwen/go-bindata/...
as @brocaar  said
not worked for me
then i found the bin directory where dev-requirements were installed i did
export PATH=$PATH:$GOPATH/bin
giving same Error
help me !!
ignore my english please

The recommended way is to use the provided Docker image for compiling the source, please see https://www.loraserver.io/loraserver/community/source/ for instructions and commands to execute.

This issue is present but closed but now i am feeling this difficult to debug this problem though it is a small error i think so
please guide me to debug this

I installed GO language using command
sudo snap install go --classic
go version =>go version go1.12.9 linux/amd64
then cloning the git repository git clone https://github.com/brocaar/loraserver.git
cd loraserver
sudo make dev-requirements
sudo make
I am getting the go-bindata executable file not found in $PATH
so i did go get -u github.com/jteeuwen/go-bindata/...
as @brocaar said
not worked for me
then i found the bin directory where dev-requirements were installed i did
export PATH=$PATH:$GOPATH/bin
giving same Error
help me !!
ignore my english please

Hey @brocaar !
I am also getting the same issue. There seems to be some kind of problem in migrations.go file.
Previously, I compiled the code on Ubuntu 18.04.3 LTS(without Docker), 4 times, and it compiled successfully, but right now, I am trying to compile the code on Ubuntu 16.04.6 LTS, it is giving the same error as above, when I try to make build.
Is there some kind of dependency on Ubuntu Version?
The go-bindata binary is already present in my $GOPATH/bin but it still can't find it in the $PATH. Kindly suggest a solution to this(without using Docker).
error: ```
Generating static files
internal/migrations/migrations.go:1: running "go-bindata": exec: "go-bindata": executable file not found in $PATH
Makefile:46: recipe for target 'statics' failed
make: *** [statics] Error 1
`GOPATH="/home/network-server"`

`$PATH = -bash: /home/network-server/bin:/usr/local/go/bin:/home/network-server/bin:/usr/local/go/bin/bin:/home/network-server/bin:/usr/local/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin: No such file or directory
`


Jupyter notebook integration

Since we use HistomicsTK in Jupyter notebooks, I'm not sure what this issue is requesting.  I'll close this; please reopen with more specifics if desired.


Network Watcher Agent on Target

Why is it required to install the Network Watcher Agent on the Target machine for the probe. Isn't the agent just required on the server that is going to be sending the packets to validate the connection?
Thank you in advance,
Hernán

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3bf662d1-53fb-f651-ee67-6e174836d739
Version Independent ID: 67782b9a-1dd5-acb4-6d93-62ee9ff60d43
Content: Monitor network communication - tutorial - Azure portal
Content Source: articles/network-watcher/connection-monitor.md
Service: network-watcher
GitHub Login: @KumudD
Microsoft Alias: kumud

@hjlarrea The agent is required on both machines to know if the probe reached the destination machine successfully. if we check the connection between 2 VMs VM1 & VM2, and the connection fails, we have more information about where the failure Is occurring if traffic is reaching VM2 but not returning properly back to VM1.
Please let me know if you need any additional clarity.

Perfectly clear, thanks for the answer.
Now, one last question, let's say that I want to test connectivity against an on-premise hosted service, in that case I wouldn't be able to install the Network Watcher extension on the other side (not just because is not Azure hosted, but I don't own the server, so even if there is an agent installer is not an option for me to deploy it).
Given what you've said, that means that Network Watcher / Connection Monitor is not fit for my scenario, or it will work, but it will not provide as much information as it could if the agent was to be installed on both sides?
Thanks in advance for the info!

@hjlarrea If the endpoint is not another Virtual Machine, you can still use Azure Network Watcher to monitor and troubleshoot, but the diagnostics & results will not be as thorough as between 2 VMs.
If you do have access to the on-prem machine, you can also look into Network Performance Monitor.

Awesome, thanks a lot for the info!

Closing the issue -


debian package deinstallation – many files remain

$ sudo find / -iname \*influxdb\*
/etc/rc6.d/K20influxdb
/etc/init.d/influxdb
/etc/rc3.d/S20influxdb
/etc/rc2.d/S20influxdb
/etc/rc4.d/S20influxdb
/etc/rc1.d/K20influxdb
/etc/rc0.d/K20influxdb
/etc/rc5.d/S20influxdb
/var/log/influxdb
/var/opt/influxdb
/opt/influxdb

$ ls /opt/influxdb/
influx  influxd  init.sh # broken links

You need to purge: --purge.

I did already.

Sending this to the man that knows best.

@rossmcdonald -- happy to discuss this and share what I've learned from trying to solve this issue.

We are experimenting with simplifying our open GitHub Issues. This feature request has been rolled into an aggregate issue for all packaging requests, so that we can close this issue until we are ready to work on it.
You may continue to make comments here. Closing the issue does not mean we are rejecting this idea.


Restarting project from services panel no longer works

Describe the bug
I have updated Rider to 2024.3 and the plugin to 1.6.4 and I can no longer restart projects from the services panel. My current Aspire version is 8.2.1.
If I update the Aspire AppHost to 9.0.0, the restart button will now not be greyed out but clicking will only restart the project and not rebuild it like it did before, meaning that any changes to the source code will now no longer be reflected in the restarted project.
In addition, the restart with debug button that was previously on the services panel has now disappeared as well.
To Reproduce
Steps to reproduce the behavior:

Start apphost project
Restart button is greyed out

After updating to Aspire 9:

Expected behavior

Restart button works on all Aspire version
Restart with debug button appears again.

System information:

OS: Windows 11 (22631)
.NET version: 8.0.404
JetBrains Rider version: 2024.3
Aspire plugin version: 1.6.4
Aspire workload version: 8.2.1

Downgrading to 1.6.0 of the plugin seems to restore functionality back to normal.

Hello! This is not a bug, we've switched to the Aspire Dashboard API instead of our internal implementation. Unfortunately, it looks like it's only available starting with .NET Aspire 9.0, so it's not supported for previous versions. And the Dashboard API doesn't have a feature like restarting with a debugger, so it's not available anymore.
https://learn.microsoft.com/en-us/dotnet/aspire/whats-new/dotnet-aspire-9?tabs=windows#manage-resource-lifecycle

clicking will only restart the project and not rebuild it like it did before, meaning that any changes to the source code will now no longer be reflected in the restarted project

Sorry, I've missed that part. Yes, we should build the project before restarting it.

Not being able to restart with a debugger is pretty annoying since that is the easiest way to debug startup code.
I know this would be for Visual Studio, but in that section it does mention

For project resources, when the debugger is attached, it's reattached on restart.

Is it not be possible to store some internal state inside of the plugin that contains a list of projects that want to be debugged (and is added to by pressing the restart with debugger button). Then upon receiving a start/restart command from Aspire, automatically attach a debugger to the project and remove it from the list.
Or failing that, would it be possible to but a button on the services panel for the project to attach a debugger to a running process so I would not have to go hunting for it in the attach to process dialog.

Thank you, I'll think about it.


Add coremod support

Add the MANIFEST.MF attributes, and the -Dfml.coreMods.load property to the generated launch files.

Should also make it easy to add and shade Mini, since that's a thing now.


Sidenav not working

The Sidenav is not working even on the new Starter Template Provided there  were always Null Errors
Uncaught TypeError: Cannot read property 'M_Sidenav' of null at HTMLBodyElement._handleTriggerClick (materialize.js:5479)
_handleTriggerClick @ materialize.js:5479

What version?

You can see the error on this page:
http://next.materializecss.com/templates/starter-template/preview.html
Stretch the page until the menu shows & then click to reproduce.
Version: 1.0.0 Alpha-1

I get this error with Firefox using 1.0.0 Alpha-1:
Empty string passed to getElementById().  materialize.js:5479:32

I did some debugging I found out the problem:
The function  getIdFromTrigger expects the  data-target  attribue to be available, but the documentation example uses  data-activates .
Changing  data-activates to  data-target fixed this error & the menu is working.

Same issue on 1.0.0 Alpha-1. Should we get back to .100?

@peecaboo Try changing your data-activates attribute on the sidenav-trigger class element to data-target. I believe that will fix the problem for you.
Here's a picture:

https://github.com/Dogfalo/materialize/blob/v1-dev/js/global.js#L261

@matugm It worked!  I thank you

@matugm  I thank you too  XD

This is already the case in the newest templates

@

same error even if i have data-target.... any ideas ?

@stefancata92 Please create a new issue illustrating your example with a Codepen

@stefancata92 you get this error message if you have another id on your side menu. Make sure you are using mobile demo on both places.
<a href="#!" data-target="mobile-demo" ... >

i've got this error, but only in situation when trigger={element} was not
Try to wrap your trigger component into  link :
menu

Still giving me a problem

This issue is still not resolved

@GeorgesGITHUB live example or codepen please, so we can help.

@GeorgesGITHUB live example or codepen please, so we can help.

nvm, it was a simple mistake. Works good

Try to set the id attribute in sidenav ul
`
Home
QA Bank
Blog
`

I get this error with Firefox using 1.0.0 Alpha-1:
Empty string passed to getElementById().  materialize.js:5479:32

I did some debugging I found out the problem:
The function  getIdFromTrigger expects the  data-target attribue to be available, but the documentation example uses  data-activates .
Changing  data-activates to  data-target fixed this error & the menu is working.

ua a star,l got it

bravo


Update group.js

Allow to use triggersEnter in Group without Array (like in FlowRouter)
It is work:
FlowRouter.route '/',
  triggersEnter: (context, redirect, stop) ->

But it has error: this._triggersEnter.concat is not a function
Routes = FlowRouter.group
  triggersEnter: (context, redirect, stop) ->

did this ever get resolved?? I'm still getting this error when attempting to add a trigger to route group and individual route in that group:
Error: "Uncaught TypeError: this._triggersEnter.concat is not a function"
Caused by: "options.triggersEnter = this._triggersEnter.concat(triggersEnter);"
Code:
const privateRoutes = FlowRouter.group({
  name: 'privateRoutesGroup',
  triggersEnter: function() {
    if(!Meteor.userId() && !Meteor.loggingIn()) redirect(FlowRouter.path('login'));
  }
})

privateRoutes.route('/home', {
  name: 'home',
  action: function() {
    BlazeLayout.render('homeLayout', {
      header: 'header',
      sidebar: 'userSidebar',
      main: 'userPool'
    });
  }
});


Fix cross-reference in custom plugins doc of user guide

Context
The cross-reference link to the Lazy Configuration page of the User Guide is broken. This patch fixes the malformed cross-reference syntax and uses the correct cross-reference.
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commmits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[x] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

Awesome @k-mack! I've confirmed this fixed the link to the Lazy Configuration page.
Thanks so much, and deepest welcome as a new contributor!


Use named ports

Named ports helps with better reasoning over the service's port
abstractions.
a series of perceived tiny improvements from while working on #193

Yes, definitely a good idea, but I'm a bit concerned with changing the service port to 80 from 8000. I'm trying to figure out when that port is used and I'm not sure. It would be used for internal k8s communication, so may affect the health check for example.

The service port 80 (or 443) is only used when the service is accessed directly. That only is the cade for a cluster wide ingress controller (since containerd/ etc) are not plugged into the k8s dns when pulling images. So any "in cluster" fetching would have to go through node port anyway (localhost:).
In order not to (implicitly) insinuate it's relevant we probably should leave it at 8000. I'll fixup.

Yeah, it can't affect the health check as that must be implemented at the container level (I think even below the pod level).
It probably depends on the ingress controller - I think most of them try to avoid the overhead of going through the service and enumerate the pods directly (at least that's what the nginx ingress used to do).

So I forced pushed and reverted back to 8000 to avoid any tacit not-yet-vested implications.

I'm about to merge this.
In general the installers need more testing with various platforms. We may be able to extend the existing Helm tests with microk8s to cover some cases, but others need tests with specific platforms e.g. GKE which is more difficult to automate.


Can't leave clippy lints unfixed 😅

(llogiq like and 3 more people like this 👍)

Thanks for your efforts! But there is now a merge conflict.

Oh no, you pushed your changes 😅 It was mergeable before ;)

@jbethune Here you go :) Thanks for the presentation!


API cleanup: Remove getDataflowClient() from DataflowPipelineJob

DataflowClient can be easily get from PipelineOptions, and I think getDataflowClient() doesn't belong to DataflowPipelineJob.

R: @lukecwik

LGTM


AsyncDefog

For postgres and redshift, we have the asynchronous asyncpg to replace psycopg2
For mysql, we have aiomysql to replace mysql.converter
However, for Databricks, Snowflake, BigQuery, and SQL Server, no native asynchronous alternatives were found. To mimic asynchronous behavior for these databases, we are using asyncio.to_thread to handle blocking operations in a non-blocking manner.
Methods of AsyncDefog have the exact same signature (name, params) but have to be awaited. The initial methods like save_connection_json, check_db_creds, to_base64_creds, from_base64_creds are kept as it is (not made async) but do let me know if those also need to be async and that will be a 3 mins fix (because it will just need wrap its parent class's method into an async function).
create_table_ddl and create_ddl_from_metadata also made async under async_admin_methods for the sake of consistency even though they are not I/O bound or db intensive.

Thanks for pointing this out! Will add native support for these!
Get Outlook for iOShttps://aka.ms/o0ukef

From: Rishabh Srivastava @.>
Sent: Tuesday, September 10, 2024 10:03:11 PM
To: defog-ai/defog-python @.>
Cc: Muhammad Abdullah @.>; Author @.>
Subject: Re: [defog-ai/defog-python] AsyncDefog (PR #61)
    - External Email -

@rishsriv approved this pull request.
Thanks Abdullah! This looks very, very good. And +1 for the tests.
Could you please add native asynchronous mode for the following:

Snowflake: example herehttps://docs.snowflake.com/en/developer-guide/python-connector/python-connector-example#submitting-an-asynchronous-query
SQLServer, by using aioodbc. Example herehttps://github.com/mkleehammer/pyodbc/issues/901#issuecomment-869225912

After that, I can test and merge!
—
Reply to this email directly, view it on GitHubhttps://github.com/defog-ai/defog-python/pull/61#pullrequestreview-2292635011, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZGPXGWBY5KVWH5A6W4EVDLZV33Z7AVCNFSM6AAAAABN6POFK2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEOJSGYZTKMBRGE.
You are receiving this because you authored the thread.Message ID: @.***>


PostgreSQL connecting article

Detail how to find and use the connection details for this service

Code samples are included in the docs


Option to run tests on previous build

Feature request:
Reason
For larger projects this will greatly increase build time on automated build servers where running tests is prerequisite for successful build. For example our builds now take 10-15min. Having also tests doubles that time.
Example usage
ng test --path path/to/existing/build --query=<something to pass through to phantom via query params>
What I tried
ng test --build false didn't help and the build was run
Possible issues
can this work with --aot flag?

Links to existing feature and pull requests in ember-cli

https://github.com/ember-cli/ember-cli/issues/4872
https://github.com/ember-cli/ember-cli/pull/4874

Angular CLI and Ember CLI use vastly different build systems.
In ours, it doesn't make sense to use an existing build for unit tests. A build application has no unit test code, nor does it have the TS code needed for the unit tests to import.


Face helmet on a phone application

Context and Problem Statement
With a face helmet we can capture the face movement reliably.
Describe the proposed option and how it helps to overcome the problem or limitation
We don't have a way to talk to v-sekai for capture.
Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams

Run the v-sekai app
Export either VMC or Godot Networking protocol for facial tracking
Open question on how to have tracking.

Positive Consequences
No response
Negative Consequences
No response
Option graveyard
No response
If this enhancement will not be used often, can it be worked around with a few lines of script?
Not a few lines of script.
Is there a reason why this should be core and done by us?
I have the raw materials to do this.
References

V-Sekai

License of the contribution
Copyright (c) 2022 K. S. Ernest (iFire) Lee
Copyright (c) 2022 V-Sekai contributors.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Added as part of https://github.com/V-Sekai/V-Sekai.github.io/commit/71779d0bbc5a68663f049852a77ecc4c2e10b03d


Update line and column

Summary
Update line and column on cursor change
Changes Made
Update line and column on cursor change
TODO
None
Motivation
Make the UI and Extensions update on changes.
Testing
None
Screenshots/GIFs

Checklist
Please ensure all of the following are completed before submitting the PR:

[x] Code has been tested and verified.
[x] Documentation has been updated to reflect the changes.
[x] All tests pass successfully.
[x] Code follows the project's coding guidelines and style.
[x] The branch is up-to-date with the latest changes from the main branch.
[x] Reviewed by at least one other contributor.

Related Issues
None
Additional Notes
None

Thanks for submitting a pull request!
We will review it as soon as possible.

Hey @0xWDG,
Thanks for your contribution.
Your PR has been merged!
Your name will appear on https://auroraeditor.com/#contributors in a few moments, if you have contributed to the editor.
Thanks again for your contribution!
Kind Regards,
Aurora Editor Team.


Priority issue: phpdoc_types_order should run before no_superfluous_phpdoc_tags

The PHP version you are using ($ php -v):
PHP 7.1.18 (cli) (built: May 25 2018 19:18:59) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.1.18, Copyright (c) 1999-2018, by Zend Technologies

PHP CS Fixer version you are using ($ php-cs-fixer -V):
PHP CS Fixer 2.12.1 Long Journey by Fabien Potencier and Dariusz Ruminski
The command you use to run PHP CS Fixer:
vendor/bin/php-cs-fixer fix -v --using-cache=no
The configuration file you are using, if any:
Basically the same as dmvdbrugge/dynamic-components, except explicit_string_variable, header_comment, no_alternative_syntax, and no_unset_on_property
If applicable, please provide minimum samples of PHP code (as plain text, not screenshots):

before running PHP CS Fixer (no changes):

/**
 * @param null|string $myStr
 */
public function testFunc(?string $myStr);

after first run:

/**
 * @param string|null $myStr
 */
public function testFunc(?string $myStr);

after second run:

public function testFunc(?string $myStr);

expected:
Immediately arrive at the last step

This could also be seen as a bug in no_superfluous_phpdoc_tags that it doesn't think null|string is superfluous, whereas it (rightfully) does think so about string|null.
Meta: this is case 4 of #3844

This could also be seen as a bug in no_superfluous_phpdoc_tags that it doesn't think null|string is superfluous, whereas it (rightfully) does think so about string|null.

Indeed I would consider it a bug in no_superfluous_phpdoc_tags.


Better type def for CLI args

Right now it basically has all type as possible available. It would be awesome if we could define an interface for each command and get rid of some !s
NOTE: I've spent hours trying to get this to work just right but haven't really gotten close at all

Depending on how bold you want to be about this, oclif is the best CLI framework I've seen for this kinda thing (and is fully typed)


Event bus system

It will solve several problems.

It will much easier to implement  CLI: addition/exctraction progress bar #31, because otherwise we need to redo addition/excratcion logic so it can yield back to the caller what file is processing/processed at this moment. With event bus we can register listener for events FileAdded/FileExtraced that would print in CLI or show some progress bar in GUI and just fire those events in the lib.

As @romibi said in Backup functionality and its Tests needs refactoring and maybe has some bugs  #38:

Maybe using callbacks in Scrap Packed File "DoOnBeforeSave", "DoOnSaveSuccess" and "DoOnSaveError"?

It can be done with same event bus system

It appears that C# already have pub/sub system with delegate and event keywords :sweat_smile:


Path switch was wrong

The -e is used for env vars. --path or -p are the correct arguments for the prisma export command

Thanks for catching this @c316 and apologies for the delay! While we're now on a newer version of Prisma and the content is outdated, it's still a valuable fix for developers that are using an older version  🙏


Epic: improve walreceiver observability

[ ] https://github.com/neondatabase/neon/issues/3115

There's only one item left: https://github.com/neondatabase/neon/issues/3115, the rest were moved to more general observability epic https://github.com/neondatabase/neon/issues/3218 , so closing this Epic and leaving its item alone.


Apply clang-format

Stack from ghstack (oldest at bottom):

-> #319
#318
#317
#316

IMO clang-format should have been applied right away, but also I wonder if the repo has a clang-rules to follow (default 80 lines per character is imo too restrictive, in PyTorch we extend it to 120)

yeah I forgot and was too lazy to go back to old commit, apply clang-format and resolve merge conflict. Hence resorted to this.

Do you want me to change the base commit and fix clang-format? I dont suppose this is too important though, is it?


Create an issue template similar to what is used in the grails-data-mapping plugin

This will be great for prompting users to supply the information required to reproduce and fix the issue.
Example issue template: https://github.com/grails/grails-data-mapping/blob/master/ISSUE_TEMPLATE.md

Closed by : https://github.com/grails-plugins/grails-spring-security-core/commit/397ceda47a88d0d5aa81c758806a50bcd5fc8c17


center figures

just adds #| fig-align: center to all figure generating chunks

Start fresh on a new branch


Tracking issue: More flexible tables

This issue's contents are under construction. More information might be added over time.

Check out the planning document: https://pgbiel.github.io/typst-improv-tables-planning/main.pdf

(Source: https://github.com/PgBiel/typst-improv-tables-planning)

Discord forge thread link: https://discord.com/channels/1054443721975922748/1182377294682128445

Planned Roadmap: (order and items subject to change)

[x] 1. Grid and table API unification (https://github.com/typst/typst/pull/3009)

Related issue(s): https://github.com/typst/typst/issues/2616

[x] 2. Per-cell customization (table.cell element, perhaps other initial refactors)

[x] Initial cell elements with basic properties (align, fill, inset local overrides) https://github.com/typst/typst/pull/3037
[x] Add x, y fields to cell elements https://github.com/typst/typst/pull/3050

[x] 3. Merged cells (colspan, rowspan)

Related issue(s): https://github.com/typst/typst/issues/131
[x] Issue https://github.com/typst/typst/issues/1386 will also have to be resolved.
[x] Colspans (https://github.com/typst/typst/pull/3239)
[x] Rowspans (https://github.com/typst/typst/pull/3501)

[x] 4. Line/stroke customization (https://github.com/typst/typst/pull/3393)
[ ] 5. Repeatable headers

Related issue(s): https://github.com/typst/typst/issues/400
[x] Headers MVP/in first row (https://github.com/typst/typst/pull/3545)
[ ] Headers in arbitrary positions Split off into #5375
[ ] Subheaders Split off into https://github.com/typst/typst/issues/5377

[ ] 6. Repeatable footers

[x] Footers MVP/in last row (https://github.com/typst/typst/pull/3577)
[ ] Footers in arbitrary positions Split off into #5375
[ ] Subfooters Split off into https://github.com/typst/typst/issues/5377

[ ] 7. More? (Table orientation, other ideas) Further ideas will become separate issues.

Closing as the initial round of features was merged into Typst 0.11. Any further features are tracked in separate issues.


Shop API Integration

Hello,
First thank you for your great work !
Could you please indicate in the doc how to use this plugin with the Sylius Shop API ?
Thank you !

@pierre-H Have you found a way to make it work? What i'm trying to accomplish is to simply redirect the user to the mollie payment page without having to select a payment method on my own website. Also, i can't even find the "Load methods" button, i have no idea where to find it and my Sylius interface is way different from the screenshots in the docs. As far as i've seen everything in this bundle is build around selecting a payment method on your own website, not in the Mollie "payment portal".
Thanks :)

Unfortunately no.
I've decided to give up this plugin and to use the ReactJS Stripe plugin.

Hi @pierre-H ,
We've decided to not implement the Shop API, as this will be deprecated(Read more here).
The replacement API Platform is something we'll jump on as early as possible. This seems to be released somewhere around September 2020. Keep an eye out on the releases to see how we make sure you can integrate all necessary channels!
Kind regards,
Merijn
Technical Partner Manager Mollie


Use field.name for DeferredAttributes for Django 3.x, fixes #20

This PR should fix #20

Codecov Report

Merging #21 into master will decrease coverage by 0.83%.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master   #21      +/-   ##
=======================================
- Coverage   57.84%   57%   -0.84%
=======================================
  Files           6     6
  Lines         204   207       +3
=======================================
  Hits          118   118
- Misses         86    89       +3

Impacted Files
Coverage Δ

sphinxcontrib_django/docstrings.py
41.44% <0%> (-0.84%)
:arrow_down:

Continue to review full report at Codecov.

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


Fix where refine is placed in test tilesets

This problem was in the Batched, Composite, Instanced, and Points folders. At least not in the Tilesets folder.

Good catch!


[Gardening] Add troubleshooting links to getting started

Add forums threads links as references to troubleshooting section in the forums.
Add notes about --test flag when used with --Xcode which is a common source of issues when people try to build.

@AnthonyLatsis, all fixed and looks indeed better. Thanks!

@swift-ci Please smoke test

Ah, having to run the CI for this got me thinking if that is really needed. Wonder if swift-ci could detect that only markdown files were changed and skip build and testing? Maybe that was discussed already at some point @xedin


Upgrade to Angular 8

At the moment ngx-translate does not support Angular 8 offically. Please upgrade the package.

It works fine with v8. What do you mean by does not support v8 officially?

In the documentation there is no hint that it works with Angular 8 and the package.json refers also to Angular 7 dependencies.
That’s why I created this issue.

The package.json says ">= 7" which includes v8
I'll update the readme


Multicluster group support

Fixes #384

Hi @froesef
We talked about making multiclusterGroup part of the razee configuration.
Before reviewing, did you decide not to? can you share why?

You're right it belongs into the razee configuration. I changed this. Let's wait for https://github.com/IBM/satcon-client-go/pull/30 to be merged. Then we won't depend on a branch of a fork but on master branch of that dependency.


support jsx-control-statements

Personally, the only use I've found for eject commands so far is is to add the jsx-control-statements support.
It would be nice if it would be supported by default, with the eslint-plugin-jsx-control-statements as well.
If it seems a good idea, I can try to do a pull request

Hi, thanks for the suggestion. We won't be adding any plugins that extend JSX behavior with something that isn't overwhelmingly adopted in the ecosystem. This makes people new to React confused about what exactly JSX is, and which features come “out of the box”. For example we don't want somebody using Create React App posting a StackOverflow answer using this syntax, and other people being unable to run it. I hope this helps, even if this isn't what you wanted to hear, sorry!

For those that found this via Google, try using https://github.com/timarney/react-app-rewired which can allow you to extend create-react-app configs