🐛 [firebase_ui_localizations] Unknown error

Is there an existing issue for this?

[X] I have searched the existing issues and found no duplicates.

What plugin is this bug for?
Firebase UI Localizations
What platform(s) does this bug affect?
Web
List of dependencies used.

flutter pub deps -s list

  calendar_date_picker2: ^0.5.2
  collection: ^1.17.1
  equatable: ^2.0.5
  extended_masked_text: ^2.3.1
  file_picker: ^5.3.3
  firebase_analytics_web: ^0.5.4+3
  firebase_auth: ^4.6.3
  firebase_core: ^2.14.0
  firebase_ui_auth: ^1.4.3
  firebase_ui_localizations: ^1.6.1
  flutter:
    sdk: flutter
  flutter_bloc: ^8.0.1
  flutter_localizations:
    sdk: flutter
  get_it: ^7.2.0
  go_router: ^11.1.1
  google_fonts: ^4.0.4
  intl: ^0.18.0
  isoweek: ^1.1.4
  pdf: ^3.10.4
  rxdart: ^0.27.7
  screenshot: ^2.1.0
  uuid: ^3.0.7

Steps to reproduce
Not sure how to reproduce this error. I used firebase_ui_localizations to translate Firebase UI Auth screen from the default english to dutch. It seems everything is translated as expected except for the error below:

I can't seem to reproduce this error as it pop, I encountered it a few times.
I tried: non-existent username and password, non-existent username and existing password and vice versa, and the error messages are translated, except the error message in the image. I couldn't find a pattern to reproduce this error.
Expected Behavior
The error message to be translated, like every other field in the Firebase UI Auth screen currently is.
Actual Behavior
That specific error message from the picture provided isn't translated to dutch, yet the other fields are.
Additional Information

flutter doctor -v
[✓] Flutter (Channel stable, 3.13.7, on macOS 14.0 23A344 darwin-arm64, locale en-NL)
    • Flutter version 3.13.7 on channel stable at /Users/andreisas/Development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2f708eb839 (3 weeks ago), 2023-10-09 09:58:08 -0500
    • Engine revision a794cf2681
    • Dart version 3.1.3
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /Users/andreisas/Library/Android/sdk
    • Platform android-33, build-tools 33.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] VS Code (version 1.83.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.74.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 14.0 23A344 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 118.0.5993.117

[✓] Network resources
    • All expected network resources are available.

Hi @andreisas06, do you get this issue on either android or iOS as well? Do you also get this issue with the plugin example app?
Please also provide the output of flutter pub deps -- --style=compact.
Thank you

Nope, the project that I am working on is exclusively a Web project, it doesn't have the build files for Android or IOS.
Here is the output you requested:
Dart SDK 3.1.3
Flutter SDK 3.13.7
zwierink_workspace 0.0.0
dev dependencies:

melos 3.1.1 [ansi_styles args cli_launcher cli_util collection conventional_commit file glob graphs http meta mustache_template path platform pool prompts pub_semver pub_updater pubspec string_scanner yaml yaml_edit]

transitive dependencies:

ansi_styles 0.3.2+1
args 2.4.2
async 2.11.0 [collection meta]
boolean_selector 2.1.1 [source_span string_scanner]
charcode 1.3.1
cli_launcher 0.3.1 [path yaml]
cli_util 0.4.0 [meta path]
collection 1.18.0
conventional_commit 0.6.0+1
file 6.1.4 [meta path]
glob 2.1.2 [async collection file path string_scanner]
graphs 2.3.1 [collection]
http 1.1.0 [async http_parser meta]
http_parser 4.0.2 [collection source_span string_scanner typed_data]
io 1.0.4 [meta path string_scanner]
json_annotation 4.8.1 [meta]
matcher 0.12.16 [async meta stack_trace term_glyph test_api]
meta 1.9.1
mustache_template 2.0.0
path 1.8.3
platform 3.1.2
pool 1.5.1 [async stack_trace]
process 4.2.4 [file path platform]
prompts 2.0.0 [charcode io]
pub_semver 2.1.4 [collection meta]
pub_updater 0.3.1 [http json_annotation process pub_semver]
pubspec 2.3.0 [path pub_semver yaml uri]
quiver 3.2.1 [matcher]
source_span 1.10.0 [collection path term_glyph]
stack_trace 1.11.1 [path]
stream_channel 2.1.2 [async]
string_scanner 1.2.0 [source_span]
term_glyph 1.2.1
test_api 0.6.1 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph]
typed_data 1.3.2 [collection]
uri 1.0.0 [matcher quiver]
yaml 3.1.2 [collection source_span string_scanner]
yaml_edit 2.1.1 [collection meta source_span yaml]

Hi @andreisas06, I am not seeing the versions of the firebase_ui_* packages you're using in your project from the output your provided above.
What version you're of the firebase_ui_* packages are you using in your project? Also, what version of auth do you have in your project?
From what I'm seeing in the translations for dutch, it seems like the account not found error should have been translated, but the error seems different that what you are showing. See https://github.com/firebase/FirebaseUI-Flutter/blob/1a0385c3aa61e1bf9b67e8d42e72f29004074ff1/packages/firebase_ui_localizations/lib/src/lang/nl.dart#L245

firebase_analytics_web: ^0.5.4+3
firebase_auth: ^4.6.3
firebase_core: ^2.14.0
firebase_ui_auth: ^1.4.3
firebase_ui_localizations: ^1.6.1
These are my firebase dependencies.
Yes it should have been translated since the other parts of firebase ui are translated.
Is there any other thing I can provide you with to narrow down the issue and give you more context?

Hi @andreisas06, you are using older versions of the firebase packages, can you upgrade to the latest versions to see if you still have this issue?

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Update versions in include-metrics documentation

In the include metrics documentation, the bStats version is 2.2.1 but the latest is 3.0.0 as of writing this. There may be other outdated versions e.g. maven plugins, but I haven't checked.

Fixed in https://github.com/Bastian/bStats/commit/3c8830c522133bba7addb315290e79c08486f59f


css-minification-benchmark results

Hi, Ben!
I found a link to css-minification-benchmark. Based on the information in it now cssnano slowest, in comparison with the others. Perhaps this information will be of interest to you.

Sorry, I looked at the closed issues and understand that you are informed a long time.

Yep, actually I sent in a couple of patches for that. But it's using the old 2.x releases, we are async since 3.x. :smile:


ProjectProvider & ProjectFactory -> VFPT.Core

Dependent upon completion of Open Documents Tracker #1410
IProjectProvider interface will be defined and the ProjectProvider type will be implemented in VFPT.Core. (Logic may still need to have a VsProjectProvider that implements the IProjectProvider interface). The ProjectProvider implementation can probably be changed to acquire compilation flags, project contents and configurations settings,
Most of the ProjectFactory  business logic can be changed to respond to events sent from the logic side.
Any data that requires the DTE for acquisition should be sent from Logic to Core

VirtualProjectProvider should be passed the FSharpCompilerVersion as a parameter instead of the VisualStudioVersion

WIP - Need to review further to layout how to split roles between ProjectFactory in Core and Logic
Code Located @
https://github.com/fsprojects/VisualFSharpPowerTools/blob/master/src/FSharpVSPowerTools.Logic/ProjectSystem/ProjectProvider.fs
https://github.com/fsprojects/VisualFSharpPowerTools/blob/master/src/FSharpVSPowerTools.Logic/ProjectSystem/ProjectFactory.fs

I'd like to rename it to ISolution/Solution.

@cloudRoutine having this moved to core would simplify work I'm doing on GoToDefinitionFilter as i'd need not to get rid of it / ISolution.
So for now, I won't move stuff to Core but focus on other remaining dependencies.

@vasily-kirichenko I agree we should have something for Solution but we can't just rename it I believe, for example GetReferencedProjects doesn't make sense on Solution and probably other inconsistencies.
I think we can start define Solution and move the "identified once for all projects in solution" aspects to that interface when they become identified.
What do you all think?

Solution concept for us is just "set of projects", nothing more. I don't think it should do anything beyond simple operations like "opened", "closed", "project loaded", "project updated", etc.

We can split out ProjectDescriptor (a record with the same member as the get properties in current IProjectProvider) as I was (kind of) describing in #1440, I think this should be done disregarding the fact that #1410 is done or not.


Support for MERGE WITH SCHEMA EVOLUTION

Describe the feature
Add support for the new MERGE WITH SCHEMA EVOLUTION syntax available on the current and preview channel SQL Warehouse versions. https://docs.databricks.com/en/delta/update-schema.html#schema-evolution-syntax-for-sql.
This is especially useful if you need schema evolution on struct data types.
The change is quite easy SQL wise, but I don't know how you would want to expose the option... via on_schema_change?

@stevenayers-bge Hi, just to be sure I understand correctly. What is the difference between running this and setting the parameter for the table?
Based on Databricks documentation there are no differences.
Some use case might be helpful.

Fixed in #739


ReactiveUI-Events doesn't have "Click" for a Windows Store Button

When trying to hook the Click event of a Button up to execute a command (not attached to a ViewModel, so I couldn't use BindCommand), I discovered that Click wasn't implemented in ReactiveUI.Events. Is there a reason for that, or just an oversight? If an oversight would you take a PR (or someone else would do it)?

All of ReactiveUI.Events are generated code - digging out why Click doesn't show up might not be a Joy (it looks to be defined on ButtonBase)

All of ReactiveUI.Events are generated code - digging out why Click doesn't show up might not be a Joy (it looks to be defined on ButtonBase)

All of ReactiveUI.Events are generated code - digging out why Click doesn't show up might not be a Joy (it looks to be defined on ButtonBase)

The same applies to WPF, so assuming it works there, the cause is probably in the reflection code.

Works on my machine

CloseDetailViewButton is of type Button
App is a Windows 8.1 Store app

@flagbug @gordonwatts which versions of reactiveui-events are we using here?

@shiftkey <IP_ADDRESS>

Aha! I had a reference to the Win81 profile in the NuGet package where the Click event exists, but it seems like it's missing in the WPA81 profile.

That is the issue for me, then. I'm using the WPA81.

Since this is a difference in the implementations is it obvious what happened to one of you (e.g. it didn't get rebuilt) or shall I investigate?

Can you try  using Windows.UI.Xaml.Controls.Primitives?

How do you mean (and was that suggestion addressed to me)?

I believe @jlaanstra meant adding a using statement for Windows.UI.Xaml.Controls.Primitives. Because events is generated code, the events for a given control are generated in the same namespace as said control. Since the event you want is on the base class, and the base class is in a different namespace to the derived class, you have to take the somewhat confusing step of including the base class's namespace.

I had the same problem yesterday. Feels weird because there is no way to find Click event except to add the using manually.


fix: make lean4 build on FreeBSD

Upstreaming patches from the FreeBSD port.
The port compiles successfully on FreeBSD and all but 6 tests pass.

Please don't include the changes to stage0 in the PR (unless they are needed for subsequent changes, in which case they should be in their own commit. (See https://lean-lang.org/lean4/doc/dev/bootstrap.html#updating-stage0)


Using Testcontainers for R2DBC MySQL Integration Testing #108

Motivation:
To use testcontainers for R2DBC MySQL Integration Testing #76
Modification:

Removing block to start/destroy mysql container from ci-integration-tests.yml
In IntegrationTestSupport adding static block to start mysql container.
Use mapped port of container while building MySqlConnectionConfiguration

Result:
All tests working locally.

close after making coauthored https://github.com/asyncer-io/r2dbc-mysql/pull/264 based off of this


[bug?] Revealed back layout in post frame callback is not concealed

Hi. I was trying to simulate the automatic revealing of the back layer right after the widget tree was created. For this, I placed a BackdropScaffoldState::revealBackLayer() call in WidgetsBinding.instance.addPostFrameCallback(). It works, but there is a side effect: when I tap the "Close" button to conceal the back layer, it doesn't concealed, it just doesn't respond when clicked. I gave an example here to make it easier to understand what it is about.
class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Backdrop Example',
      theme: ThemeData(
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: BackdropScaffold(
        appBar: BackdropAppBar(
          title: Text("Backdrop Example"),
        ),
        backLayer: BackLayer(
          text: "Back Layer",
        ),
        frontLayer: Center(
          child: Text("Front Layer"),
        ),
      ),
    );
  }
}

