docs: polish doc update to date

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary

add 'real dashboard' and 'segments' in role matrix
add troubleshooting for the server error of web console
update the template links for China regions

Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[ ] add new test cases
[x] all code changes are covered by unit tests
[ ] end-to-end tests

[ ] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting
[ ] streaming ingestion

[ ] with Redshift Serverless
[ ] with provisioned Redshift

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.70
< 80

Duplicated lines density
:white_check_mark: OK
8.50
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
9
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 7/23/2024, 08:03:42 (UTC+0)

SonarQube Code Analytics
Quality Gate passed

Additional information
The following metrics might not affect the Quality Gate status but improving them will improve your project code quality.
Issues
 0 Bugs
 0 Vulnerabilities
 0 Code Smells
Coverage and Duplications
No data Coverage
No data Duplication

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.70
< 80

Duplicated lines density
:white_check_mark: OK
8.50
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
9
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 7/23/2024, 09:13:36 (UTC+0)


Handle ocdm errors

Summary: MediaKeySession now stores ocdm errors received via onError and returns the relevant status from Apis.
Type: Feature
Test Plan: Unittests, NPLB
Jira: RIALTO-154

https://jenkins.code.rdkcentral.com/job/github-triggered/28386/ started

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/20280/ started

https://jenkins.code.rdkcentral.com/job/build-component/64836/ started.

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/32771/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/28388/ started

https://jenkins.code.rdkcentral.com/job/build-component/64837/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/20299/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/32799/ started.

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/139754/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/139755/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/139780/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/139781/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/139782/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/139783/

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/20308/ started

build-brcm-va-sgc Console Log uploaded to Gist URL: https://gist.github.com/rdkcmf-jenkins/85cb7afb9bbc0aa68fe39e226da134de

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/20321/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/32820/ started.

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/139819/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/139818/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/139820/


Documentation site not linking to appropriate files

When trying to look at the API references for a lot of materials, the pages are not appropriately referenced.
For example, on this API Reference page,
the link for the "rect-series" is given as
https://uber.github.io/react-vis/website/dist/rect-series.md
=> which gives an empty container, when I assume we want it to serve the contents of https://github.com/uber/react-vis/blob/master/docs/rect-series.md
This page is appropriately rendered at
https://uber.github.io/react-vis/documentation/series-reference/rect-series
There are instances of this throughout the documentation, such as the General-Principles page providing the same incorrect links to Arc Series, Line Series, etc.
I hope this is as simple as changing all of those links from /website/dist/ARTICLE_NAME to /documentation/series-reference/ARTICLE_NAME

Closed due to valiant work of @gsas2


wagtailimages "file" field length should be 255 not 100

I see no reason to limit this to less than the db field maximum. More importantly a 255 limit would be more compatible with imports from other CMS, where an arbitrary limit of 100 might not exist (as was the case with a recent client)

No one has commented on this in 9 years so I’ll close this now. If anyone feels this is important please re-open with our current feature request template so the request is clearer.


[MM-35184] Update apps install command for Marketplace

Summary
Changes per https://github.com/mattermost/mattermost-plugin-apps/pull/166
Ticket Link
https://mattermost.atlassian.net/browse/MM-35184
Related Pull Requests

Has Apps plugin changes: https://github.com/mattermost/mattermost-plugin-apps/pull/166

Release Note
NONE

/cherry-pick release-5.35

Cherry pick is scheduled.

/cherry-pick cloud

Cherry pick is scheduled.

@hanzei  and @amyblais can we confirm were this was cheery picked?
@hanzei not sure this is supposed to go to May 5th.

@DHaussermann It was cherry-picked to v5.35 and cloud (for May 5).

Sorry I was under the impression this would not got until next cloud release.
@catalintomai and @hanzei or possibly @mickmister Can you help with some options here?
v5.35 is not an issue but, this requires an upgraded app-plugin which we will only release next week.
Can we pull this out maybe?

cc @amyblais ☝

I've opened a PR to revert the cloud cherry-pick: https://github.com/mattermost/mattermost-webapp/pull/8069

Yes, this change should not have been to cloud. Thanks for taking care of this @amyblais :+1:


US data displays negative annualized return for all the models

I tried US data for all the models, but all of them showing negative annualized return, (while the SP500 benchmark showing 12% annualized return). For examples, here are my workflow for LSTM, I wonder did I make any mistakes?  (I also checked the SP500 from 2017 to 2020,  the portfolio cannot be negative even randomly select stocks) Thanks a lot!
qlib_init:
provider_uri: "~/.qlib/qlib_data/us_data"
region: us
market: &market SP500
benchmark: &benchmark ^gspc
data_handler_config: &data_handler_config
start_time: 2008-01-01
end_time: 2020-11-01
fit_start_time: 2008-01-01
fit_end_time: 2014-12-31
instruments: *market
infer_processors:
- class: RobustZScoreNorm
kwargs:
fields_group: feature
clip_outlier: true
- class: Fillna
kwargs:
fields_group: feature
learn_processors:
- class: DropnaLabel
- class: CSRankNorm
kwargs:
fields_group: label
label: ["Ref($close, -2) / Ref($close, -1) - 1"]
port_analysis_config: &port_analysis_config
strategy:
class: TopkDropoutStrategy
module_path: qlib.contrib.strategy
kwargs:
signal:
-
-
topk: 50
n_drop: 5
backtest:
start_time: 2017-01-01
end_time: 2020-11-01
account: 100000000
benchmark: *benchmark
exchange_kwargs:
deal_price: close
open_cost: 0.0000229
close_cost: 0
min_cost: 0.01
task:
model:
class: LSTM
module_path: qlib.contrib.model.pytorch_lstm
kwargs:
d_feat: 6
hidden_size: 64
num_layers: 2
dropout: 0.0
n_epochs: 200
lr: 1e-3
early_stop: 20
batch_size: 800
metric: loss
loss: mse
GPU: 7
dataset:
class: DatasetH
module_path: qlib.data.dataset
kwargs:
handler:
class: Alpha360
module_path: qlib.contrib.data.handler
kwargs: *data_handler_config
segments:
train: [2008-01-01, 2014-12-31]
valid: [2015-01-01, 2016-12-31]
test: [2017-01-01, 2020-11-01]
record:
- class: SignalRecord
module_path: qlib.workflow.record_temp
kwargs:
model:
dataset:
- class: SigAnaRecord
module_path: qlib.workflow.record_temp
kwargs:
ana_long_short: False
ann_scaler: 252
- class: PortAnaRecord
module_path: qlib.workflow.record_temp
kwargs:
config: *port_analysis_config
'The following are analysis results of benchmark return(1day).'
risk
mean               0.000508
std                0.013132
annualized_return  0.120839
information_ratio  0.596487
max_drawdown      -0.382494
'The following are analysis results of the excess return without cost(1day).'
risk
mean              -0.000012
std                0.005776
annualized_return -0.002809
information_ratio -0.031517
max_drawdown      -0.191328

Try to change label to ["Ref($close, -1) / $close - 1"]. The original label is for Chinese market, which has different T0 trading rules. Also, US market is more mature and more competitive, so it is harder to find profitable strategies. If your annualized return is negative, that means your strategy is not profitable.


Expose override in qhub-config.yaml for prefect

Description
Currently the prefect chart provided in QHub is too restrictive. Would like to provide the option for more flexible Prefect deployments while making the helm chart follow prefect more closely.
Acceptance Criteria

[x] add an overrides variable to prefect chart that follows the model in jupyterhub
add an overrides key to the qhub-config.yaml in prefect that allows user based overrides

prefect:
   enabled: true
   ...
   overrides:
       ...

Tested it and got the following resuts:
# module.prefect.helm_release.prefect will be created
# module.prefect.helm_release.prefect will be created
   + resource "helm_release" "prefect" {
       + atomic                     = false
       + chart                      = "modules/kubernetes/services/prefect/chart"
       + cleanup_on_fail            = false
       + create_namespace           = false
       + dependency_update          = false
       + disable_crd_hooks          = false
       + disable_openapi_validation = false
       + disable_webhooks           = false
       + force_update               = false
       + id                         = (known after apply)
       + lint                       = false
       + manifest                   = (known after apply)
       + max_history                = 0
       + metadata                   = (known after apply)
       + name                       = "prefect"
       + namespace                  = "dev"
       + recreate_pods              = false
       + render_subchart_notes      = true
       + replace                    = false
       + reset_values               = false
       + reuse_values               = false
       + skip_crds                  = false
       + status                     = "deployed"
       + timeout                    = 300
       + values                     = [
           + <<-EOT
                 spec:
                   template:
                     spec:
                       containers:
                         - env:
                             - name: IMAGE_PULL_SECRETS
                               value: ''
                             - name: PREFECT__CLOUD__AGENT__LABELS
                               value: '[]'
                             - name: JOB_MEM_REQUEST
                               value: ''
                             - name: JOB_MEM_LIMIT
                               value: ''
                             - name: JOB_CPU_REQUEST
                               value: ''
                             - name: JOB_CPU_LIMIT
                               value: ''
                             - name: IMAGE_PULL_POLICY
                               value: ''
                             - name: PREFECT__BACKEND
                               value: cloud
                             - name: PREFECT__CLOUD__AGENT__AGENT_ADDRESS
                               value: http://:8080
             EOT,
           + "[{'PREFECT__CLOUD__AGENT__LABELS': ['dev', 'prod'], 'JOB_MEM_REQUEST': '20Gi'}]",
         ]
       + verify                     = false
       + version                    = "0.1.0"
       + wait                       = true
       + wait_for_jobs              = false

       + set {
           + name  = "cloudApi"
           + value = "https://api.prefect.io"
         }
       + set {
           + name  = "namespace"
           + value = "dev"
         }
       + set {
           + name  = "prefectImage"
           + value = "prefecthq/prefect:0.14.22-python3.8"
         }

       + set_sensitive {
           # At least one attribute in this block is (or was) sensitive,
           # so its contents will not be displayed.
         }
     }

