tag images we create in the Makefile

[ ] creds shared among @cloudfoundry-incubator/blockhead-team
[ ] make target to docker push separate from the build images target.
[ ] overridable registry so I can push to my personal location instead of blockheads
[ ] travis gets special revokable push creds to push to docker hub

#50 tags images
#53 makes image repo customizable


Writing ARM outputs to YAML file (instead of, currently, Azure DevOps variable group)

Is your feature request related to a problem? Please describe.
Currently, we have in our Azure DevOps module some functionality to write the ARM outputs to Azure DevOps variable groups but not yet to YAML configuration files.
Describe the solution you'd like
Adds functionality to write the ARM outputs to an YAML file.
Additional context
Follow-up of https://github.com/Codit/codit-academy/issues/132#issuecomment-1072259534

A reminder for my fellow partner @pim-simons 😉 .

I'm actually very much doubting if this is something that we want.
This would mean that pipeline-runs modify the contents of your  code-base, as the yaml files are stored in your repository.
Actually, I would try to avoid using ARM outputs alltogether in CI/CD pipelines, and if you really need them, I'd just make them available in a non-persistent way: in variables that are scoped to my pipeline. (And thus even not write them to variable groups).

I'm actually very much doubting if this is something that we want. This would mean that pipeline-runs modify the contents of your code-base, as the yaml files are stored in your repository.
Actually, I would try to avoid using ARM outputs alltogether in CI/CD pipelines, and if you really need them, I'd just make them available in a non-persistent way: in variables that are scoped to my pipeline. (And thus even not write them to variable groups).
I used ARM outputs in the past as well, but I now tend to avoid them alltogether. When I need a certain property of something that was deployed in my pipeline, I now use Azure CLI script to look-up that value, instead of having it outputted in an ARM template, especially when we're talking about sensitive information.

Honestly, I'm way outside this scope of technology 😅 , so I can't really give my view on things bc I've have actually no idea how these things are used, or even what ARM templates are actually for. I'll let @pim-simons handle this. 😄
If it's indeed about sensitive information, then I'm all for removing it from public spaces. 👍

I'm actually very much doubting if this is something that we want. This would mean that pipeline-runs modify the contents of your code-base, as the yaml files are stored in your repository.
Actually, I would try to avoid using ARM outputs alltogether in CI/CD pipelines, and if you really need them, I'd just make them available in a non-persistent way: in variables that are scoped to my pipeline. (And thus even not write them to variable groups).
I used ARM outputs in the past as well, but I now tend to avoid them alltogether. When I need a certain property of something that was deployed in my pipeline, I now use Azure CLI script to look-up that value, instead of having it outputted in an ARM template, especially when we're talking about sensitive information.

Some good points 👍🏻
Writing to a file in your code-base will be a challenge indeed, since you cannot simply change this in your main branch you would have to create a new branch for this, this would make the script a lot more complex.
Regarding:

I used ARM outputs in the past as well, but I now tend to avoid them alltogether. When I need a certain property of something that was deployed in my pipeline, I now use Azure CLI script to look-up that value, instead of having it outputted in an ARM template, especially when we're talking about sensitive information.

I suppose you get the values using Azure CLI and then pass them along using a variable? Do you maybe have an example of this you can share?

I suppose you get the values using Azure CLI and then pass them along using a variable to your ARM/Bicep? Do you maybe have an example of this you can share?

Actually, it is quite simple.
The below sample shows how I retrieve ACR credentials and put them in a variable that I then can use in another task.
- task: AzureCLI@2
  displayName: 'Get ACR credentials'
  inputs:
      azureSubscription: ...
      scriptType: 'pscore'
      scriptLocation: 'inlineScript'
      errorActionPreference: 'stop'
      inlineScript: |
        $registryName = "$(ContainerRegistry.Address)".TrimEnd('.azurecr.io')

        $containerCreds = az acr credential show --name $registryName --resource-group rg-myresourcegroup | ConvertFrom-Json

        $acrPwd = $containerCreds.passwords[0].value
        Write-Host "##vso[task.setvariable variable=ContainerRegistry.Password;issecret=true]$acrPwd"

Ah, was under the impression that "writing to a YAML" file here meant that it is written to a file during the CI build and so never is placed in source control, but only gets written and read during the CI build. But, then I'm wrong, here 😅 .