class BackLayer extends StatelessWidget {
  final String text;

  BackLayer({Key key, this.text}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    WidgetsBinding.instance.addPostFrameCallback((_) {
      Backdrop.of(context).revealBackLayer();
    });

    return Container(
      child: Center(child: Text(text)),
    );
  }
}

@proninyaroslav the problem is you are calling
    WidgetsBinding.instance.addPostFrameCallback((_) {
      Backdrop.of(context).revealBackLayer();
    });

every time the build method is executed. So back layer always gets revealed when the UI is repainted.
Convert the BackLayer to a StatefulWidget and put the code within initState() instead of build(). This way, the code is executed only after the very first paint.

Thank you.


Add customize options for time & date picker dialog

Add all of property in TimePickerDialog and DatePickerDialog class to customize color

Hi Sonnt1012,
You've answered my question! I had the exact same issue with changing the colors in these controls. I see you've committed some changes but they're not in the master branch. I'm new to using git and don't understand how to  get your changes using cocoa pods. Any ideas?
Best Wishes
Jim


Turn off the base map tiles?

Issue Type
[x] Question
[ ] Bug
[ ] Improvement
[ ] Build system related
[ ] Performance
[ ] Documentation
Description and/or steps/code to reproduce the problem
How does one turn off the base map, so that only the overlays are visible? MapView.setEnable(false) has no effect. OfflineTileProvider.setUseDataConnection(false) will stop the downloading of tiles, but cached tiles are still rendered. Is there away to disable cached tile retrieval? Lastly I thought perhaps a BlankTileSource that serves up a blank image tile. Before I dive off into "BlankTileSource" development. Have I missed something simple? Is there a way to turn off base map tile rendering and only render overlays.
Version of osmdroid the issue relates to:
6.0.2

nice username, had a chuckle for sure.
try iterating over the overlays and remove the TilesOverlay. Not sure what will happen but it might work

I guess a custom BlankTileSource would be safe, and it shouldn't take that long. Something like min and max zoom = 30 should be enough, starting from any existing tile source.


Scaffolding never connects on 2.0.0-preview018.1

I attempted using the latest version of prisma2 CLI scaffolding for GraphQL no auth starter project (currently 2.0.0-preview018.1) but that never connected to the database (Windows 10 + Powershell 6).
I tried using instead npx<EMAIL_ADDRESS>init myproject and it worked with the same parameters

Hi,
Thanks for reporting this! It has already been reported before, so I am going to close this as a duplicate of #1087 or #1092


Add process to workstreams when on-boarding users to determine appropriate sizing of environment

Determine Small, Medium, Large sizing for notebooks

Would like workstream leads to help define memory needs using yml file format to programmatically setup configurations


feat: show /star-search suggestions as carousel

Description
Change the SuggestionBoxes in /star-search from a scrollable  list to a carousel, based on the shadcn component.

Related Tickets & Documents
Closes #3243
Closes #3423

Mobile & Desktop Screenshots/Recordings
https://github.com/open-sauced/app/assets/20603494/fba70e4d-45b9-46bf-bfda-2085c620619c

Steps to QA

Tier (staff will fill in)

[ ] Tier 1
[ ] Tier 2
[x] Tier 3
[ ] Tier 4

[optional] What gif best describes this PR or how it makes you feel?

@zeucapua nice work!!
can we maybe bring the carousel waaay down? should be very close to the input box, kind of like this:

@zeucapua, I'll be taking a peek at this after the livestream and all hands.
Ensure that the carousel when opened or closed adjusts the prompt/response area height accordingly. (relates to #3444
The logic for determing that can be found here.
https://github.com/open-sauced/app/blob/beta/pages/star-search/index.tsx#L465-L469


"err wrong command" on correct command

So this happened. Got Err... wrong command when the comment was corrected.

LOL you typed js arrya slice (spot the type?).
Wat was smart enough to auto-correct it, but my Tour code wasn't:
  tour.step(1)
    .begin(start1)
    .expect("command", function (data, cb) {
      cb(data.command === 'js array slice');
    })
    .reject('Err.. wrong command.')
    .wait(1000)
    .end(end1)

Fixed it to be more lenient.

Published the fix :)


WIP: allow using either scipy-openblas64 or MKL

add a meson option for the LAPACK lib
remove scipy-openblas64 from pyproject.toml
build with --no-build-isolation

Success! Builds with ILP64 MKL, and 2**28 test passes locally.
TODO:

[ ] make it build with either OpenBLAS or MKL; need to pass the name mangling rule from meson/pip to the C preprocessor;
[ ] the "add symlinks" step from https://github.com/numpy/numpy/pull/24893 does not seem needed. Has been fixed with MKL 2024?
[ ] mkl_sequential is hardcoded. Changing to _gomp/_iomp variants both give a silent wrong answer for 2**28 test and segfaults regular tests
[ ] incompatible pointer warnings: benign or not? What are the actual MKL prototypes / int types.


Dark mode test

Cypress Test for dark mode button on offcanvas menu

Odd that prettier might different results on different machines. Regardless, code should be fine for now, feel free to merge it if it is green.


Will use fabbers to construct factories when the commander should really do it

Queller will make sub-optimal decisions when it comes to building factories.

This is a limitation of the AI engine. Locking out other builders from constructing factories has proven worse than allowing the odd sub-optimal decision as to who should construct the next factory.


Fix the cleanup of file cache in server

Fix #4278 , without the cleanup, editing tspconfig.yaml won't take effect in LSP server

All changed packages have been documented.

:white_check_mark: @typespec/compiler

Show changes
@typespec/compiler - fix ✏

Changing tspconfig.yaml won't take effect in LSP server because of the cache

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


Install redux-thunk. Apply middleware.

This was completed in a prior pull request.

This was completed in a prior pull request.


Receive: make exemplars storage a flag

Is your proposal related to a problem?
Right now Thanos Receiver hardcoded exemplarStorage to true here https://github.com/thanos-io/thanos/blob/main/cmd/thanos/receive.go#L86.
For users who don't need exemplars at all, this introduces additional overhead on the TSDB side. We should make it configurable to turn on/off for this feature. Even in Prometheus this is not enabled by default.
Describe the solution you'd like
Add a new flag in Thanos Receiver.

Ah actually for Receiver we can disable exemplar storage by setting max exemplars to 0, which is the default value.
However, in TSDB there is code like this https://github.com/prometheus/prometheus/blob/main/tsdb/head_append.go#L133.
Even if the max exemplar is 0, as long as the flag is enabled then TSDB will allocate a buffer for exemplars. Maybe we should change the logic in the tsdb side to avoid the allocation.

Hi, if we want to activate exemplars, what value could be set for max exemplar ?
could it be just 1 ? or any specific number ?
regards

@flenoir Hi, any value that is > 0 can activate exemplars feature, but in that case only 1 exemplar can be kept.

Can we disable exemplar storage when exemplars is set to 0?


_plot.AllVar() misbehaves a bit

Motivations:

The new routine _plot.AllVar() seems to not behave the way it is supposed to
In particular:

the argument rows has the wring name: it is in reality the number of columns
When the number of columns (rows) is increased, the a large blank space is left at the bottom of the figure

Proposition:

Introduced the matplotlib.gridspec sub-library that gives more detailed control over that type issues
Rename rows to ncols (the way it is called in gridspec)
Make the whole space of the figure is used
use axes and figure handles instead of plt for more control

Oh excellent ! I didn't knew indeed about gridspec, I'll implement this in a new PR. I'll also replace the variable name with the symbol and latex in it

Included in PR, thanks !


Parameter Mandatory Guidelines

What's the right guidelines for Parameter Mandatory in each get/set/test targetresource.
If it's false no need to mention, but it's true, it should be written:
Good
[System.Management.Automation.PSCredential]  $InstallAccount
Bad
[parameter(Mandatory = $false)] [System.Management.Automation.PSCredential]  $InstallAccount

@luigilink [Parameter(Mandatory = $false)] should not be used as it is implied for all parameters in PowerShell functions. If you want to point out to the user that the parameter is optional, this should be done in the help comment for the function instead of by declaring this attribute in the code.
An example of how to write the attribute correctly can be seen here, but perhaps, yes, we should also add a best practice not to use [Parameter(Mandatory = $false)]

I'll throw my two cents in here seeing as the reason @luigilink is bringing this up is my fault.
I thought the logic behind specifying it was essentially the same reason we don't use positional parameters. By not specifying it we rely on people knowing the default behaviour that is implied when it comes out, but by having it there we are very clear what is mandatory and what isn't. So I would argue that putting it in would be a better practice than taking it out and letting it be implied.

I would argue for not using Mandatory = $false.
First because I think by using Mandatory = $false it does not improve the readability which parameter are mandatory or not.
If a parameter has Mandatory = $false on it, the first you see is Mandatory and you read it as as 'Oh, it's mandatory' and then you see $false and you think '...or not' 😉
Secondly I don't like adding code that is not necessary. Unless it improves readability.
And third, a parameter that is mandatory could be written as following. Might not be allowed in style guidelines now.
[Parameter(Mandatory)]
[System.String]
$Name

I my opinion I think for best readability the following would be a good example of writing mandatory and non-mandatory parameters. The eyes likes consistent look and can easily and fast distinguish small differences. Good when reviewing. 😄
function MyFunction
{
    param
    (
        [Parameter(Mandatory)]
        [System.String]
        $Name,

        [Parameter()]
        [System.String]
        $ServerName
    )
}

As always. I'm happy for whatever we decide, as long as we use the same. 😄
And finally a big thanks to @luigilink for his efforts in all the repositories he is contributing too which make differences such as this brought to light. 👏 😄

@johlju - gets my vote. I also follow the above style when I can. Although I think you're right about [Parameter(Mandatory)] not being allowed.

Urgh - fine I'll cave to peer pressure then :P
I'll arrange the updates to be made to SharePointDsc and OfficeOnlineServerDscto bring them up to scratch

If we all are in agreement, I think we also need to add a section to the style guideline as well, so this is documented. Like Parameters using Mandatory attribute. I could send in a PR with a proposal for that, unless someone else would like to do it.
@kwirkykat is there a reason we use [Parameter(Mandatory = $true)] and not [Parameter(Mandatory)]?
@BrianFarnhill  Sorry for all the code you need to change. :) But something you can be proud of it that the way we do things in other resources is because of the way you do it in SharePointDsc. You do some great work! 😄