Tying to solve the folowing error:
Error: ---> error unmarshaling JSON: while decoding JSON: json: cannot unmarshal array into Go value of type map[string]interface {} [{'PREFECT__CLOUD__AGENT__LABELS': ['dev', 'prod'], 'JOB_MEM_REQUEST': '20Gi'}]
 │
 │   with module.prefect.helm_release.prefect,
 │   on modules/kubernetes/services/prefect/main.tf line 1, in resource "helm_release" "prefect":
 │    1: resource "helm_release" "prefect" {
 │

Error solved and deplymen was suecessuf, simple test on qhub-config:
prefect:
  enabled: true
  overrides:
      prefect_agent:
        prefectLabels: [dev, prod]
        job:
          resources:
            requests:
              memory: 20Gi

Output on Prefec-agent service (by K9s):
Environment:
│       PREFECT__CLOUD__AGENT__LABELS:         ["dev","prod"]                                                                                │
│       JOB_MEM_REQUEST:                       20Gi

https://github.com/Quansight/qhub/pull/813

Closed by #813


Use fd/find to search for files and folders instead of glob()

Hi @tfeldmann.
First, thank you for this awesome project! 🙂
I have a suggestion/feature request that I'd like to run by you before trying to work on a pull request.
Python glob() is not particularly fast.
So my idea would be to replace it internally by calling fd (A simple, fast and user-friendly alternative to 'find') or even find (which is not that fast, but it is present by default).
VSCode already did something similar, using ripgrep for its search engine.
Rough specs:

organize could have a configuration like glob_with_fd: true|false or something similar;
The app would use which fd or something to determine if fd is installed, or which find to get find's path;
All calls to glob() would use fd/find internally instead, and return files/folders in the same format as before (pathlib.Path or str, I'm not sure how is the return type);
This feature could also be useful for #32 (another pull request I'm waiting for anxiously 😬 , but unfortunately inactive for a while...).

I saw that you mentioned something about glob in your roadmap; maybe you already have something on your mind.
What do you think?
Would you be interested in this feature?

Thank you for reaching out and wanting to help! Much appreciated 👍
That's a good idea and surely would speed things up quite a bit.
The thing is I'm knee deep in the middle of rewriting the core and directory tree walking algorithms at the moment (Pull request #85).
The idea is to use PyFilesystem  for globbing to support zip files, S3 Buckets, remote file systems via SSH and many others in the future.
So I'd say it would be better to wait a bit until #85 is done. I'll keep this optimization in mind so your idea can be integrated afterwards for local filesystems without much hassle.
I'm keeping this issue open in the meantime.

Nice, using fd/find seems related to #85 indeed. Looking forward to it.
I also checked the roadmap... some cool ideas on your scratchpad. 😉
Interesting how you also face some similar issues I have on my Nitpick project.
Stuff like:

Config file validation;
Using a plugin system;
Testing on Windows OS.

I would be interested in knowing how you intend to solve those problems in the future. 😄
You also inspired me to (soon) make public notes on the GitHub project by using cards (I didn't know about this feature).
Thanks and keep up the nice work! 💪

I know this answer is late - but great project! I'll try that out!
I'm closing this issue because I implemented the full PyFilesystem support. Using find would be a nice optimization but v2 is already so much faster I don't really see the need for that and it would make the code much more complicated.
So thanks for the issue and maybe you can try the new version. Keep up the good work!


Suggest Clumsy as a testing option on Windows

The open-source utility is very easy to use and has a lower barrier to entry than the other tools. It is very close to Network Link Conditioner on OS X.
Disclaimer: I have no relation to Clumsy or their website other than having used it as a user for eight months.

cc @addyosmani and @gauntface for feedback.  I believe we have been trying to limit ourselves to one choice rather than a selection to help avoid choice paralysis.  I'll let Matt decide what to do.

I personally don't have experience with Clumsy. @gauntface? Where possible I would like us to manually evaluate options to ensure they provide sane recommendations before we commit to including them.

Seeing that most folks don't have experience, I'm going to close this for now, if it becomes more popular or offers a special set of features, happy to revisit.


DraggableScrollableSheet programmatically dragged doesn't maintain size after rebuild

Steps to Reproduce

Run code below
Try expand the sheet by scroll, tap light and dark button
Minimize sheet, now expand it by tapping the button, tap light and dark button

Expected results: Sheet maintain it size
Actual results: Sheet lost the size and went back to initial size during rebuild if previous size was changed from controller

Code sample
import 'package:flutter/material.dart';

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();

  runApp(const App());
}

class App extends StatefulWidget {
  const App({Key? key}) : super(key: key);

  @override
  State<App> createState() => AppState();

  static AppState of(BuildContext context) {
    return context.findAncestorStateOfType<AppState>()!;
  }
}

class AppState extends State<App> {
  ThemeMode _themeMode = ThemeMode.light;

  void setThemeMode(ThemeMode mode) {
    if (_themeMode != mode) {
      setState(() {
        _themeMode = mode;
      });
    }
  }

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      themeMode: _themeMode,
      theme: ThemeData(brightness: Brightness.light),
      darkTheme: ThemeData(brightness: Brightness.dark),
      home: const Home(),
    );
  }
}

class Home extends StatelessWidget {
  const Home({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('Demo'),
      ),
      body: Center(
        child: ElevatedButton(
          onPressed: () {
            showModalBottomSheet(
              context: context,
              isScrollControlled: true,
              builder: (context) => const _DemoSheet(),
            );
          },
          child: const Text('Open'),
        ),
      ),
    );
  }
}

class _DemoSheet extends StatefulWidget {
  const _DemoSheet({Key? key}) : super(key: key);

  @override
  _DemoSheetState createState() => _DemoSheetState();
}

class _DemoSheetState extends State<_DemoSheet> {
  final _draggableController = DraggableScrollableController();

  void _expand() {
    _draggableController.animateTo(
      0.9,
      duration: const Duration(milliseconds: 150),
      curve: Curves.easeOut,
    );
  }

  void _setTheme(ThemeMode themeMode) {
    App.of(context).setThemeMode(themeMode);
  }

  @override
  Widget build(BuildContext context) {
    final theme = Theme.of(context);

    return DraggableScrollableSheet(
      controller: _draggableController,
      initialChildSize: 0.5,
      minChildSize: 0.2,
      maxChildSize: 0.9,
      expand: false,
      builder: (context, scrollController) => ListView(
        physics: const BouncingScrollPhysics(),
        controller: scrollController,
        children: [
          Padding(
            padding: const EdgeInsets.all(8.0),
            child: ElevatedButton(
              onPressed: _expand,
              child: const Text('Expand'),
            ),
          ),
          Padding(
            padding: const EdgeInsets.all(8.0),
            child: Text(
              'Current brightness: ${theme.brightness}',
              textAlign: TextAlign.center,
            ),
          ),
          Padding(
            padding: const EdgeInsets.all(8.0),
            child: ElevatedButton(
              onPressed: () => _setTheme(ThemeMode.light),
              child: const Text('Light'),
            ),
          ),
          Padding(
            padding: const EdgeInsets.all(8.0),
            child: ElevatedButton(
              onPressed: () => _setTheme(ThemeMode.dark),
              child: const Text('Dark'),
            ),
          ),
          for (int i = 0; i < 100; i++)
            Padding(
              padding: const EdgeInsets.all(8.0),
              child: Text(
                i.toString(),
                textAlign: TextAlign.center,
              ),
            ),
        ],
      ),
    );
  }
}

Logs
[✓] Flutter (Channel stable, 3.3.6, on macOS 12.5 21G72 darwin-x64, locale en-GB)
    • Flutter version 3.3.6 on channel stable at /Users/*/Flutter/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6928314d50 (6 days ago), 2022-10-25 16:34:41 -0400
    • Engine revision 3ad69d7be3
    • Dart version 2.18.2
    • DevTools version 2.15.0

[!] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/*/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

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

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

[✓] Android Studio (version 2021.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
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.70.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • iPad Pro (9.7-inch) (mobile) • 3B8FD730-4BA9-444C-866A-D6BB7616D597 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-5 (simulator)
    • macOS (desktop)              • macos                                • darwin-x64     • macOS 12.5 21G72 darwin-x64
    • Chrome (web)                 • chrome                               • web-javascript • Google Chrome 106.0.5249.119

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

! Doctor found issues in 1 category.

Basically, I duplicated the issue #101114 since it's still occurring the same exact way (I just did put my doctor output in place of). Initial author: @SuperPenguin
Initial fixer: @caseycrogers

@lionelmennig Hi, thanks for reporting.
Can you test the master channel branch, the patch has not been released to the stable branch yet.

@lionelmennig Hi, thanks for reporting. Can you test the master channel branch, the patch has not been released to the stable branch yet.

Hi! You're right, it works on master! Thanks!


How accessible are the generated PDF's?

Worth investigating https://www.gov.uk/guidance/how-to-publish-on-gov-uk/accessible-pdfs

Obvs a lot of this will ride on the data we give it but we should try and come up with a decent semantic html doc and see how well it converts.


Command feature added (process(), reject())

I made two functions that mark a command as processed or rejected at lib/command.js

Hey @CILP, thanks for the contribution.
Actually, this functionality is already included in the library on the devices.js file so we shouldn't merge this one in order to avoid duplicating it.
This decision was made because we believe it's a device's responsibility to accept or reject a single command. This is how the feature was implemented in other libraries as well.
Thanks anyway!

Oh, @fsaravia  I see.
Well, thank you.!

@CILP: thank you for contributing! :)


stage error

Describe your problem here.
i did a copy and paste sooooooooooooo and it keep saying expected near end 'nursejoy  idk  if its just me so i check lua app and it seem to tell me the same

What do i do?
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
its a copy n  paste from hxs to lua  spript

oh and im unable to find  dis

💀💀💀

bruh

That is not lua

ik but  it react the same  thing in the game it somehow still reconize it

It's not going to work, you can try running the code through runHaxeCode(), but as it is it won't run in a script

aight so i did an altered way and  it work  i put em together as one png
ty  for tryna help me yall


Please keep command parameter names consistent with JSON parameters

While reading the RPC API page on various commands, I can see entries like:
Command line:
wallet_propose [pass_phrase]
JSON:
{
passphrase: string
}
With two different ways of writing the same command parameter. This has caused me a few times to use the wrong spelling for my program. If it is possible, it would be great to keep those parameter names the same (preferably without the underscores).

I agree with the sentiment entire! - and sorry for the frustration - but we aren't unfortunately going to change any names until a future RPC 2.0, where everything will be consistent.


tf.compat.v1.data.get_output_shapes(datasets) gives Errors

Iam getting different types of errors in different projects whenever I use tf.compat.v1.data.get_output_shapes(datasets)
I have tried all the Codes in Colab only.

System information
COLAB

Tensorflow Version :  Latest on Colab : 2.3.0
Python 3
COLAB GPU

