Change transition selection component not working

We have an ATEM Mini Pro (v8.4) and I'm trying to turn the upstream keyer on and off directly before a transition in order to control the state of our custom PIP when using upstream keyer 1 DVE configured to an input. The 'change transition selection component' is exactly what I wanted and have downloaded the latest Companion (2.1.1 - 4797bf3-2584 at the time of this writing) but when I configure it to either 'Key 1 & On Air' or 'Key 1 & Off Air', it does nothing. Even with a dedicated button to turn it on and off, set to Toggle, Off, or On, it does nothing. Is this supposed to work on the Mini Pro or is this a known issue? Otherwise, this appears to be a bug. I'd so like to use this instead of the macros I'm using today, since those only toggle it on or off and don't set it direct to a specific state.

I have just tested this in the exact same build and it is working for my mini pro iso, so I don't know why it wouldnt be working for you.
Just to check, you are expecting the yellow row of buttons here to be changing. And you have background already enabled? (the atem wont let that it go to nothing)

Yes, absolutely correct. I’ll double check tonight that the background was
still enabled but I’m pretty sure it was. Thanks for checking  I’ll get
back to you and confirm.
On Mon, Sep 21, 2020 at 6:50 AM Julian Waller<EMAIL_ADDRESS>wrote:

I have just tested this in the exact same build and it is working for my
mini pro iso, so I don't know why it wouldnt be working for you.
Just to check, you are expecting the yellow row of buttons here to be
changing. And you have background already enabled? (the atem wont let that
it go to nothing)
[image: image]
https://user-images.githubusercontent.com/1327476/93763237-f810a600-fc08-11ea-949c-b0cd71c16035.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-bmd-atem/issues/83#issuecomment-696064430,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWZ2KQL452VMVQCYAGDGKLSG44ZBANCNFSM4RUDEB2Q
.
--
Todd Witten
<EMAIL_ADDRESS>

I was able to confirm that you were right. I did not understand the
interaction between the "Change transition selection" and the "Change
transition selection component" feature.
I finally got it to work, though it would be nice if the "Change transition
selection component" feature, when setting the Key 1 state to a specific On
or Off state didn't do the opposite if that button is hit a second time.
That seems to be counter-intuitive as compared to the Toggle feature, which
ended up working well for me. It's all about what's left in the Preview
state at the end of the steps and I know this may be a BlackMagic thing and
not a module thing, but it doesn't work the way I expected it to when
setting an explicit state.
Thanks again for all of your work on this. This will make our workflow at
church much more approachable by those less tech-savy and give more
opportunities for those to serve. Very much appreciated. Thanks!
Todd Witten
<EMAIL_ADDRESS>On Mon, Sep 21, 2020 at 5:23 PM Todd Witten<EMAIL_ADDRESS>wrote:

Yes, absolutely correct. I’ll double check tonight that the background was
still enabled but I’m pretty sure it was. Thanks for checking  I’ll get
back to you and confirm.
On Mon, Sep 21, 2020 at 6:50 AM Julian Waller<EMAIL_ADDRESS>wrote:

I have just tested this in the exact same build and it is working for my
mini pro iso, so I don't know why it wouldnt be working for you.
Just to check, you are expecting the yellow row of buttons here to be
changing. And you have background already enabled? (the atem wont let that
it go to nothing)
[image: image]
https://user-images.githubusercontent.com/1327476/93763237-f810a600-fc08-11ea-949c-b0cd71c16035.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-bmd-atem/issues/83#issuecomment-696064430,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWZ2KQL452VMVQCYAGDGKLSG44ZBANCNFSM4RUDEB2Q
.
--
Todd Witten
<EMAIL_ADDRESS>

I dont follow what you mean with:

it would be nice if the "Change transition selection component" feature, when setting the Key 1 state to a specific On or Off state didn't do the opposite if that button is hit a second time

Tacking on here, because I feel like I'm running into the same issue and I'm not clear from the thread what the resolution was.
Is there documentation anywhere about what the "Change transition selection component" action is supposed to do? Based on the naming, I would expect that, for example, if Key1 is currently deselected for the next transition, and if I execute the "Change transition selection component" action with following options:
M/E: M/E 1
Component: Key 1
State: On
that it would set Key 1 as "On" for the next transition, but much like OP's initial description, the state of the next transition doesn't change at all for me. I'm also unsure what OP is referring to with the "interaction between the "Change transition selection" and the "Change transition selection component" feature."
Companion 2.1.2 build f4bcaf3-2679
ATEM Mini Pro firmware 8.6 build 2562fc70

that it would set Key 1 as "On" for the next transition,

@cybershoe yes, that is how it is supposed to work and is whenever I test it
The difference between the two is this:

"Change transition selection component" - changes one of the background/key1/key2
"Change transition selection" - changes the whole selection to whatever is specified

I noticed that I mistyped my scenario... the state isn't "On", the state is "On Air". That implies that the selection will result in the key becoming "On Air" as part of the next transition (i.e. if key 1 is on air, then key 1 next transition is disabled, else key 1 transition is enabled).
Either this is a terminology problem (in which case I'd suggest "On Air" be changed to just "On", since it doesn't seem to affect "On Air" status, just whether the selection is "On"), or even better, change it to be "Selected" and "Not selected".
We're getting into feature request territory here, but ideally I'd like to see 5 options:

Selected: The component is selected for the next transition, no matter what
Not selected: The component is not selected for the next transition, unless it's the only currently selected component, in which case no action is taken
Toggle: What it currently does, toggle the selection state for the component
On Air: (only available for key components) If the component is currently on air, the component is not selected for the next transition (component remains on air), otherwise it is selected (component goes on air)
Off Air: (only available for key components) If the component is currently not on air, the component is not selected for the next transition (component remains off air), otherwise it is not selected (component goes off air).

Admittedly I see this getting pretty hairy, and I expect that it's just a mislabelling of what's supposed to be the "On" option. Getting #1052 in companion core implemented would get away from that though and let us define this behaviour through conditions.


"ERROR: conflicting dependencies, requested rsa==4.7, google-auth 1.11.0 depends on rsa<4.1 and >=3.1.4"

Hi there 👋
Firstly, thanks for making this project, and making it open source! I hope my reporting an issue is helpful.
I received this error when building the docker image:
INFO: pip is looking at multiple versions of cachetools to determine which version is compatible with other requirements. This could take a while.
ERROR: Cannot install -r requirements.txt (line 6) and rsa==4.7 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested rsa==4.7
    google-auth 1.11.0 depends on rsa<4.1 and >=3.1.4

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies
The command '/bin/sh -c pip install --no-cache-dir -r requirements.txt' returned a non-zero code: 1
ERROR: Service 'google-ddns' failed to build : Build failed

G'day,
You're welcome, and thanks for pointing out the issue. This is a good reminder to test my repo after a Github security pull request.
First, I have updated my requirements.txt file after a complete reinstall of all packages using pip. I tested locally and all went well.
I don't use the docker functionality myself, but I did have a play with it just now and it runs fine on my local machine. I modified the Dockerfile to include the config.yaml and ddns-api-key.json files to the Dockerfile's COPY command, but remember that you'll have to provide them. I give an example of them on the project's homepage.
With a correct config file and a valid credentials file the docker image ran well and updated my Google DNS A record.
I'm not much a Docker wizard, so please forgive me if I'm stating the obvious, but I successfully ran the image using the following commands:
docker build -t dns .
docker run dns
For the sake of science, I made a docker-compose.yml file
version: '3'

services:
  ddns:
    image: dns
    volumes:
    - ./config:/ddns

and ran with docker compose up.
Please let me know how you get along, and thank you for taking the time to report the issue.
Cheers,
Conor

Thanks! The changes look good except for one thing. I get an error when I build:
  => ERROR [3/4] COPY LICENSE gcp_ddns.py requirements.txt config.yaml ddns-api-key.json ./                                                            0.0s

You definitely don't want to embed a secret API key in the Docker image. I don't think it makes sense to have the example config in the Docker image either.
I prefer using docker-compose to build the image, so I'm using this docker-compose file:
version: "3.9"

services:
  google-ddns:
    build:
      context: "."
    container_name: "google-ddns"
    image: "docker.io/conorcunningham/google-ddns"
    volumes:
        - "./ddns-config.yaml:/ddns/config.yaml"
        - "./.secret.dns-api-key.json:/ddns/ddns-api-key.json"

P.S. a minor point but there's a spelling mistake in the repo's tags :) https://github.com/topics/python-dynmaic-dns


Misaligned popper position

CodeSandbox demo
https://codesandbox.io/s/magical-kowalevski-4b9nw?file=/src/Popover.js
Steps to reproduce the problem
Check the provided codesandbox and play around with window width as this bug is not always visible
What is the expected behavior?
I'd expect the right border of both the reference element and popper element to be perflectly aligned.
What went wrong?
There is a slight 1px misalignment.

Any other comments?
I noticed that this bug occurs when both the x position and width of the reference element are decimals.
It looks like Popper incorrectly calculates the position of the element.
I've added logger modifier so that you can check console in the codesandbox to see and compare the resulting value provided by Popperjs and the one provided by me (which seems to be correct).
I also played around with roundOffsets, gpuAcceleration and nothing seems to fix this issue.
I'd consider this issue a high priority as it basically defeats the purpose of using this otherwise very useful library.
I'm happy to help with fixing this issue if someone would provide me with some guidance :)

Have you tried to disable the roundOffsets option?
https://popper.js.org/docs/v2/modifiers/compute-styles/#options

Have you tried to disable the roundOffsets option?
https://popper.js.org/docs/v2/modifiers/compute-styles/#options

@FezVrasta It's already disabled in the provided sandbox :)

@FezVrasta It's already disabled in the provided sandbox :)

You can now tweak the roundoffsets option to address these edge cases.

Hey @FezVrasta thanks for the reply, but I'm afraid that possibility to tweak the roundOffsets does not really help in this case as the x value passed to that roundOffset function is still incorrect.

Oh I see, you are right.
It seems to fix itself if you resize vertically, so it's more some timing issue than a wrong computation of the offsets.

Oh wait, sorry, I didn't read your code. You are using useLayoutEffect to generate a new popper each time, so the issue must be in the moment React calls your code. This is not really something Popper can address, you should make React play nicely with it tweaking your code.
Sorry for the churn. Closing.

@FezVrasta the issue is the popper's rect (width/height) is done with layout, while the reference is done with getBoundingClientRect(). In the CodeSandbox you can see the layout is 110 but the client one is 109.5xxx, which looks to be causing the issue.  We use layout because of issues with transforms IIRC.