@johlju I generally put in [Parameter(Mandatory = $true)] instead of [Parameter(Mandatory)] because technically the Mandatory parameter is a boolean and not a switch. You can also have other values after Mandatory that do not have boolean values (such as Position which takes an int), and I just personally think it looks strange to provide values for some and not others.
You can use either one though. I'm really not a big stickler on this rule to begin with as long as the attribute is in the right place above the parameter declaration.
[Parameter()] feels like the same thing as [Parameter(Mandatory = $false)] to me. It's just not needed. But I think technically [Parameter()] probably should be included everywhere just to formally declare the parameters as public cmdlet parameters as the documentation here describes.
@BrianFarnhill This wouldn't really change anything. You don't need to update SharepointDsc just for style unless you really want to.

So to summarize (if I may):

Every parameter must include regardless if it actually requires decoration: [Parameter()]
A parameter that is mandatory should contain this decoration:  [Parameter(Mandatory = $true)]
A parameter that is not mandatory should contain this decoration:  [Parameter(Mandatory = $false)]
These guidelines should only be applied to future resources and changes. Updating existing repositories to meet these guidelines is up to the repository administrator(s).

Does the above sound correct?

I interpreted @kwirkykat as that number 3 in your summary list should be replaced by number 1. And in future (and current) PRs all parameters should contain number 1 for all non-mandatory parameters.
But I do think present HQRM resources should adhere to the guidelines in the earliest convenience, to not confuse contributors to what style/method to use. Or at least submit an issue that the resource(s) does not yet follow new guidelines.
But that just my opinion :)

@PlagueHO @johlju
1, 2, and 4 are correct
3 --> A parameter that is not mandatory should not contain the decoration [Parameter(Mandatory = $false)] but instead just use [Parameter()] as specified in 1

@kwirkykat - doh! Thanks for the correction. So:

Every parameter must include regardless if it actually requires decoration: [Parameter()]
A parameter that is mandatory should contain this decoration: [Parameter(Mandatory = $true)]
A parameter that is not mandatory should not contain a Mandatory decoration in the [Parameter()]
These guidelines should only be applied to future resources and changes. Updating existing repositories to meet these guidelines is up to the repository administrator(s).

Added a proposal to the StyleGuildelines.md. let me know if it looks okay and that's what we want. I used @PlagueHO's summation.


When setting left and right padding in RTL mode, the click area will become larger.

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Set horizontal padding to the PlatformView: const EdgeInsets.symmetric(horizontal: 20)

          child: Container(
            width: 300,
            height: 300,
            color: Colors.green,
            child: Padding(
              padding: const EdgeInsets.symmetric(horizontal: 20),
              child: PlatformViewLink(
                viewType: 'plugins.flutter.io/demo_platform_view',
                surfaceFactory:
                    (BuildContext context, PlatformViewController controller) {
                  return AndroidViewSurface(
                    controller: controller as AndroidViewController,
                    gestureRecognizers: _generateGestureRecognizers(),
                    hitTestBehavior: PlatformViewHitTestBehavior.opaque,
                  );
                },
                onCreatePlatformView: (PlatformViewCreationParams params) {
                  return PlatformViewsService.initSurfaceAndroidView(
                    id: params.id,
                    viewType: 'plugins.flutter.io/demo_platform_view',
                    layoutDirection: TextDirection.ltr,
                    creationParams: <String, dynamic>{},
                    creationParamsCodec: const StandardMessageCodec(),
                    onFocus: () {
                      params.onFocusChanged(true);
                    },
                  )
                    ..addOnPlatformViewCreatedListener(params.onPlatformViewCreated)
                    ..create();
                },
              ),
            ),
          ),

Change the language to "ar"
The toast will be shown when clicking the red area and the right of the red area.

Expected results
The toast should not shown when clicking the right of the red area.
Actual results
The toast will be shown when clicking the right of the red area.
Code sample
rtldemo.zip
Screenshots or Video
https://github.com/flutter/flutter/assets/95599645/77b81fe7-a101-497f-8e09-6d099cf271c6
Logs
No response
Flutter Doctor output
Doctor output
waylon@macbook-pro-m1 example % flutter doctor -v
[!] Flutter (Channel unknown, 3.3.10, on macOS 13.2 22D49 darwin-arm, locale zh-Hans-CN)
    ! Flutter version 3.3.10 on channel unknown at /Users/waylon/MyData/software/flutter
    ! Upstream repository unknown
    • Framework revision 135454af32 (5 months ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0-rc1)
    • Android SDK at /Users/waylon/Library/Android/sdk
    • Platform android-33, build-tools 32.0.0-rc1
    • ANDROID_HOME = /Users/waylon/Library/Android/sdk
    • Java binary at: /Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment Zulu11.54+23-CA (build 11.0.14+9-LTS)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] IntelliJ IDEA Ultimate Edition (version 2021.3)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Proxy Configuration
    • HTTP_PROXY is set
    • NO_PROXY is localhost,<IP_ADDRESS>,::1
    • NO_PROXY contains localhost
    • NO_PROXY contains <IP_ADDRESS>
    • NO_PROXY contains ::1

