Generated schema contains unrenamed colliding column names

I'm using the latest master of diesel and diesel_cli.
After https://github.com/diesel-rs/diesel/pull/1897 was merged, the generated schema causes compilation errors for me, such as:
error: expected identifier, found keyword `type`
    --> database/src/schema/gen.rs:1489:50
     |
1489 |     joinable!(user_tokens -> user_token_types (type));
     |                                                  ^^^^ expected identifier, found keyword
help: you can escape reserved keywords to use them as identifiers
     |
1489 |     joinable!(user_tokens -> user_token_types (r#type));

I have to manually change the generated schema to this, to make it compile:
joinable!(user_tokens -> user_token_types (type_));

(In the db, the column is named type.)

As #1897 contains a test case for exactly this case I would like to see a reproducing example for this otherwise I consider this fixed.

As #1897 contains a test case for exactly this case I would like to see a reproducing example for this otherwise I consider this fixed.

Closed as we cannot reproduce that without details + the corresponding PR contains a test case for exactly the mentioned scenario.


How to get screenshot from a video path?

Hello, I try to use this package to get the thumbnail of videos by providing video paths. Using player.screenshot() seems not working.
Here is my code:
/// Get a video thumbnail from the local video file.
Future<Uint8List?> getVideoThumbnail(String videoPath) async {
  print("--- get video thumbnail from $videoPath ---");

  final player = Player();
  await player.open(Media(videoPath), play: false);
  await player.seek(Duration(milliseconds: 100));
  await player.pause();

  final thumbnail = await player.screenshot(format: "image/png");

  player.dispose();

  print("--- get video thumbnail done: $thumbnail ---");

  if (thumbnail != null) {
    return thumbnail;
  }

  return null;
}

I can see the video path, but the thumbnail returned from player.screenshot() is always null. Maybe it's because the code is problematic. If so, is there any correct  example  to take thumbnail of videos? Thanks in advance.

Need to attach VideoController before taking screenshot.

@alexmercerind what about getting image from a position on the video when the video is playing in the player

Need to attach VideoController before taking screenshot.

It's working, good to know.
But I find the screenshot process is slow. Say I want to build thumbnails for some videos in the same page. No matter I use a global player to generate screenshot for them separately, or initialize one controller and player for each video to take screenshot, the process could make the UI jam (I'm in debug mode). It's slower than directly read each video into Media and put each of them into a Video widget with separate VideoController, which won't even jam the UI.

It's slower than directly read each video into media and put each of them into a Video widget.

2 reasons:

We use package:image to encode screenshot's pixel buffer... and Dart is slower than C/C++.
The video playback happens through the GPU... where things are far more optimized. The video output that you see in the Video widget is not stored like a "screenshot" in the memory, but using OpenGL etc. specific primitives.

I personally use screenshot-to-file in my project... but it won't really work with our default libs since image encoders have not been enabled. I plan to replace current screenshot implementation with that one in new release... but honestly I'm too tired to figure out CI/CD now, so many attempts.

Good to know those details. I will try more solutions to deal with video thumbnails.


Same commands as to set up unified messaging?

These steps are identical from a powershell command perspective to setting up  the soon to be retired Unified messaging, is that to be expected?
https://blogs.technet.microsoft.com/nagshettykadwadi/2017/10/18/integrate-skype-for-business-server-with-exchange-online-unified-messaging-in-hybrid-scenario/

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

ID: ec8b8afb-b9ca-8136-b907-5bbff4c9dcf1
Version Independent ID: d4f68818-6fe6-5bb7-f108-e26a643f2cc7
Content: Configure Cloud Voicemail service for on-premises users
Content Source: Skype/SfbHybrid/hybrid/configure-cloud-voicemail.md
Product: skype-for-business-itpro
GitHub Login: @dstrome
Microsoft Alias: dstrome

@briandahlincoyne  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@briandahlincoyne thanks for pointing this out. I'll investigate further and get back to you.

@dstrome could you perhaps assist please.

Checking

@briandahlincoyne if you're referring to the new hosting provider command, the endpoint configuration is the same. We handle routing to the proper service via routing on the backend.


ProcessGroupNCCL.cpp:784, unhandled system error

(nanodet) simon@Simon:~/nanodet$ python tools/train.py config/nanodet-m-416.yml
[root][07-16 11:17:37]INFO:Using Tensorboard, logs will be saved in workspace/nanodet_m_416/logs
[root][07-16 11:17:37]INFO:Setting up data...
loading annotations into memory...
Done (t=16.84s)
creating index...
index created!
loading annotations into memory...
Done (t=0.72s)
creating index...
index created!
[root][07-16 11:17:55]INFO:Creating model...
model size is  1.0x
init weights...
=> loading pretrained model https://download.pytorch.org/models/shufflenetv2_x1-5666bf0f80.pth
Finish initialize Lite GFL Head.
GPU available: True, used: True
TPU available: False, using: 0 TPU cores
initializing ddp: GLOBAL_RANK: 0, MEMBER: 1/1
Traceback (most recent call last):
File "tools/train.py", line 100, in
main(args)
File "tools/train.py", line 95, in main
trainer.fit(task, train_dataloader, val_dataloader)

File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 460, in fit
self._run(model)
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 714, in _run
self.accelerator.setup_environment()
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py", line 80, in setup_environment
self.training_type_plugin.setup_environment()
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/plugins/training_type/ddp.py", line 118, in setup_environment
self.setup_distributed()
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/plugins/training_type/ddp.py", line 206, in setup_distributed
self.init_ddp_connection()
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/plugins/training_type/ddp.py", line 273, in init_ddp_connection
torch_distrib.init_process_group(self.torch_distributed_backend, rank=global_rank, world_size=world_size)
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/torch/distributed/distributed_c10d.py", line 455, in init_process_group
barrier()
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/torch/distributed/distributed_c10d.py", line 1960, in barrier
work = _default_pg.barrier()
RuntimeError: NCCL error in: /opt/conda/conda-bld/pytorch_1607370172916/work/torch/lib/c10d/ProcessGroupNCCL.cpp:784, unhandled system error, NCCL version 2.7.8

This problem comes, costed days to solve, but there seems no right solutions.
Is there anyone has solved this error? plz, thinks a lot.

It seems that there are some problems with your pytorch DDP. If you are using only one GPU, try to delete this line: https://github.com/RangiLyu/nanodet/blob/4ecfb1cbf7378582713a62bc31b331f635dd82c0/tools/train.py#L87

It seems that there are some problems with your pytorch DDP. If you are using only one GPU, try to delete this line:
https://github.com/RangiLyu/nanodet/blob/4ecfb1cbf7378582713a62bc31b331f635dd82c0/tools/train.py#L87

Thinks lot, problems solved. But another error came out , as following:
python ./tools/train.py ./config/nanodet-m-416.yml
[root][07-23 14:36:11]INFO:Using Tensorboard, logs will be saved in workspace/nanodet_m_416/logs
[root][07-23 14:36:11]INFO:Setting up data...
loading annotations into memory...
Done (t=14.44s)
creating index...
index created!
loading annotations into memory...
Done (t=0.44s)
creating index...
index created!
[root][07-23 14:36:27]INFO:Creating model...
model size is  1.0x
init weights...
=> loading pretrained model https://download.pytorch.org/models/shufflenetv2_x1-5666bf0f80.pth
Finish initialize Lite GFL Head.
GPU available: True, used: True
TPU available: False, using: 0 TPU cores
LOCAL_RANK: 0 - CUDA_VISIBLE_DEVICES: [0]
Traceback (most recent call last):
File "./tools/train.py", line 99, in
main(args)
File "./tools/train.py", line 94, in main
trainer.fit(task, train_dataloader, val_dataloader)
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 460, in fit
self._run(model)
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 717, in _run
self.accelerator.setup(self, model)  # note: this sets up self.lightning_module
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/accelerators/gpu.py", line 41, in setup
return super().setup(trainer, model)
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py", line 92, in setup
self.setup_optimizers(trainer)
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py", line 374, in setup_optimizers
optimizers, lr_schedulers, optimizer_frequencies = self.training_type_plugin.init_optimizers(
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/plugins/training_type/training_type_plugin.py", line 190, in init_optimizers
return trainer.init_optimizers(model)
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/trainer/optimizers.py", line 34, in init_optimizers
optim_conf = model.configure_optimizers()
File "/mnt/f/ubuntu_temp/nanodet/nanodet/trainer/task.py", line 174, in configure_optimizers
optimizer = build_optimizer(params=self.parameters(), **optimizer_cfg)
TypeError: init() got an unexpected keyword argument 'momentum'
Did you have this porblems?

It seems that there are some problems with your pytorch DDP. If you are using only one GPU, try to delete this line:
https://github.com/RangiLyu/nanodet/blob/4ecfb1cbf7378582713a62bc31b331f635dd82c0/tools/train.py#L87

Thinks lot, problems solved. But another error came out , as following:
python ./tools/train.py ./config/nanodet-m-416.yml
[root][07-23 14:36:11]INFO:Using Tensorboard, logs will be saved in workspace/nanodet_m_416/logs
[root][07-23 14:36:11]INFO:Setting up data...
loading annotations into memory...
Done (t=14.44s)
creating index...
index created!
loading annotations into memory...
Done (t=0.44s)
creating index...
index created!
[root][07-23 14:36:27]INFO:Creating model...
model size is 1.0x
init weights...
=> loading pretrained model https://download.pytorch.org/models/shufflenetv2_x1-5666bf0f80.pth
Finish initialize Lite GFL Head.
GPU available: True, used: True
TPU available: False, using: 0 TPU cores
LOCAL_RANK: 0 - CUDA_VISIBLE_DEVICES: [0]
Traceback (most recent call last):
File "./tools/train.py", line 99, in
main(args)
File "./tools/train.py", line 94, in main
trainer.fit(task, train_dataloader, val_dataloader)
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 460, in fit
self._run(model)
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 717, in _run
self.accelerator.setup(self, model) # note: this sets up self.lightning_module
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/accelerators/gpu.py", line 41, in setup
return super().setup(trainer, model)
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py", line 92, in setup
self.setup_optimizers(trainer)
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py", line 374, in setup_optimizers
optimizers, lr_schedulers, optimizer_frequencies = self.training_type_plugin.init_optimizers(
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/plugins/training_type/training_type_plugin.py", line 190, in init_optimizers
return trainer.init_optimizers(model)
File "/home/simon/anaconda3/envs/nanodet/lib/python3.8/site-packages/pytorch_lightning/trainer/optimizers.py", line 34, in init_optimizers
optim_conf = model.configure_optimizers()
File "/mnt/f/ubuntu_temp/nanodet/nanodet/trainer/task.py", line 174, in configure_optimizers
optimizer = build_optimizer(params=self.parameters(), **optimizer_cfg)
TypeError: init() got an unexpected keyword argument 'momentum'
Did you have this porblems?

I use Adam instead of SDG, so 'momentum' in config file is useless, #it, solved this problem!


deleted phone number from reg page

Description

Please include a summary of the change and, if applicable, which issue is fixed. Please also include relevant motivation, context, and screenshots.
Removing phone number from registration form.

Testing

Please briefly note how you tested and verified your changes.

Reviewers

Tag one or two teammates to review your code. Ideally, you should tag people who have worked on the same files or similar features to notify them of your changes. If you pair programmed with someone, please indicate that here as well.

LGTM


FileCreationInformation conflict

Fix for the following exception:
Exception occurred!
Exception Type: System.Management.Automation.MethodException
Exception Message: Cannot convert argument "parameters", with value: "Microsoft.SharePoint.Client.FileCreationInformation", for "Add" to type "Microsoft.SharePoint.Client.FileCreationInformation": "Cannot convert the "Microsoft.SharePoint.Client.FileCreationInformation" value of type "Microsoft.SharePoint.Client.FileCreationInformation" to type "Microsoft.SharePoint.Client.FileCreationInformation"."

I'm assuming somehow the PnP PowerShell DLL's are getting conflicted with local/GAC DLL's when using the FileCreationInformation class. Solution is to use the Add-PnPFile cmdlet.
Also reported in issue 20

Hi @KEMiCZA,
Thanks for your feedback. Your PR is really good. However, you are targeting the MASTER branch. Could you please target the DEV branch, instead? Then, I will be more than happy to merge it. Thanks. In the meantime, I will close this item.


Reimplementation/Reinterpretation of FOPBot

This is a from scratch reimplementation of the fop bots from https://github.com/lr32/fopbot.
What is lost (maybe not forever)?

Since this is "from scratch" and thus using non if the original code. There will be no Backward compatibility. Some of it can be regained by naming methods as in the original or adding a compatibility layer. I've tried to stay close to the original with the core interfaces Robot and World. However, to get animations going I went strait to write my own, very different drawing routines.
The ability for a freshman to just call new Robot() in the main method and have a Window pop up. My implementation, as is, requires to implement the Scene interface and pass an instance to the GUI frame. I have not investigated it, but it could be possible to create a package, e.g. fopbot.global, and put a global world there.
Screenshots. There a several ways to regain screenshots. First of all it is possible to record a Scene with an external program. This might not be that practical, however. Another option is to just rewrite the GUI but don't render to a window, but to disk.
The ability to customize robot sprites.

What is won?

Animations. All in all, I think I have improved the look of the fopbot code being run in a window.
A scrolling GUI allows for bigger worlds.
The ability to run the same code written by a freshmen in very different environments (World implementations). The only one written currently is the GUI. Nevertheless, screenshots (headless rendering) would fall in one of these environments. Another idea is to use this for automated testing.

Reimplemented the ability to run fop bots with just a main.
As described above, there is now the package fopbot.global holding the code to make this possible.
However, with that I have finally added the ability to run the freshmens main headless and run tests against it.

Run fopbot.global.SimpleExample.java to get the GUI.

Run fopbot.global.TracingGlobalTest.java to get test results.


add milvus init args support

Description
Add Milvus init args support, include the user, password and db_name. Meanwhile, there have the default value, will not affect the exist code.
Fixes #

[ ]

[ ] (issue)

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (does not change functionality, e.g. code style improvements, linting)
[ ] Documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Please delete options that are not relevant.

[x] Unit Test
[ ] Test Script (please provide)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Maintainer Checklist

[ ] closes #xxxx (Replace xxxx with the GitHub issue number)
[ ] Made sure Checks passed

Hey, what is the requirement to add this? And you will have to make changes to configs and Milvus Doc as well.

Hello, There is no requirements changes


syslog/channel: add constant attribute if SYSLOG_IOCTL is not enabled

Summary
syslog/channel: add constant attribute if SYSLOG_IOCTL is not enabled
move all private channel define from data to rodata
Signed-off-by: chao an<EMAIL_ADDRESS>Impact
N/A
Testing
ci-check

[Experimental Bot, please feedback here]
No, this PR does not fully meet the NuttX requirements.
Missing Information:

Summary:

Why is this change necessary? What problem does it solve or what improvement does it provide?
What functional part of the code is being changed (be specific)?
How does the change work? Provide a clear explanation of the technical implementation.

Impact:

While "N/A" might be accurate for some fields, it's best to explicitly confirm  each point:

Impact on user:  Will users notice any changes in functionality or behavior?
Impact on build: Will any build steps, dependencies, or configurations be affected?
Impact on documentation: Even if no documentation updates are required, state this explicitly.

Testing:

Insufficient Detail: "ci-check" is not descriptive enough.  Specify:

Build Hosts: List the operating systems, CPUs, and compiler versions used for testing.
Targets:  Provide details about the target architectures and boards you tested on.

No Logs:  The "Testing logs" sections are empty. Include relevant logs demonstrating the issue before the change and the improvement after the change.

Recommendations:

Expand the Summary: Provide a more detailed explanation of the change's purpose, implementation, and benefits.
Address all Impact Points: Explicitly confirm or describe the impact (or lack thereof) for each category.
Provide Specific Testing Details:  List the build hosts and target environments used for testing. Include relevant log snippets to illustrate the problem and the solution.


Support simpler syntax for specifying pipeline splits

What does this PR do?

This PR is a WIP
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

class IPUUNet2DConditionModel(UNet2DConditionModel, PipelineMixin):
    pipeline_splits = [
        ("conv_in", 0),
        ("down_blocks[2].downsamplers[0]", 1),
        ("up_blocks[0].resnets[2]", 2),
        ("up_blocks[1].attentions[2]", 3),
    ]
    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)

    def parallelize(self):
        super().parallelize()
        print(self.pipeline_splits)
        for layer, ipu_id in self.pipeline_splits:
            self.add_block(layer, ipu_id)
        return self

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


TP2000-617 Implement the new content for the TAP/TaMaTo homepage

TP2000-617 Implement the new content for the TAP/TaMaTo homepage
Why
The homepage needs to have additional content added to it so that users can better understand the page that they have accessed. There is also a need to correct some accessibility inconsistencies on the page.
What
Reduces font size of form label, removing multiple uses of H1 on page
Adds collapsible details component explaining what a workbasket is
Checklist

Requires migrations? No
Requires dependency updates? No

Also Jess raised a point in the show and tell yesterday about the "This service lets you manage UK trade tariffs" and that this was too specific. I think she's right. There's a difference between talking about tariffs plural as a shorthand for duties and the UK tariff as the collection of all different components (measures, quotas, commodities etc.). I would change the line to "This service lets you manage the UK tariff"

You have a CI test failing. It's unrelated to your change. It fails intermittently. (Doug is working on a fix). Update your branch to rerun it and it hopefully will pass second time of asking


Define remaining required OpenType tables

This adds:

OS/2
post
Enable the name records in the name table.

post version 2 (embedded Pascal string glyph names) does not currently parse the names. I think this would be possible if there was a way to get the maximum (numeric) value from an array. That maximum value is the number of glyph names to read, which would allow something like
let pascal_string = {
    length <- u8,
    string <- array8 length u8
};

string_data <- array16 num_strings pascal_string,

Also is there a better way to handle the layering of versions in OS/2?

It might be time to make an issue for "sequences of unspecified length", with the glyph names example and also the glyf flags example and others as we encounter them.

It might be time to make an issue for "sequences of unspecified length", with the glyph names example and also the glyf flags example and others as we encounter them.

I did have #310 open which might do part of what we need, but I wasn't entirely happy with how I implemented the binary parser portion of it. Haven't got back to it yet.

It might be time to make an issue for "sequences of unspecified length", with the glyph names example and also the glyf flags example and others as we encounter them.

I opened  #352 for this.


Unable to successfully stand up pod(s)

Uncertain if output is referring to the container itself or my host.  Maximum number of retries (20) reached.
airflow-init_1       |
airflow-init_1       | Last check result:
airflow-init_1       | $ airflow db check
airflow-init_1       | /home/airflow/.local/lib/python3.7/site-packages/airflow/configuration.py:440: DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
airflow-init_1       |   is_sqlite = "sqlite" in self.get("database", "sql_alchemy_conn")
airflow-init_1       | /home/airflow/.local/lib/python3.7/site-packages/airflow/configuration.py:360: DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
airflow-init_1       |   self._upgrade_postgres_metastore_conn()
airflow-init_1       | /home/airflow/.local/lib/python3.7/site-packages/airflow/settings.py:249 DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
airflow-init_1       | Unable to load the config, contains a configuration error.
airflow-init_1       | Traceback (most recent call last):
airflow-init_1       |   File "/usr/local/lib/python3.7/pathlib.py", line 1273, in mkdir
airflow-init_1       |     self._accessor.mkdir(self, mode)
airflow-init_1       | FileNotFoundError: [Errno 2] No such file or directory: '/opt/airflow/logs/scheduler/2023-01-20'
airflow-init_1       |
airflow-init_1       | During handling of the above exception, another exception occurred:
airflow-init_1       |
airflow-init_1       | Traceback (most recent call last):
airflow-init_1       |   File "/usr/local/lib/python3.7/logging/config.py", line 563, in configure
airflow-init_1       |     handler = self.configure_handler(handlers[name])
airflow-init_1       |   File "/usr/local/lib/python3.7/logging/config.py", line 736, in configure_handler
airflow-init_1       |     result = factory(**kwargs)
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/utils/log/file_processor_handler.py", line 49, in __init__
airflow-init_1       |     Path(self._get_log_directory()).mkdir(parents=True, exist_ok=True)
airflow-init_1       |   File "/usr/local/lib/python3.7/pathlib.py", line 1277, in mkdir
airflow-init_1       |     self.parent.mkdir(parents=True, exist_ok=True)
airflow-init_1       |   File "/usr/local/lib/python3.7/pathlib.py", line 1273, in mkdir
airflow-init_1       |     self._accessor.mkdir(self, mode)
airflow-init_1       | PermissionError: [Errno 13] Permission denied: '/opt/airflow/logs/scheduler'
airflow-init_1       |
airflow-init_1       | The above exception was the direct cause of the following exception:
airflow-init_1       |
airflow-init_1       | Traceback (most recent call last):
airflow-init_1       |   File "/home/airflow/.local/bin/airflow", line 5, in <module>
airflow-init_1       |     from airflow.__main__ import main
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/__init__.py", line 55, in <module>
airflow-init_1       |     settings.initialize()
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/settings.py", line 569, in initialize
airflow-init_1       |     LOGGING_CLASS_PATH = configure_logging()
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/logging_config.py", line 74, in configure_logging
airflow-init_1       |     raise e
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/logging_config.py", line 69, in configure_logging
airflow-init_1       |     dictConfig(logging_config)
airflow-init_1       |   File "/usr/local/lib/python3.7/logging/config.py", line 800, in dictConfig
airflow-init_1       |     dictConfigClass(config).configure()
airflow-init_1       |   File "/usr/local/lib/python3.7/logging/config.py", line 571, in configure
airflow-init_1       |     '%r' % name) from e
airflow-init_1       | ValueError: Unable to configure handler 'processor'
airflow-init_1       |
airflow_airflow-init_1 exited with code 1```

follow up details:
┌─[tyler@perihelion]-[~/Documents/play/kdp4-solutions/airflow]-[ (main)]
└──╼ $docker ps -a
CONTAINER ID   IMAGE                    COMMAND                  CREATED         STATUS                     PORTS                                       NAMES
d82fb8e7858b   koverse/airflow:latest   "/usr/bin/dumb-init …"   7 minutes ago   Exited (1) 6 minutes ago                                               airflow_airflow-init_1
84a8dc45a3f9   postgres:13              "docker-entrypoint.s…"   7 minutes ago   Up 7 minutes (healthy)     5432/tcp                                    airflow_postgres_1
466932b34f39   redis:latest             "docker-entrypoint.s…"   7 minutes ago   Up 7 minutes (healthy)     <IP_ADDRESS>:6379->6379/tcp, :::6379->6379/tcp   airflow_redis_1
┌─[tyler@perihelion]-[~/Documents/play/kdp4-solutions/airflow]-[ (main)]
└──╼ $docker image ls -a
REPOSITORY        TAG       IMAGE ID       CREATED         SIZE
koverse/airflow   latest    b6fed856e8b6   8 minutes ago   1.53GB
<none>            <none>    d324d857a008   9 minutes ago   1.46GB
<none>            <none>    5cfaa33707a8   9 minutes ago   1.46GB
<none>            <none>    f34d988a7eae   9 minutes ago   1.42GB
<none>            <none>    5fbb1a78f39e   9 minutes ago   1.23GB
<none>            <none>    1e11eee5dac7   9 minutes ago   1.23GB
<none>            <none>    dba1b57313c3   9 minutes ago   1.23GB
apache/airflow    latest    282394d57c1e   3 hours ago     1.23GB
redis             latest    19c51d4327cf   3 days ago      117MB
postgres          13        beb2ef252f25   9 days ago      373MB

Purged the entire kdp4-solutions directory, re-cloned and attempted from scratch with only modification being to .env to configure the Client ID and Client Secret to match my KDP4 application. Output follows:
┌─[tyler@perihelion]-[~/Documents/play/kdp4-solutions/airflow]-[ (main)]
└──╼ $dbt koverse/airflow .
Sending build context to Docker daemon  52.22kB
Step 1/8 : FROM apache/airflow:latest
 ---> 282394d57c1e
Step 2/8 : USER airflow
 ---> Using cache
 ---> dba1b57313c3
Step 3/8 : COPY requirements.txt /tmp/
 ---> Using cache
 ---> 5fbb1a78f39e
Step 4/8 : USER root
 ---> Using cache
 ---> 1e11eee5dac7
Step 5/8 : RUN apt-get update &&     apt-get install -y gcc
 ---> Using cache
 ---> f34d988a7eae
Step 6/8 : RUN apt-get install -y g++
 ---> Using cache
 ---> 5cfaa33707a8
Step 7/8 : USER airflow
 ---> Using cache
 ---> d324d857a008
Step 8/8 : RUN /usr/local/bin/python -m pip install --upgrade pip ipython ipykernel &&     ipython kernel install --name "python3" --user &&     pip3 install -r /tmp/requirements.txt
 ---> Using cache
 ---> b6fed856e8b6
Successfully built b6fed856e8b6
Successfully tagged koverse/airflow:latest
┌─[tyler@perihelion]-[~/Documents/play/kdp4-solutions/airflow]-[ (main)]
└──╼ $dc up airflow-init
airflow_postgres_1 is up-to-date
airflow_redis_1 is up-to-date
Recreating airflow_airflow-init_1 ... done
Attaching to airflow_airflow-init_1
airflow-init_1       | ....................
airflow-init_1       | ERROR! Maximum number of retries (20) reached.
airflow-init_1       |
airflow-init_1       | Last check result:
airflow-init_1       | $ airflow db check
airflow-init_1       | /home/airflow/.local/lib/python3.7/site-packages/airflow/configuration.py:440: DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
airflow-init_1       |   is_sqlite = "sqlite" in self.get("database", "sql_alchemy_conn")
airflow-init_1       | /home/airflow/.local/lib/python3.7/site-packages/airflow/configuration.py:360: DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
airflow-init_1       |   self._upgrade_postgres_metastore_conn()
airflow-init_1       | /home/airflow/.local/lib/python3.7/site-packages/airflow/settings.py:249 DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
airflow-init_1       | Unable to load the config, contains a configuration error.
airflow-init_1       | Traceback (most recent call last):
airflow-init_1       |   File "/usr/local/lib/python3.7/pathlib.py", line 1273, in mkdir
airflow-init_1       |     self._accessor.mkdir(self, mode)
airflow-init_1       | FileNotFoundError: [Errno 2] No such file or directory: '/opt/airflow/logs/scheduler/2023-01-20'
airflow-init_1       |
airflow-init_1       | During handling of the above exception, another exception occurred:
airflow-init_1       |
airflow-init_1       | Traceback (most recent call last):
airflow-init_1       |   File "/usr/local/lib/python3.7/logging/config.py", line 563, in configure
airflow-init_1       |     handler = self.configure_handler(handlers[name])
airflow-init_1       |   File "/usr/local/lib/python3.7/logging/config.py", line 736, in configure_handler
airflow-init_1       |     result = factory(**kwargs)
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/utils/log/file_processor_handler.py", line 49, in __init__
airflow-init_1       |     Path(self._get_log_directory()).mkdir(parents=True, exist_ok=True)
airflow-init_1       |   File "/usr/local/lib/python3.7/pathlib.py", line 1277, in mkdir
airflow-init_1       |     self.parent.mkdir(parents=True, exist_ok=True)
airflow-init_1       |   File "/usr/local/lib/python3.7/pathlib.py", line 1273, in mkdir
airflow-init_1       |     self._accessor.mkdir(self, mode)
airflow-init_1       | PermissionError: [Errno 13] Permission denied: '/opt/airflow/logs/scheduler'
airflow-init_1       |
airflow-init_1       | The above exception was the direct cause of the following exception:
airflow-init_1       |
airflow-init_1       | Traceback (most recent call last):
airflow-init_1       |   File "/home/airflow/.local/bin/airflow", line 5, in <module>
airflow-init_1       |     from airflow.__main__ import main
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/__init__.py", line 55, in <module>
airflow-init_1       |     settings.initialize()
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/settings.py", line 569, in initialize
airflow-init_1       |     LOGGING_CLASS_PATH = configure_logging()
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/logging_config.py", line 74, in configure_logging
airflow-init_1       |     raise e
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/logging_config.py", line 69, in configure_logging
airflow-init_1       |     dictConfig(logging_config)
airflow-init_1       |   File "/usr/local/lib/python3.7/logging/config.py", line 800, in dictConfig
airflow-init_1       |     dictConfigClass(config).configure()
airflow-init_1       |   File "/usr/local/lib/python3.7/logging/config.py", line 571, in configure
airflow-init_1       |     '%r' % name) from e
airflow-init_1       | ValueError: Unable to configure handler 'processor'
airflow-init_1       |
airflow_airflow-init_1 exited with code 1

Continued troubleshooting. Determined Maven Jetty9 service reserved port 8080. Stopped service and attempted to run through on a fully sanitized docker environment with a clean copy of the repo.  Maximum number of retries (20) reached.
airflow-init_1       |
airflow-init_1       | Last check result:
airflow-init_1       | $ airflow db check
airflow-init_1       | /home/airflow/.local/lib/python3.7/site-packages/airflow/configuration.py:440: DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
airflow-init_1       |   is_sqlite = "sqlite" in self.get("database", "sql_alchemy_conn")
airflow-init_1       | /home/airflow/.local/lib/python3.7/site-packages/airflow/configuration.py:360: DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
airflow-init_1       |   self._upgrade_postgres_metastore_conn()
airflow-init_1       | /home/airflow/.local/lib/python3.7/site-packages/airflow/settings.py:249 DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
airflow-init_1       | Unable to load the config, contains a configuration error.
airflow-init_1       | Traceback (most recent call last):
airflow-init_1       |   File "/usr/local/lib/python3.7/pathlib.py", line 1273, in mkdir
airflow-init_1       |     self._accessor.mkdir(self, mode)
airflow-init_1       | FileNotFoundError: [Errno 2] No such file or directory: '/opt/airflow/logs/scheduler/2023-01-25'
airflow-init_1       |
airflow-init_1       | During handling of the above exception, another exception occurred:
airflow-init_1       |
airflow-init_1       | Traceback (most recent call last):
airflow-init_1       |   File "/usr/local/lib/python3.7/logging/config.py", line 563, in configure
airflow-init_1       |     handler = self.configure_handler(handlers[name])
airflow-init_1       |   File "/usr/local/lib/python3.7/logging/config.py", line 736, in configure_handler
airflow-init_1       |     result = factory(**kwargs)
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/utils/log/file_processor_handler.py", line 49, in __init__
airflow-init_1       |     Path(self._get_log_directory()).mkdir(parents=True, exist_ok=True)
airflow-init_1       |   File "/usr/local/lib/python3.7/pathlib.py", line 1277, in mkdir
airflow-init_1       |     self.parent.mkdir(parents=True, exist_ok=True)
airflow-init_1       |   File "/usr/local/lib/python3.7/pathlib.py", line 1273, in mkdir
airflow-init_1       |     self._accessor.mkdir(self, mode)
airflow-init_1       | PermissionError: [Errno 13] Permission denied: '/opt/airflow/logs/scheduler'
airflow-init_1       |
airflow-init_1       | The above exception was the direct cause of the following exception:
airflow-init_1       |
airflow-init_1       | Traceback (most recent call last):
airflow-init_1       |   File "/home/airflow/.local/bin/airflow", line 5, in <module>
airflow-init_1       |     from airflow.__main__ import main
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/__init__.py", line 55, in <module>
airflow-init_1       |     settings.initialize()
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/settings.py", line 569, in initialize
airflow-init_1       |     LOGGING_CLASS_PATH = configure_logging()
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/logging_config.py", line 74, in configure_logging
airflow-init_1       |     raise e
airflow-init_1       |   File "/home/airflow/.local/lib/python3.7/site-packages/airflow/logging_config.py", line 69, in configure_logging
airflow-init_1       |     dictConfig(logging_config)
airflow-init_1       |   File "/usr/local/lib/python3.7/logging/config.py", line 800, in dictConfig
airflow-init_1       |     dictConfigClass(config).configure()
airflow-init_1       |   File "/usr/local/lib/python3.7/logging/config.py", line 571, in configure
airflow-init_1       |     '%r' % name) from e
airflow-init_1       | ValueError: Unable to configure handler 'processor'
airflow-init_1       |
airflow_airflow-init_1 exited with code 1

The PermissionError: [Errno 13] Permission denied: '/opt/airflow/logs/scheduler' message suggests that your local ./logs directory might have permission problem.
Are you using Linux or Mac ?
There are some suggestions mentioned in this stackoverflow post worth of trying https://stackoverflow.com/questions/59412917/errno-13-permission-denied-when-airflow-tries-to-write-to-logs
You probably need something similar to one of the solutions
chmod -R 777 dags/
chmod -R 777 logs/

Are you using Linux or Mac ?

This is from the Linux system. Ubuntu 22.04 LTS with Budgie DE. I'll give those a gander to ensure the permissions in the logs folder and dags folder. Those suggestions are for the actual host's logs, not the containers being spun up, correct?

Okay looks like the chmod in the working directory for that copy of the GH repo did the trick on the Mac. I'm actually getting somewhere and it at least appears to be fully standing up!

Permissions in the local copy of the GH repo were not correctly set for the dags/ and logs/ directories. Modified permissions via sudo chmod 777 dags/ logs/ and was able to complete the lab.


Fix item.group bug in process.yml

This patch fixes a bug where the setup-maas.yml playbook would
fail when checking for item.group in the host groups.
Connects rcbops/u-suk-dev#1025

recheck_swift
Quota exceeded.

recheck_swift
Quota exceeded.

👍


Change uintptrSize to constant

Like Go runtime, change uintptrSize to constant.

https://github.com/golang/go/blob/master/src/reflect/value.go#L14
😄
LGTM !! Thanks !


yarn dev fails because of undefined publicRuntimeConfig

Describe the bug
I get an error when trying to run the solution locally (next dev). It seems like there's a missing manual step in the readme about defining the env configs.parsed.APIGateway?
To Reproduce
Follow 'running locally' steps in readme to setup, then run: yarn dev
Expected behavior
App to load on localhost:3000.
Please complete the following information about the solution:

[ ] Version: e.g. v1.0.1
[ ] Region: us-east-1
[n] Was the solution modified from the version published on this repository?

Additional context
ERROR:
TypeError: Cannot read property 'APIGateway' of undefined
at Object. (/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/next.config.js:20:5)
at Module._compile (node:internal/modules/cjs/loader:1108:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1137:10)
at Module.load (node:internal/modules/cjs/loader:973:32)
at Function.Module._load (node:internal/modules/cjs/loader:813:14)
at Module.require (node:internal/modules/cjs/loader:997:19)
at require (node:internal/modules/cjs/helpers:92:18)
at loadConfig (/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/next-server/server/config.js:8:100)
at new Server (/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/next-server/server/next-server.js:1:4383)
at new DevServer (/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/server/next-dev-server.js:1:2964)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I realized I didnt have next cli installed, so i installed it, and get this instead:
`yarn run v1.22.5
warning ../../package.json: No license field
$ NEXT_PUBLIC_ENABLE_KENDRA=$npm_package_enableKendra next app
Error: Cannot find module 'webpack'
Require stack:

/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/mini-css-extract-plugin/dist/index.js
/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/mini-css-extract-plugin/dist/cjs.js
<EMAIL_ADDRESS><EMAIL_ADDRESS>/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/next.config.js
/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/next-server/server/config.js
/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/next-server/server/next-server.js
/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/server/next.js
/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/server/lib/start-server.js
/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/cli/next-dev.js
/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/bin/next
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:925:15)
at Function.Module._load (node:internal/modules/cjs/loader:769:27)
at Module.require (node:internal/modules/cjs/loader:997:19)
at require (node:internal/modules/cjs/helpers:92:18)
at Object. (/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/mini-css-extract-plugin/dist/index.js:7:16)
at Module._compile (node:internal/modules/cjs/loader:1108:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1137:10)
at Module.load (node:internal/modules/cjs/loader:973:32)
at Function.Module._load (node:internal/modules/cjs/loader:813:14)
at Module.require (node:internal/modules/cjs/loader:997:19)
at require (node:internal/modules/cjs/helpers:92:18)
at Object. (/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/mini-css-extract-plugin/dist/cjs.js:3:18)
at Module._compile (node:internal/modules/cjs/loader:1108:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1137:10)
at Module.load (node:internal/modules/cjs/loader:973:32)
at Function.Module._load (node:internal/modules/cjs/loader:813:14) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/mini-css-extract-plugin/dist/index.js',
'/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/mini-css-extract-plugin/dist/cjs.js',
<EMAIL_ADDRESS><EMAIL_ADDRESS>'/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/next.config.js',
'/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/next-server/server/config.js',
'/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/next-server/server/next-server.js',
'/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/server/next.js',
'/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/server/lib/start-server.js',
'/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/cli/next-dev.js',
'/home/shenry/freelance/AWS_Textract/document-understanding-solution/source/node_modules/next/dist/bin/next'
]
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.`

Thanks for reaching out @spencerrichardhenry
Have you deployed the solution before running the yarn dev command?
The infrastructure has to be deployed once so that the the endpoints and resources are available for developing the U locally.

Ah thank you! I have not deployed the solution via cli previously. I'll do that.

Sure.
Just one call out. As seen in the README, yarn dev is a part of Development Deploy method
If you want to use yarn dev as part of the CICD method (which is also the method used in the AWS Solutions page )
, you would need to take the additional step to export the .env file from the CodeBuild project and store it in local development env

Your steps worked. Thanks!


fix: xcode 12 compatibility

According to https://github.com/facebook/react-native/issues/29633#issuecomment-694187116 - "React pod is in fact really only an umbrella dependency for pure JS applications to depend on, whereas the native APIs that these libraries rely on actually reside in the React-Core pod." and it will fail to build on Xcode12. This PR updates the dependency from React to React-Core.

@kasinskas Is this change compatible with older RN versions or do we need to make a major bump?

Hey, it requires RN 0.60.2 or newer.

Not stale, @DanielMSchmidt check this

@organom Sorry for the late response. Since the 7.X version only supports RN >=0.60 I think we are fine with making this a patch release

:tada: This PR is included in version 7.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Subtitles] How to use a typeface from assets directory with ttml attribute tts:fontFamily?

How can I configure exoplayer to use a custom font for subtitles, when the font name is referenced within the TTML sample?
The font is not already installed on the users device and would be distributed via the assets directory.
So given:

a ttf inside my assets directory:

The font is referenced inside a TTML sample's tts:fontFamily attribute, eg:

    <styling>


Feature request: global error logging

one flag to enable logging (into file) of all database errors.

Since this can be handled at the database configuration level, I think there's no need to bloat the database interaction layer. Keeping it in the database config allows you more flexibility, such as the option to log it to a file/table etc.

you misunderstoo d the request. it is about logging invalid / failed queries. MySQL doesn't log invalid/failed queries anywhere. http://stackoverflow.com/questions/4631133/mysql-log-of-invalid-queries

We create a simple medoo wrapper include monolog logging.
Create a class named "Database", extends Medoo and overwrite methods like:
  public function insert($table, $data) {
    $this->logger->info( 'insert', ["table" => $table, "data" => $data] );
    return parent::insert($table, $data);
  }

So for error logging, I write a errorHandler:
Query/Exec method:
  public function query($query, $context = []) {
    $this->logger->info('query', $context);
    $result = parent::query($query);
    $this->handleSqlError( $result ); // <-- handle errors
    return $result;
  }

Error handling:
 private function handleSqlError($query) {
   $error = $this->error();

   if ($error[0] != '00000') {
     $this->logger->critical('ERROR', ["sql" => $query,"error" => $error]);
   }

 }


Use production API endpoint

Replace all references to things like: https://backend-v3-canary.beets-ftm-node.com/graphql

Is this issue related to #339 & #332 ?

Is this issue related to #339 & #332 ?

Not really, those issues more referenced the fact the API was not returning V3 data. This is more of a tidy up issue.


[Feature Request] Automatically do a database fetch if the policy rules use fields not provided in the user context object

Just realized to do that we need to change enhance to an async API. It'll be a breaking change. Punting to V2.


1797650: Remove '?view=' syntax

No extension changes. Part of an effort to remove unnecessary versioning link syntax.
See user story 1797650 for more information.

doc

hi @danieldoolabh could you pls help to review this PR also? thanks


Output differs from md5sum

Running on Lua 5.3, sumhexa returns a different value from md5sum.

Hi, can you provide more information about this? In particular, which string did you use?

md5sum.lua source code:
#!/usr/bin/lua
md5 = require("md5")
if arg[1] then
print(md5.sumhexa(arg[1]))
else
print("syntax: md5sum.lua ")
end
md5sum.lua output for "test" (without quotes): 098f6bcd4621d373cade4e832627b4f6
/usr/bin/md5sum output for "test" (without quotes): d8e8fca2dc0f896fd7cb4cb0031ba249
Commands used:

md5sum.lua - lua md5sum.lua test
/usr/bin/md5sum - echo test | md5sum

After further testing, I've realized that feeding "echo test" to md5sum also includes the newline. Using the -n flag with echo (which is supposed to not put a newline at the end) returns the same result.
This issue can be closed.

Thanks a lot, I was a bit worried about this ^__^


[C++][Parquet] Implement support for DataPageV2

Reporter: Wes McKinney / @wesm
Assignee: Hatem Helal](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hatem) / @hatemhelal
Related issues:

[C++] Unable to read parquetjs-created file using low-level parquet-cpp API (causes)
[Python] Parquet files v2.0 created by spark can't be read by pyarrow (causes)

PRs and other links:

GitHub Pull Request #6481

Note: This issue was originally created as PARQUET-458. Please see the migration documentation for further details.

Ivan Sadikov / @sadikovi:
Hello,
If it helps, Rust parquet library in Apache Arrow already implements Data page V2 for both writes and reads, so you can use that as a reference when working on C++ code and check correctness in either Rust or C++.
Here are some links for column reader/writer:
https://github.com/apache/arrow/blob/master/rust/parquet/src/column/reader.rs#L342
https://github.com/apache/arrow/blob/master/rust/parquet/src/column/writer.rs#L544
We also added a bunch of Data page v2 encodings added in Rust, and quite a few correctness tests to check encoding/decoding works.
Hopefully, it helps,  @wesm.

shravani kalikiri:
Okay.

Wes McKinney / @wesm:
There's multiple issues here preventing the library from reading the pages yet:
In DataPageV2

the encoded rep/def levels prefix is not included in the data, it's part of the page header, so this logic is incorrect: https://github.com/apache/arrow/blob/master/cpp/src/parquet/column_reader.cc#L53

the compressed data size in the page header refers only to the portion of the page after the definition_levels_num_bytes and repetition_levels_num_bytes from the page header
I started working on a patch, I'll see if I can get something up in the next week or so

Wes McKinney / @wesm:
I do plan to write a C++ patch for this but it will be next week at the earliest. I expect the fix will be a part of the next Arrow release, but you can create builds from master in the meantime once a fix it in

skreddy:
Thanks for the response Ivan Sadikov.

skreddy:
Hi Wes Mckinney,
Are you working on fixing this issue ? Any update on when this fix will be available?
Is below reported datapage v2 issue will also be solved with your fix?
https://issues.apache.org/jira/browse/PARQUET-1560
Thanks in advance for your response.

shravani kalikiri:
Hello @wesm ,
Any update on when this fix will be merged ?

Siva:
Thanks Wes Mckinney

Wes McKinney / @wesm:
Seeing as how I haven't written it yet I have no idea

Wes McKinney / @wesm:
Issue resolved by pull request 6481
https://github.com/apache/arrow/pull/6481

Wes McKinney / @wesm:
@xhochy I think we should disable V2 writes until this can be correctly implemented, what do you think? It's unfortunate that it's been broken for such a long time

TP Boudreau / @tpboudreau:
Thanks for the heads up.
WRT timestamps, it seems the primary consequence of withdrawing V2 support will be that (Py)Arrow/Parquet users will not be able to create int64 nanosecond timestamps, while non-Arrow parquet-cpp users will still be able to create them.
I suppose we could consider adding a separate Arrow boolean file writer property like "retain_nanosecond_timestamps" that defaulted to "false" (meaning preserve legacy (V1) behavior of coercing nanos to micros) but could be overridden to obtain the current V2 behavior. But this would probably only be worth the effort (and API clutter) if the reintroduction of V2 were a long way off.

Sk:
@wesm  any update on this issue?

Wes McKinney / @wesm:
I'd like to fix the underlying issues with the V2 read/write path. I'm not sure if I'll get to it this month but I at least have it on mind. I'm doing some refactoring of parquet/column_writer.cc at the moment but the change to get the format right should not be too large. Making sure it's adequately tested may be as much or more work

Wes McKinney / @wesm:
BTW V2 files are not considered suitable for production by the Parquet community

Wes McKinney / @wesm:
@tpboudreau wanted to make sure you're aware of this issue

Wes McKinney / @wesm:
I have no immediate plans to do this work. Such is the nature of open source software.

Sk:
Thanks for the information.


Retain the error message in task execution even when next pod succeeds

What this PR does:
Retain the error message from the management-api.
Which issue(s) this PR fixes:
Fixes #612
Checklist

[ ] Changes manually tested
[x] Automated Tests added/updated
[ ] Documentation added/updated
[x] CHANGELOG.md updated (not required for documentation PRs)
[x] CLA Signed:  DataStax CLA

Yeah, they were flakes (there's some resource issues, would need a bigger runner probably)


Run_at for Delayed Job Always Set to Create Time

I have Delayed Job set up in my app to send out an email for an reminder at the date saved in the mail_date column in the reminders database table.  Along with the bright minds on my Stack Overflow post, I have troubleshot the issue and tried two different ways to call Delayed Job:
RemainderMailerJob.set(wait_until: self.mail_date).perform_later(user, remainder)

and
ReminderMailer.delay(run_at: self.mail_date).reminder_send(self.user, self)

Unfortunately, no matter what I tried, the run_at date when I check Delayed::Job.all in my console remains the date/time the reminder was saved, not the mail_date listed in the database.  I know this forum is for bugs not implementation issues, but seeing as the good folks at SO are stumped as well, I figured it might be of interest here, if only for the purposes of possibly expanding the documentation to cover this issue.

Closing stale


Filter debug variables

Here is my attempt to fix https://github.com/Microsoft/vscode/issues/13201

@cshung thanks for this PR. However we usually prefer that we first start a discussion before coding away. In this particular case this should be implemented on the Tree level and @joaomoreno is actually currently working on this. Once it is done on a tree level we can reuse this nicely for the explorer and variables view.
Apart from that I tested your PR and it does not work for me: once I type in the input box in the variables view it always hides everything.
Due to the above I am closing this PR and we actually plan to adopt tree filtering in the variables view in the near future.


Fixed XML validation issues

Changed “&” to “$amp;”, added missing end tags for elements
The existing XML files were not valid and required some cleanup.

Thanks! I'll merge and make sure these issues are fixed prior to the next update commit.


added more details to getLaunchTag()

Added infos from closed issue #208 to readme.

Thanks for the contribution!


StateColab imeAction does not add TodoItem

When clicking the imeAction Done on the keyboard the submit callback is run but the text is always blank.
val submit = {
    if (text.isNotBlank()) {
        onItemComplete(TodoItem(text, icon))
        onTextChange("")
        onIconChange(TodoIcon.Default)
    }
}

When clicking imeaction Done the statement
if (text.isNotBlan())

is always false, even if there is text in the textfield.
The strange thing is that the TodoEditButton has the exact same callback and it works every time.

Tried this with an emulator with API 24 and I'm unable to reproduce it.
Is there any other info you can provide?

Tried this with an emulator with API 24 and I'm unable to reproduce it.
Is there any other info you can provide?


New version: sxyazi.yazi version 0.3.2

Pull request has been created with komac v2.5.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree


this and typeof are not type keywords in completions

In services/utilities.ts:1213, this and typeof are not in
    export const typeKeywords: ReadonlyArray<SyntaxKind> = [
        SyntaxKind.AnyKeyword,
        SyntaxKind.BigIntKeyword,
        SyntaxKind.BooleanKeyword,
        SyntaxKind.FalseKeyword,
        SyntaxKind.KeyOfKeyword,
        SyntaxKind.NeverKeyword,
        SyntaxKind.NullKeyword,
        SyntaxKind.NumberKeyword,
        SyntaxKind.ObjectKeyword,
        SyntaxKind.ReadonlyKeyword,
        SyntaxKind.StringKeyword,
        SyntaxKind.SymbolKeyword,
        SyntaxKind.TrueKeyword,
        SyntaxKind.VoidKeyword,
        SyntaxKind.UndefinedKeyword,
        SyntaxKind.UniqueKeyword,
        SyntaxKind.UnknownKeyword,
    ];

even though they are type keywords. Unfortunately, adding them breaks some tests to do with find-all-refs with global this -- patterns like function f(this) { this } start identifying the this inside the function as the global this.

function f(this) { this }

Isn’t this a syntax error?

In JS yes, in TS no. TS allows the first parameter to be this in order to specify the type of this inside the function.

Ah right - I knew about the this parameter but didn’t make the connection since that would be an automatic noImplicitAny error - not used to seeing bare parameters anymore :smiley:

This was half-fixed in #53325, but things do still fail as described if you just add ThisKeyword without other changes.


basic: introduce the _environment compilation conditional

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

Windows has multiple environment flavours, each of which are different.  cygwin
provides a glibc based environment, MinGW provides a msvcrt based GNU
environment, itanium provides a msvc environment with an itanium C++ ABI, and
msvc is the pure msvc, msvcprt based environment as vended by Microsoft.  Due to
the differences in the environment, we need a means to differentiate them at the
stdlib level.  Provide the _environment conditional which would allow you to
query what environment is being targeted.

CC: @jrose-apple

@swift-ci Please test

I'd rather not accept this right now unless we absolutely need it. Otherwise, it's worth actually going through swift-evolution and figuring out what os(…) means and what's going to be above or below that.

@jrose-apple without this, unfortunately, it means that we can't do a windows port without breaking cygwin.  Could we do both?

Can you elaborate? What's something we're relying on in a Windows port that doesn't work with Cygwin?

Sure, there are cases where certain functions are available on cygwin and not in MSVCRT.  Other cases are where they are just different.  Because that may be a bit vague, lets take concrete examples:
Just different:
errno: __errno() on cygwin, _errno() on msvcrt.
Unavailable:
lgamma_r on cygwin, not available on msvcrt.

Hm, got it.
I really don't want to introduce this because people will immediately start using it outside of the standard library.

Im open to alternative suggestions.  I don't know how long it would take to get through everything with the swift-evolution (especially since Ive not gone through it previously).

Well, there's the hack of moving things into a C function for the few things that are different.

What about the larger pieces like pthread (available on cygwin, not on msvc)?

What about putting it behind a compiler flag? We already have one for the standard library, could it maybe fit inside -parse-stdlib?

If we really just want a workaround, we could also use an ad hoc -D flag.

Sure, the ad-hoc -D flag sounds like it should be sufficient for now.  I think that we should work out a proper environment check though.

Definitely. May be worth starting a thread on swift-dev with @karwa and @hpux735? Then someone can write it up as a proper proposal for swift-evolution, and we can consider prototyping it during that time as well.

Oops, and @tinysun212.

Thanks for your mention.
I started similar discussion in #2351 and swift-evolution, but it is discontinued.
I am positive to the approach in this PR, it will be useful for Foundation porting as well as standard library porting.
I tried ad hoc -D flag in Foundation PR. In there, the code is like this.
#if os(OSX) || os(iOS)
    import Darwin
#elseif os(Linux) || IS_CYGWIN
    import Glibc
#endif

I think if we use the method 'ad hoc -D flag', we need the convention for the macro name.

Ill definitely bring this up again.  I used CYGWIN, as I don't want to break cygwin support as Im adding MSVCRT support.  I have the work available on my own fork of the repository, and will be sending out a PR for a good chunk of it soon.


[PE-D][Tester C] Cannot add note with same content but different tag

This might be an intended behaviour but perhaps a message can be displayed in the UI?

For example, the error is visible here:

Labels: type.FunctionalityBug severity.Medium
original: jx124/ped#6

Note too sure what this bug report is talking about, @aliciamichellew maybe you can take a look?


[Bug] query by limit offset missing records

Search before asking

[X] I searched in the issues and found nothing similar.

Version
v1.1.0
Describe the bug and provide the minimal reproduce step
query sql statement
SELECT * FROM root.p_95.d_9081.SQ order by time desc limit 30 offset 0 align by device

and
SELECT * FROM root.p_95.d_9081.SQ order by time desc limit 20 offset 0 align by device

What did you expect to see?
The first 20 pieces of data should be the same
What did you see instead?

missing records 2023-06-02T09:00:01.000+08:00 and  2023-06-02T08:50:01.000+08:00
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Fixed by #9437


Verification code is not showing

unable to load verification code image

It works by enabling the GD extension in apache server Config. In xampp, prress the config button right next to  apache server, search for GD, then remove the semicolon infront of the GD option


pin wins to v0.2.5

https://github.com/rancher/rancher/issues/37022

https://github.com/rancher/rancher/issues/36574


Remove upper bound on justified-containers

Failing test cases resolved in <IP_ADDRESS>. See https://github.com/matt-noonan/justified-containers/issues/4

Merged, thanks


Multiple Lines

A feature that would be interesting is the support for multiple lines
When you press enter the textView increase up to the limit of NavigationViewController

Hi @bfernandesbfs,
Thanks for the feature request. That feature would really be outside the scope of this control which is mainly focused on keeping an input view about the keyboard while supporting panning.
Here are a few alternative libraries which provide the feature you are looking for:
https://github.com/jessesquires/JSQMessagesViewController
https://github.com/HansPinckaers/GrowingTextView (A little outdated but has worked for me in the past)


Devise 4.2.0  Browser sends GET request on page reload after unsuccessful form submission.

With Rails 5 and default devise routing settings after unsuccessful form submission on /users/sign_up I'm being redirected to /users path. After that I reload the page in my browser and it sends GET request to /users path and receives 'No route matches [GET] "/password"'.
With Rails 4 and Devise 3 a browser sends POST request performing form resubmission as I expect.
Any suggestions how to make things work as it used to be? Thanks in advance.

I had the same effects as you @ibarchenkov. After page reload on unsuccessful sign_up  devise/registrations#create it redirect to no route users#index.  It looks like bug.
Routing Error
No route matches [GET] "/users"

I used temporary workaround in /config/routes.rb :
devise_for :users, :path => '', :path_names => {:sign_in => 'login', :sign_out => 'logout'},

after unsuccessful sign_up and reload will redirect you to root_path.

Closing in favor of #4573


Display icons for each page inside the Configuration menu

Feature Request
I confirm:

[x] that I have searched for an existing feature request matching the description.

Feature Information:
Issue
As a user, from an accessibility stand point I find it difficult navigating the Configuration menu, being a wall of text with 15 different pages. Additionally for newer users to AMP , the number of pages and the lack of structure creates an unnecessary amount of visual complexity.
Change
Display icons for each page inside the Configuration menu for improved readability.
Example:
Default

Current view of the Configuration menu today

New
Here is an examples of how I would imagine implementing this change...

I've added relevant emojis here as example icons

This was actually implemented!

Thank you @PhonicUK, it's been awesome seeing my suggestions and so many other UI improvements come to AMP. It really is a great experience and an absolute joy to use.

Community contributions are always very welcome :)


Large delay before and after  tag in SSML

Describe the bug
When using  tag within SSML, there is a large delay (about 1s) before and after the audio file.
To Reproduce
just use the following SSML to produce a speech
<speak version="1.0" xmlns="https://www.w3.org/2001/10/synthesis" xml:lang="en-US"><voice name="en-US-AriaNeural">Hello<audio src="https://germiz.com/world.wav" />, how are you?</voice></speak>

Expected behavior
I'm attaching an audio file generated by a competitor speech synthesizer using the same SSML, you can notice the different in delay between "Hello" and "World" compared to MS Azure TTS
hello_world.zip

@alaa-eddine , thx for reaching out. I forward your issue to service team and will get back to you when I get anything.

I got an answer from service team. You can using the following SSML to set the tailing silence of Hello to reduce the silence.
<speak version="1.0" xmlns="https://www.w3.org/2001/10/synthesis" xmlns:mstts="http://www.w3.org/2001/mstts" xml:lang="en-US">
<voice name="en-US-AriaNeural">
<mstts:silence type="tailing" value="100ms"/>Hello<audio src="https://germiz.com/world.wav" />, how are you?
</voice></speak>

Awesome !
I was not aware that we can use mstts:silence this way .
This fixes my issue, thank you very much!

That it great!


Silvester Party! 🎆

This is not a typical wishlist issue, but it‘s also a wish. I want to wish everyone a happy new year, „Einen guten Rutsch“ and say: Thank you! ❤
Thank you for another great year in the Community of the Corona-Warn-App, thank you for the big updates we saw over the last 365 days, which brought some great new features to all the users of the CWA. 🚀
We are close to 40.000.000 downloads, more than 1.00.000 users who were tested positive with a PCR tests have warned their contacts via the app and at least 9 million users were warned via the CWA! 🎉
To all of the team, the community & their loved ones: Stay healthy, stay safe & see you in 2022! 🎇

Feel free to comment below & say thank you!

Wishing one and all a happy and prosperous new new year !!
Thanks for the good work everyone !!

@vaubaehn does sadly not have time to comment here, so I'm commenting on behalf of him:
"Greetings and a good and healthy start into 2022 for all of you!" 🎉🎆

Thanks for everything! Happy new year!!!

Sweet 💖
Thanks and all the best and may this 202[01] shithole end!

Thanks for all the work you all done this year and helping all of us with it. I did not think that this app would be such an simple but important app in our lifes.
@Ein-Tim is always in my Twitter timeline helping everyone, thank you, too.
Happy new year to all of you.

What Tim says ;)
Don´t you wonder, I made a new account probably not only just for this.
Thanks-a-mile to all contributors, evangelists and basically everyone supporting this project.  Seeing how CWA has evolved this year I am certain we can make this an even better and more popular tool to fight the pandemic. Let us not lose focus and only implement the features people really want, use and understand.
As we say in Bavaria: Kemmt´s guad ummi!
P.S.: Where can I file a pull-request for 2021? And 2020 for that matter? ;)

Thanks a lot for such an effective app and good early warning system. I also had a red CWA warning and PCR testing was flawlessly and easily done after that.
Thanks a lot and happy new year fighting your/our new evil Omicron… We can make that! :blush: :tada:

Thank you guys for the good work and for giving me a good topic for my bachelor thesis. Wish you all the best! 🎉

Nice issue. 👍
Happy New Year!

Keep up the great work! #LucaSucks

Happy new year to the team & community. Let's hope we don't need such an issue again...

Keep your good work up. Und rutscht gut :)

Happy new year to everybody! I'm looking forward to the next year 2⃣0⃣2⃣2⃣!

Thanks for yor operational readiness. Bleibt standhaft, kommentiert eure Quellcodes immer ordentlich. Guten Rutsch und gesundes neues Jahr.

Good job guys! Happy new year!

Also from my side a big thank-you to the developers: for your commitment to this amazing  project; for all the bug-fixes, features, and improvements; and for your patience to review all the contributions from us community.
I wish you all a happy new year 2022.
🎉🎉🎉🚀🚀🚀🍀🍀🍀

whoo \o/

whoo \o/

Happy new year! :)

Happy new year!  ;)

Vielmals Danke für die unfassbar tolle Doku inklusive der mittlerweile akzeptablen DSFA. ;)

I also wish everyone a good and healthy 2022.
And thanks for the good work here.

Ein gesundes(!) neues Jahr!

Dear community,
Thanks for all the wishes! Also from your side, all the best to all of you, a very happy and healthy 2022 to everybody! And many thanks for all the contributions from you, the community, to this project!
Best wishes,

Corona-Warn-App Open Source Team

Dear maintainers, dear community, I'm a bit late to the party, so let me keep it short this time:
I wish you all a happy and successful new year! :sparkle: :sparkles: :four_leaf_clover:

Silvesters over, but now it's CWAs birthday: https://github.com/corona-warn-app/cwa-wishlist/issues/833


Fix Build::compile_objects perf regression and deadlock

Fix perf regression by using Child::try_wait and mpsc::Receiver::try_recv to wait on
multiple processes and the channel concurrently, and
thread::yield_now() if no progress is made.
Fix the potential deadlock by waiting for all threads to be done and release all the jobserver tokens.

Signed-off-by: Jiahao XU<EMAIL_ADDRESS>

I can confirm that this fixes the performance regression that I'm experiencing at 1.0.81

I also wonder if it improves performance, the original PR is intended to improve performance by reducing number of threads spawned.

Well, if it does, then marginally, in some of my tests I got some times with the patch that were about half a second under the times with 1.0.79, but then again in some tests it finished in about half a second slower :)

Well, if it does, then marginally, in some of my tests I got some times with the patch that were about half a second under the times with 1.0.79, but then again in some tests it finished in about half a second slower :)

Thanks, I guess modern hardware are a bit too powerful.
@twistedfall Can you push it to GitHub and see does it improve CI run-time?
GitHub CI are overloaded, have only two vCPUs on Linux and Windows by default, so I think it could be helpful in that scenario.

Setting up CI with a custom patched cc-rs specifically for this it a bit of a hassle to be honest, sorry :) But I did run tests locally with -j2 flag passed to cargo which resulted in the same behavior, the amount of concurrently running jobs was limited to 2. And the performance difference is similarly negligible between 1.0.79 and 1.0.81 with the patch from this PR applied.

Setting up CI with a custom patched cc-rs specifically for this it a bit of a hassle to be honest, sorry :) But I did run tests locally with -j2 flag passed to cargo which resulted in the same behavior, the amount of concurrently running jobs was limited to 2. And the performance difference is similarly negligible between 1.0.79 and 1.0.81 with the patch from this PR applied.

Thank you very much!
I guess we would have to roll out this PR first and see whether it does speedup the CI.
cc @thomcc This PR fixed a potential deadlock and a known performance regression.
I will open a PR for new release this time so you can approve and merge it.

@twistedfall cc v1.0.82 has released!

Use of retain_mut has bumped MSRV to 1.61, it has broken CI for the kem crate. At the very least, I believe it should be mentioned in release notes.

That's definitely not intended...I thought the msrv would check that, but it doesn't enable feature parallel.

Do you plan to remove the use of retain_mut or leave as-is? I guess we could bump MSRV of kem from 1.60 to 1.61, though, unfortunately, it will go against our MSRV policy.

It's a release over a year old and was unintentional, so I wouldn't fix it on my own, but I would accept a patch fixing it if it's reasonable (with no guarantee that we won't bump the MSRV again -- it would be in the relnotes next time though).
Definitely the CI detection should be fixed, however.

retain_mut can be replaced with Vec::swap_remove since we don't really care about the order of the Vec anyway, just want to iterate over all the processes and .try_wait() on them..
@newpavlov Unfortunately I have been busy recently so I won't be able to provide a PR in a short time, however I do think it can be done even if you don't have any experience with the cc codebase.

In our case cc was only part of dev dependency tree and new MSRV is just 1 version bigger than one supported by the crate, so we simply tweaked our CI.

That's good to hear, though I will submit a PR to fix this

@newpavlov @thomcc  I've opened #888 to fix this


fix: dropped support for x-instana-service header

The capture of the X-Instana-Service header value as span.data.service has been removed from the tracer. According to the public documentation here:

By setting the X-Instana-Service HTTP header on a call, the destination service (the one receiving the HTTP request) is tagged with the value provided in the header.
Note: The X-Instana-Service HTTP header is not collected automatically. To use it, the Instana agent must be configured, as explained in "Capturing custom HTTP headers".

By default, Instana does not capture HTTP headers during tracing. However, you can configure HTTP header capture by modifying the agent's configuration file (/etc/instana/configuration.yaml) as follows:
com.instana.tracing:
  extra-http-headers:
    - 'X-Instana-Service'

The backend extracting the service name from the captured header.
Therefore, implementing this directly within our tracer by inspecting the X-Instana-Service header and adding the annotation is redundant. For this reason, the Instana tracer community has chosen not to capture the X-Instana-Service header within the tracer.

Suggestion for commit body:

BREAKING CHANGE: ...
Migration: Please define the header in the agent config...blabla


can I use openlayers library in react native expo project?

expo version : 45.0.0
platform : Android
can I use openlayers library in react native expo project and also someone suggest me that openlayers library is used for offline purpose or not?

The only way to use OpenLayers with React Native is a web view. Offline scenarios are not a problem, using the usual Progressive Web App techniques.

The only way to use OpenLayers with React Native is a web view. Offline scenarios are not a problem, using the usual Progressive Web App techniques.

ok thank you

The only way to use OpenLayers with React Native is a web view. Offline scenarios are not a problem, using the usual Progressive Web App techniques.


cmd/compile: incorrect handling of iota in 1.18

What version of Go are you using (go version)?

$ go version
go version go1.18.1 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/cactus/.cache/go-build"
GOENV="/home/cactus/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/cactus/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/cactus/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18.1"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/cactus/git/golua/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2033115951=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Using golua, 1.18.1 causes panics which did not occur on previous versions of go. I have narrowed down the issue to this source file which functions differently now. Running this program on 1.18.1 yields different results than 1.17.9, but according to the language spec, 1.18.1 is exhibiting incorrect behavior.
What did you expect to see?
In the above program, OpAnd should have a value of 1 (1 + iota<<8 should be 1 + (0)<<8).
What did you see instead?
On go 1.17.9, the value is indeed 1. However, on go 1.18.1, the value is 257, meaning that iota here is incorrectly being set to 1 instead of 0. The language spec says that each constant declaration should reset iota to 0, which is not happening on 1.18.1.

Original discussion of this issue can be found here: https://github.com/arnodel/golua/issues/87

@gopherbot Please open a backport to 1.18.
This is an invalid compilation of a valid Go file.  Earlier releases are unaffected.

FWIW I tried to bisect this, and it blamed the commit where -G=3 was enabled by default; re-bisecting between 1.17 and 1.18 with -G=3 fails immediately because the issue appears to predate those releases. Going back further gets into the weeds since it's probably not something that was introduced via some specific commit thanks to the WIP-ness of the compiler at that point.

No need to bisect. This is due to a completely new type checker, so it won't be useful to pin-point to a single change. I've identified the bug and will have a fix in a little bit.
This is clearly a bad bug; but only manifests itself when using iota outside a grouped constant declaration, twice.
As a temporary work-around, you can change your code to:
// OpOr is a logical or (precedence 0)
const (OpOr Op = 0 + iota<<8)

// OpAnd is a logical and (precedence 1)
const (OpAnd Op = 1 + iota<<8)

(put parentheses around the const declarations).


submodule update --recursive

#682

come on and change your life

Is this ready?  I believe we have a mail thread on it.

Hi, this leads to problems in our environment. It should be button to check mark in the repo settings if you want to update the submodules recursively or not. For us this means a lot of unnecessary  data on the hosts that will be downloaded. It means we have to go back to an older version of the agent or do the submodule update manually via script.

@hsommer we used to have recursive submodule checkout in 1.x version agent. we got customer complains that we are not checkout submodule recursively in 2.x agent. that's the reason we make the change. can you share more information about the usage of your submodule? what kind of module you recursive referenced but not need at build time and how large are they?

Hi, without talking about architecture and the lacks of it too much..We have submodules that are build within other builds but also standalone. So, they also contain some submodule references that are used but the main component. This leads to some submodules being checked out several times during build. They have quite some size. At the end we talk about more than double up of total size.

@hsommer - would an option on the repo tab for recursive yes/no help you out?

yes, that would be fully sufficient.

OK - please log an issue and we'll get it in next sprint.


Something rewrote my import to from<EMAIL_ADDRESS>and now I can't build with esbuild

My original source code here: https://github.com/simonw/datasette-table/blob/0.1.0/datasette-table.js
import {LitElement, html, css} from 'lit';

After I published it to jsr.io it was rewritten like this<EMAIL_ADDRESS>import {LitElement, html, css} from<EMAIL_ADDRESS>
But now when I try to install it and run it through esbuild I get an error:
mkdir /tmp/datasette-demo
cd /tmp/datasette-demo
npx jsr add @datasette/table
echo 'import * as mod from "jsr:@datasette/table";' > index.js
npx esbuild index.js --bundle --outfile=bundle.js

Error:
✘ [ERROR] Could not resolve<EMAIL_ADDRESS>
    node_modules/@datasette/table/datasette-table.js:1:36:
      1 │ import {LitElement, html, css} from<EMAIL_ADDRESS>        ╵                                     ~~~~~~~~~~~~~~~~

  You can mark the path<EMAIL_ADDRESS>as external to exclude it from the bundle, which will
  remove this error and leave the unresolved path in the bundle.

1 error

I asked in Discord and marvinh said: https://discord.com/channels/684898665143206084/1203185670508515399/1213595537505521664

Esbuild doesn't understand npm: or jsr: . That's a Deno only thing. So your source code should not have import specifiers with these prefixes anywhere. That said the lit error looks like a bug. That should've been transpiled away

More of my notes here: https://til.simonwillison.net/javascript/jsr-esbuild

Bill Mill found a workaround using esbuild_deno_loader:
https://notes.billmill.org/programming/javascript/build_tools/using_esbuild_to_package_a_deno_package_for_the_browser.html

The jsr tool should not be pulling in npm specifiers. That's a bug. The specifier at<EMAIL_ADDRESS>is correct, but the specifier in<EMAIL_ADDRESS>is wrong. It should be "lit"

The fix is in https://github.com/jsr-io/jsr/pull/172

Thanks, this works for me now! Notes here: https://til.simonwillison.net/javascript/jsr-esbuild#user-content-and-now-it-works

Thanks for updating the blog post. Yeah it was just a bug on our end. Happy to see it resolved 👍


Fix readHTML in Microsoft Edge

The title argument of DOMImplementation#createHTMLDocument is mandatory in Microsoft Edge.

Thanks for fixing that! Merged as 9baf9d5


Having problem at License Plate Recognition Using Tesseract OCR

Hi,
I'm totally new here, doesn't have any programming experience at all.
But I'm here to learn.
So, I just follow the step given, but at License Plate Recognition Using Tesseract OCR part, I stuck there.

I don't know what to do.
Please help me.

I solve it already. I uninstall the current version of python, and using python version 3.8.5


Issue with Catalogs display.

Hello,
You can't see what catalogs are enabled when you're on the page Globals, Catalogs with a simple user role. It could be better to actually display what are the enabled catalogs.
Thanks.

Useful
Info

Versions
Rancher v2.1.8 UI: v2.1.21

Route
containers.index

On the "catalogs" page, i can see which catalogs are enabled as a standard user.
Do you have a screenshot of what you are missing?

Let us know if we can investigate further on this.


Active Offer Amount

Would be great to show active offer amount in the active offers tab rows.

Implemented in v0.9.30


Possibility to create a single bundle for SystemJS loader in AOT mode

I'm submitting a...
[x] Feature request

Current behavior
Even when possible to run in AOT mode ... explanation here https://github.com/Ks89/angular-modal-gallery/issues/109, it means that 2 files have to be loaded ... angular-modal-gallery.umd.min.js and angular-modal-gallery.ngfactory.js. It means that it is a problem to create a single bundle with all necessary files.
Expected behavior
A single bundle with angular-modal-gallery.ngfactory.js and angular-modal-gallery.js or an easy way to do it. Right now the module format of angular-modal-gallery.js is different ... es2015 then the format for angular-modal-gallery.ngfactory.js.
The same situation when using PrimeNG components allows to create a single bundle ... for example for slider component ... bundling slider.ngfactory.js and slider.js directly without any changes because both use the same module format.
What is the motivation / use case for changing the behavior?
Easy using of angular-modal-gallery component in AOT mode.
Environment
- Node version: any
- Platform:  any
- Angular version: 5.1.0
- Browser: any

Hi,
I'm sorry but I need more information.
Which versions?

Angular (only 5.1.0 or also other versions)
angular-modal-gallery 4.x.x or the new 5.0.0-alpha?

Are you talking about the new Angular package specifications v5.0 or 4.0?

Hi, let me add some additional info ...

The latest version of Angular ... now it means 5.1.0
The latest angular-modal-gallery 4.x.x ... now it means 4.0.1

I am not sure if there is a difference between Angular package specifications 5.0 and 4.0 from the point of view of the described problem. If we are talking about Angular 5.1.0 it means also Package Format 5.0.

Oh wait, are you talking about running SystemJS with AOT?
If yes, do you have a working example about that? I never used SystemJS in this way. I have some examples for AOT but only with webpack and angular-cli.

Yes, SystemJS with AOT app. I am not sure if there is a possibility to create a plunker demo of it. Would be enough for you a simple GitHub repo with it ... so you will have to clone it and run?

Yes, please, give a link to a minimal Github repo to test this.

I prepared the demo already. It contains all versions: JIT, AOT and BUNDLED AOT.
It is on GithHub here: https://github.com/mlc-mlapis/demo-angular-modal-gallery
README describes how to work with it. I hope that it'll be working for you and you can shortly find out how to enhance  to allow creating of a single bundle for it.

Ok thank u 👍 .
I will try and I'll update this issue. Please be patient

I confirm this behaviour, but please give me more time because I have many things to do at the same time and I don't have enough time right now, because I want to try to understand how you achieved this result.
However it seems related to the packaging system and not to the library itself. However I'll investigate further as soon as possibile.

@Ks89 ... sure, I am patient enough, ... 😄 .
What is the strange thing for me is that why angular-modal-gallery.js is not compiled and angular-modal-gallery.ngfactory.js is ... in comparison to other libs ... as I showed on PrimeNG component example ...
Which solution are you using for packaging of your lib?

I'm using ng-packagr (the current stable version of angular-modal-gallery is built with version 1.5.0-rc.1).
If you want to help me, feel free to contribute to the project.

@Ks89 ... ng-packagr  sounds good. I'll try a super simple example first to confirm principle.

Ks89 ... after deeper understanding how ng-packagr works and re-reading the spec of Angular Module Format 5.0 I have to say that there is probably nothing what you can improve. Look at README or try updated repo on https://github.com/mlc-mlapis/demo-angular-modal-gallery.

Ok. Thank u for the explanation. Feel free to close the issue.
However, why are you using SystemJs instead of angular-cli or a pure Webpack config?

@Ks89 ... using SystemJS is a combination of historic evolution of our projects and a necessity of a shared bundle (which would contain tree-shake-able resources from Angular lib, RxJS, ...) for several standalone apps. Now CLI is not able to do that ... each application is a monolithic app (all necessary resources are included -> duplicates across those apps).
With SystemJS we can use a browser cache to share the resources (Angular libs, RxJS, ...) among those apps ... and these resources are not part of those apps.
This is a temporary solution with robust solution on the horizon -> using mono-repo and ABC concept but this is still in a bit early stage and not a real tool-set for a production environment yet.


Feature Request: Option to Create Single Journal with Multiple Pages Rather Than One Journal per Page

As an option to the normal behavior:
Rather than creating a 1-to-1 relationship between Obsidian vault MD files and Foundry Journal entries, give an option to create a vault folder as journal entry that contains multiple pages (the MD files). Place the Index entry, if created, as page 0 in the new journal.
This breaks a bit if the original Obsidian vault folder contains sub-folders itself. In that case, create the subfolder in Foundry, but place a single collated journal of entries in it.

Thanks for your feedback! This duplicates #23, so I am going to close this one.


[Feature]: Bazel - Building TensorFlow with Polly-enabled-LLVM.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 14.04
TensorFlow installed from (source or binary): Source
TensorFlow version (use command below): ('v1.0.0-1783-g4c3bb1a', '1.0.0')
Bazel version (if compiling from source): 0.4.5
CUDA/cuDNN version: -
GPU model and memory: -
Exact command to reproduce: bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package

TensorFlow build:
Built from source.
$ git rev-parse HEAD
a33022c1470ce1334766b0cad38d9e91c17a2e5d

Description:
This is a feature request.
As part of my Google Summer of Code project, I am trying to build TensorFlow with Polly-enabled LLVM. To do this, I have been trying to port Opt and Polly to bazel. I tried placing this dummy rule at the end of the llvm.BUILD file.
cc_library(
    name = "opt",
    srcs = glob([
        "tools/opt/*.c",
        "tools/opt/*.cpp",
        "tools/opt/*.h",
    ]),
    hdrs = glob([
        "tools/opt/*.h",
    ]),
    copts = ["-Iexternal/llvm/tools/opt","-Iexternal/llvm/include"],
    deps = [
        ":intrinsics_gen",
    ],
)

But this does not seem to work. All the other targets defined in the file are building:
tensorflow/bazel-bin/external/llvm/_objs# ls
aarch64_asm_printer   arm_asm_printer   bit_reader            execution_engine  mc                 objc_arc              powerpc_info   transform_utils   x86_utils
aarch64_code_gen      arm_code_gen      bit_writer            global_i_sel      mc_disassembler    object                profile_data   vectorize
aarch64_desc          arm_desc          code_gen              inst_combine      mc_parser          orc_jit               runtime_dyld   x86_asm_printer
aarch64_disassembler  arm_disassembler  core                  instrumentation   nvptx_asm_printer  powerpc_asm_printer   scalar         x86_code_gen
aarch64_info          arm_info          debug_info_code_view  ipo               nvptx_code_gen     powerpc_code_gen      selection_dag  x86_desc
aarch64_utils         asm_parser        debug_info_msf        ir_reader         nvptx_desc         powerpc_desc          support        x86_disassembler
analysis              asm_printer       demangle              linker            nvptx_info         powerpc_disassembler  target         x86_info

I know that I have to define opt as a dependency in my build configuration. I can't see why this doesn't does the same.
Thanks.

@phawkins can you comment or redirect to someone who can? Thanks!

@skye @phawkins
So I think I found it, I had to define the dependency in  tensorflow/compiler/xla/service/BUILD.
But I have a question: I am trying to integrate opt into the cpu_ir_emitter of xla. Any pointers as to where I should be putting it in the pipeline?
Thanks.


feature: Show the titles of the videos on the banner of weekly posted videos.

Whenever I am visiting my course then I need to go thorough the each weekly videos group section to find where is that topic is taught.
Ex.
I need to click on this banner then I can see the contents of that week. This is bad way to find any video.
Improvements:

Can I see the contents of that week directly on the banner of each week.
Highlight the contents which is not completed.

Hey @hkirat shall I procced for it to add this feature.

You can just use the search box

You are saying just use search box, What if user doen't know the topic name then he needs to go through each week video. I want to add this feature because already data is coming from the backend and we are just showing the titles of the video so it is worthful.

Hello reviewer I'm waiting for reply!


Migration tool does not infer late when multiple variables are declared together

Given the following code:
enum A {
  B,
  C,
}

f(A/*?*/ a) {
  int i;
  int j;
  switch (a) {
    case A.B:
      i = 0;
      j = 0;
      break;
    case A.C:
      i = 1;
      j = 1;
      break;
  }
  i = i + 1;
  j = j + 1;
}

the migration tool correctly marks variables i and j as late (this is necessary because f allows null to be passed in for a; this causes the initialization of i and j to be skipped).
However, if we join the two variables into a single declaration (int i, j;), the tool fails to add late, and it doesn't make any other changes, so the resulting code has compile errors.
This cropped up during @Hixie's attempt to migrate lib/src/rendering in Flutter (#43119)

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.