@atomiks Popper properly computes it if you vertically resize the window when the issue is present, so I'm positive is not a positioning bug.

@FezVrasta Changing the useLayoutEffect to useEffect does not change anything (apart from adding another issue of flash of unpositioned element ;) )

Ok nevermind, looked again, Popper bug, lol

I think we can use the client rect if it's within 0.5px of the layout one, otherwise, we don't use it (due the transforms issue).

@FezVrasta @atomiks sorry for the late reply, but unfortunately it looks like your PR does not 100% fix the issue. Take a look at the videos:
https://user-images.githubusercontent.com/20651022/109499396-238b9c80-7a95-11eb-8766-e5636c11f648.mov
https://user-images.githubusercontent.com/20651022/109499401-25556000-7a95-11eb-9e57-799722e5af05.mov
As you can see the right side border of the popper element is changing position while I'm scrolling, it occurs both in the provided codesandbox (although same as previously you have to play with screen width, as it does not occur all the time) and other project where I'm using popper.


Fix Fix partition name NPE and sample for all table during auto analyze.

Fix partition name NPE and sample for all table during auto analyze.
Sample for all tables because getData may have latency, which may cause full analyze a huge table and use too much resource. Sample for all tables to avoid this. Will improve the strategy later.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


sectionInset causes week view cell misalignment

IMPORTANT - BEFORE CREATING YOUR ISSUE PLEASE READ THE FOLLOWING:

PLEASE STATE THE VERSION NUMBER you are using.
7.1.7
Are you using the latest version of JTAppleCalendar? Latest version is currently 7.1.6
Yes
PROVIDE ENOUGH INPORMATION SO I CAN RECREATE THE PROBLEM.

I am trying to switch from monthly view to week view. However, this causes all the dates in weekly view mis-aligned with headers if there are sectionInsets.
The configuratinParameters I am using are as follows:
        switch (mode) {
        case .daily:
            return ConfigurationParameters(startDate: startDate,
                                           endDate: endDate,
                                           numberOfRows: 6,
                                           generateInDates: .forAllMonths,
                                           generateOutDates: .tillEndOfGrid,
                                           firstDayOfWeek: .sunday,
                                           hasStrictBoundaries: true)
        case .weekly:
            return ConfigurationParameters(startDate: startDate,
                                           endDate: endDate,
                                           numberOfRows: 1,
                                           generateInDates: .forFirstMonthOnly,
                                           generateOutDates: .off,
                                           firstDayOfWeek: .sunday,
                                           hasStrictBoundaries: false)
        }

The calendar was set up using:
    func setupCalendarView() {
        calendarView.minimumLineSpacing = 0
        calendarView.minimumInteritemSpacing = 0
        calendarView.sectionInset = UIEdgeInsets(top: 0, left: 10, bottom: 5, right: 10)
        calendarView.visibleDates { (visibleDates) in
            self.setupDatesOfCalendar(from: visibleDates)
        }
    }