[✓] Connected device (3 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 12 (API 31) (emulator)
    • macOS (desktop)             • macos         • darwin-arm64   • macOS 13.2 22D49 darwin-arm
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 113.0.5672.126

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 2 categories.

If I change the initSurfaceAndroidView to initExpensiveAndroidView.

To sum up, there are three issues:

If we use the initSurfaceAndroidView in RTL mode, the click area will become larger.
If we use the initExpensiveAndroidView in RTL mode, the click area will become larger.
If we use the initExpensiveAndroidView in RTL mode, the layout is wrong. it should be centered not right.

Hi,
How do I set my language to "ar"?
I can't reproduce using just layoutDirection.

I was not able to reproduce this after setting the language to ar and running your demo app.

@johnmccutchan
https://github.com/flutter/flutter/assets/95599645/b3874142-ca6c-4c39-8b9d-bbf750c09fa5
Just change the device language, it can be reproduced

@Waylon-Firework I tried to reproduce again today but cannot given your instructions.
Without a way to reproduce this issue we won't be able to fix it.


In cases where the user profile cannot be fetched, or the user is unauthorized, redirect the user to the home page.

Description
In cases where the user profile cannot be extracted from the session or the user is not authorized to access a resource, redirect user to the home page.
Release notes
In cases where the user profile cannot be extracted from the session or the user is not authorized to access a resource, redirect user to the home page.
This can happen if the browser session expires (say, a tab is left open overnight).
Before this PR, we return HTTP error codes to the browser that give no information to the user. It doesn't make sense to create a guest session at this point, because the new account would not be able to access applications of a previous applicant. There is really no reasonable action we can take under these circumstances, so we redirect the user to the home page.
Checklist
General
Read the full guidelines for PRs here

[x] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release | database >
[x] Created unit and/or browser tests which fail without the change (if possible)
[x] Performed manual testing (Chrome and Firefox if it includes front-end changes)
[ ] Extended the README / documentation, if necessary

User visible changes

[ ] Followed steps to internationalize new strings
[ ] Wrote browser tests using the validateAccessibility method
[ ] Tested on mobile view. See mobile device mode
[ ] Manually tested at 200% size
[ ] Manually evaluated tab order

New Features

[ ] Add new FeatureFlag env vars to server/conf/helper/feature-flags.conf
[ ] Conditioned new functionality on a FeatureFlag
[ ] Wrote browser tests with the feature flag off and on, etc.

Issue(s) this completes
Fixes #4944

Current dependencies on/for this PR:

main

PR #5316   👈

This comment was auto-generated by Graphite.


Clean up Document Structure, add initial reflection skeleton, add heroku link to README.md

Reviewed changes -  found no issues. Merged as requested.


33 preview for video gif pdf

Maybe we should create a PreviewRepo that can be delivered via DI, can generate previews and provide them?

To me, seems like overkill for this kinda task. Are there many more places where we'll implement previews?

If we are implementing "Link to Web" resource type, then I think we will need to show a preview before adding a resource on another screen.
We can also keep a cache for the preview paths in the application lifecycle instead of looking for previews in the file system every time.

Made PreviewRepo. Not sure how much of the logic is intented to be moved to the PreviewRepo. What are your thoughts? For example, function createPdfPreview - seems like it still should stay in FileUtils.

@mdrlzy

If we are implementing "Link to Web" resource type, then I think we will need to show a preview before adding a resource on another screen.

Could you elaborate this?

I've added getMeta() method into ResourcesIndex and also modified ResourceMeta to contain type-specific data. Sorry, I had no time to implement type-specific data itself and put stubs (see //TODO: PR #33 in the code). The idea is that we have to generate metadata like video duration/resolution during indexing and save it into extra field.

Work moved to https://github.com/ARK-Builders/ARK-Navigator/pull/122


Case in organisation name

There are upper-case letters in the package org-name.
spark-shell --packages com.ibm.SparkTC:spark-netezza_2.10:0.1.1

It's the first time I've seen this so I'm not sure if it's really good practice.

FYI, the case actually matters for resolution

Thanks for reporting this issue. Good catch.  It is already published , not sure if I can fix it now.
@lresende


chore(storage-extract-image-text): rename extension

This PR renames the extension to "Image Text Extraction from Storage"

Closing as not needed


Is it possible to refer a field with quote and parse_quote?

Is it possible to refer a field with quote and parse_quote?
quote!{ #( #attrs )* #( self.vis ) }

You just opened 3 beginner question issues in quick succession. Please go to the resources shown in https://www.rust-lang.org/community instead if you need guidance learning this library. Syn is one of the most widely used crates so lots of people will have experience with it.


Load size information from DWARF debug info in COFF files and adapt to latest changes in ObjectUtils

This PR combines two commits:

Load symbols from DWARF debug info to also have size of symbols

The symbol table in COFF files does not have size information about symbols, which we need. We therefore switch to loading symbols from DWARF debug info.

Add LoadBias and GetExecutableSegmentOffset to PE/COFF object files

Symbols addresses stored in DWARF debug info in COFF files have a
preferred load address added to them (which is not used anymore). We
need to subtract this address in the same way as the load bias for ELF
files. We also add the executable segment offset ("base of code" in
PE/COFF) for PE/COFF files and move up the common methods to get this
value and the load bias into the ObjectFile class.
Bug: http://b/192067670, http://b/191948103
Tested: Unit tests, tried Orbit with PE/COFF files (hooking, sampling).

Thanks for the review and discussion @dimitry-


Replace Windows custom toolchain hack

When using a custom toolchain on Windows, Rustup ensures that the
fallback Cargo calls the correct rustc executable by hardlinking cargo
into an empty directory and executing it there. The problem with this
method is that if cargo is invoked twice at the same time, the second
invocation fails because it can't replace the hardlink which it is in use
by the first. This occurs when an integration test itself invokes cargo.
This commit replaces the hack by specifying the correct version of rustc
by setting the RUSTC environment variable when cargo is invoked. This is
set to the absolute path of rustc in the correct toolchain rather than
the rustup wrapper. This is consistent with the way rustc is invoked on
a normal toolchain on Windows.

Does this fix https://github.com/rust-lang-nursery/rustup.rs/issues/1197?
(The last time I tried, "fallback Cargo" didn't work at all, as described in that issue.)

Fallback Cargo is working for me on Windows both with and without this change.

We need this over at https://github.com/rust-lang-nursery/rust-clippy to get Appveyor green again. It would be great if someone could review this!
r? @Diggsey


LEA instruction not working

I have this string declared like the helloworld example:
hello: DB "Hello World" ; store string
Now I have just one instruction:
LEA DX, hello
it should load the address of hello string inside DX but it doesn't compile.
Errors:
Syntax Error at line 5:16 : LEA DX, hello : Unexpected Token : hello
Thank you!
PS:
Please can you implement service 0x09 (MOV AH, 0x09) with INT 0x21 ??? This way I could easly print strings like with EMU8086.

Hey, the issue is that for LEA, you need to specify word before the label, as LEA DX, word hello . One of the reasons is this emulators expects you to explicitly write what kind of data you mean (byte or word) when you use label or memory. That said, I'm not sure why this only supports word and not byte as technically the address of that label should be the same in either case :thinking:
I'll check why  it is so, but in the meantime, adding word before label should solve the issue mentioned.
As for printing strings, INT 0x10H supports printing stings to stdout, check out https://github.com/YJDoc2/8086-Emulator/blob/master/examples/hello_world.s for its use.
Hope this helps!

Thanks!


fix(client): public profile qa and infosec certification links

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

Currently the new Information Security and the Quality Assurance certificate buttons on the public profile page point to the old certification/user_name/information-security-and-quality-assurance path:

This change points them to the new URLs, certification/user_name/information-security and certification/user_name/quality-assurance.

This may be a partial fix? What about who already has the older cert?
/cc @ahmadabdolsaheb

view it on GitHub
<EMAIL_ADDRESS>From: Mrugesh Mohapatra
Date: 2020-05-29 19:23
To: freeCodeCamp/freeCodeCamp
CC: Subscribed
Subject: Re: [freeCodeCamp/freeCodeCamp] fix(client): public profile qa and infosec certification links (#38948)
This may be a partial fix? What about who already has the older cert?
/cc @ahmadabdolsaheb
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@raisedadead, those who already have the old cert will have it under Legacy Information Security and Quality Assurance. That button points to the correct certificate.


Unable to connect to RPC Endpoint that requires API key

I am able to add an RPC Header while using the rc version of the cli but it doesn't seem like it is actually using the header. I get 403 errors when trying to connect to an RPC that requires an API key.
What version are you using?
stellar 22.0.0-rc.1 (715a2008090afdc6c538a1c373d89709981181d6)
stellar-xdr 22.0.0-rc.1.1 (72e523004b5906eb1829990f9b14d2f0fa3018f0)
xdr curr (529d5176f24c73eeccfa5eba481d4e89c19b1181)
What did you do?
Add an RPC URL and RPC Header
stellar network add --rpc-url 'https://rpc-testnet.nodeswithobsrvr.co'  --network-passphrase 'Test SDF Network ; September 2015' --rpc-header 'Authorization: Api-Key 4mDhDFDFDGHhhhhhrtttttttt'  obsrvr-testnet
And then attempted to invoke a contract
stellar contract invoke --id CBO476K55KTBBS4HJB2VFVKZA6SR52RH2VRWHBPG4TZTR3OXKRELBBFW  --source stellartestnet2 --network obsrvr-testnet --very-verbose -- provision_environment --user alice2  --env_type hz25 --resources 8 --duration 10
What did you expect to see?
stellar contract invoke --id CBO476K55KTBBS4HJB2VFVKZA6SR52RH2VRWHBPG4TZTR3OXKRELBBFW  --source stellartestnet2 --network testnet -- provision_environment --user alice2  --env_type hz25 --resources 8 --duration 10
ℹ Signing transaction: 926a84a6ffda76fe46d84b387a4b46b8697c95df79081a5de7384bdddc529d56
2024-11-14T17:29:01.582055Z  INFO contract_event: soroban_cli::log::event: 1: AAAAAQAAAAAAAAABXc/5XeqmEMuHSHVS1VkHpR7qJ9VjY4Xm5PM47ddUSLAAAAABAAAAAAAAAAIAAAAPAAAACXByb3Zpc2lvbgAAAAAAAA0AAAAgRoa3LDbAcNcnZoQyHIZtjBQLFDFHJPSpDcVZxlAGnRgAAAARAAAAAQAAAAMAAAAPAAAACGVudl90eXBlAAAADwAAAARoejI1AAAADwAAAApleHBpcmF0aW9uAAAAAAAFAAAAAGc2M2gAAAAPAAAACXJlc291cmNlcwAAAAAAAAMAAAAI {"in_successful_contract_call":true,"event":{"ext":"v0","contract_id":"5dcff95deaa610cb87487552d55907a51eea27d5636385e6e4f338edd75448b0","type_":"contract","body":{"v0":{"topics":[{"symbol":"provision"},{"bytes":"4686b72c36c070d7276684321c866d8c140b14314724f4a90dc559c650069d18"}],"data":{"map":[{"key":{"symbol":"env_type"},"val":{"symbol":"hz25"}},{"key":{"symbol":"expiration"},"val":{"u64":1731605352}},{"key":{"symbol":"resources"},"val":{"u32":8}}]}}}}}
"4686b72c36c070d7276684321c866d8c140b14314724f4a90dc559c650069d18"

What did you see instead?
I received a 403 error
2024-11-14T17:24:42.232241Z DEBUG soroban_cli::upgrade_check: start upgrade check
2024-11-14T17:24:42.232345Z TRACE soroban_cli::commands::contract::invoke: network=Network { rpc_url: "https://rpc-testnet.nodeswithobsrvr.co", rpc_headers: [("Authorization", "Api-Key 4mDhDFDFDGHhhhhhrtttttttt")], network_passphrase: "Test SDF Network ; September 2015" }
2024-11-14T17:24:42.232371Z DEBUG soroban_cli::upgrade_check: finished upgrade check
2024-11-14T17:24:43.898052Z TRACE soroban_cli::get_spec: network=Network { rpc_url: "https://rpc-testnet.nodeswithobsrvr.co", rpc_headers: [("Authorization", "Api-Key 4mDhDFDFDGHhhhhhrtttttttt")], network_passphrase: "Test SDF Network ; September 2015" }
❌ error: Networking or low-level protocol error: Server returned an error status code: 403

Using httpie works fine
http POST https://rpc-testnet.nodeswithobsrvr.co 'Authorization: Api-Key 4mDhDFDFDGHhhhhhrtttttttt' jsonrpc="2.0" id:=1 method="getLatestLedger"
{
    "id": 1,
    "jsonrpc": "2.0",
    "result": {
        "id": "fbacaeb65d94773da05213375c83c82caeabfac14463e864acc86c9e9e0ef3ec",
        "protocolVersion": 22,
        "sequence": 955485
    }
}

Thanks for reporting this, @tmosleyIII ! There is an open PR that should fix this issue: https://github.com/stellar/stellar-cli/pull/1799
Also, when testing this out, I noticed that when calling the getHealth method for testnet, I was getting an error. Not sure if this is an issue with the request I sent, or maybe there is an update that is needed to the testnet node after testnet was reset last week.
curl -X POST 'https://rpc-testnet.nodeswithobsrvr.co' \
--header 'Content-Type: application/json' \
--header 'Authorization: Api-Key <my-api-key>' \
--data '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getHealth"
Health
{"jsonrpc":"2.0","id":1,"error":{"code":-32603,"message":"[-32603] latency (215h7m22s) since last known ledger closed is too high (\u003e30s)"}}%

Thanks for reporting this, @tmosleyIII ! There is an open PR that should fix this issue: https://github.com/stellar/stellar-cli/pull/1799
Also, when testing this out, I noticed that when calling the getHealth method for testnet, I was getting an error. Not sure if this is an issue with the request I sent, or maybe there is an update that is needed to the testnet node after testnet was reset last week.
curl -X POST 'https://rpc-testnet.nodeswithobsrvr.co' \
--header 'Content-Type: application/json' \
--header 'Authorization: Api-Key <my-api-key>' \
--data '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getHealth"
Health
{"jsonrpc":"2.0","id":1,"error":{"code":-32603,"message":"[-32603] latency (215h7m22s) since last known ledger closed is too high (\u003e30s)"}}%

That's great news.
I'll look into that error and get it fixed up.


Support Logger for debug log messages

I love the support for debugging in GLContext. The setupDebugMessageCallback() method is super convenient.
While building up the debugging support in my own project I thought of something that would make the logging support even better.
Please consider adding a method that sends debug messages to a java.util.logging.Logger rather than a PrintStream. This would help lwjgl users easily tie GL debug messages in to application logs and enable the output during runtime.
To take this idea a bit further, the holy grail would be swapping in slf4j loggers for log output throughout the lwjgl library. That might take a bit more time to implement though so feel free to consider slf4j a low priority nice to have.
java.util Loggers are already on hand and slf4j can remap their output so that might be the best option if adding the slf4j dependency is undesirable.
Thanks again for all the great work! The new version is looking really good!

I will wait for input from other users before doing anything. But I don't think having a dependency on slf4j would be a good idea (for LWJGL users, I personally don't mind).

Personally, I would like to have more control over the formatting of the generated messages.
And this would usually be done with a common callback interface that the user can set.
Having had a look into the relevant code in LWJGL 3 the problem seems, though, that the callback interface and the actual formatting of the messages are intertwined because both depend on the underlying native extension/GL core function being used, which have differing signatures and provided information.
The only thing I can think of right now is a common interface which is the union of the information provided by all different underlying callbacks.
This way the user can adapt any logging library he/she wants to use, without introducing a dependency into LWJGL 3.

Well, setupDebugMessageCallback is a "reference implementation" really. It is almost too complex for LWJGL, which is supposed to be super lightweight and not provide high-level abstractions. The only reason it's there is because it's so damn useful. My experience so far has been that many users simply ignore that the modern debug mechanisms exist and go through the pain of good old glGetError.

It is almost too complex for LWJGL ...

Yes, it almost feels like a "utility" method. But there is a pattern to observe: The more something becomes "utility" the more people demand for it and the more useful it becomes.
See for example the math classes. :)

... and go through the pain of good old glGetError

That's a pitty. But glGetError of course has its use. I once used a very old Intel card with a GL 2.0-only driver, that had neither of these debugging extensions. But of course, I wouldn't develop and debug on that, but glGetError was still necessary to catch errors only occurring there.

Yes, it almost feels like a "utility" method. But there is a pattern to observe: The more something becomes "utility" the more people demand for it and the more useful it becomes.
See for example the math classes. :)

Of course, but there's nothing bad about making standalone libraries out of specialized utility functionality. JOML is a perfect example of that.
By adding this method to LWJGL, trying to be helpful, I have created more work for myself. Someone asks for Logger/slf4j integration. Then someone else asks for a high-level callback. Who knows what comes next... You cannot keep everyone happy and the only way to satisfy a request is by making the library opinionated, which LWJGL doesn't want to be.
The raw functionality is there, it's simple and publicly available, anyone could roll their own implementation. This is even the primary reason LWJGL 3 exists and the whole point of writing it from scratch.

I agree with you on all points there. I was actually never in favor of having "utility" things in LWJGL itself, just mentioned that those things are useful. :)
LWJGL is fine as it is and that particular utility method shouldn't be there in the first place.
And yes, clients should roll their own utilities on top of what LWJGL provides as low-level library.
It's just that most clients probably woudn't know how to do that properly, or even that the GL debugging extensions exist. That's probably why that utility method is in GLContext.