Current behavior :
While using tf.compat.v1.data.get_output_shapes(datasets), I got 2 types of errors in 2 projects:

ValueError: logits and labels must have the same shape ((None, 1) vs ())
ValueError: Input 0 of layer global_average_pooling1d is incompatible with the layer: expected ndim=3, found ndim=4. Full shape received: [None, None, None, 128]

As a temporary solution, I used datasets.output_shape & I got the desired output.
But whenever I use datasets.output_shape , I get a warning as below:
WARNING:tensorflow:From :3: DatasetV1.output_shapes (from tensorflow.python.data.ops.dataset_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.compat.v1.data.get_output_shapes(dataset).
Request to the Tensorflow Team:
I kindly request the Tensorflow team to look into this issue and help me solve it.
Thank you Tensorflow Team in Advance...!!!
Colab file Link

I tried in colab with TF version 2.3, nightly(2.4.0-dev20200831) and was able to reproduce the issue. Please, find the gist here. Thanks!

Hi @iamsrilakshmi, I think your issue here is that you first define
tr = tr.shuffle(10000)
tr = tr.padded_batch(64, tr.output_shapes)

And then when defining tr2, you are again padding tr, which is already padded, and that results in an extra dimension, hence the error message expected ndim=3, found ndim=4. Full shape received: [None, None, None, 128]
If you just remove the following lines from your colab notebook, it runs without error:
tr = tr.shuffle(10000)
tr = tr.padded_batch(64, tr.output_shapes)
val = val.padded_batch(64, val.output_shapes)

Hi @nikitamaia ,
Can you please check in this Colab code file... Link to colab file
I am facing the same error with tf.compat.v1.data.get_output_shapes. This error is displayed only when training the model
The error I am talking about is as follows:
ValueError: logits and labels must have the same shape ((None, 1) vs ())
Please look into the issues concerning this particular error

The error you see is because you are passing in the wrong datasets to your model.fit
You are calling  model.fit(train_data, epochs=num_epochs, validation_data=test_data)
but train_data and test_data are the raw datasets from tfds, and not the ones you have applied  tf.compat.v1.data.get_output_shapes to.
You should be passing in train_dataset and test_dataset like so:
model.fit(train_dataset, epochs=num_epochs, validation_data=test_dataset)
For future reference, Github is a place for filing bugs. These kinds of support requests are better for Stack Overflow where there is a wider community to troubleshoot.

Closing issue since a solution was found and there is no bug here.


Add diagnostic tools to this project

Similar to diagnostic tools implemented in the Kuzzle core project, the proxy should also be able to generate dumps to be used by the support team to solve potential technical issues

as kuzzle-proxy is deprecated => close


sas-access.properties is not being picked up into kustomization.yaml

In order to configure access engines, ../sas-bases/examples/data-access/README.md  indicates that you need 3 tranformers as well as a sas-access.properties, which should be added to kustomization.yaml as a configMapGenerator like shown below.
configMapGenerator:
- name: sas-access-config
behavior: merge
envs:
- site-config/data-access/sas-access.properties

This is not happening, even to the file is in the same location as the transformers (these are working as expected):
jumpuser@vm$ ll .../site-config/data-access/
-rw-rw-r-- 1 jumpuser jumpuser 679 Sep  2 12:01 sas-access.properties
-rw-rw---- 1 jumpuser jumpuser 550 Sep  2 13:28 deployment-access-nfs-mount.yaml
-rw-rw---- 1 jumpuser jumpuser 542 Sep  2 13:29 podTemplate-access-nfs-mount.yaml
-rw-rw---- 1 jumpuser jumpuser 567 Sep  2 13:29 cas-access-nfs-mount.yaml

Another architect told me he's having the same issue.

Quick update, another architect showed me an example of how to convert the access.properties format the doc has and perform it as a patch transformer.  That worked as expected.  So, perhaps, this issue becomes an opportunity to document that process.

Here is a helpful resource: https://communities.sas.com/t5/SAS-Communities-Library/How-to-Configure-a-SAS-ACCESS-interface-in-SAS-Viya-4/ta-p/720888
It mentions this README: sas-bases/docs/configuring_sasaccess_and_data_connectors_for_sas_viya_4.html
@andybouts, does that cover the steps you performed?

Hey @enderm , yep, that's good reference materials and mentions that env variables can be setup as configMaps, but the specific problem is that this deployment project did not use the site-config/data-access/sas-access.properties as documented in the ../sas-bases/examples/data-access/README.md.  Instead, the env variables in sas-access.properties must be converted into a .yaml file so that it will be picked up as a patch transformer.

I am having the same issue.  Apparently kustomize version 3.7.0 has a reported bug with merging configMapGenerators.   I have found a workaround which I will provide on request, but instructions on creating a patch transformer to update the configMap would be helpful.

If the current examples do not work with kustomize 3.7.0 you'll have to reach out to the data-access team. They need to fix there code base. They can also provide a sample patch transformer for use.

Last time, I tried to set data-access stuff for teradataa and I thought it worked since I could run libname statement successfully.
I will try to deploy one tomorrow.

I created a file in the $deploy/site-config/data-access directory called configmaps.yaml.  The instructions say to modify the base kustomization.yaml file, which is impossible if using this project.  The configmaps.yaml file will be picked up during the kustomize build step and be included in the deployment.  This assumes that the sas-access-properties file is also in the $deploy/site-config/data-access directory as well as the file data-env.yaml that is copied from the $deploy/sas-bases/examples/data-access folder.
$deploy/site-config/data-access/configmaps.yaml
apiVersion: builtin
kind: ConfigMapGenerator
behavior: merge
metadata:
name: sas-access-config
envs:

sas-access.properties

In my previous comment, the bullet should be a dash.

I will have old deployment directory.
I placed data-access directory under site-config/transformers/ and viya4-deployment added below to base kustomization.yaml
## user defined generators   \- site-config/transformers/data-access/sas-access-config.yaml
Since I don't have any working deployment now, I cannot check further. I will check more tomorrow.

You should be adding the data-access directory here: site-config/data-access the viya4-deployment code base will place it where it needs to go. If these samples are transformers it'll place those in the correct location when it generates the code base with kustomize.

Yes, that's what happened in my deployment.
--
Jim Brousseau
From: JK Min @.>
Sent: Wednesday, January 5, 2022 3:48 PM
To: sassoftware/viya4-deployment @.>
Cc: Jim Brousseau @.>; Comment @.>
Subject: Re: [sassoftware/viya4-deployment] sas-access.properties is not being picked up into kustomization.yaml (#138)
EXTERNAL
I will have old deployment directory.
I placed data-access directory under site-config/transformers/ and viya4-deployment added below to base kustomization.yaml
user defined generators - site-config/transformers/data-access/sas-access-config.yaml
Since I don't have any working deployment now, I cannot check further. I will check more tomorrow.

Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsassoftware%2Fviya4-deployment%2Fissues%2F138%23issuecomment-1006165638&data=04|01|jim.brousseau%40sas.com|3cd35e07147b45b89ccf08d9d0a5c8eb|b1c14d5c362545b3a4309552373a0c2f|0|0|637770232727941165|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=VFdPWNbhqV%2BTpwY8Y%2B63fI4ziPVN5J5WB5SAIoev0Rw%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJHY3NGTDJY5YVFRIO7J7RDUUTKCNANCNFSM5DJQ3FXQ&data=04|01|jim.brousseau%40sas.com|3cd35e07147b45b89ccf08d9d0a5c8eb|b1c14d5c362545b3a4309552373a0c2f|0|0|637770232727941165|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=HGYu7avDEGKT6VBQw0VrzYw2P4vBhEiU2Dgrdzp%2FAII%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|jim.brousseau%40sas.com|3cd35e07147b45b89ccf08d9d0a5c8eb|b1c14d5c362545b3a4309552373a0c2f|0|0|637770232727951135|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=hGMTIK8yRLTVrLZ1vXVuW7Xs7u7%2F3pZ%2FX63UZgXL6Gg%3D&reserved=0 or Androidhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|jim.brousseau%40sas.com|3cd35e07147b45b89ccf08d9d0a5c8eb|b1c14d5c362545b3a4309552373a0c2f|0|0|637770232727951135|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=m1S4bz5A6gT6R0vN6Q4atL3UAigB5BVbWvxnnsc0yDw%3D&reserved=0.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

Correct.
--
Jim Brousseau
From: Thomas S. Pangborn @.>
Sent: Wednesday, January 5, 2022 3:52 PM
To: sassoftware/viya4-deployment @.>
Cc: Jim Brousseau @.>; Comment @.>
Subject: Re: [sassoftware/viya4-deployment] sas-access.properties is not being picked up into kustomization.yaml (#138)
EXTERNAL
You should be adding the data-access directory here: site-config/data-access the viya4-deployment code base will place it where it needs to go. If these samples are transformers it'll place those in the correct location when it generates the code base with kustomize.

Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsassoftware%2Fviya4-deployment%2Fissues%2F138%23issuecomment-1006167453&data=04|01|jim.brousseau%40sas.com|8e9e99d24a714a09fe3108d9d0a666c4|b1c14d5c362545b3a4309552373a0c2f|0|0|637770235378520332|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=KL2JpJqATLxS3%2B7s36Qd9j2vXR17f6Wrj5ZZsTdSV84%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJHY3NGGF7E6YOWHQUONZGLUUTKS7ANCNFSM5DJQ3FXQ&data=04|01|jim.brousseau%40sas.com|8e9e99d24a714a09fe3108d9d0a666c4|b1c14d5c362545b3a4309552373a0c2f|0|0|637770235378530288|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=l8v8fCAYljRNvrVOdQ5m7sLUf3pJuDr%2FEbQ%2BOs6MvxA%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|jim.brousseau%40sas.com|8e9e99d24a714a09fe3108d9d0a666c4|b1c14d5c362545b3a4309552373a0c2f|0|0|637770235378540243|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=j7UtaiCioIdic80y5UPysRu1B2m4Jc25Qmfb7YZKQOs%3D&reserved=0 or Androidhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|jim.brousseau%40sas.com|8e9e99d24a714a09fe3108d9d0a666c4|b1c14d5c362545b3a4309552373a0c2f|0|0|637770235378540243|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=3AOEwTTCb0qzzGEFZCjZn36XVnXYvQWHfnYr3U6xG9w%3D&reserved=0.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

o.k. I checked what I did in more detail.
I also did the almost same thing as what @JimBrousseau did.
I placed these files under site-config/transformers/data-access (you can place under site-config/data-access too)

data-env.yaml
data-mounts-cas.yaml
data-mounts-deployment.yaml
data-mounts-job.yaml
enable-dc-ports.yaml
enable-epcs-port.yaml
sas-access-config.yaml
sas-access.properties

I copied data-env.yaml from sas-bases/overlays/data-access/ so that viya4-deployment can pick it up and add it to kustomization.yaml.
I created sas-access-config.yaml like below since I didn't want to update kustomization.yaml manually. I also wanted viya4-deployment to pick this up and add it to the kustomization.yaml.

configmap of my deployment has the values in added to sas-access.properties

Just like most of other READMEs, sas-bases/examples/data-access/README.md is for manual deployment (or any deployment method which requires manual update on kustomization.yaml), not for viya4-deployment.
I'm following the instruction as it is for our opensource deployments such as DDT daily deployment.
If you need, you can check our deployment directory. Please contact me if you need to check on it.

I removed sas-access-config configmap of my deployment.
I manually updated kustomization.yaml which IAC created - I added configMapGenerator part instead of using yaml file.

With this, I could build site.yaml successfully.
When I applied it, a new sas-access-config configmap got generated w/o problem.

@jkmin96 either method will work, however, kustomization.yaml will be rebuilt on the next deployment.

@JimBrousseau
If you update kustomization.yaml manually to add configMapGenerator, yes viya4-deployment will create a new kustomization.yaml removing it.
If you use a yaml like my sas-access-config.yaml (I guess you also use it), I think we can run viya4-deployment w/o problem.

Hi @jkmin96 checking for clarification. You were able to include the items listed in their own directory under site-config and have the DAC tooling apply those items into the kustomization.yaml and site.yaml without any issues, correct?

Yes, that is correct.
--
Jim Brousseau
From: Thomas S. Pangborn @.>
Sent: Tuesday, April 5, 2022 6:42 AM
To: sassoftware/viya4-deployment @.>
Cc: Jim Brousseau @.>; Mention @.>
Subject: Re: [sassoftware/viya4-deployment] sas-access.properties is not being picked up into kustomization.yaml (#138)
EXTERNAL
Hi @jkmin96https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjkmin96&data=04|01|jim.brousseau%40sas.com|b5684d9a2bdb424c779808da170a1094|b1c14d5c362545b3a4309552373a0c2f|0|0|637847629241907233|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=7%2FyvtJWPVJLtZx2f0ER8xY5z27gRla0M0aughZaClTg%3D&reserved=0 checking for clarification. You were able to include the items listed in their own directory under site-config and have the DAC tooling apply those items into the kustomization.yaml and site.yaml without any issues, correct?

Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsassoftware%2Fviya4-deployment%2Fissues%2F138%23issuecomment-1088719495&data=04|01|jim.brousseau%40sas.com|b5684d9a2bdb424c779808da170a1094|b1c14d5c362545b3a4309552373a0c2f|0|0|637847629241907233|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=WAhsdd0DE0cyxdiuyzUAnWaIfM9nQB2veDJeKchq8Yc%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJHY3NGIKLPPH5KP4U463ITVDQ7KTANCNFSM5DJQ3FXQ&data=04|01|jim.brousseau%40sas.com|b5684d9a2bdb424c779808da170a1094|b1c14d5c362545b3a4309552373a0c2f|0|0|637847629241907233|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=LZ0cF5MN0Yt6qZp6Ec44mxvzsZDH6Mv73pzGvIC%2BKWU%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

If that's the case I'll close this one. Andy is no longer with the company.

@JimBrousseau   How did you fix this issue?
I have set
ORACLE:   /access-clients/oracle/instantclient_19_8
How do I add access-clients/oracle/instantclient_19_8 to "$LD_LIBRARY_PATH". ?
360  proc sql;
361    connect to oracle (user='admin' password=XXXXXXXXXXXXXXXXXXXXXX path='dsdfdf.bx9.eu-west-2.rds.amazonaws.com');
ERROR: Unable to load oracle client (libclntsh.so)
ERROR: A Connection to the oracle DBMS is not currently supported, or is not installed at your site.
NOTE: PROC SQL set option NOEXEC and will continue to check the syntax of statements


Thread safe?

Hi,
When using the pyisyntax wrapper for this library I noticed segmentation faults when reading with multiple threads. Not sure if this is a Python problem or if libisyntax is not thread safe?
Can you clarify if the library is thread safe?

Sorry for the late reply!
I haven't tried the pyisyntax wrapper yet, and I'm not 100% sure about whether it 'should' work in the exact use case in the issue you linked to. But, I suspect it is currently not possible to do it in this way.
At least internally, there is some degree of thread-safety to make sure that tiles can be loaded in parallel (also because to load a single tile, there is usually a dependency on other tiles to be loaded first and there is a lot of complex caching stuff and internal synchronization going on). But, this doesn't necessarily translate to thread safety to the external API.
Maybe @alex-virodov knows a more complete answer for how the reader API is implemented right now?
For the streaming implementation in Slidescape I used a separate thread that collects requests for tiles periodically (each frame), and tries to continually satisfy these requests by pulling from a wishlist and reading as many tiles from that list as possible in a somewhat efficient way. I can imagine we could adjust the implementation to work similar to this, to collect tile requests in parallel and them dispatch them in batches periodically (although that would require some more work to be done).


⚠ Bofrost.de has degraded performance

In c8d7018, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 950 ms

Resolved: Bofrost.de performance has improved in 65551b1.


remove unnecessary android:exported="true" attribute from FCMPluginActivity in AndroidManifest.xml

Removed android:exported="true" attribute from FCMPluginActivity in AndroidManifest.xml as it is unnecessary and a potential security risk, as it makes the activity startable from any external app, as it is not protected with an app defined permission.

Tested locally and merged!
Thank you @apoorvakorde

Thanks @andrehtissot !

I'll make another release today


site-policy: Remove Enterprise Cloud Addendum from translations

Why:
Enterprise Cloud Addendum content/github/site-policy/github-enterprise-cloud-addendum.md looks removed in the past, the history is not disclosed: 3df90fc9b811728a9b7ee
/LANG/free-pro-team@latest/articles/github-enterprise-cloud-addendum has come to be redirected to /LANG/free-pro-team@latest/github/site-policy/github-enterprise-service-level-agreement.
What's being changed:
⚖  Removes Enterprise Cloud Addendum from translations:

de-DE: GitHub Enterprise Cloud-Nachtrag
es-XL: Anexo de GitHub Enterprise Cloud
ja-JP: GitHub Enterprise Cloudの補遺
pt-BR: Adendo do GitHub Enterprise Cloud
zh-CN: GitHub 企业云附录

Check off the following:

[x] All of the tests are passing.
[x] I have reviewed my changes in staging.
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

👋 @tnir Thanks for opening this pull request! Unfortunately, we are not able to accept pull requests for translated content. Our translation process involves an integration with an external service at crowdin.com, where all translation activity happens. We hope to eventually open up the translation process to the open-source community, but we're not there yet.
See https://github.com/github/docs/blob/main/CONTRIBUTING.md#earth_asia-translations for more details.

@janiceilene Thanks, but this PR is not directly relevant to translations of CONTENT. This is about a technical debt similar to #256
@zeke (approver of the PR above) What do think?

Thanks for the PR, but we're not accepting contributions on this issue right now. This is normally handled by a script and we're working internally on cleaning up all the extraneous files and re-enabling the script.


We must process parameter sets even in DecodingState::{AwaitingStreamInfo|Reset}

This issue was discovered when developing the h.265 code. If we fail to take in new SPS and PPS in this state (using process_nal()) they will be dropped. No test currently exercises this for H.264 but it remains a possibility, nevertheless.

decoders: h264: process PPS even in AwaitingStreamInfo|Reset was merged a while ago.


Apps closes

Bug or Regression?
Bug
System Info and Version
echo $DISPLAY
:0

spotify
[53310:53310:0617/223844.828528:ERROR:ozone_platform_x11.cc(243)] Missing X server or $DISPLAY
[53310:53310:0617/223844.828568:ERROR:env.cc(257)] The platform failed to initialize.  Exiting.
[53310:53310:0617/223844.828623:ERROR:main_runner.cc(261)] ContentMainRun failed with exit code 1

Description
Applications like spotify/android-studio suddently closes and refuses to launch after 30-40min of usage
How to reproduce
Use android-studio for around 40min
Crash reports, logs, images, videos
No response

#6398


missing values during prediction should throw an Exception if missing data wasn't present during training

Summary
When we encounter missing values during prediction after training without any missing data, the model predicts these examples without logging a warning or an exception (see issue [this issue])(https://github.com/microsoft/LightGBM/issues/2921):

Missing numerical values set to zero
Missing categorical values are sent to the right leaf

As a result, several or all features could be missing and the model would still return a prediction (of unknown quality).
I propose to at least log a warning and allow the model to be configured in a strict mode where unexpected missing values lead to an exception (I would argue this should be the default, but it might not work for compatibility reasons).
Motivation
Changing the current behavior is important for using lightgbm in production. When working with a train-test-split missing data in the testset is easily recognized and a difference between test and train is less likely than a difference between training and production data.
In production, data or code bugs can lead to one or multiple features being missing. In my experience, bugs that change the data happen as commonly as other bugs.
The current behavior would silently impute them to zero (numerical case) or assign them to an existing leaf (categorical case). The model would silently misbehave and it could be hard to detect, especially if the bug is only on the inference side, but not on the training data (which is typical when the data is not coming from a common feature store).
Description
Throw an exception when missing values are seen during inference but not during training. Value imputing should probably be done before calling the model, so I propose to make throwing an exception the default behaviour.
You might not agree (hence the current implementation), so maybe it could be an option to log a warning?
It would also be great to improve the documentation on the use_missing=false flag:
set this to false to disable the special handle of missing value

The doc string doesn't give an explanation of what is done instead during training and inference when disabling the special value handling.
References
https://github.com/microsoft/LightGBM/issues/2921
https://lightgbm.readthedocs.io/en/latest/Parameters.html

Closed in favor of being in #2302. We decided to keep all feature requests in one place.
Welcome to contribute this feature! Please re-open this issue (or post a comment if you are not a topic starter) if you are actively working on implementing this feature.


Document GitHub org owners and add new interim owners

Ping @zimbatm @Lassulus

Ok you're both org owners now


Enable editation of the input

[ ] When you tab selected number the input second time, it shall be possible to edit the number (currently it persist the selection of the whole input and it is not possible to perform the edit)

If I see it correctly it is achvied by setting .setSelectAllOnFocus(true); on the EditText

There is no EditText in Jetpack Compose. Please don't consider simple kotlin with xml. I tried the same behavior in Jetpack Compose but the problem is the same that I mentioned earlier

Hmm Understood. I have played around with the code. Can you please share the code what you have done for the provided APK?

I have played a little bit with the code I this is working for me
https://github.com/Minimalistic-Apps/price-converter/pull/42/commits/7735cbdcbcb6531bf521ac2d7bea4d3c674f3d92
(I have commented out the BTC formatting logic, to make it easier to demonstrate the functionality.)

An after I have implemented it I have found this solution that seems to work: https://stackoverflow.com/a/72504219

I have tested it here, and it seems it works: https://github.com/Minimalistic-Apps/price-converter/pull/42/commits/01ae2e5bb23872f9c4a0cd5211716273adddf21e

How do you want to receive the code for this apk, Please let me know?
And please join Jira. It would be easy for us to communicate there on each ticket

@hafizsaadiftikhar yes I am in jira, I have mentioned you in the relevant issue


Cannot use ManagedIdentity from a VM within Azure ML

Package Name: Azure Identity
Package Version: 1.15.0
Linux: 23.12.08
Python Version: 3.8.5

Describe the bug
2 out of our 7 users are unable to use their Azure Managed indentity when running a notebook on a VM inside Azure ML workspace.
Here is the compete error with DefaultAzureCredential

DefaultAzureCredential failed to retrieve a token from the included credentials.
Attempted credentials:
EnvironmentCredential: EnvironmentCredential authentication unavailable. Environment variables are not fully configured.
Visit https://aka.ms/azsdk/python/identity/environmentcredential/troubleshoot to troubleshoot this issue.
ManagedIdentityCredential: Unexpected content type "text/plain; charset=utf-8"
Content: SSO failure: unable to retrieve a token. Error Token service emacdonald3. Token not found
To mitigate this issue, please refer to the troubleshooting guidelines here at https://aka.ms/azsdk/python/identity/defaultazurecredential/troubleshoot.
File "/home/azureuser/cloudfiles/code/test.py", line 6, in
credential.get_token("https://management.azure.com/.default")
azure.core.exceptions.ClientAuthenticationError: DefaultAzureCredential failed to retrieve a token from the included credentials.
Attempted credentials:
EnvironmentCredential: EnvironmentCredential authentication unavailable. Environment variables are not fully configured.
Visit https://aka.ms/azsdk/python/identity/environmentcredential/troubleshoot to troubleshoot this issue.
ManagedIdentityCredential: Unexpected content type "text/plain; charset=utf-8"
Content: SSO failure: unable to retrieve a token. Error Token service emacdonald3. Token not found
To mitigate this issue, please refer to the troubleshooting guidelines here at https://aka.ms/azsdk/python/identity/defaultazurecredential/troubleshoot.

To Reproduce
We tried to get the token in its simplest form using this piece of code
import os
import requests
msi_endpoint = os.environ.get("MSI_ENDPOINT", None)
msi_secret = os.environ.get("MSI_SECRET", None)
client_id = os.environ.get("UAI_CLIENT_ID", None)

print(msi_endpoint)
print(msi_secret)
print(client_id)

token_url = msi_endpoint + "?resource=https://management.azure.com"
headers = {"secret": msi_secret, "Metadata": "true"}
resp = requests.get(token_url, headers=headers)
resp.raise_for_status()
access_token = resp.json()["access_token"]

print(access_token)

It works for every user except for this one. He is getting this error

Exception has occurred: HTTPError
404 Client Error: Not Found for url: http://<IP_ADDRESS>:46808/MSI/auth?resource=https://management.azure.com
File "/home/azureuser/cloudfiles/code/test.py", line 14, in
resp.raise_for_status()
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://<IP_ADDRESS>:46808/MSI/auth?resource=https://management.azure.com
content='SSO failure: unable to retrieve a token. Error Token service emacdonald3. Token not found'

All the VM have been created using the same configurations, and every users have Owner permissions on the tenant.
The Azure ML Workspace uses a User Assigned Identity that has Contributor role on the tenant
Any help would be appreciated
Expected behavior
User is able to retrieve the ManagedIdentity

Hi @gregoireIL, thank you for opening an issue! I'll tag some folks who should be able to help; we'll get back to you as soon as possible.

Thanks for reaching out. Given it is a user assigned MI, you need to specify the client id in your request.
You can get more details on https://learn.microsoft.com/en-us/azure/machine-learning/how-to-identity-based-service-authentication?view=azureml-api-2&tabs=python.

Like this? The client id is None when I print it
def get_token_rest():
    """
    Retrieve an access token via REST.
    """

    access_token = None
    msi_endpoint = os.environ.get("MSI_ENDPOINT", None)
    msi_secret = os.environ.get("MSI_SECRET", None)

    # If UAI_CLIENT_ID is provided then assume that endpoint was created with user assigned identity,
    # # otherwise system assigned identity deployment.
    client_id = os.environ.get("UAI_CLIENT_ID", None)
    if client_id is not None:
        token_url = (
            msi_endpoint + f"?clientid={client_id}&resource=https://storage.azure.com/"
        )
    else:
        token_url = msi_endpoint + f"?resource=https://storage.azure.com/"

    logging.info("Trying to get identity token...")
    headers = {"secret": msi_secret, "Metadata": "true"}
    resp = requests.get(token_url, headers=headers)
    resp.raise_for_status()
    access_token = resp.json()["access_token"]
    logging.info("Retrieved token successfully.")
    return access_token

/unresolve

Have you tried this?
client_id = os.environ.get('DEFAULT_IDENTITY_CLIENT_ID')
:)

From what we have found permissions to key vault take until Friday to propagate on azure ml computes. Its the second time this is happening to us.

Seems like it works.
I will close the issue and please feel free to open a service ticket for the issue that the permissions take a long time to propagate.


Internal server error while calling personal drive children endpoint for user without access to OneDrive

While calling endpoint for personal drive children:
https://graph.microsoft.com/v1.0/me/drive/root/children?filter=folder%20ne%20null&top=30&%24skiptoken=
For the user that does not have access to OneDrive 500 status is being returned.
Category

[ ] Question
[ ] Documentation issue
[x] Bug

Expected or Desired Behavior
The endpoint should return 403
Observed Behavior
Yesterday (6th of May 2020) it was working fine and was returning expected 403, but starting from today (7th of May 2020) it started to fail with 500

Date: Thu, 07 May 2020 10:33:13 GMT
request-id: 313e5f56-1a0e-4e42-80c6-10fa3b99b371
client-request-id: 313e5f56-1a0e-4e42-80c6-10fa3b99b371
x-ms-ags-diagnostic:
`{"ServerInfo":{"DataCenter":"West Europe","Slice":"SliceC","Ring":"5","ScaleUnit":"003","RoleInstance":"AGSFE_IN_61"}}"

Steps to Reproduce
Call https://graph.microsoft.com/v1.0/me/drive/root/children?filter=folder%20ne%20null&top=30&%24skiptoken= with a user that does not have access to OneDrive or Sharepoint

Thanks for your feedback. If you remove the skiptoken query argument with empty value, does that fix the issue?

@chackman, unfortunately, no, it's still the same.

Thanks for your feedback. Could you please also provide the request id and date / time for a request that doesn't have a skipToken query argument, e.g.
https://graph.microsoft.com/v1.0/me/drive/root/children?filter=folder%20ne%20null&top=30


Region geometry bug in FD

It seems like FD is multiplying new region-geometry when serialising to .struxml...
Originally posted by @andosca in https://github.com/strusoft/femdesign-api/issues/334#issuecomment-1112327211

119964


[JENKINS-63146] Honor ibm.system.encoding property in passphrase file

JENKINS-63146 Honor ibm.system.encoding property in passphrase file
Consistent with usage in other locations in the plugin but requires that a property be set on the agent JVM.  Setting a property on the agent JVM may be a little more complicated than setting an environment variable.  May require setting the argument in the advanced section of the agent startup rather than in the agent properties.
Checklist

[x] I have read the CONTRIBUTING doc
[x] I have referenced the Jira issue related to my changes in one or more commit messages
[ ] I have added tests that verify my changes
[x] Unit tests pass locally with my changes
[x] I have added documentation as necessary
[x] No Javadoc warnings were introduced with my changes
[x] No spotbugs warnings were introduced with my changes
[ ] I have interactively tested my changes

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)

Closed - not tested by Randall Becker and cannot be tested by Mark Waite (no access to z/OS)


helm dependency update returns 0 for failed update

All *nix systems return a non-zero error code when the command fails.  I expect the same behavior from helm when an dependency update fails.
Steps to repro:

create a requirements.yaml for an upstream dependency that doesn't exist

run 'helm dependency update --debug <chart name>'
actual output:

bash-4.3# linux-amd64/helm dependency update --debug kafka
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "stable" chart repository
...Successfully got an update from the "atlas" chart repository
...Unable to get an update from the "local" chart repository (http://localhost:8879/charts):
	Get http://localhost:8879/charts/index.yaml: dial tcp: i/o timeout
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Downloading zookeepers from repo http://atlas.cnct.io
WARNING: entry not found (skipped)

run 'echo $?'
actual output:

bash-4.3# echo $?
0

expected output:
bash-4.3# echo $?
1

We've been treating download failures on helm dependency update as warnings, not errors. And warnings emit an exit code of 0. Based in your feedback, I'm wondering if we should consider download failures to be an error instead.

I would consider a download failure to be a helm error, the operation as a whole has not created the desired state of a fully satisfied parent package.  its probably not helm's fault but that doesn't mean we succeeded.
I hit this while setting up a CI pipeline for a chart with a dep.

awesome!  thanks!


Add RP to layout

I will not lie: this was not enjoyable. With the realization that this page might be shuffled around to a new spot in the TOC, it was a delicate act balancing Razor pages and traditional MVC without getting too intrusive about it.
As such, I:

Included a note at the top of the document outlining the subtle differences, so I can just casually reference them later and don't have to explain which is which
Replaced wording of "views" with "pages or views"
Changed controller wording to "the folder where the handler method (or controller) exists."
I also updated the _Layout.cshtml sample file. It's a little different, two years later.

I expect some back-and-forth about this—let me know what you think, @Rick-Anderson.
Fixes #8030

Thanks for the review, @Rick-Anderson. I like it!


Simple easy helpful change

At lexer.py, line 225, please output filename, otherwise the user does not know which file is causing the error.
Suggestion:
throw new FormatException(string.Format("Indentation of {0} line {1} is incorrect .", filename, LineNumber));

Implemented in 62aea91888299504f497e60d448a9a68aeac2d3c.


Comments are moved in files with CRLF line endings

My TypeScript source files have some eslint ignore lines in them next to imports at the top of the file; but when I run import-sort on them, it moves them after all of the imports so they no longer apply to the correct lines and cause my eslint rules to give me errors.
before:
import * as React from 'react'
// eslint-disable-next-line no-restricted-imports
import Flexbox from 'flexbox-react'
import { connect } from 'react-redux'
import {
  Redirect,
  Route,
  RouteComponentProps,
  Switch,
  withRouter
} from 'react-router'

after:
import Flexbox from 'flexbox-react'
import * as React from 'react'
import { connect } from 'react-redux'
import {
  Redirect,
  Route,
  RouteComponentProps,
  Switch,
  withRouter
} from 'react-router'

// eslint-disable-next-line no-restricted-imports

The files have CRLF line endings because I'm on Windows. If I save them with LF line endings and then run import-sort, it has the expected result:
// eslint-disable-next-line no-restricted-imports
import Flexbox from 'flexbox-react'
import * as React from 'react'
import { connect } from 'react-redux'
import {
  Redirect,
  Route,
  RouteComponentProps,
  Switch,
  withRouter
} from 'react-router'

We are having the same issue on the VS Code extension https://github.com/amatiasq/vsc-sort-imports/issues/57, changing the line endings to LF works fine.

node already exposes os.EOL maybe we should use that instead?

@jquense I think there is no guarantee the system EOL is the file's EOL. On cross-OS teams there is usually a convention for all to use the same EOL style whatever system each one uses.


Download config.json for conversion script

Additionally downloads the config.json file, which is required if we want to convert Lit models back to HF and use the checkpoint via transformers. If this is merged, we can then simplify the tutorial in #959
(Note that it's also downloading the tokenizer_config.json if it's present. Imho it's a super tiny file and doesn't hurt to download it if it exists; we may use it somewhere later in the future, who knows.)
Closes #919

Redundant if we implement #923

Addressed your suggestion and updated the docs.


JSON-RPC error: transport error: Couldn't connect to host: Resource temporarily unavailable

often appear follow error:
failed to fetch block 779834, retrying in 2s: JSON-RPC error: transport error: Couldn't connect to host: Resource temporarily unavailable (os error 11)

BTC node issue, unrelated to ord.


When I use the PhotoViewGalleryPageOptions.customChild , the scaleState doesn't work

I don't know if I use the controller correctly. but  it still didn't work when i have tried many times? could you please pointed out where my fault is？
final item = widget.galleryItems[index];
    return PhotoViewGalleryPageOptions.customChild(
      scaleStateController: scaleStateController,
      child: GestureDetector(
        behavior: HitTestBehavior.translucent,
        onTap: () {
          Navigator.of(context).pop();
        },
        onDoubleTap: () {
          scaleStateController.scaleState = PhotoViewScaleState.zoomedOut;
        },
        child: CustomImage(
          imageSize: ImageSize.original,
          width: MediaQuery.of(context).size.width,
          imageUrl: item,
        )
      ),
      initialScale: 0.5,
      minScale: PhotoViewComputedScale.contained * 1,
      maxScale: PhotoViewComputedScale.covered * 2,
    );
  }

what i want to deal is to zoom the pic by doubleTap

There is a couple of problems with this usage.

In this way, you are interfering directly with how the scale state cycle inside photo view is handling double tap. We have to ways to customize the double-tap gesture cycle, one of them is passing a custom scaleStateCycle.

zoomedIn and zoomedOut are generic values for any state not controlled by the scale state cycle, one should never set it as one of these two values.

If you intend to set the double-tap gesture to have totally different behavior than the one we have, you have to pass an empty function as scaleStateCycle on PhotoView's constructor and wrap PhotoView in a gesture detector, not use a child.

There is a couple of problems with this usage.

In this way, you are interfering directly with how the scale state cycle inside photo view is handling double tap. We have to ways to customize the double-tap gesture cycle, one of them is passing a custom scaleStateCycle.
zoomedIn and zoomedOut are generic values for any state not controlled by the scale state cycle, one should never set it as one of these two values.
If you intend to set the double-tap gesture to have totally different behavior than the one we have, you have to pass an empty function as scaleStateCycle on PhotoView's constructor and wrap PhotoView in a gesture detector, not use a child.

Having read your reply, i just want to have the double tap behavior like yours.PhotoViewGalleryPageOptions is normal, but once i added the customChild,it didn't work.I have deleted the scaleController.

Yeah, the problem is how you did it. You don't need to add an internal GestureDetector to do that.

I removed my GestureDetector, the only trigged event is  the default doubleTap event. it did worked,but the image remains still...

Now I see something else.
Your initialScale is a absolute number (0.5) while minScale and maxScale are relative ones (PhotoViewComputedScale.contained and PhotoViewComputedScale.covered).
This is a problem since you cannot determine if half of the size of the image is bigger than half of the container smallest side or smaller than twice the size of the biggest size of the container).
also, I have to ask your code without the gesture detector.
As a resource, you can try to pass childSize to the page options as MediaQuery.of(context).size (I assume you are using the size of the screen as a guide).

  PhotoViewGalleryPageOptions _buildItem(BuildContext context, int index) {
    final item = widget.galleryItems[index];
    return PhotoViewGalleryPageOptions.customChild(
      scaleStateCycle: customScaleState,
      child: SupermonkeyImage(
        imageSize: ImageSize.original,
        width: MediaQuery.of(context).size.width,
        imageUrl: item,
      ),
      initialScale: PhotoViewComputedScale.contained * 1,
      minScale: PhotoViewComputedScale.contained * 1,
      maxScale: PhotoViewComputedScale.covered * 2,
      childSize: MediaQuery.of(context).size
    );
  }

PhotoViewScaleState customScaleState(PhotoViewScaleState actual) {
  print('actual--');
  print(actual);
  switch (actual) {
    case PhotoViewScaleState.initial:
      return PhotoViewScaleState.covering;
    case PhotoViewScaleState.covering:
      return PhotoViewScaleState.originalSize;
    case PhotoViewScaleState.originalSize:
      return PhotoViewScaleState.initial;
    default:
      return PhotoViewScaleState.initial;
  }
}

when i double tapped, the 'actual' has been printed three times.

Unfortunately, I have an another question..if I set the initialValue is lower than container * 1, or bigger than it, it works now.But once I set it container * 1, it remains unchanged, cause doubleTap recovered it to originalSize. Then how can I zoom out when I first preview it :(

It is really hard for me to understand to me what you are trying to achieve here. What is "container * 1"?

Due to my limited English, I am sorry for what I described.Please let me re-describe my question:
Once I set the initialScale is lower than PhotoViewComputedScale.contained * 1.0 or bigger than it, the image will change bigger or smaller which means double tap works.
but once I set the initialScale to PhotoViewComputedScale.contained * 1.0.  minScale is PhotoViewComputedScale.contained * 1.0 too, and the maxScale is PhotoViewComputedScale.covered * 2, When I double tapped the image, the nextScaleStateCycle was triggered, but the image didn't change. I guess it's because nextScaleStateCycle recovered the scale to originalSize.
I need to set the image fit the screen's width when I firstly previewed the image, it's necessary to set PhotoViewComputedScale.contained * 1.0 . So how can I change the image when I set the initialScale PhotoViewComputedScale.contained * 1.0 ?
Here is my code:
PhotoViewGalleryPageOptions _buildItem(BuildContext context, int index) {
 final item = widget.galleryItems[index];
 return PhotoViewGalleryPageOptions.customChild(
   scaleStateController: _controller,
   child: Container(
     alignment: Alignment.center,
     child: Scrollbar(
         child: SingleChildScrollView(
       scrollDirection: Axis.vertical,
       child: Container(
         child: CustomImage(
                     imageSize: ImageSize.original,
                     imageUrl: item,
                     fit: BoxFit.fitWidth,
                     alignment: Alignment.center,
                     placeholder: (context, url) {
                       return CustomImage(
                         width: MediaQuery.of(context).size.width,
                         imageUrl: item,
                         fit: BoxFit.fitWidth,
                         alignment: Alignment.center,
                       );
                     },
                   ),
     )),
   ),
   ),
   scaleStateCycle: nextScaleStateCycle,
   initialScale: PhotoViewComputedScale.contained * 1,
   minScale: PhotoViewComputedScale.contained * 1,
   maxScale: PhotoViewComputedScale.covered * 2,
//      childSize: MediaQuery.of(context).size
 );
}

PhotoViewScaleState nextScaleStateCycle(PhotoViewScaleState actual) {
 print('actual--');
 print(actual);
 switch (actual) {
   case PhotoViewScaleState.initial:
     return PhotoViewScaleState.covering;
   case PhotoViewScaleState.covering:
     return PhotoViewScaleState.zoomedOut;
   case PhotoViewScaleState.originalSize:
     return PhotoViewScaleState.initial;
   case PhotoViewScaleState.zoomedIn:
   case PhotoViewScaleState.zoomedOut:
     return PhotoViewScaleState.initial;
   default:
     return PhotoViewScaleState.initial;
 }
}

这英文。。太绕了。我昨天下的源码，今天才刚刚看的。我猜是你的 nextScaleStateCycle 设置有问题。doubleTab 之后，进入到 covering 状态。你换成 zoomedIn 不知道可不可以 @cherrybiu
case PhotoViewScaleState.initial:          return PhotoViewScaleState.zoomedIn;

这英文。。太绕了。我昨天下的源码，今天才刚刚看的。我猜是你的 nextScaleStateCycle 设置有问题。doubleTab 之后，进入到 covering 状态。你换成 zoomedIn 不知道可不可以 @cherrybiu
case PhotoViewScaleState.initial: return PhotoViewScaleState.zoomedIn;

这些状态都试了，不行的

Since I dont speak chinese, is this issue still going on? We may change the name of things on #322 since initialScale is not the best one.


Question: Local Livestream Clarification

Hey Bropat,
Awesome work on this eufy security extension! I know you are working on the wiki / docs but I had a question. The README file states that this supports

Start livestream (hls; supports also local livestream)
Stop livestream (hls)".

I have a Eufy wired 2k doorbell Wired Doorbell 2k (T8200).  Is this livestream local or through the cloud (RTMP?). If this is through the local device directly, I would love to stream it continuously (almost like a poor mans RTSP stream). The only reason I have not done this is I am not sure if it is through the cloud (thus using my internet cap from my ISP). I have seen other Eufy extensions that will give you a URL but it is a cloud web address.

Hi @wjbridge,
If the adapter establishes a successful connection to the station/device via P2P (visible through an info message in the log), then the stream is local, otherwise the stream via the cloud in RTMP is used as a fallback.
What I have seen so far from the Wired Doorbell, this allows a maximum P2P livestream of 10 minutes, then it disconnects.


Child element description

In the guidelines the description of the child elements is not correct: all child elements have the text of the mother element and not their own text

Could you please post a link to an example?

On https://music-encoding.org/guidelines/v4/elements/manifestation.html, when you look at the "may contain" facet in "by class" mode, you will get the content of //manifestation/desc, not of the descs of those direct child elements. My fault :-)

this mistake is also to find in the description of the elements for example under model.textPhraseLike.limited (and other "models"); see for example  Element
https://music-encoding.org/guidelines/v4/elements/decodesc.html


[SG-133] fixing proto file paths for sdk 0.47

Moving the proto files so that the OS path matches package name
Reason: https://github.com/cosmos/cosmos-sdk/blob/main/UPGRADING.md#gogoproto-import-paths

Closing in favor of  https://github.com/public-awesome/stargaze/pull/871


CLI?

At the moment the following is available:
python -m demesdraw.size_history ...
# and
python -m demesdraw.schematic ...

The CLI is currently half baked. I'm in two minds here... We could either (1) do something minimal for folks to quickly look at their demes graph, and customisation must be done through the python API; or alternately (2) do everything the API does, and possibly more (like multi panel figures).
And possibly the CLI should instead be driven like:
python -m demesdraw ...

Maybe with subcommands.

I yanked out the CLI. For now.


Replace sources with https://github.com/cquiroz/scala-java-time and release new version

I just spent many hours trying to figure out why an application I'm trying to build is behaving differently between sbt 1.28 and sbt 1.3.13 and figured out that in sbt 1.3.13 this library was placed before scala-java-time in the compile classpath and then throwing errors during compile.
As this project is hosted under the scala-js namespace, developers expect the library to be more complete than the one linked at https://github.com/cquiroz/scala-java-time . They would not expect that the "official" library is making problems.
To follow the principle of least surprise, I suggest the following:
Please coordinate with @cquiroz and replace the code in this library with his,
then release a new version 1.0.1 to maven central.
For reference, this is the problem I've stumbled upon:
https://stackoverflow.com/questions/65063755/scalajs-zio-program-works-with-sbt-1-2-8-but-not-1-3/65275462#65275462

Have you read the README of this project?

Yes, and by the status of this project (and its prominent org.scalajs organization name),
in its current state, its making more trouble than helping.
People expect projects under the org.scalajs organization to be somekind stable
and complete, especially if they have a 1.0 version.

I understand what you're saying. However, I still disagree with the solution you're proposing.
We marked this project as deprecated and clearly pointed to its replacement. If the "official" project points to another one, that makes that project official. We are not maintaining this project. We haven't been for a while. The other project is maintained, by maintainers who actually use it. We don't use any of this stuff. We don't have the capacity or the knowledge to maintain it. So we won't.

Reading trough this conversation, it is not 100% clear to me what @domdorn is asking. @domdorn, are you asking for:

Ongoing development* in this repository supervised by the Scala.js core maintainers.
An even clearer way for users to see that this repository should not be used.
Something else?

I'm afraid (as @sjrd pointed out), we cannot offer (1) due to mere resource/time constraints.
As far as (2) goes, I think we are all on the same page that we should make it as clear as possible that this project should not be used.
However, I'm not sure what you are proposing (forward merging sources) is the most effective solution: This is quite the overhead for the Scala.js core maintainers and likely to be forgotten, basically putting us in the same spot we are now 6 months down the line (two libraries are published, one of them is out of date).
Options I can see to redirect devs to the right artifact:

GitHub: Archive this repository. This should make it very clear for folks arriving from GitHub that this is not to be used (GitHub seems to display a message bar).
Maven: We could set the relocation field in a last version to publish (also see MNG-3952, MNG-5604). I do not know to what extent package managers actually warn if this is present, but at least the metadata would be correct.

*by that I mean actually development, not just procedural merging of code that lives somewhere else.

The problem is not people finding this library through github / google, cause they will already see the deprecation warning and can already chose to go down a different path.
The problem comes
1.) from people that are using their IDE or
2.) from people that use websites like  https://mvnrepository.com/artifact/org.scala-js/scalajs-java-time to look for dependencies with a reasonable name to solve their problem.
3.) from people using software like scala-steward to keep their dependencies up2date
4.) from people using existing projects, upgrading versions of other tools (e.g. sbt 1.2 -> 1.3) and suddently run into problems.
I propose the following steps:

offer @cquiroz to move his project under the official scalajs umbrella with the organizationId and artifactId of this repo, so that one working library under the org.scalajs namespace exists, then release a new version so that people will upgrade to it.
if @cquiroz does not want to move his project, then
2.1a mark all code as deprecated - or something similar which will print out a compiler warning, stating to read the readme of this project and migrate away
2.1b alternatively remove all code, so that users will download a empty jar and because of the resulting compile errors "fail fast" and will look for a solution
2.2 release a new version with the deprecated methods/removed methods
2.3 and the maven relocation field turned on to point to @cquiroz repository.

@gzm0: So what I'm asking for is a mixture of 1, 2, and 3.
Imho the perfect solution would be 1, where @cquiroz would develop here and gets as much help as possible from scalajs maintainers.
or
2: an even clearer way that this code should not be used, as outlined above (2.1 - 2.3)
3: if we can't bring @cquirez to move his code here (1) AND we are not able to somehow make it foolproof to not use this library anymore (2) (through compiler warnings and/or maven things), then a solution would be to simply (3)

regularly pull changes from @cquirez repo to this one
change the organizationId and artifactId
release new versions whenever he releases

is not an option. We (I at least) want this code to be maintained outside of the scala-js organization, under a different organization, because we want to make it clear that it's OK for third-party maintainers to develop quality JDK extensions (and other kinds of libraries). Bringing one under org.scala-js would make the case even stronger that what's not in org.scala-js is not to be trusted. We don't want that to happen.
..
2.1 Unfortunately, that is technically not possible, because calls to JDK APIs compile against the original JDK .class files, which don't have the deprecations.
2.1.b How is that better than what you ran into?
"would be to simply [pull changes and do work]". That's just busywork. No thank you.

The only possibility I see here would be:

Someone make sure that scala-java-time contains everything that this library contains (so that "upgrading" does not break anything)
Publish a version 2.0.0 with no sources and a dependency on scala-java-time (and a relocation field), which would act as a meta-package.

Just to provide my POV on this:
@domdorn In the list of problems you describe, 1 - 3 are essentially a missing deprecation "flag" from the maven side (assuming IDEs pull in stuff via maven). I agree that we should fix this. @sjrd's meta-package proposal seems to address this (as good as we can).
Problem 4 is simply an instance of cargo-culting. I do not see how we can fix this.
As far as the proposed steps are concerned:

I second @sjrd's opinion. Maven organizations should reflect actual organizations. Further, this would set a precedent that it is not OK to discontinue/fork a project. IMHO this is not a message we'd like to send.

IMO this is what we should do on a higher level, unfortunately only 2.3 (IMO) actually addresses the problem (primarily due to technical constraints).

This is merely a poor mans way of implementing (1) and causes an untenable amount of busywork. I really do not think this is a good idea.

hmm.. could we hook something into the linker maybe?

No, definitely not. This is not the linker's job.


Valid shell command fails silenty when using the exec dispatch

The bug
The following shell command would succeed in sh
(command; (test $? == 0) && doSomethingOnError)) | doSomethingWithTheOuput

But when set as a dispatch through a keybind, it wont run at all. Which is confusing.
bind = , key, exec, (command; (test $? == 0) && doSomethingOnError)) | doSomethingWithTheOuput

Cause
After a little bit of digging, I found that it fails because hyprland is injecting some variables before the command by modifying the command itself, which is leading to a syntax error.
[LOG] Executing WAYLAND_DISPLAY=wayland-1 DISPLAY=:0 (true; (test $? == 0) && notify-send -a title "text")

Workaround
Putting a ; before the command removes the syntax error, but that's not the best solution and just a frustrating experience overall.
bind = , key, exec, ;(command; (test $? == 0) && doSomethingOnError)) | doSomethingWithTheOuput

Fix
If possible, inject the variables without modifying the command itself. Basically, make no assumption about the command.

you can now use execr for no parsing 6e16627cbcb5d4712195c97e106f2198076c8aff


Disallow some dependency configuration combinations

Illegal to mix variant aware attributes or capabilities with configuration / artifacts
Illegal to mix configuration and artifacts

@melix Exception updated, checkstyle happy.
For the perf impact, I hope not. After all it only adds logic if you specify a configuration, artifact, attribute or capability, which is not the most common use case.


Fix the issue#4138

Fix the issue #4138
Redefine the w and w_t for improving the efficiency in case of handling sparse IndexedSlices objects

Can one of the admins verify this patch?

@lukaszkaiser Please take a look.

Looks good to me, thanks!  (We should merge it anyway, I think, just curious).

@lukaszkaiser The issue shows it gives a speedup and set a contribution welcome  tag. So, I think it maybe help to do this. At least, it can'b be worse.

Let's merge this! Is anything blocking it?

@lukaszkaiser I don't know, what happened when you merge?  My branch is still has the commit

Can one of the admins verify this patch?

@tensorflow-jenkins test this please

@lukaszkaiser, based on your comments I think you might have meant to merge this and closed the PR instead? I'm re-opening it and testing it :)

@danmane ooh..I got your point! 👍

@lukaszkaiser Could you merge it? :)

I'm not authorized to merge. vrv -- could you merge?

Please merge.


HDDS-8875. Reduce duplicate delete transactions write to the DB

What changes were proposed in this pull request?
DeleteBlockCommands can be sent out of order, so even DeleteBlockCommand's transaction is smaller than container's deleteTransactionId, we cannot tell it's duplicate or not. we must put this may be committed transaction to the RocksDB.
However, if we know that transaction has been executed successfully, we can skip these duplicate transactions. This PR caches the most recently executed transactions in memory. Through this cache, we can avoid duplicate transactions from being submitted, which can effectively reduce the waste of system resources.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8875
How was this patch tested?
unit tests

/pending conflict


Setup prometheus

[ ] also connect ubiquiti with prometheus

/dog

For sure

/label letsgo

Closed by https://github.com/axeII/home-ops/pull/144.


Minor typos in chap.19 of book1 (draft of August 3, 2021)

p.630, sec.19.1.2: $\ell (f(\mathbf{x}), y)$ -> $\ell (f(\mathbf{x}), \mathbf{y})$

p.630, sec.<IP_ADDRESS>: semi-supervised -> self-supervised

fixed, thanks


Docs for exporting environment do not work on Intel Mac

In the installation commands section of the README, the docs state to run:
./install-rust-toolchain.sh --toolchain-version <IP_ADDRESS>
. export-esp.sh

However, the export command doesn't seem to work on my x86 Mac:
% . export-esp.sh
.: no such file or directory: export-esp.sh

The file is present in the current working directory:
% ls export-esp.sh
export-esp.sh

I can solve this by running:
. ./export-esp.sh

or
source export-esp.sh

Thoughts? Am I missing something or is this a typo? Thanks!

Hi! Thanks for opening the issue, do you mind detailing your environment (macOS version, shell...). Using . export-esp.sh works fine in macOS Monterey 12.5 on M1 with bash 3.2.57 and fish 3.4.1.  I am happy to make the change to . ./export-esp.sh as it also works, but I would like to understand what is causing the issue.

Certainly!
I'm using macOS Monterey 12.6 on Intel, with:

zsh 5.9 (x86_64-apple-darwin21.3.0)
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin21)

My terminal is configured to use zsh. Perhaps that is the difference?
Let me know if I can provide any other info.

Hi! Would you mind trying with no zsh?

Thanks for all your tests! We will merge #156 to solve the issue for zsh users.

Much appreciated!

Now that https://github.com/esp-rs/rust-build/pull/156 and https://github.com/esp-rs/rust-build/pull/165 are merged, this issue is now solved!


Mod is incompatible with canvas renderer for Fabric

Can you please also report it to them and link the issues.

Linking issue for Canvas https://github.com/vram-guild/canvas/issues/407


cli(ticdc): refactor cdc cli changefeed cyclic to use api v2

What problem does this PR solve?

Issue Number: close #5812
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
refactor cdc cli changefeed cyclic to use api v2

/cc @sdojjy @asddongmen

@crelax, jenkins-ticdc/verify failed. Please execute make check to solve the lint problems.

@crelax, jenkins-ticdc/verify failed. Please execute make check to solve the lint problems.

Hi xinyu, this pr is not going to be merged for now, since it relies on the refraction of other changefeed cli. It will be tested and processed to merge then

cli no longer supports changefeed cyclic


Update sql-database-business-continuity.md

add a link to the details about recovery time

@allenwux : Thanks for your contribution! The author, @anosov1960, has been notified to review your proposed change.

#sign-off

@CarlRabeler: I'm sorry - only the author of this article, @anosov1960, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Can I use that package as api?

I'm using React for Frontend and Laravel for the Backend.  Now I need to integrate Nagad to accept payment.  Can I use that package to create a Nagad payment API? Is it possible?

Yep, we can use it as api.


Accept and pass along Fedora base url

GitHub Issue: https://github.com/Islandora/documentation/issues/926
Related to:

https://github.com/digitalutsc/islandora/tree/fedora_url
https://github.com/Natkeeran/Crayfish-Commons/tree/container_name

What does this Pull Request do?
Instead of setting the Fedora base url in the microservice configuration we can instead provide it in the message. It is possible that we retain the configuration argument as a fall back, but if you have multiple containers for a multi-site you might want to dynamically change the base url per request.
This work relies on @Natkeeran's work in the above branches to send the event and receive the event.
I went with the header X-Islandora-Fedora-Endpoint but this could be a configuration parameter if we like.
How should this be tested?
I did not test this with the derivative connectors as that would require a full playbook setup which I did not have.

How I tested this was to stand up islandora-playbook.
I had a synced folder into my playbook.# Configure sync directory
config.vm.synced_folder ".", home_dir + "/islandora"
config.vm.synced_folder "/my/Alpaca/directory", home_dir + "/Alpaca"

In vagrant (vagrant ssh) I didcd /home/ubuntu/Alpaca
sudo ./gradlew clean build install

Then I removed the old Alpaca and installed the new one./opt/bin/karaf/client
> feature:uninstall islandora-indexing-fcrepo islandora-indexing-triplestore
> repo-remove islandora-karaf-1.0.1
> logout
sudo service karaf stop
sudo rm -rf /opt/karaf/data/*
sudo service karaf start
/opt/karaf/bin/client
> repo-add mvn:org.apache.camel.karaf/apache-camel/2.20.4/xml/features
> repo-add mvn:org.apache.activemq/activemq-karaf/5.15.0/xml/features
> repo-add mvn:org.fcrepo.camel/fcrepo-camel/5.0.0/xml/features
> repo-add mvn:org.fcrepo.camel/toolbox-features/5.0.0/xml/features
>  repo-add file:/home/ubuntu/Alpaca/karaf/build/resources/main/features.xml
> feature:install fcrepo-service-activemq
> feature:install fcrepo-service-camel
> feature:install islandora-http-client
> feature:install islandora-indexing-triplestore
> feature:install islandora-indexing-fcrepo
> feature:install islandora-connector-derivative
> logout
sudo service karaf stop
sudo service karaf start

This should restart the derivative routes as well.
I also edited the log configuration to see my logging messages.sudo vim /opt/karaf/etc/org.ops4j.pax.logging.cfg

I edited the last line of the file - log4j.logger.ca.islandora.camel=DEBUG, islandora
 + log4j.logger.ca.islandora.alpaca=DEBUG, islandora

Now you need to replace your islandora with the branch above, go to the Islandora Settings form and add your Fedora base url.
Then you can create a Repository Item and you should see a line in your /opt/karaf/data/logs/islandora.log like:2019-10-24 15:07:27,849 | DEBUG | -fcrepo-content] | FcrepoIndexer                    | 56 - ca.islandora.alpaca.islandora-indexing-fcrepo - 1.0.2 | Received Node event for UUID (b096a183-6ca9-4aa8-95e5-d30a5a246e67, jsonld URL (http://localhost:8000/node/1?_format=jsonld, fedora base URL (http://<IP_ADDRESS>:8080/fcrepo/rest)

Interested parties
@Islandora/8-x-committers especially @Natkeeran

@dannylamb your comments lead me to believe we need to make the differentiation between the "Base URL of a Fedora instance" and a "single Fedora resource URI" clearer or others will get confused. I'm still fighting with this and may end up backing out if these annotations don't help me out. But either way I'll try to make it clearer.

Okay, I think this is ready. I was able to get it working passing stuff around and still indexing in Fedora and creating derivatives. I updated the instructions at the top to get the various dynamic routes to regenerate after you install the new islandora-connector-derivative.

@whikloj
Sorry for lingering this one.  Is is possible for you to rebase this one.

I'm good with the changes you made @whikloj :+1:

do you need someone to test this?

@elizoller sure, if you want to give it a test that would be great.

I've managed to get this installed and working with all the other pieces.  I'm happy to pull all this work in, but Travis is not happy :cry:

Also, if you want tests to pass on the main islandora repo, this'll need to get merged beforehand: https://github.com/Islandora/islandora/pull/747

I feel like we should consider removing Oracle Java from our testing matrix, but I'll spin up a Travis box and see if this is a simple fix.

@whikloj I'm fine with sticking to openjdk for testing

@dannylamb fixed


400 Bad Request

Hello,
I am getting this error when I try to use call function.
ERROR #22: The requested URL returned error: 400 Bad Request
$sh = new API;

$sh->setup(['API_KEY' => $this->api_key, 'API_SECRET' => $this->api_secret, 'SHOP_DOMAIN' => session('shop'), 'ACCESS_TOKEN' => session('access_token')]);

$call = $sh->call(['URL' => 'products.json', 'METHOD' => 'GET', 'DATA' => ['limit' => 5, 'published_status' => 'any']]);

return $call;

Hi @mohdaftab ,
I am facing same issue whenever i am passing Data then it throwing ERROR #22 , To solve this issue i have passed parameter with URL as query parameter
$call = $sh->call(['URL' => 'products.json?limit=5&published_status=any', 'METHOD' => 'GET', ]);
And it is working fine now. You can try this and if you got any other solution please also share.

I have solved it by commenting out these 2 lines in the api.php file
CURLOPT_FAILONERROR     => $request['FAILONERROR'],
CURLOPT_VERBOSE         => $request['ALLDATA'],

@gurjanjua's solution worked for me.

ditto - @gurjanjua's solution was the ticket. Any idea why? This was working fine for us until now.

@gurjanjua solution worked. What gives?

The problem is that Shopify has updated their server standards: https://ecommerce.shopify.com/c/shopify-apis-and-technology/t/shopify-api-call-returns-a-http-400-error-with-html-from-google-484157
Basically, you are not allowed to pass body data with a GET request anymore. This wrapper isn't updated to handle that case yet. I was able to resolve in my code performing the call like this instead passing as 'DATA' (see commented out code).
$call = $sh->call(
	[
		'URL' => "/products.json?limit=$perPage&page=$i",
		'METHOD' => 'GET',
//		'DATA' =>
//			[
//			        'limit' => $perPage,
//				'page' => $i
//			]
		]);

@calebl THANK YOU! This worked for me

@calebl It's work for me Thank You


LibWeb: Multiple fixes for WebCryptoAPI derive bits/keys

Small changes that have a great impact on tests. I have updated the SubtleCrypto IDL because I think the spec was updated to make length parameter of deriveBits optional.
Additionally, I have corrected some behaviours when the requested length is not a multiple of 8 or isn't indicated at all.
I haven't checked extensively, but I think this should get derive_bits_keys to almost 100%, so this fixes ~3300 tests.

Commit that changed how the length works: https://github.com/w3c/webcrypto/commit/c0e18561921af8bd9ac70105d3fba1e09e80c08d

Seems like an urelated test crash


fix: Import the blocks from root rather than src

@johno @bkrausz Here you guys go! Got to love those one-line changes 😁
Fixes #101

Thanks!