I am also reloading the calendar each time after the switch as required:
func switchToStatsView(mode: statsViewMode) {
        switch (mode) {
        case .daily:
            statsViewCurrentMode = .daily
            calendarViewHeightConstraint.constant = 260
            self.view.layoutIfNeeded()
            calendarView.reloadData()
            setupDefaultSelectDates(mode: .daily)
            break;
        case .weekly:
            calendarViewHeightConstraint.constant = 47.5
            statsViewCurrentMode = .weekly
            self.view.layoutIfNeeded()
            calendarView.reloadData()
            setupDefaultSelectDates(mode: .weekly)
            break;

Here are screenshots of calendar in month view and in weekly view:

If I comment out sectionInsets, dates in weekly view is aligned perfectly

Please let me if I am doing anything wrong. Thank you very much!

Does master branch also have this issue?
Master branch contains a number of fixes for section inset.
You can test it by following this -> https://github.com/patchthecode/JTAppleCalendar/wiki/Common-Questions

Thank you for your quick response.
Sadly no, the issue still persists after I updated pod, cleaned and rebuild my project.

ok, its hard to determine what the issue is without a sample app replicating the issue.
Its difficult because these types of errors are visual. Therefore a sample app with the issue would be helpful.

I think I am experiencing the same issue as #1032

i just made a push to master branch

let me know if issue is resolved.

Thanks, it's resolved after updating to the most recent pod:)

@ImEric
OK, i am still making fixes to it, and i am still testing it.
It should be more well tested by the weekend.
But you can use it for now.
Any new issues found then let me know.


Fix issue #1802

Fix the error described on issue #1802.

@Eonasdan This fix is in master and development branch for quite some time, but somehow not in the latest release.
https://github.com/Eonasdan/bootstrap-datetimepicker/blob/4.17.44/src/js/bootstrap-datetimepicker.js#L950
Would be great to have this in the released version. A lot of people seem to have problems with this. (#1960, #1894, #1914, #1897, #1865, ...)

Need this in the release version, i don't want to go live with a temporary fix.

pushed 4.17.45

Looks like this fix isn't in 4.17.45 or master.
https://github.com/Eonasdan/bootstrap-datetimepicker/blob/v4.17.45/src/js/bootstrap-datetimepicker.js#L950
https://github.com/Eonasdan/bootstrap-datetimepicker/blob/master/src/js/bootstrap-datetimepicker.js#L950
Should this line be erased or changed like
https://github.com/Eonasdan/bootstrap-datetimepicker/pull/1854 ?

@Eonasdan Somehow the fix always refuses to get into the released versions. Can you have a look at this again?
Thanks


@craigspaeth => Article caching and Magazine router cleanup

A couple places we weren't using server-side caching (i'll keep an eye out for stale content complaints from editorial)
Remove extra Section fetch on /articles (and remove the "featured section" html+css altogether)

Solid! Looking forward to hearing the perf. wins vs. maintenance overhead this incurs.


Log changes to fix uwanted log message when auth provider configured is

Log changes to fix uwanted log message when auth provider configured is not supported by rancher-auth-service
https://github.com/rancher/rancher/issues/6899

@alena1108 can you provide a review

LGTM


heibox.uni-heidelberg.de

Hi Joshua, may I ask what the last.ckpt is intended for? There are also some other files downloaded from this server.
THanks

That is used for LDSR. These downloads are handled by the webui.sh script, and soon will be ahdnled automatically by the fork itself.


Pantheon updates 2021-12-13

Motivation for this change
Part of Pantheon 6.1 Jólnir updates (previous one at #150233).
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

The following content is machine generated and may contain invalid information.

pantheon.elementary-wallpapers: 6.0.0 -> 6.1.0

Release on GitHub
Compare changes on GitHub

Comment
To inspect upstream changes

[ ] Ashim DSilva: Fix permissions
[ ] AppData: Use implicit none in OARS (#161)
[ ] Create CONTRIBUTING.md (#163)
[ ] Change default to Odin Dark (#164)
[ ] Release 6.1.0 (#166)

pantheon.elementary-screenshot: 6.0.1 -> 6.0.2

Release on GitHub
Compare changes on GitHub

Comment
To inspect upstream changes

[ ] Flatpak: Remove accountsservice hole (#229)
[ ] Update Flatpak runtime to 6.1 (#232)
[ ] Release 6.0.2 (#233)

pantheon.elementary-calculator: 1.7.1 -> 1.7.2

Release on GitHub
Compare changes on GitHub

Comment
To inspect upstream changes

[ ] Flatpak: Remove accountsservice hole (#212)
[ ] Meson: remove positional arguments from i18n.merge_file (#214)
[ ] Update to elementary 6.1 runtime (#215)
[ ] Release 1.7.2 (#216)

pantheon.elementary-camera: 6.0.2 -> 6.0.3

Release on GitHub
Compare changes on GitHub

Comment
To inspect upstream changes

[ ] README: correct deps (#197)
[ ] Update elementary runtime to 6.1 (#201)
[ ] Release 6.0.3 (#202)

pantheon.switchboard-plug-onlineaccounts: 6.2.2 -> 6.3.0

Release on GitHub
Compare changes on GitHub

Comment
To inspect upstream changes

[ ] New feature: Editing a CalDAV account (#216)
[ ] Release 6.3.0 (#236)

pantheon.elementary-tasks: 6.0.4 -> 6.1.0

Release on GitHub
Compare changes on GitHub

Comment
To inspect upstream changes

[ ] Self contained scheduled list (#292)
[ ] Update io.elementary.tasks.yml (#310)
[ ] Free libical cache before exiting the application (#311)
[ ] Granite.HyperTextView: Support for clickable hyperlinks in task description (#314)
[ ] Update tasks.appdata.xml.in
[ ] Drag Task to another List (#296)
[ ] Use floating timezones when saving timed tasks (#313)
[ ] Update tasks.appdata.xml.in
[ ] Release 6.1.0 (#316)

pantheon.elementary-mail: 6.3.0 -> 6.3.1

Release on GitHub
Compare changes on GitHub

Comment
To inspect upstream changes

[ ] Flatpak: Remove accountsservice hole (#731)
[ ] avoid assertion error in add_internal_resourcewhencontent_id is… (#736)
[ ] Update io.elementary.mail.appdata.xml.in
[ ] Release 6.3.1 (#740)

pantheon.elementary-terminal: 6.0.0 -> 6.0.1

Release on GitHub
Compare changes on GitHub

Comment
To inspect upstream changes

[ ] l10n: Correctly setup the locales (#611)
[ ] Use locale independent conversion for zoom (#615)
[ ] MainWindow: Use the XTerm title if defined (#602)
[ ] Update io.elementary.terminal.appdata.xml.in
[ ] Update io.elementary.terminal.appdata.xml.in
[ ] Avoid F5 shortcut clash with some foreground processes (#623)
[ ] Release 6.0.1 (#642)

@ofborg test pantheon

Result of nixpkgs-review pr 150627 run on x86_64-linux 1

1 package marked as broken and skipped:

pantheon.elementary-screenshot-tool

33 packages built:

monitor
pantheon-tweaks
pantheon.elementary-calculator
pantheon.elementary-camera
pantheon.elementary-greeter
pantheon.elementary-gsettings-schemas
pantheon.elementary-mail
pantheon.elementary-screenshot
pantheon.elementary-session-settings
pantheon.elementary-tasks
pantheon.elementary-terminal
pantheon.elementary-wallpapers
pantheon.gala
pantheon.switchboard-plug-a11y
pantheon.switchboard-plug-mouse-touchpad
pantheon.switchboard-plug-onlineaccounts
pantheon.switchboard-plug-pantheon-shell
pantheon.switchboard-plug-power
pantheon.switchboard-plug-security-privacy
pantheon.switchboard-with-plugs
pantheon.wingpanel
pantheon.wingpanel-applications-menu
pantheon.wingpanel-indicator-a11y
pantheon.wingpanel-indicator-bluetooth
pantheon.wingpanel-indicator-datetime
pantheon.wingpanel-indicator-keyboard
pantheon.wingpanel-indicator-network
pantheon.wingpanel-indicator-nightlight
pantheon.wingpanel-indicator-notifications
pantheon.wingpanel-indicator-power
pantheon.wingpanel-indicator-session
pantheon.wingpanel-indicator-sound
pantheon.wingpanel-with-indicators


Dynamic payload lengths

Some protocolls do not specify the length of their payload explicitly but just keep it as "the rest of the packet". This is the case for example for Ethernet and ICMP. In this case Payload'Length = Message'Last - Previous_Field'Last usually applies.
The problem is that we detect accessible fields by the evaluability of the length property but in this case the length property cannot be evaluated as it basically depends on itself.
So we have to detect if a field depends on itself and then make it accessible. When it is set we have to check if the value resolves this dependency.

Fixed by #167.


EventGrid subscription filtering on arrays

Query/Question
Hi Team,
I have question regarding Event Grid Subscription filtering via Azure Portal/Rest api. This may not be the right place for asking that, but I could not find a proper repository for that. My question is, whether it will be possible to filter array fields in the event. Do you have any timeline for that or maybe is it on your roadmap? The documentation clearly states that it is not possible today but maybe it will be available in the future (https://docs.microsoft.com/en-us/azure/event-grid/edge/advanced-filtering#filtering-on-array-values)

. I'm attaching a screenshot from the docs. Thanks in advance.
Best regards

Hi @garoplin.  Thank you for reaching out and we regret that you're experiencing difficulties.  Unfortunately, this repository is focused on the Azure SDK for .NET - we're unable to assist with other Azure issues.  Since what you're describing appears to be related to the portal and not one of its SDKs, your best path forward would be to open an Azure support request.
I'm going to close this out;  if I've misunderstood what you're describing, please let us know in a comment and we'd be happy to assist as we're able.


[Relay][Frontend] Support tf.where

@srkreddy1238 @kazum @wweic @zhiics pls take a look

@srkreddy1238 incorporated comments. Pls take another look.

Thanks @zhiics @yongwww @jroesch . This is now merged.


[CSL-446] Test master with rocks-db compiled and packed under Windows

@georgeee

Make it compile
Pack with our ready-to-go installer
Check it actually works

master branch is eventually unstable, please consult @gromak for which branch to use

@georgeee
Not relevant due to time passed


some error in python3.6   system ubuntu16.04LTS

Traceback (most recent call last):
File "study.py", line 131, in
save_record(section, True)
File "study.py", line 105, in save_record
if f'L{dic["id"]}' in studied and studied[f'L{dic["id"]}']['watchState'] == 1:
TypeError: argument of type 'NoneType' is not iterable

Please try the latest version.

File ".\study.py", line 131, in
save_record(section, True)
File ".\study.py", line 112, in save_record
'recruitId': recruit_id, 'chapterId': dic['chapterId'], 'sourseType': 3, 'playTimes': video_time,
KeyError: 'chapterId'

every nice thanks


Request: Per-domain configuration options

I read through the docs and searched but didn't see a way to configure youtube-dl on a per-domain basis. This would be very useful as there are various domains I use different settings with, and having to change the settings for each is time consuming.
Being able to specify different youtube-dl settings per domain (such as Youtube, Comedy Central, Vimeo) in the config file would be a great addition to the functionality.

Duplicate of #3101

@jaimeMF Ah, searched but didn't find anything. Definitely has my support.


Fix bug with name of sleep function

Change name of sleep function with compiler type checking.

Thanks, please fix the lint error, and it will be merged

What kind of error do you mean? Because my cppcheck shows me that everything is Ok with this file.

https://travis-ci.org/dmlc/rabit/jobs/91655536

I fixed this bug.

Thanks this is merged


⚠ Samsung has degraded performance

In 8c1b64c, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2626 ms

Resolved: Samsung performance has improved in 6e1b11d.


Should the Thermostat endpoint have a Fan Control cluster? (CON-811)

Per Matter Device Library Specification R1.1, a Thermostat endpoint shall include a Fan Control cluster. However, in esp_matter_endpoint.cpp, I only see a thermostat cluster in the thermostat endpoint, and no fan control cluster. Is this something I should add myself, or am I misinterpreting the specification?

@adailydose Fan control cluster is provisional and optional. You have to add it yourself, if you needed.


Bump to<EMAIL_ADDRESS>

Fixes #2560. Fixes #2597.

Changelog Entry
Fixed

Fixes #2560. Bumped to<EMAIL_ADDRESS>to workaround a bug from Angular/zone.js, by @compulim in PR #2960

Changed

component: Bumps<EMAIL_ADDRESS>by @compulim in PR #2960

Description
Bump to<EMAIL_ADDRESS>diff here.
It picked up a change to workaround a long-time Angular bug.
Specific Changes

Bump to<EMAIL_ADDRESS>

[x] ~Testing Added~

Manual testing done, we don't test Angular in an automated way

What is the change on react-dictate-button?

Click the "diff here" link above.


Resolution and selected ROI different from snapshot

IDE 2.6.9 / Windows 10
If the buffer has an image of W229 x H152 sensor.set_windowing((196 , 82 , 229 , 152)):
Res displayed is 228x152
ROI selectable is 229x153

Noted. I'll see if I can fix the selectable window being 1-pixel too large.

Plus, none of the three rectangles have the same dimension:
sensor.set_windowing : 229x152
Res: 228x152
ROI selectable: 229x153

Set windowing doesn't accept odd resolutions. So, it just removes 1 pixel. The ROI selectable in the IDE is just larger than should be allowed.

This is fixed in the latest firmware. Things are no longer rounded down.

I'm not sure if is related as my bug is for IDE, but until the update I had som calculated ROI that may have been odd. Then sometimes I called sensor.set_windowing(roi) with some odd numbers.
I can't do that anymore with MT9V034 but only for the width. Else I have "ValueError: Sensor control failed!". You may update the documentation on the set_windowing function, I didn't find anything about it.

Hi, I’m the latest firmware the function is now extremely forgiving and does exactly what you want. It shouldn’t throw any errors even if you ask if to give you pixels out of bounds. It will just crop the rect.


how to use database transaction in FastAPI

###how to use database transaction in FastAPI

[ ] Thanks FastAPI
[ ] As we all know the database transaction has specition function, but when I want to use it in my fullstack,  cannot find an example to study .
can anyone show a example or a link here?
thanks.

I made boilerplate that has sqlalchemy transaction feature
https://github.com/teamhide/fastapi-boilerplate

thanks  a  lot

I'm looking for it in tortoise-orm


fix(curriculum):unnecessary blank line in pyramid generator project

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #56143

why did you close the other PR please? it makes a lot of unnecessary noise to close a PR to open it again, it's not something you should do.

why did you close the other PR please? it makes a lot of unnecessary noise to close a PR to open it again, it's not something you should do.

It had some problem with the task

Yes, so you add commits to the branch that solve the problem, you don't close teh PR

Yes, so you add commits to the branch that solve the problem, you don't close teh PR

got it

@ilenia-magoni Is this PR still relevant for review?

probably not, there is #56523 which does the same changes and was opened earlier


Guide: Migrate "Enabling SSL/TLS on your Kitura server"

We have an existing guide for how to enable HTTPS on a kitura server here. This is pretty useful guide and should be migrated over to the new guides (Possibly into a new utilities section)

@Andrew-Lees11 Where are you planning to add this guide?
We currently do not have a 'utilities' section, nor can we easily add one at the moment.
I have plans to add a new section for guides/information that won't fit into the current flow but we don't have it yet.
For now I'd recommend not adding this guide, it's still available to users via the old docs page if they require it. But leave this issue open so we know to migrate it in the future.

I think this would fit pretty naturally as part of the Deployment section.

I agree this could go in deployment. I think it is quite an important guide and would like to migrate it over so I am working on that at the moment (Since the base guide exists in the old docs). If any section gets to large we could look at creating a new one.

Yeah we can add it to deployment for now then, once we have the scope for adding a new section we can move it to there.
The only section at risk of being to large is Getting Started and in the original layout, Getting Satrted had a configuration section which probably could have included this.

I think Deployment should be the long-term home. It's the natural place people will look for info about TLS.

@ianpartridge natural place based on what?
TLS/SSL information typically falls under Security, Settings or Configuration. You could argue that only users wanting to deploy may wish to use TLS/SSL, unless for example; they are simply playing around with/learning Kitura or creating a Web Application they don't want to deploy. In which case Deployment wouldn't be the place I'd look for information about Security.
Either way, for now we can place it under Deployment and we can decide what to do with it later.

Deciding whether to use TLS is a deployment decision.

I feel it's a security decision and I think we should adhere to what users would expect.
Apple keeps their docs around SSL under Security, as do many other frameworks.
We should also follow this trend going forward so there's no confusion on where to find this information.

Apple keeps their docs around SSL under Security, as do many other frameworks.

Can you provide links please?

Apple - https://developer.apple.com/documentation/security/secure_transport)
Django - https://docs.djangoproject.com/en/2.2/topics/security/#ssl-https)
Express - https://expressjs.com/en/advanced/best-practice-security.html#use-tls)
Rails - https://guides.rubyonrails.org/security.html & https://guides.rubyonrails.org/configuring.html
There's a few links, I did do research before starting to design the new website layout and by extension the new side list for the docs.

Thanks for the links!
I think the difference here is that none of those links are guides on how to enable TLS in those frameworks.  As we have designed the Learn section as an end to end flow the question we need to ask ourselves is "when in the process of following these guides would the user consider whether they require TLS?"  And the answer is deployment. Why? Because that's when the user is deciding whether to use Cloud Foundry / k8s etc. And if they're using k8s they probably don't want TLS on their Kitura app because the TLS will likely be terminated at Ingress. If they're using CF they have similar considerations to make.
Now, there is definitely value in "security best practices" document like Express have, but I don't currently see how that would form part of the flow we've designed at the moment.  It would have to stand alone somehow, like the "Kitura architecture best practices" doc we've discussed previously.
Hope that makes my thinking clearer.

Thanks for adding some clarity :)
I think whether they instruct a user how to enable TLS on those frameworks or not is irrelavant, it's where you'd look to find out about the TLS options available. In some of the cases in the links, they recommend using an external tool whereas we provide that option for you. The example we currently use in our TLS guides has nothing to do with Deploying to K8s or CF, it's simply a Hello World example that you can view via https.
Now I definitely agree with thinking about what the user would want as that is what is most important. The guides are an end-to-end flow but they also need to cater for users to enter the docs at any point and work through a section they need. Not everyone will want to follow the docs end-to-end so we should ensure that information is available in a logical place.
The new layout I'm working on does have a section for Security, as Security is such an important concept which alot of people care about and as such probably should be it's own section.
I don't seem to recall the discussion about Kitura architecture best practices but I also agree we should have something like that.
As for the current flow, it's a little more coupled than I originally planned for it be. They should flow in a way that also allows them to also stand alone, which they currently do not but I've been talking to Helen about ways to resolve that.

What else are you imagining will go in the Security section?

I haven't got a plan for that yet.
I first need to research what is typically found in Security, and what users typically would want to know about security when developing a Kitura Server.
With the former I can draw up a proposal, but the latter will come from asking our users.

OK thanks. @Andrew-Lees11 - for now TLS can go in Deployment.  In future we can rethink once @ddunn2 has a proposal for a Security section.  Thanks!


Update Composer dependencies (2023-05-12-00-09)

Visual regression test passed!
View the visual regression test report


Converts to Maui for non-Maui projects

Discussed in https://github.com/dotnet/upgrade-assistant/discussions/1150

Originally posted by ERobishaw June  2, 2022
If you find the upgrade assistant is trying to make all your projects into Maui projects, even if they have no xamarin code -- it's because you have multi-targeted frameworks...
In your csproj files, change:
<TargetFrameworks>net48</TargetFrameworks>
to
<TargetFramework>net48</TargetFramework>
And it will no longer do this...
I didn't dive into the code enough to determine the thinking behind this...  but the analysis believes you have a Maui project if it sees any code related to Xamarin.Forms, OR the PLURAL version of "TargetFrameworks" targeting.

This is because of the following line:
https://github.com/dotnet/upgrade-assistant/blob/6233e2bba56cc29956a93764b33b4475fcd55914/src/extensions/maui/Microsoft.DotNet.UpgradeAssistant.Extensions.Maui/MauiComponentIdentifier.cs#L16
We should not be using TargetFrameworks as the flag to convert to Maui - many projects will have this flag. Currently, this stops any conversion.


Package Calico as a Helm chart

See https://github.com/kubernetes/helm/blob/master/docs/charts.md

Last I checked there was a dependency on networking in order to use helm - the tiller Pod needed networking installed in order to work, which meant installing networking wasn't possible through Helm.
This was many months ago, so may have changed since!

Helm now allows running the tiller Pod using host networking, but we're still currently blocked on this: https://github.com/kubernetes/kubernetes/issues/45717

Here is aws helm chart for calico in case anyone is looking for it. Still needs some values restructuring, but its a first stab at it.
https://github.com/mrzobot/calico-helm-chart

I'll test this and get back to you .  Thanks @mhobotpplnet  .

@caseydavenport do you have a preference for where this lives ?

where should it live?

I'm assuming, stable/ upstream,
projectcalico/helm-chart
something else?

where should we test it?

assuming we have a ci pipeline somewhere.
if someone could introduce me to who runs it, and  how i could add jobs to it, that would be cool.

Is there any update of this issue?
After helm 3 was released, the tiller pod was removed, so it probably will be more straight forward to deploy calico by helm chars.

Currently, the core Calico team is not really able to be in the business of maintaining a Calico helm chart. There are a lot of different ways to configure and package Kubernetes applications and we can't maintain and test all of those ourselves, so we need to rely on others to do that packaging.
I think there are some third-party helm charts out there in the wild, though.

@caseydavenport, understood: a supported Helm chart cannot be maintained without great expense and will only work for specific conditions.  A link to a minimal chart used for system testing is useful: there is one in the code and an "in the wild" link already provided in this issue.  It should suffice for further development.

Will this be it? https://github.com/projectcalico/calico/tree/master/_includes/charts/calico

@rochaporto we use helm templating to help render our current manifests in docs.projectcalico.org, which is what you have found, but I want to point out that it's not a supported API / install mechanism. We don't consider the logic in those manifests to be suitable for general use and we don't test all of the permutations.

Seems quite useful though. What would it take for it to become supported?

Thanks @invidian . To help others, here are the steps:
helm repo add flexkube https://flexkube.github.io/charts
helm upgrade --install --namespace kube-system calico flexkube/calico

OR, if you want automatic detection of cidr:
helm upgrade --install --namespace kube-system calico flexkube/calico --set podCIDR=$(grep cluster-cidr /etc/kubernetes/manifests/kube-controller-manager.yaml | cut -d"=" -f2)

chart/calico default cidr is "<IP_ADDRESS>/16"
podCIDR="<IP_ADDRESS>/16" # if you had flannel before and your cluster uses this range
@caseydavenport @rochaporto
Is there a helm repository already holding that "might be official" chart? Also I noticed there is no values.yaml.

Seems quite useful though. What would it take for it to become supported?

We'd need to do a review of the options available in the chart and build a values.yaml "API" that we think is supportable.
IMO we should instead be pushing for integrating the Calico Operator into a helm chart. It can do more nuanced and useful lifecycle management than a pure helm chart can, and already has a well-defined API with validation, etc.

That operator requires scary amount of permissions:
https://github.com/tigera/operator/blob/master/deploy/role.yaml
Basically its not far out from cluster-admin, and a black box with cluster-admin permissions.
Operators work really well when you have something to manage it, like the olm. But the olm depends on having a working sdn layer, so doesn't help here.
What I like about the helm chart in this repo, is its still configurable, its auditable by the end sysadmin, and it doesn't have a bad dependency stack during bootstraping. core k8s, helm install, working cluster. How does the operator get updates? If you have to helm upgrade the operator, its still as much work to install the updated operator as it is to install an upgraded calico itself?
I trust that the olm can deploy operators in a namespace that can't escape the namespace. As I've looked through the code. I'm much more worried about non olm managed operators that can escape a namespace and/or have a lot of permissions.
I'm not sure its worth the complexity tradeoffs of using an operator here instead of just using helm to deploy/manage the base sdn layer. Maybe an operator is appropriate for functionality on top, like webui's and stuff that can be more restricted / managed by the olm.
I could be totally off base here, and could be convinced otherwise. Just a gut feeling after using lots of these components over the years.

Yep, I appreciate where you're coming from. Let me add my thoughts and see if they make sense:

Yup. Thanks for the discussion. :)

Absolutely, we're working on improving that - the RBAC in that file there isn't representative of the true number of permissions the code needs. In other words - it's giving unnecessary permissions right now. We can even use Kubernetes RBAC to limit to specific resource names, which will really tightly scope the power of the operator.

👍

its auditable by the end sysadmin

I'm not sure I buy this. At the end of the day, the helm chart would be deploying some sophisticated software into the cluster that is not audit-able except by someone who has read the source code. Both Calico and Kubernetes itself are both made out of of a set of compiled controllers written in golang, just like an operator is.

Hmm... yes and no. I wasn't scoping all of Calico into my statement but I guess I did not state that. I was more referring to the packaging. If I can quickly audit the deployment scripts, I know roughly what box the software under deployment is restricted to. I can quickly look at the rendered templates and see what its going to do. With an operator, you can't see what it always will do, just what its done after the fact. So the best you can do is look at the operator's rbac rules and guess. That does relate to previous concern, which would be better when tightened. So will be less of a problem later.

it doesn't have a bad dependency stack during bootstraping. core k8s, helm install, working cluster.

I'm not sure I follow here - an operator based approach is the same set of dependencies. Core k8s, kubectl apply the operator+CR, working cluster. Am I missing something?

I guess I might have been mixing concerns a little bit here. If you were to deploy the operator using the OLM, I think you run into bad bootstrapping dependencies. If simply using helm to deploy the operator, its not a problem. Without something like the olm, I'm not sure how much helm installing the operator vs just helm installing calico directly buys you for the extra complexity.

How does the operator get updates?

As a basic level, it's as simple as bumping the image version, maybe make some manifest changes. I see helm as a lightweight way to manage upgrades of the operator itself, rather than using something like OLM (which could also be an option for those who want it, though as you said would need some special steps to work with a network operator)

Ok, yeah.
So once permissions are tightened up, I think the main trade off I see, is more obscurity on the deployment for sysadmins because its harder to see the manifests before the operator generates them vs the ability for the operator to do complex lifecycle operations on Calico to save the sysadmins work? So work for an sysadmin doing some verification vs work for a sysadmin doing more complicated upgrades.
I think the canal -> calico upgrade procedure was more complicated then just a helm upgrade, but was a one time thing and even with the few extra steps wasn't a huge deal.
Do you envision much need for more complicated upgrade procedures beyond what a simple helm upgrade could do?

Appreciate your feedback. I'll continue to chew on this a bit.

Yeah, me too. Thanks again for the discussion/thought.

Can we just get this packaged up as a helm chart? https://github.com/projectcalico/calico/tree/master/_includes/charts/calico

@cabrinha please see my earlier comments on this - that chart is for internal website rendering purposes only.

I want to point out that those helm "charts" are not a supported API / install mechanism. We don't consider the logic in those charts to be suitable for general use and we don't test all of the permutations.

So once permissions are tightened up, I think the main trade off I see, is more obscurity on the deployment for sysadmins because its harder to see the manifests before the operator generates them vs the ability for the operator to do complex lifecycle operations on Calico to save the sysadmins work?

@kfox1111 Yes, this is certainly part of the benefits it brings (handling complex lifecycle operations).  There are other, perhaps more subtle, benefits as well, that it brings to every release.

Reduces the potential for misconfigurations by putting an API with validation and defaulting on top.
Reconciles changes to ensure the cluster stays in its desired state and accidental changes are not made.
Provides a more scalable default configuration, including auto-scaling for components like Typha.
Provides a better default security posture by provisioning TLS certificates on connections that use them by default (e.g., calico/node to Typha).
Ensures that what you get is what is tested and supported. I've often seen clusters fail when a user decides to use the same manifests they have been using for Calico v3.6, but bump the image version to Calico v3.14 (as an example).
Consistent experience across all platforms (e.g., OpenShift, which doesn't allow installation of network plugins via helm).

Of course, some of these things are achievable via a helm chart. But also some of them are not.

Now that latest helm does not have tiller, does it work without CNI? If so, calico can have helm charts and can be installed by helm? Thoughts?

It works without cni.

Would love an official helm chart

Any reason there are no official helm charts to install calico or calico operator?
Docs say we need to create the manifests (calico.yaml or tigera-operator.yaml) using kubectl.
Looking at the manifests, it looks like:

calico.yaml manifest renders the calico helm charts at https://github.com/projectcalico/calico/tree/master/_includes/charts/calico but it doesn't have values.yaml

tigera-operator.yaml manifest renders the calico operator helm charts at https://github.com/projectcalico/calico/tree/master/_includes/charts/tigera-operator but it doesn't have values.yaml

Can these manifests be converted to values.yaml so calico or calico operator can be installed using helm instead of kubectl?

It works without cni.

Thanks. I made helm charts for calico by adding values.yaml for https://github.com/projectcalico/calico/tree/master/_includes/charts/calico and was able to install it using helm install.
So, yes, helm does work without CNI. I'm using helm v3.2.4:
$ helm version
version.BuildInfo{Version:"v3.2.4", GitCommit:"0ad800ef43d3b826f31a5ad8dfbb4fe05d143688", GitTreeState:"clean", GoVersion:"go1.13.12"}

How about getting this packaged up as a helm chart? https://docs.projectcalico.org/manifests/calico-vxlan.yaml

@invidian ->
as you already maintain the calico non-operator charts in your helm repo (https://github.com/projectcalico/calico/issues/717#issuecomment-622265192), can you add also the operator one (https://github.com/projectcalico/calico/tree/master/_includes/charts/tigera-operator ) along with a values.yaml ?

@ReSearchITEng I'm not actively using tigera-operator, so perhaps it would be better if someone else would maintain it.

Any updates? Is there any guide, how to install calico with helm chart?

This issue has been open since 2017. Can we get a helm chart made for calico please?

@caseydavenport so I made some changes to the helm chart and added values.yaml file and a README.md. It is after pushing it to my Github I realized values.yaml files are ignored for charts. Is there a reason why this can't be allowed? This along with the readme will help others to download and use this chart locally at least.  I can create a pull request if you are fine with the approach.
https://github.com/im-nonedone/calico/tree/nsadineni/added-values-readme/_includes/charts/calico

@caseydavenport so I made some changes to the helm chart and added values.yaml file and a README.md. It is after pushing it to my Github I realized values.yaml files are ignored for charts. Is there a reason why this can't be allowed? This along with the readme will help others to download and use this chart locally at least.  I can create a pull request if you are fine with the approach.
https://github.com/im-nonedone/calico/tree/nsadineni/added-values-readme/_includes/charts/calico

CC @ozdanborne and @lwr20 who are currently working on a helm3 chart, and know better than I.

CC @ozdanborne and @lwr20 who are currently working on a helm3 chart, and know better than I.

@ozdanborne  @lwr20 can you guys take a look at this and see if this can be packaged as a helm chart. I changed it to helm 3, added crds folder and added readme.
https://github.com/im-nonedone/calico/tree/nsadineni/added-values-readme/_includes/charts/calico

@ozdanborne  @lwr20 can you guys take a look at this and see if this can be packaged as a helm chart. I changed it to helm 3, added crds folder and added readme.
https://github.com/im-nonedone/calico/tree/nsadineni/added-values-readme/_includes/charts/calico

For the benefit of those watching along, the helm3 charts work has progressed to the point that you can build helm3 charts from this repo:
git checkout origin/master
make charts

and the charts tgz will be built and can be found in /bin/
This works for master and release-v3.17 branches at present.
Work is still ongoing on adding automated testing for the resulting helm bundle and on the machinery to actually add a helm charts bundle as a release artifact.

For the benefit of those watching along, the helm3 charts work has progressed to the point that you can build helm3 charts from this repo:
git checkout origin/master
make charts

and the charts tgz will be built and can be found in /bin/
This works for master and release-v3.17 branches at present.
Work is still ongoing on adding automated testing for the resulting helm bundle and on the machinery to actually add a helm charts bundle as a release artifact.

It would be great if the chart could get added to https://chartcenter.io/ -- makes it really easy to consume your chart without maintaining your own helm repo.

It would be great if the chart could get added to https://chartcenter.io/ -- makes it really easy to consume your chart without maintaining your own helm repo.

Helm chart bundles are now being added to the release artifacts.  e.g.
in https://github.com/projectcalico/calico/releases/tag/v3.18.1 the helm chart is tigera-operator-v3.18.1-1.tgz

How do i need to configure helm to fetch those bundles? Normally you you need a helm repo.
Is it planned to publish them as helm repo or do we need to create our own repo for it? 😕

There's no need for a helm repo:
https://docs.projectcalico.org/master/getting-started/kubernetes/helm
But I can see that it would make finding the chart easier.  I'll raise an issue to track that.

Raised https://github.com/projectcalico/calico/issues/4514
Please add comments to that to explain why this would be a good thing to have so that this work can be prioritised appropriately.

@lwr20 If I understood correctly currently there is only helm chart fo tigera operator. But what about calico?
Do you consider to release this chart as well?

If I understood correctly currently there is only helm chart for tigera operator. But what about calico?

tigera-operator installs Calico.  (It can also be used to install Calico Enterprise, but that's not relevant here).


Support new POSIX 2024 non-greedy repetition operators ?? *? and +?.

Reference: https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/V1_chap09.html section 6.4.6:
"Each of the duplication symbols ('+', '*', '?', and intervals) can be suffixed by the repetition modifier '?' (), in which case matching behavior for that repetition shall be changed from the leftmost longest possible match to the leftmost shortest possible match, including the null match."


Updated to work on modern svelte docs.

Updated everything to work on the modern version of the svelte docs. Please find the generated docset attached.
Major changes:

Removed left column because IMO it doesn't add much given that we already have the TOC right there
Removed permalink text from every key - I guess they changed smth that caused that to appear

Known issues:

Examples don't appear in main page TOC, making them hard to discover a little bit (I think this was an issue before - don't reallyyyy care about fixing it too much)

svelte.docset.zip

@Cobular Awesome!!  Thanks for submitting this.  I'll review ASAP.

Update - Made it generate a new docset for Sveltekit as well!


iotagent-mosca is not starting right

It seems the iotagent-mosca is starting before the auth service being operational. See the logs bellow:
<17:23:41 13/09/2018> -- || -- ERROR: Could not get list of current tenants.
<17:23:41 13/09/2018> -- || -- ERROR: Error is: Error: getaddrinfo ENOTFOUND auth auth:5000
The problem is that it keeps running in a non-operational way, ie, no data is sent to kafka and no errors are logged.

<16:57:52 20/09/2018> -- || -- DEBUG: Trying to publish someting. Current producer topics are {}
<16:57:52 20/09/2018> -- || -- WARN: No producer was created for subject device-data. Maybe it was not registered?


Scroll does not stick to bottom when loading images

Overall the MessageList component works pretty great. When set autoScrollToBottomOnMount, the list starts at the bottom but when the images load from a URL it keeps the scroll position (at least when using custom Message component). Any solution/workaround for this?

Hi @p-Jimenez, thanks for the question.
This is because <MessageList /> doesn't know something inside has changed.
I think it can be solved in two ways:

Set explicit height of the image
or:
Call the scrollToBottom() method of the <MessageList /> component in the onload event of the image

How to use  scrollToBottom: https://chatscope.io/storybook/react/?path=/docs/components-messagelist--scroll-to-bottom


PostgreSQL Database creation error.

Describe the bug
When creating tenant whit postgresql database driver im getting syntax error at or near "-" error.
When i update PostgreSQLDatabaseManager.php with below my problem fixed;
public function createDatabase(string $name): bool
{
    return DB::statement("CREATE DATABASE \"$name\" WITH TEMPLATE=template0");
}

Steps to reproduce
tenant()->create('tenant-2.myapp.localhost')

Expected behavior
Creating new tenant
Your setup

Laravel version 6.0
stancl/tenancy version custom fork
Storage driver PostgreSQL

Hi.
Thanks for reporting this. Will be fixed in 1.8.0.

By the way, it's work great i my medium size project to your package in minutes.
Thank you.

Glad to hear that :)


fix: link to deprecated notebook in README.md

fixes #219.

Without this change
https://github.com/d3/d3-force/assets/43425812/5e2099ae-7283-4891-a00a-0adbb7eae5a6
With this change
https://github.com/d3/d3-force/assets/43425812/b276df26-69e4-4b4e-9f17-90138eaa526c

Thanks! Note that we plan to retire the README very soon, and link to d3js.org instead.

 I'll keep that in mind.


Test Connection on Athena Datasource: Fatal Python error: _Py_InitializeCore: main interpreter already initialized

Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Superset version
0.28.1
Expected results
Expected connection OK
Actual results
Fatal Python error: _Py_InitializeCore: main interpreter already initialized
Current thread 0x00007fc2727b0540 (most recent call first):
File "", line 219 in _call_with_frames_removed
File "", line 1043 in create_module
File "", line 583 in module_from_spec
File "", line 670 in _load_unlocked
File "", line 967 in _find_and_load_unlocked
File "", line 983 in _find_and_load
File "/usr/local/lib64/python3.7/site-packages/jpype/_jpackage.py", line 18 in
File "", line 219 in _call_with_frames_removed
File "", line 728 in exec_module
File "", line 677 in _load_unlocked
File "", line 967 in _find_and_load_unlocked
File "", line 983 in _find_and_load
File "/usr/local/lib64/python3.7/site-packages/jpype/init.py", line 17 in
File "", line 219 in _call_with_frames_removed
File "", line 728 in exec_module
File "", line 677 in _load_unlocked
File "", line 967 in _find_and_load_unlocked
File "", line 983 in _find_and_load
File "/usr/local/lib/python3.7/site-packages/pyathenajdbc/connection.py", line 8 in
File "", line 219 in _call_with_frames_removed
File "", line 728 in exec_module
File "", line 677 in _load_unlocked
File "", line 967 in _find_and_load_unlocked
File "", line 983 in _find_and_load
File "/usr/local/lib/python3.7/site-packages/pyathenajdbc/init.py", line 65 in connect
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/default.py", line 412 in connect
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/strategies.py", line 106 in connect
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/pool.py", line 671 in __connect
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/pool.py", line 474 in init
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/pool.py", line 347 in _create_connection
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/pool.py", line 1190 in _do_get
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/pool.py", line 529 in checkout
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/pool.py", line 788 in _checkout
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/pool.py", line 342 in unique_connection
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 2158 in _wrap_pool_connect
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 2188 in raw_connection
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 90 in init
File "/usr/local/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 2102 in connect
File "/usr/local/lib/python3.7/site-packages/superset/views/core.py", line 1780 in testconn
File "/usr/local/lib/python3.7/site-packages/flask_appbuilder/security/decorators.py", line 52 in wraps
File "/usr/local/lib/python3.7/site-packages/superset/views/base.py", line 69 in wraps
File "/usr/local/lib64/python3.7/site-packages/flask/app.py", line 1598 in dispatch_request
File "/usr/local/lib64/python3.7/site-packages/flask/app.py", line 1612 in full_dispatch_request
File "/usr/local/lib64/python3.7/site-packages/flask/app.py", line 1982 in wsgi_app
File "/usr/local/lib64/python3.7/site-packages/flask/app.py", line 1997 in call
File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 176 in handle_request
File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 135 in handle
File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 30 in accept
File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 68 in run_for_one
File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 124 in run
File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/base.py", line 134 in init_process
File "/usr/local/lib/python3.7/site-packages/gunicorn/arbiter.py", line 583 in spawn_worker
File "/usr/local/lib/python3.7/site-packages/gunicorn/arbiter.py", line 616 in spawn_workers
File "/usr/local/lib/python3.7/site-packages/gunicorn/arbiter.py", line 545 in manage_workers
File "/usr/local/lib/python3.7/site-packages/gunicorn/arbiter.py", line 203 in run
File "/usr/local/lib/python3.7/site-packages/gunicorn/app/base.py", line 72 in run
File "/usr/local/lib/python3.7/site-packages/gunicorn/app/base.py", line 223 in run
File "/usr/local/lib/python3.7/site-packages/gunicorn/app/wsgiapp.py", line 61 in run
File "/usr/local/bin/gunicorn", line 11 in
Steps to reproduce
New DataSource, entered SQLAlchemy URI, Pressed "Test Connection" button
Sample URI used:
awsathena+jdbc://myKey:mySecret@athena.us-east-1.amazonaws.com:443/analytics?s3_staging_dir='s3%3A//athena-results-wpt-dev/'

Note: works Ok when switched to awsathena+rest instead of awsathena+jdbc

I don't know if it helps at all , but we a few weeks pass we had the same error, and it was the VPC configuration as the JDBC port that Athena use changed when we updated the JDBC driver.


Add an issue template for documentation

I put in a pull request the other day to add docs to a method with none. I spent too long trying to decide which issue template to use (are missing docs a bug? A language feature? My brain almost crashed trying to decide!:) and as it was a small change @straight-shoota suggested I could've skipped opening an issue, which I agree with but only did as the contribution guidelines say to always do "unless it is a minor fix". One man's minor fix is another's rejected PR…
So, I propose a new issue template (added below), just for doc changes. My reasoning is:

It clears up any confusion
It follows the contrib guidelines
Reviewers know it shouldn't touch code and therefore might be an easier/quicker review. That's nice.
Newcomers wishing to contribute can see an obvious low-hanging-fruit path to contributing (let's be honest, even with friendly people such as yourselves it's still scary putting forth changes)
It might encourage more/better documentation.
Issues like this are better labelled as documentation than bug or feature, why not automate it

And, I've been using the API docs a lot lately (I've the memory of a goldfish so I will continue to) and saw lots I'd like to add, having a button would be nice :)
This is the template:
## Documentation Improvement

This is for documentation only, no changes to code!

Please state what you think needs changing, or if it's for a pull request, how this change would improve the docs (e.g. there were none, clarification, better examples etc)

Any thoughts?
Regards,
iain

I've sent my first PR (adding missing docs) yesterday, and it was pretty straightforward. The issue originated at #12048 and my PR was #12530, you can skim through and maybe it'll give you an idea.
In any case, once the PR was sent I was mentored all the way with great feedback so there's really nothing to be afraid of :smile:.
In my experience, reading CONTRIBUTING.md, engaging the team in an issue, opening a PR and following regular Git flow was a smooth ride.

I don't think it's a good idea to add too many specialized options to the list. It would just become overwhelming. There are already 6 items which I see as a lot.
IMO this should fall under Language Improvement Discussion. Perhaps the description is not clear enough for that, though.
So perhaps we can change the label and description in a way that it better communicates this is a very generic option. It basically catches anything that is not a bug report or a specific feature request.

@analogsalad

In any case, once the PR was sent I was mentored all the way with great feedback so there's really nothing to be afraid of

Acknowledging a good experience after the fact and believing you'll have a good experience beforehand are two separate things. If you're telling me that the Crystal team are friendly and helpful, I agree. If you're telling me that you've never encountered strangely rude and unhelpful resistance to a high quality or (to your mind) uncontroversial suggestion of any size from an open source project, then I wish I had your luck. On this point, the point is to make it easier for newcomers.
@straight-shoota I disagree about the number of buttons (as an example I like, Rust's choices are good) but that could well be in the realm of preference so perhaps your suggestion is best.
Instead of

I want to start a new discussion about improving the language.

how about?

I want to start a new discussion about improving the language (if you're not sure what type of issue you have, pick this one)

If we widen it out, Language Improvement Discussion might be better termed Language/Project Improvement Discussion.
Regards,
iain

as an example I like, Rust's choices are good

Honestly, I feel overwhelmed by that huge amount of choices.
It looks like the more relevant options, especially for uninitiated users, are at the top. Towards the bottom are more specialist choices. This is however contradicted by the options pointing to external links (aka contact_links) located at the very bottom. I think this is entirely on GitHub, though. These links (vulnerability, question, feature request) are certainly some of the most important ones for newcomers. Yet they're hidden away below the fold on a typical screen size. So I think that's another argument for keeping the list of choices short.
The Blank Issue choice serves as an easy way out if you don't know what to choose. I like that.

I've collected some statistics, just to see how much the options are used. I looked at the issues created since the start of this year (2022) and their current labels. So it does not exactly represent the choices made at the issue templates selection because labels are often altered afterwards by moderators. But it should be close enough.
As a base line, 381 issues have been created this year. 214 of them are bug reports. 77 of them are feature requests and 72 labeled as discussion.
For comparison, only 12 issues labeled as docs have been created. There is currently no option for this which likely accounts for some under-representation.
So I would say the choices we present are pretty good in covering the most common cases.

We can certainly make improvements, but I think the overall selection of choices is good.
Language Improvement Discussion is a bit of an odd item and might be cause for confusion. I had already mentioned that when the issue templates were initially introduced: https://github.com/crystal-lang/crystal/pull/8934#issuecomment-603491758
Picking up on the definition I used above ("It basically catches anything that is not a bug report or a specific feature request.") I would suggest to move it more toward Rust's Blank Issue. Maybe call it exactly that? And move it to the top?
And probably don't apply any label (moderators can add discussion if it's actually a discussion).
As a description, maybe the suggestion from https://github.com/crystal-lang/crystal/issues/12534#issuecomment-1263046971 would fit?

I want to start a new discussion about improving the language (if you're not sure what type of issue you have, pick this one)

I agree with everything except that I wouldn't move it to the top. It seems better to have Bug, Feature, Anything else. Thanks @yb66 for bringing the issue!

@analogsalad I know many professional developers who never contribute to open source or will never again, because of the difficulties they may face. I want to help them overcome their anxiety and make things as easy as possible for them. I may be right in my proposals for that, or I may be wrong, but in my experience it works for me helps absolutely no one and is rarely relevant, and here, not at all.
As to this:

I don't think we need to further complicate the process by adding documentation that will surely go stale and create bureaucratic burden for prospective contributors.

If the documentation button that's there to make documentation changes easier "surely go[es] stale" then I think we can all pack up and leave for another project because that's a canary in the coalmine if ever I heard one.

As @straight-shoota has brought up the level, I did some digging around.
Projects that have some kind of documentation button:

Python
Go
Rust
Zig
PHP
Haskell

Projects with a miscellaneous (or similar) button:

Ruby
Elixir
Haskell

Projects with neither:

Typescript
Nim
Scala
Swift
Julia

That's all either Github or stuff I have an account with, there's plenty of others like Kotlin and D that aren't using Github (and Ruby, though several sub-projects are using Github but if I start down that track I'll never finish!)
Without access to their stats/experience, and as each project has its own needs, this may mean little.

Language Improvement Discussion is a bit of an odd item

I agree, but some of those project have this though many shuffle it off to a forum.

I would suggest to move it more toward Rust's Blank Issue. Maybe call it exactly that? And move it to the top?

Sounds good. The language Elixir use (link above) seems slightly better to me though, worth considering?

Report an issue
Tell us about something that is not working the way we (probably) intend
Get started (button text)


fix(v2): use current color for language icon

Motivation
Currently the lang icon is visible only in dark mode, so to make it visible in all color modes we need to use the currentColor value.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan

Before
After

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

ah yeah 😅 thanks didn't see that


Laravel 7 support

Hi Liam,
Are you already working on Laravel 7 support? Is there anything I can do to help you?

I have submitted the PR #24 to add Laravel 7 support. Brief testing in a personal project and it works as 0.5.0 (Laravel 6 version - not deep tested in a real project, but I hope that works as expected). Tests and styles passes.
CC: @liam-wiltshire

Thanks - appears to work, so have merged :)


RC6: import @angular/core/src/facade/lang causes traceur error

I'm submitting a ...  (check one with "x")

[x] bug report => check the FAQ and search github for a similar issue or PR before submitting
[ ] support request => check the FAQ and search github for a similar issue before submitting
[ ] feature request

Current behavior
Running an Angular2 application with ng2-translate fails because it looks for traceur.js but fails to find it. In RC6, you should import the bundles as described by @robwormald in his gist.

As I believe, you where already in contact with @robwormald for this?
Expected/desired behavior
To just work out of the box :).
Reproduction of the problem
Upgrade to RC6, load in the bundles instead and it will fail with the traceur error.
What is the motivation / use case for changing the behavior?
Because ng2-translate seems to be unusable in RC6/
Please tell us about your environment:

ng2-translate version: 2.4.2

Angular version: 2.0.0-rc.6

Browser: all

Language: TypeScript (1.8)

yes, I'm on it right now, struggling with the changes to the test API which breaks my tests (the code of the lib is already updated), expect a release soon

Thanks for jumping on this so quickly!

I must admit, in my projects I had to ditch tests because of the testing API changes in ng2... It will be a while before I "trust" the testings.. given the discussions on Github..
Thank you for your effort, Olivier, it is much appreciated!

yeah they really fucked things up :(
got a few friends helping me and we cannot get the setup working :D

In case you missed it, I've updated the lib to rc6

Thanks @ocombe! Works like a charm!

You are the best!!

@ocombe This error started showing up after updating to 3.1.3.
I refered to this plnkr  but the result is the same.  in Systemjs is this the correct way of mapping the library?
'ng2-translate': 'npm:ng2-translate',

On plunkr we map directly npm to https://unpkg.com/, that's why we use the binding npm:ng2-translate.
On your own app you should just use ng2-translate

I found the issue and it is happening only with this library.
the browser is trying to look for ng2-translate.js under bundles directory and it is not there.
Sorry for asking but what would be the correct settings for transpiling the ng2-translate.d.ts file?
Is there something that is needed to be done in tsconfig.json file?

did you import from ng2-translate and not ng2-translate/ng2-translate ?

Odd, have to dig deeper into this later today. ng2-translate/ng2-translate should still work though but the preferred way of doing this now is ng2-translate.

it doesn't work because there is no ng2-translate file in the bundles directory which is where is searches now, I think

Let me try to explain here.
First of all, I'm not an expert in SystemJS/Webpack at all. I'm pretty noob on those to be honest. BUT, when I take your plunkr, it just works. I can change the language and it changes the interface.
As you said before, the config maps 'ng2-translate': 'npm:ng2-translate'. To be clear, this has nothing to do with the UMD bundle whatsoever. More to this later on.
Open up app.component.ts which imports ng2-translate/ng2-translate. This is the "old way" but still works as ng2-translate just exposes with index.ts exposes. So both can be seen as identical. You could change that line to this
import {TranslateService} from 'ng2-translate/index';

And it will still work. This is what they call a Barrel. It's the main entry point for everything inside ng2-translate. If you would use Webpack, you could just write it like this
import {TranslateService} from 'ng2-translate';

But SystemJS does not support that (currently).
I agree that importing ng2-translate/index seems weird. But you should use the ng2-translate bundle instead. This is the part where I'm stuck currently with the plunkr so I will have to dig deeper on my local filesystem. Will try to do that later today.
@ocombe Why does the bundles directory has the type definitions? The UMD bundle has nothing to do with typings. It will not try to load them or whatsoever. If someone imports ng2-translate, TypeScript will resolve the typings as configured in the package.json, being index.d.ts. The bundle is just something that SystemJS/Weback consumes.
If you look at how Angular2 ships it

I think we should try to mimick that behavior is much as possible as people are already familiair with that.

There are typings in the bundles folder because I forgot to disable typings generation when generating the bundle :D
When you import from ng2-translate/ng2-translate it takes the ng2-translate.js file at the root, which was generated when running ngc, it means that it is not UMD but ES2015 module, and I think that's a problem for systemjs, maybe we should just switch it back to commonjs instead to be sure that it works everywhere (and keep the bundle as umd) ?

There are typings in the bundles folder because I forgot to disable typings generation when generating the bundle :D

Hahah, those things happen :D.
Will check this today. Eager to know the answer :p.

@ocombe sorry for the delay.
If I map as below, the following error is thrown from traceur.
'ng2-translate': 'node_modules/ng2-translate' OR 'ng2-translate': 'npm:ng2-translate'
error message: Error loading http://<IP_ADDRESS>/node_modules/ng2-translate/ng2-translate.js as "ng2-translate/ng2-translate"
If I map as below, the following error is thrown
'ng2-translate': 'node_modules/ng2-translate/ng2-translate',
error message: GET node_modules/ng2-translate/ng2-translate/ng2-translate.js 404 (Not Found)
the above one is clearly the wrong path.
Now if I go to my browser and look for ng2-translate.js to path where is mapped I also I get "Cannot GET /node_modules/ng2-translate/bundles/ng2-translate.js" from my browser.
If I do the same thing with other libraries I can access the JS file. Any ideas of how I could solve this? :(
I will look at @SamVerschueren approach and see if it works.

In my systemjs I ended mapping as below:
'ng2-translate': 'npm:ng2-translate'
then in my components where I import the TranslateService and the TranslateModule I imported as below:
import { TranslateModule } from 'ng2-translate/bundles/index';
import { TranslateService } from 'ng2-translate/bundles/index';
As in my first comment, this problem started when I upgraded to 3.1.3. When I was using 3.1.2
I was importing as below
import { TranslateModule } from 'ng2-translate/ng2-translate';
import { TranslateService } from 'ng2-translate/ng2-translate';
and my systemjs looked like this
'ng2-translate': 'npm:ng2-translate/bundles'
I know this is a temporal workaround, @ocombe I would appreciate if you let us know if you decide switching back to commonjs.

I believe this is nothing to do with CommonJS/UMD. It has everything to do with the configuration of ng2-translate and how you consume it.
In the new release (I thought we supported the old notation as well but not sure if it works), you have to import from ng2-translate instead of ng2-translate/ng2-translate.
Because SystemJS does the module resolution, you don't have to import from bundles/index of from anywhere else. Just import from ng2-translate, that's the first step in the process.
Angular 2 suggests you use their UMD bundles in development. You could either choose to do that or not, that's up to you. The only thing you have to change is how SystemJS consumes the library in the configuration.
In the plunker you provided, you can either choose to consume the CommonJS files, or the UMD bundle.
CommonJS
'ng2-translate': 'npm:ng2-translate/index.js',

UMD
'ng2-translate': 'npm:ng2-translate/bundles/index.js',

This doesn't change anything on how you import them in your main files. It just tells SystemJS where to look if it sees an import statement for ng2-translate. This does also mean, that if you want to keep import { TranslateService } from 'ng2-translate/ng2-translate';, you can simply change the config to something like this.
'ng2-translate/ng2-translate': 'npm:ng2-translate/bundles/index.js',

You can just rename it to whatever you want.
I adjusted the plunk for both scenarios, CommonJS and UMD.
CommonJS: http://plnkr.co/edit/Qs9n2NSqGynEKmQvL5Xy
UMD: http://plnkr.co/edit/eKVwIDVPBNpEBABd5HcR
I really hope this helps and gives a better understanding of how things work.

We should probably add all of this to the readme

@ocombe Yes, was thinking the same. It just follows how Angular does it though, but apparently the Angular docs seems clearer :).
Maybe we should create a docs directory where we explain how people should configure the module with SystemJS and with Webpack. This way we could keep the main docs in the readme, "how to use the module" and the APIs etc. And then we can extract bundle specific stuff to seperate doc files. Let me know what you think, I would be happy to do it for SystemJS. Not much experience with Webpack but I can always take a look. We should also update the examples :).

We can use the wiki here, and link to it from the readme. I gave you collaborators rights on the repo.
For webpack it's easier, it just works out of the box, it's systemjs that's complicated because the config is used browser side where it cannot look for modules in node_modules all by itself so you have to define everything manually

I gave you collaborators rights on the repo.

Thanks 🎉

We can use the wiki here

👍

Unsure if it's related but I'm getting
  26 10 2016 08:59:33.116:WARN [web-server]: 404: /base/node_modules/ng2-translate.js
  26 10 2016 08:59:33.162:WARN [web-server]: 404: /base/node_modules/lodash.js
  PhantomJS 2.1.1 (Windows 7 0.0.0) ERROR: '(SystemJS) XHR error (404 Not Found) loading http://localhost:9876/base/node_modules/ng2-translate.js

When I run karma test. Those files don't even exist in my node_module directory (under that path) . my app.component.ts imports from ng2-translate.
Any idea?

well yeah it doesn't exist, you're trying to load http://localhost:9876/base/node_modules/ng2-translate.js instead of http://localhost:9876/base/node_modules/ng2-translate/ng2-translate.js or http://localhost:9876/base/node_modules/ng2-translate/bundles/index.js

Nothing to do with this as lodash suffers the same fait. Not that familiair with Karma but either it's a  karma config thing, or a SystemJS config thing when it can't find the correct file in the correct location. If it's working in development, it's probably Karma who can't find the correct file, so that means it's a karma config.
When I open a Karma config file, this is what I see
...
files: [
    // paths loaded via module imports
    // Angular itself
    { pattern<EMAIL_ADDRESS>included: false, watched: true },
    { pattern<EMAIL_ADDRESS>included: false, watched: false },

    // NgRx
    { pattern<EMAIL_ADDRESS>included: false, watched: true },
    { pattern<EMAIL_ADDRESS>included: false, watched: false },

    // many more
]
...

Try to add ng2-translate over there.

Adding it to my karma config file doesn't work. This is based off of angular2 seed for what it's worth. If my app.component.ts is importing from ng2-translate (and that's the standard) why would it be looking for non existent files?

Like I said, I'm not familiair with Karma so I can't answer that question. The thing I know though is that it's the module bundler (SystemJS or Webpack) that does the module resolution. That's why you need to configure SystemJS that it looks for<EMAIL_ADDRESS>How Karma does it? I have no clue, does it use SystemJS? And if so, what config does it pick?
I don't think this discussion belongs here though and is more like a StackOverflow support question. Like I said, it doesn't find lodash as well so it's definitely a config problem.

@SamVerschueren, thank you for explaining. I mapped as you mentioned here fixed my issue.

@3du4 Glad you got it working :)


Atom will not start

After I install this package Atom will not start and don't get any errors. ps shows a few atom processes but there is no window. After some debugging I found that the problem is with this statement:
alert "Warning from atom-ctags:
atom-ctags replaces and enhances the symbols-view package.
Therefore, symbols-view has been disabled."
After removing this alert and running "apm install" atom works again.

Cannot reproduce this issue. Please provide these information to me:
os version
atom version
atom-ctag version

Linux Mint 17.1 with Cinnamon 2.4.6
This happened when I installed from terminal with apm. When I installed the package from the UI, the message was displayed and it worked. I am on another PC right now and can't give you more info but will  try to when I can.

Similar problem here.
Ubuntu 14.04
Atom 0.189.0 (had issue in previous version too)
atom-ctags 2.6.1

Same problem here.
Ubuntu 14.04
Atom 0.198.0
atom-ctags 3.2.0 (Version that I can see when installed through interface)
Also solved by installing through editor.


EPSG

Hi Craig,
I'm the Geodetic Datum Manager at Geoscience Australia and I have received advice from a colleague in the New South Wales Government that Microsoft SQL Server does not yet accommodate Australia's new geodetic datum, the Geocentric Datum of Australia 2020 (GDA2020). Can you please let me know if the next version of SQL Server (2019?) will update from the EPSG Geodetic Parameter Dataset, or put me in touch with the appropriate Microsoft SQL Server development team to discuss this issue?
Kind Regards
Daniel Jaksa

Apologies Criag,
I mean't to say "... will update from the EPSG Geodetic Parameter Dataset, or ..."
Kind Regards
Dan

@MashaMSFT Hi Masha, Ping me and I can explain how you, as this week's Triager, should process and update this type of GitHub Issue (1641).  Thx G

@craigg-msft FYI

Hi @danieljaksa , thanks for contacting Microsoft! This is really something that should be requested via User Voice https://aka.ms/sqlfeedback. However, as a courtesy, I'll ask around a bit to see if I can find any more information about existing plans for SQL Server 2019. Thanks!

Thank you @MashaMSFT,
Much appreciated.  I attempted going through various support avenues, but the contact and support links went litterally around in circles or with a "Gateway Timeout".  You are my only hope (Obi Wan) :)
Kind Regards
Dan

Hi @danieljaksa , can you please confirm if this is referring to spatial data? You're asking if the spatial data coordinates are going to updated to the GDA2020 version, right? Thanks!

Thanks @MashaMSFT,
Yep, that's correct, I'm referring to spatial data. To use the SQL Server parlance "geography".  All spatial coordinates (latitude, longitude or X, Y, Z or eastings and northings) must use a coordinate reference system (CRS). The geodetic parameters that define these CRS's used around the world can be found in the EPSG Geodetic Parameter Dataset.  Your documentation mentions the EPSG in the MSFT Spatial Reference Identifiers (SRIDs) webpage.  It is my understanding that SQL Servers uses the EPSG register.
If you're interested in more information on Australia's  new CRS have a look at the GDA2020 website.  The USA is going through a similar process which NOAA's National Geodetic Survey is running.
Kind Regards
Dan

Hi @danieljaksa ,
We'd like to get a bit more information about this. Would you mind emailing me directly at<EMAIL_ADDRESS>Thanks!

Will do.

Hi @danieljaksa , thanks again for bringing this to our attention! We will work online to research this further, and I will proceed with closing out this Git Issue at this time. Thanks!

@danieljaksa Hi Daniel, Here is a set of links about other ways to contact Microsoft or to get more info. Perhaps one of these links might be more useful to you for this particular inquiry, than this documentation Issues webpage can be.
Thanks.

All the ways to get help
UserVoice - Suggestion to improve SQL Server?
Setup and Upgrade -  MSDN Forum
SQL Server Data Tools - MSDN forum
Transact-SQL - MSDN forum
SQL Server Security -  MSDN Forum
DBA Stack Exchange (tag sql-server) - ask SQL Server questions
Stack Overflow (tag sql-server) - also has some answers about SQL development
Reddit - general discussion about SQL Server
Microsoft SQL Server License Terms and Information
Support options for business users
Contact Microsoft
Edit SQL Docs
SQL Docs Feedback
SQL Docs Survey

CC: @MashaMSFT

Thanks Gene,
Much appreciated.  I’ll see how I get on.
Kind Regards,
Dan
Daniel Jaksa |  Datum Manager |  National Geodesy Section
National Positioning Infrastructure Branch  |  Positioning and Community Safety Division
t +61 2 6249 9685    m +61 (0) 438 245 637    @danksahttps://twitter.com/danksa www.ga.gov.auhttp://www.ga.gov.au/
[16-9481 GA Email Signature_social media-04]http://www.ga.gov.au/
[16-9481 GA Email Signature_social media-v2-01]https://twitter.com/GeoscienceAus[16-9481 GA Email Signature_social media-v5]https://www.facebook.com/GeoscienceAustralia[16-9481 GA Email Signature_social media-v2-02]https://www.youtube.com/user/GeoscienceAustralia[16-9481 GA Email Signature_social media-03]https://www.linkedin.com/company/geoscience-australia<EMAIL_ADDRESS>http://www.ga.gov.au/scientific-topics/positioning-navigation/datum-modernisation
From: Gene Milener<EMAIL_ADDRESS>Sent: Saturday, 16 February 2019 9:53 PM
To: MicrosoftDocs/sql-docs<EMAIL_ADDRESS>Cc: Jaksa Daniel<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/sql-docs] EPSG (#1641)
@danieljaksahttps://github.com/danieljaksa Hi Daniel, Here is a set of links about other ways to contact Microsoft or to get more info. Perhaps one of these links might be more useful to you for this particular inquiry, than this documentation Issues webpage can be.
Thanks.

All the ways to get helphttps://docs.microsoft.com/sql/sql-server/sql-server-get-help
UserVoice - Suggestion to improve SQL Server?https://feedback.azure.com/forums/908035-sql-server
Setup and Upgrade - MSDN Forumhttps://social.msdn.microsoft.com/Forums/en-US/home?forum=sqlsetupandupgrade&filter=alltypes&sort=lastpostdesc
SQL Server Data Tools - MSDN forumhttps://social.msdn.microsoft.com/Forums/en-US/home?forum=ssdt&filter=alltypes&sort=lastpostdesc
Transact-SQL - MSDN forumhttps://social.msdn.microsoft.com/Forums/en-US/home?forum=transactsql
SQL Server Security - MSDN Forumhttps://social.msdn.microsoft.com/Forums/en-US/home?forum=sqlsecurity&filter=alltypes&sort=lastpostdesc
DBA Stack Exchange (tag sql-server) - ask SQL Server questionshttps://dba.stackexchange.com/questions/tagged/sql-server
Stack Overflow (tag sql-server) - also has some answers about SQL developmenthttps://stackoverflow.com/questions/tagged/sql-server
Reddit - general discussion about SQL Serverhttps://www.reddit.com/r/SQLServer/
Microsoft SQL Server License Terms and Informationhttps://www.microsoft.com/download/details.aspx?id=39299
Support options for business usershttps://support.microsoft.com/gp/support-options-for-business
Contact Microsofthttps://support.microsoft.com/gp/contactus81?Audience=Commercial
Edit SQL Docshttps://aka.ms/editsqldocs
SQL Docs Feedbackhttps://aka.ms/sqldocsfeedback
SQL Docs Surveyhttps://aka.ms/sqldocsurvey

CC: @MashaMSFThttps://github.com/MashaMSFT
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/sql-docs/issues/1641#issuecomment-464335948, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ApIEXjd1HKywEjou6mq-aQ_7GAwSs3N4ks5vN-L0gaJpZM4a6l9n.
Geoscience Australia Disclaimer: This e-mail (and files transmitted with it) is intended only for the person or entity to which it is addressed. If you are not the intended recipient, then you have received this e-mail by mistake and any use, dissemination, forwarding, printing or copying of this e-mail and its file attachments is prohibited. The security of emails transmitted cannot be guaranteed; by forwarding or replying to this email, you acknowledge and accept these risks.


feat: copy code

Related to #238

I think we still need a tooltip/popover as a feedback that the code has been copied.

Do you have any ideas about how to handle long text that appears under the copy button?

Perhaps we can add pe-10 to the content of the <pre>  to add padding at the end so that the copy icon is not covering the text?

Perhaps we can add pe-10 to the content of the  to add padding at the end so that the copy icon is not covering the text?

Actually no that wouldn't look good if there are more than 1 line in the codeblock. This problem only happens to the first line of the content of the codeblock. If we add the end-padding it will look good when it's only 1 line but won't look good when more than 1 line.

Actually it doesn't look bad and works well.
Although I had to do style={{ paddingInlineEnd: 50 }} because tailwind's pe-12 classname didn't work for some reason

You're welcome 👍
@colebemis if I ever get around making a popover that says "copied", should I place it inside the IconButton next to the shortcut condition? or make it stand-alone and wrap the IconButton in this PR with the new popover?

@zaaakher I don't think it needs to be a popover. I like the idea of having it switch to a checkmark icon temporarily instead (which also seems simpler to implement).
https://github.com/lumen-notes/lumen/assets/4608155/49ed5908-94a0-4fe7-acd8-055d725438d9

Agree, much simpler 👍 just implemented it in #241


Install Mathjs

Hi and good day,
I would like to ask, why the error kept on showing as i already tried to installed 3 different version of node.js (v12, v20, and v21) but the error kept on showing the same things. Do you have any suggestion for this?

For some reason it happened in your environment, but i made sure it won't happen again.
Thank you for reporting.


Ollama Embedding provider

Hello,
This is my first contribution on this project and I would like to propose the usage of ollama as an Embedding Generator.
This PR is mainly about a new Class OllamaEmbeddingGenerator.php that implements the EmbeddingGeneratorInterface and make an API Call to Ollama embedding endpoint.

Hello @npotier ,
Thanks for your PR! Few comments :

for now, we only support OpenAI, so it would start a not-so-little change ;)
because OpenAI embeddings have 1536 dimensions, this PR needs to add a dynamic length for embeddings like in the DoctrineEmbeddingEntityBase class and QdrantVectorStore class.

@MaximeThoonsen I just sent a proposal for supporting other LLMs using Ollama. I think we can add the embedding support as @npotier proposed.

@npotier do you plan to resolve conflicts ? I can help if you want it. Thanks !

@npotier I created another PR for this feature, hope it does not upset you.
https://github.com/theodo-group/LLPhant/pull/84

Hey @npotier , I'm closing this one because I merged the work of Arnaud.

Hello @arnaudgoulpeau thanks for your rework, and i'm not upset about it ;)


Android restful implementation

Android restful implementation
1. Implemented a way of calling WorldScope App Server's RESTful API using Retrofit and Gson library
2. Implemented logging in and out of WorldScope App Server after Facebook authentication
3. Added a navigational drawer in MainActivity and populate it with Facebook data into it
4. Added an animated background into WorldScope client's login screen
5. Refactored a callback class into LitmusPlayer that instantiated it

I don't see any other major issues.

Okay. Good to merge

Thanks =)


Great!!!!

Mike,
Whooo....this is so nice you made this setup. For months, I have been trying to find a good, simple dev setup for a client's Elecrow 7 inch (ca. 18 cm). What you made is exactly what I was looking for. Amazing work!!
Only one suggestion, add a Linux sh command for Linux users (like me). I manually copied the board JSON file to the correct folder. Works like champ.
Warm regards
Rob

You can just replace /Users/mikewarriner in the Mac script with ~ (which should be done anyways for Mac users)