Personally I would like to be able to customize log message format by having LWJGL using SLF4J.
I am using SLF4J in my project so that would make it very easy to me.

I'm currently experimenting with how to address this issue:

Any time LWJGL prints debug information or non-fatal errors, it uses a PrintStream instance in LWJGLUtil.
That instance defaults to System.err.
It can be overridden with a system property (that specifies a factory class that returns a PrintStream instance).

Using the above, I'm able to create a PrintStream implementation that forwards everything to a logger or whatever. Any comments?

I think that sounds workable. My only reservation is that it may be duplicating functionality already provided by java.util.logging.Logger.
If LWJGLUtil.log(CharSequence) could switch to a Logger based on a system property that might cover it without duplication.

My only reservation is that it may be duplicating functionality already provided by java.util.logging.Logger.
If LWJGLUtil.log(CharSequence) could switch to a Logger based on a system property that might cover it without duplication.

I wanted to avoid such a solution because SLF4J users would then be forced to use the jul-to-slf4j bridge.
LWJGL now supports (in build 3.0.0b build 37) programmatic configuration with the org.lwjgl.system.Configuration class. It can be used to setup forwarding to any logger with:
Configuration.DEBUG.set(true);
Configuration.setDebugStreamConsumer(new DebugStreamConsumer() {
	@Override
	public void accept(String message) {
		Logger.getLogger("MyLogger").info(message);
	}
});

I believe that's easy enough and avoids any dependencies to j.u.l.Logger or any other logging framework.

@Spasi this haven't been released to the maven release 3.1? or changed since there?

Yes, setDebugStreamConsumer has been removed. Its implementation was complicated and its usefulness questionable.
You can still use Configuration.DEBUG_STREAM to forward messages to a custom logging solution.


Adding missing feature descriptions - Batch 4

One comment left to resolve, but then the PR should be about ready to merge.


Add python bindings

Adding python bindings for the replication API
Adding a new ReplicatorConfiguration and Replicator python class
Fixing code in include/cbl/CBLDatabase.h, src/CBL.exp and  src/CBLDatabase.cc that was causing compilation errors when building the python bindings.

This has grown stale.  I will close it in one week if there is no update.


Doesn't support stylers

I wanted A plastic code wrap styler and this but it jus gets wierd with it. Can u add a features

Oh thanks for pointing that out, I'll look into this! I definitely didn't do this UDL to the same standards as the others, I might as well  read up on how I can get the background to just match the editor's existing style.

Oh thanks for pointing that out, I'll look into this! I definitely didn't do this UDL to the same standards as the others, I might as well read up on how I can get the background to just match the editor's existing style.

Ok thanks for responding and I would love to see if it can work. If it can't then I will be sad and btw it works with far mode plugin.

So it does support stylers but the background wasn't set to transparent, thanks for pointing that out. I'll next try to get the basic text and comments to match the theme colour if one is set.

Ok

Thnx

@CybearTron Did you get this working with stylers in the end now that it's been updated? Just checking so I can close.

Oh I had forgotten to check it again! I will check it when I get time 🙂 cuz I am not on the pc rn


Consider adding a Target counterpart for CallNode

It seems to me reasonable (at least for the sake of consistency) to have a target node for a method call, e.g. CallTargetNode.
It would be helpful to differentiate (without checking the context) a simple method call from a synthetic call node that is missing the last argument (that will be assigned in runtime). Such a target call node might be present in the rescue operator and multi-assignment and could be either attribute assignment (a.foo, b = []) or reference assignment (a[:foo], b = []).
Does it make sense?

Right, this seems a perfect fit given the other *TargetNode used in such a case.

Okay, let's do this one.


Quick patch bootstrax

Solve these kind of issues:
Traceback (most recent call last):
  File "/home/xedaq/miniconda/envs/py37/bin/bootstrax", line 7, in <module>
    exec(compile(f.read(), __file__, 'exec'))
  File "/home/xedaq/software/straxen/bin/bootstrax", line 1464, in <module>
    main()
  File "/home/xedaq/software/straxen/bin/bootstrax", line 326, in main
    main_loop()
  File "/home/xedaq/software/straxen/bin/bootstrax", line 388, in main_loop
    process_run(rd)
  File "/home/xedaq/software/straxen/bin/bootstrax", line 1271, in process_run
    min([x.get('first_time', float('inf')) for x in md['chunks']])) / 1e9)
OverflowError: cannot convert float infinity to integer

By accident was on wrong branch while drafting


why my input type="text" broken?

Very strange bug.
Demo - http://normal-minute.surge.sh/
Recreate:

Go to Page One. Username input is ok
Refresh page. Username input is broken, nuxt take of type="text" attribute.

What the hack is that?
The worst part - this bug appears only after npm run generate, so it is IMPOSSIBLE to trace in development.
Is it because I import this Form from my Form.vue Component to Page One? How to use Components without this bugs? I have the same issue with Google Map few days ago. There was not working when I use them as Components, but work when I just insert Map directly in page. What I can use as components and what I can't?

hi ,
that because html-minify setting .
you can try on this site ( nuxt.js used )
https://kangax.github.io/html-minifier/
type="text" will be remove .
because default that is not necessary .
you can ..
option 1 .
defined your css with class
option 2 .
override html-minify setting , escape remove type="text"

@ausir0726 thank you! That's make sense.

@ausir0726 as for option 2. Can I override just type="text" without disabling whole html minify?

And where should I edit minify: {}? In nuxt.config.js?

@kodekrendel
maybe try disabled some minify setting will be better ?
I don't know it can be disable all option . usually I don't have these issue 😆
in nuxt.config.js add
module.exports = {
  // add this generate object
  generate : {
    minify : {
       //options in here
    }
  },
  // same as old file
  // ... bula bula ...
}

As for form after google map , I can't answer you .

@ausir0726 thanks a lot! That's solve my issue
  generate: {
    minify: {
      removeRedundantAttributes: false
    }
  }


Private IP frontend support

We are in need of creating an end point which is accessibly only internally.
If we move the associated listeners it automatically creates to the Private IP Address, it momentarily works as expected until kubernetes automatically re-applies the config to the public IP.

@richardcatania were do you mean to say that initially the Application Gateway v2 had a public IP, and when you move it to a private IP the ingress controller overrode that config with the public IP?

What I meant was that if we configure the Associated Listeners to the Private from the Azure Portal, Kubernetes will move them back to Public. Please have a look at the screen shot below so you can see a clearer picture of what I am trying to explain:
https://pasteboard.co/HSJKHZh.png

Does this support ILB App Gateway deployment at all?

I've got the same question.  The docs seem to indicate that this only works with a Standard V2 application gateway.  However, V2 gateways apparently require you to have a public IP address.
Our security requirements prevent us from serving up on public IPs.  We've used Standard gateways with private IPs only (with backend pools of VMs) + internal DNS to meet our requirements, but now we're prototyping AKS and wanting to leverage the App Gateway/Ingress Controller, but it appears we won't be able to.
Can standard gateways be used? Or is there another workaround for this?

@richardcatania @benrj As of release v0.7.0,  appGW v2 now supports a private ip config.

@benrj current recommendation is attach a Network Security Group to AppGW Subnet blocking anything but management ports.


vector: intermittent stroke on vector.CubicTo()

Ebitengine Version
v2.5.0-alpha.12
Operating System

[X] Windows
[X] macOS
[X] Linux
[ ] FreeBSD
[ ] OpenBSD
[ ] Android
[ ] iOS
[ ] Nintendo Switch
[ ] Xbox
[ ] Web Browsers

Go Version (go version)
1.20
What steps will reproduce the problem?
Example:
package main

import (
	"image"
	"image/color"
	"log"
	"math"

	"github.com/hajimehoshi/ebiten/v2"
	"github.com/hajimehoshi/ebiten/v2/vector"
)

func main() {
	ebiten.SetWindowResizingMode(ebiten.WindowResizingModeEnabled)
	if err := ebiten.RunGame(NewGame()); err != nil {
		log.Fatal(err)
	}
}

type Game struct {
	Empty *ebiten.Image
}

func NewGame() *Game {
	return &Game{Empty: Empty()}
}

func (g *Game) Update() error {
	return nil
}

func (g *Game) Draw(screen *ebiten.Image) {
	sw, sh := screen.Bounds().Dx(), screen.Bounds().Dy()
	size := int(math.Min(float64(sw), float64(sh)) * 0.2)
	bounds := image.Rect(sw/2, sh/2, sw/2, sh/2).Inset(-size)
	var path vector.Path
	path.MoveTo(float32(bounds.Min.X), float32(bounds.Min.Y))
	path.CubicTo(
		float32(bounds.Min.X),
		float32(bounds.Max.Y),
		float32(bounds.Max.X),
		float32(bounds.Min.Y),
		float32(bounds.Max.X),
		float32(bounds.Max.Y),
	)
	g.DrawPath(screen, path, 15, color.White)
	vector.StrokeRect(
		screen,
		float32(bounds.Min.X),
		float32(bounds.Min.Y),
		float32(bounds.Dx()),
		float32(bounds.Dy()),
		2,
		color.White,
	)
}

func (g *Game) Layout(w, h int) (int, int) {
	return w, h
}

func (g *Game) DrawPath(screen *ebiten.Image, path vector.Path, stroke int, color color.Color) {
	op := &ebiten.DrawTrianglesOptions{
		FillRule:  ebiten.EvenOdd,
		Filter:    ebiten.FilterLinear,
		AntiAlias: true,
	}
	strokeOp := &vector.StrokeOptions{}
	strokeOp.Width = float32(stroke)
	strokeOp.LineCap = vector.LineCapRound
	vs, is := path.AppendVerticesAndIndicesForStroke(nil, nil, strokeOp)
	cr, cg, cb, ca := color.RGBA()
	for i := range vs {
		vs[i].SrcX = 1
		vs[i].SrcY = 1
		vs[i].ColorR = float32(cr) / float32(0xffff)
		vs[i].ColorG = float32(cg) / float32(0xffff)
		vs[i].ColorB = float32(cb) / float32(0xffff)
		vs[i].ColorA = float32(ca) / float32(0xffff)
	}
	screen.DrawTriangles(vs, is, g.Empty, op)
}

func Empty() *ebiten.Image {
	emptyImage := ebiten.NewImage(3, 3)
	emptyImage.Fill(color.White)
	return emptyImage.SubImage(image.Rect(1, 1, 2, 2)).(*ebiten.Image)
}

What is the expected result?
Continuous stroke.
What happens instead?

Anything else you feel useful to add?
No response

Also, when parts of the curve are superimposed on each other, there is an overlap like xor.

Looks like ebiten.DrawTrianglesOptions.FillRule = ebiten.FillAll resolves it.
But it still shouldn't behave like this with EvenOdd right?