Yaml pipelines in Azure DevOps are afaik comparable to GitHub actions.
You write a pipeline in yaml, and your pipeline consists of multiple tasks.   Your pipeline also uses variables, which you can declare in your yaml.
Azure DevOps allows you to split your pipeline over multiple files.  So, what I typically do, is split my tasks logically and put the ones that belong together in separate files.   I also create separate files that contain the variables that my pipelines need.
It can be that, during the execution of your pipeline, you need to have some values that are the output of a deployment of an Azure resource.   In the past, we retrieved those outputs and put them in a 'Variable group' and since that variable group (which is defined in Azure DevOps is linked to your pipeline, you have access to those values.
However, what this issue is talking about, is that you write those outputs to a separate yaml file which would then be part of your pipeline.

I suppose you get the values using Azure CLI and then pass them along using a variable to your ARM/Bicep? Do you maybe have an example of this you can share?

Actually, it is quite simple. The below sample shows how I retrieve ACR credentials and put them in a variable that I then can use in another task.
- task: AzureCLI@2
  displayName: 'Get ACR credentials'
  inputs:
      azureSubscription: ...
      scriptType: 'pscore'
      scriptLocation: 'inlineScript'
      errorActionPreference: 'stop'
      inlineScript: |
        $registryName = "$(ContainerRegistry.Address)".TrimEnd('.azurecr.io')

        $containerCreds = az acr credential show --name $registryName --resource-group rg-myresourcegroup | ConvertFrom-Json

        $acrPwd = $containerCreds.passwords[0].value
        Write-Host "##vso[task.setvariable variable=ContainerRegistry.Password;issecret=true]$acrPwd"

Awesome, thanks for the example!

Ah, was under the impression that "writing to a YAML" file here meant that it is written to a file during the CI build and so never is placed in source control, but only gets written and read during the CI build. But, then I'm wrong, here 😅 .

Yaml pipelines in Azure DevOps are afaik comparable to GitHub actions. You write a pipeline in yaml, and your pipeline consists of multiple tasks. Your pipeline also uses variables, which you can declare in your yaml. Azure DevOps allows you to split your pipeline over multiple files. So, what I typically do, is split my tasks logically and put the ones that belong together in separate files. I also create separate files that contain the variables that my pipelines need. It can be that, during the execution of your pipeline, you need to have some values that are the output of a deployment of an Azure resource. In the past, we retrieved those outputs and put them in a 'Variable group' and since that variable group (which is defined in Azure DevOps is linked to your pipeline, you have access to those values. However, what this issue is talking about, is that you write those outputs to a separate yaml file which would then be part of your pipeline.

So what is our conclusion here, do we still see the need for writing the ARM outputs to a YAML variable file?
Personally I think there are enough doubts around this (and maybe even better ways of working) to at least put it on hold for a while and discuss a bit further. @fgheysels @stijnmoreels what do you think?

I don't think we need this.
I don't even know if it is possible to do this, and I very much doubt that if this would be possible, if it's even useful. :?

I'll let you guys decide, happy to close this if it's not necessary or helpful. 👍

I think we can close this for now, if the need comes up again we can discuss this later. For now I see too many issues and better ways of working.


ddnet: 16.3.1 -> 16.3.2

Description of changes

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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 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

[ ] Fits CONTRIBUTING.md.

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

1 package built:

ddnet

Game starts, diff looks good

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/603

Doesn't build on darwin according to ofborg

Before we do that let us try adding the darwin frameworks. Maybe it just works.


Add example covering the conformance mismatch section

I've added a bunch of examples here to cover the content in Common Errors > Protocol Conformance Isolation Mismatch.
Depends on #23

Yes I always try to do that. I don’t know why I did it…


NXP sensors - add SW filters set from params

fxos8701cq:Clean up & paramater based low pass fileter

Added paramater based low pass fileter settting from
IMU_ACCEL_CUTOFF.

removed gotos.

fxas21002c:Clean  and speed up with SW, HW LPF.

Added paramater based low pass fileter settting from
IMU_GYRO_CUTOFF.

Added interfaces for setting the HW low pass filter.
Set HW LPF to 64 Hz

Changed poll rate to ODR to 800 Hz.

Documented the TIMER_REDUCTION value as 20% and changed it to
250 Us / 1250 us.

Added standby control API, to insure chip is configured in standby mode.

removed tabs.

removed gotos.

@davids5 The vehicle does not maintain the heigt on altitude mode, and the position mode does not work. also the telemetry conction it's broken and the conection by usb to qgc.
Also sometimes does not respond to the radio.
https://review.px4.io/plot_app?log=1c07ef0b-32dd-4e25-ad4e-fa397306de03

Rebased on master with "Mavlink Fixes for NXPhlite"
@PX4/testflights Please test this by comparing it to master, Both this PR and master have the coms issue fixed. We want to see if calibration and flight is better with this PR's  filter changes for the sensors
I also need you to offer feedback on the following:
I either have an issue with the GPS/MAG of there is a bug I need you to confirm if you are seeing the same thing.
Build and upload the firmware with QGC or make nxphlite-v3_default upload
(do not connect debugger or console)
Connect buzzer.
Power from battery cycle the power and see if the boot hangs.
Observe the green LED it should be blinking. If it is not or the buzzer is stuck you are seeing what I am.
Thank you!


Is it possible to have a function nearest_radius that includes the maximum radius?

I think that everything is ready to allow users to pass the maximum radius when searching for nearest points. Unfortunately rust does not support optional arguments yet, so something like this could be trivial to implement:
pub fn nearest_radius<F>(
        &self,
        point: &[A],
        num: usize,
        radius: A,
        distance: &F,
    )

The current function
pub fn nearest<F>(
        &self,
        point: &[A],
        num: usize,
        distance: &F,
    )

calls to
self.nearest_step(
                point,
                num,
                A::infinity(),
                distance,
                &mut pending,
                &mut evaluated,
            );

which already has the maximum radius as A::infinity().

So we already have nearest by count and within by radius, and the suggestion seems to be a combination of them.
Any thoughts how we can combine them with a flexible interface instead of adding another method?
Currently not actively working on this - if you're interested, a PR would be great!

If it is possible to modify the function signature (adding the new parameter) the modified function should be:
pub fn nearest<F>(
        &self,
        point: &[A],
        num: usize,
        radius: A,
        distance: &F,
    )

Not sure if a good idea to change the API. That was the reason to propose a new method instead. A simple solution could be implementing a new nearest_with_radius and the old nearest calls to nearest_with_radius to avoid code duplication:
pub fn nearest<F>(
        &self,
        point: &[A],
        num: usize,
        radius: A,
        distance: &F,
    ) -> Result<Vec<(A, &T)>, ErrorKind> {
   nearest_with_radius(self,point,num, A::infinity(), distance)
}

I can make PR but I want to discuss first with you the proposed solution.

Thanks @exepulveda I'm supportive of merging them into one interface - it'd be a breaking change & we will just follow semantic versioning bumping to 0.7


Do not panic inside the lib, handle errors in main()

As far as I can see this is entirely obsolete now that the argument parser has been merged. For now I'll leave it open for review anyway, and have another look at it later.

Rewritten based on current master.


Attachment Option

This Issue relies on https://github.com/discordjs/discord-api-types/pull/272 and https://github.com/discord/discord-api-docs/pull/4253

[x] Wait for https://github.com/discordjs/discord.js/pull/7200 to be published.

Closed by https://github.com/SocketSomeone/necord/commit/6dfbe8d62ba8b0232fbfd9eb7b03fdc72a291d16


Test types for browser actions

Hi!
With this PR I submit tests for all types related to taiko API's browser actions, i.e.:

openBrowser
closeBrowser
client
switchTo
intercept
emulateNetwork
emulateDevice
setViewPort
openTab
closeTab
openIncognitoWindow
closeIncognitoWindow
overridePermissions
clearPermissionOverrides
setCookie
deleteCookies
getCookies
setLocation
clearIntercept

Some of them required to fix the type declaration in index.d.ts.
Also the last commit imports (as dev dependency) devtools-protocol which is the official repository of the protocol and provides some useful types that otherwise we should re-define. In this commit we use the type Cookie for getCookies. previously that was treated simply as an object, now it gets proper typing.
Sorry if the PR is quite heavy and it may require some time to review.
Filippo

@fmpanelli Thanks for taking effort to correct these 👍


[i18n] multi-language for pages

Issue Summary
I followed the tutorial on multi-language content for Ghost, but it does only seem to work for posts and not for pages created in the backend. Is there something I’m doing wrong?
To Reproduce

/german-blog-post automatically redirects to /de/german-blog-post
/german-page doesn’t redirect to /de/german-page

both (blog post and page) have the tag de that is defined for the collection in routes.yaml
Technical details:

Ghost Version: 2.21.1
Node Version: 10.15.2
Browser/OS: Vivaldi/Chromium on mac OS
Database: MySQL

Hi,
thanks for clarification. Actually I created a forum post 3 days before, but had no replies at all and the documentation is at least not clear enough on that topic. I was thinking that this might be a bug (or feature request).


GET ERROR: failed to pull image: exit status 1 for all syncs

for example
02/09/2024 13:50:05 INFO: pulling image docker://ghcr.io/mergestat/sync-mergestat-explore:latest
02/09/2024 13:50:05 ERROR: failed to pull image: exit status 1

pulled ghcr.io/mergestat/sync-mergestat-explore:latest to host then it looked like it works
but after some time it stoped working

You may find more logs on what's going on in the worker logs.
If you are using a laptop with an ARM CPU, maybe your issue could be related to this Pull Request

I've found occasionally you have to shell into the worker and run:
rm -rf /tmp/containers-user-1001 /tmp/podman-run-1001

to get it to pull the image correctly


Move currentStartTime into remember block

Issue

close 227

Overview (Required)

Just move into remember block

Let me check！👓

@minibugdev
thank you for separating PR 😉


Font color in Dark Theme is too dark

Font color in Dark and Black Themes is too dark
Description
Unlike screenshots on README file the font color in Dark Theme and in Black Theme is gray, too dark, making it unreadable
Environment
OS Platform:	linux
OS Release: 	4.4.0-96-generic
Architecture: 	x64

Tusk version: 0.5.1

You can change the text color to any you like using the colors palette from the editor toolbar.

I have the same issue here. I want to make it readable without changing the color.


Recent commit prevents Format Document from working on custom extension vue files.

This commit (d7202e3a1b318b798ac9869912c1b09d4dc314a1) appears to have broken the Format Document command (probably all document formatting) when using custom extensions for Vue files.
In volar 1.0.16, our project that uses custom file extensions works fine with the format document command. After upgrading to the latest version (1.0.18) I noticed it no longer was formatting the documents when requested. After digging through the commits one by one this specific commit seems to be where it broke.
I looked through the changes in that commit and I don't see anything that should be causing this problem. But I have tried going back and forth between those two commits a couple times and it always works on the commit before but not on the commit mentioned above.
I'll keep poking around, but wanted to get it on the board since it was a recent change. If you have any specific ideas on researching this further I'd be happy to dig deeper.
Steps to reproduce:

Check out the repository at the commit just PRIOR to the one mentioned above.
Run "pnpm i" followed by "pnpm run build"
Open repo in VS Code and run it.
Add "obs" to volar.vueserver.additionalExtensions configuration setting.
Add "src/**/*.obs" to tsconfig includes.
Add "*.obs" -> "vue" to files.associations configuration setting.
Rename "HelloWorld.vue" to "HelloWorld.obs".
Open the Volar-Starter repo in the development environment VS Code.
Make a change to the file that would be fixed by formatting (such as additional space between the "import" keyword and the opening brace).
Activate the VS Code command "Format Document" and see that the spacing is correctly fixed.
THEN update repo to the next commit - that is the one mentioned above.
Remove node_modules and run "pnpmi" and "pnpm run build".
Open repo in VS Code again and run it.
Make the same change to the "HelloWorld.obs" file.
Activate the VS Code command "Format Document" and see that nothing happens.

(Edit: Fixed link to commit to be in the main repo instead of my forked repo)

Thanks for your detailed information! Will check it out.

Before https://github.com/johnsoncodehk/volar/commit/d7202e3a1b318b798ac9869912c1b09d4dc314a1 all document names all is untitled + document language, so the vueCompilerOptions.extensions is just getting ignored.

@johnsoncodehk Thanks for the quick response on this! I just tested against our main repo/branch and confirm it does indeed fix the problem.


[Bug] Descending column sort does not work with empty cells

Describe the bug
When a table is presented to boomtable and there are cells with no value, a "descending sort" (arrow points down as selected from the column header) fails to sort the table correctly.
Screenshots
Later.
Version Details:

Grafana version :  6.3.4
Plugin version : 1.3

Additional context
Doing an ascending sort (arrow points up) works correctly. The descending sort does not present the table in the reverse order of an ascending sort.

I think that is the expected behaviour. Even default grafana table plugin works same way. Doesn't?

i have not tested it.


Finish mobile version

In this PR I worked on other two sections Works section and the About section to finish the mobile version of a portfolio project. They are built with HTML and CSS only.

Hello @AbelG101
Thanks for your feedback on my submission. I have made the correction as per your request Plz let me know what is next.


maturinBuildHook assumes target path

Describe the bug
The maturinBuildHook appears to assume the output path for the wheel will be build/target/wheels/*.whl
In the case of docleaf the rust code lives under a subdirectory.
docleaf repo https://github.com/docleaf-labs/docleaf/tree/main
buildPythonPackage expression I wrote https://github.com/teburd/nix-flake-zephyr-dev-shell/blob/main/nix/docleaf.nix
Steps To Reproduce
Steps to reproduce the behavior:

clone nix-flake-zephyr-dev-shell repo
nix develop

Expected behavior
I think the issue is the script is not taking into account the cargoRoot attribute

With #272661 the cargoRoot will be taken into account, when moving the wheel into the dist directory.


Flutter Doctor doesn't recognise installed Dart/Flutter IDEA/AS plugins

Steps to Reproduce

Make sure Flutter is up to date: $ flutter update (on master)
Install Android Studio 3.3 canary 13, and/or IDEA 2018.3 AEP
Install the Dart and Flutter plugins in the IDE(s) and restart them
Run flutter doctor

Observe how the Dart and Flutter plugins aren't picked up by Doctor, that sees the IDEs as installed but doesn't pick up the plugins.
Logs
flutter doctor -v
[✓] Flutter (Channel master, v0.10.1-pre.66, on Mac OS X 10.14 18A391, locale en-GB)
    • Flutter version 0.10.1-pre.66 at /Users/rock3r/src/flutter
    • Framework revision 936dea28da (4 hours ago), 2018-10-17 08:09:29 +0200
    • Engine revision 08272ee6aa
    • Dart version 2.1.0-dev.7.1.flutter-b99bcfd309

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    • Android SDK at /Users/rock3r/android-sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /Users/rock3r/android-sdk
    • Java binary at: /Applications/Android Studio 3.3 Preview.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.0, Build version 10A255
    • ios-deploy 2.0.0
    • CocoaPods version 1.5.3

[✓] Android Studio
    • Android Studio at /Applications/Android Studio 3.3 Preview.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[!] IntelliJ IDEA Ultimate Edition (version 2018.3 EAP)
    • IntelliJ at /Users/rock3r/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.io/intellij-setup/#installing-the-plugins

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

Proof that the plugins are installed:

Android Studio 3.3 Canary 13
IntelliJ IDEA 2018.3 (EAP)

Closing as dup of https://github.com/flutter/flutter-intellij/issues/2644

@zoechi this is completely unrelated with the issue you linked. It's a doctor issue, not an IntelliJ plugin issue.

Install Android Studio 3.3 canary 13

flutter/flutter-intellij#2644 says Canary is not supported.

AS 3.3 Canary is supported since v28.0 of the IntelliJ plugin and IDEA 2018.3 EAP since v29.0 — see the changelog. Regardless, this is not a "plugin not working/supported in an IDE". The issue is that flutter doctor detects the IDEs but does not seem to recognise that they have the plugins installed — both Dart and Flutter.

Sorry for not coming back to this earlier.
I assume this issue is stale. Please let us know if you're still seeing this problem.

Maybe duple of: https://github.com/flutter/flutter/issues/26928 and fixed totally after https://github.com/flutter/flutter/pull/27687/files.

Please reopen - it resurrected.
Seeing the 35.0 plugin and Dart 2.3 I've switched to beta channel.
Now doctor sees no plugins in AS 3.4. Neither it sees installed NDK:
cat $NDK_HOME/source.properties
Pkg.Desc = Android NDK
Pkg.Revision = 19.2.5345600

Plugins:
Dart v183.6270
Flutter v35.0.1

I even did a reinstall plugins voodoo. To no avail.
flutter doctor -v
[✓] Flutter (Channel beta, v1.5.4, on Linux, locale pl_PL.utf8)
    • Flutter version 1.5.4 at /testbed/flutter
    • Framework revision b593f5167b (7 days ago), 2019-04-22 07:51:33 -0700
    • Engine revision ca31a7c57b
    • Dart version 2.3.0 (build 2.3.0-dev.0.1 cf4444b803)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /testbed/Android/Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /testbed/Android/Sdk
    • Java binary at: /testbed/Android/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152_testbed)
    • All Android licenses accepted.

[!] Android Studio
    • Android Studio at /testbed/Android/android-studio
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • android-studio-dir = /testbed/Android/android-studio
    • Java version OpenJDK Runtime Environment (build 1.8.0_152_testbed)

[!] Connected device

I am also facing the same issue with IntelliJ Ultimate and Android Studio.
✅ Android Studio Issue is solved
❌ IntelliJ Issue still exists
This ist What I have figured out till now:
I install IDEA products using IDEA Toolbox, that's why the plugins are not saved under:

/Users/[USER]/Library/Application Support/IntelliJIdea2019.1
but under
/Users/[USER]/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/192.5728.98/IntelliJ IDEA.app.plugins
I assume, Flutter is looking for plugins in the first directory and cant find them.

ℹ To solve the issue with Android Studio I simply installed and updated the Flutter and dot plugins. The only difference between Android Studio and IntelliJ on my machine(macOS Mojave) is that the Android Studio's plugins are installed under:
 /Users/[User]/Library/Application Support/AndroidStudio3.4 and IntelliJ installs its plugins under:
  /Users/[USER]/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/192.5728.98/IntelliJ IDEA.app.plugins

[✗] Cannot determine if IntelliJ is installed
    ✗ Directory listing failed

https://qnttran.medium.com/flutter-in-multiple-ide-android-intellij-vscode-for-macos-ba928d58b4a4
hope this help


[Bug]: OpenAPI YAML converts strings to boolean

Describe the bug
TypeSpec converts "no" enum strings to "False", which is incorrect.
This is the so-called Norway Problem:
countries:
- GB
- NO  // Becomes false

The safest way would be to use "string" quotes for enum string values that convert to a boolean, case-insensitive:
y|yes|n|no|true|false|on|off

Reproduction
This TypeSpec file:
@service({})
namespace Main;

enum Countries {
    GB: "gb",
    NO: "no",   // !!! Norway problem
}

gets compiled into this OpenAPI:
components:
  schemas:
    Countries:
      type: string
      enum:
        - gb
        - no   # !!! Becomes boolean "false", but must be a string

Playground: link
Or compile locally this way:
$ npm install @typespec/compiler @typespec/openapi3
$ tsp compile --emit @typespec/openapi3 .

Checklist

[x] Follow our Code of Conduct
[x] Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[x] The provided reproduction is a minimal reproducible example of the bug.

@kolypto I try it in Playground, but it looks like want you want. Could you double confirm?

@wanlwanl it looks alright, but it won't work alright :)

Indeed, the Yaml list is rendered this way:
      enum:
        - gb
        - no

However, in Yaml, this will result in this JSON: [ "gb", false ] because no in Yaml is a boolean value! :)
It should be quoted in the output:
      enum:
        - gb
        - "no"

@kolypto Thank you for your explanation. This is indeed related to the YAML standard specifications. YAML 1.1 treats yes/no as boolean values, while YAML 1.2 does not. The issue in typespec should indeed be addressed to support YAML 1.1 properly. For now, a temporary workaround could be explicitly specifying YAML version 1.2.x doc section 1.6.8.
FYI:
https://yaml.org/spec/1.1/current.html#id864510
https://yaml.org/spec/1.2.2/#3232-scalar-formats
https://perlpunk.github.io/yaml-test-schema/schemas.html


How to enable pinch to zoom?

How can I add pinch to Zoom?
It seems that it's enabled by default, but I can't get it to work.
Is there any special property I'm supposed to set to PDF()?

@yakeer It looks like other widget consumes your pinch gestures.
Try to specify PanGestureRecognizer explicitly in gestureRecognizers.
PDF(gestureRecognizers: [Factory(() => PanGestureRecognizer())].toSet())

You can read more about it from here:
  /// Which gestures should be consumed by the pdf view.
  ///
  /// It is possible for other gesture recognizers to be competing with the pdf view on pointer
  /// events, e.g if the pdf view is inside a [ListView] the [ListView] will want to handle
  /// vertical drags. The pdf view will claim gestures that are recognized by any of the
  /// recognizers on this list.
  ///
  /// When this set is empty or null, the pdf view will only handle pointer events for gestures that
  /// were not claimed by any other gesture recognizer.
  final Set<Factory<OneSequenceGestureRecognizer>>? gestureRecognizers;

This will help https://www.youtube.com/watch?v=gAUVz0U7eyA


Japanese Holidays in English from 2019

Hello,
Wonder if there is a script in English. Where I work, we've been using Outlook with English version. This script can't be run due to language...
Appreciate your help if possible and thank you for sharing this.

Hi @moon73 ,
Thank you for your feedback.
It seems that we need to add English environment support. I'll work on this and update the script in the near future.

Hi @moon73 ,
I added an English version script. You can download the file from here.
https://github.com/microsoft/AddOutlookJapanHoliday/releases/download/PreRelease/AddHolidays_en.zip
I hope this script works for you. Let me know if you have any problems on this script.
Especially, let me know if you are using Outlook in English and the names of holidays are Japanese. This script expects the environment that Outlook in English and the names of holidays are also English.

Hi @rykoma,
This worked perfect! Much appreciated. You saved me! :)
The script successfully run in the following environment, Outlook in Eng + Holidays in Eng + Windows in Eng. This is what I expected exactly. Can't thank you enough. I will distribute this to end users. Again, thanks a lot for your quick help.

Closing...

I'm glad to hear that!
I added the English script to the latest release.
https://github.com/microsoft/AddOutlookJapanHoliday/releases/download/v1.1/AddHolidays_en.zip
Thank you again for your feedback.


Error when running lift save following tutorial

Hi there,
I followed the guide here, ran into #73 where the init flow didn't finish because I'm using psql and then followed the Tutorial doc.
When I tried to run prisma2 lift save, I got the following error, Error: Got invalid RPC response without .result property: {}
Running<EMAIL_ADDRESS>binary version: 33e5fc84b6bd61602f8d634beb558230ca3e3054 on macOS 10.14.3 and psql 11.
Thanks :)

I am unable to reproduce this.
Can you please tell me which OS you are using and where is your postgres instance hosted?

@pantharshit00 I'm also having the same issue. Here you go.
Prisma version<EMAIL_ADDRESS>binary version: 33e5fc84b6bd61602f8d634beb558230ca3e3054
PostgreSQL version psql (PostgreSQL) 11.4
macOS version 10.14.5 (18F132)

I got the same error using MySQL 5.7 on localhost on MacOS 10.14.6

@ralvs @alizahid
Still no luck. Maybe can you please share your schema files?

@pantharshit00 I got the same error, but noticed that the error went away as soon as I took out the enum. I didn't exactly follow the tutorial so my schema is a bit different (this current schema doesn't work).
datasource db {
  provider = "postgresql"
  url      = "postgresql://albert@localhost:5432/theorem?schema=public"
}

generator photonjs {
  provider = "photonjs"
}

model Product {
  id          String   @default(cuid()) @id
  createdAt   DateTime @default(now())
  description String?
  name        String?
  type        String?
  updatedAt   DateTime @updatedAt
  url         String?
  vendor      Vendor[] @map("Vendor")
}

model User {
  id         String    @default(cuid())  @id
  createdAt  DateTime  @default(now())
  email      String    @unique
  name       String?
  phone      String?
  updatedAt  DateTime  @updatedAt
  role       Role      @default(USER)
  vendor     Vendor[]
}

model Vendor {
  id        String    @default(cuid()) @id
  createdAt DateTime  @default(now())
  name      String?
  product   Product[] @map("Product")
  slug      String?
  updatedAt DateTime  @updatedAt
  user      User?
}

enum {
  USER
  ADMIN
}

I had the same problem, but it turned out to be because of an extra ! that I left in my schema (what used to signify required fields). I'm no expert on the matter so I don't know what caused it at all, but that's just what happened in my case.

@pantharshit00 I have the same problem
Docker postgres version: 11.5-1
Created with docker run --name prisma -v pgdata:/var/lib/postgresql/data -p 54321:5432 -e POSTGRES_PASSWORD=postgres -d postgres
Prisma version<EMAIL_ADDRESS>binary version: 33e5fc84b6bd61602f8d634beb558230ca3e3054
MacOS version: 10.14.5
This is the schema.prisma file:
datasource db {
  provider = "postgresql"
  url      = "postgresql://postgres:postgres@localhost:54321/postgres?schema=public"
}

generator photonjs {
  provider = "photonjs"
}

model User {
  id        Int      @id
  createdAt DateTime @default(now())
  email     String   @unique
  name      String?
  role      Role     @default(USER)
  posts     Post[]
  profile   Profile?
  address   Address?
}

embed Address {
  street  String
  zipCode String
}

model Profile {
  id   Int    @id
  user User
  bio  String
}

model Post {
  id         Int        @id
  createdAt  DateTime   @default(now())
  updatedAt  DateTime   @updatedAt
  author     User
  title      String
  published  Boolean    @default(false)
  categories Category[]
}

model Category {
  id    Int    @id
  name  String
  posts Post[]
}

enum Role {
  USER
  ADMIN
}

More info:
When removing:
embed Address {
  street  String
  zipCode String
}

and address   Address? from user the migrations work.

<EMAIL_ADDRESS>binary version: 33e5fc84b6bd61602f8d634beb558230ca3e3054
PostgreSQL 10.3
macOS 10.12.6
I had this issue and fixing two things allow the migration to work.

I used a new schema instead of using  'public' but the name had hyphens in it (test-schema). Looking at logs revealed:

ERROR:  syntax error at or near "-" at character 23
STATEMENT:  SET search_path = test-schema

- Fixed by deleting dir and rerunning `prisma2 init prisma2` making sure my schema had no hyphens.

The next issue might be related to a schema linting. I finally learned of vscode-prisma where issue 8 revealed that the linter doesn't accept optional lists []?.

Fixed by changing all []? to []

@Oscarteg that's because embed is not supported yet

Yes, indeed @Oscarteg, embeds are not implemented yet as pointed out by @deadcoder0904. Follow https://github.com/prisma/lift/issues/43 for updates on that.
@bearcanrun
We are aware of the error caused by dashes in the schema name. It is being tracked here: https://github.com/prisma/prisma2/issues/311.The other issue is also being tracked for as you have already mentioned.
I think I can close this issue now as it is touching multiple other issues. If anyone of you are getting a different problem which was not already reported, please open a new issue 🙂


Latest version on NPM is older (1.0.11) than latest release (1.0.12)

see https://www.npmjs.com/package/BaremetricsCalendar

Updated!


tune PID parameter

i have a six rotor aircraft on hand, the weight is about 10Kg, the wheelbase is about 1680MM, the default pid parameter dose not work well, so can anybody give me some advice about tuning the pid parameter?

What do you mean by not working?
What is the problem? What is the multicopter behavior? Is it too aggressive or drunk copter?

哥们。你是哪的呀？你的问法太中式化了 😁

It's always a good idea to share a log and/or video. Otherwise it is very hard to give advice.
(And please stick to English here, thanks).

i see @julianoes

it didn't work well, not "not working", it was  too aggressive, but now it's better. Thanks!!!

it didn't work well, not "not working", it was too aggressive, but now it's better. Thank you!!! @AlexisTM

shandong @ardente

@applededipan The log download function (new in last QGroundControl version) allow you to download the log (.px4log file). You upload the log to Log Muncher and it will plot relevant data!

To tune the PID, you can go in the "tuning section" of qGroundControl. NOTE : Correctly read the informations. I would suggest putting Roll & Pitch Sensitivity to the right, Attitude Control Sensitivity to the left and Position Control Sensitivity to the left.

@applededipan What are your current parameters (Multicopter Attitude Control) ?

Closing as stale.


Update tables requirement, remove 3.9 warning

Tables was updated in December 2021 to cover Python 3.9. This PR updates requirements.txt with the latest tables version, and removes the warning in clients.py.
Note I didn't touch requirements.in. I'm not sure how that one is used.

Thank you, Greg. Much appreciated!


gateway: set CORS headers for browser support

@smuu was recently hacking on celestia-node and wasn't able to use any of our APIs in the browser because of CORS issues. We should add CORS headers on both gateway and RPC and allow all the origins

Ideally, the port the RPC server listens on should not be exposed to WAN. It can be shared in LAN or within datacenter clusters. Even if there is a rare usecase for remote usage, it's better to filtering on IP firewall level, rather than polluting config with HTTP headers for gateway.

https://github.com/celestiaorg/celestia-node/pull/2373


added a semi-colon (prevent conflicts with bundlers)

without this our minifiers bundlers can produce unexecutable code :
TypeError: (intermediate value)(...) is not a function

(close was by accident)

This actually solved the issue!

Hmm it's rather bundler problem, but OK :-)

1.1.1 release with your fix published.


CodeBuild Artifacts NameSpaceType not Supported

Hi,
Just came across the Issue with CodeBuild Artifacts Property NameSpaceType. AWS Cloudformation gives me following error:

Property validation failure: [Encountered unsupported properties in {/Artifacts}: [NameSpaceType]]

which means that Cloudformation only supports Property "NamespaceType" and not "NameSpaceType" according to the AWS Documentation. Can you please update this at your end.
Please let me know if you require more information.
Regards

Thanks for the issue.


display-dependency-updates is showing a version that no longer exists

A coworker accidentally published an incorrect version "62" instead of "1.2.062". When running display-dependency-updates 62 was showing, so I deleted it from my local ~/.m2/repositories cache and also deleted it from our private Nexus. The build is now fixed and we have versions past 1.2.063. For some reason display-dependency-updates is still showing version 62. I tried deleting ~/.m2/repository/org/codehaus/mojo/versions-maven-plugin/ but it still shows up. Is there another cache somewhere that has this info in it? I know that version 62 is gone from Nexus because the build fails if we try to use it.
We could add a ruleset to ignore this version, but I'd prefer not to have to do that in all of our projects since this used in all of them.

Have you regenerated the Maven Metadata in Nexus ?

Sorry, was on vacation. Will check shortly.

I went in to our private repo and the mirrors/groups and clicked "rebuild index" and "invalidate cache" and I'm still getting those versions. Is there something else I can try?

Can you check the maven-metadata.xml file which is created from your Nexus? Just a second. There two things. Rebuilding index and Rebuilding metadata...you need to rebuild metadata...

I added a rebuild metadata task and ran it. Still getting it. We've been suppressing it w/ a rule, so I guess this isn't that important.


Metadata Configuration

In thinking about a general purpose release of this utility, we should explore ways to extract metadata elements and directory structure for input and output into a config file.

This is handled through the MAP (https://uhlibraries-digital.github.io/bcdams-map/) which is integrated into Brays.