<EMAIL_ADDRESS>
The returned values are intended to be passed to DrawTriangles or DrawTrianglesShader with a solid (non-transparent) color with the FillAll fill rule (not the EvenOdd fill rule).

So this is working as intended. I have a plan to support transparent colors btw.


Wrong cache client path

Describe the bug
SSR case with client folder in root project folder.
I changed cache folder with cacheDir using defineConfig (cacheDir: '.cache\.vite').
Actual cache folder is C:\<PROJECT_PATH>\client\.cache\.vite.
Expected cache folder is C:\<PROJECT_PATH>\.cache\.vite.
Reproduction
TODO
Steps to reproduce
vite.config.js
import { join } from 'node:path'
import { defineConfig } from 'vite'
import viteSolid from 'vite-plugin-solid'

const root = join(process.cwd(), 'client')
// C:\<PROJECT_PATH>\client

const plugins = [
  viteSolid({ ssr: true }),
]

const ssr = {
  noExternal: ['@solidjs/router'],
}

export default defineConfig({
  cacheDir: '.cache/.vite',
  root,
  plugins,
  ssr
})

System Info
OS: Windows
Node: 16.17.0
Yarn: 4.0.0-rc.39

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This is as expected since you changed the  root config.
Try cacheDir: join(process.cwd(), '.cache/.vite')


X-T2 fix

fixed wrong app version error on X-T2 (issue #2)

Did a quick test with X-T10, works fine. Thanks!


[enhancement] An option to require the Ember Bore to be placed above a certain block to function

From what I understand, the Ember Bore currently functions only depending on dimension and y level. I believe another useful option to have would be to whitelist/blacklist blocks as well, and require the machine to have contact with them to extract Ember.

Should be quite easy to implement. I'll try to implement it this evening. I'll let you know how things are going.

v1.25.1 should be on curseforge.


SAK-29819 We don't need svn files in git.

The toplevel .gitignore should catch all these things now.

+1


RF: nwb.json => dandiset_metanwb.json

Initially I had missed the fact that it is not the schema we impose on top
of nwb, but rather a schema for dandiset.yaml fields which are derived from
metadata we find in nwb files.  As it is not directly the information from
nwb, I decided to call it metanwb.
I left variable NWB_SCHEMA as is since it seems that UI is anyways dandiset specific, but can change that one to METANWB_SCHEMA for clearer correspondence. Let me know
This is a follow up to previous renamings in bdf09cfed3d76a7dc73de7bcf82bdd28f984c9f2

don't you merge master branch into it once in a while?  or you mean that you have some additional code relying on that path, thus merging wouldn't be enough?

The differences between master and refactor are so substantial that I'm afraid this might be lost in the shuffle of a typical merge if we don't look out for it.

ah, ok... then I will keep that in mind, and try to not bother with little and not that important changes for now.

@yarikoptic You can certainly still make any PRs, but it's probably better to make them against refactor, instead of master for the very near term.

@yarikoptic I've actually just rewritten this branch (keeping you as the Git author) to be based on and merged into refactor.


Leaflet custom projection transform issue with leaflet 0.7.2

Example http://test0.127.ru worked fine with leaflet 0.6.* and fails to work correctly with 0.7.2
Looks like the latest proj4leaflet version fails to transform coords correctly. The example I've written, should be centered by Moscow center and now it is set much more southward.
Custom projection I use is
var PGCRS = new L.Proj.CRS.TMS(
    'EPSG:3395',
    '+proj=merc +lon_0=0 +k=1 +x_0=0 +y_0=0 +ellps=WGS84 +datum=WGS84 +units=m +no_defs',
    [-20037508.343, -19930481.933, 20037508.343, 20144534.753],
    {
        resolutions: [
            null,
            78271.51696484375,
            39135.758482421875,
            19567.8792412109375,
            9783.93962060546875,
            4891.969810302734375,
            2445.9849051513671875,
            1222.99245257568359375,
<PHONE_NUMBER>87841796875,
<PHONE_NUMBER>439208984375,
<PHONE_NUMBER>7196044921875,
            76.437028285980224609375,
            38.2185141429901123046875,
            19.10925707149505615234375,
            9.554628535747528076171875,
            4.7773142678737640380859375,
            2.388657133934688201904296875,
            1.194328566968441009521484375
        ]
    }
);

map init
map = L.map( $('.b-map')[0], {crs: PGCRS, minZoom: 1, maxZoom: 17}).setView([55.75, 37.67], 9),

tiles are set up like that
function balance (tile) {
    var h = 9, s;
    if (tile.s == 'a') s = 1;
    if (tile.s == 'b') s = 2;
    if (tile.s == 'c') s = 3;
    return s;
}

function tile (tile){
    return (tile.z +'00'+<PHONE_NUMBER> + tile.x).toString().substr(1)
           +<PHONE_NUMBER> + tile.y).toString().substr(1)).
           replace(/^(\d{1,2})00(\d{3})(\d{3})(\d{3})(\d{3})(\d{3})(\d{3})/, '$1/00/$2/$3/$4/$5/$6/$7');
}

L.tileLayer('http://h0{front}.tiles.tmcrussia.com/map/lv{path}.png', {
    front: balance,
    path: tile,
    attribution: '© CDCOM',
    tms: true
}).addTo(map);

Closing this as too old to act. Please open a new issue with example code if there are similar problems with latest Proj4Leaflet and/or Leaflet.


[kubernetes] Data published in tenants other than admin are being discarded

creation of another tenant:

[10/10/19 - 20:24:44] |RelationshipController| INFO: user bete added to group admin by admin
[10/10/19 - 20:24:44] |CRUDController| DEBUG: ... user profile was configured.
[10/10/19 - 20:24:44] |CRUDController| DEBUG: Configuring user password...
[10/10/19 - 20:24:44] |CRUDController| DEBUG: ... user password was configured.
[10/10/19 - 20:24:44] |CRUDController| DEBUG: Sending tenant creation message to other components...
[10/10/19 - 20:24:44] |CRUDController| INFO: Will emit tenant lifecycle event teste - CREATE
[10/10/19 - 20:24:44] |CRUDController| DEBUG: ... tenant creation message was sent.
[10/10/19 - 20:24:44] |webRoutes| DEBUG: ... user data was inserted into the database.
[10/10/19 - 20:24:44] |webRoutes| DEBUG: ... new user was created.

login of new user:

[10/10/19 - 20:28:43] |AuthenticationController| INFO: user bete loged in

template creation:

[10/10/19 - 20:31:14] |TemplateHandler| DEBUG:  Created template in database
[10/10/19 - 20:31:14] |TemplateHandler| INFO: Creating a new template
[10/10/19 - 20:31:14] |TemplateHandler| DEBUG: Retrieving templates.
[10/10/19 - 20:31:14] |TemplateHandler| DEBUG: Initializing tenant context...
[10/10/19 - 20:31:14] |TemplateHandler| DEBUG: ... tenant context initialized.
[10/10/19 - 20:31:14] |TemplateHandler| DEBUG: Pagination configuration is {'page': 1, 'per_page': 6, 'error_out': False}
[10/10/19 - 20:31:14] |TemplateHandler| DEBUG: Sortby filter is DeviceTemplate.label
[10/10/19 - 20:31:14] |TemplateHandler| DEBUG:  Querying templates sorted by DeviceTemplate.label
[10/10/19 - 20:31:14] |TemplateHandler| DEBUG: Adding resulting template to response...
[10/10/19 - 20:31:14] |TemplateHandler| DEBUG: Template is: t
[10/10/19 - 20:31:14] |TemplateHandler| DEBUG: ... template was added to response.
[10/10/19 - 20:31:14] |TemplateHandler| DEBUG: Full response is {'pagination': {'page': 1, 'total': 1, 'has_next': False, 'next_page': None}, 'templates': [{'data_attrs': [{'type': 'dynamic', 'template_id': '1', 'static_value': '', 'value_type': 'integer', 'id': 1, 'created': '2019-10-10T20:31:14.732037+00:00', 'label': 'int'}], 'attrs': [{'type': 'dynamic', 'template_id': '1', 'static_value': '', 'value_type': 'integer', 'id': 1, 'created': '2019-10-10T20:31:14.732037+00:00', 'label': 'int'}], 'config_attrs': [], 'id': 1, 'created': '2019-10-10T20:31:14.728404+00:00', 'label': 't'}]}
[10/10/19 - 20:31:14] |TemplateHandler| INFO:  Getting template with id 1

device creation:

[10/10/19 - 20:32:34] |DeviceHandler| DEBUG:  Generated a new device id 48f63c
[10/10/19 - 20:32:34] |DeviceHandler| DEBUG:  Adding new template list for device <Device(label='d')>
[10/10/19 - 20:32:34] |BackendHandler| INFO:  Publishing create event to Kafka
[10/10/19 - 20:32:34] |KafkaNotifier| DEBUG:  topic for dojot.device-manager.device is adf0f9e1-a369-4ace-ade6-5f7e7161cbc3
[10/10/19 - 20:32:34] |DeviceHandler| INFO:  Creating a new device with id 48f63c.

publication in the teste tenant: Message is being discarded!

mosquitto_pub -h <IP_ADDRESS> -p 30002 -t /teste/48f63c/attrs -m '{"int":5}'

<20:35:30 10/10/2019> -- DEBUG: Authenticating MQTT client
{"pid":8,"hostname":"iotagent-mosca-94f84568-xkfb6","name":"MoscaServer","level":30,"time":1570739730518,"msg":"client connected","client":"mosqpub|9017-dojot-mast","v":1}
<20:35:30 10/10/2019> -- INFO: client up
<20:35:30 10/10/2019> -- DEBUG: Authorizing MQTT client mosqpub|9017-dojot-mast to publish to /teste/48f63c/attrs
{"pid":8,"hostname":"iotagent-mosca-94f84568-xkfb6","name":"MoscaServer","level":30,"time":1570739730526,"msg":"closed","client":"mosqpub|9017-dojot-mast","v":1}
<20:35:30 10/10/2019> -- INFO: client down
<20:35:30 10/10/2019> -- |iotagent -- INFO: Getting device from http://device-manager:5000/device/48f63c
<20:35:30 10/10/2019> -- INFO: Parameters are: url: http://device-manager:5000/device/48f63c, headers: { authorization: 'Bearer and0IHNjaGVtYQ==.eyJzZXJ2aWNlIjoidGVzdGUiLCJ1c2VybmFtZSI6ImlvdGFnZW50LW1xdHQifQ==.ZHVtbXkgc2lnbmF0dXJl' }, method: get, TAG
<20:35:30 10/10/2019> -- DEBUG: Got device {"attrs":{"1":[{"created":"2019-10-10T20:31:14.732037+00:00","id":1,"is_static_overridden":false,"label":"int","static_value":"","template_id":"1","type":"dynamic","value_type":"integer"}]},"created":"2019-10-10T20:32:34.083251+00:00","id":"48f63c","label":"d","templates":[1]}
<20:35:30 10/10/2019> -- DEBUG: Expected topic is /teste/48f63c/attrs
<20:35:30 10/10/2019> -- DEBUG: Device published on topic /teste/48f63c/attrs
<20:35:30 10/10/2019> -- DEBUG: Authorized client mosqpub|9017-dojot-mast to publish to topic /teste/48f63c/attrs
<20:35:30 10/10/2019> -- DEBUG: Published data: {"int":5}, client: mosqpub|9017-dojot-mast, topic: /teste/48f63c/attrs
<20:35:30 10/10/2019> -- |messenger -- DEBUG: Trying to publish someting. Current producer topics are { 'device-data': { admin: '7b94733a-1733-4b6d-9a06-461d43252d1d' } }
<20:35:30 10/10/2019> -- |messenger -- WARN: No producer was created for subject device-data@teste. Maybe this tenant doesn't exist?
<20:35:30 10/10/2019> -- |messenger -- WARN: Message {"metadata":{"deviceid":"48f63c","tenant":"teste","timestamp":1570739730573},"attrs":{"int":5}} is being discarded!

publication in the admin tenant: Published data

<20:38:10 10/10/2019> -- DEBUG: Authenticating MQTT client
{"pid":8,"hostname":"iotagent-mosca-94f84568-xkfb6","name":"MoscaServer","level":30,"time":1570739890265,"msg":"client connected","client":"mosqpub|11475-dojot-mas","v":1}
<20:38:10 10/10/2019> -- INFO: client up
<20:38:10 10/10/2019> -- DEBUG: Authorizing MQTT client mosqpub|11475-dojot-mas to publish to /admin/ff6fcb/attrs
{"pid":8,"hostname":"iotagent-mosca-94f84568-xkfb6","name":"MoscaServer","level":30,"time":1570739890267,"msg":"closed","client":"mosqpub|11475-dojot-mas","v":1}
<20:38:10 10/10/2019> -- INFO: client down
<20:38:10 10/10/2019> -- |iotagent -- INFO: Getting device from http://device-manager:5000/device/ff6fcb
<20:38:10 10/10/2019> -- INFO: Parameters are: url: http://device-manager:5000/device/ff6fcb, headers: { authorization: 'Bearer and0IHNjaGVtYQ==.eyJzZXJ2aWNlIjoiYWRtaW4iLCJ1c2VybmFtZSI6ImlvdGFnZW50LW1xdHQifQ==.ZHVtbXkgc2lnbmF0dXJl' }, method: get, TAG
<20:38:10 10/10/2019> -- DEBUG: Got device {"attrs":{"1":[{"created":"2019-10-10T20:36:48.689582+00:00","id":1,"is_static_overridden":false,"label":"int","static_value":"","template_id":"1","type":"dynamic","value_type":"integer"}]},"created":"2019-10-10T20:36:58.698862+00:00","id":"ff6fcb","label":"device","templates":[1]}
<20:38:10 10/10/2019> -- DEBUG: Expected topic is /admin/ff6fcb/attrs
<20:38:10 10/10/2019> -- DEBUG: Device published on topic /admin/ff6fcb/attrs
<20:38:10 10/10/2019> -- DEBUG: Authorized client mosqpub|11475-dojot-mas to publish to topic /admin/ff6fcb/attrs
<20:38:10 10/10/2019> -- DEBUG: Published data: {"int":5}, client: mosqpub|11475-dojot-mas, topic: /admin/ff6fcb/attrs
<20:38:10 10/10/2019> -- |messenger -- DEBUG: Trying to publish someting. Current producer topics are { 'device-data': { admin: '7b94733a-1733-4b6d-9a06-461d43252d1d' } }

Affected version: v0.4.0

Issue resolved with KAFKA_HOSTS environment variable correction (related with #1273).

There is a problem with Auth's initialization. If the KafkaPublisher initialization fails, the webserver continues, in this way the service becomes a zombie, once it cannot work properly.

Test OK.
If there is a problem with the communication between Auth and Kafka, Auth tries again to communicate with Kafka.

iotagent-mosca:
<19:12:56 26/11/2019> -- DEBUG: Authenticating MQTT client
{"pid":7,"hostname":"iotagent-mosca-8df9f9656-kz7w8","name":"MoscaServer","level":30,"time":1574795576649,"msg":"client connected","client":"mosqpub|22971-efaber-Op","v":1}
<19:12:56 26/11/2019> -- INFO: client up
<19:12:56 26/11/2019> -- DEBUG: Authorizing MQTT client mosqpub|22971-efaber-Op to publish to /cpqd/1e3b0/attrs
{"pid":7,"hostname":"iotagent-mosca-8df9f9656-kz7w8","name":"MoscaServer","level":30,"time":1574795576662,"msg":"closed","client":"mosqpub|22971-efaber-Op","v":1}
<19:12:56 26/11/2019> -- INFO: client down
<19:12:56 26/11/2019> -- |iotagent -- INFO: Getting device from http://device-manager:5000/device/1e3b0
<19:12:56 26/11/2019> -- INFO: Parameters are: url: http://device-manager:5000/device/1e3b0, headers: { authorization: 'Bearer and0IHNjaGVtYQ==.eyJzZXJ2aWNlIjoiY3BxZCIsInVzZXJuYW1lIjoiaW90YWdlbnQtbXF0dCJ9.ZHVtbXkgc2lnbmF0dXJl' }, method: get, TAG
<19:12:56 26/11/2019> -- DEBUG: Got device {"attrs":{"1":[{"created":"2019-11-26T18:38:31.080244+00:00","id":1,"is_static_overridden":false,"label":"int","static_value":"","template_id":"1","type":"dynamic","value_type":"integer"}]},"created":"2019-11-26T18:38:41.114422+00:00","id":"1e3b0","label":"device","templates":[1]}
<19:12:56 26/11/2019> -- DEBUG: Expected topic is /cpqd/1e3b0/attrs
<19:12:56 26/11/2019> -- DEBUG: Device published on topic /cpqd/1e3b0/attrs
<19:12:56 26/11/2019> -- DEBUG: Authorized client mosqpub|22971-efaber-Op to publish to topic /cpqd/1e3b0/attrs
<19:12:56 26/11/2019> -- DEBUG: Published data: {"int":1}, client: mosqpub|22971-efaber-Op, topic: /cpqd/1e3b0/attrs
<19:12:56 26/11/2019> -- |messenger -- DEBUG: Trying to publish someting. Current producer topics are { 'device-data':
   { admin: 'c00e1bcd-426b-43dc-ad4c-b92e72f214dc',
     cpqd: '62fe20c0-a1be-4925-be67-83c20b19baed' } }

persister:
[26/11/19 - 19:12:58] |messenger| INFO: Emitting new event message for subject device-data@cpqd
[26/11/19 - 19:12:58] |persister| INFO: Received data: {'metadata': {'deviceid': '1e3b0', 'tenant': 'cpqd', 'timestamp':<PHONE_NUMBER>733}, 'attrs': {'int': 1}}
[26/11/19 - 19:12:58] |persister| DEBUG: got data event b'{"metadata":{"deviceid":"1e3b0","tenant":"cpqd","timestamp":1574795576733},"attrs":{"int":1}}'

Tested in version: v0.4.1_rc2


footer template doesn't handle changed feed config of new 0.19.0 version of Zola

Bug Report
The new 0.19 version of Zola breaks addition of feed icon in templates/partials/footer.html.
Environment
Zola version: 0.19.0
tabi version or commit: 2.10
Expected Behavior
A feed icon is present in the footer.
Current Behavior
Due to testing for variables that no longer exist, no feed icon is generated in the footer. I was also actually getting errors from zola serve related to this, but now I don't seem to be able to reproduce that.
Also it seems there can be multiple feeds now (atom and rss at the same time) so it's unclear what changes would need to be made to this template.
Step to Reproduce
After upgrading Zola to 0.19.0 it forces me to change generate_feed to generate_feeds and feed_filename = "atom.xml" to feed_filenames = ["atom.xml"] (I understand there could also be an rss.xml in there, to generate both).
Now serving or building the site results in there being no feed icon because of this test and this test in templates/partials/footer.html which are now testing unset variables.
I can make it work again by doing this:
{%- if (config.generate_feeds or config.generate_feed) and config.extra.feed_icon -%}

but I don't know what should be done about the possibility of there being multiple feed_filenames now.
The 0.19.0 release of Zola is forcing me to make those config key renames so even if I am happy with a single feed I can't avoid the change. Perhaps that is a bug in Zola also.

Thanks for the report.
I am working on making tabi 0.19.0 ready. Development is happening on branch 0.19.x.
My goal is to make tabi 0.19.0 compatible while not breaking anything for 0.18.0 users. I've just pushed a commit that should achieve this for the feed icon.
For now, I'm just linking the first feed in feed_filenames. I think a better solution would be to:

add an extra option so users can set which icons to show
add new icons for atom and rss. the current one is generic
show icons as per the user's configuration

If you could give that branch a try and let me know of any issues, I'd really appreciate it.

If you could give that branch a try and let me know of any issues, I'd really appreciate it.

Thanks, I am now doing that and footer work as expected with config.toml:
generate_feeds = true
feed_filenames = ["atom.xml"]

Thanks for testing! I've merged the branch.


Getting client.py to 100% coverage.

In particular:

step1_get_device_and_user_codes
step2_exchange with device info
Making explicit the code= argument in calls to
step2_exchange in tests
flow_from_clientsecrets branches with revoke and
device URI optional args

NOTE: Has #485 as diffbase.

Woo hoo 100%!

LGTM.

Looks great; merge.

Gonna merge this one, which will auto-merge #485.


Api to get all configurations

This PR fetch's all the configurations configured for the subscription.

Needs to bump Nuget package version


decide which font to be used

I'm still hesitating about the font to be used.
Current setup:

Dosis for headings
Lato for other texts

Perhaps it's not so bad, finally.
P.S. Nice font I noticed recently: Myriad pro.

@blueclock your opinion, please?
Let's try to take a decision quickly for this one.

Chosen fonts:

headings in Raleway
texts in Roboto


Fixes #1605

I'll trust that this has no side-effects or at least these are tested in other portions of the code. The change looks straightforward but far-reaching perhaps.

Though it looks dramatic, there are very few real cases where this will change anything: it only impacts partial sanitization where adjustHs() is called but not updateProperties() and where there are valence violations in the input.
I'm comfortable that the tests would have caught any broader effects and doubt this is actually a problem many people have


Add IAE school on Toulouse - France

@tvluong051 Pull request merged. Thank you!
For the record: this is the same university as in #1531


Spec needs an update for noImplicitThis behavior.

https://github.com/Microsoft/TypeScript/blob/b8f22f51441495203c96b95969c45a3f78482517/doc/spec.md#3811-this-type-references
Also related is #20343.

Also https://github.com/Microsoft/TypeScript/blob/75e5b1377558aa88a0b3d3dc821e050a2492261b/doc/spec.md#3.6.3 needs to be fixed up


Security Vulnerability in moment

The moment code is in the following, which will cause security vulnerability.
https://github.com/sferik/rails_admin/blob/master/vendor/assets/javascripts/rails_admin/moment-with-locales.js
so looks need to upgrade the version of moment to solve this security problem
https://www.cvedetails.com/vulnerability-list/vendor_id-16043/product_id-35644/Moment-Project-Moment.html

This really should be added to the "security" disclosure tab of Github. It's something they added in the last few weeks.

@EthanZeigler good suggestion, how can I make this in security tab?

... good point. Looks like they haven't added a disclosure piece yet.
On Mon, Aug 19, 2019 at 1:54 PM Elvis<EMAIL_ADDRESS>wrote:

@EthanZeigler https://github.com/EthanZeigler good suggestion, how can
I make this in security tab?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sferik/rails_admin/issues/3182?email_source=notifications&email_token=ACFTL6AB7IQP45LVIGNTYELQFLM4NA5CNFSM4IJY6DZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4TY5KQ#issuecomment-522686122,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACFTL6C3ZWTJP4CLZ3KUAY3QFLM4NANCNFSM4IJY6DZQ
.

--

Ethan Zeigler
Open Source Developer & Junior CS Major
ethanzeigler.com & ethanzeigler.com/blog
(Websites Under Development)


Raise exception on unknown document types

Trello: https://trello.com/c/Zx8mNyZi/35-investigate-how-could-data-be-exported-from-whitehall-m-1-day
I hit an issue experimenting with Whitehall data as the document_type is news_story rather than news_article (which is the schema name) - I've set this up to raise an exception now as it's quite cryptic debugging this without.
I've also fixed the document_type values to have news_story - note this will cause problems editing documents if you have news_article document_types in your database.

@tijmenb I'm guessing it was once a format and was since replaced since there are 34887 news_story document types compared to 1366 news_article document types.
Yeah you could validate on a Document but since the database and YAML files are both moving targets  it's always possible for it not to exist so we either throw an exception somewhere or deal with that the value can be nil


Cannot use 'in' operator

Hello, I added a script to the page, but it does not work, it gives errors in the console:
Uncaught TypeError: Cannot use 'in' operator to search for 'tachyon' in undefined
at t (tachyon.min.js:1:380)
at NodeList.forEach ()
at tachyon.min.js:1:619
at Array.forEach ()
at MutationObserver.observe.childList (tachyon.min.js:1:595)
What could be the problem? Thank you

Thanks for bringing this to my attention.

Can you double check that you're using the correct version? I pushed out a fix for a similar error recently with 2.0.1

What website are you getting this error on? How do you have Tachyon installed?


No media source error when there is no stream

When there is no stream, I receive "No media source" error. Is there a way for it to stream a broadcast empty?

@winlinvip Can you help me?

For discussion or idea, please ask in discord.
This issue will be eliminated, see #2716


cant do remote desktop connection

Hi, just updated Windows 11 version and now can´t do a remote desktop connection. All the labels on rdp.config appear on green (supported, listening, etc), i can even ping just fine with the server but at the moment i try to do a remote connection i get this error (image above).

If you changed RDP port you need to open this port in firewall.

All the labels on rdp.config appear on green

No RDPConf attached. Closed as invalid :)


Vulnerable Dependency: macaddress

Hi, apologies if this isn't the right place for this.
Using create-react-app and running npm audit  (available as npm 6) returns a vulnerable dependency report with Critical tag:
=== npm audit security report ===
Package: macaddress
Dependency of: react-scripts
Path: react-scripts > css-loader > cssnano >  postcss-filter-plugins > uniqid > macaddress
More info: https://nodesecurity.io/advisories/654

npm audit outputs:
Run  npm install --dev<EMAIL_ADDRESS>to resolve 1 vulnerability

But according to https://github.com/facebook/create-react-app/issues/3815 the newest version is 2.0.0-next.66cc7a90.
What version should I install?

From the vulnerability description you linked to:

For this vulnerability to be exploited an attacker needs to control the iface argument to the one method.

If you look at the code for uniqid you'll see this is not the case.
So there is no actual vulnerability you're being exposed to.
Feel free to send us a PR that bumps the package version when downstream packages stop using the vulnerable one but there is no issue that we need to address on our side.

For this vulnerability to be exploited an attacker needs to control the iface argument to the one method
@gaearon can you explain what this means?

It’s said here:
https://nodesecurity.io/advisories/654

For this vulnerability to be exploited an attacker needs to control the iface argument to the one method.

The macaddress package exports a method called one that takes a single argument. If that argument was supplied by an attacker they could trigger the vulnerability. However, in our case that argument is hardcoded in the uniq implementation I linked to above:
// ...
var mac = typeof __webpack_require__ !== 'function' ? require('macaddress').one(macHandler) : null ;
// ...
function macHandler(error){
  // ...
}

It’s not based on user input and can’t be controlled by an attacker. So there is no vulnerability in this case.
Does this explanation help?

@gaearon you were really helpful !

Stuff will break if you start updating internal packages without ejecting. You’ve been warned :-)
Going to lock this thread because there’s no actionable thing here for us. I’ll see if we can bump the dependency in 1.x branch. But again, there’s no real vulnerability here and you’re wasting effort trying to fix it.


Make template Rust only

Compiling still happens with cdylib.
The file linked against (in target/release) is the compiled plugin file.

Chunkwm plugins export:

plugin_details Exports:

int ApiVersion;
const char *FileName;
const char *PluginName;
const char *PluginVersion;
plugin_func Initialize; (the same as GetPlugin)

plugin *GetPlugin()


How to record multi-operation/table/dbs operations on DB metrics

For  a simple database queries (such as SELECT * from foo where bar="baz"), we'd like to capture the following attributes when possible (on spans):

db.operation.name = SELECT
db.collection.name = foo (aka db.sql.table and other similar system-specific attributes)
db.collection.namespace = mydb (aka db.name along with db.instance.id and similar)
db.query.text = SELECT * from foo where bar=? (aka db.statement)
db.query.parameter.bar=baz

(attribute names are being discussed and are not final).
This simple case is supported by current version of DB semantic conventions. It's also a common one in the NoSQL world if we exclude bulk operations (or non-homogeneous batch operations).
Attributes (except db.query.* ones) have reasonable cardinality and can be used on traces and metrics.

More complicated queries involve multiple operations, tables, or even databases. E.g. in SELECT * from foo JOIN bar ON baz
we have two operations (SELECT and JOIN), two tables (foo and ``bar`), and just one database.

db.query.text and db.query.parameter.* for such queries are still relevant and make sense on spans (still cardinality is a problem for metrics)
Operation and collection names become problematic to record

DB WG is considering multiple options:

Option 1: always capture db.operation.names, db.collection.names, db.collection.namespaces as  arrays
Pros:  consistent understandable model
Cons:

array attribute on metrics
simple case (one operation) becomes hard to use
hard to query and not quite useful on spans (if we already capture templatized query text)
the combined cardinality of operation name, collection names, database names is the same as in the db.query.text

Option 2: capture both db.operation.name and  db.operation.names  (same for collections and namespaces).
The array attributes are only captured when more than one operation is performed.
In this case we can entertain different options for db.operation.name - it may contain the first operation, operations joined as string, or shouldn't be reported at all.
Pros:

simple case is easy
complex case is slightly better (e.g. when db.operation.name contains joined list SELECT JOIN)

Cons:

array attribute on metrics
hard to query  and not quite useful on spans (if we already capture templatized query text)
the combined cardinality of operation name, collection names, database names is the same as in the db.query.text

Option 3: don't capture multiple operation names, collection names, namespaces
Pros: simple case is easy
Cons:  nothing distinguishes  different operations in the complex case
There could be other options including opting into collecting templatized query string on metrics, but none of those is perfect.
Still, we'd like to provide a default experience which could be improved with users providing query nick-names (see https://github.com/open-telemetry/semantic-conventions/issues/521 for the context).

Additional context

similar problem exist for bulk operations - https://github.com/open-telemetry/semantic-conventions/issues/712
in case of bulk operations in gets even worse since we'd need two-dimensional arrays
array attributes, if protocol does not support them "SHOULD be represented as JSON-encoded strings". I.e. {[\"SELECT\", \"JOIN\"]} making them even harder to use. Space (or comma) delimited list would be nicer ([SELECT, JOIN])

Option 2: capture both db.operation.name and db.operation.names (same for collections and namespaces).

I wonder if we are over-engineering here. Taking SQL statements as an example, they can be parsed into an AST which has a top-level statement, which tells you whether you SELECT, INSERT, DROP, CREATE ... It's important to have this top-level statement in db.operation.name, as it tells you about the effect the operation has.
I'm not sure about db.collection.name. However, we should avoid a situation where we define a field as an array, which in 95% of all cases only has a single value.

Another thought I have is that what we actually want is to capture duration per query template. Operation/collection/db names on the measurement is  a proxy to identify a subset of queries.
So we want to have a metric for a thing that has high-cardinality in general case (query template) which seems to be impossible.
Ways to limit the cardinality provided above:

capture array - limited usability and still has a cardinality issue
capture the first: we end up with ambiguity (SELECT * from foo is represented exactly as SELECT * from foo JOIN bar on baz)
capture none: resulting metric is not useful

What if we give up on a general case support in default experience?
Option 4:

simple case: capture individual operations/collections/namespaces
complex case: opt-in to capture templatized db.query.text. We can templatize even further to something like SELECT ? from users where ?  or even SELECT ? from users where user_id = ?

the cardinality of it would be similar to http.route one
we can normalize everything (spaces, case, etc)
we can think about other mitigations, like limiting it to X chars

Pros: explicit choice for users who don't expect high cardinality
Cons: perf
Option 5:

simple case: capture individual operations/collections/namespaces
complex case: users provide a hint for db.query.name (e.g. SQL commenter, or in some other way) like get user by user id or get user address by user name

Pros:

awesome metrics
metrics are future-proof - all we need to know about query is expressed in that attribute
Cons:
users need to provide hints in the code
we don't have such mechanism in otel (but see https://github.com/open-telemetry/semantic-conventions/pull/675  - there is a need for one)

so the proposal:

Introduce opt-in db.query.name|template|alias attribute that'd capture low-cardinality name when it's available

it can be provided by user - instrumentations MAY support a way and MUST document how if they do. We may need to find a generic way for otel, but independently of DB semconv stability
it can be parsed from the query text if instrumentation supports it

Capture db.operation.name, db.collection.name, db.collection.namespace ONLY if there is one operation (table or db involved). E.g.:

select * from mydb.foo join mydb.bar on baz would result in only the db.collection.namespace=mydb collected
select * from foo1 foo, foo2 foo where... would result in the db.operaion.name=select,  db.collection.namespace=mydb

It seems the dynamodb (which btw don't live under the db. namespace 😓) use an array attribute for the tables aws.dynamodb.table_names

@lmolkova is this resolved now that db.collection.name and db.operation.name are specified as the "first found in the query" (when parsed from db.query.text)?

Reopening based on the community feedback (thank a lot @pellared for bringing it up).
Discussed and tentatively agreed on the following approach
No-query operations:

span name = findAndModify foo
db.operation.name = findAndModify
db.collection.name = foo
no db.query.synthetic

Query-based operations:

multiple operations

span name = { db.query.synthetic }
db.query.synthetic = SELECT foo, DELETE bar, INSERT baz  - recommended on metrics
db.query.text - opt-in on metrics (or not add it yet)
no db.collection.name or db.operation.name on spans or metrics

single operation

span name = { db.query.synthetic } or {operation} {collection} which are the same
db.query.synthetic = SELECT foo  - recommended
db.query.text - opt-in on metrics (or not add it yet)
db.operation.name = SELECT
db.collection.name = foo

I have a naive question about whether db.operation.name is actually useful for users. If users want to diagnose a query, they could use spans from SQL clients, which already contain the full query text. Why do we need aggregated value about db.operation.name?